Related
I almost had a heart attack last night doing some kernel work. This is what happened, and how I got out of it.
I had just finished compiling a kernel I was working on and was excited to flash it and give it a run. So I built the boot.img and did
Code:
adb reboot bootloader
I got into the bootloader and
Code:
fastboot flash boot [B][I]boot.zip[/I][/B]
fastboot reboot
Working quickly, a got a little sloppy. Most unfortunately, I had a boot.zip in the same folder as the boot.img so boot.zip got flashed to the boot partition. Upon reboot, I got the usual splash screen but the upper left hand corner indicated I was in "RSD Mode 3". I pressed and held Vol up + power to get into bootloader but that was unresponsive. All I could do was press Vol Down + power which brought me back to the same state. I was unable to issue fastboot commands from here as well. This is what I did to fix it.
While I was in "RSD Mode 3" I did
Code:
fastboot flash boot boot.img
Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img. Finally, I did
Code:
fastboot reboot
and was back in the game.
Guys, I think the moral of the story is to slow down and be careful with fastboot. You can bet i'll be a little more careful
good post I'm sure this will help devs in the future
way to stay calm under pressure lol. good info.
Small world, I used to live in Fontana for 25 years and moved to NY couple of years ago Oh and thanks for the tip
Ran into this today, i had a similar, but different experience..hope this helps
Once i got into the RSD 3 mode, fastboot commands were basically dead...all i would get was <waiting for device>...
in order to get out, i had to hold BOTH VOL+ and VOL- and Power at the same time, then as soon as the screen turned off, I had to press VOL- and power at the same time to get to a 'regular' looking boot screen. I saw regular because there was no text at the top ofthe screen; however fastboot commands would work here. Because i FUBAR'd a kernel install, i just did
fastboot flash boot boot.img
fastboot reboot
and voila...it was alive again
a bit scary though
Ok, so I definitely know the heart attack feeling, and hopefully someone here can help me out. I got my Xoom today(wifi), and went looking for a root. I found a link to a root here that -said- it worked for both 3g and wifi models(found out later that it doesn't, obviously). So, I flashed the boot image, and came up with the RSD message. At that point all fastboot and adb capability was lost, and I can't seem to get it back.
Here's what happens with the following button combo's:
Hold Power+VolUp and release on screen-black: Motorola splash screen(dual core etc) with no text in corner
Hold Power+VolUp until after the splash comes up: splash with "Starting RSD protocol support 3"
Hold Power+VolUp and then hold VolDown immediatedly afterward: Splash screen with "Starting Fastboot protocol support."
Hold Power+VolUp and then VolDown after waiting a second: Splash screen with NvFlash/RSD/Fastboot menu
Hold Power+VolUp and then press VolUp again: Splash with "Starting RSD protocol support 3"
If I choose Fastboot from the menu, it just sits at the "starting fastboot protocol support".
If I choose RSD, it gives me the "starting RSD protocol support 3"
If I choose NvFlash, it says "entering nvFlash (something) and the screen immediately goes black and the notification led comes on (sits there until reboot)
No other button combinations seem to do anything. Holding Power+VolDown doesn't do anything from any mode, and Power+VolUp+VolDown acts just like Power+VolUp.
In any mode, I can't issue fastboot or adb commands. Fastboot simply says <waiting for device> for anything. I tried the advice above, to queue up a "good" boot.img (from here at xda), but it doesn't recognize it on a reboot from/to any mode I can get to. I've tried each about 20-30 times now, and I'm about ready to test the thing's shatter-resistance with my fist, so any help here would be -greatly- appreciated.
Quick update to previous post: Resolved!!
My advice? If you get stuck unable to fastboot or adb in linux, try it in windows. I hadn't booted into win for over a year, so it never occured to me until I saw someone mention it in the Tiamat thread. Even a fresh JDK/SDK install in Ubuntu didn't work for me. I didn't have any tools or SDK's installed in my winXP partition, but after a quick install, it worked first time, so now I'm the happy owner of a rooted Wifi Xoom with SD card.
Once again, the XDA forum saves the day. I love this place.
I recommend everyone keep a backup copy of their system.img around just in case too. I was going nuts after messing with my framework-res.apk file to get SMS working (for the verizon web account activiation message). I used root explorer, and BAM! crash, crash, FC, FC, then stuck at the moto logo at boot. I couldnt get it back with just a boot.img flash. I went for broke and found a post of the HI66 system.img. it was HUGE, dont know if thats what I needed. but flashed that and I was back in business as nothing else was working and couldnt get ADB to take to push the old framework-res.apk.
I have a similar issue. I have tried for over three hours now to understand why I cannot reboot into fastboot. It seems lika I have lost both fastboot and NVflash. Only RSD mode and a logo screen without text. Can't shut it down with powerbutton or factory reset. I tried to root it with a 3g boot.img whitch was terribly wrong on a wifi-only xoom and I'm now trying to flash a stock wifi boot.img. It just sits there on the M dual core screen.
What can I do from RSD mode 3?
EDIT: I have a feeling that it has freezed on that logo screen. I want to try a hard reset and the only way for me is to try to first shut it down then power it on again. Don't know if it helps but it is silly to be unable to stop it. How can I shut it down?
I've tried all the suggestions above with no luck
Will try a windows machines tonight to see if that will help, but I fear I will need to send my Xoom back to mfg for rework
may seem a stupid suggestion but what if you let the battery go dead. it will turn off. Then connect to power supply and do a fast boot restart, holding power button and vol down.
Just a thought!
I will try but I think I already tried that. It seems like boot and recovery is dead. I tried to flash the 3g .sbf file today. Thought that an already bricked tab couldn't be more bricked and perhaps it would restore the recovery or boot but RSD Lite couldn't do it. It's unvisible for a computer. I've tried both win7 and my Arch Linux box. The device is dead. Hopefully they wont have to replace the motherboard. I'm sending it for repair on Monday.
mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.
dogma444 said:
mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.
Click to expand...
Click to collapse
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock
orionshock said:
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock
Click to expand...
Click to collapse
Man that just sound to easy to work. ADB has no clue the device is.....wel, a device! Its like my xoom de-evolutionized to a primitive state and is suffering from tourrets. Anyway command typed in adb gives you back < waiting for device >. I've tried just about all the techniques here on the forums. And the people who claim to have been brought back to life are not victims of this "RSD mode 2" Im pretty sure this is like a failsafe if you blow up the original bootloader, 3. IDK though, pretty sure they are going to require some hardware replacements. Im not sure people are recognizing the degree of our bricks. These are what appear to be real BRICKS. no "soft" ness up in here. straight up cement
http://forum.xda-developers.com/showthread.php?t=1041192
adb wait-for-device && adb reboot recovery
tried this command and seemed pretty slick but, still nothing
Same thing here, was there any solution?
Give this a try:
http://forum.xda-developers.com/showthread.php?t=1079784
Please, I have same problem, but I can just reset it by pressing and holding Vol Up + Power On. When I press Vol Down + Power Down, nothing happens. If I press Vol Down when it restarts, it doesn't show me the message but shows the Motorola Dual Core logo and stops. Even in this situation I can't comunicate via usb. Now it just turn off when the battery is totally low.
I CAN boot into fastboot mode and issue fastboot commands from CMD. apparently mine is booting into RMD 3 mode or whatever it's called. when I boot normally (just hold down power button, I get the moto dual-core screen, and then it boots into the Clockwork Recovery Mod... PLEASE HELP
Moto G not boot, it just gets in the bootloader screen warning
I'm having the exact same issue, just flashed the latest stable version of CM11 (with gapps obviously) from dhacker's thread in CWM.
Coming from 4.3 with the US version t-mobile moto g.
Stuck on the bootloader unlocked screen.
I thought for a while it was just that the first loadup takes awhile but has been 10 minutes now and am figuring something bad happened.
ignore all the italics, I'm an idiot
Edit: 25 minutes in, have tried connecting the phone to computer and running command prompts to it like I did to get into recovery, device not recognized under cmd "adb devices" or "fastboot devices" when connected to computer
Phone screen goes black for about 0.8 seconds when power button is held down and immediately pops back up into warning bootloader unlocked screen, trying to go into fastboot or anything like with volume down and power button achieves the exact same effect.
Any help would be greatly appreciated.
Edit2: If I hold the power button and down volume for 20 seconds (just ignore when the screen goes black and hold it for 20 seconds) it will boot into fastboot mode
Recovery seems to do nothing but the device is now recognized by the mototool all in one, I will report back if I figure out anything more useful, I am hoping the mototool will save me
Edit3: tried flashing stock recovery, my phone now says in pink "hab check failed for recovery", tried flashing CWM recovery, it seemed to work. I then clicked "fix boot logo" it worked. The phone is now showing the motorola logo but doesn't seem to be doing much else, I'll let it sit for a couple minutes.
Edit4: If none of this works at least you'll have an interesting read about how to further destroy your phone
Tried rebooting to recovery, the mototool thinks it did it but my phone stays stuck at the motorola logo. I then told it to check connection and it now thinks there is no longer a device connected. Tried turning the phone off again, went immediately back to the motorola screen. I seem to be in the same situation except the bootlogo is no longer that ugly text. Back into fastboot mode, lets see what else we can do.
I checked to see if it was recognized by command prompts now and it IS, if you go back under like you were unlocking the bootloader and open up a cmd prompt and type "fastboot devices" it's recognized in this fastboot mode. This has given me new optimism, I'm feeling hopeful that my device is not destroyed, hopeful and very hungry, I will report back in after getting food.
Edit5: I've realized that I have no idea where to go from here, while I can access command prompts I have no idea what commands to put in, I tried hitting "factory" under the fastboot in hopes that it would flash my factory recovery, no such luck, I'm back to the same situation, tried hitting BP tools next because I didn't know what it was and thought it would be helpful, no such luck, back to the same screen, my quickly inflated confidence is now waning, I do have hope that someone can fix this issue but I am thinking that someone is not me.
I hit the recovery button, I'm sure I had done this before but this time it worked, went to restore from sd card, and restored my backup I made right before all these issues, it recovered my device, I then restarted it and everything is good now.
Apparently I am an idiot, but that's okay because my phone is working again now, after only about an hour or something.
TO FIX YOUR ISSUE HOLD DOWN VOLUME AND POWER AT THE SAME TIME FOR 20 SECONDS, IGNORE WHEN THE SCREEN GOES BLACK, KEEP HOLDING FOR ALL 20 SECONDS, CHOOSE RECOVERY, THEN GO BACK TO YOUR BACKUP THAT YOU SAVED BEFORE FLASHING A NEW ROM, RESTART THE DEVICE AND NOW THE DAY IS SAVED
Hello guys. This is the problem.
I made a bootloader unlock, did just great. Installed CWM 6.0.13, great too. But when I try to boot the phone just got stucked on Sony logo, and won´t pass from there. Sadly, I ran out of battery, so I searched the "fix low battery fastboot" bat, executed it, and the phone gives me this:
battery-voltage:
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
As you see, there is no value in battery-voltage (is that ok?). After the device is rebooted, gives me a red light led followed by a green light led and then nothing for a couple of seconds. The bat just get there in "waiting for device", and the phone just gives me that led colours. If I need to reboot into fastboot everytime, I press the vol + so I can get into fastboot, and repeat the process of the bat. Besides, charging the phone just doesn´t work. Just restart the logo and won`t do nothing. But what I discovered is that pressing POWER button and vol + while charging, it vibrates, turns on red light led, makes 3 more vibrates, and restart.
Any help possible? Tried EVERYTHING, wiping cache, factory reset, everything.
Thank you for reading, have a great day
EDIT:
After fighting with this phone for 4 days, found on Sony official website that I need to hold the reset button for 120 seconds AND NO MORE. After that, charged the phone for 4 hours aprox. There is no animation of charge, just the logo of Sony but it´s charging.
Installed the S1 drivers so the phone can be recognized by the pc in fastboot. Plugged in the phone in fastboot (hold vol + while connecting to pc until you see a blue led light), downloaded the stock rom for this model (D2305) and installed the rom via flashtool. Restarted the phone after the flashtool finished succesfully and VOILA! Xperia logo and booting like a newborn baby.
Already try to follow step in http://forum.xda-developers.com/showthread.php?t=2771449 ?
Nashville99 said:
Already try to follow step in http://forum.xda-developers.com/showthread.php?t=2771449 ?
Click to expand...
Click to collapse
Thank you for your reply.
Holded the reset button by 120 secs, charged battery for 4 hours and flashed stock rom via flashtool. Worked like a charm.
Your welcome,love to hear it..hit "thanks" if my post is useful
I've foolishly tried coming back down from NXT-L29C636B585 ending up on NXT-L29C636B330 after using the roll back update mid-way. I then tried the roll back update again to then flash to NXT-L29C636B211 and now my phone does nothing but show the boot logo and get hot - which in this weather I could live without!
Power+up does nothing, power+down does nothing, and power+up+down also does nothing. I don't have TWRP on, and adb/fastboot commands do nothing as it can't get to recovery. I can't even turn it off!
Is it now a paperweight? The only way to turn it off is to let the battery run down I think as holding power down just makes it restart.
Confirmed - it only turns off if the battery runs out. On giving it charge it then pops up with the logo screen again, and again none of the buttons combinations do anything other than restart it. I think my only option now is to send it off to Huawei. Does anyone have any ideas other than having to send it off?
Did you connect it to a PC before trying power + volume down? Was the reason it didn't work for me before.
Yeah, hold Power + Volume down after connecting it to your computer via USB and you should see go into fastboot mode.
arvin2212 said:
Yeah, hold Power + Volume down after connecting it to your computer via USB and you should see go into fastboot mode.
Click to expand...
Click to collapse
I'll give it a go when I get home! god I hope this works..
YES! FASTBOOT! Only issue now is i'm FRP unlocked, but PHONE locked.. I can use the tool to unlock the phone as I have my password from Huawei, but what then? use the tool to flash one of the recoveries?
Thanks for the advice so far - I was very nearly physically sick when i realised nothing worked..
Try unlocking the bootloader and flashing twrp
bootloader unlocked and I used the SRK tool to flash stock 4.1 so now getting messages about my phone not being secure. Next step I figure is build enough charge in it to try flashing B330 again assuming power + vol up/down is working
bootloader unlocked. twrp 3.0.3 flashed ok:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (23498 KB)...
OKAY [ 0.500s]
writing 'recovery'...
OKAY [ 0.330s]
finished. total time: 0.834s
However TWRP is nowhere to be found.. I just get the 'Your device has been unlocked' waffle and can't get to recovery still. Left the phone to fully discharge, and on inserting a mains lead to charge it for a while it then auto starts up and goes to the same screen - I try power&up and it just goes to the red charging 'lightning bolt' screen - then back to 'Your device' etc. I have no way of getting into TWRP!
I've been flashing Samsung phones for years and I can't remember ever getting this infuriated on a flash procedure..
I think I may have to do everything through fastboot as that's the only screen I can get to - but the only thing I can alter which seems to make a visible change is locking or unlocking the bootloader.
Should I re-lock with TWRP supposedly on? I have tried, and all I get is the 'not enough charge' screen - regardless of how long it is left untouched on power. It's as if all the charge I am putting in is just going to heating up the back and showing me the flipping message - then it runs low enough on charge to blank the screen, reboot and then end up with the unlock screen.
All I want to do is hold down all the buttons and have it install B211 - B330 - B'anything' from the dload folder on the sdcard I have in there. If anyone could tell me what to do to get to that point i'd be super happy. Failing that is there a way to fastboot flash a rom file?
Make sure to unplug the usb cable in order to get to TWRP.
malekowsky said:
Make sure to unplug the usb cable in order to get to TWRP.
Click to expand...
Click to collapse
At the moment i'm just struggling to get back to stock let alone a custom rom! If I ever get back to working phone in any way i'll be happy..
I've extracted out the boot, recovery and system from B330 and flashed them all through fastboot then re-locked the bootloader. It is still starting up with the Huawei logo as if booting up, and stays at that screen - It eventually then goes blank, pops up with the red circle with red charge pic in it, then after a while the Huawei logo reappears. I am essentially no further forward.
The more I flash things the more it pays no attention to me and sits on my work desk doing nothing.
I'm wondering if - in my epic screw-up - I managed to somehow destroy some part of the OS that governs charging, as it refuses to hold a charge while plugged in to the pc, powerbank or mains lead. At least thats what it is showing me.. It stayed powered long enough for me to fastboot flash the system.img, but that is when on the pc usb connection.
When I lock/unlock the bootloader through the SRK tool it finishes with the 'choose lock or unlock then press power' option which then promises a system reset.. and then it turns off with the red power screen. I can flash TWRP but because it is seeming not to hold a charge, I cannot then get into it without cables attached as it just boots back to the red charge screen.
Is there another file from the update.app I need to flash? should I just flash every single image and hope for the best? I really felt I was getting somewhere this afternoon..
Have you tried what I posted to you on?
https://forum.xda-developers.com/showthread.php?p=72758529#post72758529
Don Kronos said:
Have you tried what I posted to you on?
https://forum.xda-developers.com/showthread.php?p=72758529#post72758529
Click to expand...
Click to collapse
I plan to in the morning at work!
SOLVED: Phew - problem solved! see https://forum.xda-developers.com/mate-8/general/best-c636-rom-battery-life-t3623313#post72775720
Don Kronos said:
Have you tried what I posted to you on?
https://forum.xda-developers.com/showthread.php?p=72758529#post72758529
Click to expand...
Click to collapse
Hey,
I unbricked my phone using the same method - thanks for mentioning it! But sadly I'm stuck again. Maybe you have a hint for me?
Patneu said:
Hey,
I unbricked my phone using the same method - thanks for mentioning it! But sadly I'm stuck again. Maybe you have a hint for me?
Click to expand...
Click to collapse
Replied on that post! Probly not that useful though..
WINDOWS 10 TERMINAL:
Desktop\7pro> fastboot devices
d###### fastboot
***TRIED FLASHING twrp-3.3.1-74-guacamole-unified-Pie-mauronofrio
Desktop\7pro> fastboot flash recovery twrp-3.3.1-24.img
target reported max download size of 805306368 bytes
sending 'recovery' (30752 KB)...
OKAY [ 0.668s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.685s
My Device is GM1915
I understand GM1915 is a "branded phone" but maybe the same as a GM1917
i tried using FLASH-ALL.bat from the following zip file:
10.0.3-GLOBAL-OnePlus7ProOxygen_21.O.23_OTA-023_all_1912032357_76b445-FASTBOOT
everything seems to be working but the end result puts me in
QUALCOMM CrashDump Mode
dm-verify device corrupted Force Dump
kernel_restart
(because the phone was instructed to restart. If i try to 'start' phone from fastboot i'm taken to CrashDump Mode)
using MSMDownloadTool
when i can finally get the tool to recognize my phone.
a grew bar grew for 6 seconds.. .then "waiting on phone" status
i need to follow someone's steps and give a result
nothing seems to work
It's tricky to connect. Volume up & down + power.. then plug in to phone Keep trying. It may take many attempts before it connects. You're not doing anything wrong. It's tricky
csmooth2001 said:
WINDOWS 10 TERMINAL:
Desktop\7pro> fastboot devices
d###### fastboot
***TRIED FLASHING twrp-3.3.1-74-guacamole-unified-Pie-mauronofrio
Desktop\7pro> fastboot flash recovery twrp-3.3.1-24.img
target reported max download size of 805306368 bytes
sending 'recovery' (30752 KB)...
OKAY [ 0.668s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.685s
My Device is GM1915
I understand GM1915 is a "branded phone" but maybe the same as a GM1917
i tried using FLASH-ALL.bat from the following zip file:
10.0.3-GLOBAL-OnePlus7ProOxygen_21.O.23_OTA-023_all_1912032357_76b445-FASTBOOT
everything seems to be working but the end result puts me in
QUALCOMM CrashDump Mode
dm-verify device corrupted Force Dump
kernel_restart
(because the phone was instructed to restart. If i try to 'start' phone from fastboot i'm taken to CrashDump Mode)
using MSMDownloadTool
when i can finally get the tool to recognize my phone.
a grew bar grew for 6 seconds.. .then "waiting on phone" status
i need to follow someone's steps and give a result
nothing seems to work
Click to expand...
Click to collapse
tool all in one
joeygee23 said:
It's tricky to connect. Volume up & down + power.. then plug in to phone Keep trying. It may take many attempts before it connects. You're not doing anything wrong. It's tricky
Click to expand...
Click to collapse
trying "TOOL ALL IN ONE", for the first time it is recognizing my phone..
but still no luck.... tried flashing twrp but "TAIO" software was waiting for phone to reboot in twrp..
which of course didnt happen..
not sure what else i can do with "tool all in one"
joeygee23 said:
It's tricky to connect. Volume up & down + power.. then plug in to phone Keep trying. It may take many attempts before it connects. You're not doing anything wrong. It's tricky
Click to expand...
Click to collapse
you're right it is tricky
i started MSMDOWNLOADTOOL
with phone off... (i know phone was off cuz i selected phone off in the fastboot mode that i've been looping in)
with phone off, i pressed volume up + volume down (w/o power button) counted to like 4 and a half then plugged in usb cord on phone side (cord already plugged in pc on usb side)
one of the COM ports in the msmdownload software is now connected
i clicked start and now a bunch of downloading to phone is happening
this is the most that has happened with my phone in a week.
it was after trying stuff on the TOOL ALL IN ONE SOFTWARE....
ugh all this software has me wanting to REinstall windows..
(prolly spyware.. dont mind me im suspicious of everything)
OMG phone just booted.... case closed (ugh, until i brick it again... fingers crossed)