Okay, nobody say I told you so here - I was doing some reverse engineering on a ROM and wrecked it, so I went and used the LG Flash Tool to reflash the KDZ file.
This then crashed half way through, and seems to have deleted my recovery and everything. I've opened her up and disconnected the battery, then tried to turn it back on, and it can boot into recovery... sort of. It asks if I want to do a wipe, I say yes, and it suddenly boots to fastboot. Or, anything else I do, fastboot.
[EDIT] My previous problems are gone now, to be replaced by new, weird ones. Fastboot picks up my phone, and executes commands. For example, fastboot erase recovery shows on my phone as "fastboot: erase:recovery", as it should. My issue, is that it won't stop doing that. It's stuck. I have to unplug it and plug it back in to try any command, and they all freeze. fastboot reboot just shows "fastboot: reboot" on my phone, but stays on. Heeeeeelllppp!
Er, I replied instead of editing, sorry.
Related
Can't find an example of this happening to anyone else, but it seems to be a difficult problem to search for since any possible fix appears to require that the problem I'm having not exist.
Basics: bootloader is unlocked, but otherwise everything is stock, NOT rooted.
Had a hard lockup a couple of days ago and any attempt to reboot would just get stuck at the Google logo. Even waiting for over an hour, it just wouldn't move on. Went into the bootloader, which was also acting weird, hanging up and just not working properly. A search indicated that the best thing to do is just grab the factory images from Google and use fastboot to re-flash the bootloader image (checksum was verified before I attempted to flash). That process went ok and "fastboot reboot-bootloader" sent to a nice and properly working bootloader. I used fastboot again to load up TWRP (via the "boot" command) to do a backup, and then rebooted back into the bootloader from TWRP. At this point it went fubar.
The screen will show just the up and down arrows for a couple of seconds, then the entire screen goes grey. Neither fastboot nor adb will see the tablet when in the bootloader and my only option seems to be to just hold the power button down and force a restart.
Luckily the original problem did get fixed with this process and it boots up fine now and works perfectly otherwise. adb does work fine when not in the bootloader, and I can use adb to restart into recovery which also works fine. It's just that the bootloader gives me nothing usable.
I'm not going to try and RMA for something that was obviously my fault, and the tablet works fine now except for the bootloader, but I'm sure that I'll want/need it fixed at some point. Does anyone have any suggestions for attempting to fix this, or am I just screwed?
Hey all, I figured it was time to make a post and see if anyone could help figure out what I'm missing.
So I recently got my G2 and rooted it, then I installed Team Win Recovery Mod (on accident, actually. Was intending to install Clockwork, but figured it wouldn't hurt anything and it was working fine). Anyway, moved on to install Cyanogen Mod and gapps following the usual factory reset -> flash from /sdcard/ approach. Unfortunately on reboot, it went into fastboot mode.
Since then I've read a ton of stuff about fastboot, and I've reflashed recovery, boot, and system a dozen times, but I'm still stuck in fastboot mode. I've grabbed the CWM for LG G2 (AT&T) from http://www.clockworkmod.com/rommanager and the latest stable Cyanogen Mod from http://wiki.cyanogenmod.org/w/D802_Info. Sadly everything I've seen just tells me to do what I did - reflash recovery and tell it to reboot. I've also tried the "volume down + power until logo, then release and re-hit" method of getting into recovery mode, but the logo is present for literally less than a second, so I just end up back in fastboot.
Perhaps I need to find an flash a stock OS first? The thread on returning to stock firmware scares me :/ http://forum.xda-developers.com/showthread.php?t=2432476 Edit: I gave in and tried playing with this anyway. No good, I can't get the phone to enter "download mode", no matter what I do, it reboots into fastboot.
Any ideas?
Edit: The flash method I used for TWRM: http://forum.xda-developers.com/showthread.php?t=2449670
Edit2: This seems possibly relevant. When I do "fastboot devices", I get "? fastboot". So something is wonky in terms of its detection. But all the commands seem to be getting executed fine...
Edit3: Finally a potentially useful piece of info: If I flash the boot image extracted from the Cyanogen mod zip, then run "fastboot continue" I get "ERROR: Getting device tree address failed". Which is the same message I get when trying to remotely run a boot image without flashing it. Possibly related to the "?" in the "fastboot devices" listing above? I switched to Koush's Universal Adb Drivers, but no change.
Pretty please?
I find it hard to believe I could manage to brick a 2 week old phone just by following the guides posted here
Well, I still have no clue what went wrong, but I was finally able to make use of the reset to stock thread. It was strange and scary and at no point did I really have any idea I was hitting the right buttons, and at the end it said it failed... BUT it rebooted me into a fresh install, apparently even unrooted! My problems along the way appear to have entirely been related to actually getting the phone *into* download mode since I couldn't get it to actually turn off. Once it ran itself out of battery and turned off, I was able to enter download mode while reconnecting it to power.
No to decide if I want to try installing a custom ROM again, or take this as a sign...
Who am I kidding. *re-roots phone and pulls up the mod threads*
So I think my Nexus 6P is hard bricked, but I just want to be sure before I issue an RMA.
I was on a plane flying over the Pyrenees and opened the camera to take a picture. The phone froze and started rebooting, which I found strange really strange as it never happened before. Since then, it wasn't able to boot again. The phone is completely stock, running 7.0, apart from the unlocked bootloader that I had unlocked the day I bought it (March/April this year). The phone shows the unlocked bootloader warning, goes to the white Google logo with the padlock below, and then goes back to the unlocked bootloader.
From here I can Power + Vol down and get to bootloader, which I thought would leave me to recover the phone somehow. I know my way around nexus devices so the first thing I tried was scrolling in the bootloader menu and boot into stock recovery. No luck, unlocked bootloader warning, white Google logo and loop. Tried "Factory" in the menu and the same thing happens.
So then I've gained access to a computer and tried downloading a twrp recovery and boot into it. Ran fastboot boot twrp.img, the phone tries to boot again, and the same thing happens. Boot loop. After that, I've downloaded the latest stock Google images and I've run a different set of things, all with no luck. Booting directly from fastboot into stock recovery doesn't work. Flashing stock recovery and trying to enter stock recovery via bootloader menu doesn't work. I've erased and flashed bootloader, radio, and all other partitions (system, boot, recovery, vendor and cache), without any luck. The fastboot commands return "OKAY" but it seems like it's doing nothing.
I am out of ideas, I always thought I would be able to recover a Nexus phone as long as I could reach bootloader mode, but I guess I'm wrong. Should I RMA, or is there anything else I should try?
Thank you.
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
vladniko said:
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
Click to expand...
Click to collapse
Done both, actually. Tried to boot directly from a fastboot command and then tried flashing the actual recovery image to the phone. No luck in both. Never able to get into twrp.
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
hubhib said:
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
Click to expand...
Click to collapse
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
eddie_gordo said:
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
Click to expand...
Click to collapse
Needed the RMA anyways. If you had an unlocked bootloader and formatted each partition and then flashed each partition with the corresponding image file from the latest factory image, it was shot. It happens from time to time. Happened to mine as well. 2 or 3 days after I finally got it (pre ordered on launch) I rebooted the phone at some point 2 or 3 days later and it just never turned back on. 100% bone stock. Not even an unlocked bootloader. Nothing would happen when I plugged it into a PC, left it on AC power for hours and hours and still nothing. Holding power 10-15 seconds, nada. RMA'd and luckily this one's been perfect ever since. Good luck with the new device!
Hello everyone!
First of all - this is my first post here, so if I'm doing something wrong, please, correct me.
Three days ago i dropped my ALE-L21 into water closet (don't ask). I dismantled it and put into rice for 2 days. Today I decided to check if phone will start normally, but there is a following problem:
The phone is stuck into bootloop - after turning it on I see only the brand logo and after every 1 minute it vibrates for a while, the screen goes black and the brand logo appears once again. I tried to get it into recovery mode, but nothing happens. (none of button combination: holding power, power+volup or power+volup+voldown works. The phone always try to reboot)
I plugged it to PC and the only thing I can do is to get into fastboot (bootloader unlocked, phone rooted, but USB debugging is off, so adb doesn't see the device).
Any ideas of how can I fix that? Maybe just volume button is broken? Should I try to clean volume&power flex? Maybe there is an alternative solution to turn usb debugging mode on? Then I could try to recover it manually, with adb.
Flash the correct firmware in fastboot.
Szabi01 said:
Flash the correct firmware in fastboot.
Click to expand...
Click to collapse
How can I do that?
I can run fastboot by power+vol_down, but probably USB-debugging is turned OFF. ADB doesn't see any devices plugged in.
turbotramp said:
How can I do that?
I can run fastboot by power+vol_down, but probably USB-debugging is turned OFF. ADB doesn't see any devices plugged in.
Click to expand...
Click to collapse
If you pc doesn't recognize phone with adb or fastboot commands in fastboot you propably have some broken hardware.
But you can try this stuff if it recognize something.
Go to fastboot and flash TWRP with "fastboot flash recovery (recovery_filename_here).img" then try power + vol up, if it doesn't work you can try to extract UPDATE.APP app and flash system.img, boot.img, cust.img in fastboot. If TWRP works use this to re-install stock firmware https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702.
Ok. Fastboot recognized my device, so I installed everything what you mentioned. Everything went 'OKAY', as it printed in cmd, but still there is no change. Whatever I am doing it freezes at brand logo and after some time reboots.
But I used branded ROM, which I downloaded from huawei website - it is the only one that not gives me "balong" error.
Any ideas before I give back my Huawei to the official service? Maybe there is some way to diagnose volume_up button?
My superrom rooted v20 keeps crashing just recently out of nowhere. I forgot what the first crash screen is but I had a green, purple,yellow or black crash screens with "TZ crash", "secure watch dog bite" and "kernel crash" header? It is now stuck in boot sequence or crashed after a few minutes if I get pass it.
I'm a noob in rooting so I just followed the steps from here and managed to root my original H910PR with no problem previously. Forgot where I got the link but then I flashed it with the Super-4.0-H91010u.
I can't even get through TWRP, it turned off suddenly a few times and now I'm hit with a yellow RPM crash screen. The phone wont even start right now after I pull out and put the battery (70% last I checked) back in, even with my new, barely 1 week ZeroLemon 10k. Not responding any button presses either.
Hopefully you did the optional step in that process and backed up your phone before rooting it.
If you did, you should be able to get to fastboot (with the phone off, hold vol down and plug in the USB cable). Once in fastboot:
fastboot flash aboot_COMXX aboot
fastboot flash xbl_COMXX xbl
fastboot flash laf_COMXX laf
I think you get the idea. Repeat for every file that was dumped. Replace the XX with the actual com number. Once your phone is back to stock, see if you have a problem.
-- Brian
runningnak3d said:
Hopefully you did the optional step in that process and backed up your phone before rooting it.
If you did, you should be able to get to fastboot (with the phone off, hold vol down and plug in the USB cable). Once in fastboot:
fastboot flash aboot_COMXX aboot
fastboot flash xbl_COMXX xbl
fastboot flash laf_COMXX laf
I think you get the idea. Repeat for every file that was dumped. Replace the XX with the actual com number. Once your phone is back to stock, see if you have a problem.
-- Brian
Click to expand...
Click to collapse
The problem is I only understand about half of what you wrote up there. I think I followed your previous tutorial step by step, so I think I did all the optional steps also. Tried to go into fastboot like you said but can't get the phone to responding, its like there's no power even when the battery is plugged in. Did I missed a step for this fastboot? Should the PC running anything for the fastboot to open? Currently trying to read back the previous tutorial and on the fastboot process.