Anyone know how to do it or some work around? It has the last OTA update and I have sbf'd it several times now. using rsd lite and the linux boot cd.
The problem is the phone does not boot past the M logo and the hardware home key was not working when it was booting normally.
I believe the only thing keeping it from booting now is the inability to enter the recovery and wipe the data.
I read there is a way to boot to recovery sending commands to the phone but can this be done in bootloader? Its the only thing i can get into besides the M logo.
Is it rooted?
Sent from my SCH-I605 using xda premium
Related
Help. I accidently my girlfriend's mom's phone.
Unable to boot into recovery.
The phone has been running the first Pre-Rooted DX GB Leak for a while now, and still works great, but when I went to load the latest leak I had some trouble. Rom Manager wont boot into recovery (it just reboots the phone). When I try to manually get into recovery by holding the home button, I get stuck at the Android "!" screen; pushing the search button at this point does nothing.
Does anyone know where I went wrong? I've tried re-flashing Clockworkmod several times, and also DX Bootstrap. No luck.
What do?
Follow this..... http://www.droidxforums.com/forum/g...ing-gingerbread-help-please-3.html#post289033
you need droid 2 bootstrap, or turn off usb debugging.
To get menu in stock recovery in gb you hold volume up+vokume down... U need d2bootstrap to access cwm on gingerbread
Sent from my DROIDX using XDA App
Hello, I rooted my phone using the instructions on this site and flashed Liberty 1.5 onto my Droid X. When I rebooted through the bootstrap my phone has been stuck at the Liberty boot animation screen. Is there any way to recover my backup if I can't actually get into my phone? I think I might be out of luck.
Are you able to boot into cwm? Try booting while plugged into a charger and/or booting while holding volume down.
If not, you will have to sbf. This has a bad rep but is actually very easy and I have never had any issues with it.
I've been running on Apex 2.0 for about a month without issue. Last night the phone locked up and would not respond to any key press so I pulled the battery. Since then, powering on the phone stalls at the white motorola logo endlessly. I've tried SBF by way of RSDlite and the linux cd method, note that I've SBF'd many times before and have never run into an issue. Holding Home and powering on does not bring up recovery, with or without SD card. Swapped with a fully charged battery with no additional luck. Any more ideas?
NerdInTheNW said:
I've been running on Apex 2.0 for about a month without issue. Last night the phone locked up and would not respond to any key press so I pulled the battery. Since then, powering on the phone stalls at the white motorola logo endlessly. I've tried SBF by way of RSDlite and the linux cd method, note that I've SBF'd many times before and have never run into an issue. Holding Home and powering on does not bring up recovery, with or without SD card. Swapped with a fully charged battery with no additional luck. Any more ideas?
Click to expand...
Click to collapse
You have tried to get to the bootloader right? As long as you can get to the bootloader you are good to go.
Sent from my DROIDX using XDA Premium App
scottyd035ntknow said:
You have tried to get to the bootloader right? As long as you can get to the bootloader you are good to go.
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
Yes, I can access the bootloader. I've used both the 2.3.340 and 4.5.596 full sbf files with no change. The logo does alter between White and Red depending on the sbf flashed so I know they were successful.
while in the boot loader you wiped everything right?
m16-maniac said:
while in the boot loader you wiped everything right?
Click to expand...
Click to collapse
are you thinking of recovery? If so, that is not accessible in the current state.
Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.
Hyflex said:
Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.
Click to expand...
Click to collapse
Reboot holding Power and both volume buttons and you should be able to get to recovery
brees75 said:
Reboot holding Power and both volume buttons and you should be able to get to recovery
Click to expand...
Click to collapse
I'm on the xda-devs irc at the moment and we've got so far... but still its messed up.
- Recovery is dead (can't get into it atm, orange triangle guy every time)
- Flashed stock via fastboot and unrooted, but on reboot I get the triangle guy.
- I can boot into unsecure roms (temporary)
- I can boot into temporary recoverys, clearing cache works but davlik cache and factory reset doesn't work both say "failed"
I'm currently awaiting the guy whos been helping me get back from the shops.
From what I remember you need to either install something or run a command after "oem unlock" for security reasons. Android wont let you boot back into the OS until you have wiped all the data after the unlock.
The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD
Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!
altimax98 said:
The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
The pressing 3 buttons at once; cycling to recovery... method wasnt working because there was no recovery accessable what so ever and temporary recoveries weren't working.
That's what a few guys in IRC said too about the toolkits haha
Thankfully some guy by the name of YellowGTO spent some time helping me out and we finally got there in the end, he's awesome and extremely patient
jlvlawrence said:
Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!
Click to expand...
Click to collapse
Okay, updates for everyone just incase someone else gets the problem.
- Factory Images via fastboot flashed fine but never stuck, just kept returning me to triangle dude.
- Fix permissions, did nothing
- Restoring stock recovery did nothing, I still couldn't get to a recovery.
- Temporary recoveries only had limited functionality.
I decided to unlock an already unlocked phone again
I flashed stock, Ran file permissions
Used the temporary recovery to clear the cache/davlik (previously didn't work)
I re-rooted, Installed TWRP 2.4.4.0, this finally stuck.
I double checked that it had stuck by booting the system, rebooting into recovery, powering device of and powering it on to Android. It was all working perfectly.
I then made my backup and put a custom rom and kernel on, it's working lovely now.
It seems that somewhere during the oem unlock it messed up some partitions or something resulting in recoveries and flashing not to work/stick.
Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That's the thing, the recovery wasn't available in any way shape or form and temporary recoveries wouldn't wipe the cache... the oem unlock went wrong somehow even though it had full power, wasn't interrupted or anything.
I'm glad it's all working now, I thought the device was completely dead at one stage.
I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well
anazei said:
I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well
Click to expand...
Click to collapse
I think you are right and that was his problem..... The toolkit actually told him how to handle this ... but who reads all the that text anyway
Was on 4.1.2 OTA (yeah I know dumb of me, but it did it overnight), rooted with TWRP all was fine untill I decided to power cycle and got stuck in a boot loop...
Booted to twrp...tried to recover from a back up, still boot loop....Cleared dalvik and all other caches, Still bootloop....factory reset, still no change...
Last resort was to flash using RSDlite v6.1.5 to VRZ_XT907_9.8.1Q-78-1_1FF.xml ...and i'm still bootlooping!!:crying: Now I've lost root, NO Custom recovery with a locked bootloader. I can't push anything through adb cuz bootlloop interrupts windows recognizing the phone and the drivers don't properly install while in Stock Recovery (I do have the latest drivers BTW)...and only sees it as 'MOT SINGLE ADB INTERFACE' while in fastboot.
Question is, what could still be causing it to bootloop?? Anyone know?.. and is there any way to get this fixed and/or get back root and a custom recovery??
At the end of my rope here! Need some guidance....
Alright Guys and Gals I solved the issue (even though I'm not sure how! LOL)
What I did (with simplified instructions)
1. Let it bootloop till the battery ran down...
2. recharged it up to 100%
3. opened it up while still off
4. disconnected battery cable for 5 secs
5. reconnected battery cable
6. started into boot menu (hold POWER and VOL UP & VOL DOWN together) and chose recovery (VOL DOWN to highlight recovery and VOL UP to select it)
7. While in recovery Hold VOL DOWN and tap VOL UP to get the Recovery Menu
8. Chose wipe cache ( VOL buttons to highlight, Power Button to select)
9. then chose wipe data/factory reset
10. rebooted into boot menu again
11. chose Factory option
*12. Held my breath :fingers-crossed:*
AND IT BOOTED!!!:laugh:
Now just to be clear I am not even sure if it was one of these steps or the combination of all of them that got me off the Boot Loop, but I just thought I'd outline them just in case someone stumbles on the same problem I had. Also please note that all this was after I fastboot flashed the 4.1.2 (.78) firmware using RSDLite v6.1.5
Being stuck on on 4.1.2 (.78) Stock is alot better than being stuck in a Boot Loop at least, so I'm happy!
P.S: F.Y.I... I was getting stuck halfway through the boot animation (just about where the droid eye kinda thing closes up) so I could still recharge my Battery from a powered off state (why I had to let it run down to zero, as it was either that or open it up and manually disconnect the battery cable and I was feeling lazy.
Now I have another Logic Board which doesn't boot past the initial Motorola "M" Logo, and thus can't get into recovery or even charge from a powered down state (can only get into fastboot) even though I've successfully flash 4.1.1 to it TWICE!!
meaty0025 said:
Now I have another Logic Board which doesn't boot past the initial Motorola "M" Logo, and thus can't get into recovery or even charge from a powered down state (can only get into fastboot) even though I've successfully flash 4.1.1 to it TWICE!!
Click to expand...
Click to collapse
Do you know what build that logic board is... if its an older version use Matt's utility on it simply swap with your current one and have the joy of an unlocked device... first time I flashed (well almost every time I flash) 4.3 I get stuck on the boot logo and have to use Matt's utility to bring it to life again....
Sent from my XT907 using xda app-developers app
ezknives said:
Do you know what build that logic board is... if its an older version use Matt's utility on it simply swap with your current one and have the joy of an unlocked device... first time I flashed (well almost every time I flash) 4.3 I get stuck on the boot logo and have to use Matt's utility to bring it to life again....
Click to expand...
Click to collapse
That was my initial thought but, Where on the board can I find that info? and doesn't matt's utility in essence perform a fastboot flash, same as RSDlite?? Would love to have an unlocked device or at the very least a working back up board in case of unforeseen accidents, but this one has me stumped...
It won't say it on the board you'll have to install it to the housing n digitizer n get it to boot... I think you can tell by the fast boot menu but I'm not sure what to look for.... n to be honest I have never used rsd I've always used one of Matt's utilities for all my moto devices he has saved several of my phones...
Sent from my XT907 using xda app-developers app
ezknives said:
It won't say it on the board you'll have to install it to the housing n digitizer n get it to boot... I think you can tell by the fast boot menu but I'm not sure what to look for.... n to be honest I have never used rsd I've always used one of Matt's utilities for all my moto devices he has saved several of my phones...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Utility doesnt seem to work for me for some reason, it just closes when i "hit any key to continue" even flashed it with rsd using the xml from matt's ultilty... Still no go.
It should be an older board though, i bought off ebay with a broken screen just mainly so i could get the pristine back housing off of it (lol) ... and that was in february.
The guy did say he'd dropped a wrench on it breaking the screen while workin on his car, guess it was a bigger wrench than i thought and it damaged the board too :laugh: