Develop Bugs

Unlock bootloader on GT-I9250 without wipe and without root

Hi! After latest OTA update I was left with an unbootable Galaxy Nexus (zygote couldn't start) and I lost root (su needed activitymanager up). So I needed to unlock to revive the phone, but I really didn't want to lose my data. After some exploration I could come up with a way to unlock bootloader without wipe and without root. I have seen several questions about this here and this was deemed impossible, so I decided to share my findings and expect they might help someone. Should work with GSM tuna phones.
Components for success:
— unlocking without wipe via putting a byte in param partition (needs root):
[1] http://forum.xda-developers.com/showthread.php?t=1650830&page=15
— OMAPFlash, a low-level utility for manipulating and flashing chipset (usually used to unbrick phones)
[2] http://forum.gsmhosting.com/vbb/f63...9250-galaxy-nexus-gt-i9100g-gt-i9300-1465412/
Take the two of them and you have a solution. I could successfully flash unlock byte to param partition using OMAPFlash.
A sketch of a guide:
1. Boot windows xp, download OMAPFlash (http://d-h.st/XNv), connect a turned off phone without battery, install drivers for omap device. (Mod edit: I've updated the download link.)
2. Dump a part of param partition. You don't need to dump the whole partition, but I think it is safer if you dump a sector-aligned area (512*n). I used 4KB (8 sectors).
Code:
OMAPFlash -omap 4 -2 -p OMAP4460_TUNA_8G_HS_PRO -t 36000 chip_upload [email protected] 1000 param.img
chip_upload is for downloading data from device memory
[email protected] is the start of params partition (check /sys/block/mmcblk0/mmcblk0p4/start, multiply by sector size 512 and convert to hex)
1000 is to copy 4KB.
Sometimes the process stalls (esp if you try to download larger dumps), just reconnect and retry.
3. Verify that the content is similar to first 4 KB of the dumps of param partitions attached in the thread [2]. For me they matched entirely.
4. Change the byte at offset 124 (0x7C) from 01 to 00.
Code:
echo -ne "\x00" | dd obs=1 count=1 seek=124 of=param.img conv=notrunc
5. Flash it back to the device.
Code:
OMAPFlash -omap 4 -2 -p OMAP4460_TUNA_8G_HS_PRO -t 36000 chip_download [email protected] param.img
Reboot, you are unlocked.
Additional links:
[3] http://forum.gsmhosting.com/vbb/f634/gt-i9250-pinout-enjoooy-1463061/ GT-I9250 JTAG pinout. Not directly releavant to the guide, but I found it while searching for solution, thought that can help someone in future.

Additional reading
The dangers of OTA when you have root, or why I was stuck with an unbootable phone at all
I learned the hard way that OTA may cause unpleasant results if you are trying to preserve root and mess with filesystem.
I was trying to preserve root in a way similar to one used by rootkeeper apps: put a copy of su somewhere in /system and make it immutable. So I went and put my su to /tts (thought that it's unprobable that OTA will do something there), and made it immutable.
And then the update came. As part of the the update process it copied a new version of /system/usr/share/zoneinfo/zoneinfo.version file and the file got 660 perms (package_extract_dir("system", "/system") in the update_script). Then it went on to recursively fix permissions so that the mentioned file would be made readable (set_perm_recursive(0, 0, 0755, 0644, "/system")). But the set_perm_recursive was met by immutable su in tts directory, chmod returned error and the recursive process was stopped before it got to zoneinfo.version file. So the latter file remained unreadable.
Unfortunately during startup zygote preloadsClasses, static constructor in some sqlite class needs DateFormat, and DateFormat reads zoneinfo. And fails cause it's unreadable. Exception, System.exit. Phone boot stuck.
To work my copy of su needs to send a message to ActivityManager service using binder. I wrote a dirty mock for AM but servicemanager didn't accept my fraud, it checked uid. I tried to bypass preloadClasses with overflowing system file descriptors count to prevent zygote from reading preload class list, but somehow it didn't succeed. Thus the only option I had was unlocking bootloader.
So it may end bad if you mess with /system on a stock rom with locked bootloader and want to receive OTA. It may seem natural, but sometimes the changes seem irrelevant, and then a chain of small failures leads you to loss of everything: boot, root, and data.

This is great work! Kudos to you for figuring it out.
By the way, where did you find the syntax for OMAPFlash commands?

efrant said:
This is great work! Kudos to you for figuring it out.
By the way, where did you find the syntax for OMAPFlash commands?
Click to expand...
Click to collapse
There are some docs in OMAPFlash_tuna.zip package. The most interesting is OMAPFlash.txt that lists options and commands and has some examples.
Also I was lucky that there is a complete example for unbricking GT-I9250 in Targets/Projects/tuna. This is where I took the options specific for this device.

nichtverstehen said:
There are some docs in OMAPFlash_tuna.zip package. The most interesting is OMAPFlash.txt that lists options and commands and has some examples.
Also I was lucky that there is a complete example for unbricking GT-I9250 in Targets/Projects/tuna. This is where I took the options specific for this device.
Click to expand...
Click to collapse
Exactly. I haven't needed this yet, but i had looked in those board files, cross examining with omap 4460 manual that can be found on the web. Thanks for sharing.
I was not aware that JTAG method had been found. Great news.
Sent from my i9250

Works!
Awesome - this worked for me! Unlocked, unrooted, TAKJU Galaxy Nexus w/JB 4.2.2. I used OMAPFlash_tuna.zip (download link).
I had issues when the downloaded param.img file was long, so I replaced 1000 with 200 in the commands. Regardless, it still took me probably 5-10 tries on each command to get it working (unplugging and replugging the phone in between), and sometimes it would freeze up and I'd have to restart Windows. If it takes longer than 5 seconds, you should press Ctrl+C and restart that step.
My problem was that one of my volume buttons is messed up, and as a result the fastboot screen doesn't work - Windows doesn't detect a fastboot device, and none of the hardware buttons or the touchscreen works either. As a result I needed to unlock the bootloader without using fastboot (oem unlock), and this did the trick!
Also, on Windows, I downloaded a hex editor (i.e., HxD) to do the editing. My modified param.img (only 512 bytes) is attached as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thank you!!! It worked for me too!
The volume buttons on my Galaxy Nexus didn't work and I can't recharge the battery via USB. The USB works only as data connection. Despite all these issues on my phone, it worked for me too!!
I replaced the size in the commands from 1000 to 400 (1024 bytes = 2*512), and I had to put the battery on the phone.

Sweet jesus I cannot express enough gratitude for this post. While I was a little worried about bricking my device, it would up working perfectly.
A couple of confusing points for anyone out there trying to do this:
- The dump / reflash should only take a few seconds each. If it hangs, cancel and re-start the process.
- Install the drivers with the device OFF but plugged in. You will have an OMAP device without a driver in your device manager. Update the device driver and you're good to go.
- I didn't know how to get the dd command to work on windows, so I also went the Hex editor route it it worked flawlessly
- The only snag I ran into was that it did not boot into my flashed CWM after doing an "adb reboot recovery" from the stock rom. It went back to the stock android recovery. From there I did "fastboot boot cwmrecovery.img" and installed my rom and gapps. After that initial boot, it rebooted into recovery just fine! It seems like a weird glitch (maybe just a one-off).
Cheers

techobrien said:
- Install the drivers with the device OFF but plugged in. You will have an OMAP device without a driver in your device manager. Update the device driver and you're good to go.
Click to expand...
Click to collapse
This is a critical step right here. This thread either should be linked on the 101 FAQ if it's not already or stickied.
a maguro wrote this.

techobrien said:
- The only snag I ran into was that it did not boot into my flashed CWM after doing an "adb reboot recovery" from the stock rom. It went back to the stock android recovery. From there I did "fastboot boot cwmrecovery.img" and installed my rom and gapps. After that initial boot, it rebooted into recovery just fine! It seems like a weird glitch (maybe just a one-off).
Cheers
Click to expand...
Click to collapse
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely. It shouldn't exist in custom ROMs, which would explain why after installing a ROM and Gapps you were fine.
This is pretty cool. Nice find OP.

cupfulloflol said:
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely. It shouldn't exist in custom ROMs, which would explain why after installing a ROM and Gapps you were fine.
This is pretty cool. Nice find OP.
Click to expand...
Click to collapse
This post thread have not been getting the attention it deserves..
Beamed from my Maguro.

cupfulloflol said:
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely.
Click to expand...
Click to collapse
Good to know for next time round. The flimsy headphone ribbon cable is the bane of my existence and it seems like a somewhat common problem. I didn't think that the custom rom would touch the bootloader so I was confused, but /system/ makes sense. Thanks for the tip.

Just in case anybody was wondering, this method also worked for my Verizon GNex LTE. I also used a HEX editor.

Hi,
i'm thinking to use this method to unlock my Nexus' bootloader, in order to gain root privileges without wiping the memory.
This because i need to try and undelete files i have lost on my phone, to do this i need the root but i can't use the normal procedure that would wipe forever all the data i need to restore.
As i am new to this kind of operations, i never even rooted my Android phones, i wanted to ask if this procedure can fit my situation, and if there are any risks....
Thank you very much
EDIT: It worked perfectly!!
Thank you very much!!

Did anybody try it on MAGURO device? Does it require any change in the procedure?

Um... The op (and others) did it on a maguro? After all, the title says "on GT-I9250".

Isn't a i9250 a Maguro?
Beamed from my Grouper

Mod edit: removed quote of the OP.
Is WinXP really required for this process or will it work on newer versions of Windows ie Win8?

mielli1 said:
Is WinXP really required for this process or will it work on newer versions of Windows ie Win8?
Click to expand...
Click to collapse
Please do not quote the first post of threads when you reply.
As for your question, if you can get the driver to install on Windows 8, the program will work fine. The driver installs fine in Windows 7 by the way.
Don't forget to disable driver signature verification if you are trying to install drivers in Windows 8.

Windows 8 - stuck at installing drivers
beekay201 said:
This is a critical step right here. This thread either should be linked on the 101 FAQ if it's not already or stickied.
a maguro wrote this.
Click to expand...
Click to collapse
I have a Nexus with a broken volume up button, so am trying this method as a way of unlocking the bootloader and rooting my device.
When I plug the powered off device into the usb port, constantly get the sounds of a device being inserted, and then unplugged (two different beeps.) This continues until I unplug the phone.
Is this the step where I should get a "found new hardware" notification? It is not happening for me, and I'm wondering if this is Windows 8 related.
FYI - I have already disabled driver signature verification.

My adventures with my ZenWatch over the weekend

I spent a lot of the weekend trying to root my Zenwatch (on 4.4.2w), or get a custom recovery working. Here's what I have tried and found out so far. They locked it down pretty damn well.
Unlocking bootloader and accessing recovery
Go to Settings -> About -> Press Build Number 7 times -> Swipe right, Developer Options now shows under About.
Theres a few different options including an Asus utility to check sensors and such.
To get into recovery or fastboot, you need to active ADB Debugging, unplug the watch than plug it back in, then run "adb reboot recovery" or "adb reboot fastboot"
To unlock bootloader, you need to push the reset button on the back to select.
In recovery, swipe right to left to show screen, up and down to select, and left to right to select.
My Findings so far
The kernel source and ROM source are not available anywhere.
There is no way that I can find to get root. I even went as far as loading towelroot onto the watch through adb install, but it just hangs and eventually closes.
There is no way I have found to build a custom recovery with CWM or TWRP.
There is no way I have found to dump the boot or recovery partitions.
There is no su binary preinstalled. Attempting to link a su binary has come up null.
dump_image binary is not installed, nor can you get it to install.
Trying to install any packages through stock recovery gives signature error.
Trying to use dd command to dump boot or recovery ends with "permission denied"
Trying to use "fastboot oem saveprt2sd recovery -n recovery.img -a" ends with "invalid page size". Same with trying to dump boot in this fashion.
Trying to boot either the LG G Watch or Samsung Gear Live unsecured boot images comes back with "(remote) dtb not found" (No surprise here, but it was worth a shot)
fstab is root only.
/dev tree is root only.
all init.asus scripts are root only.
You can install packages with "adb install" but all the standard root gaining apps stall or force close. Towelroot seems to try, but locks up after hitting "make it r4in." trying to change the modstring on v3 (with triple tap title) does not provide a field to change.
Kernel command line is root only.
I browsed EVERY file on my watch hoping to find a hole that I could build off of, but alas, I had failed.
Even trying to do "adb backup" results in "Confirm on Device," and closes immediately afterwards, with no confirm.
I believe that unless they release either the kernel source or the full ROM source, we are unable to root or modify any options.
Which really sucks, because the "OK Google" screen is REALLY F****** BRIGHT.
if anyone has success, please share

I thought I'd try installing one of my own apps and see what happened. It installs okay, but it crashes immediately. I'm guessing it's because I'm using something that's not supported, probably sound or Webkit (the app displays an HTML tutorial the first time it's run). I haven't had time yet to run it from the debugger and see what's going wrong.

I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/

dgjenkins said:
I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/
Click to expand...
Click to collapse
To build a custom recovery, you need to pull the existing recovery or boot partition off of the device and pull partition information (fstab, which is not readable by user on this device) and the build.config information (which is also not readable by user), or pull the fstab.anithias and build.config from the running system (which again is not accessible to the standard user account).
Without that information, you can't build a custom recovery. I've been attempt this for almost 2 weeks now, and its locked down pretty well. The G Watch and Gear Live allowed access to the needed files, but Asus did not with the ZenWatch.
If anyone is willing to risk bricking their watch (by getting past the dtb error when trying to boot the LG G Watch or Samsung Live recovery images, which is a long shot in itself) to get the openRecovery/CWM/TWRP to install and work to the point of getting ADB working through recovery mode, I can do the rest to build the recovery.
I just dont want to risk bricking mine quite yet, as the google play store was out of stock the last time I checked to purchase a "testing" watch.

@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip

CSX321 said:
@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip
Click to expand...
Click to collapse
Kernel source code
Sent from my SM-G900P

@z3nful And an ota? Would it be usefull?
OTA LWX48S

I haven't had a chance the last week to work on this with the holiday season going on and having to run my store. When I get a chance to get back to it, I'll let you guys know what I come up with

I started trying to build the kernel yesterday, but I'm not getting far yet. I've been a developer for over 30 years, but most of my Linux/other UNIX experience was over 10 years ago, and I've forgotten a lot.
I've tried a couple of different compiler versions, but I'm pretty quickly running into different issues with either one. I'm not sure what version Asus used, but it's apparently not either of the ones I've tried. Also not entirely sure what configuration to use. I'm using the 8226 configuration now, because there's no 8026 configuration in the source archive. I don't know if that's suitable or not.
All-in-all, I may not be out of my depth, but I'm out of my area of experience, at least. Any tips, @z3nful?
Edit...Is there any useful information in the OTA zip file? It's available. Partition info or a boot image or something?

@z3nful and @CSX321 - Any luck moving forward on this? I'm not a programmer, but I'd be glad to offer any assistance if needed!

btonetbone said:
Any luck moving forward on this?
Click to expand...
Click to collapse
No progress here, I'm afraid. I think I just don't know enough about this environment to do it, without devoting a lot more time to learning.
I've also lost some motivation, because there doesn't really seem to be anything I need root for on the watch. About the only thing I would do if I had it is delete a couple of apps, but since Mini Launcher lets me hide apps, I don't care so much about actually deleting them.

Has anyone had success with adb push? It seems the system is read only and doesn't allow for pushing files. Is root required?

Asus is good at locking down their devices, requiring you to register it with them to get an app to unlock it (you also acknowledge that by downloading the app you are voiding your warranty). I really wouldn't be surprised if they did the same thing with this watch and just haven't released the unlock app yet.
I am kinda disappointed to see this sort of thing from a device licensed by Google. It's like the exact opposite of the Nexus line.

@z3nful Just some helpful links, thought I could help a wear user out (I have the G Watch)
Kernel --> https://android.googlesource.com/kernel/msm/+/android-msm-anthias-3.10-lollipop-wear-release
Also, Gohma ROM for gwatch includes a boot img that auto roots android wear. (http://forum.xda-developers.com/g-watch/development/rom-gohma-2-0-12-15-2014-t2974052) Named rboot.img, I think it might be worth a shot to run "fastboot boot rboot.img" to see if it does anything.

Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.

I tried, no luck.. Gave the same "dtb not found" error.
Here is a thread related to DTB in boot images: XDA Topic 2428117
Attached is the rboot.img if anyone wants to see if they can modify it to pass whatever DTB issue is making it fail, if that's even possible. I will dig a little bit deeper once I get out of the office.
The error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rboot.img, zipped:
View attachment rboot.zip
Ignore my sig, it is several years out of date
Regards,
weasel5i2
Doc Ames said:
Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.
Click to expand...
Click to collapse

How to up date LeEco Le Pro3, no root, no TWRP, 100% Stock

I am a New Pro3 owner, and a old XDA flasher. These days I just want stability and battery life. So given no one is getting OTA updates because the LeEco US office are... well about to close doors? Or at a minimum they are not maintaining the OTA servers as of today (09/06/2017 MM/DD/YEAR). I took it on myself to figure out how to get the updates and how to do them.
What you need:
These three files, nothing else.
5.8.019_sta.zip
5.8.020_sta.zip
5.8.021_sta.zip
Found here.
https://drive.google.com/open?id=0B2EAg2WU3OwpSHRMdEZ0Tks0a3M
It is very simple, but also very finicky.
1. Download 5.8.019_sta.zip, rename to update.zip
2. Place the update.zip on the root directory of your phone storage
3. Go to Settings -> System update (about 3/4 the way down)
4. Top right corner will see three vertical dots, tap the dots and select "local update" (see image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. When you select "local update" if you did everything correct it should say "Update package found bla bla bla". Click continue.
That's it, it will load the file, reboot in to recovery and flash the file.
Then just follow this process for each file 19s->20s-21s. Make sure you remove the last update.zip before you put the new one in place.
Now, here is how it can be "finicky". For some reason using an android file manager to rename the files to "update.zip" corrupts the file in some way... and the update once you get in to the recovery section of the auto update fails. BEST PRACTICE IS TO DOWN LOAD THE FILES TO YOUR PC, THEN RENAME IT ON YOUR PC TO update.zip AND TRANSFER TO YOUR PHONES ROOT STORAGE.
Why? no clue, but you can try it either way... but if you find it failing try ^^

Hi, thanks for sharing the files, nuch appreciated.
For some reason I cannot acces the files today ?

bethe said:
Hi, thanks for sharing the files, nuch appreciated.
For some reason I cannot acces the files today ?
Click to expand...
Click to collapse
https://drive.google.com/drive/folders/0B2EAg2WU3OwpSHRMdEZ0Tks0a3M?usp=sharing
made a new sharable link

Hi and thanks for sharing. If you don't mind could you tell me
what's included in these updates?

dallorsj said:
Hi and thanks for sharing. If you don't mind could you tell me
what's included in these updates?
Click to expand...
Click to collapse
Just google "5.8.019_sta" (for each one)
You should be able to find the change-log somewhere.

Edward,
Works great! Just some notes for everyone else.
1) Make sure phone is set to MTP (Media Transfer Protocol).
2) If you are using Windows and are 'dragging and dropping' onto the device just copy to the phone icon in file explorer, that will put it at / which is where it needs to be.
3) When I did this and used the local update option, it didn't even prompt for 19S, it just moved forward and started the upgrade and rebooted the phone. All it asked me to confirm was right when I selected local update to 'make sure' I wanted to do it. No version check, etc. I was on 18S, btw.

Are you saying you went straight from 18s to 21s? Without the intermediary updates? Are you bootloader locked or unlocked?

Thanks for all of those OTAs. I was restoring my device to stock and every update kept failing when I tried to manually update it. Note: Update will fail if your OTA is not called update.zip.
IT IS CASE SENSITIVE; in other words, it will fail if you name is 'Update.zip'.
Thanks again and this post should be stickied tbh.

If my phone has twrp and on a custom rom could i use the same steps to go back to stock?
Sent from my LEX727 using XDA-Developers Legacy app

Ugh
I could not resist the $199 sale on Amazon despite knowing all the shortcomings. I am starting to regret this decision ... somewhat ... especially since Amazon no longer lets you return phones & can only exchange within 10 days.
Anyhow, I was excited when I got this phone the next day after I ordered it but my 1st frustration was that I could not do any system updates. I read about all the improvements like app drawer & really wanted them but no, it kept saying my system was up to date (still on 18 mind you). Which led me to this thread ... but now my computer will not recognize the Le Pro 3 when I connect it. I tried different USB ports & cords and no luck so far. I also cannot download the above links from my phone so I am kind of stuck @ the moment ...
I do, however, think that I got the work around for the notification issue as they seem to be coming in now, so that's good.
Overall, the phone mostly works so I am not totally mad at this purchase but getting the updates would be nice.
Quick Question: if I try to install Lineage OS, will the phone still have the T-Mobile wifi calling?
Thank you all for this super helpful forum for basic users like me.
UPDATE: Rebooting the phone got my computer to recognize the phone. However, I have followed all the instructions above (downloaded the file, renamed it update.zip, dragged & dropped it right on the phone in explorer, but it still will not find it with the local update.
I downloaded the Cheetah File Manger which shows you the Root Directory, which did not look like where I put mine. So I tried to move it over to the Root Directory but it would not let me paste it there. So close ...................................... calling it a night ...... sigh

i wanted to follow your guidelines but there is no system update in settings in my device. i ve bought it from banggood if that info is useful.

Could you please add check sums for these files.
Thanks in advance!

Try to update my X727 from 5.8.018s to 5.8.019s:
1. Renamed 5.8.019_sta.zip to update.zip and copied it to phone root.
2. From File Manager pressed on update.zip and choose "Upgrade", it has started updating "Upgrading, do not power off the phone".
3. The phone rebooted and entered to Recovery with an error message: "Failed to update! Cause: Installation failed"
4. Presses Back-button and tried again "Update system" and got an error message "Failed to update! Cause: APK not found"
What's wrong?

[ROM][UNOFFICIAL][N][UsU]CypherOS 4.2 [H815]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is Cypher. An extension to pure Android. Cypher tries maintain the purity of Android while offering useful features for users. The goal is to give the highest level of performance whilst achieving Simplicity.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
**** These builds are for UsU'd devices only ****
UsU? http://bit.do/unlockg4
Get your builds from my leech service
http://leech.binbash.rocks:8008/aoscp/nougat/h815-UsU/
Note: Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Become apart of our G+ community - JOIN
REMINDER
If you're having issues and want to submit a report (Logcat) please make sure you are reporting from the stock kernel, not a modified kernel. Modified kernels can break or fix, even improve things. It depends. I can't get a full clue of the issue when you're not running the original kernel.
Click to expand...
Click to collapse
​
Features:
- Status bar Customization
- Changeable icons
- Quick pulldown
- Smart pulldown
- Notification count
- Clock position
- Seconds in clock
- Date design
- Quick Settings
- Brightness slider
- Brightness icon
- Tile tap customization
- System
- Screenshot partial and full
- Scrolling cache customization
- Power menu customization
- One-handed mode
- Specials
- UsU compatible build so no need for a baseband package to be flashed!
- Using latest TITAN kernel sources
Requirements
Your device need to be unlocked by UsU
Your bootloader stack should be on MM (see FAQ #20 for how to upgrade your bootloader stack)
Latest TWRP - PREVIEW build: click
Clean modem partition (so no UsU baseband flashed) - see Installation topic for details
Installation
If you have ever flashed the UsU baseband package: Clean flash the modem partition in TWRP:
- TWRP flashable N modem (recommended)
Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash AOSCP
Flash GApps (7.1 - ARM64) if you like to use google apps
Flash SuperSU / Magisk if you want root
Boot (will take long on first boot!)
Enjoy
Credits
LineageOS
AICP
PureNexus
AOKP
Dirty Unicorns
Paranoid Android
kessaras
steadfasterX
and more..
Sources
Kernel
device tree

reserved 1

reserved 2

Error Status 7
Using lastest TWRP preview, I get the above error.
I know to fix it I just need to delete the "assert" line in the .zip, but I thought this ROM (UsU's supported) had the model that TWRP show.
I mean, the model according to;
(*) TWRP: LGUSU
(*) ROM (assert): p1, h815, h815_usu & g4 (not 'LGUSU' as shown in TWRP).
Thanks!

the_naxhoo said:
Error Status 7
Using lastest TWRP preview, I get the above error.
I know to fix it I just need to delete the "assert" line in the .zip, but I thought this ROM (UsU's supported) had the model that TWRP show.
I mean, the model according to;
(*) TWRP: LGUSU
(*) ROM (assert): p1, h815, h815_usu & g4 (not 'LGUSU' as shown in TWRP).
Thanks!
Click to expand...
Click to collapse
correct the removal of that line is not needed but i can see that the model detection is wrong on your device.
Please share the recovery log file!
Sent from my LG-H815 using XDA Labs

steadfasterX said:
correct the removal of that line is not needed but i can see that the model detection is wrong on your device.
Please share the recovery log file!
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
OK. Here is the recovery.log

ROM works great. Very smooth with no bloatware.
Just one problem, when setting the lockscreen type in security it doesn't seem to apply correctly. I have set it to "pattern" but it keeps defaulting back to swipe. I then tried to set it to PIN and it just crashes when I go back into lock screen settings now.

the_naxhoo said:
OK. Here is the recovery.log
Click to expand...
Click to collapse
ok the reason is clear:
download: https://androidfilehost.com/?fid=746010030569958479
extract it
flash in fastboot:
Code:
fastboot flash laf laf_UsU.img
fastboot flash raw_resources rawres_UsU.img
Then boot into TWRP again and share the recovery log again.
Rich Rich said:
ROM works great. Very smooth with no bloatware.
Just one problem, when setting the lockscreen type in security it doesn't seem to apply correctly. I have set it to "pattern" but it keeps defaulting back to swipe. I then tried to set it to PIN and it just crashes when I go back into lock screen settings now.
Click to expand...
Click to collapse
seems to be a known issue for some rare cases.
I cannot reproduce it here it works fine so far.
Have you clean flashed ? Format(!) data as written in the OP?

steadfasterX said:
ok the reason is clear:
download: https://androidfilehost.com/?fid=746010030569958479
extract it
flash in fastboot:
Code:
fastboot flash laf laf_UsU.img
fastboot flash raw_resources rawres_UsU.img
Then boot into TWRP again and share the recovery log again.
Click to expand...
Click to collapse
lol its worked... thx!

steadfasterX said:
seems to be a known issue for some rare cases.
I cannot reproduce it here it works fine so far.
Have you clean flashed ? Format(!) data as written in the OP?
Click to expand...
Click to collapse
Yes, did the "format data" wipe before install.
It may be a slight difference in the way I set the device up. I did select "pattern lock" when I first installed the OS. I noticed this was not working then re-set "pattern lock" in settings a few times but nothing worked. I then tried setting it to "pin lock" and now it just crashes the settings app every time I try to change the security.
It's not a big issue for me as the G4 is just used as a work phone. I'll flash the next build when available and see if that sorts the problem.

Rich Rich said:
Yes, did the "format data" wipe before install.
It may be a slight difference in the way I set the device up. I did select "pattern lock" when I first installed the OS. I noticed this was not working then re-set "pattern lock" in settings a few times but nothing worked. I then tried setting it to "pin lock" and now it just crashes the settings app every time I try to change the security.
It's not a big issue for me as the G4 is just used as a work phone. I'll flash the next build when available and see if that sorts the problem.
Click to expand...
Click to collapse
oh well i have tried PIN only.. sorry havent read carefully. will try the pattern thing..

Hello thanks for all of your efforts I follow your toppic for long time and finally yesterday I unlocked my h815tr device successfully. And I flash the ROM you shared in this topic. All works fine thanks again. I just have a problem about Yahoo mail account. I can't add it to my Gmail app. I enter my mail and password I allow the permissions about mail and at final step screen shows 404 can't found. But I solve this by using Yahoo's mail app. But it would be good if I can use Gmail app. And I realised that if I take a photo and immediately if I tap to photo I took the camera app crash but if I wait few seconds and then if I tap the photo it's all ok. I'm not complaining don't get me wrong, again thank you so much.

Is this ROM support quick charge? Because when I plug to QC adapter, phone says slow charging. Original adapter says slow charging also

emrtnl said:
Is this ROM support quick charge? Because when I plug to QC adapter, phone says slow charging. Original adapter says slow charging also
Click to expand...
Click to collapse
slow charging is everywhere due to power hal and due to our sources.
In the rom to show if its fast normal or slow it needs to read the voltage not the ampere. but in kernel we read no voltage. we only read the ampere.
Totally stupid since its the ampere that matters , but thats how things work there.
EDIT:
i mean it's always showing slow for the reason i explained , but it's not.

kessaras said:
slow charging is everywhere due to power hal and due to our sources.
In the rom to show if its fast normal or slow it needs to read the voltage not the ampere. but in kernel we read no voltage. we only read the ampere.
Totally stupid since its the ampere that matters , but thats how things work there.
EDIT:
i mean it's always showing slow for the reason i explained , but it's not.
Click to expand...
Click to collapse
Thanks for that information. At v29 ROM previously I use I could see quick charging notification, that's why I asked.

emrtnl said:
Thanks for that information. At v29 ROM previously I use I could see quick charging notification, that's why I asked.
Click to expand...
Click to collapse
stock lg stuff handle many things differently from the open source.
but we do not have access there, only LG has.
What we do in this side of development is to work with the open source.
LG rom may read the ampere. Or they may have added a voltage reading. We do not know...

have done all steps but reboot into twrp always (((

floast said:
have done all steps but reboot into twrp always (((
Click to expand...
Click to collapse
I had the same problem.
While in TWRP go to Advanced, then select Terminal
type this command:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
keep in mind that there's a space before if and before of, like below replaced with underscores:
dd_if=/dev/zero_of=/dev/block/bootdevice/by-name/fota
If you don't get an error, just reboot the phone and it will go into the system.
I found this solution here and adjusted it a bit:
https://forum.xda-developers.com/showthread.php?t=2451696
---------- Post added at 03:24 PM ---------- Previous post was at 03:06 PM ----------
#EDIT: Ok, so funnily enough, me helping the guy above also risked having him screw his mac address up the same way I describe as a separate problem below Looks like we need to adjust he process below to our model:
https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12
Sorry for being clumsily underqualified, everyone.
#EDIT2: A better and easier solution that might work for us:
https://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
And now my own problem. I cannot connect to any WiFi network and noticed that my mac address is 00:00:00:00:00:00.
I stays that way even if I do the whole process again: format data, flash the rom, flash the gapps, flash supersu.
After I reboot into the system and wait for it to initialise and enter the initial phone config, where it asks me to connect to a WiFi network I can see my zeroed out mac address at the bottom. If I try to connect to a 5G wifi network or 2.4G one it says "Connecting" and then just displays "Saved" under the selected network. It doesn't ever connect. I checked one 5G network and two different 2.4G networks, triple-checking the password each time.
In "settings>about phone>status>WiFi MAC address" I also see 00:00:00:00:00:00.
I checked /system/etc/wifi/bcmdhd.cal file and the attribute there seems normal:
Code:
macaddr=00:90:4c:c5:12:38
I've seen in a thread concernig a different phone that some people advise to put the desired mac address into a /system/etc/wifi/.mac_info file and reboot but this doesn't work (might be dumb to even try that but it didn't hurt so I gave it a shot).
I wanted to try working around the issue using a mac address changer app off of Play Store but I can't connect to any Google Account (in the settings or any Google app), even on the cellular data - seems like the authentication looks at my mac and doesn't like it.
I considered finding and sideloading an apk of some mac address changer app, but that's doesn't seem like a viable solution - people say it only works temporarily and I'm not even sure if that will fool Play Store authentication if it really does rely on mac add somehow.
Any ideas where else the system might be pulling that 00:00:00:00:00:00 from or where the mac is missing?
Does fixing the mac issue might also fix the Google Services authentication problem?

Derpthunder said:
I had the same problem.
While in TWRP go to Advanced, then select Terminal
type this command:
keep in mind that there's a space before if and before of, like below replaced with underscores:
dd_if=/dev/zero_of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/fota
Also, the soc.0/f9824900.sdhci/ part might be different in your case. If after typing the above command you'll get an error saying that there's no such file, type these commands:
And it will tell you if you have soc.0 or something else. Then type (if you had something else than soc.0 in the previous step, replace soc.0 with what it told you)
and you'll see what you have instead of f9824900.sdhci
Once you know what you have instead of soc.0/f9824900.sdhci/, just type that command again replacing that section:
If you don't get an error, just reboot the phone and it will go into the system.
I found this solution here and adjusted it a bit:
https://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
That's why
/dev/block/bootdevice/by-name/
exists. It's always pointing to the correct SOC path.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
That's why
/dev/block/bootdevice/by-name/
exists. It's always pointing to the correct SOC path.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Thanks, I edited the post to add the correction.
#EDIT: I don't quite remember if I actually overwrote the fota or the misc to get out of booting into TWRP loop. The G2 and G5 threads advise to overwrite the misc and the G3 one to overwrite fota. Is there a difference?
Plus, I added this since it turned out that my mac problem was due to that exact fix I recommended:
Derpthunder said:
#EDIT: Ok, so funnily enough, me helping the guy above also risked having him screw his mac address up the same way I describe as a separate problem below Looks like we need to adjust he process below to our model:
https://forum.xda-developers.com/sho...0&postcount=12
Sorry for being clumsily underqualified, everyone.
#EDIT2: A better and easier solution that might work for us:
https://forum.xda-developers.com/lg-...g-ota-t2907508
Click to expand...
Click to collapse

[EOL][ROM][UNOFFICIAL][12.1] LineageOS 19.1 for Galaxy Note10 5G [d1x][N971N][ENCRYPTION]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Known Issues
You tell me
Requirements
Required firmware version is N971NKSU2HVE9.
Instructions
You can follow the instructions on the wiki page for d1: https://wiki.lineageos.org/devices/d1/install
Please remember to upgrade your firmware through Odin. Put the provided file in the BL slot.
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads
Builds: https://sourceforge.net/projects/lineageos-samsung-note10-5g/files/lineage-19.1/
GApps: https://wiki.lineageos.org/gapps.html
Firmware: https://sourceforge.net/projects/firmware-samsung-note10-5g/files/
Source
https://github.com/Rocky7842/android_kernel_samsung_exynos9820/tree/lineage-19.1
Contributors
Rocky7842
Linux4 for maintaining the trees for exynos982x devices.
LineageOS team

About Safetynet
The safetynet on this ROM can pass basic integrity, but not CTS.
Due to the official stance of LineageOS team, and spoofing the build fingerprint may causes issues because Android uses build fingerprint changes as a signal to clear and rebuild several caches, I will not put the modifications in the ROM itself. Instant I'll put the information here, you can choose to do it or not.
To pass CTS:
We have to install Magisk(or Lygisk), then install both Universal SafetyNet Fix and MagiskHidePropsConf modules.
Reboot, enter adb shell.
In adb shell, type in "props". Now Magisk should ask you for su, accept it.
Type in "1". Which is edit device fingerprint.
Type in "samsung/d1xks/d1x:12/SP1A.210812.016/N971NKSU2HVE9:user/release-keys".
Type in "y" to confirm.
Type in "n" to avoid reboot now.
Type in "b" to go back to main menu.
Type in "5". Which is add/edit custom props.
Type in "n". Which is new custom prop.
Type in "ro.build.version.security_patch".
Type in "2022-05-01".
Type in "y" to confirm.
Type in "y" to reboot.
Now the security patch date and build fingerprint should be what we set, and Safetynet should pass now.

Working, I can confirm

A working rom for d1x, am I dreaming?

jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Give it a try and you'll know if it's a dream or not.

jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Thanks to Rocky7842

jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Please give some feedback if you already try it.

Rocky7842 said:
Please give some feedback if you already try it.
Click to expand...
Click to collapse

Bro can you give me rooting tools for note 10 N971N? Please or even just the link bro please!

JÅ“508 said:
Bro can you give me rooting tools for note 10 N971N? Please or even just the link bro please!
Click to expand...
Click to collapse
What do you mean...? Just use magisk.

Rocky7842 said:
What do you mean...? Just use magisk.
Click to expand...
Click to collapse
i want to root my samsung note 10 n971n version. Maybe you can help me

I don't know where to download the root files.

Enable Developer Options
Under developer options enable OEM unlock
Download latest firmware for your phone
Go-to https://galaxyfirmware.com/model/SM-N971N/
Download the right file for your device (just choose one)
Download magisk
Once this is downloaded, we can install it.
With that done, extract. The contents of the firmware you downloaded earlier.
Copy the AP file onto your phone.
Now open magisk app and tap on the install button and, make sure that the recovery mode Option stays checked, now tap the next option to bring us to the method which lets us select and patch a file.
Locate that AP file and then load it up into magic before tapping. The, let's go button.
After magisk is done patching the files..
Now you're going to be told that there is an output file, You just need to make sure that we look at where this file is and copy it to your PC.
Put the device into download mode,
Now extract the Odin program and open it
connect phone to PC
disable the auto reboot option under options tab
Locate the firmware that was downloaded and the patched file.
start loading these files into Odin.
click the BL button and load the file that begins with the letters BL.
Remember the same with the CSC and we need to load the CSC file (not the home CSC file).
Now click the AP button right here, but instead of loading, the AP file, instead we're going to load the AP file magisk patched.
there is a progress bar on the phone itself as well on the PC.
So once you get a green pass message
Device is not going to reboot because we need to manually reboot to instantly however.
With Odin finished, unplug USB cable. now, We're going to press the VOLUME DOWN and the SIDE BUTTON till the screen go black, let go of the VOLUME DOWN button while still holding the SIDE BUTTON and press and hold the VOLUME Up button. So you're gonna press these two buttons to force the device to reboot.
After reboot locate and open magisk

VoLTE Supported?

Alexis Levin said:
VoLTE Supported?
Click to expand...
Click to collapse
VoLTE is not supported.

New build uploaded. Security patch date is now 2022-11-05.

I flashed recovery using Odin and can enter Lineage recovery mode successfully.
But when I use adb sideload <ROM.zip>, it cannot detect my devices to sideload the custom ROM.
There's no devices under adb devices either.

ngfuong said:
I flashed recovery using Odin and can enter Lineage recovery mode successfully.
But when I use adb sideload <ROM.zip>, it cannot detect my devices to sideload the custom ROM.
There's no devices under adb devices either.
Click to expand...
Click to collapse
If you sure you have put the phone into sideload mode, check your cable/driver or change a computer.

Rocky7842 said:
If you sure you have put the phone into sideload mode, check your cable/driver or change a computer.
Click to expand...
Click to collapse
Thank you for replying. I changed to Linux and now I can sideload the .zip file.
However, after sideloading using this command:
adb sideload lineage-19.1-20221113-UNOFFICIAL-d1x.zip
The phone returns this:
E: Signature verification failed
E: error: 21
Then I choose Install anyway, and receive:
Installing update...
E: Failed to find update binary META-INF/com/google/android/update-binary
Any idea what I missed?

ngfuong said:
Thank you for replying. I changed to Linux and now I can sideload the .zip file.
However, after sideloading using this command:
adb sideload lineage-19.1-20221113-UNOFFICIAL-d1x.zip
The phone returns this:
E: Signature verification failed
E: error: 21
Then I choose Install anyway, and receive:
Installing update...
E: Failed to find update binary META-INF/com/google/android/update-binary
Any idea what I missed?
Click to expand...
Click to collapse
Please try re-download the file. If it still fails, try install the "20221023" build.
I didn't test the "20221113" version since I'm doing the bring up of A13. There's a possibility that the file was corrupt in the uploading procedure. No one reports that so far, though.