I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.
Gitnerd said:
I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.
Click to expand...
Click to collapse
If you ask me
since i have s-off I would just change my mid and cid to dev edition then flash dev end ruu.
Gitnerd said:
I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.
Click to expand...
Click to collapse
That's not how to flash an RUU.zip
This is how it is done.
Make sure that your extSD is formatted to FAT32 first. It won't work otherwise.
After the format, rename the zip to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your card.
Boot into bootloader (Turn off you phone, then boot it up while holding power + vol down) and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash ~ power to reboot)
That's it. Super easy.
Make sure to delete the renamed file from your extSD, otherwise every time you boot to hboot, it'll try to update again.
xunholyx said:
That's not how to flash an RUU.zip
This is how it is done.
Make sure that your extSD is formatted to FAT32 first. It won't work otherwise.
After the format, rename the zip to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your card.
Boot into bootloader (Turn off you phone, then boot it up while holding power + vol down) and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash ~ power to reboot)
That's it. Super easy.
Make sure to delete the renamed file from your extSD, otherwise every time you boot to hboot, it'll try to update again.
Click to expand...
Click to collapse
Hello, thank you for your reply, I was traveling for holidays and have been working on the phone for the past couple of days and have run into alot of trouble doing what you say here, any help would be greatly appreciated I'm at the end of my rope with this phone. I got the 0P6BIMG.zip RUU and loaded it onto my Fat.32 formatted SD Card , I loaded the card into the phone and followed the fastboot options to flash, it recognized the RUU and attempted to flash it but said the model ID was incorrect. I opened up the zip and sure enough the android-info.txt file in the RUU does not list my model number and I cannot put my model number into it because it is an htc encrypted zip that will not let me change the file properties of the archive. I thought about trying to put the HTC into developer kernel so that my model ID would line up with that of the RUU info file but I did something (don't know what I did) and now fastboot won't even recognize the device (fastboot devices command shows nothing when phone is in fastboot USB mode).
My mid is 0P6B20000
My cid is VZW_001
Gitnerd said:
Hello, thank you for your reply, I was traveling for holidays and have been working on the phone for the past couple of days and have run into alot of trouble doing what you say here, any help would be greatly appreciated I'm at the end of my rope with this phone. I got the 0P6BIMG.zip RUU and loaded it onto my Fat.32 formatted SD Card , I loaded the card into the phone and followed the fastboot options to flash, it recognized the RUU and attempted to flash it but said the model ID was incorrect. I opened up the zip and sure enough the android-info.txt file in the RUU does not list my model number and I cannot put my model number into it because it is an htc encrypted zip that will not let me change the file properties of the archive. I thought about trying to put the HTC into developer kernel so that my model ID would line up with that of the RUU info file but I did something (don't know what I did) and now fastboot won't even recognize the device (fastboot devices command shows nothing when phone is in fastboot USB mode).
My mid is 0P6B20000
My cid is VZW_001
Click to expand...
Click to collapse
You need to use this RUU.zip
It is for the Verizon model
xunholyx said:
You need to use this RUU.zip
It is for the Verizon model
Click to expand...
Click to collapse
My goodness, I looked for this RUU everywhere, I would type in my mid and cid into google, I checked the One m8 archive of RUU's in that XDA thread, I couldn't find it. I don't know how you did, but you just saved my phone! Im booted into Android 4.4.2, receiving texts and everything. I'll figure out if I'm safe to update android later, I'm just so happy to have a working phone again. I gave you a thanks but do you have a contribution link or anything I could give to? You have helped me out tremendously.
Gitnerd said:
My goodness, I looked for this RUU everywhere, I would type in my mid and cid into google, I checked the One m8 archive of RUU's in that XDA thread, I couldn't find it. I don't know how you did, but you just saved my phone! Im booted into Android 4.4.2, receiving texts and everything. I'll figure out if I'm safe to update android later, I'm just so happy to have a working phone again. I gave you a thanks but do you have a contribution link or anything I could give to? You have helped me out tremendously.
Click to expand...
Click to collapse
I gave you an old RUU link. Sorry.
You can get the 5.0.1 RUU.zip from here if you want to update. It would be good to do it now, since running the RUU wipes your device, and yours is already wiped.
I've sent a PM with a donation link.
Thank you!
Related
Really hoping I can revive this incredible.
Got the phone in attempt to fix it, it's in a constant state of 'boot-loop syndrome'..
Can't go into recovery.. can't factory data reset.. all I get is the
....*vibrate*, white HTC incredible screen....*vibrate off*, etc. etc. etc.
The only thing that is working is hboot (as well as hboot usb when plugged into a pc).
But that's as far as I can get.. anything else I attempt to load from the hboot/bootloader it goes into a constant boot loop spasm.
The incredible is currently S-ON
Hboot- 0.92.0000
Radio-2.15.10.07.07
I've tried numerous PB31IMG stock files in attempt to recover the system.
The system/sd card detect the files just fine and attempt to load them.
The PB31IMG at pvillcomp ( http://pvillecomp.com/?page_id=22 ) didn't work, too old
This one, however, does work (only one so far I've found that does)
http://dinc.does-it.net/Stock_Images/4.08.605.2/PB31IMG.zip
But while going through the installation process it fails at Radio_**
all other variables within the file (bootloader, system, recovery, etc) complete successfully.
Once all the components of the zip file are installed, it gives the message
partition update fail!
Update fail!
Click to expand...
Click to collapse
Am stuck at this point, hoping for assistance.. if anyone knows any possible solutions or what the issue could be, please help!
Thank you.
echoedge said:
But while going through the installation process it fails at Radio_**
.
Click to expand...
Click to collapse
That sounds scary. I've heard that a failed radio flash is the only way to permenantly brick one of these phones.
Here's what I would try:
1. Update HBOOT to the latest, from here:
http://dinc.does-it.net/Hboots/Hboot_1.07/
2. Unlock the bootloader using htcdev (see cmlusco's or scotty's guides)
3. Flash a custom recovery using fastboot (I've used CWM and TWRP)
IF you can get all that to complete successfully, and can boot into recovery, you should then be able to get root adb access to the system. This will give you some more options, such as flashing an older RUU (again, see cmlusco's and scotty's guides for downgrading), and just maybe you'll be able to find something that works.
musical_chairs said:
That sounds scary. I've heard that a failed radio flash is the only way to permenantly brick one of these phones.
Here's what I would try:
1. Update HBOOT to the latest, from here:
http://dinc.does-it.net/Hboots/Hboot_1.07/
2. Unlock the bootloader using htcdev (see cmlusco's or scotty's guides)
3. Flash a custom recovery using fastboot (I've used CWM and TWRP)
IF you can get all that to complete successfully, and can boot into recovery, you should then be able to get root adb access to the system. This will give you some more options, such as flashing an older RUU (again, see cmlusco's and scotty's guides for downgrading), and just maybe you'll be able to find something that works.
Click to expand...
Click to collapse
Thanks for the website, was looking for something like that
Anywho, tried to flash it in the bootloader, it seems to find it a file for which is proper but does not give me any option to update it.
It just says "looking for PB31IMG... then finds it, says checking PB31IMG...", then the prompt goes away.
I'm quite limited when it comes to knowledge on this stuff, but anyone think if I decompile the stock ruu (~180mb) PB31IMG.zip, and flashboot each part of the update separately it may work?
So tonight around 6pm EST I noticed that there was a Cyanogen mod nightly for my wife's Verizon htc one. I also noticed that there was an update function so I decided to give it a try. However, I didn't realize I had yet to make a backup of her current ROM. I thought I had done this when I originally rooted the phone... HUGE MISTAKE NUMBER 1. Once the update was flashed it gave me an error and began boot looping. I tried to find the original version of Cyanogen but could not locate it on the device. Since the HTC One doesn't have an SD card and I Don't have the special OTG USB I couldn't get the storage to mount to add a new ROM. After 2 hours of searching I was finally able to Push a ROM to her device but I kept getting an E: Error executing updater binary... <--- this error I researched only to find that I couldn't flash the rom I was trying to lash in the latest TWRP recovery.
ALL I want to do now is to flash a new recovery to the phone so I can install a ROM and get this paperweight working again.
Can someone please explain to me STEP by STEP what to do here?
volumebmx15 said:
So tonight around 6pm EST I noticed that there was a Cyanogen mod nightly for my wife's Verizon htc one. I also noticed that there was an update function so I decided to give it a try. However, I didn't realize I had yet to make a backup of her current ROM. I thought I had done this when I originally rooted the phone... HUGE MISTAKE NUMBER 1. Once the update was flashed it gave me an error and began boot looping. I tried to find the original version of Cyanogen but could not locate it on the device. Since the HTC One doesn't have an SD card and I Don't have the special OTG USB I couldn't get the storage to mount to add a new ROM. After 2 hours of searching I was finally able to Push a ROM to her device but I kept getting an E: Error executing updater binary... <--- this error I researched only to find that I couldn't flash the rom I was trying to lash in the latest TWRP recovery.
ALL I want to do now is to flash a new recovery to the phone so I can install a ROM and get this paperweight working again.
Can someone please explain to me STEP by STEP what to do here?
Click to expand...
Click to collapse
It depends on what you are trying to do. You said you wanted to flash a new recovery, so go ahead and do it.
http://forum.xda-developers.com/showthread.php?t=2416431
If you want to revert back to stock, go ahead and do that too.
http://forum.xda-developers.com/showthread.php?t=2475216
But I say your best bet is to just push a ROM in recovery. Are you S-Off?
Also, what commands are you doing to push a ROM? Is the E: drive where your SDK toolkit located?
Karn101,
What ROM and RECOVERY would you suggest I flash?
I had the TWRP 2.6.3.4 touch recovery installed but for some reason it would not allow me to install the following 2 ROMS
1. Google Edition HTC One VZW [KITKAT]
2. Inverted-EclipticONE-KitKat-v1.2
When I did this I kept getting the E: Error executing updater binary which really had me as a loss.
To answer your question I am S-OFF it says UNLOCKED M7_WLV PVT SHIP S-OFF RH @ the bootloader screen.
HBOOT Version is 1.54.000
Also when I was pushing a ROM I was using some commands I found in a guide here: http://forum.xda-developers.com/showthread.php?t=2354259
I followed some of the steps on here with no luck...
Also I attempted to flash several recoveries from Fast boot with the Fastboot flash recovery recovery.img in the command promt. It shows that the files was sent but the phone just get stuck at the bootloader saying loading recovery at the top in blue font.
Can you walk me through each step on this? I need to get a recovery on there first them push a ROM to the device and install it via the recovery.... I am assuming that would be the easiest method.
If your s-off can't you flash the Ruu in fastboot? Maybe that will help
sent from my JAVA CARD S-OFF FAUX HBOOT BLUE HTC ONE using xda premium app.
Tigerstown said:
If your s-off can't you flash the Ruu in fastboot? Maybe that will help
sent from my JAVA CARD S-OFF FAUX HBOOT BLUE HTC ONE using xda premium app.
Click to expand...
Click to collapse
I suggest this as well.
also
"brick" means phone is dead. you're phone turns on..
not a brick.
what i did once when i couldnt flash RUU was it should work S-On and well Its got to work on S-Off
1-Download TWRP recovery also the System.img and boot.img
2-Rename TWRPRecovery6.3xx.img to Recovery.img
3-Flash recovery in fastboot fastboot flash recovery Recovery.img
4-boot into recovery via fastboot fastboot boot recovery.img
This will boot your device into the custom recovery
5-press Backup
6-swipe to confirm
7-after it's done making a backup
8-navigate back to the home screen
9-press Advanced
10-press Mount
11-check the box next to USB-OTG
This will allow to mount your sdcard into the computer and you can copy the system.img from the RUU
12-open folder TWRP open folder BACKUPS ETC ETC until you get to the folder with the backup you just made
13-delete the system.ext4.win delete the system.ext4.win.md5
14-copy the system.img here abd rename it to
15-system.ext4.win
16-then unmount
17-then navigate back to the home page in the recovery and
18-press Restore
19-then choose that backup and swipe to confirm
20-also recommend fastbooting the boot.img
this is what i did when i couldnt get any rom to flash any roms via recovery nor a i could do a RUU saved my phone.
Okay Im going to try to get the whole story in here, so stick with me.
I bought a used ATT m8, that was converted to GPE. It was unlocked and s-off.
I wanted to go back to stock Rom, but twrp recovery wouldnt flash ANYTHING. I tried a bunch of roms and mod files. I would frequently get Status 7 error. Tried different recoveries, same thing.
I tried using http://forum.xda-developers.com/showthread.php?t=2733523 this to get back to stock. Changed my CID to 11111111. Still didnt work. ROM would install, but it kept rebooting to recovery. I reflashed stock recovery and factory wiped. Then I installed TWRP again and nothing changed. Something really jacked up when I tried to flash an RUU zip using the ./fastboot oem rebootRUU command to flash a 1.5 gb RUU zip. Obviously I did something wrong, because now all I see is an HTC logo and four triangles at each corner. I can still enter adb commands, but the bootloader and recovery are both gone.
Any assistance would be SO appreciated. Im without a phone right now.
Yall are the best.
UPDATE: used fastboot to flash stock firmware. Now i have bootloader and twrp recovery but no rom to flash or nandroid to restore. I cant move any nandroid TO the device for some reaodn. Ive tried for about a half hour now. And the one rom that I tried to adb sideload failed to install
bigbuckin said:
Okay Im going to try to get the whole story in here, so stick with me.
I bought a used ATT m8, that was converted to GPE. It was unlocked and s-off.
I wanted to go back to stock Rom, but twrp recovery wouldnt flash ANYTHING. I tried a bunch of roms and mod files. I would frequently get Status 7 error. Tried different recoveries, same thing.
I tried using http://forum.xda-developers.com/showthread.php?t=2733523 this to get back to stock. Changed my CID to 11111111. Still didnt work. ROM would install, but it kept rebooting to recovery. I reflashed stock recovery and factory wiped. Then I installed TWRP again and nothing changed. Something really jacked up when I tried to flash an RUU zip using the ./fastboot oem rebootRUU command to flash a 1.5 gb RUU zip. Obviously I did something wrong, because now all I see is an HTC logo and four triangles at each corner. I can still enter adb commands, but the bootloader and recovery are both gone.
Any assistance would be SO appreciated. Im without a phone right now.
Yall are the best.
Click to expand...
Click to collapse
Did you run a Sense RUU? You'll need to to resize your partitions.
When the previous owner converted to GPE, he ran a GPE RUU that makes the system partition too small for Sense.
You need to run an AT&T RUU to convert back properly.
Here is a link for the official HTC/AT&T RUU download.
The full instructions are there as well for manually updating.
Read them.
The download is at the bottom of the page.
I finally got the phone booted back into gpe FYI.
But yes, I tried two different HTC ruu zip files by using the OEM rebootruu command and then flashing them. They were around 1.5 GB in size and I do recall it failing because the file was too large to complete is there a way to manually change partition size?
Also worth noting I am using a Mac, and can't use the HTC ruu .exe files
bigbuckin said:
I finally got the phone booted back into gpe FYI.
But yes, I tried two different HTC ruu zip files by using the OEM rebootruu command and then flashing them. They were around 1.5 GB in size and I do recall it failing because the file was too large to complete is there a way to manually change partition size?
Click to expand...
Click to collapse
bigbuckin said:
Also worth noting I am using a Mac, and can't use the HTC ruu .exe files
Click to expand...
Click to collapse
This thread has everything you need.
You'll want option 1. When you boot into bootloader, you'll have to select hboot to start the flash. I don't know why he left that out of his instructions.
Just to clarify, there are no prerequisites to doing this? I don't need to bother with firmware or anything? I just put that file on my SD card, rename it, flash hboot, flash file, reboot into sense?
bigbuckin said:
Just to clarify, there are no prerequisites to doing this? I don't need to bother with firmware or anything? I just put that file on my SD card, rename it, flash hboot, flash file, reboot into sense?
Click to expand...
Click to collapse
Petty much.
Boot into bootloader, select hboot, press vol up to flash, press power button to reboot after the flash. Done.
You'll get prompts for the volume up and press power button.
No need to do anything but rename it, put it on extSD, and go to hboot.
You're amazing. I've spent countless hours troubleshooting this and never came across this thread. I'll update when finished to confirm it worked for me
Oh, I forgot to add, when you done with the flash make sure you delete the renamed file from your extSD. If you don't, every time you boot to hboot it'll try to update again.
So, everything was looking good until (11) System - FAILED
...at the bottom it had an error message saying something like "Image size too large" or something like that. I took a picture if it would help.
Basically the same thing ive been seeing with every other thing ive tried to do
bigbuckin said:
So, everything was looking good until (11) System - FAILED
...at the bottom it had an error message saying something like "Image size too large" or something like that. I took a picture if it would help.
Basically the same thing ive been seeing with every other thing ive tried to do
Click to expand...
Click to collapse
http://forum.xda-developers.com/att...u-m8att-4-4-4-s-off-onlynewest-t3015680/page2
Scroll to post #17, and read the next few.
You need to run it twice.
Yo. (sorry if this thread is already on the board, I couldn't see it after a quick check)
So, I've hit upon quite a snag while trying to update my custom ROM (Android Revolution HD). I made a rookie error of installing this without installing the new firmware.zip first , but I was able to flash the correct firmware.zip (my phone if S-OFF, CID = 02__001). However, after this, my phone went into Android stock recovery <3e> after being in a bootloop, even though I'd already had TWRP installed. Also, ADB on my computer no longer recognises my phone, so I can't flash an img on it; the only option I can now see is to find a zip which I can install from the stock recovery via my SD card, but I can't seem to find one which the stock recovery will let me install.
Anyone have any ideas?
Strangiato said:
Yo. (sorry if this thread is already on the board, I couldn't see it after a quick check)
So, I've hit upon quite a snag while trying to update my custom ROM (Android Revolution HD). I made a rookie error of installing this without installing the new firmware.zip first , but I was able to flash the correct firmware.zip (my phone if S-OFF, CID = 02__001). However, after this, my phone went into Android stock recovery <3e> after being in a bootloop, even though I'd already had TWRP installed. Also, ADB on my computer no longer recognises my phone, so I can't flash an img on it; the only option I can now see is to find a zip which I can install from the stock recovery via my SD card, but I can't seem to find one which the stock recovery will let me install.
Anyone have any ideas?
Click to expand...
Click to collapse
the stock recovery can be easily replaced by going to bootloader/FASTBOOT USB, and
Code:
fastboot flash recovery <name of twrp>.img
so that's easy, but it sounds to me like you flashed a firmware pulled from an OTA, which could have a potential problem:
If you didnt flash "OTA firmwares" incrementally, then you may have missed updates.... ie firmwares pulled from OTAs are incremental, because they expect all previous updates to already there, flashing the "latest" does not mean you actually have all the firmware updates
I recommend using "Combined" "NoWipe" firmwares, such as the ones found here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
(^^ those also happen to include TWRP, but you can still reflash a newer version using above fastboot command)
this is what a firmware flash would look like: http://forum.xda-developers.com/showpost.php?p=60259359&postcount=2
nkk71 said:
the stock recovery can be easily replaced by going to bootloader/FASTBOOT USB, and
Code:
fastboot flash recovery <name of twrp>.img
so that's easy, but it sounds to me like you flashed a firmware pulled from an OTA, which could have a potential problem:
If you didnt flash "OTA firmwares" incrementally, then you may have missed updates.... ie firmwares pulled from OTAs are incremental, because they expect all previous updates to already there, flashing the "latest" does not mean you actually have all the firmware updates
I recommend using "Combined" "NoWipe" firmwares, such as the ones found here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
(^^ those also happen to include TWRP, but you can still reflash a newer version using above fastboot command)
this is what a firmware flash would look like: http://forum.xda-developers.com/showpost.php?p=60259359&postcount=2
Click to expand...
Click to collapse
Thanks for this info and links to the relevant threads, btw.
My biggest problem was that my computer wouldn't find my phone, so I couldn't use fastboot, but now for some reason, using the HTC One Toolkit that was in the post you linked me to, my computer can now see it. I've hit another snag, though, whereby I'm just after flashing the newest version of TWRP, but now for some reason, it didn't seem to install correctly, as the phone has booted into recovery mode, according to my computer, but is stuck on the opening screen with the pink "Entering Recovery..." message on the top. Also, my computer can't seem to touch it now, as even though the toolkit finds it and sees it in recovery mode, any time I try to reboot it or do any other command, the program crashes. I've no idea what's happened, unfortunately :/
Update: after fiddling around with the HTC Toolkit, I was eventually able to boot my phone into bootloader which, from there, I could install what I needed, so my problem's been resolved. Thanks again for your help, as those links proved very useful.
Glad everything worked out.
By the way:
Strangiato said:
but is stuck on the opening screen with the pink "Entering Recovery..." message on the top.
Click to expand...
Click to collapse
^^ is usually caused by using a new version of TWRP with old firmware
I have flashed many phones before my G4 and this is the first time I'm having to ask for help.
The firmware installed was AICP CM13, then the screen went green with a DemiGod message. I held the vol down button to reboot and it came back up. After a few restarts and green screens i figured I needed to reflash the firmware. I booted into Recovery and while wiping the device to flash a new firmware, TWRP crashed. After leaving it for half hour or so, I took the battery out to enter into TWRP so I can flash the new firmware. TWRP is no there to be seen. I hold down the vol down and power button, releasing power for second or two and choose to go into recovery. Every time the phone just gets stuck on the LG screen displaying "Bootloader state :Bootlader unlocked!".
In short, I have no firmware, the device has been wiped and TWRP doesn't seem to be working.
I have tried to flash a KDZ file (H81520A_00.kdz) using the flash guide here. This comes back as unsuccessful saying "connection to server failed". As shown below.
View attachment 3605673
The method to flash an .img file using cmd on the pc includes moving the 4gb .img file to the parent folder of the phone storage. I can't get to move any files whatsoever to my device so figured this method would not work.
Seems if I can somehow flash TWRP, then I should be able to install a new firmware.
Any help much appreciated.
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
rav101 said:
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
Click to expand...
Click to collapse
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
AndHD2 said:
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
Click to expand...
Click to collapse
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
It is late here and with me being tired I said recovery instead of download. I can boot into download mode but when I try to boot into recovery then it just goes straight to the LG splash screen and it will either remain in that screen or the green Demigod screen would come up.
I'm off to sleep and away from my laptop as I have to be up in 5 hours. Luckily I still have my Note 4 so at least I'm not without a phone in the morning. I will try the steps what you have suggested just as soon as I get back from work.
Many thanks
rav101 said:
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
Click to expand...
Click to collapse
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
AndHD2 said:
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
Click to expand...
Click to collapse
Hi @AndHD2, I'm sorry but I can't think of anything else
rav101 said:
Hi @AndHD2, I'm sorry but I can't think of anything else
Click to expand...
Click to collapse
I had another demigod type screen but this was grey and not green with less detail. However it did say it were a kernel error.
Is the handset still under warrenty with the bootloader unlocked. I have a feeling its not