Database Info

Can't factory reset after encryption.

Alright its my first issue that I have needed to post about so here we go.
Basically I decided to encrypt my doom before I brought it with to spring break and now that I'm home I want to un encrypt it. I tried the way through settings and it just boots into recovery and will not format the /data option. Next I tried to factory reset through rom manager and through CWM (I'm rooted running codename android) it wont let me mount the SD card to do anything so I'm wondering how can I get it to factory reset? Thanks
Sent from my Incredible 2 using XDA

diablodow said:
Alright its my first issue that I have needed to post about so here we go.
Basically I decided to encrypt my doom before I brought it with to spring break and now that I'm home I want to un encrypt it. I tried the way through settings and it just boots into recovery and will not format the /data option. Next I tried to factory reset through rom manager and through CWM (I'm rooted running codename android) it wont let me mount the SD card to do anything so I'm wondering how can I get it to factory reset? Thanks
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
I've had this problem too. Not 100% positive this is the BEST way to do it, but it certainly works: download the proper build files you need, then, using fastboot, use these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Hope that helps. Let me know if I can clarify.

Ok I can update with what happens I'm on a roadtrip now. It managed to format /system so now its stuck at the boot screen but still lets me go into recovery and fastboot so I feel its not hopeless.
Sent from my Incredible 2 using XDA

So you don't have any access to a laptop or anything you could use to use fastboot? In my experience, you cannot do a wipe from recovery when you've encrypted the device. I have only been able to get back to factory with the method described above.
I don't mean to discourage you, I'm not completely positive you can't do something in recovery that might be able to get you back to stock, hopefully someone else can chime in if that's the case.

Got it fixed once I got to a machine that had ADB and could do some fastboot command. Moral of the story is don't encrypt your tablet then format random stuff. Please close.
Sent from my Incredible 2 using XDA

Problem solved please delete
Sent from my Incredible 2 using XDA

johnpwu said:
I've had this problem too. Not 100% positive this is the BEST way to do it, but it certainly works: download the proper build files you need, then, using fastboot, use these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Hope that helps. Let me know if I can clarify.
Click to expand...
Click to collapse
I just had this same issue with my Galaxy Nexus (GSM) and now I'm back to factory!
Thanks so much!!!

johnpwu said:
I've had this problem too. Not 100% positive this is the BEST way to do it, but it certainly works: download the proper build files you need, then, using fastboot, use these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Hope that helps. Let me know if I can clarify.
Click to expand...
Click to collapse
Trully sorry man for my ignorance here but...
I'm a complete n00b and i wanted to know, like, what do i need to do with that exactly, I also have my phone encrypted
could you tell me, I'm kind of a beginner so please don't be harsh lol

[Q] Sticky Bit Fastboot

So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.

fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.

KitsunePaws said:
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.
Click to expand...
Click to collapse
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.

fallnSaint said:
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.
Click to expand...
Click to collapse
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.

KitsunePaws said:
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.
Click to expand...
Click to collapse
I had this same issue when porting TWRP ^^^.
I can't seem to find my posts on it right now, but someone just said do a clean flash. No problems since

how did you do this please!

fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Okay, this will probably help you...while your device is in Sticky Bit Factory Fastboot, open up a command prompt and connect to your device (given you know how to do so in your folder containing your fastboot app and drivers). Then type "fastboot oem fb_mode_clear" This command will allow your device to boot into system normally. Problem is (I think) when a failed flash occurs sometimes it sets your device in that mode and the above command clears it. Another way to manually place a device in the same state you described is to enter this command using fastboot: fastboot oem fb_mode_set. I believe that is how RSD Lite automatically reboots your device into factory fastboot mode after flashing partitions (.mbn) on your system so that it may resume flashing the boot, recovery, and system images, etc. Let me know if it helps.....
Sent from my XT897 using xda premium

[Q] What are the signs of a Bricked phone?

My MT4GS is boot looping. I can get into the bootloader, but can't get into recovery and flashing a stock image doesn't do anything. I've unlocked the phone and achieved S-OFF using the j-bear wire trick. I've ran the phone for a few weeks after getting the s-off, so I don't think it's that. When I flash a stock image from the bootloader, the software/radio versions don't change and it still boot loops. I also have a faint red light in the notification and trackpad. I'm out of ideas. Anyone have any suggestions?

well first thing id attempt is to grab an image of a recovery and try and flash it through fastboot, image HERE
fastboot command
Code:
fastboot flash recovery recovery.img
if you need any further instruction on how to use fastboot you can get some info HERE
or if this dosent work or have more questions feel free to ask
its not a brick if you can get into hboot, you may have a tough time getting your phone working again but usually its doable.
good luck!

Thanks for the quick reply. I did a recovery flash through fastboot (CWM 5.0.2.7), but still couldn't get to recovery. I was able to update hboot to the jb_hboot. That allowed me to perform some more fastboot commands, such as: erase boot, recovery, system, userdata. I then tried to flashed a signed stock image, but still got stuck at boot loop and couldn't get into recovery. I might try TWRP recovery to see if it changes anything.

what all does it say on your bootloader screen now?

It says:
= Juopunut Bear =
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.1313
RADIO-11.16.3504.20_2
eMMC-boot
Nov 21 2011, 20:20:47

Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2

when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.

demkantor said:
Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2
Click to expand...
Click to collapse
Riyal said:
when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.
Click to expand...
Click to collapse
I didn't get a fastboot error when I wrote to boot, it said completed and a time. When I choose recovery, I get a boot loop. I can't connect via adb. I don't think I have the right drivers setup for adb because when I type "adb remount" it says no device found.

Drivers taken from weekendsr2shorts mirror thread
it is strange that you can get fastboot working but not adb, but maybe more digging needs to be done to solve that. but it could just be from hboot screen there is no access to adb... come to think of it that sounds normal
try erasing recovery partition and flashing again, maybe there is some corruption there that stuck around even after the last flash
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot-bootloader
see if any of that works

Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?

Not too sure a great way of telling, maybe try reformatting recovery? On a side note what exactly were the stock image you were trying to flash? I believe there is an issue when flashing certain stock setups after the radio s-off, being the way bootloader varifies the radio, recovery, Rom, etc. Sometimes things can go awry when doing this. I don't have a ds yet (still waiting on stupid parts from China) so I haven't done a whole lot of research on this phone. Maybe someone will chime in who knows more specifically what to be looking for
Sent from my Desire Z using xda premium

I tried to flash both "PG59IMG_Doubleshot_TMOUS_1.55.531.3_Radio_11.59.3504.00_11.16.3504.20_2_release_227956_signed" and "PG59IMG_Doubleshot_TMOUS_1.63.531.2_Radio_11.59.3504.00_11.16.3504.20_2_release_245247_signed". You think I should try a custom ROM instead? Is there one available to flash through the bootloader or fastboot? I tried to flash the signed stock image zips with fastboot, but it complained about not finding expected signature. Sorry to hear about your DS. Hope you get your parts soon.

rumi409 said:
Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?
Click to expand...
Click to collapse
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.

Well you can flash roms through fastboot,
fastboot update.zip
Just change the name of the Rom to what's needed
Maybe try to format as many partitions as you can through fastboot first?
Sent from my Desire Z using xda premium

WeekendsR2Short said:
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.
Click to expand...
Click to collapse
I flashed this recovery image via the bootloader and fastboot. Still no luck. Is erase and format the same thing? I've erased boot, recovery and system. I checked that they were erased by doing a Image CRC, which resulted in a 0 value. Then flashed the signed DS ROMs. It still resulted in the same, boot loop.

erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation

demkantor said:
erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation
Click to expand...
Click to collapse
I can't seem to get any of the format commands to work. It just displays the fastboot commands and options, as if I typed something it can't understand.

Have you tried a different SD card?

mattlowry said:
Have you tried a different SD card?
Click to expand...
Click to collapse
I'm not using a micro sd card. Have been flashing through the computer.

rumi409 said:
I'm not using a micro sd card. Have been flashing through the computer.
Click to expand...
Click to collapse
have you tried placing the pg file on your sd card and let the bootloder load it itself?

[SOLVED/THANKS GUYS] hopeless boot loop.. :(

was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
can i RUU or something?

wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try

wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
Can you relock the bootloader? If can then download the official RUU(here is 2.20 firmware http://www.htc.com/us/support/htc-one-x-att/software-updates) and that'll probably save your phone.
oh, you can use the all in one toolkit(http://forum.xda-developers.com/showthread.php?t=1952426) to relock your bootloader if you can.. good luck

TheEmpyre said:
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try
Click to expand...
Click to collapse
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing. tried to mount SD card: windows wants to format it. **** me

wdkingery said:
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing
Click to expand...
Click to collapse
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.

iElvis said:
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.
Click to expand...
Click to collapse
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?

wdkingery said:
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?
Click to expand...
Click to collapse
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM

TheEmpyre said:
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM
Click to expand...
Click to collapse
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.

wdkingery said:
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.
Click to expand...
Click to collapse
Does your TWRP not have a "Format Data" Option in the Wipe Menu?
Edit: Just read your most recent edit, happy flashing hope everything works out. Oh and add [Solved] to your title if you don't mind

it does, but even that didn't work..

Xoom 4g Stuck at Red M

My Xoom is a 3g that I sent in to have the 4g upgrade. Ive been running different roms for a couple years, decided to go back to stock the other day. I followed some steps I found at xda about how to do that, It was some version of honeycomb.
Anyways, after a reboot of the xoom It is stuck at the red M. I cannot get into recovery, cannon use adb commands. However, fastboot is working. What can I try next? After spending hours googling it, this doesnt seem real uncommon. But most of the links on how to put on a new bootloader with something called avalance 1.35 seem to be broke. Any ideas?

Your Xoom does not have an OS installed, nor a recovery.
Need to fastboot the stock images.

Mjamocha said:
Your Xoom does not have an OS installed. Flash a custom ROM
Click to expand...
Click to collapse
Correct. However, I cannot get into recovery to flash a rom. I have tried pushing the Motorola default through fastboot. It says it takes it but doesnt do anything.

ArXane said:
Correct. However, I cannot get into recovery to flash a rom. I have tried pushing the Motorola default through fastboot. It says it takes it but doesnt do anything.
Click to expand...
Click to collapse
yeah, i corrected my last comment.
hmmm .... odd

Mjamocha said:
yeah, i corrected my last comment.
hmmm .... odd
Click to expand...
Click to collapse
I have done the following:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
I got the files from the Motorola Support site.
I also used the RSD Lite to try and push factory image.

ArXane said:
I have done the following:
Click to expand...
Click to collapse
you forgot the last command
fastboot oem lock

Mjamocha said:
you forgot the last command
fastboot oem lock
Click to expand...
Click to collapse
Sorry, I have done that one also.

are you using the correct stock images for the 4G version?

Mjamocha said:
are you using the correct stock images for the 4G version?
Click to expand...
Click to collapse
Here are the links I have tried:
http://www.randomphantasmagoria.com/firmware/xoom/trygon4g/
HLK75D
I also tried the motorola image: MZ602_HLK75D that I had to request from Motorola.

It seems that what you have tried is the correct process. I too have the 4G Xoom (USA) and have used that process myself many times. However I used the "MZ600_HRI66" images, to return to stock with no problems. I may suggest to repeat the return to stock process using the HRI66 images.

Mjamocha said:
It seems that what you have tried is the correct process. I too have the 4G Xoom (USA) and have used that process myself many times. However I used the "MZ600_HRI66" images, to return to stock with no problems. I may suggest to repeat the return to stock process using the HRI66 images.
Click to expand...
Click to collapse
WIll try, thank you. Ever heard of everest 1.5 bootloader? It looks like that may be a common fix. All the links I find are broken.

Nope.... flashing HRI66 didnt change anything. Still cannot ADB, still doesnt boot.

no never heard of it. are you on everest?
adb wont work unless usb debugging is enabled, and you can't get into
USB debugging because you can't get into the system.
try this to place a recovery;
fastboot oem unlock
fastboot reboot
Get back into fastboot then grab a recovery image;
fastboot flash recovery (your recovery.img here)
if all else fails - go here - http://forum.xda-developers.com/showthread.php?t=1468298

Mjamocha said:
no never heard of it. are you on everest?
adb wont work unless usb debugging is enabled, and you can't get into
USB debugging because you can't get into the system.
try this to place a recovery;
fastboot oem unlock
fastboot reboot
Get back into fastboot then grab a recovery image;
fastboot flash recovery (your recovery.img here)
if all else fails - go here - http://forum.xda-developers.com/showthread.php?t=1468298
Click to expand...
Click to collapse
Tried flashing recovery with the stpes agove, same deal, cannot get into recovery. WIll try the LORD tool and will let you know.