I have a N5 stock/rooted. Does this mean I will have to unroot just to update my phone to KitKat 4.4.1 when it comes out? I would prefer to keep the stock ROM but want the camera upgrades that 4.4.1 is supposed to offer.
so reroot if you are going to have to unroot, big deal. if you want to update from the stock update, you will lose root. then all you have to do is flash a custom recovery then flash the latest supersu in your recovery. it takes about 3-4 minutes of work(without toolkits)..
simms22 said:
so reroot if you are going to have to unroot, big deal. if you want to update from the stock update, you will lose root. then all you have to do is flash a custom recovery then flash the latest supersu in your recovery. it takes about 3-4 minutes of work(without toolkits)..
Click to expand...
Click to collapse
Ok. So you are saying that I can unroot, upgrade to 4.4.1, then flash a backup recovery from something like TWRP and be all set? I was under the impression that flashing a custom recovery will also wipe out the current OS version.
shampiaj said:
Ok. So you are saying that I can unroot, upgrade to 4.4.1, then flash a backup recovery from something like TWRP and be all set? I was under the impression that flashing a custom recovery will also wipe out the current OS version.
Click to expand...
Click to collapse
flashing a custom recovery doesnt wipe anything(except the stock recovery). unlocking the bootloader wipes data, not the recovery
simms22 said:
flashing a custom recovery doesnt wipe anything(except the stock recovery). unlocking the bootloader wipes data, not the recovery
Click to expand...
Click to collapse
Thanks.
Doesn't ADB side-loading still work with custom recovery?
You need to unroot
shampiaj said:
I have a N5 stock/rooted. Does this mean I will have to unroot just to update my phone to KitKat 4.4.1 when it comes out? I would prefer to keep the stock ROM but want the camera upgrades that 4.4.1 is supposed to offer.
Click to expand...
Click to collapse
Yes, you need to unroot to recive the OTA, in my case, i have a custom rom, so i will go stock if the update improves perfomance,because i have installed the camera fix v 1.3 and I'm happy with it
jt3 said:
Doesn't ADB side-loading still work with custom recovery?
Click to expand...
Click to collapse
I was just about to copy the steps you posted before your edit! If side loading works for OTAs (which i need the answer for as well), that writeup you had posted would've been clutch!
AceKingNYC said:
I was just about to copy the steps you posted before your edit! If side loading works for OTAs (which i need the answer for as well), that writeup you had posted would've been clutch!
Click to expand...
Click to collapse
Yeah, sorry. I posted them, then started thinking whether I'd ever actually done it with a custom recovery. Here are the steps for side-loading with a STOCK recovery. I'd be curious to see if it works with custom. I KNOW it works to install the OTA update (which, you'll need to download, so... not technically an OTA, but you get the idea), since I always seem to be at the back of the OTA list, so I never wait. Once the OTA zip is posted, I've always side-loaded it.
Download the update.zip from Google to your PC that you would like to install on your Nexus.
Move the file into your Platform-Tools folder.
Plug in your android device to your Windows machine. Make sure USB Debugging is enabled.
To test that you have adb up and running, and that your device is recognized, open a command prompt and change to the folder where ADB is installed.
Type: adb devices
You should get a serial number followed by “device.” (like this: 0a1b2c3d4e5f6789 device). This shows that you have a good connection to your device.
Still at the command prompt, type: adb reboot bootloader
Your device will now reboot to the bootloader.
Use Volume Down on your device to until you see “Recovery.”
Select it with the Power button.
Your device will boot to an Android logo with a exclamation mark.
To jump past this, press Volume Up and Power at the same time (Hint: Push Power first, then push Volume Up).
You will now be in stock recovery.
With Volume Down, highlight “apply update from ADB.” Press Power to choose it.
Back to your PC command prompt, type: adb sideload <filename of update.zip>
If your adb is working properly, you should see the file transfer to your device in adb.
Once that finishes, your device will begin to update. Be patient, it takes a bit.
Once it has finished, simply reboot and enjoy the update.
EDIT: In my original response post, I'd noted that the OP was obviously familiar with ADB, since he'd rooted his Nexus, I left that out of this post, so if you're wondering what the heck ADB is, that's why this post seems incomplete. ADB is part of the Android SDK. There are many other threads that cover its installation and use, but it's a good tool to have, even if you don't root (for side-loading updates, via the above steps, for example... no root required!).
jt3 said:
Yeah, sorry. I posted them, then started thinking whether I'd ever actually done it with a custom recovery. Here are the steps for side-loading with a STOCK recovery. I'd be curious to see if it works with custom. I KNOW it works to install the OTA update (which, you'll need to download, so... not technically an OTA, but you get the idea), since I always seem to be at the back of the OTA list, so I never wait. Once the OTA zip is posted, I've always side-loaded it.
Download the update.zip from Google to your PC that you would like to install on your Nexus.
Move the file into your Platform-Tools folder.
Plug in your android device to your Windows machine. Make sure USB Debugging is enabled.
To test that you have adb up and running, and that your device is recognized, open a command prompt and change to the folder where ADB is installed.
Type: adb devices
You should get a serial number followed by “device.” (like this: 0a1b2c3d4e5f6789 device). This shows that you have a good connection to your device.
Still at the command prompt, type: adb reboot bootloader
Your device will now reboot to the bootloader.
Use Volume Down on your device to until you see “Recovery.”
Select it with the Power button.
Your device will boot to an Android logo with a exclamation mark.
To jump past this, press Volume Up and Power at the same time (Hint: Push Power first, then push Volume Up).
You will now be in stock recovery.
With Volume Down, highlight “apply update from ADB.” Press Power to choose it.
Back to your PC command prompt, type: adb sideload <filename of update.zip>
If your adb is working properly, you should see the file transfer to your device in adb.
Once that finishes, your device will begin to update. Be patient, it takes a bit.
Once it has finished, simply reboot and enjoy the update.
Click to expand...
Click to collapse
That would be key if this works... guess we shall have to wait and see. So with this method you theoretically won't have to unroot/re-root or lose any data/settings, correct?
shampiaj said:
That would be key if this works... guess we shall have to wait and see. So with this method you theoretically won't have to unroot/re-root or lose any data/settings, correct?
Click to expand...
Click to collapse
If it works, that's correct. ADB side-loading works on a stock, unrooted device (even with locked bootloader), so it doesn't mess with anything. It's possible that it won't work with a custom recovery. Even if it does, you may lose root in the process, but since rerooting your phone doesn't wipe the data (since the bootloader is already unlocked), that wouldn't be a big deal.
Also... even if it DOESN'T work, as stated before, it's unlocking the bootloader that wipes your device, so flashing a stock recovery THEN following these steps should certainly work with no data loss. Having said that... a nandroid backup is always your friend.
---------- Post added at 12:34 PM ---------- Previous post was at 12:11 PM ----------
Hate to respond to my own post, but after doing some checking, it looks like adb sideloading will still work with a custom recovery, assuming your recovery supports it. Both TWRP and CWM supposedly have supported this for quite awhile, so any version new enough to work with a Nexus 5 should certainly work.
Keep in mind that sideloading is not the same as flashing a custom ROM. Think of it more as a manual way to launch an update. So... you'll need to comply with any prerequisites of that update. So... say you're flashing from KRT16M to KRT16Z (or whatever). You'd need to get the correct KRT16M-to-KRT16Z update for your device. That update is certainly going to assume that you're bone-stock, so if you've added any mods or otherwise screwed around with your system files after rooting, the update may fail, or it may simply undo your mods (including unrooting your device). As I said before, a current nandroid backup is always your friend.
jt3 said:
If it works, that's correct. ADB side-loading works on a stock, unrooted device (even with locked bootloader), so it doesn't mess with anything. It's possible that it won't work with a custom recovery. Even if it does, you may lose root in the process, but since rerooting your phone doesn't wipe the data (since the bootloader is already unlocked), that wouldn't be a big deal.
Also... even if it DOESN'T work, as stated before, it's unlocking the bootloader that wipes your device, so flashing a stock recovery THEN following these steps should certainly work with no data loss. Having said that... a nandroid backup is always your friend.
---------- Post added at 12:34 PM ---------- Previous post was at 12:11 PM ----------
Hate to respond to my own post, but after doing some checking, it looks like adb sideloading will still work with a custom recovery, assuming your recovery supports it. Both TWRP and CWM supposedly have supported this for quite awhile, so any version new enough to work with a Nexus 5 should certainly work.
Keep in mind that sideloading is not the same as flashing a custom ROM. Think of it more as a manual way to launch an update. So... you'll need to comply with any prerequisites of that update. So... say you're flashing from KRT16M to KRT16Z (or whatever). You'd need to get the correct KRT16M-to-KRT16Z update for your device. That update is certainly going to assume that you're bone-stock, so if you've added any mods or otherwise screwed around with your system files after rooting, the update may fail, or it may simply undo your mods (including unrooting your device). As I said before, a current nandroid backup is always your friend.
Click to expand...
Click to collapse
Yeah, I'm stock/rooted but have flashed some mods. Luckily I keep all the .zip files so it sounds like the worst case scenario is that I'd have to re-flash the mods and re-root, which isn't a big deal. And I always make a nandroid before I do something. I'm more worried about data loss since it's taken me weeks to get to where I am now
Thanks for all this information, dude.
There's going to be boat loads of these exact same threads all over General, Q/A and Development when the update is released. Not sure why there isn't a sticky pertaining to OTA updates with regard to root, recovery, etc to curb all these posts.
To the OP, just use ADB and manually flash the images you want. Then simply flash SuperSU in recovery. Done.
If you don't know how to use ADB, then you need to do yourself a favor and learn about it. It'll save you time in the long run and you'll realize that GUI and CLI toolkits aren't necessary.
jt3 said:
If it works, that's correct. ADB side-loading works on a stock, unrooted device (even with locked bootloader), so it doesn't mess with anything. It's possible that it won't work with a custom recovery. Even if it does, you may lose root in the process, but since rerooting your phone doesn't wipe the data (since the bootloader is already unlocked), that wouldn't be a big deal.
Also... even if it DOESN'T work, as stated before, it's unlocking the bootloader that wipes your device, so flashing a stock recovery THEN following these steps should certainly work with no data loss. Having said that... a nandroid backup is always your friend.
---------- Post added at 12:34 PM ---------- Previous post was at 12:11 PM ----------
Hate to respond to my own post, but after doing some checking, it looks like adb sideloading will still work with a custom recovery, assuming your recovery supports it. Both TWRP and CWM supposedly have supported this for quite awhile, so any version new enough to work with a Nexus 5 should certainly work.
Keep in mind that sideloading is not the same as flashing a custom ROM. Think of it more as a manual way to launch an update. So... you'll need to comply with any prerequisites of that update. So... say you're flashing from KRT16M to KRT16Z (or whatever). You'd need to get the correct KRT16M-to-KRT16Z update for your device. That update is certainly going to assume that you're bone-stock, so if you've added any mods or otherwise screwed around with your system files after rooting, the update may fail, or it may simply undo your mods (including unrooting your device). As I said before, a current nandroid backup is always your friend.
Click to expand...
Click to collapse
This is super clutch ! I thanks alot for this
Im rooted/unlockled BL and have TWRP. I havent done ANYTHING else, not even Titanium backup for fear it would affect my ability to OTA. So it seems that I should be good right?
I will almost certainly sideload the update, as I've never had a device get an OTA less than a week after it has gone live.
Assuming a bone-stock, unrooted Nexus 5, should I consider returning the phone to the factory-set Dalvik JIT instead of the ART compiler (been using this since day one) prior to side loading the downloaded OTA update (when that becomes available)?
Sent from my Nexus 5 using Tapatalk
Guys, maybe I missed something, but I did a totally different thing on my Nexus 7. When The first release of 4.4 released, I flashed manually with flash-all.sh. Then I flashed TWRP, and rooted my N7. Couple of days later I received OTA update, I didn't do anything just clicked to the flash update. It is reboot my device, and the OTA successfully installed automatically from the TWRP, and rebooted my N7. After this I reboot my device to TWRP and flashed the superuser.zip. I rebooted the N7 and everything works well.
This way is not possible to receive and install the next OTA for N5?
Sent from my Nexus 7 using Tapatalk
Okay, got the 4.4.1 update. Here's the scoop.
My N5 is unlocked and rooted with CWM. I've installed one root application, which increases my vibrate intensity to 100% (N5 is defaulted to 63%), otherwise, i'm bone stock.
Applied sideload via directions I posted previously. There are a couple steps that change due to the different recovery, but they were easy to figure out (like, where to choose "update from sideload"). Once I rebooted after the sideload, I got the "Android is upgrading" message (good sign). Once it finished, I was running 4.4.1. (KOT49E).
I did lose root though. A quick reboot into recovery mode showed that I'd lost CWM too, and was back to the stock recovery. Reinstalled CWM and rerooted. Back to normal.
Here's the link, for anyone who wants it: KRT16M to KOT49E Update.
I have it on root and CWM also. I get to the step of install from sideload. I use CWM to say "install from sideload" and it starts ADBd but i can't connect to it via the pc. If i am in just android i can ADB. So something is up there.
jt3 said:
Yeah, sorry. I posted them, then started thinking whether I'd ever actually done it with a custom recovery. Here are the steps for side-loading with a STOCK recovery. I'd be curious to see if it works with custom. I KNOW it works to install the OTA update (which, you'll need to download, so... not technically an OTA, but you get the idea), since I always seem to be at the back of the OTA list, so I never wait. Once the OTA zip is posted, I've always side-loaded it.
Download the update.zip from Google to your PC that you would like to install on your Nexus.
Move the file into your Platform-Tools folder.
Plug in your android device to your Windows machine. Make sure USB Debugging is enabled.
To test that you have adb up and running, and that your device is recognized, open a command prompt and change to the folder where ADB is installed.
Type: adb devices
You should get a serial number followed by “device.” (like this: 0a1b2c3d4e5f6789 device). This shows that you have a good connection to your device.
Still at the command prompt, type: adb reboot bootloader
Your device will now reboot to the bootloader.
Use Volume Down on your device to until you see “Recovery.”
Select it with the Power button.
Your device will boot to an Android logo with a exclamation mark.
To jump past this, press Volume Up and Power at the same time (Hint: Push Power first, then push Volume Up).
You will now be in stock recovery.
With Volume Down, highlight “apply update from ADB.” Press Power to choose it.
Back to your PC command prompt, type: adb sideload <filename of update.zip>
If your adb is working properly, you should see the file transfer to your device in adb.
Once that finishes, your device will begin to update. Be patient, it takes a bit.
Once it has finished, simply reboot and enjoy the update.
Click to expand...
Click to collapse
jt3 said:
Okay, got the 4.4.1 update. Here's the scoop.
My N5 is unlocked and rooted with CWM. I've installed one root application, which increases my vibrate intensity to 100% (N5 is defaulted to 63%), otherwise, i'm bone stock.
Applied sideload via directions I posted previously. There are a couple steps that change due to the different recovery, but they were easy to figure out (like, where to choose "update from sideload"). Once I rebooted after the sideload, I got the "Android is upgrading" message (good sign). Once it finished, I was running 4.4.1. (KOT49E).
I did lose root though. A quick reboot into recovery mode showed that I'd lost CWM too, and was back to the stock recovery. Reinstalled CWM and rerooted. Back to normal.
Click to expand...
Click to collapse
So steps 13 and 14 in your list were done in CWM recovery instead of the stock recovery, correct? So if you're attempting the sideload using a custom recovery (I have TWRP), step 14 will be just choosing "apply update from ADB" or similar depending on which recovery you use. Everything else should be the same. Just wanted to make sure I understood your steps before attempting it myself.
Thanks!
---------- Post added at 01:12 PM ---------- Previous post was at 01:02 PM ----------
Alternatively, could we just grab the stock recovery image for 4.4 and reflash that using fastboot and apply the OTA when it lands on the phone? I'm thinking about doing that for my wife's Nexus 4.
Has anyone else lost 'reboot' from the power menu? I did have the Advanced 4 way reboot menu mod installed, but restored stock menu before TWRPing the update. It this a side effect of that or just 4.4.1?
Related
Hi All,
I have a Nexus S with a strange problem. It was originally stock, with no ROM mods at all, I then applied the SU patch get root happening - all worked fine for months.
I then manually applied the 2.3.3 update about 1 week ago. All working fine with no issues.
Today however, i've come to check my phone to find it 'frozen' on the boot screen.
Thinking it was just another lovely OS glitch, I battery pulled, to find it turned into an endless Nexus S boot loop. I booted into recovery, wiped the cache. Same Issue. I Booted into recover a gain, did a factory data reset. Same issue. I booted in recovery again and re-applied the 2.3.3 update which was on my memory from the previous update. Same issue.
The phone seems to either freeze during boot, or go into and endless loop.
Ideas? - The only other thing that i thought would be to do a bootloader unlock to wipe EVERYTHING... but im not sure if its worth it.
Why not? You can lock it back with fastboot oem lock command.
If you can get into clockwork recovery, you have access to adb, so be sure to use adb pull to grab everything off your sdcard before doing something drastic like a oem unlock to wipe the phone.
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.
distortedloop said:
If you can get into clockwork recovery, you have access to adb, so be sure to use adb pull to grab everything off your sdcard before doing something drastic like a oem unlock to wipe the phone.
Click to expand...
Click to collapse
Sadly, it was a locked bootloader, so had no luck with that
distortedloop said:
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Click to expand...
Click to collapse
As above, no permission to run recovery image.
distortedloop said:
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.
Click to expand...
Click to collapse
Couldn't get in as i had no ADB access.
In any case, i did a OEM unlock, and still had similar boot issues. The OS would boot, but despite flashing a custom clockwork recovery, it wouldn't get from BootLoad thru to Recovery. It also still had random hangs on boot.
I performed a fastboot flashall and also a fastboot erase boot and recovery. Leaving the phone totally empty.
I then re-loaded a rooted 2.3.3 with latest Clockwork and all worked fine. I've also updated radio to B3 - seems to work flawlessly.
I can only think something was screwy with the boot/recovery sections - very weird but all appears to work fine now.
Many thanks for the help.
g33k84 said:
distortedloop said:
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.
Click to expand...
Click to collapse
As above, no permission to run recovery image.
Couldn't get in as i had no ADB access.
Click to expand...
Click to collapse
You don't need recovery access to use adb. We might be miscommunicating, and it doesn't matter much since you've already nuked the phone, but what I was suggesting was a regular boot while trying to adb logcat the phone. I've used this technique to document the startup process in the past. Adb access loads up fairly soon in the process. If your phone wasn't even getting that far, of course it wouldn't work, but wanted to clear up what I was suggesting with that particular paragraph.
Hey all,
So tonight I attempted to install the Unofficial AOKP Jelly Bean posted here: http://forum.xda-developers.com/showthread.php?t=1862156
Before doing that, I followed the instructions to Unlock, Recovery, and Root my One S here: http://forum.xda-developers.com/showthread.php?t=1583427
After following those instructions, I then followed the instructions for AOKP Jelly Bean however my sdcard couldn't be mounted and the phone was in a boot loop if I didn't boot into fastboot by holding down the volume - and power buttons.
I attempted these instructions below however I couldn't get a stock recovery flashed.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Click to expand...
Click to collapse
Still caught in the reboot loop, I relocked and tried to run an RUU file found here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
I was able to successfully re-lock the phone however every time I try to run the RUU file it comes back with an error about 3-5 minutes into the process.
At this point, my phone boots into fastboot. At the top I have "Tampered, Relocked, Security Warning." My HBOOT is 1.14.0004 and my Radios is 1.08ts.50.02.16
I would appreciate any help if there is a solution. Thank you for your time!
Update: Not sure if this is helpful or not, but whenever I try to do something with The All in one toolkit the cmd window says device not found. Also, when I try to boot into recovery from fastboot, I get a green downward and circular arrows before getting the red triangle and exclamation point.
Update: Running the RUU mentioned above fails at the Signature stage and the cmd prompt when trying to write recovery returns "signature verify fail"
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
whozilla said:
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I am pretty sure I am S4 (tmobile USA). I am on a windows 7 home build, and the drivers should be installed (at least, I could use HTC sync before all of this). I'll definitely try again tonight. If anyone has any other suggestions they would be much appreciated!
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
whozilla said:
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help!
Here are my results:
HTC Sync is not running. Fastboot devices returns a device ID so that seems good. When trying to flash a stock recovery (that I got on this forum somewhere, but can't remember where) it sends it ok but I still get "remote: signature verify fail"
I unlocked the device and flashed TWRP 2.2.2.0 with the all in one tool kit. This put me back into the boot loop mentioned above. Once I manually got back into the bootloader and selected recovery, I was able to get into the TWRP recovery. At this point, I am kind of worried about doing anything. I would like to be able to push AOKP Unofficial JB if at all possible. Any further guidance would be appreciated!
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
usaff22 said:
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
It is clear to me that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
You have to fastboot push the AOKP zip through the bootloader I think.
Sent from my locked, tampered ville
Veritas327 said:
It is clear to fme that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
Click to expand...
Click to collapse
Just like the post above mine says, you have to adb push the file onto the sd card. I'm not to familiar with TWRP (using it actually got me into a bit of a dilemma) so I only know the process for CWM. If TWRP is anything like CWM then you have to be in recovery to adb push and have sdcard and system set to "unmont". It's pretty easy and there's a couple threads explaining how to do it. The command basically is :: adb push romname.zip /sdcard/romname.zip:: Note the space before "/sdcard" I'dpn't know if this ill help you or if you've solved your problem already but this is just my 2 cents, good luck!
Sorry for my late reply; I was rushed to the ER last night in excruciating pain. Looks like I'll be dealing with a kidney stone over the next few days.
So far, I have tried to push AOKP through fastboot. ADB says "no devices found" and when I type adb devices, I get "List of devices attached" and nothing under it. However, when I type fastboot devices, I do get a device ID. As of now, I am downloading the TWRP 2.3 recovery and will try to sideload with adb with that.
Update:
I was able to successfully install TWRP 2.3 and adb sideload the AOKP zip file. The phone then went back into a reboot loop, and I was able to get into recovery to install the .zip. The phone then rebooted, showed the HTC with red text screen very briefly, went to black, showed the HTC with red text screen again, went black, and now the aokp boot animation is repeating over and over. It has been doing so for about 5-7 minutes. I haven't yet installed gapps as mentioned in the AOKP post (I'm honestly not even sure what that is). Where should I go from here?
As a side note, the phone is plugged into power though the LED is not lighting up. It was at 98% when I flashed the .zip, but I obviously don't want it to die on me. Should I turn the phone off or is it still charging?
Veritas327 said:
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Click to expand...
Click to collapse
The newer hboot versions (1.13 and up) don't let you flash boot images in recovery, even if it reports success.
So there is technically no difference, except fastboot always works and recovery depends on hboot version.
Did you fastboot flash the boot image that comes with your rom?
-Jobo
Edit to add: So it seems that following the recipe in your post #1 did in fact make your sdcard mountable again, or did you do something else as well for that?
Fixed!
I ended up flashing the boot.img with fastboot and then going into recovery, factory resetting and then re-installing the rom (and gapps which I now know stands for google apps). I'll be playing around with the ROM but at least I have a working phone again!
I think, in the end, it came down to my sd card not being mounted and my lack of knowledge about how to fix it.
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
TROUBLESHOOTING:
If ADB Sideload gives you a Can't Read error, try these steps:
1. Download Large Address Awareness from here https://www.techpowerup.com/forums/threads/large-address-aware.112556/
2. Download ADB from here http://forum.xda-developers.com/showthread.php?t=2588979
3. Start Task Manager and kill adb.exe if its running
4. Load the adb.exe file from Large Address Awareness and check the flag button
5. Continue on with adb sideload
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
UPDATE:
This method might not be for everyone, and if you're not interested in sticking with stock 7.0 and potentially want to roll around to other ROMs you should follow this guide instead; http://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Great thank you! Question:
Will all the radio bands (T-MOBILE) still work as normal?
Have you try this out with Google Day Dream VR yet?
I had the note 7 and the Galaxy VR., Kinda of miss that.
dallas90733 said:
Great thank you! Question:
Will all the radio bands (T-MOBILE) still work as normal?
Have you try this out with Google Day Dream VR yet?
I had the note 7 and the Galaxy VR., Kinda of miss that.
Click to expand...
Click to collapse
Daydream works from what I can tell. Also I'm on att so I haven't checked T-Mobile bands but im assuming they work fine. I know there's an app to check which bands your device supports. I'll try downloading it and let you know
So I get to the point to sideload the nougat update and it always says "can't read..." I've done factory resets and everything else I could think of, still no go for me.
Prfndhatrdofman said:
...
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
So... are you of the opinion that recovering a Nougat boot+system TWRP backup on a MM phone would cause a soft brick too?
What type of soft brick do you faced exactly?
Prfndhatrdofman said:
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
I did up until this
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
But when I boot up i have no wifi and I am unable to get the no command to go away to select sideload any ideas?
pieman13 said:
So I get to the point to sideload the nougat update and it always says "can't read..." I've done factory resets and everything else I could think of, still no go for me.
Click to expand...
Click to collapse
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
pixelens said:
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
Click to expand...
Click to collapse
This happened to me as well. I think it came down to being an ADB Driver issue for me. I reinstalled a different set of ADB drivers and it had no issue after that.
enetec said:
So... are you of the opinion that recovering a Nougat boot+system TWRP backup on a MM phone would cause a soft brick too?
What type of soft brick do you faced exactly?
Click to expand...
Click to collapse
Didn't work for me. As soon as the system partition was mounted R/W My device would boot loop. Could be a symptom of something else but im not sure.
Prfndhatrdofman said:
This happened to me as well. I think it came down to being an ADB Driver issue for me. I reinstalled a different set of ADB drivers and it had no issue after that.
Click to expand...
Click to collapse
Interesting... I'm using the adb drivers from Android Studio.
---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------
Tried using the ADB drivers from Minimal ADB and Fastboot, same result. Oh well.
pixelens said:
Interesting... I'm using the adb drivers from Android Studio.
---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------
Tried using the ADB drivers from Minimal ADB and Fastboot, same result. Oh well.
Click to expand...
Click to collapse
Yeah i struggled for about 3 hours trying to get sideload to work. I dunno why but after i completely deleted the driver, rebooted, reinstalled from ADB it finally worked. Its definitely not your device or the image its just ADB being a pain in the ass. I even tried multiple versions of ADB. One guy just tried on a different computer and it worked. I dunno why
Prfndhatrdofman said:
Yeah i struggled for about 3 hours trying to get sideload to work. I dunno why but after i completely deleted the driver, rebooted, reinstalled from ADB it finally worked. Its definitely not your device or the image its just ADB being a pain in the ass. I even tried multiple versions of ADB. One guy just tried on a different computer and it worked. I dunno why
Click to expand...
Click to collapse
Yah, I've had similar experiences in the past - been ages since I've done this though (Samsung Galaxy SII Skyrocket days) so just wanted to make sure I wasn't missing something.
Quick question though, title says "unlocked retail devices" - does that mean the bootloader has to be unlocked? Or will this work with a locked bootloader? Cheers.
pixelens said:
Yah, I've had similar experiences in the past - been ages since I've done this though (Samsung Galaxy SII Skyrocket days) so just wanted to make sure I wasn't missing something.
Quick question though, title says "unlocked retail devices" - does that mean the bootloader has to be unlocked? Or will this work with a locked bootloader? Cheers.
Click to expand...
Click to collapse
I specifically meant network unlocked. Really just any device purchased directly from Motorola.
But yeah i think you might need to have an unlocked bootloader as well.
pixelens said:
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
Click to expand...
Click to collapse
Fix was I went back to my pixel and sold the Z.
Mine has unlocked bootloader. Unlocked thru Motorola's website since the first hour I got it
Got the Nougat update to sideload (yay!) - tried a different computer that had no adb drivers installed, used the ones from Minimal ADB and Fastboot and they worked no problem.
Is it possible to lock the bootloader after the Nougat update? I tried and received "(bootloader) still require signed boot.img" message.
pixelens said:
Got the Nougat update to sideload (yay!) - tried a different computer that had no adb drivers installed, used the ones from Minimal ADB and Fastboot and they worked no problem.
Is it possible to lock the bootloader after the Nougat update? I tried and received "(bootloader) still require signed boot.img" message.
Click to expand...
Click to collapse
Dunno. I get the same error.
Thank you for this guide!
Prfndhatrdofman said:
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
Hello
I flashed the rogers 45 firmware, but when I go to recovery mode I can't get the ADB menu to appear. I've held power and down, power and up, nothing, etc. Am I missing something? I did the rogers install, then went to homescreen, then powered off.
EDIT
after restarting my phone like 10 times in 5 minutes (rest in peace...) I finally figured it out. Now my issue is that I can't seem to get the sideload to work. I am going to try uninstalling android studio and start again. Did you guys figure out why it says * cannot read ' blur.....' * ?
I found how to fix the adb problem about being unable to read from another thread on XDA
1. Download Large Address Awareness from here https://www.techpowerup.com/forums/threads/large-address-aware.112556/
2. Download ADB from here http://forum.xda-developers.com/showthread.php?t=2588979
3. Start Task Manager and kill adb.exe if its running
4. Load the adb.exe file from Large Address Awareess and check the flag button
5. Continue on with adb sideload
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
Porcelainfog said:
Hello
I flashed the rogers 45 firmware, but when I go to recovery mode I can't get the ADB menu to appear. I've held power and down, power and up, nothing, etc. Am I missing something? I did the rogers install, then went to homescreen, then powered off.
Click to expand...
Click to collapse
Do you see the "No command" picture after choosing Recover Mode? Once you get to that, I hold down power and tap volume up and down again and again
Hi everyone
More than a question, I wanted to share some steps I plan to follow to apply the monthly system update and check I am on the right track. I had a Google Pixel 2 for a few months and I am learning more about the model every day.
Previously, I tried to follow different procedures found here on XDA such as applying OTA with boot images temporarily restored but I ended up with a bootloop not event TWRP could fix since all data was encrypted.
Objective:
Update the system to the latest Pixel 2 update (in this case Feb 2018) avoiding bootloops or bricks
Current Status:
Pixel 2 Walleye with Jan 2018 update
Rooted systemlessly with Magisk
No Magisk modules installed
/system modified since I have AdAway and other apps
No BusyBox installed
No Custom Recovery installed
Proposed steps:
Uninstall Magisk completely
Remove root apps from Device Admin (such as Greenify, Tasker, etc.)
Download latest factory image from Google
Extract the following from the image zip:
bootloader.img
radio.img
boot.img
dbto.img
cache.img
system.img
recovery.img
Restart phone into booloader
Fastboot bootloader.img
Reboot the bootloader
Fastboot the following commands in this order:
radio.img
boot.img
dbto.img
cache.img
system.img
recovery.img
Reboot phone
Install Magisk by patching boot
Re-run root apps (AdAway, etc.)
Renable root apps as Device Admin (Tasker, Greenify, etc.)
Is the above safe enough to avoid bootloop and also not lose apps and data installed?
I am aware any modifications to /system will be lost.
Have a look, let me know if on track, and if you want, give me your blessing.
Yesterday I used Dueces bootloop recovery script to update without losing anything.
I had magisk + TWRP installed
Download full update not OTA, extract to program tools directory or where you keep your goodies. Pull all factory update in folder with deuces recovery script.
From stk rooted ROM reboot bootloader,
Run dueces script from bootloader
After finished script No to format data
Reboot system when done.
From there you should be good to go, you will need to repatch but image in magisk and all that but i lost no data and had no issues
So I was on 1.171019.019 installed 1.172019.21 from fastboot with script and wiped nothing and lost nothing..
** My directions are probably incomplete so follow his instructions in his OP.
This has been discussed all over the place on the forums but you're over complicating the update process. Here's what you do:
Code:
Download the latest Pixel update
extract the update in your ADB folder on a computer
reboot to bootloader
look for the flash-all.bat and remove the -w at the bottom of that code, Save that file (the -w is what causes the device to be wiped)
run flash-all.bat
once that finishes you can fastboot boot twrp.img
it won't decrypt (Feb update broke TWRP decryption) but go read only and get into ADB Sideload mode
adb sideload kernel.zip
adb sideload magisk.zip
reboot
This is what I've done everytime (minus the adb sideload) and I have had zero issues. No loss of data being the biggest concern. Did this using the march update just yesterday and now I'm good to go.
It is worth saying when you start trying to flash (roms, kernels ect..) and you get a little crazy, Dueces Bootloop Recovery script is 100% something to have on deck if something /does/ go wrong.
nolimit78 said:
adb sideload kernel.zip
Click to expand...
Click to collapse
kernel.zip from where? The OTA? One you saved with TWRP on it?
I currently have TWRP and Magisk (default - nothing changed yet) installed on the February update. Is this going to be a monthly thing - flash the update, reinstall TWRP, reinstall Magisk? Not a complaint, just want to know what I'm doing. (Samsung, for all its faults, was a little easier after 6 years of not even having to look at what I was doing. I'll get comfortable with the Pixel, but this is my first update with TWRP and Magisk installed - it did the February update almost before I could read the screen.)
Rukbat said:
kernel.zip from where? The OTA? One you saved with TWRP on it?
I currently have TWRP and Magisk (default - nothing changed yet) installed on the February update. Is this going to be a monthly thing - flash the update, reinstall TWRP, reinstall Magisk? Not a complaint, just want to know what I'm doing. (Samsung, for all its faults, was a little easier after 6 years of not even having to look at what I was doing. I'll get comfortable with the Pixel, but this is my first update with TWRP and Magisk installed - it did the February update almost before I could read the screen.)
Click to expand...
Click to collapse
The kernel.zip is whatever kernel you'd like to use (flash or elemental) but it's not required. I just rename for shorter commands for ADB Yes, you've hit the nail on the head. If you're going to be stock/rooted, you'll have to do this every month to stay current.
And we're still waiting for Dees_Troy to figure out how to add decryption back to TWRP, so it's reinstall everything - including fingerprints - every month. Oh, well. (Hey, no pressure, Dees_Troy - I appreciate just having TWRP on this thing.)
Rukbat said:
And we're still waiting for Dees_Troy to figure out how to add decryption back to TWRP, so it's reinstall everything - including fingerprints - every month. Oh, well. (Hey, no pressure, Dees_Troy - I appreciate just having TWRP on this thing.)
Click to expand...
Click to collapse
In my process outline, you don't have to remove fingerprints.
To boot to TWRP to handle files that you already copied to the phone? TWRP doesn't decrypt the names any more, does it? So all you see is garbage (encrypted hash, I guess). If I want to restore a backup I have to remove the PIN, which seems to remove the fingerprints. Or are you saying to restore the PIN and the fingerprints are still active?
Rukbat said:
To boot to TWRP to handle files that you already copied to the phone?
Click to expand...
Click to collapse
No, this is only to apply the update and flash a custom kernel and magisk
Rukbat said:
TWRP doesn't decrypt the names any more, does it?
Click to expand...
Click to collapse
No, it sure doesn't. This was caused by the Feb Update
Rukbat said:
If I want to restore a backup I have to remove the PIN, which seems to remove the fingerprints.
Click to expand...
Click to collapse
Yeah, to do anything in TWRP (outside of ADB Sideloading) you'll need to remove the PIN.
And evidently something else. I removed the PIN, updated, and the phone's been sitting on the G screen for half an hour. So I rebooted to the bootloader, locked it, and now I'm flashing 021. I have a bad feeling that I'm going to be stuck.
---------- Post added at 05:09 PM ---------- Previous post was at 04:10 PM ----------
As I feared. So I followed Google's instructions to flash the factory image. It went fine, until I got:
Created filesystem with 11/7389184 inodes and 511894/29553659 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
Click to expand...
Click to collapse
Then it wrote the system, but
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
Click to expand...
Click to collapse
It never reboots. If I reboot at that point, I get the recovery screen.
If I reboot into the bootloader and lock it, I get the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.
I was able to load twrp.img and use it to sideload twrp.zip, but that still doesn't get me back to Android. I tried b ooting into A and B and got the same result - TWRP.
What next? Is there a fix, or does this one have to be replaced also?
Rukbat said:
And evidently something else. I removed the PIN, updated, and the phone's been sitting on the G screen for half an hour. So I rebooted to the bootloader, locked it, and now I'm flashing 021. I have a bad feeling that I'm going to be stuck.
---------- Post added at 05:09 PM ---------- Previous post was at 04:10 PM ----------
As I feared. So I followed Google's instructions to flash the factory image. It went fine, until I got:
Then it wrote the system, but
It never reboots. If I reboot at that point, I get the recovery screen.
If I reboot into the bootloader and lock it, I get the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.
I was able to load twrp.img and use it to sideload twrp.zip, but that still doesn't get me back to Android. I tried b ooting into A and B and got the same result - TWRP.
What next? Is there a fix, or does this one have to be replaced also?
Click to expand...
Click to collapse
Oh my gosh. Stop sending your phone back.
Update your platform-tools. Change cables. Change ports. Use the search function.
Sent from my Pixel 2 using Tapatalk
I'm not exactly new at this. Different cable, every USB port (including a 2.0 port, new download of both Google's driver and adb/fastboot, a new download of the firmware (and the sha256 is correct).
The next thing I'm going to try, as soon as I finish eating, is another computer. If that fails, and I'm pretty sure it will, I'll call Google tech support. Since it happened twice during an OTA, on two different phones, I may be able to get someone who knows how to feed the firmware into a nearly dead phone. I'm just looking for ideas I haven't had, when I post here. I'm about out of ideas. Again.
Evidently some computer manufacturers don't exactly build what they claim to build. My desktop has 2 USB 3.0 ports (which I already knew wouldn't work) and - supposedly - a USB 2.0 port. Flashing the firmware on the "2.0" port didn't work. Evidently it's not 2.0.
So I resurrected an old Windows 8.0 laptop. I think it has 0 cores running at 0MHz - it's SLOW! But it finally flashed the February update. Tomorrow (it's going on midnight here, and the phone is still downloading the last Google backup) I'll update to March.
Madness - but at least I have a working phone, and know how to get it working again if I need to (and have a few lifetimes to do it). And I have another laptop in the closet that actually works. That one gets resurrected next.
So what you're experiencing isn't new or an issue with your phone that you'd need to RMA the device. It's a learning curve because the A/B partitions are a completely different beast compared to older/other Android devices. Use Duece's Bootloop Recovery script to fix your problems. It'll work and you'll be good to go. Just be sure not to wipe. During my testing, I had to figure out all this myself and was /REALLY/ close to RMA'ing my device. But I continued to research and plugging away and found that that script helps users in your situation, as I've been in that very same situation myself.
No, it's a learning curve because, even though the USB ports on the back of the case are labeled 2.0, and have black plastic, they act like 3.0 ports with a Pixel 2. Doing exactly what both I and Google tech support did with the supposed 2.0 ports, on the aging laptop with real 2.0 ports, solved the "problem" that both Google and I were having. The phone was fine, what we were doing was right, the Acer desktop has a documentation error, and that was the only problem. (Even Google didn't seem to be aware of the USB 3.0/Pixel2 incompatibility, which many of the people in the Pixel 2 forums at XDA are.)
Follow the guide in my signature, it works, and you don't have to muck around with removing PINs and fingerprints.
Thanks for paying attention, but what really bothers me is having to remove the fingerprints in order to do a backup or restore in TWRP. I'm used to just booting to it and flashing a backup if I need it for some reason. If only Google would leave the fingerprint file alone when we went to None for the lock screen, just putting the PIN back would bring the fingerprints back. There's really no reason to delete that file. Maybe delete individual prints at the user's discretion (like changing passwords every once in a while), but not delete the whole thing just because I want to back up my current configuration.
What I do is uninstall Magisk. Then do the normal update from the update page in settings. After this I copy Magisk zip file to a usb drive. I boot into twrp using ADB. It doesn't decrypt but that doesn't matter. Use the USB as storage and install Magisk zip file through TWRP. Reboot and you are done updating with Magisk installed.
That sounds like an easy way of doing it, but doesn't the update balk at the patched boot file? Mine balked at something yesterday, which is what started all the mess yesterday. (Or does Magisk have a "remove and replace the boot file" button?)
nolimit78 said:
This has been discussed all over the place on the forums but you're over complicating the update process. Here's what you do:
Code:
Download the latest Pixel update
extract the update in your ADB folder on a computer
reboot to bootloader
look for the flash-all.bat and remove the -w at the bottom of that code, Save that file (the -w is what causes the device to be wiped)
run flash-all.bat
once that finishes you can fastboot boot twrp.img
it won't decrypt (Feb update broke TWRP decryption) but go read only and get into ADB Sideload mode
adb sideload kernel.zip
adb sideload magisk.zip
reboot
This is what I've done everytime (minus the adb sideload) and I have had zero issues. No loss of data being the biggest concern. Did this using the march update just yesterday and now I'm good to go.
It is worth saying when you start trying to flash (roms, kernels ect..) and you get a little crazy, Dueces Bootloop Recovery script is 100% something to have on deck if something /does/ go wrong.
Click to expand...
Click to collapse
Thank you for the feedback!
One question I had for a while: flashing the data.img wipes what? Doesn't it wipe the apps you have installed?
As there seems to be no such guide yet and it took me quite a while to get all this information together, I thought of giving back something by putting information together for others to start.
This guide is meant for the CLT-L29 (dual SIM). Rebranding and switching your CLT-L09 (single SIM) to dual is not subject of this guide and is not adviced.
This is for a Huawei P20 Pro CLT-L29 with factory reset. Please bear with me if there really is a step missing as I try to reproduce this for the documentation with an already bootloader unlocked and previously rooted phone (root should be gone after [factory] resetting via eRecovery).
A collection of all tools used can be found here.
As always, you are doing this on your own risk, no one else can be held responsible for this.
Cheat sheet
eRecovery
The recovery sitting in the "recovery" partition. eRecovery is Huawei's recovery that is able to fix your phone by downloading the latest OTA update via WiFi if you got stuck in a boot loop for several reasons.
To boot into eRecovery:
Power down your phone (if you are stuck in a boot loop simply continue with the next step).
Hold volume up until you end up in eRecovery.
Setup your WiFi access and let it recover your phone.
If unsure, "wipe data/factory reset" to get rid of any leftovers you messed up.
Reboot and be happy that you have not fully bricked your phone.
TWRP
The recovery typically flashed to the "recovery_ramdisk" partition. TeamWin Recovery Project is what you typically use to flash ROMs, to root the phone and to install OTA updates.
Do NOT flash TWRP into "recovery" partition or you will lose eRecovery and the ability to easily recover your semi-bricked phone via WiFi!
To boot into TWRP (once flashed):
Power down your phone (if you are stuck in a boot loop simply continue with the next step).
Hold volume up and power until you end up in TWRP.
Unlock your bootloader
Get your bootloader unlock code from here https://emui.huawei.com/en/unlock_detail (available until mid of July I think). Some report to have to wait 24/48h to get their code via mail, I got mine directly.
Register via mail and do not get confused that you can not select USA or Germany or whatever country, simply use location Hong Kong.
Make sure you select "EMUI above 5.0" when entering your phone data (P20 Pro comes with EMUI 8.x).
Connect your phone via ADB. There are tons of HowTos about this, so I will not be covering this here.
Use Tool All In One to check that you can talk to your device via ADB. It will also help you installing the correct ADB USB drivers.
Unlock your bootloader using Tool All In One.
Reboot back into system.
Flash TWRP
Make sure no lock screen or other locking is set:
"Settings > Security": Remove fingerprint, face or password locking, simply set to none.
Enter developer mode, should already been done for unlocking the bootloader.
Setting > System > Developer options: Disable the display lock.
Download latest ADB & Fastboot as I will continue with the rest on command line.
Verify connection to your phone with "adb devices", this should list your phone.
Reboot into fastboot by using "adb reboot bootloader".
Verify connection to your phone with "fastboot devices", this should list your phone.
Flash TWRP by Pretoriano80 with "fastboot flash recovery_ramdisk twrp_clt_0.1.img". This TWRP is able to access the encrypted internal storage! TWRP is flashed to "recovery_ramdisk". This ensures that you can still access eRecovery if something goes wrong.
Remove the USB cable.
Reboot into TWRP. If you do not boot directly into TWRP the Huawei eRecovery might replace TWRP again. Once you booted into TWRP you are fine for future reboots.
Use "Keep Read Only" for the system partition.
Make a backup!!!
Backup your phone to internal storage (USB stick via USB-OTG adapter failed for me):
Select "Backup".
Tick all partitions (scroll down and tick all).
Swipe to Backup.
Select "Reboot System", "Do Not Install".
Back in Android make a copy of your backup located in your internal storage "/TWRP/" to an external location like your PC. Keep the backup on your phone to be able to go back quickly to this point via TWRP.
Root the stock ROM
Place "Magisk-v16.4-Beta.zip" onto the internal storage.
Power off the phone and remove the USB cable.
Boot into TWRP.
Install root and Magisk Manager:
Select "Install".
Select "Magisk-v16.4-Beta.zip"
Tick "Reboot after installation is complete".
Swipe to confirm Flash.
Select "Do Not Install".
Back in Android start "Magisk Manager" and check that it is green and therefore rooted.
Install an OTA (Over The Air) stock update
PC method
Method involving ADB based on this guide.
First make sure no OTA update gets installed automatically as this will end up in booting into TWRP and failing with the update.
Go to "Settings > System > System Update".
Open the three dots menu on the top right and select "Update Settings".
Disable automatic update download via WiFi as once updates are downloaded the phone will bug you to update and maybe tries to update itself during the night!
Start in Android but do not download the OTA update yet.
Verify connection to your phone with "adb devices", this should list your phone.
Reboot into fastboot by using "adb reboot bootloader".
Verify connection to your phone with "fastboot devices", this should list your phone.
Flash "recovery_ramdisk_nocheckP20.img" with "fastboot flash recovery_ramdisk recovery_ramdisk_nocheckP20.img". For official OTA updates that you would regularly get, the "nocheck" feature should not be needed but does not harm. This will remove TWRP and you have to flash it again after the OTA update has finished.
Reboot into Android by using "fastboot reboot".
Remove the USB cable.
Download your OTA update via "Settings > System > System Update".
Let the phone reboot to install the OTA update and follow the update until you are back in Android with your new firmware version.
Install TWRP and root again.
Standalone method
Deprecated/wrong method based on this guide.
Read first!!!
While this method should do no harm it will only ever update to CLT-L29 8.1.0.128a(C432) [hw/eu] as this is what is inside the file "update.zip" that you can currently download and that gets installed by "HuRUpdater_0.3.zip" in the same folder. This was not clearly explained in the source thread, therefore sorry about this wrong information. If you intend to update to this stock ROM continue, otherwise use the "PC method".
I will check about the best way to install OTA updates without PC interaction in the next couple of days (currently waiting for 130+ getting rolled out for me for some investigations regarding the OTA process).
First make sure no OTA update gets installed automatically as this will end up in booting into TWRP and failing with the update.
Go to "Settings > System > System Update".
Open the three dots menu on the top right and select "Update Settings".
Disable automatic update download via WiFi as once updates are downloaded the phone will bug you to update and maybe tries to update itself during the night!
Place the following files into a folder on the internal storage (for sure not all are required but this is part of the little information not clear right now):
"HuRUpdater_0.3.zip"
"recovery.img"
"update.zip"
"update_all_hw.zip"
"update_data_public.zip"
Go to "Settings > System > System Update" and check for an update.
Download the OTA update.
Do not reboot when prompted.
Make sure no lock screen or other locking is set:
"Settings > Security": Remove fingerprint, face or password locking, simply set to none.
Enter developer mode, should already been done for unlocking the bootloader.
Setting > System > Developer options: Disable the display lock.
Power down the phone.
Boot into TWRP.
Install "HuRUpdater_0.3.zip". Do not get irritated if it tells you it is for CLT-L09 instead of CLT-L29, everything is fine.
Wipe dalvik cache before rebooting.
Reboot back into Android.
Check "Magisk Manager" to see if root got removed. TWRP might get removed as well. If TWRP or root got removed, repeat the install for one or both like before.
In my case only root got removed but TWRP was kept functional. If this is the case for you as well, simply flash "Magisk-v16.4-Beta.zip" via TWRP again.
Changelog
2018-06-21
Updated/corrected wrong information collected about installing OTA updates standalone (without PC). Until further notice use the PC method.
Great post. Thank you
Very good post!
Thank you to collect all this important info!
[emoji481]
P20 Pro & Tapatalk
can i use your step above to rebranding from L29c636 to l29c432? Thanks
Barcovn said:
can i use your step above to rebranding from L29c636 to l29c432? Thanks
Click to expand...
Click to collapse
Not sure, not tested and not topic of this thread.
For my understanding, why do you want to rebrand it to C432 which is the region code as far as I understand.
Is there a BIG benefit of getting OTA updates earlier or why do you want to mess around with it ?
Xcelsior said:
Not sure, not tested and not topic of this thread.
For my understanding, why do you want to rebrand it to C432 which is the region code as far as I understand.
Is there a BIG benefit of getting OTA updates earlier or why do you want to mess around with it ?
Click to expand...
Click to collapse
yes, i mean change the region code. as i use the p20 pro since April, newer firmware ususal fix/improve performance for phone or camera. however it seem the c636 update is much slower then C432. currently i have problem with facebook lagging which inhope newer firmware fix it
This is good! I'll sticky it when I get a chance later tonight. I'm mobile atm
Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there
dladz said:
Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there
Click to expand...
Click to collapse
They're a bit different. The debrand thread is obviously good but much more specific to debranding. This is a more generic for general How-To's
dladz said:
Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there
Click to expand...
Click to collapse
I was reading this one as well but like matt4321 already said, it is actually for a different purpose.
And even the "ROOT ONLY" instructions are either widespread over the whole P20 Pro forum, incomplete or even outdated:
Linking to other threads with endless, partly revised instructions (on page n of the thread).
Referring to wrong official TWRP that can not use internal storage.
Hard to understand for beginners on this device (not even talking about someone who is entirely new to all of this).
Missing steps or expecting that you have already successfully flashed your first ROM (talking about advanced things like rebranding).
Don't get me wong, I am used to read a lot when it comes to custom ROMs (if you check the old part of my signature you can see that I am not actually a newbie here and my roots actually reach back to when all of the Android stuff startet at all, back when XDAs flashed HTC HD2 WinMo to Android). However I really missed a guide that actually collects all the basic information for beginners without going off roads too early.
These are more or less the steps I'm used to when I owned my nexus phones.
I have some questions:
If I root my phone and install, let's say adaway, will I be able to receive OTA? Or I will have to flash a new image manually?
If after root I relock bootloader, will I be able to unlock it again later for further modding?
This method implies that I can return to stock anytime and relock bootloader?
Thanks for the guide and answers , great job
mangusZen said:
If I root my phone and install, let's say adaway, will I be able to receive OTA? Or I will have to flash a new image manually?
Click to expand...
Click to collapse
Yes, exactly what I am doing. I need root for some apps and besides that I am happy with the stock OTA ROM, at least for the moment. OTA updates work fine so far.
The only thing as explained in my guide is that OTA updates will fail as they boot into TWRP instead of original fastboot. Therefore you need to explicitly boot into TWRP and install the downloaded OTA update with "HuRUpdater_0.3.zip".
mangusZen said:
If after root I relock bootloader, will I be able to unlock it again later for further modding?
Click to expand...
Click to collapse
From what I have read so far re-locking your bootloader is not advised. You seem to be unable to unlock it again or at least need to request another unlock code from Huawei.
At least this is my understanding of the situation so far.
mangusZen said:
This method implies that I can return to stock anytime and relock bootloader?
Click to expand...
Click to collapse
Returning to stock is even easier if you keep eRecovery working as explained in the guide (flashing TWRP only to recovery_ramdisk partition). With eRecovery you can wipe TWRP and root and let eRecovery download and install the latest official stock ROM.
Regarding the bootloader re-locking, see my answer above.
Xcelsior said:
Yes, exactly what I am doing. I need root for some apps and besides that I am happy with the stock OTA ROM, at least for the moment. OTA updates work fine so far.
The only thing as explained in my guide is that OTA updates will fail as they boot into TWRP instead of original fastboot. Therefore you need to explicitly boot into TWRP and install the downloaded OTA update with "HuRUpdater_0.3.zip".
From what I have read so far re-locking your bootloader is not advised. You seem to be unable to unlock it again or at least need to request another unlock code from Huawei.
At least this is my understanding of the situation so far.
Returning to stock is even easier if you keep eRecovery working as explained in the guide (flashing TWRP only to recovery_ramdisk partition). With eRecovery you can wipe TWRP and root and let eRecovery download and install the latest official stock ROM.
Regarding the bootloader re-locking, see my answer above.
Click to expand...
Click to collapse
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
For what I read and understood, but I may be wrong, the problem with relocking bootloader is encountered by who used the funkyhuawei method, that alters bootloader in some way, especially to achive the mono sim - dual sim switch.
With this you cant for now re unlock the bootloader again.
But I could be wrong and be like that for everyone, will see if someone will come up with some clarifications.
It would be nice to have the ability to return to stock, lock bootloader and use warranty
[emoji14]
Thanks for your work and answers
mangusZen said:
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
Click to expand...
Click to collapse
Yes, that is basically what "HuRUpdater_0.3.zip" will do, it will flash/install an OTA update that has previously been downloaded.
Wipe cache afterwards and be happy with your new up to date stock ROM version.
Xcelsior said:
Yes, that is basically what "HuRUpdater_0.3.zip" will do, it will flash/install an OTA update that has previously been downloaded.
Wipe cache afterwards and be happy with your new up to date stock ROM version.
Click to expand...
Click to collapse
I have to rename the downloaded OTA packages for huru to work, right?
mangusZen said:
I have to rename the downloaded OTA packages for huru to work, right?
Click to expand...
Click to collapse
Not for me. Just downloaded the OTA update via the EMUI system menu in Android, rebooted into TWRP and installed (aka executed) HuRu.
HuRu did the rest for me.
Tested with 120 -> 128 OTA update.
Hi It is late at night and I am not sure if I typed fastboot flash recovery twrp_clt_0.1.img instead off fastboot flash recovery_ramdisk twrp_clt_0.1.img. How can I make sure I still have erecovery? super newbie to android rooting, please help Thank you
Amowiel said:
Hi It is late at night and I am not sure if I typed fastboot flash recovery twrp_clt_0.1.img instead off fastboot flash recovery_ramdisk twrp_clt_0.1.img. How can I make sure I still have erecovery? super newbie to android rooting, please help Thank you
Click to expand...
Click to collapse
Simplest way would be to try to boot into eRocovery:
Power off the phone.
Power on the phone until you see the "you are a baddy because you unlocked your bootloader" screen.
Hold volume up (you can already hold it when powering on the phone) until you end up in eRecovery or TWRP.
If you end up in TWRP it should still be possible to recover your eRecovery with a proper backup of the "recovery" partition from any other P20 Pro.
Xcelsior said:
Simplest way would be to try to boot into eRocovery:
Power off the phone.
Power on the phone until you see the "you are a baddy because you unlocked your bootloader" screen.
Hold volume up (you can already hold it when powering on the phone) until you end up in eRecovery or TWRP.
If you end up in TWRP it should still be possible to recover your eRecovery with a proper backup of the "recovery" partition from any other P20 Pro.
Click to expand...
Click to collapse
thank you so much for such a quick reply, can confirm that my brain was not so fried and I didn't wipe my ercovery
thank you for your amazing guide, everything worked perfectly
mangusZen said:
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
For what I read and understood, but I may be wrong, the problem with relocking bootloader is encountered by who used the funkyhuawei method, that alters bootloader in some way, especially to achive the mono sim - dual sim switch.
With this you cant for now re unlock the bootloader again.
But I could be wrong and be like that for everyone, will see if someone will come up with some clarifications.
It would be nice to have the ability to return to stock, lock bootloader and use warranty
[emoji14]
Thanks for your work and answers
Click to expand...
Click to collapse
Actually you don't in some cases, if your simply rooted with twrp and you want to install an OTA that's been advertised to your device. All you need to do is install the nocheck recovery IMG and then take the update, reinstall twrp and magisk after the update and you're done.
If it's an update that's not advertised to your device yet then hur updater is the way.