Related
I got the OTA Notification, I click Update, it reboots my phone, and then the phone goes into ClockWorkMod Recovery. Is that supposed to happen? If I select "apply Update" from CWM it tells me it can't find an update.zip file on the sdcard. So I select reboot, and it reboots the phone and it reboots back to old Android, with the OTA Notification still there.
U can't update via ota when ur rooted...
That's what she said...
Suprah said:
U can't update via ota when ur rooted...
That's what she said...
Click to expand...
Click to collapse
So if I unroot via one-click it'll work?
RueTheDay said:
So if I unroot via one-click it'll work?
Click to expand...
Click to collapse
I'm pretty sure you'll also need to flash back to stock recovery.
r4d14n7 said:
I'm pretty sure you'll also need to flash back to stock recovery.
Click to expand...
Click to collapse
Actually, unrooting was not necessary. Just nvflashing back to stock recovery allowed the OTA update to proceed successfully. Not sure I like the way GB looks on this phone though.
My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?
try this posted by @zachariahpope http://crackflasher.com/blur_version-9-18-94-xt926-verizon-en-us-zip-motorola-droid-razr-hd-cdma-livinginkaos/
billycar11 said:
try this posted by @zachariahpope http://crackflasher.com/blur_versio...zip-motorola-droid-razr-hd-cdma-livinginkaos/
Click to expand...
Click to collapse
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk
samabuelsamid said:
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo
billycar11 said:
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo
Click to expand...
Click to collapse
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch
samabuelsamid said:
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch
Click to expand...
Click to collapse
I was reading that it rewrites your recovery. Go back into your recovery (should be a new version) and try to I stall again.
Yeah you need to install 2 times.
Did it install the recovery?
billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.
samabuelsamid said:
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.
Click to expand...
Click to collapse
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
Thanks, I'll provide an update of how this works!
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
This all worked perfectly and I'm now rocking KitKat
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?
samabuelsamid said:
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?
Click to expand...
Click to collapse
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.
iBolski said:
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.
Click to expand...
Click to collapse
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience
samabuelsamid said:
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience
Click to expand...
Click to collapse
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1
iBolski said:
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1
Click to expand...
Click to collapse
good thing I asked first
Update: not rooted on KitKat!
samabuelsamid said:
My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?
Click to expand...
Click to collapse
I have the same problem, but I'm getting the error message that expects your device. What was the image that you used? I have the vanquish:4.1.2/9.8
1Q-94/56:user.
samabuelsamid said:
good thing I asked first
Update: not rooted on KitKat!
Click to expand...
Click to collapse
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.
iBolski said:
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.
Click to expand...
Click to collapse
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser
samabuelsamid said:
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser
Click to expand...
Click to collapse
you know what, color me stupid.
I've been helping so many people that when I read "no root", I interpreted it as "locked bootloader".
My bad.
I just got the 4.4.4 OTA update and appear to have lost root, i'm sure i can re root again when i get home.
However i'm wondering what people recommend in keeping root when taking an OTA update.
Thanks for any advice.
InsaneNutter said:
I just got the 4.4.4 OTA update and appear to have lost root, i'm sure i can re root again when i get home.
However i'm wondering what people recommend in keeping root when taking an OTA update.
Thanks for any advice.
Click to expand...
Click to collapse
SuperSU has a "survival" mode you can check off. It basically tries to keep root after an update. Luckily its easy enough to re-root the One+.
theorioles33 said:
SuperSU has a "survival" mode you can check off. It basically tries to keep root after an update. Luckily its easy enough to re-root the One+.
Click to expand...
Click to collapse
Thanks for the tip, I purchased SuperSU Pro and enabled the feature. As you say though easily enough to re root if you have access to a PC.
InsaneNutter said:
Thanks for the tip, I purchased SuperSU Pro and enabled the feature. As you say though easily enough to re root if you have access to a PC.
Click to expand...
Click to collapse
Its easy to re-root from your phone too, just flash SuperSU in recovery.
InsaneNutter said:
Thanks for the tip, I purchased SuperSU Pro and enabled the feature. As you say though easily enough to re root if you have access to a PC.
Click to expand...
Click to collapse
You're welcome!
zephiK said:
Its easy to re-root from your phone too, just flash SuperSU in recovery.
Click to expand...
Click to collapse
+1 (no pun intended Lol)
InsaneNutter said:
Thanks for the tip, I purchased SuperSU Pro and enabled the feature. As you say though easily enough to re root if you have access to a PC.
Click to expand...
Click to collapse
You don't need a pc at all, you boot back into recovery after the update and flash your SuperSU zip.
Transmitted via Bacon
timmaaa said:
You don't need a pc at all, you boot back into recovery after the update and flash your SuperSU zip.
Transmitted via Bacon
Click to expand...
Click to collapse
Could you please tell where to find the SupetSU zip? Thanks in advance.
Send with my OPO using Tapatalk
HasseY said:
Could you please tell where to find the SupetSU zip? Thanks in advance.
Send with my OPO using Tapatalk
Click to expand...
Click to collapse
I'm guessing you used a toolkit to unlock and root, right? If you haven't done it already, download SuperSU from here:
http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
Then you can flash it using the install menu in TWRP recovery.
Transmitted via Bacon
theorioles33 said:
SuperSU has a "survival" mode you can check off. It basically tries to keep root after an update. Luckily its easy enough to re-root the One+.
Click to expand...
Click to collapse
Do you have tried it successully?
TazZHD said:
Do you have tried it successully?
Click to expand...
Click to collapse
Of course it works. Also guys TWRP will try and reroot your phone a well after a flash if it detects you lost root. Not for nothing but some of you need to do more reading before you street messing with your phones and leave them toolkits alone.
This is not meant to be disrespectful or directed at anyone in general but informative.. Read Read Read
@playya alright mate got my one plus one now. unlocked bootloader installed twrp and flashed super su. disabled update cm recovery on update. then did update from 22r - 25r then did 25r - 30O and obviously 30O - 33r I didn't realise that the update cm recovery would not stick after each update. so ive now tried to reflash twrp but command line says writing recovery ok and finished but checked on phone and its not there? any ideas do I need to unlock bootloader again which I doubt. but not sure if flashing update would also relock?? cheers
---------- Post added at 10:58 AM ---------- Previous post was at 10:43 AM ----------
nathlynn22 said:
@playya alright mate got my one plus one now. unlocked bootloader installed twrp and flashed super su. disabled update cm recovery on update. then did update from 22r - 25r then did 25r - 30O and obviously 30O - 33r I didn't realise that the update cm recovery would not stick after each update. so ive now tried to reflash twrp but command line says writing recovery ok and finished but checked on phone and its not there? any ideas do I need to unlock bootloader again which I doubt. but not sure if flashing update would also relock?? cheers
Click to expand...
Click to collapse
lol ignore me something simple haha
Heisenberg said:
I'm guessing you used a toolkit to unlock and root, right? If you haven't done it already, download SuperSU from here:
http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
Then you can flash it using the install menu in TWRP recovery.
Transmitted via Bacon
Click to expand...
Click to collapse
I've been told that Oreo OTA will replace the recovery and get rid of root. Is this true?
BearOfXDA said:
I've been told that Oreo OTA will replace the recovery and get rid of root. Is this true?
Click to expand...
Click to collapse
Wooot?!!!
BearOfXDA said:
I've been told that Oreo OTA will replace the recovery and get rid of root. Is this true?
Click to expand...
Click to collapse
If you have root and a custom recovery you shouldn't be taking an OTA in the first place.
I am rooted with an unlocked bootloader and TWRP installed.
I tried removing root and still having the same issue.
The OTA downloads but fails shortly into the first step. Is there a better way to side-load this? I would rather not do a full re-install again...
You probably need the stock recovery.
roirraW "edor" ehT said:
You probably need the stock recovery.
Click to expand...
Click to collapse
Can we flash stock recovery over TWRP? If not, can a customer update be rolled to be used with TWRP?
Moogagot said:
Can we flash stock recovery over TWRP? If not, can a customer update be rolled to be used with TWRP?
Click to expand...
Click to collapse
I don't know any reason why you wouldn't be able to put the stock recovery back over TWRP.
Moogagot said:
I am rooted with an unlocked bootloader and TWRP installed.
I tried removing root and still having the same issue.
The OTA downloads but fails shortly into the first step. Is there a better way to side-load this? I would rather not do a full re-install again...
Click to expand...
Click to collapse
You need to flash stock boot back before upgrading.. You can then side load the ota, install twrp and reroot again.. No loss of data
kyle4269 said:
You need to flash stock boot back before upgrading.. You can then side load the ota, install twrp and reroot again.. No loss of data
Click to expand...
Click to collapse
Thanks! Do you happen to know where I can download the stock bootloader?
Moogagot said:
Thanks! Do you happen to know where I can download the stock bootloader?
Click to expand...
Click to collapse
You'll locate it at the Google Developers' site.
Moogagot said:
Thanks! Do you happen to know where I can download the stock bootloader?
Click to expand...
Click to collapse
You're welcome!
https://developers.google.com/android/images
So, I'm on B380 since febuary or march (L09C432), and I think my battery stinks. It was way better before upgrading to Emui5. I haven't had the time to fix it but no I do. Just can't remember the "rules".
I'm no unlocked, Twrped and rooted. In System update I can download B389. But, will this work? Can I install it just like that? Will I loose Twrp and/or root?
I don't have a computer with me atm so I have no way of undoing the upgrade if I start it, thats why I want to be sure.
Thanks a bunch in advance guys!
Sent from my FRD-L09 using Tapatalk
i preffer no, because if you brick at certain points ,PC is must to unbrick,if your phone is hard bricked.so stay back is good.
Rommco05 said:
I'm no unlocked, Twrped and rooted. In System update I can download B389. But, will this work? Can I install it just like that? Will I loose Twrp and/or root?
I'm not sure about this sentence, u not unlocked, no rooted no twrp? If no make update without any issue. If u are rooted and u have root update will be unsuccessful
Anyway B389 is pretty good update
Click to expand...
Click to collapse
Sorry. It's supposed to say "I'm NOW unlocked, twrped and rooted."
Ok so it's a no go then. Guess I'll better wait until I'm back home and have access to a computer.
Thanks guys.
Sent from my FRD-L09 using Tapatalk
were u rooted at b380?
if so, which root?
Since there is already B394 and some reported B398 coming I would wait a bit longer to update your device. And since you have twrp it's either flashable through it or you must first unroot your device, second fastboot stock recovery.img (don't forget recovery2.img) and then finally update via system update or dload. IF you are not familiar with the methods or the process please use search function on this website.
nortish said:
Sorry. It's supposed to say "I'm NOW unlocked, twrped and rooted."
Ok so it's a no go then. Guess I'll better wait until I'm back home and have access to a computer.
Thanks guys.
Click to expand...
Click to collapse
Yeah, take a TWRP backup in case you've done something wrong
PalakMi said:
Yeah, take a TWRP backup in case you've done something wrong
Click to expand...
Click to collapse
But the twrp backup wont work until u got the patched boot image .so first patch the boot by installing magisk and then proceed to take back up
venugopalu007 said:
But the twrp backup wont work until u got the patched boot image .so first patch the boot by installing magisk and then proceed to take back up
Click to expand...
Click to collapse
I got it
PalakMi said:
I got it
Click to expand...
Click to collapse
Good bro:good:
EduBaixo said:
were u rooted at b380?
if so, which root?
Click to expand...
Click to collapse
im not sure to be honest. SuperSU i think but might be magisk as well.
im at home with my computer now. Should i just install stock recovery and install via System update? or download some files and flash via twrp?
nevermind backup, i have all my pictures on nextcloud and everything else is ok to loose.
nortish said:
im not sure to be honest. SuperSU i think but might be magisk as well.
im at home with my computer now. Should i just install stock recovery and install via System update? or download some files and flash via twrp?
nevermind backup, i have all my pictures on nextcloud and everything else is ok to loose.
Click to expand...
Click to collapse
Flash stock recovery and then do dload method.
PalakMi said:
Flash stock recovery and then do dload method.
Click to expand...
Click to collapse
Ok thanks.
Figure I might do a full factory reset and then upgrade. Do I have to unroot first and install stock recovery in this case also?
Sent from my FRD-L09 using Tapatalk
nortish said:
Ok thanks.
Figure I might do a full factory reset and then upgrade. Do I have to unroot first and install stock recovery in this case also?
Click to expand...
Click to collapse
It will be better if you do so.
nortish said:
Ok thanks.
Figure I might do a full factory reset and then upgrade. Do I have to unroot first and install stock recovery in this case also?
Click to expand...
Click to collapse
After update the root willbbe automatically removed.so no need to again unroot
nortish said:
Ok thanks.
Figure I might do a full factory reset and then upgrade. Do I have to unroot first and install stock recovery in this case also?
Click to expand...
Click to collapse
So regarding root. Magisk is currently running systemless. So i hope u wont face any difficulties
Magisk is best but it didn't passed me the safety net
gopinaidu77 said:
So regarding root. Magisk is currently running systemless. So i hope u wont face any difficulties
Click to expand...
Click to collapse
Ok. Do You think I will?
Maybe I should unroot, factory reset, update, install twrp again and root again? Or will the factory reset not install stock recovery?
Sent from my FRD-L09 using Tapatalk
nortish said:
Ok. Do You think I will?
Maybe I should unroot, factory reset, update, install twrp again and root again? Or will the factory reset not install stock recovery?
Click to expand...
Click to collapse
Factory reset will not bring stock recovery back.
gopinaidu77 said:
Factory reset will not bring stock recovery back.
Click to expand...
Click to collapse
But upgrade can
Ok so I ended up downgrading to B131 and from there I upgraded via System Update to B389.
I have installed TWRP, no problems there. But I cant get SuperSU to work.
Running TWRP 3.0.3.0 and tried flashing SuperSU-v2.79-201612051815-EMUI5.0 (which is what i think i used before). No luck. SuperSU app says "no binaries". So then I tried to mount system partition in TWRP and install Supersu again. Made no difference.
I have also tried flashing a newer version och SuperSU, but that didnt help.
So, what am I missing guys?