Database Users

Help me please

So I've been messing around with android phones for a while now and I'm stuck. I was on the oxygen 2.1.6 Rom then decided to make a back up. However instead of going into CWR it just went into fast boot. When I go into recovery it just says fast boot mode no reboot or recovery img. I tried to odin back to stock like I usually do but adb wont recognize my device like it usually does. Please don't tell me I'm bricked and that I messed up bad. Any help would be appreciated. Thanks in advance.
I tried reinstalling drivers etc etc. Somebody help me lol

futuralabs87 said:
So I've been messing around with android phones for a while now and I'm stuck. I was on the oxygen 2.1.6 Rom then decided to make a back up. However instead of going into CWR it just went into fast boot. When I go into recovery it just says fast boot mode no reboot or recovery img. I tried to odin back to stock like I usually do but adb wont recognize my device like it usually does. Please don't tell me I'm bricked and that I messed up bad. Any help would be appreciated. Thanks in advance.
I tried reinstalling drivers etc etc. Somebody help me lol
Click to expand...
Click to collapse
It sounds like you flashed a bad recovery. Download a new recovery , boot into fastboot, and
Code:
fastboot flash recovery yourrecoveryfile.img

adb wont recognize my device so how do I flash a new recovery

futuralabs87 said:
adb wont recognize my device so how do I flash a new recovery
Click to expand...
Click to collapse
Adb only works when the phone is booted normally, provided usb debugging is on.
Use fastboot. If you want to make sure it's working, boot into fastboot mode and
Code:
fastboot devices
If it's working, you will see your serial number.

If the other options can't help you get your problem solved try Odin.
www.samfirmware.com
get the right files for your device and Odin program itself. There are tutorials on here how to use it.

sorry I was being an idiot. I tried fastboot and it showed nothing connected. When I flashed a recovery it just hung waiting for device. I have all the drivers loaded on the computer but my device is still unknown and wont be recognized. I have all the odin files and I have used odin before. This sucks

btw appreciate the help guys

futuralabs87 said:
btw appreciate the help guys
Click to expand...
Click to collapse
Try installing pdanet, that will install all the drivers you need for fastboot and Odin.
Sent from my Nexus S using XDA Premium App

Have you tried to run shabbys 1 click root to get the recovery in place? Assuming your on sprint that is
Sent from my Nexus S 4G using Tapatalk

dreamsforgotten said:
Have you tried to run shabbys 1 click root to get the recovery in place? Assuming your on sprint that is
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot

shabbypenguin said:
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot
Click to expand...
Click to collapse
Sorry I didn't say anything, it was a burp
Sent from my Nexus S 4G using Tapatalk

shabbypenguin said:
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot
Click to expand...
Click to collapse
Maybe not, but it does include some handy files. ;-)
Download and unzip Shabby's OneClickRoot
Install pdanet. (See the readme for which one.)
Reboot your computer.
Then try using his version of fastboot.
I'm assuming you are in fastboot mode (it will say so) and that you're using the usb cable that came with the phone.

I will give it a go now I do have PDA installed too

No luck boys just bought a sensation but still wanna fix my nexus s
Sent from my HTC Sensation 4G using XDA Premium App

HELP! I think I bricked my nexus 7. [SOLVED]

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

AT&T Galaxy S4 Wont Boot into Recovery

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.

[Q] Factory Reset from Fastboot

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

[Q] LG G2 Bricked! PLEASE HELP!!!

i have the VZW G2 (VS-980) and its stuck in fastboot mode. ive tried all the different methods listed in these forums and nothing has worked. i cant get into download mode as everytime i try, download mode shows for a second then goes into fastboot mode again. PLEASE HELP!!

simon_lefisch said:
i have the VZW G2 (VS-980) and its stuck in fastboot mode. ive tried all the different methods listed in these forums and nothing has worked. i cant get into download mode as everytime i try, download mode shows for a second then goes into fastboot mode again. PLEASE HELP!!
Click to expand...
Click to collapse
How the hell did you brick it? Give us some more background on what tweaks, root methods, flashing recovery methods did you use or else its hard to diagnose the issue.

ericdabbs said:
How the hell did you brick it? Give us some more background on what tweaks, root methods, flashing recovery methods did you use or else its hard to diagnose the issue.
Click to expand...
Click to collapse
ok. i was on stock. rooted with the IO method. wanted to flash a ROM (clean rom). downloaded ROM, wipe dalvik/cache/data. after reboot, phone booted into recovery mode. tried going into download mode to revert back to stock and LG FlashTool failed. said phone was the wrong model number (D802). the ROM i Downloaded said it was for VZW G2. obviously it wasnt. so i finally ended up using fastboot to push boot image and it booted, but in about phone, it says it D802 model (i just got it to boot, where as before i was stuck in fastboot mode). now i need to return to stock, but dont know how. any ideas?

Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517649&highlight=bricked

Gnarfsan said:
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517649&highlight=bricked
Click to expand...
Click to collapse
well, i actually was able to restore a backup i had of my stock rom and that fixed the model number prob, however now i cant get into download mode so i can do a reflash :/

simon_lefisch said:
well, i actually was able to restore a backup i had of my stock rom and that fixed the model number prob, however now i cant get into download mode so i can do a reflash :/
Click to expand...
Click to collapse
Even following the steps posted in that thread?

Gnarfsan said:
Even following the steps posted in that thread?
Click to expand...
Click to collapse
yes. not sure why its doing that. is there any way that download mode can be deleted from the phone? also, how do you get into fastboot mode?
EDIT: nevermind. i finally got it into download mode!! (thank god!!) flashing right now. damn that was a pain in the ass. i was starting to freak out that i messed up my phone. this is my first LG phone so this process is a little new to me (been on moto for the last few years) thanks for trying to help me out. this was def a learning experience.

Phew, I'm glad to hear that. Some day I will be in the same situation
Sent from my LG-D802 using XDA Premium 4 mobile app

Just a quick question. Why would you even need to go into download mode to flash a Rom? Never once have I done that. Really, just curious.
Thanks Devs. From my VZW G2.

trickster2369 said:
Just a quick question. Why would you even need to go into download mode to flash a Rom? Never once have I done that. Really, just curious.
Thanks Devs. From my VZW G2.
Click to expand...
Click to collapse
I was thinking the same thing. It's best to stay out of those modes. Get a recovery installed ASAP and do everything that you need to do from there. I recommend TWRP Recovery.
Sent from my LG-D802 using XDA Premium 4 mobile app

Maybe because when flashing stock rom download mode is needed (atleast in my old sammy phone, maybe same in moto phones)

What's wrong with restoring the backup of the stock rom that should have been made before wiping and flashing a different rom? Not sure what I'm missing here.
Sent from my Nexus 10 using XDA Premium HD app

Download mode is useful to flash the entire phone back to stock using the OEM tools. It's not just for the stock ROM. It's everything. It's useful if you get a bit carried away in TWRP and wipe partitions you really shouldn't be touching. Or if you somehow manage to bork your recovery, or at least can't get into it. It's also good if you want your phone to be completely stock to sell it or to send it in on warranty. I'm sure someone could come up with other scenarios where it's useful.
But yes, it is a good idea to keep a backup of your stock ROM. And as always, know what you're flashing, make sure it's for your phone and check md5s. And be mindful of what you're doing in recovery. You should be able to avoid most issues. Download mode is indeed something you shouldn't be using often but as I said above there are situations where it is useful or necessary. It's actually something I suggest you know how to use. I say it's always a good idea to know how to get back to complete stock for warranty stuff, selling, or if something just goes majorly wrong.

The Rom I was trying to flash was apparently for a different model number, yet it was under the Verizon thread. There was no md5 to cross reference. In the end I ended up finding the proper boot image/twrp files and pushed them via fastboot (since I was unable to use adb) which then allowed more to restore a backup of the original Rom. Just took me all night to finally get back to stock. Then I decided to restore to out-of-the-box stock just to make sure all files weren't corrupted our anything.
Sent from my VS980 4G using Tapatalk

Not for nothing, but I ran the LG flash tool without putting the phone in download mode and it worked fine.

Semantics said:
Not for nothing, but I ran the LG flash tool without putting the phone in download mode and it worked fine.
Click to expand...
Click to collapse
Hmm.....interesting. I may try that next time I have to flash to stock.
Sent from my VS980 4G using Tapatalk

Same Problem
simon_lefisch said:
The Rom I was trying to flash was apparently for a different model number, yet it was under the Verizon thread. There was no md5 to cross reference. In the end I ended up finding the proper boot image/twrp files and pushed them via fastboot (since I was unable to use adb) which then allowed more to restore a backup of the original Rom. Just took me all night to finally get back to stock. Then I decided to restore to out-of-the-box stock just to make sure all files weren't corrupted our anything.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Can you fill me in on how you used fastboot to install twrp? I am in the same boat right now...

i'm stuck as well in Fastboot and can't figure it out

emmur0 said:
i'm stuck as well in Fastboot and can't figure it out
Click to expand...
Click to collapse
I sent you a pm

You can you adb side load which is the same for flashing rom, pushing, or pulling file from the phone which is the first thing to learn before flashing anything to the new device that you got and know nothing about.
Sent from my LG-LS980 using xda premium