Database Info

[Q] Completely Wipe Xoom?

I am running an early 3.2 tiamat rom and i'm wanting to completely wipe all my things like music etc.
When I do a system reset there is no option to get rid of the data.
I have tried doing a wipe via CWM but this doesnt clear this data either.
Any ideas?

andypotts said:
I am running an early 3.2 tiamat rom and i'm wanting to completely wipe all my things like music etc.
When I do a system reset there is no option to get rid of the data.
I have tried doing a wipe via CWM but this doesnt clear this data either.
Any ideas?
Click to expand...
Click to collapse
Are the files you want to clear in your internal storage ("sdcard") or on your external micro sdcard? I think solarnz' version R4c CWM recovery was configured to avoid wiping data, and I know a wipe data/factory reset in CWM rcovery menu never touches the external sdcard.
You may be best off just manually deleteing your unwanted files, through a file manager app or via pc connection.

okantomi said:
Are the files you want to clear in your internal storage ("sdcard") or on your external micro sdcard? I think solarnz' version R4c CWM recovery was configured to avoid wiping data, and I know a wipe data/factory reset in CWM rcovery menu never touches the external sdcard.
You may be best off just manually deleteing your unwanted files, through a file manager app or via pc connection.
Click to expand...
Click to collapse
Sorry to revive an old thread but are you sure that is the only way?
I have done experimentation with files and (not knowing what I was doing really) and now I have various/random files scattered throughout my Xoom.
I would rather start over with a fresh clean slate but every time I do I factory reset (from xoom settings, not clockwork) the files are still there.
Any suggestions??
Thanks,
Digital
BONUS QUESTION: Which version of Clockwork should I be running now? I'm currently on 3.1x something I think. 3.2.0.0 ?
EDIT: Well never mind, I guess I got it to work. Not sure what the exact process/steps are supposed to be but I did a factory reset within Xoom and clockwork (plus extras) without a SD card then I did it the same process again with SD card and then I finally did a reboot into recovery after factory reset in clockwork (i think that may have been the key?)

digitalnerd said:
Sorry to revive an old thread but are you sure that is the only way?
I have done experimentation with files and (not knowing what I was doing really) and now I have various/random files scattered throughout my Xoom.
I would rather start over with a fresh clean slate but every time I do I factory reset (from xoom settings, not clockwork) the files are still there.
Any suggestions??
Thanks,
Digital
BONUS QUESTION: Which version of Clockwork should I be running now? I'm currently on 3.1x something I think. 3.2.0.0 ?
EDIT: Well never mind, I guess I got it to work. Not sure what the exact process/steps are supposed to be but I did a factory reset within Xoom and clockwork (plus extras) without a SD card then I did it the same process again with SD card and then I finally did a reboot into recovery after factory reset in clockwork (i think that may have been the key?)
Click to expand...
Click to collapse
Great! There is also a way to wipe from fastboot, but you would have to look up the exact commands. But it looks like you got your clean start.

easiest way i found is bassicaly flash through fastboot stock kernel rom and recovery etc...then you can start allover again with a nice "virgin xoom thats needs a good root"

okantomi said:
Great! There is also a way to wipe from fastboot, but you would have to look up the exact commands. But it looks like you got your clean start.
Click to expand...
Click to collapse
I guess I jumped the gun, still finding scraps of old files left behind.
It looks like I'll be trying the fastboot method. I had put the Xoom in a bad state a while back and had to learn some of those commands to revive it. I'll look into it, thanks for the tip!!
zbee said:
easiest way i found is bassicaly flash through fastboot stock kernel rom and recovery etc...then you can start allover again with a nice "virgin xoom thats needs a good root"
Click to expand...
Click to collapse
Would you mind writing up some quick steps and links to do that?
I have the xoom wifi mz604. Should I use Build HWI69 for US Retail
MD5 Sum: 3f52762e56474070fa71bdf34ba9afd1 or follow this?: http://forum.xda-developers.com/showthread.php?t=1446469
Once I get the correct ROM, it looks like I'll need to run the following commands.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
I don't think I need to do a: fastboot oem lock
after all that since I plan on rooting again right away.
I'm really enjoying the custom rom over here and would like to apply that again: http://forum.xda-developers.com/showthread.php?t=1400958
Basically, I just want to have a Xoom the cleanest it can be from time to time with the least amount of hassle. I rarely backup/restore data so that is not an issue for me right now.
This time around I would like to do it the right way and not just be in the dark. I'm starting to see that XDA is awesome community. Never thought my problem would actually get some input.

Can somebody confirm my steps?

Having a problem with my home button lighting up but not taking me home. I would like to wipe clean as well and start from scratch. Could someone please confirm the steps above?
Thanks ~

digitalnerd said:
...
Click to expand...
Click to collapse
before going through all that, just try an fastboot erase userdata, that should clear all your data in /data (and that includes /sdcard). If it doesn't, you could try fastboot oem unlock, that should most definately clear everything, no need to flash the stock rom or lock the device again.
Only if all that fails (with all that I'm talking about these two commands) I'd try to go with the steps you mentioned, they look quite okay to me.

llama-power said:
....
Click to expand...
Click to collapse
Thanks, llama-power. Works great! I also added the "fastboot erase cache" as well, not sure if it helps or hurts but just trying to ensure a clean wipe.
Here are my steps which might help somebody else out down the road:
1. Install motohelper usb drivers from : http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
1. Unzip "SDK_tools.zip" to C:/
2. Use command promot and type : cd c:/
3. Then type : cd sdk_tools
4. Then type : adb.exe
5. Thne type : adb devices
6. Make sure Xoom shows up as a device
7. Then type : adb reboot bootloader
8. Wait for the xoom to reboot
9. Then type : fastboot erase userdata
10. Wait 60 seconds or so
11. Then type : fastboot erase cache
12. Then type fastboot reboot (if you want to to use xoom and set up)
13. Consider rebooting into recovery if you are upgrading the ROM as well.
Click to expand...
Click to collapse

Note that you can also run "fastboot -w" for a shortcut to wipe both userdata and cache

kofrad said:
...
Click to expand...
Click to collapse
even better, thanks!!

digitalnerd said:
Can somebody confirm my steps?
Click to expand...
Click to collapse
This worked for me

[Q] Nexus 5, internal storage 0Mb

Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc

Sounds like uv messed up the partitions. unsure if theres a fix on this

Try
fastboot flash cache cache.img
Where cache.img is from the factory image

jd1639 said:
Try
fastboot flash cache cache.img
Where cache.img is from the factory image
Click to expand...
Click to collapse
This is happening without any problems but it does not change the problem.
I'm lost ...

in TWRP i have
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage

Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help

worfeur said:
Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help
Click to expand...
Click to collapse
What version of twrp are you using?

jd1639 said:
What version of twrp are you using?
Click to expand...
Click to collapse
I use twrp 2.6.3.2

worfeur said:
I use twrp 2.6.3.2
Click to expand...
Click to collapse
Try to flash this in fastboot, fastboot flash recovery recovery.img. Where recovery.img is the file below. If it installs, wipe cache within it
http://d-h.st/nbu. It's 2.6.3.4

This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?

N5
1. you unlock it
2. recovery with software.
Thanks

Wergin said:
1. you unlock it
2. recovery with software.
Thanks
Click to expand...
Click to collapse
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.

worfeur said:
Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc
Click to expand...
Click to collapse
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.

WoodburyMan said:
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.
Click to expand...
Click to collapse
Sorry, I do not know the firmware that was installed
It is a device used
habitformer said:
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.
Click to expand...
Click to collapse
when I flash a custom-recovery (stock or cwn) TWRP 2.6.3.2 always returns

I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).

WoodburyMan said:
This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?
Click to expand...
Click to collapse
thank you for your help
I have access to adb fastboot mode by boot recovery.img (recovery stock google)
and using the control slidload ADB
but impossible to get the command line
but when I type ADB Devices, my phone is found
otherwise I can not do a stock restoration because the bootloader does not update (KKX11D then I flashed back KKX11K) when I do well:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader

Beauenheim said:
I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).
Click to expand...
Click to collapse
thank you I'll try it tonight but I think I already tried

worfeur said:
thank you I'll try it tonight but I think I already tried
Click to expand...
Click to collapse
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem

jd1639 said:
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem
Click to expand...
Click to collapse
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory

worfeur said:
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory
Click to expand...
Click to collapse
Can you format data in 2.6.3.2? I'm thinking you have a bigger problem as you've already tried to flash the factory image and it did not work.

[Q] stuck without recovery acess & now phone only booting completely

hi guys,
system win7x64, moto g retail uk
in order to root i unlocked the bootloader from motorola page. successfully unlocked and rooted but...
problem nr 1 - from that day i was unable to access recovery by any means. every time i accessed it the withe screen with the motorola warning after unlocking came and nothing happened. i discovered this thread forum.xda-developers.com/showthread.php?t=2585755 and was able to change the boot logo from that screen to a regular one, but the problem persisted. tried to solve the problem and came to this thread forum.developers.com/showthread.php?t=2037808. "There's a file in /system/etc/ called install_recovery.sh that may need to be deleted for the custom recovery to stick. You need root to remove it."
converted that install_recovery.sh to bak and rebooted.
problem nr 2 - no access to recovery. lost root privileges. no acess to bootloader. the phone does a full reboot everytime (goes on reding every android app).
tried to upload an new "install_recovery.sh" (the same but renamed) but have no privileges through airdroid.
any suggestions highly appreciated. can i push the file through adb or sanything else?

after opening /system/etc/install-recovery.sh with notepad it reads like this. i guess it was changing the name from .sh to .bak that broke rooting
#!/system/bin/sh
# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc
# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.
# If you want to force loading the daemon, use "--daemon" instead
/system/xbin/daemonsu --auto-daemon &
# Some apps like to run stuff from this script as well, that will
# obviously break root - in your code, just search this file
# for "install-recovery-2.sh", and if present, write there instead.
/system/etc/install-recovery-2.sh

install-recovery.sh is altered by superSU. You lost root as this file is required for root.
The original file does flash stock recovery on boot (or at least after an OTA AFAIK)
Sounds to me like your original problem of not accessing recovery was maybe due to you using the power button to select recovery option in bootloader rather than volume UP which is the button used to select an option.
No idea why you can't now get to the bootloader at all, just renaming that file would not cause that. I guess altering the boot logo has caused an unknown issue somehow.
Putting back the install-recovery.sh file won't help at all with not being able to boot to bootloader. In actual fact I find it hard to believe you can't get to the bootloader, as if the bootloader was messed up you wouldn't even be able to boot the phone.
Anyway - without root the only way to get the file back in place is to flash the file (ie as a flashable zip) from custom recovery AFAIK. ADB won't work as you can't push a file to /system without using 'insecure ADB' which needs a rooted device.
Maybe search XDA and see if there is some other key combination to access bootloader.

scott_doyland said:
install-recovery.sh is altered by superSU. You lost root as this file is required for root. RIGHT! I altered its extension to .bak, rebooted and lost root access
The original file does flash stock recovery on boot (or at least after an OTA AFAIK)
Sounds to me like your original problem of not accessing recovery was maybe due to you using the power button to select recovery option in bootloader rather than volume UP which is the button used to select an option. Really dont know if that was the mistake. I lost recovery access (but not bootloader) immediately after unlocking the bootloader, when i saw the screen turning blue/violet i took the usb cable and it might have been the mistake.
No idea why you can't now get to the bootloader at all, just renaming that file would not cause that. I guess altering the boot logo has caused an unknown issue somehow. I altered the boot logo because everytime i tried to acess recovery the phone gave me the motorola warning and didn't go to recovery, just booted, after altering the logo the behaviour stayed the same, no recovery, juts normal booting.
Putting back the install-recovery.sh file won't help at all with not being able to boot to bootloader. In actual fact I find it hard to believe you can't get to the bootloader, as if the bootloader was messed up you wouldn't even be able to boot the phone. Yes, no bootloader by any means, the phoe just cold boots and checks every app (it takes a lot of time)
Anyway - without root the only way to get the file back in place is to flash from custom recovery AFAIK. ADB won't work as you can't push a file to /system without using 'insecure ADB' which needs a rooted device.
Click to expand...
Click to collapse
Right. Already tried different forms of adb (mount, remount, su, push, but NADA). Didint go for the custom recovery because i'm noob and dunno what it is (yet) but i'll try to find out. If you can guide me i any direction i really appreciate :good:
Despite all this mess, at least i hope this knowledge serves the community.

If you can't access bootloader and no longer rooted I don't think you are going to be able to flash a custom recovery anyway (custom recovery allows you to backup/restore entire device and flash ROMS).
Without bootloader access you are in a mess as can't access recovery and can't root.
You can't even reflash entire stock ROM inc recovery etc.
Basically unless you get bootloader access you are screwed AFAIK.
Hopefully someone else may have an idea.
As I mentioned before - search XDA and see if there are some button combos that may get you to bootloader rather than normal combos. Or any button combos to hard reset bootloader etc. It doesn't look good though.

screwed is the word scott. at least its a "normal phone", for now, it works normally, the only drag is the slow booting everytime i shut it down, oh and it doesnt shutdown, just reboots

scott
i have bootloader again, dontt know how but i do. can you point me how to root the phone again?

Have a read through this link, my posts in it should explain what to do
http://forum.xda-developers.com/showthread.php?t=2612195

scott_doyland said:
Have a read through this link, my posts in it should explain what to do
http://forum.xda-developers.com/showthread.php?t=2612195
Click to expand...
Click to collapse
Thanks Scott.
The situation got a little worse. Now SO (w7x64 and x32 i have both) do not recognize moto g. I connect usb cable and it only charges.
- if i connect it while off it reboots (every time rebuilds dalvik cache)
- if i connect it while on it only charges but windows doesn't make any sound (nothing at device manager)
- if i connect usb cable (while in bootloder screen) windows recognizes it only as android adb but not as media player (drivers installed). when i do 'adb devices' nothing comes although the phone says usb connected.
at settings i have USB-MTP, USB debugging enabled.
i can power off and acess bootloader screen but at that screen if i choose any option it just cold reboots. no recovery acess, nada! no adb acess.

In bootloader ADB doesn't work by design. Its fastboot you need.
So do in bootloader
fastboot devices
When booted to android AND if you turn on USB debugging in dev options you can do
adb devices
So one you have 'fastboot devices' working, ie PC recognizes device, then you are OK as if need be you can even download and flash complete stock images for everything inc /system, recovery etc to get it back to how it was out of the box.

scott_doyland said:
In bootloader ADB doesn't work by design. Its fastboot you need.
So do in bootloader
fastboot devices
When booted to android AND if you turn on USB debugging in dev options you can do
adb devices
So one you have 'fastboot devices' working, ie PC recognizes device, then you are OK as if need be you can even download and flash complete stock images for everything inc /system, recovery etc to get it back to how it was out of the box.
Click to expand...
Click to collapse
It was a good tip Scott, it kept me walking and this morning i was about to give up :good:
Below you can see what happened. I flashed cwm (for 4.4.2) successfully but when trying to access it phone cold reboots as usual. Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it?
...\root motorola>fastboot devices
TA8830L7VY fastboot
...\root motorola>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7604 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.461s]
finished. total time: 0.728s
>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.267s]
booting...
OKAY [ 0.504s]
finished. total time: 0.772s After this it does a cold reboot
you said i could re-flash a stock image. the phone came with 4.3 but in the meanwhile upgraded to 4.4.2. can i flash 4.3 after having unlocked the bootloader and updated to 4.4.2?. i managed to download both firmwares.
Having read that 4.4.2 bootloader is having trouble with accessing recovery (my case also) i tried to upload 4.3 bootloader. this was the result
...>fastboot-moto-windows.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.836s]
finished. total time: 1.934s
...>fastboot-moto-windows.exe reboot-
bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
i guess everything went right. the phone didnt a cold reboot and went right away to the bootloader. after selecting recovery in this new bootloader i finally managed to have acess to the last CWM 6.0.4.6 recovery. UFFFF!!!
After that i did a wipe cache partition and rebooted. Phone did a cold reboot. after that i follwed the post you mentioned and flashed SUper SU.through CWM
As seen before after renaming install-recovery.sh to .bak root was lost I checked and the file is there again along with the bak so i guess super su created it again.
Check list: Have bootloader. have recovery. have root, i'm on 4.4.2 with 4.3 bootloader. one thing thats not ok, everytime phone reboots android goes on with the following message "android is upgrading --- optimising app x of y" which takes a lot of time. even if i ask for a fast reboot. that was not the usual procedure, the phone just did a fast reboot and nothing more. any advice on this one?
What a enormous trip for someone that didnt knew much about this. Kudos to you for keeping the help!

Sounds like its pretty OK then apart from the 'android is upgrading' message. I would wipe dalvik cache from CWM. Im not 100% sure but I *think* 'android is upgrading' indicates its rebuilding the dalvik cache, although as I say Im not sure. Anyway wiping dalvik cache wont hurt. I'd wipe, reboot and you *may* still get the messages on first reboot, once all complete and phone is fully operational then reboot again and see if messages are gone.
You said you already wiped cache via CWM but may as well wipe that again as well.
If you still get the error go to 'settings/storage and click on 'cached data' and chose to wipe it (this is different from a cache wipe in CWM).
If messages still happen them Im afraid I dont know what else to do (factory reset of course is last resort).
To attempt to answer your other questions:
***************
** can i flash 4.3 after having unlocked the bootloader and updated to 4.4.2? **
I think so, if you have the entire firmware it includes recovery, bootlloader, android, radio images, kernel etc so flashing it in the correct sequence as can be found in other threads should give you complete 4.3 as it was out of the box. However please read other posts related to this as its not something I have done or have read much about.
If you have an entire 4.4.2 firmware (rather than just a 4.4.2 update) then same applies as above, ie flashing it will give you 4.4.2 entirely inc bootloader, recovery etc.
***************
Re bootloaders and recoveries - I havet followed the threads much regarding 4.4.2 and recoveries as its not that relevant to me right now but if 4.3 bootloader is working, ie you can get to recovery etc, I'd be inclined to stick with it.
fastboot boot recovery.img - all this does it boot the recovery.img direct from your PC, works for some people and not others - dont know why. Its not actually booting CWM from your phone.
When on 4.4.2 bootloader after flashing CWM (the 4.4.2 one I assume) did you try booting the recovery that was actually on the phone, eg booting up android then using ADB to issue
adb reboot recovery
OR just try selecting recovery from bootloader using VOL UP
or did you just 'fastboot boot recovery.img'
However as you have CWM on 4.3 bootloader and its working its irrelevant really, was just interested.
** Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it? **
root and/or unlocked bootloader makes no difference to booting into recovery. Booting into recovery should work, Im assuming you did a 'fastboot boot recovery.img' and this is what failed (as I said just above) as opposed to actually booting into the recovery on the phone itself?
Hope the above makes some sense. And I hope wiping dalvik cache etc does the trick.
If you get any other 'funnies' I'd personally install 4.3 images entirely so its out of the box stock and start from there, ie flash 4.3, allow kitkat to do OTA, then flash CWM for 4.4.2 and hope it works, then root.
If CWM for 4.4.2 doesnt work then downgrade bootloader and flash CWM then root.
Im a bit OCD about these things so I'd probably start from scratch anyway to ensure its all 100% nice and clean but thats up to you

Good morning Steve, thanks for your helpful info, once again.
scott_doyland said:
Sounds like its pretty OK then apart from the 'android is upgrading' message. I would wipe dalvik cache from CWM. Im not 100% sure but I *think* 'android is upgrading' indicates its rebuilding the dalvik cache, although as I say Im not sure. Anyway wiping dalvik cache wont hurt. I'd wipe, reboot and you *may* still get the messages on first reboot, once all complete and phone is fully operational then reboot again and see if messages are gone. Again, the same messages.
You said you already wiped cache via CWM but may as well wipe that again as well.
At CWMR there's also these options besides dalvik cache, a) wipe data/factory reset and wipe cache partition. factory reset is pretty obvious, it cleans all your data but does not fully restore 4.4.2 functionality (or does it? and it goes back to 4.3). Wipe cache partition is the same as settings/storgae/cached data?
If you still get the error go to 'settings/storage and click on 'cached data' and chose to wipe it (this is different from a cache wipe in CWM).
If messages still happen them Im afraid I dont know what else to do (factory reset of course is last resort). Does it go back to 4.3?
To attempt to answer your other questions:
***************
If you have an entire 4.4.2 firmware (rather than just a 4.4.2 update) then same applies as above, ie flashing it will give you 4.4.2 entirely inc bootloader, recovery etc. It might not be "entire". What i have 4.3 is 400MB, 4.4.2 is 180 MB, might be an upgrade.
***************
Re bootloaders and recoveries - I havet followed the threads much regarding 4.4.2 and recoveries as its not that relevant to me right now but if 4.3 bootloader is working, ie you can get to recovery etc, I'd be inclined to stick with it.
fastboot boot recovery.img - all this does it boot the recovery.img direct from your PC, works for some people and not others - dont know why. Its not actually booting CWM from your phone. it didint in 4.4.2, now it does.
When on 4.4.2 bootloader after flashing CWM (the 4.4.2 one I assume) did you try booting the recovery that was actually on the phone, eg booting up android then using ADB to issue. I did, but without sucess.
adb reboot recovery
OR just try selecting recovery from bootloader using VOL UP
or did you just 'fastboot boot recovery.img'
However as you have CWM on 4.3 bootloader and its working its irrelevant really, was just interested.
** Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it? **
root and/or unlocked bootloader makes no difference to booting into recovery. Booting into recovery should work, Im assuming you did a 'fastboot boot recovery.img' and this is what failed (as I said just above) as opposed to actually booting into the recovery on the phone itself? Both things failed, the phone just rebooted.
Hope the above makes some sense. And I hope wiping dalvik cache etc does the trick. it did not.
If you get any other 'funnies' I'd personally install 4.3 images entirely so its out of the box stock and start from there, ie flash 4.3, allow kitkat to do OTA, then flash CWM for 4.4.2 and hope it works, then root. I probably will take that road.
If CWM for 4.4.2 doesnt work then downgrade bootloader and flash CWM then root. Yes, at least i know that works.
Im a bit OCD about these things so I'd probably start from scratch anyway to ensure its all 100% nice and clean but thats up to you
Click to expand...
Click to collapse
In brief: Rebooting problem persists even when wiping dalvik cache twice. Now the device is not recognized in windows. Neither on desktop pc w7x64 nor laptop w7x32. have motorola drivers on both. It used to recognize device as mtp (media player xt1032) but not anymore. When connected in bootloader device manager recognizes as android adb. I feel the problem is from the phone and not SO. I'll try to fix it this morning.
If i reflash 4.3 do i have to do anything before? Wipe something? Do a nandroid backup? Do a normal backup? I have a few backup apps but never used any of them.
Great appreciation for your help Steve. Have a nice Sunday.

About the phone not being recognized as mtp, after a brief search it has to do with locking. If it's locked then windows explorer is denied any access for security reasons. As soon as i unlocked it windows recognized the device immediately. -1 problem. only the rebooting stuff now.
:good:

rebooting ptoblem
wyped dalvik and cache data several times
also wiped odex files
fixed permissions in rom manager
behaviour persists. after wiping, the phone goes "upgrading android - optimising 225 apps" after that when rebooting the phone goes "android is upgrading... - optimising 103 apps". factory reset as last resort sigh... i hate that :crying:

I am having the same issue with the phone being boot loader unlocked and when I try to get into recovery through fastboot it just reboots.
Do you have the stock files that you used along the way?
Thanks. I have never had a phone give me this much hassle before ??:'(

[Q] Razr HD Stuck in bootloop

Hey guys, love all the work that goes on in this forum.
I've run into a bit of a problem. My mate gave me his phone to try and fix after he interrupted a factory reset. It's stuck in a bootloop.
It's a RAZR HD and was originally from Telstra (Aus).
I've managed to unlock the bootloader, but quickly after that everything has gone to hell.
When I turn the phone on, it gives the bootloader is unlocked message. Then the android installation guy comes up and after about 5 seconds of trying to install the phone bootloops.
I am able to enter the Android System Recovery (3e) and have done factory reset/wipe data and wipe cache options, however does not change anything. When I press reboot system, the bootloop continues as if I did nothing. I have tried installing a ROM from an SD card however it fails at the Verifying Package stage. I am unable to adb push anything as usb debugging wasn't turned on.
I am able to enter into fastboot and can see my device however cannot flash any images from there for some reason using the fastboot commands (it comes up with a <bootloader> variable not supported! error: cannot load '[name of image file]'
I was able to use RSD Lite to flash the official Telstra ROM to the phone, however at the very end of the installation when it rebooted, it just went into the bootloop again.
Any help would be muchly appreciated.
Thanks guys!

Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...

piCARSO said:
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
Click to expand...
Click to collapse
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.

bweN diorD said:
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
Click to expand...
Click to collapse
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?

piCARSO said:
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
Click to expand...
Click to collapse
yes, thats correct.

Nexus 5 Stuck On 'Formatting /Data' After Factory Image Flashing

Nexus 5 stuck on 'formatting /data' screen after factory image flashing
Sorry for the long post. I just want to ensure I am providing all relevant history.
I have a Nexus 5 (Hammerhead) 32gb device, stock with no rooting. I mean, I had never done anything special on it ever.
1. Recently I started getting Google Play Store related problems, first 194 error and then couple of days back 495 (I think). After trying switching on/off, clearing cache and some other similar ways to fix this, I decided to do a factory reset :crying:
2. I backed up all my data, and followed the documented steps for factory reset. The phone got stuck on 'erasing'. After waiting for over 24 hours, I finally figured out that this 'erasing' is not going to complete, ever.
3. So I again did some research and figured that I should do a fastboot recovery. Tried that with no difference. Recovery again took me to 'erasing' screen.
4. Some more research and then I decided to flash a factory image using ADB. I was (and still am) a complete newbie, so first I figured out what was ADB and how to get to it. After completing the installation, I found out Nexus 5 factory images. There was no mention of which ones to chose, so I just picked up the latest one.
This is what I really followed:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
https://www.youtube.com/watch?v=DRp5jJO34PE
5. Having learnt my lessons, I read the flashing instructions many times and also watched some videos 3-4 times. Once I was confident that no more information was going to be had, and the phone was unlocked (fastboot oem unlock) I went ahead with the flashing. I did it step by step - bootloader, radio and they recovery image. The last one failed.
6. I did some more research and found a method which told me to unzip the last image and flash the component images one by one. I did. Success! However, the phone did not reboot by itself as the guide said it would. So I tried to boot it manually.
7. I did not get the dead android with red exclamation mark. Instead, I got an alive android with gears whirring on its tummy and back. Pressing power + vol-up button told me that this was the 'formatting /data' screen. I am unable to get past this screen. I am supposed to get to a screen where I can wipe data and cache etc. But I cannot get to it.
8. I have tried to wait it out (16 hours) and tried flashing the images again. Ultimately, I end up here.
9. I am unable to find any answers on what to do if stuck on this screen. So this is the end? Is my phone bricked? Is there anything else I can try? Will trying TWRP way help or is that just another way to same failure?
I would appreciate if there is anybody out there who can help me get my phone working again, or point me to a thread which helps me do it. Thanks!

Just wait it took me 5 hours of waiting

Try flashing Android 4.4.4 and see if that will boot. If that does not work try installing a custom recovery like TWRP, and do the wipes from there.

dicecuber said:
Just wait it took me 5 hours of waiting
Click to expand...
Click to collapse
I doubt it. 12 more hours have passed with no change.

eross said:
Try flashing Android 4.4.4 and see if that will boot. If that does not work try installing a custom recovery like TWRP, and do the wipes from there.
Click to expand...
Click to collapse
Thanks. I was thinking of trying TWRP anyway. I will try this today.
How does one select which image to flash? Is it always the latest one? In this case, how do I know which one is Android 4.4.4, and why are you recommending this specific one? I had purchased this phone in 2013 Feb (I think). So is there any specific image to be selected or the latest one is always to be picked?

Tom2403 said:
Thanks. I was thinking of trying TWRP anyway. I will try this today.
How does one select which image to flash? Is it always the latest one? In this case, how do I know which one is Android 4.4.4, and why are you recommending this specific one? I had purchased this phone in 2013 Feb (I think). So is there any specific image to be selected or the latest one is always to be picked?
Click to expand...
Click to collapse
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.

Tom2403 said:
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Click to expand...
Click to collapse
Reboot your phone into bootloader and download latest hammerhead 5.1.1 from Google. Extract everything and then extract the images. First use these commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then fastboot flash everything including bootloader.
Use this as a guide http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Then after finished reboot phone and leave it alone it will boot right up in 5-10 mins no need to go to recovery. In future don't format partitions.

try this: fastboot format cache

matt1515 said:
Reboot your phone into bootloader and download latest hammerhead 5.1.1 from Google. Extract everything and then extract the images. First use these commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then fastboot flash everything including bootloader.
Use this as a guide http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Then after finished reboot phone and leave it alone it will boot right up in 5-10 mins no need to go to recovery. In future don't format partitions.
Click to expand...
Click to collapse
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!

Tom2403 said:
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Click to expand...
Click to collapse
Tom2403 said:
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Click to expand...
Click to collapse
Glad to hear you got it up and running! No problem at all feels great to bring something f'd back to life.

Tom2403 said:
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Click to expand...
Click to collapse
I have same problem. I did everything that was written above but still my phone shows android with rotating cube on its tummy. Any ideas? Thanks in advance

dmuml10 said:
I have same problem. I did everything that was written above but still my phone shows android with rotating cube on its tummy. Any ideas? Thanks in advance
Click to expand...
Click to collapse
Go into bootloader and format the cache: fastboot format cache

inimaitimepass said:
Go into bootloader and format the cache: fastboot format cache
Click to expand...
Click to collapse
I did that but nothing changed. Still shows android with rotating gears.
Does anyone know what does that animation mean ?

dmuml10 said:
I did that but nothing changed. Still shows android with rotating gears.
Does anyone know what does that animation mean ?
Click to expand...
Click to collapse
How long did you leave at that? Sometimes it may take long time depending upon the storage size of your phone. Usually between 20 to 40 mins.

inimaitimepass said:
How long did you leave at that? Sometimes it may take long time depending upon the storage size of your phone. Usually between 20 to 40 mins.
Click to expand...
Click to collapse
I left it more than an hour.
Is it normal that my phone shows this Android animation after I flushed new factory image? Why is it trying to still "Format /data..." after new image flush?
Is there any other way to flush android factory image from scratch? I already used nexus root toolkit and fastboot

dmuml10 said:
I left it more than an hour.
Is it normal that my phone shows this Android animation after I flushed new factory image? Why is it trying to still "Format /data..." after new image flush?
Is there any other way to flush android factory image from scratch? I already used nexus root toolkit and fastboot
Click to expand...
Click to collapse
I'm really sorry that you are stuck in this mess. It is normal but more than 1 hour is way too much. I'm not sure about the causes, but you can try two more things and see how it goes. One is to use flash-all.bat script. If that didn't work then you can flash a custom ROM like Chroma and then try flashing the stock ROM.

inimaitimepass said:
I'm really sorry that you are stuck in this mess. It is normal but more than 1 hour is way too much. I'm not sure about the causes, but you can try two more things and see how it goes. One is to use flash-all.bat script. If that didn't work then you can flash a custom ROM like Chroma and then try flashing the stock ROM.
Click to expand...
Click to collapse
Thanks for help.
I flashed philz_touch recovery. From there I did factory reset and after that I executed this commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
Now my phone works.:victory:

dmuml10 said:
Now my phone works.:victory:
Click to expand...
Click to collapse
Good to hear. Weren't you using a custom recovery before philz'?

inimaitimepass said:
Good to hear. Weren't you using a custom recovery before philz'?
Click to expand...
Click to collapse
No. I only used stock recovery before philz.