Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks
mgoldenberg said:
Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks
Click to expand...
Click to collapse
I am in the same predicament. I hope there is a way out
mgoldenberg said:
Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks
Click to expand...
Click to collapse
when you get to Android Andy what happens when you hold volume down and tap volume up?
If you get in there I would wipe the cache partition as well... tho either of these may not help the issue... what were you doing prior to this happening? were you updating and get this upon its restart? Did it die and power up to this?... did it just randomly shut off and power up to this?
Sent from my XT907 using xda app-developers app
ezknives said:
when you get to Android Andy what happens when you hold volume down and tap volume up?
If you get in there I would wipe the cache partition as well... tho either of these may not help the issue... what were you doing prior to this happening? were you updating and get this upon its restart? Did it die and power up to this?... did it just randomly shut off and power up to this?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
When I got to android andy the android system recovery 3e menu popped up. I wiped the cache partition and did a factory reset, then rebooted but I'm still going in circles between the dead android and fastboot. Prior to this I had tried using safestrap to set up a recovery, but when I rebooted, I got stuck at fastboot. There was one point when I got to what I think was the fastboot menu and from there I tried flashing cyanogenmod, which I'm pretty sure was a mistake. Now I cant figure out how to get back to that menu.
mgoldenberg said:
When I got to android andy the android system recovery 3e menu popped up. I wiped the cache partition and did a factory reset, then rebooted but I'm still going in circles between the dead android and fastboot. Prior to this I had tried using safestrap to set up a recovery, but when I rebooted, I got stuck at fastboot. There was one point when I got to what I think was the fastboot menu and from there I tried flashing cyanogenmod, which I'm pretty sure was a mistake. Now I cant figure out how to get back to that menu.
Click to expand...
Click to collapse
OK...
First, what do you mean by "set up a recovery"?
I noticed your bootloader is locked. That means no custom recoveries can be flashed, so that's probably your problem.
If you tried to fastboot the Cyanogenmod zip (!?) that definitely didn't help.
What exactly are you trying to accomplish? Are you trying to reset to sell or return or something? Also, what system version did you have (or, if you don't know that, when did you get the phone and have you taken any OTA updates)? And were you previously rooted?
It sounds like you had a bad flash. Give me that info and I'll try to help you unbrick it...
Sent from my Nexus 7 using Tapatalk 4
From the fastboot details it looks like the most recent ota
mgoldenberg said:
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Click to expand...
Click to collapse
I say rsd the recent firmware....
Sent from my XT907 using xda app-developers app
sloosecannon said:
OK...
First, what do you mean by "set up a recovery"?
I noticed your bootloader is locked. That means no custom recoveries can be flashed, so that's probably your problem.
If you tried to fastboot the Cyanogenmod zip (!?) that definitely didn't help.
What exactly are you trying to accomplish? Are you trying to reset to sell or return or something? Also, what system version did you have (or, if you don't know that, when did you get the phone and have you taken any OTA updates)? And were you previously rooted?
It sounds like you had a bad flash. Give me that info and I'll try to help you unbrick it...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...
mgoldenberg said:
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...
Click to expand...
Click to collapse
Try this
I was stuck on the same screen all day
http://www.droidrzr.com/index.php/topic/28162-house-of-moto/
mgoldenberg said:
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...
Click to expand...
Click to collapse
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Oh ok, thanks for explaining. I'm not sure when I updated, but I know for sure it was OTA, so I can't downgrade. And do I need to unlock to fix this whole thing? Because for now I just want my phone back... I'm not exactly worried about flashing or rooting or anything.
mgoldenberg said:
Oh ok, thanks for explaining. I'm not sure when I updated, but I know for sure it was OTA, so I can't downgrade. And do I need to unlock to fix this whole thing? Because for now I just want my phone back... I'm not exactly worried about flashing or rooting or anything.
Click to expand...
Click to collapse
Did you try the link I provided? I was stuck on the same screen, took me all day to figure it out.
Sent from my XT907 using xda app-developers app
zombolt said:
Did you try the link I provided? I was stuck on the same screen, took me all day to figure it out.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
So this might be a stupid question... but which option do I choose after typing in my phone model? RSD, Fastboot [snapdragon] or moto-fastboot [omap]?
sloosecannon said:
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Also, I tried unlocking my bootloader. I used this thing called motopocalype and it should have worked, but apparently it didn't Im sort of hesitant about running it again.
Here's the link: http://www.droidrzr.com/index.php/t...k-your-bootloader-atrix-hdrazr-hdrazr-m-only/
Did you get your phone back up?... if your on system version .3 or .78 you cannot unlock your boot loader build date 5/2013..
Sent from my XT907 using xda app-developers app
mgoldenberg said:
Also, I tried unlocking my bootloader. I used this thing called motopocalype and it should have worked, but apparently it didn't Im sort of hesitant about running it again.
Here's the link: http://www.droidrzr.com/index.php/t...k-your-bootloader-atrix-hdrazr-hdrazr-m-only/
Click to expand...
Click to collapse
If it didn't work, you're probably already updated. Looks like you can't unlock unfortunately
Sent from my XT907 using Tapatalk 4
mgoldenberg said:
So this might be a stupid question... but which option do I choose after typing in my phone model? RSD, Fastboot [snapdragon] or moto-fastboot [omap]?
Click to expand...
Click to collapse
Rsd. From that point you should be able to choose whether you want to erase everything or save it. Worked like a charm for me, took about 10min
Sent from my XT907 using xda app-developers app
Related
So i tried to root my phone using one of the tutorials and ended up with a padlock screen on my phone. after researching i ALOT i decided on hard reseting my phone from the recovery menu. but all i see now is the google logo i believe i have deleted the 2.3.4 while reseting. can someone guide me from here. i am a n00b and i have had this phone for just 2 days. thanks in advance
anyone who can help?
youngballer said:
anyone who can help?
Click to expand...
Click to collapse
Please be more specific.
What tutorial did you use?
Did you download clockwork recovery?
Do you have the superuser zip?
If you can enable fast boot and fastboot flash recovery you should be able to mount your usb storage in CWM and then install a ROM and the su zip.
stuck on the nexus s boot screen
Babydoll25 said:
Please be more specific.
What tutorial did you use?
Did you download clockwork recovery?
Do you have the superuser zip?
If you can enable fast boot and fastboot flash recovery you should be able to mount your usb storage in CWM and then install a ROM and the su zip.
Click to expand...
Click to collapse
i used the one mentioned in addictive tips website (http://www.addictivetips.com/mobile/how-to-root-nexus-s-with-a-single-click-using-superboot/). i basically followed what these guys had mentioned.
since this failed i read that the other option is to go through fastboot > recovery > and clear everything but this did not change anything.
can someone give me a step by step guideline on how to continue. i dont mind going back to the stock 2.3.4 android. i just bought the phone yesterday
Which version do you have? The sprint or t mobile? Check if you can go into fast boot hold down volume up and then powerbutton. If not you may have to Odin it if not. That super one click looks old..
Sent from my Nexus S 4G using XDA App
chewbz said:
Which version do you have? The sprint or t mobile? Check if you can go into fast boot hold down volume up and then powerbutton. If not you may have to Odin it if not. That super one click looks old..
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I am in Canada but the model is 19020 A. I can get to the fastboot mode but don't know what to do after that.
I have the 4g so I don't want to give you the wrong information and never encountered this situation so sorry dude. Hopefully a more experanced user can help you out.
Sent from my Nexus S 4G using XDA App
Btw if all fails you can Odin it
Sent from my Nexus S 4G using XDA App
its all good thanks for trying to help
If your ROM flashed incorrectly, it would lead to your phone being in a state where it just shows a GOOGLE with a Padlock; kind of like turning on a computer without an operating system.
You would have to read the instructions on rooting your phone, which involves using fastboot and flash recovery from fastboot (All this is in the rooting guide). Simply reflash the recovery so you boot up back in recovery and try flash the rom again.
The same happened to me, I fixed it buy flashing a stock boot.img
Sent from my Nexus S using XDA App
thanks for the replies. how do i flash from the fastboot mode? when i plug it in to my computer i cant see the drive but my computer can detect the nexus s is plugged in
Set up adb first, they have the guides in the dev section, I used wolverines guide, you'll have to look for the software img, I don't know where it is at for the GSM model. Good luck
Sent from my Nexus S 4G using XDA App
Sounds like you're rooted and have recovery installed, but your OS is hosed.
Flash a ROM.
thanks for the replies guys. i have the adb setup on my laptop. i took it to one of the stores and he said he cant reflash it for some reason. he said he needs to get some software off samsung and it will take him a day. my phone is brand new and i didnt wanna trust him. do u guys think i should use odin? one of my friend has a galaxy s and he said odin should work fine on my phone.
Can you get into the ClockworkMod recovery menu? Turn the phone completely off then hold VolUp and Power until you get into Recovery.
If you get there, you're golden. Just download a ROM (I recommend Deck's) and away you go.
i can get into recovery but it gives me option like wipe everything and i selected that. but when i reboot the phone the same locked screen pops up. anyone from toronto here who i can contact?
youngballer said:
i can get into recovery but it gives me option like wipe everything and i selected that. but when i reboot the phone the same locked screen pops up. anyone from toronto here who i can contact?
Click to expand...
Click to collapse
Basically with those wipe commands you make the Rom unuseable. You have to flash a new one or apply it via Odin. There are various guides on this forum section. Odin requires less technical knowledge but is a bit more risky then flashing via recovery. Odin and the Roms for that method can be obtained from samfirmware.com. Zipped roms can be found in the development section here.
Sent from my Nexus S
After i tryed flashing kaos droid i think ive managed to brick my nexus 7. It just boots into cwm v6.0.1.0. Ive tryed a number of times holding down the power and the volume buttons together and i CANT get into the bootloader ): . No matter what i do it just boots into the recovery even if i flash another rom it goes back to cwm. I dont know what to do please help? I cant even shut the screen off its been in cwm for over 3 hours now \:
And i was rooted and unlocked before this. Tab was working fine till i flashed kaos droid
Sent from my myTouch 4G Slide using Tapatalk 2
Just use recovery to restore your backup.
Sent from my Nexus 7 using xda premium
This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.
The toolkit does everything for you. All in one method and you're done.
I'm sure its his .img
Sent from my Nexus 7 using xda premium
I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
Sent from my Nexus 7 using xda premium
El Daddy said:
I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
I will try using the toolbox but i dont think i have access to fastboot from the recovery? I mean im telling you guys my screen has been on for over 4 hours because it just reboots and wont turn off.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
When i get home. To my computeer im going to try using the toolkit hopefully it works
Sent from my myTouch 4G Slide using Tapatalk 2
nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
I had a similar problem on my og evo. Try seeing if you can flash the recovery from a computer while booted into cwm. Then it'll reboot into new recovery, you flash rom, and you stop sharding your pants
nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
kieso said:
This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.
Click to expand...
Click to collapse
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2
El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2
On a side note, i had tryed everything i formated the sd in cwm and now it appears on cwm as if theres "No files found" but on my computer everything i had previously is still there.
So there is a connection to the storage part of the device but not adb or fastboot
Sent from my myTouch 4G Slide using Tapatalk 2
nemesis93 said:
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Hmmm. You should have a working adb while booted into a custom recovery. Are your drivers installed correctly?
Also, the reason why you computer sees the files is because with mtp it caches the files.
Sent from my Nexus 7 using xda premium
El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
So far i got adb to work finally! Happy im making some progress.
Now im able to boot into the bootloader so i can run fastboot commands. I currently have NO rom whatsoever installed so im waiting to flash the stock rom using the toolkit. Thank you for your help
Also when i booted into twrp it said i had 3% battery left lol so im just hoping it will work now.
Sent from my myTouch 4G Slide using Tapatalk 2
OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?
Mach3.2 said:
OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?
Click to expand...
Click to collapse
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2
nemesis93 said:
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium
El Daddy said:
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yeah i tryed at first because i was lazy and it didnt work so i did it through fastboot.
Thanks again
Sent from my myTouch 4G Slide using Tapatalk 2
Glad you got it working
nemesis93 said:
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Sorry I wasn't trying to bust your stones. I haven't rooted yet because of all of the posts like yours. I've just seen more problems with flashing on this device then any other that I have with my past Droid devices. What we really need is apx (spelling?) Drivers and n7 files for a sure fire recovery from any disaster
Hopefully I don't have to start another thread.
I too think I bricked my Nexus 7.
I was having trouble and I accidentally cleared a file from the System UI app (its a system required app) which caused me to loose the 3 buttons on the bitten of the screen.
So I went to CWM to do a restore which said it failed.
After that it would not boot.
Its just stuck with the Google logo on the screen.
I held down the power up & down volume buttons and I get a screen that gives me that START button on the top right of the screen with the text in small size on the bottom left.
I can use the up and down volume to make the start button change to recovery mode or bootloader but activating them just goes to Google logo.
Can I recover or is it totally lost?
I also don't remember if I left the Nexus 7 in Debug mode which is usually required to perform custom Roms
Thanks
Rob
Sent from my SPH-D710 using Tapatalk 2
I have plugged in my nexus 4 i press adb reboot bootloader then i press fastboot oem unlock i click yes . afterwards the guide said that i choose recovery mode and a a green anroid would pop up and afterwards i should press volume up and power to select factory reset . sth went wrong , i don't know what and my phone started normally like i had just pressed power button. then i tried doing again the steps but when i choose recovery mode an anroid with an ! inside a red tiangle pops up. PLEASE HELP
mitsos1996 said:
I have plugged in my nexus 4 i press adb reboot bootloader then i press fastboot oem unlock i click yes . afterwards the guide said that i choose recovery mode and a a green anroid would pop up and afterwards i should press volume up and power to select factory reset . sth went wrong , i don't know what and my phone started normally like i had just pressed power button. then i tried doing again the steps but when i choose recovery mode an anroid with an ! inside a red tiangle pops up. PLEASE HELP
Click to expand...
Click to collapse
Hey bro calm down, it is definitely not a MASSIVE problem
So are you trying to root your N4?
mharis05 said:
Hey bro calm down, it is definitely not a MASSIVE problem
So are you trying to root your N4?
Click to expand...
Click to collapse
Yes ... I just bought it . I read lots of threads before I start the process of rooting but I had never read for an android with ! In a red triangle
So your bootloader is unlocked?
Can you still get into the bootloader?
Looks like all you need to do is flash a custom recovery. This can be done using the following command:
Code:
fastboot flash recovery nameofrecovery.img
Sent from my HTC Desire using xda app-developers app
chromium96 said:
So your bootloader is unlocked?
Can you still get into the bootloader?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Yes ... That is what I am trying to explain . I tried restarting the whole process of rooting included the bootloader unlockment . of course it says the boot loader is unlocked and when I choose recovery mode the android with the ! Pops up
mitsos1996 said:
Yes ... That is what I am trying to explain . I tried restarting the whole process of rooting included the bootloader unlockment . of course it says the boot loader is unlocked and when I choose recovery mode the android with the ! Pops up
Click to expand...
Click to collapse
That's because you need to fastboot flash a recovery man. That's the step your missing.
Sent from my Nexus 4 using Tapatalk 2
strapped365 said:
That's because you need to fastboot flash a recovery man. That's the step your missing.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Trying to flash a recovery in recovery? Recoveryception?
Download a recovery.img, place it in the folder where you keep fastboot, flash. What you were seeing was the stock recovery. You're OK. Panic gets you nowhere.
estallings15 said:
Trying to flash a recovery in recovery? Recoveryception?
Download a recovery.img, place it in the folder where you keep fastboot, flash. What you were seeing was the stock recovery. You're OK. Panic gets you nowhere.
Click to expand...
Click to collapse
You have the steps right.....but the command I gave should show anyone with knowledge that its to be ran in boot loader hence fastboot...nice try though
Sent from my Nexus 4 using Tapatalk 2
strapped365 said:
You have the steps right.....but the command I gave should show anyone with knowledge that its to be ran in boot loader hence fastboot...nice try though
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Obviously he doesn't have knowledge. No need to come in here and seek an argument.
estallings15 said:
Obviously he doesn't have knowledge. No need to come in here and seek an argument.
Click to expand...
Click to collapse
See, this is what happens all across xda...someone doesn't research their issue or don't understand it, but they pursue it anyways. Pointless.
Wasn't seeking an argument, just dont like being "corrected" when valid info is given. If the user is to lazy to Google how to use fastboot... Well then that's his issues and can sit in bootloop land for all I care. You can only help so many people before well....stuff becomes redundant. BTW the Nexus was the absolute easiest phone to root, so if the user can't even grasp that tint concept we will be holding their hand their entire stay in the community.
Sent from my Nexus 4 using Tapatalk 2
strapped365 said:
See, this is what happens all across xda...someone doesn't research their issue or don't understand it, but they pursue it anyways. Pointless.
Wasn't seeking an argument, just dont like being "corrected" when valid info is given. If the user is to lazy to Google how to use fastboot... Well then that's his issues and can sit in bootloop land for all I care. You can only help so many people before well....stuff becomes redundant. BTW the Nexus was the absolute easiest phone to root, so if the user can't even grasp that tint concept we will be holding their hand their entire stay in the community.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
If you thought I was correcting you, you're mistaken. I quoted your post because it was the most helpful and added to the solid information in it.
Should the OP be having this issue at all? No. But rather than berate him I chose to help. Hopefully this scare will be the impetus needed to cause him to learn and prevent these kinds of things in the future.
I have a client's Atnt galaxy s4 that will not boot up normally and will not boot into recovery also.
when i try to boot into recovery i get the blue lettering in the top left and it just sits there i have let it sit for sometime like that with no change.
this is not my first go around with flashing android devices so please even give me Dev only options if that is what you think will fix it. i feel bad because he just bought this phone 2 weeks ago and cant use it. not sure what the other guy that tried to root it did and neither does he so i am shooting in the dark so any help would be great.
I have tried flashing the stock Odin package with no luck.
Also tried Kies Firmware upgrade with no luck
Most of the custom recovery for this phone from what i read are not flashed threw odin anymore, but if i am wrong please link me and i will give it a shot.
Dose anyone have any ideas someone told me to use the .PIT file and re-partition the device and reflash the stock odin package. but i have had no luck locating the .pit file for the I337 galaxy S4 could anyone grab it from there phone and upload it for me or any ideas on how i could possibly fix this issue.
Thanks in advance
Since you already tried ODIN, why don't you try KIES.
I tried that allrdy just forgot to add it to the list updated first post
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
ok i will have him give it a try
and yes it goes into downloading mode with no issues at all.
if the os isnt hosed just download goomanager and install the recovery then download a touchwiz rom that has an extended reboot menu, you can then just boot into recovery from the OS.
C13v3r0n3 said:
if the os isnt hosed just download goomanager and install the recovery then download a touchwiz rom that has an extended reboot menu, you can then just boot into recovery from the OS.
Click to expand...
Click to collapse
The OS wont boot that is why we are having such a issue cause we have to get into the recovery to fix the phone
thanks thou
If you can get into download mode and odin it should wipe everything, it should work. Maybr its hardware?
Sent from my GT-I9505 using xda app-developers app
In addition to letting go of the power button after the vibrate, here are a couple of other things that appear to have worked for other forum members. I didn't discover any of these fixes, I just did a lot of reading and saw where others have had similar problems and found ways to solve them. That is what makes the XDA community great:
Uppercuticus said:
I've had this happen to me several times while playing around with flashing. Basically (without fail in my experience), hold power+volume up+home as you'd normally do until you see the booting recovery message and let go. It will do one of two things - boot into recovery- or - restart and vibrate-. If it restarts and vibrates, immediately hold power+volume up+home until the booting recovery message pops up again and let go. It should then boot into recovery and you shouldn't have trouble in subsequent attempts.
It took me a while to figure this out and I actually thought I had permanently bricked my phone as the phone wouldn't boot and I couldn't get into recovery. Hope this helps.
Click to expand...
Click to collapse
RiNo808 said:
Those trying to boot into recovery mode, dl quick reboot from the play store. That's what I use and it works great.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Just flash a different custom recovery tar in odin. If ur using CWM, then flash TWRP, or vice versa.
C13v3r0n3 said:
If you can get into download mode and odin it should wipe everything, it should work. Maybr its hardware?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
After using ODIN, make sure to do a software (factory reset) to get rid of any data and settings that stayed behind. The firmware packages that we have for Odin, do not wipe everything on their own.
C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Thanks - was having the same problem. At last somebody explains it properly. It worked.
(Why on earth is the script on the stock recovery screen so small. You need a microscope to read it. I am going to install CWM right away....)
Cheers LJ
S4 on veriozon only boots into download mood
Im having the same problem. I can ONLY get into download mood! Everytime I go and try to reboot all it does is vibrates. I was installing a rom before and it was installed fine then it says I lost my root and turned off. Now i can't turn my phone back on. I try to the NAND erase all but that does not work. Is my phone bricked? I have Verizon BTW. Could some body please help me ASAP!
Yankeetim92 said:
Im having the same problem. I can ONLY get into download mood! Everytime I go and try to reboot all it does is vibrates. I was installing a rom before and it was installed fine then it says I lost my root and turned off. Now i can't turn my phone back on. I try to the NAND erase all but that does not work. Is my phone bricked? I have Verizon BTW. Could some body please help me ASAP!
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=2316
any luck? im having the same problem after enabling the t-mobile aws bands on my i337. i could only get into odin mode, recovery boot sits there on end and i have no access to the phone settings. ive tried the odin with stock firmware but nothing.
xBeerdroiDx said:
http://forum.xda-developers.com/forumdisplay.php?f=2316
Click to expand...
Click to collapse
you are not playing fair sir...but a good one.
TheAxman said:
you are not playing fair sir...but a good one.
Click to expand...
Click to collapse
My unrooted s4 phone gets stuck with the blue colour legend Recovery booting with any mentioned method. I am unable to enter safe mode, any ideas? been surfing google for 6hrs with no proper answer. Thanks!!
C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Thanx bro, This is solve my problem.
Having allmost the same problem with my S4...
http://forum.xda-developers.com/showthread.php?t=2498285
continuation of SGH_1337 will not boot into recovery
norml said:
Just flash a different custom recovery tar in odin. If ur using CWM, then flash TWRP, or vice versa.
Click to expand...
Click to collapse
here are all the details;
Rooted ATT Galaxy S4 MK2 with Busybox. all went well until I tried to flash and boot into recovery. Installed ClockworkMod Recovery, tried to reboot into recovery...permission error. Installed Team Win Recovery, same problem.
investigated... Superuser.apk for some reason is NOT present in app directory. hmm. checked for root, have root.
installed ClockworkMod Superuser from play store... asks to update superuser... fails with signature error.
There seems to be no way to flash this phone. I have the original backup I made with ClockworkMod but restore fails with signature error.
The phone works fine, has root but I am concerned I will not be able to update to 4.4 when it's available. I am also NOT able to flash any alternative ROM. frustrating.
I see there are relatives to this issue all over xda but as far as I can tell after a weekend of trying is there's NO WAY to boot into recovery with write permissions being allowed.
I was trying to unlock my Nexus 10 with 4.4.2 through fastboot. First I booted into fastboot mode, and then issued the following command:
fastboot oem unlock
I saw on the tablet the status showed 'unlocked'. After that I just pushed the power button to try to reboot, but it keeps spinning. Even if I pushed the power button again, spinning remains. And I can't shut it down either. Is it hard bricked? What should I do now? Should I have waited for the tablet to reboot itself?
mj56gt said:
I was trying to unlock my Nexus 10 with 4.4.2 through fastboot. First I booted into fastboot mode, and then issued the following command:
fastboot oem unlock
I saw on the tablet the status showed 'unlocked'. After that I just pushed the power button to try to reboot, but it keeps spinning. Even if I pushed the power button again, spinning remains. And I can't shut it down either. Is it hard bricked? What should I do now? Should I have waited for the tablet to reboot itself?
Click to expand...
Click to collapse
You should be fine. Hold down the power button and both volume buttons until it restarts into the bootloader. Go into the Recovery Mode. Then, you'll see the little android on his back with a red exclamation mark over him. Don't panic. You need to hit power + volume down at the same time (no need to hold). It may take a few tries, but when successful, you'll see the recovery menu pop up. Do a factory data wipe. Then, after it does it's thing. Select reboot system and you're good to go.
charesa39 said:
You should be fine. Hold down the power button and both volume buttons until it restarts into the bootloader. Go into the Recovery Mode. Then, you'll see the little android on his back with a red exclamation mark over him. Don't panic. You need to hit power + volume down at the same time (no need to hold). It may take a few tries, but when successful, you'll see the recovery menu pop up. Do a factory data wipe. Then, after it does it's thing. Select reboot system and you're good to go.
Click to expand...
Click to collapse
Thanks a lot! Those steps fixed the problem... I really appreciate your help!!!
mj56gt said:
Thanks a lot! Those steps fixed the problem... I really appreciate your help!!!
Click to expand...
Click to collapse
No problem. Same thing happened to me on my N10 (and also my Nexus 5). Has something to do with it not properly wiping/formatting the data partition after unlock like it's supposed to, so you have to do it manually.
It was quite a scary experience for me! Thanks again for the kind help...
Also I just flashed TWRP 2.7.0.1, and then flashed SuperSU-v1.80 in TWRP. It said successful, but both Root Checker and Busybox indicate that it's not rooted. What did I do it wrong?
mj56gt said:
It was quite a scary experience for me! Thanks again for the kind help...
Also I just flashed TWRP 2.7.0.1, and then flashed SuperSU-v1.80 in TWRP. It said successful, but both Root Checker and Busybox indicate that it's not rooted. What did I do it wrong?
Click to expand...
Click to collapse
Hmm. That's odd. Unfortunately, I don't use TWRP, so probably couldn't help much there as I prefer Philz Recovery. I do know that SuperSU v1.80 is a pretty old version (may be some compatibility issues with 4.4.2). Have you tried downloading and flashing the latest SuperSU in TWRP? I believe it's v1.94. I would try that first.
charesa39 said:
I do know that SuperSU v1.80 is a pretty old version (may be some compatibility issues with 4.4.2). Have you tried downloading and flashing the latest SuperSU in TWRP? I believe it's v1.94. I would try that first.
Click to expand...
Click to collapse
You're absolutely right. Previously when I googled SuperSU, it came out with the version 1.80 for some reason. This time I used Google Play, sure enough it installed v1.94! And everything looks good now!
You made my day! Thanks a lot...
Sent from my Nexus 10 using xda app-developers app
mj56gt said:
You're absolutely right. Previously when I googled SuperSU, it came out with the version 1.80 for some reason. This time I used Google Play, sure enough it installed v1.94! And everything looks good now!
You made my day! Thanks a lot...
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
No problem. I, too, am familiar with that feeling you get in the pit of your stomach when you start to think you just ruined your not-so-cheap toy. Just glad I could help you get through it. Regards.
Sent from my Nexus 7 using xda app-developers app