Database Develop

[Q] Moto X Bootloops trying to get 4.4 OTA

Hey everyone I feel like an idiot.
I used jcase's PwnMyMoto to root my phone post camera update, running stock. I received the 4.4 OTA on Verizon today.
I went to SuperSU and clicked Full Unroot in the settings tab, then restarted my phone a couple times to make sure I still didn't have root.
After that I tried to install the update and noticed my phone won't boot into recovery now.
Is there anything I can do with RSDlite to fix the bootloop problem or am I SOL?
Thanks for all your help guys!

Boot into fastboot mode (power + vol down or through ADB) and do fastboot erase cache?
What you missed in flashing the recovery and system.....You need to get these from the latest SBF file and flash them before you take the OTA.

Fastboot erase cache to stop the bootloop then flash recovery and system then you'll be able to update. This is posted in quite a few places a little reading would have prevented this and been able to fix it

tejaskary said:
Boot into fastboot mode (power + vol down or through ADB) and do fastboot erase cache?
What you missed in flashing the recovery and system.....You need to get these from the latest SBF file and flash them before you take the OTA.
Click to expand...
Click to collapse
Thanks! I used fastboot to erase the casche, now I'm able to use the phone.
Do you know any links/threads where I can find the system image?
Since I'm on Verizon I don't need to re-flash the recovery, correct?

Bionic75 said:
Since I'm on Verizon I don't need to re-flash the recovery, correct?
Click to expand...
Click to collapse
No. Part of the rooting process overwrites the stock recovery. you need to flash stock before you take the OTA.

Thanks for all your help guys!
I used Fastboot to clear cache, then used RSD Lite with an image from sbf.droid-developers.org.
Everything is working great now, running 4.4! :victory:

[Q] Stuck on boot after KK update

This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Two problems: First, I cannot use ADB, as it does not detect his phone. When I plug in his phone, it says drivers failed to install for HTC MTP device. I also have an HTC One, unlocked, S-Off, etc., and when I plug mine in, it's detected and ADB works just fine like always (so it's not that I need to reinstall drivers).
Problem 2: the phone seems to hang trying to do a factory reset from the bootloader menu, or from the stock recovery menu. It will start the reset, reboot to the white HTC screen then hang. I left it for more than an hour twice. Nothing doing.
Is there a way to reflash/restore his phone without wiping his sdcard? He's OK losing the data partition, but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard, as will unlocking his bootloader to try to install a custom recovery. Just not really sure what tools I have at my disposal with a stock recovery and no adb. Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..

Shott3r said:
This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Click to expand...
Click to collapse
Did you tried wiping /cache?
Shott3r said:
Two problems: First, I cannot use ADB, as it does not detect his phone.
Click to expand...
Click to collapse
ADB can only be used when phone is booted+usb debug on or via custom recovery
Shott3r said:
He's OK losing the data partition
Click to expand...
Click to collapse
I hope so, factory reset is a /data wipe... probably already wiped from your first attempt to factory reset
Shott3r said:
but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard
Click to expand...
Click to collapse
And the available ruu.exe for at&t is a downgrade in version so it will require s-off.
Shott3r said:
Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..
Click to expand...
Click to collapse
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
easy way:
flash twrp custom recovery
flash guru reset rom for your version
or
flash twrp custom recovery
flash and use arhd rom
or the long way:
flash twrp
flash arhd
s-off
flash ruu.zip

alray said:
Did you tried wiping /cache?
...
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
...
Click to expand...
Click to collapse
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.

Shott3r said:
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.
Click to expand...
Click to collapse
ruu will wipe everything.
and no you can't use ruu with s-on because its a downgrade in version.

Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.

Shott3r said:
Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.
Click to expand...
Click to collapse
maybe you could use remote recovery booting (booting a custom recovery without installing it). Not sure if it still can be done (think it was disabled in 4.2.2)
fastboot boot name_of_recovery.img
then use adb from recovery to copy sdcard content to your computer
adb pull /sdcard C:\somefolder
If you can't boot from a remote recovery, then I think you can say goodbye to those files in your /sdcard

Need at&t stock and unlocked atrix HD rom

So, a while ago I started to root my atrix HD and like everybody else I started to try new roms and stuff, I always backed up my stock rom, but one day I accidentally deleted a file from a folder that clockworkMod recovery created, and then when I wanted to return to my stock rom, well it didn't let me do it!
I've tried to go back to stock with RSDlite and myth tools but I simply can't do it (maybe the virtual world hates me)
So I was wondering if any of you could send a me a backed up stock at&t unlocked rom that I could flash with clockwork recovery?
Or can I go back to stock with any other method?:crying:

Axelgux said:
So, a while ago I started to root my atrix HD and like everybody else I started to try new roms and stuff, I always backed up my stock rom, but one day I accidentally deleted a file from a folder that clockworkMod recovery created, and then when I wanted to return to my stock rom, well it didn't let me do it!
I've tried to go back to stock with RSDlite and myth tools but I simply can't do it (maybe the virtual world hates me)
So I was wondering if any of you could send a me a backed up stock at&t unlocked rom that I could flash with clockwork recovery?
Or can I go back to stock with any other method?:crying:
Click to expand...
Click to collapse
Did you unlock bootloader?
How did Myth Tools show you when it cannot help you?

Axelgux said:
So, a while ago I started to root my atrix HD and like everybody else I started to try new roms and stuff, I always backed up my stock rom, but one day I accidentally deleted a file from a folder that clockworkMod recovery created, and then when I wanted to return to my stock rom, well it didn't let me do it!
I've tried to go back to stock with RSDlite and myth tools but I simply can't do it (maybe the virtual world hates me)
So I was wondering if any of you could send a me a backed up stock at&t unlocked rom that I could flash with clockwork recovery?
Or can I go back to stock with any other method?:crying:
Click to expand...
Click to collapse
Uninstall anything Motorola driver related and once that's done let Myth install the drivers for you. With Windows & Myth, drivers are usually the problem when stocks won't flash. Running RSD as admin as well as disabling UAC can help.
What error does CWM give you? Depending on what it gives and what you deleted, this might be a simple fix.

devilsking said:
Did you unlock bootloader?
How did Myth Tools show you when it cannot help you?
Click to expand...
Click to collapse
Yes I unlocked bootloader right away with root, It just doesn't progress or anything

skeevydude said:
Uninstall anything Motorola driver related and once that's done let Myth install the drivers for you. With Windows & Myth, drivers are usually the problem when stocks won't flash. Running RSD as admin as well as disabling UAC can help.
What error does CWM give you? Depending on what it gives and what you deleted, this might be a simple fix.
Click to expand...
Click to collapse
I'll try that, thanks.
CWM just say can't flash *name of m backup*
If i remember well I deleted something like this /clockworkmod/.recovery_version
or something related to the backup

skeevydude said:
Uninstall anything Motorola driver related and once that's done let Myth install the drivers for you. With Windows & Myth, drivers are usually the problem when stocks won't flash. Running RSD as admin as well as disabling UAC can help.
What error does CWM give you? Depending on what it gives and what you deleted, this might be a simple fix.
Click to expand...
Click to collapse
UPDATE
I managed to flash stock jellybean with the updated myth tool but now I'm stuck in motorola logo
why is that?

Axelgux said:
UPDATE
I managed to flash stock jellybean with the updated myth tool but now I'm stuck in motorola logo
why is that?
Click to expand...
Click to collapse
You probably need to factory reset. If you let Myth install Philz CWM, just boot into there and do that. If not, install Philz then continue on. If your bootloader is locked and you can't install Philz, all you can do is a factory reset from stock recovery. If you're unlocked, do what's in the next paragraph else go to the end.
If you were on a custom rom before this (any rom that's Android 4.2 and above) you need to format the internal sd, change the mount point to /data/media, reboot back into recovery, format the internal sd again. Doing a full format of /data after doing all of that probably won't hurt.
There's also the following commands you can also run in fastboot mode. Myth doesn't do the erase tombstones command, but it does the rest.
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
Myth also doesn't do the fastboot erase modemst1 or modemst2, but that only matters when changing stock Android versions or going from ICS to JB to a custom rom...

skeevydude said:
You probably need to factory reset. If you let Myth install Philz CWM, just boot into there and do that. If not, install Philz then continue on. If your bootloader is locked and you can't install Philz, all you can do is a factory reset from stock recovery. If you're unlocked, do what's in the next paragraph else go to the end.
If you were on a custom rom before this (any rom that's Android 4.2 and above) you need to format the internal sd, change the mount point to /data/media, reboot back into recovery, format the internal sd again. Doing a full format of /data after doing all of that probably won't hurt.
There's also the following commands you can also run in fastboot mode. Myth doesn't do the erase tombstones command, but it does the rest.
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
Myth also doesn't do the fastboot erase modemst1 or modemst2, but that only matters when changing stock Android versions or going from ICS to JB to a custom rom...
Click to expand...
Click to collapse
Mygoooooood I really appreciate your help, I did all that and still the same, yes i was in carbon rom kitkat 4.4, and I did all that but still the same :/

skeevydude said:
You probably need to factory reset. If you let Myth install Philz CWM, just boot into there and do that. If not, install Philz then continue on. If your bootloader is locked and you can't install Philz, all you can do is a factory reset from stock recovery. If you're unlocked, do what's in the next paragraph else go to the end.
If you were on a custom rom before this (any rom that's Android 4.2 and above) you need to format the internal sd, change the mount point to /data/media, reboot back into recovery, format the internal sd again. Doing a full format of /data after doing all of that probably won't hurt.
There's also the following commands you can also run in fastboot mode. Myth doesn't do the erase tombstones command, but it does the rest.
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
Myth also doesn't do the fastboot erase modemst1 or modemst2, but that only matters when changing stock Android versions or going from ICS to JB to a custom rom...
Click to expand...
Click to collapse
sorry to bother again but I think I totally hard bricked my AHD, now in the recovery it says can't mount E:/ and I can't flash any rom :/ thanks for all your help I really appreciate it

Axelgux said:
sorry to bother again but I think I totally hard bricked my AHD, now in the recovery it says can't mount E:/ and I can't flash any rom :/ thanks for all your help I really appreciate it
Click to expand...
Click to collapse
Flash a stock fastboot, RSD, manually, Myth, whatever works (manually should always work unless you really are bricked), flash the lastest msm8960 Philz cwm (look in the razr hd dev forums), after all that, possibly take a look at post 7...I'm gusssing your a Windows user...but for me, Linux has had better results than Windows flashing stock Motorola phones.

what happens if you upgrade a rooted htc one t lollipop

so say i upgrade my rooted htc one once the ota update becomes ready.. what happens? i dont want to end up with a bricked phone.. would it harm my phone in any way?
thaaaanxxx

monrokhoury said:
so say i upgrade my rooted htc one once the ota update becomes ready.. what happens? i dont want to end up with a bricked phone.. would it harm my phone in any way?
thaaaanxxx
Click to expand...
Click to collapse
An OTA update will not work on a rooted phone! For the OTA to work it needs stock recovery, stock rom and all of the files that it is attempting to update. If anything is missing then it will error out and return to your present setup.

and to complete what majmoz already said, if your rom is 100% stock, and you have flashed back your stock recovery, the phone will update fine but you will loose root. You'll need to flash a custom recovery after the OTA to re-root the rom.

Guys you're very helpful and i must thank you for that. i am on the official 4.4.3 rom so i just need to restore the stock recovery? how to do that? and will the current rooting method work on lollipop (and should i follow the same steps to install clockwork recovery)? Will the ota update relock the bootloader?
i'm sorry if i'm asking too many questions but i don't trust any other forum.

monrokhoury said:
Guys you're very helpful and i must thank you for that. i am on the official 4.4.3 rom so i just need to restore the stock recovery?
Click to expand...
Click to collapse
If you have not modified anything to your rom (Kernel is stock and always was, you have not deleted any /system files and you still have or restored all the content in /data/preload (wiped during bootloader unlock), so yes all you need to do is to flash back the stock recovery that match your version.
how to do that?
Click to expand...
Click to collapse
The same way you did to flash a custom recovery:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
and will the current rooting method work on lollipop
Click to expand...
Click to collapse
Flash the latest supersu from a custom recovery. Version 2.37 and above should work on lollipop
and should i follow the same steps to install clockwork recovery
Click to expand...
Click to collapse
You always flash the recovery using the same commands, stock or custom, on all versions its always:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
Will the ota update relock the bootloader?
Click to expand...
Click to collapse
OTA updates will never affect the bootloader status (S-ON/S-OFF, LOCKED/UNLOCKED/RELOCKED)

If you have not modified anything to your rom (Kernel is stock and always was, you have not deleted any /system files and you still have or restored all the content in /data/preload (wiped during bootloader unlock), so yes all you need to do is to flash back the stock recovery that match your version.
Click to expand...
Click to collapse
So, if I did flash a custom kernel, and did uninstall system programs (but didn't flash a custom Rom), what are my options if I'd like to upgrade to lollipop?
Thanks!
Sent from my HTC One using XDA Free mobile app

[Q] [RESOLVED] Lollipop OTA update aborted

Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?

kamso said:
Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?
Click to expand...
Click to collapse
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.

Seanie280672 said:
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.
Click to expand...
Click to collapse
Ok, thank you. But what I don't understand is that there's a long time I'm no more root, I'm full stock (Rom, recovery...), only S-off and Unlocked. So Why for previous OTA updates I have not had this problem? Why I have to manually update successfully from 6.09.401.11 version to 6.09.401.12 one? Why it is only the upgrade to the Lollipop which has problem?
What is the preload data? I already have this: https://www.androidfilehost.com/?w=...0f40a2a319761577a4c3f1e723594b05669cb009e9d00
Can I flash it and the stock recovery only?

Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file

migascalp said:
Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file
Click to expand...
Click to collapse
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.

kamso said:
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.
Click to expand...
Click to collapse
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.

Seanie280672 said:
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.
Click to expand...
Click to collapse
Ah Ok I understand. These are applications that disappear when we unlock the bootloader. I had already installed them there's a long time. As I said my OTA updates passed without problem.

Problem flashing stock Rom in TWRP:
"- Zip signature verification failed
- Error flashing zip"
I don't understand anything, what's happen?

Problem solved and phone updated. Thank you!!!