Related
I've been fighting this for hours over the last couple of days....
I rooted my phone (ebay-purchased T-mobile G2) a few months ago with the Cyanogenmod guide (http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting), got Clockworkmod on using Rommanager and (almost) everything was good.
Recently, the entire phone crashed and seemed to get stuck in a boot loop. I booted into CWM recovery (v3.0.2.4). CWM gave me these errors every single time:
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
"E:Can't open /cache/recovery/log"
"E:Can't mount /cache/recovery/last_log"
"E:Can't open /cache/recovery/last_log"
I tried to just reflash CM7 that I loaded onto the SD card via windows, always wiping data and cache first. The install would start, and then abort with "E:Error in /sdcard/update.zip" and "(Status 1)". Eventually one of the versions of CM6 started to actually install with the progress bar, but then would abort with "assert failed: write_raw_image" and "(Status 7)". Googling pointed to CWM possibly being the problem, saying updating to 3.0.2.5 would fix it. I haven't found a download for that, and because I'm stuck with boot loops, I can't get to Rommanager.
I tried using fastboot to flash the same version of CWM, but it comes up with "Failed (remote: not allowed)". Googling hints that installing stock ROM (PC10IMG?) would fix it, but I can't get that to flash or fastboot on.
I don't have a NAND backup, but I do have a CWM backup that I can't fully restore from because it always says "Error while formatting /system!". Haven't found a fix for that.
I am able to connect with ADB, but I've tried checking for the eMMC serial to see if I have a culprit chip (http://forum.xda-developers.com/showthread.php?t=1081243), and it doesn't return a value.
This thread OP is actually almost the exact same thing as I've been through except the last part about loading with hboot, which I can't get to work. And I've tried with the sd card mounted and unmounted.
I'm stumped, as most of the solutions are just "reflash ROM" or "reflash recovery" and I can't get either to work. At this point, I don't think I care if I end up rooted/customROM or stock. Any help is appreciated a hundred fold.
S-Off
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.0226_M
eMMC-boot
Hey,
Sorry, I have had the same exact problem. Spent a week+ working non stop, following every tutorial on the forums to try and fix it. I've had zero luck. good thing it was in warranty for me, I just sent it in and got a new one. just enjoying my non-rooted G2 now. I hope there is a fix for this somewhere, It has been happening quite a bit.
That's a bit discouraging. I wish I had the knowledge of the topic to even understand what the actual problem is, unless it's multiple smaller problems that I'm dealing with. It doesn't seem like a full-brick situation, but I guess it is.
Re: warranty - was it through HTC or the carrier? And how did you convince them to accept it? They usually say that rooting voids warranty, eh?
Tmobile told me rooting voids Htc 1 year warrenty but still have 129.
deductable through asurion for 5. a month.
I called Asurion to verify.
Sent from my HTC G2 using XDA Premium App
just curious but why doesn't fastboot work? otherwise you could try to recover via fastboot:
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot reboot
Here is a thread about the error
Its most probably a hardware issue, so there's nothing you can do about it except return it.
Also, fastboot probably doesn't work cause you don't have eng hboot?
-Nipqer
http://forum.cyanogenmod.com/topic/20898-easy-way-to-flash-eng-hboot-new-80416-radio-and-cwm-3024/
That PC10IMG worked great for me. All you need is S-OFF.
Once you get eng hboot, use fastboot to flash the recovery.img from your last working nandroid backup. Might want to do 'fastboot erase recovery' just before 'fastboot flash recovery recovery.img' just to give a clean slate.
Once you get in CWM you can format system, data, cache and restore from nandroid.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!
killerbee12345 said:
just curious but why doesn't fastboot work? otherwise you could try to recover via fastboot:
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot reboot
Click to expand...
Click to collapse
"fastboot erase boot"
"Failed (remote: not allowed)"
Nipqer said:
Here is a thread about the error
Its most probably a hardware issue, so there's nothing you can do about it except return it.
Also, fastboot probably doesn't work cause you don't have eng hboot?
-Nipqer
Click to expand...
Click to collapse
starting to seem more and more like it's hardware. i don't have an Eng HBOOT, but I am S-OFF. Cyanogen wiki says that should be enough, but I'm still stuck, so maybe.
onelikeseabass said:
http://forum.cyanogenmod.com/topic/20898-easy-way-to-flash-eng-hboot-new-80416-radio-and-cwm-3024/
That PC10IMG worked great for me. All you need is S-OFF.
Once you get eng hboot, use fastboot to flash the recovery.img from your last working nandroid backup. Might want to do 'fastboot erase recovery' just before 'fastboot flash recovery recovery.img' just to give a clean slate.
....
Click to expand...
Click to collapse
tried that PC10IMG.zip and it actually recognized it as soon as I got into HBOOT. but then I came up with the Partition Update Fail message.
Any tips on convincing HTC to warranty it anyway?
tatsuha said:
"fastboot erase boot"
"Failed (remote: not allowed)"
starting to seem more and more like it's hardware. i don't have an Eng HBOOT, but I am S-OFF. Cyanogen wiki says that should be enough, but I'm still stuck, so maybe.
tried that PC10IMG.zip and it actually recognized it as soon as I got into HBOOT. but then I came up with the Partition Update Fail message.
Any tips on convincing HTC to warranty it anyway?
Click to expand...
Click to collapse
This may be a shot in the dark, but have you tried reformatting your SD card? Back it up, format, and just put that PC10IMG.zip I linked earlier on it. Maybe it's a problem reading from the source that causes the write to fail.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!
onelikeseabass said:
This may be a shot in the dark, but have you tried reformatting your SD card? Back it up, format, and just put that PC10IMG.zip I linked earlier on it. Maybe it's a problem reading from the source that causes the write to fail.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!
Click to expand...
Click to collapse
Hadn't gotten a chance to do much during these last few days, but I finally sat down with the G2 again. I had already tried formatting, but it was a quick format, I'm fairly certain.
I tried with full reformats on both the SD cards I have (the 8GB Sandisk that came with the phone and an older 2GB Kingston). One recognized the PC10IMG, but had the same partition update fail. The other didn't even recognize the file.
If this ends up being unrecoverable, does anyone have any advice for a shot at the HTC warranty? or is there no chance that they would miss the fact that it's rooted? >_>
Hello,
I've been rooted for over a year now. Have flashed back and forth roms around hundreds of times now. Unfortunately an hour after flashing synergy godmode and some of the godmode tweaks, my phone rebooted while idling and bootloops.
Now i am stuck in hboot and can not enter recovery. I am using hboot 0.76.2000 (pc3610000) and s-off. I have tried flashing seperate clockwork and amon-ra embedded pc36img.zip, these say that they will complete updating but then will bootloop after i try to enter recovery. I have tried these updates with a different sd card (as my current sd card w/godmode may be an ext2 partition?) but that has not changed anything either.
As i understand, I can only push files with adb through recovery; which i can not get into.
If anyone can please help it would be very much appreciated.
Thank you in advance
try this way? its how i flash my recoveries when im switching or testing...
remove any pc36img.zip files from your sd and boot to your bootloader...
when you bootloader boots up let it scan for the pc36img whatever thing and let it say not found...
now highlight fastboot and click the power button and wait for FASTBOOT USB to show up...
then type in these codes...
Code:
fastboot devices
it should output some info, if you get some serial number then your good
then type in...
Code:
fastboot flash recovery *whatever the name of the recovery your using is*
so like for amon_ra 2.3 (which is what i use is)
Code:
fastboot flash recovery recovery-RA-supersonic-v2.3.img
just make sure that the recovery img file is in the same directory as the fastboot.exe file on your comp (its should be with all your other sdk stuff like adb.exe and such)
if all goes well then itll say
pushing recovery OKAY
writing recovery OKAY
and the amount of time it took...
then click back into your bootloader and go to the newly written recovery
(i apologize in advance if you already tried this with no avail)
I've set up fastboot usb and done this. Everything wrote ok and finished, however i still bootloop when trying to access recovery. I have tried multiple recoveries including clockwork 3, recovery-RA-supersonic-v2.3.img, and doing entire nandroid restores using nandroid recovery batch script. In both cases everything passes and nothing seems to be functional afterwards.
Any other ideas?
dunno man.. im just trying to visualize how it bootloops going to recovery.. it should be the white htc screen (or any other splash you may have set on there) and then boink recovery... does it like just sit there on the splash and thats it?
try letting it boot normal and then when it goes to the rom loading screen type in
Code:
adb reboot recovery
other than that something is totally askew bro
When booting, i'll get the white htc screen for 4-5 seconds, then it'll power off and reboot, unless i boot to hboot. When i hit recovery, it goes black for a second, then reboots to htc screen and repeats.
I've also tried complete wiping recovery and reloading using fastboot commander, and doing full pc36img.zip that include hboot, radio wiimax updates etc http://forum.xda-developers.com/showthread.php?t=830153&highlight=wimax
I may just go into a sprint store today. Was trying to avoid it as I really don't want to be stock again.
This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again
the only hboot that allows fastboot commands is 0.76 unfortunately
try running an ruu maybe? other than that i havent the slightest idea
I used this RUU - http://forum.xda-developers.com/showthread.php?p=7529500
It passed every step, but still bootloops when booting to ROM and Recovery.
I'm out of ideas....
I'm going to go with hardware problem.
Sent from my PC36100 using XDA Premium App
bad sector on the internal flash memory ?
My brother has the same problem and i have been trying to fix it with no luck. When i boot the phone up its beeps/vibrate 5 times, then sits on a black screen. I can get into hboot and load pc.....whatever files, it says they work but still reboot, 5 beep, ect. I was going to try an RUU next i see that didnt work for op.
i just ran into this problem today. I was at work when it randomly rebooted and now is stuck in a bootloop. i have tried everything even using the latest RUU. it finished but still bootloops. I am also not able to get into recovery. Sucks because im out of warranty.
So let me get this straight...you can't go into recovery because there's no recovery? You've installed drivers and ran RUU and still nothing? That seems weird because i had the same issue when i first rooted my phone with unrevoked, all i did was run the RUU and it restored my phone back to "stock" and i re-rooted again but this time using z4 root. You might just have to take the phone back to Sprint
Same issue but worse
I'm having the same issue as the OP except that my buttons (power and volume up/down) will not respond. I have scoured these and other forums for a situation like mine and have found none.
I have tried flashing recoveries, RUU's and jsut about anything someone says.
First screen says:
supersonic evt3 ship s-off
hboot-2.10.0001
touch panel atmelc03_16ac
oct 15 2010 12:01:00
hboot
fastboot
recovery
clear storage
simlock
hboot usb
then it scans the sd card for the pc36img zip. It will load but will freeze on the next screen:
parsing...... [sd zip]
1. boot loader
2. radio
3. boot
4. recovery
5. system
6. user data
7. splash
8. wimax
it will stick here and I am completely lost. My old Palm Pre will only suffice for a day.... max.
If anyone has come across a situation like this that might help me, would you please point me in the right direction. Thanks!
kdbrown5 said:
This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again
Click to expand...
Click to collapse
If you look in autoroot thread in my sig the "tools" zip has something that will let you flash different partitions from fastboot. If you use that to flash the PC36IMG from here it will give you the eng hboot back and possibly reflash whatever got corrupted.
Keep in mind, that will only work properly if you are not using one of the 2.xx hboots. Only phones with a 0.9x hboot will let you use it.
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message <bootrom> [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
ragus15 said:
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
Click to expand...
Click to collapse
Try this ruu its the newest officially signed ruu, so it will work with s-on. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Trygon said:
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Click to expand...
Click to collapse
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
cmlusco said:
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
Click to expand...
Click to collapse
Holy cow, props on the quick reply. You're pretty much confirming my fears. I've tried a few combinations of battery and usb connections, but there's no vibration nor ADB signal.
I can't say I've ever seen a stock utility behave this way, so user beware. It's also worth noting that I have no history on this phone's modifications - Just that it was S-ON and locked when I got it, in bootloops between kernel and ROM, and attempting to access recovery looped it too.
cmlusco said:
Try this ruu its the newest officially signed ruu, so it will work with s-on. Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
Click to expand...
Click to collapse
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
ragus15 said:
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
Click to expand...
Click to collapse
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
cmlusco said:
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
Click to expand...
Click to collapse
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
ragus15 said:
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
Click to expand...
Click to collapse
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
cmlusco said:
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
Click to expand...
Click to collapse
I have tried fastboot erase recovery followed by the flash and still get the white HTC image. I am not able to boot the os... i get white HTC splash image over and over, and the USB driver that tries to mount to my desktop in the bootloop is not Android 1.0, it is CMDA technologies. I have no idea what that is or if that has to do with the previous frawg/straight talk flash attempts.
Just tried to flash a rom in recovery, but my SD Card now won't mount!!!!!!! I wiped everything needed, except SD Card, but it won't mount. I mount the card via usb, all the files are present, but why won't it read? Can someone please help on what can be done so I don't have to go back to my "Wack"Berry!?
Also, it reads the PCIMG file in HBoot, updates just fine. So why not read my card in recovery? I'm using Amon.
Try this
http://forum.xda-developers.com/showthread.php?p=6696983
death-by-soap said:
Try this
http://forum.xda-developers.com/showthread.php?p=6696983
Click to expand...
Click to collapse
You can do that, or the weaker of the 2 options which can work, if you can still see the PC36IMG in the bootloader, re-install your recovery via PC36IMG.
teh roxxorz said:
You can do that, or the weaker of the 2 options which can work, if you can still see the PC36IMG in the bootloader, re-install your recovery via PC36IMG.
Click to expand...
Click to collapse
Thanx for the replies...... Still having issues.
1. I don't have a ADB option in my fastboot menu as explained in the guide. So I don't know how to run the command.
2. I re-installed the PC36IMG, still won't read my card in recovery!!!! I even tried to update to a different recovery thinking maybe it fails to work for my phone, still no luck.
Does anyone have any other suggestions?
MsOhSoPhresh said:
Thanx for the replies...... Still having issues.
1. I don't have a ADB option in my fastboot menu as explained in the guide. So I don't know how to run the command.
2. I re-installed the PC36IMG, still won't read my card in recovery!!!! I even tried to update to a different recovery thinking maybe it fails to work for my phone, still no luck.
Does anyone have any other suggestions?
Click to expand...
Click to collapse
1. You want the FASTBOOT option, so that the device says "FASTBOOT USB" when connected to the computer. Then you can run the fastboot commands (which is what the thread should say, rather than and commands).
I've searched this and other forums, and tried virtually everything that has been suggested or that I can think of.
I have a Zenfone 2 Laser ZE551ML rooted. Phone has worked like a dream. Installed TWRP 3.0, made and saved several backups in several different places, internally and externally.
Two days ago, flashed a TWRP recovery (I was looking to get back some data I had deleted inadvertently), seemed to go well until it booted, and could not get past the screen that says "Fastboot Mode!!!". Connected to a PC and was able to execute fastboot commands; supposedly can flash various recoveries, and seemingly does so, with everything looking right on the PC, and the phone actually rebooting. But always stops at the same screen.
ADB, on the other hand, shows no devices listed. Every command results in "Error: Missing Device."
I have done everything I can think of...uninstalled and reinstalled the ADB drivers, used different ADB drivers, removed the external SD card, removed the battery (which is the ONLY way the phone will shut off...pressing the on/off button for 10 seconds just results in it booting up to the same screen. Have tried the fastboot wipe command, again it seems to do so, but always comes back to the same screen. Fastboot flashing a recovery.img appears to successfully write a recovery, then goes to same screen upon reboot.
Any ideas? I've only had this phone a couple of weeks, and really like it. But flashing what was apparently a bad TWRP backup seems to have destroyed it.
Thanks so much for any suggestions!
i have the same problem.. please help!
i have the exact same problem you had.. please tell me how you restored it
As i have a similar problem i cannot help you on the technical side.
But isn't the laser 551 KL instead of ML. Maybe you flashed the wrong files trying to restore the phone
BeachNYC said:
I've searched this and other forums, and tried virtually everything that has been suggested or that I can think of.
I have a Zenfone 2 Laser ZE551ML rooted. Phone has worked like a dream. Installed TWRP 3.0, made and saved several backups in several different places, internally and externally.
Two days ago, flashed a TWRP recovery (I was looking to get back some data I had deleted inadvertently), seemed to go well until it booted, and could not get past the screen that says "Fastboot Mode!!!". Connected to a PC and was able to execute fastboot commands; supposedly can flash various recoveries, and seemingly does so, with everything looking right on the PC, and the phone actually rebooting. But always stops at the same screen.
ADB, on the other hand, shows no devices listed. Every command results in "Error: Missing Device."
I have done everything I can think of...uninstalled and reinstalled the ADB drivers, used different ADB drivers, removed the external SD card, removed the battery (which is the ONLY way the phone will shut off...pressing the on/off button for 10 seconds just results in it booting up to the same screen. Have tried the fastboot wipe command, again it seems to do so, but always comes back to the same screen. Fastboot flashing a recovery.img appears to successfully write a recovery, then goes to same screen upon reboot.
Any ideas? I've only had this phone a couple of weeks, and really like it. But flashing what was apparently a bad TWRP backup seems to have destroyed it.
Thanks so much for any suggestions!
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
where TWRP.img is the directory of twrp
then you should get back to TWRP
flash TWRP image again in TWRP itself because the method on line 1 only temporary flashes TWRP and will auto discard TWRP after a reboot