Related
Hi,
i found a simliar thread that was talking about a similar subject, but didn't answer my question. i have lost it and cant find that same thread for help.
rooted -flashed bad rom - everything keeps closing(apps, Google sync)--- cant get int to recovery mode because of error
****I unlocked bootloader and rooted my GalaxyNex. then installed ROM maneger. i flashed CWM,then backed up my ROM. i tested it by flashing my backed up ROM, after i had messed around and my phone went back to normal. i was feeling safe. i noticed that i was having trouble getting into the recovery mode because of the belly open with exclamation Point. i read that it is because CWM was losing permission? i found that i just had to re-flash CWM every time right before i go into recover mode. i flashed a ROM from ROM maneger and everything worked until i turned the phone on. i cant sync Google account, and basically all apps close immediately (no key board too). I cant get into recovery mode and i cant down load ROM maneger to try to re-flash CMW to restore from older ROM.
I am sorry if this is already been answered i have try to find my situation but i couldn't.
I tried to re-flash the clock work recover image through the terminal of my mac but it says permission denied... i guessing i need to find a way to re flash to stock from fastboot is this possible ?
Pull the battery and hold power + volume and get into fast boot. Flash stock images from here
Sent from my Galaxy Nexus using xda premium
joshnichols189 said:
Pull the battery and hold power + volume and get into fast boot. Flash stock images from here
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks I got really lucky i was able to re flash Clock work recovery in fast boot with the command
./fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
then i was able to get into the proper recovery mode and re flash my backed up image.
if i wanted to re flash a original image would the terminal command look like this
./fastboot flash recovery "Imagename" ? i might have just got lucky but i am guessing thats how you re-flash something to your phone?
now that i have gotten back to the beginning, why is it that i have to re flash CMW every time to get in correct recovery mode? or how do i stop it from giving me the recovery error when trying to get to the correct recovery mode?
thanks again
Glad your good! Hate to see these threads but we all go through it sooner or later
Sent from my Galaxy Nexus using xda premium
billycurtis said:
now that i have gotten back to the beginning, why is it that i have to re flash CMW every time to get in correct recovery mode? or how do i stop it from giving me the recovery error when trying to get to the correct recovery mode?
thanks again
Click to expand...
Click to collapse
After you fastboot flash the CWM image, use ADB, a terminal, or a file explore to remove or rename the file /system/recovery-from-boot.p
I just got an HTC one from Best Buy Mobile (Verizon) yesterday. Turned S-Off using runrunner. Verified root but can not access recovery. I had the same issue with a S4 but it was a known issue for all that has updated to the 4.3.
I have tried all the suggestions in flashing TWRP. I am wondering if this is a Verizon related issue? Maybe they are putting something on their phones to prevent recovery?
HELP!!!!
Something is really jacked up with my phone. It kept saying Unfortunately Amazon has stopped. Over and over again. So I gave up and went to do a factory restore and data wipe. I first went to Super user and removed permanent root. I then tried to do a factory wipe through settings/backup & reset reset phone. It still gave me issues trying to enter recovery mode. It would get hung up and then reboot to a sort of safe mode version of the OS. (with a red disclaimer at the bottom). Then I tried to do factory reset by holding the volume down and power. Its doing the same thing. At this point I don't are about root I just want a working phone.
Any suggestions?
Flash twrp from the xda thread here and then flash arom. What exactly are you doing to flash it?
Sent from my One using xda app-developers app
I have tried flashing a recovery. Now I dont have root and cant do anything. It will not let me even upgrade firmware. I tried to get it back to stock. My recovery is jacked up.
adodson927 said:
I have tried flashing a recovery. Now I dont have root and cant do anything. It will not let me even upgrade firmware. I tried to get it back to stock. My recovery is jacked up.
Click to expand...
Click to collapse
OK, so you are s-ff, is your bootloader unlocked?
IF you are not on stock recovery YOU CANNOT run an update
I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
adodson927 said:
I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
.. you have to have a recovery..
I think?
can you successfully fastboot flash a custom recovery? If not can you fastboot the stock recovery..?
To be completely honest, I would just run the RUU. should fix you right up
You could boot into RUU and flash the decrypted stock rom zip to get back to straight stock. The zip reflashes stock recovery. I don't see why that wouldn't work.
Edit: Oops. Didn't even notice andy just recommended the same thing lol. My fault.
adodson927 said:
I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thats odd, i thought you had to have a recovery of some kind.
Here is what I would do:
Lets try Flashing CWM instead of TWRP in fastboot I will post it, and I will also post the stock recovery there to as well.
https://www.dropbox.com/s/kk2esdrx1g1b50p/recovery-clockwork-touch-6.0.4.5-m7vzw.img
the image is easily installed via an unlocked bootloader with the following command:
fastboot flash recovery imagename.img
in this case: fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7vzw.img
See if it actually takes, and report back any errors.
If for some reason it does not, try booting into bootloader/fastboot then push the stock recovery:
https://www.dropbox.com/s/hgzgq84svzahvnv/htconerecovery_signed.img
Hopefully that will at least take and try to push CWM again , reboot bootloader and reboot into recovery . I am hoping that does it for you.
Go here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip and dump SU on the root of your SD card and flash the SU.
I have seen people have all kind of weird issues with rum runner and I am just glad i had the official java card method used on mine. I also tend to just use a stock ROM which is just de-bloated.
Anyways I have used Santod040 roms in case i need to go back to pure stock ROM only: http://forum.xda-developers.com/showthread.php?t=2485319
You will need the odex one to run any OTA
The firmware is a different thing to flash.
here are the checksums:
htconerecovery_signed.img
MD5: E3F5208454689BE7F09835D4A60953A8
SHA-1: 1B0734D97732039528159AD1409AFEE858B5E9F1
SHA3-256: E0741EB77E5DEBEA932EE74F374FAC9E1037776178944279E8B12832C30E2546
recovery-clockwork-touch-6.0.4.5-m7vzw.img
MD5: 21A386CB920C485844E3BE0727351838
SHA-1: 312350D7383850915A648E2060AA2FC72B5EA08F
SHA3-256: 78B0C42CD62D3EB2B18BF62B544FC86878A56199DB96D13F26EA65663A822932
Thanks guys!
I was able to install TWRP and also Superuser.
Here are the instructions I used. Maybe they will help someone else like me.
Power off your device, then press and hold Power and Volume Down until you're in the bootloader menu. Highlight FASTBOOT and press Power. You should see Fastboot USB highlighted in red.
Download the latest version of TWRP for your phone and carrier. Rename file to twrp.img.
Open a command prompt on your computer and navigate to your SDK directory. Type "fastboot flash recovery twrp.img" and hit Enter.
Then I backed up my stock rom using TWRP
In TWRP's main menu, tap Reboot. It will tell you that you're not rooted and ask you to install SuperSU, so swipe to confirm. When you reboot your phone, you should see a notification that you need to install the SuperSU app. Open the notification and select TWRP, since the app from Google Play only works with S-OFF.
Worked flawlessly.
I installed NuSenseONE max and I love it so far.
adodson927 said:
Thanks guys!
I was able to install TWRP and also Superuser.
Here are the instructions I used. Maybe they will help someone else like me.
Power off your device, then press and hold Power and Volume Down until you're in the bootloader menu. Highlight FASTBOOT and press Power. You should see Fastboot USB highlighted in red.
Download the latest version of TWRP for your phone and carrier. Rename file to twrp.img.
Open a command prompt on your computer and navigate to your SDK directory. Type "fastboot flash recovery twrp.img" and hit Enter.
Then I backed up my stock rom using TWRP
In TWRP's main menu, tap Reboot. It will tell you that you're not rooted and ask you to install SuperSU, so swipe to confirm. When you reboot your phone, you should see a notification that you need to install the SuperSU app. Open the notification and select TWRP, since the app from Google Play only works with S-OFF.
Worked flawlessly.
I installed NuSenseONE max and I love it so far.
Click to expand...
Click to collapse
how else were you trying to flash a recovery ?!?
Goo.im app as well as ROM Manager, ROM Toolbox can flash recoveries. I've notice there isn't much compatibility with the m7vzw though. You can also use terminal command's from the device. All of these require root access though.
Sent from my One using XDA Premium 4 mobile app
Hey everyone, so my problem is that i did run rumrummer the way it said on the directions and i double checked my rom version type countless times. It says that i am unlocked and s-off, but i cant access recovery. I tried flashing recovery with fastboot command prompt, and still no luck. It gives me a "error: cannot open 'open.img', I navigated to the folder that it is located in and executed the command properly every time. I also dont know how to flash superuser using flashboot, so any help will be very much appreciated. Also I'm kinda new to rooted, I have some experience from a few years back, but dont remember everything.
Jo5ton1018 said:
Hey everyone, so my problem is that i did run rumrummer the way it said on the directions and i double checked my rom version type countless times. It says that i am unlocked and s-off, but i cant access recovery. I tried flashing recovery with fastboot command prompt, and still no luck. It gives me a "error: cannot open 'open.img', I navigated to the folder that it is located in and executed the command properly every time. I also dont know how to flash superuser using flashboot, so any help will be very much appreciated. Also I'm kinda new to rooted, I have some experience from a few years back, but dont remember everything.
Click to expand...
Click to collapse
place the name.img file in the same folder as the adb and fastboot executables, open command prompt as administrator for that directory, then type "fastboot flash recovery name.img" substitute name.img for the actual name of the file including extension and make sure there are no quotes around it. also, use "fastboot devices" or "adb devices" to make sure your phone is being recognized.
I got it to work, finally. Thanks for the reply pointedge. I beat u to it earlier in the day and forgot to post up again that I got it. It was like u said, I just had the file in the wrong folder.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
nrfitchett4 said:
how else were you trying to flash a recovery ?!?
Click to expand...
Click to collapse
I'm willing to bet he flashed the wrong recovery. It's happened to a lot of people.
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Try flashing the recovery again. Download it from the link provided here and confirm the md5 checksum for the zip file.
http://forum.xda-developers.com/showthread.php?t=2694564
Sent from my HTC One_M8 using XDA Premium 4 mobile app
PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
some reason doing twrp from terminal on hte m8 gets us stuck (it did for me at least.)
just reflash the insecure boot image.. fastboot flash boot blah.img
that should get you back up
PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having
darll said:
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having
Click to expand...
Click to collapse
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!
PirateP3t3 said:
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!
Click to expand...
Click to collapse
I followed the instructions on the TWRP site:
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
But that left me in a TWRP bootloop. Can you please give me step by step instructions on how to get out of this bootloop?
Thanks!
First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, then swipe for a factory reset (Advanced wipe cannot properly wipe cache and dalvik after fastboot erase cache)
then go to advanced, select cache, dalvik and system and swipe to wipe those partitions.
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.
exad said:
First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, advanced, select cache, dalvik and system
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.
Click to expand...
Click to collapse
Thanks for the detailed instructions. I opened fastboot on my PC with phone plugged in and entered the code but the cmd prompt just says <waiting for device>
Do you have the HTC drivers installed on your PC with HTC sync uninstalled?
Does it say fastboot USB on your phone?
Sent from my HTC One_M8 using xda app-developers app
Update: I ended up just installing the Viper ROM and the system rebooted fine. It's strange that I couldn't reboot the device to get out of recovery without having to install a custom ROM.
Sent from my HTC6525LVW using Tapatalk
No it's not. You flashed recovery to the boot partition.
Sent from my HTC One_M8 using xda app-developers app
How do i fix TWRP Bootloop on my HTC explorer a310e... ?
How do i fix TWRP Bootloop on my HTC explorer a310e... ?
I hav custom cm11 Kitkat ROM installed on it...
but after I installed the rom, and again tried to reboot
into TWRP recovery, it is just stuck on the blue color
TEAMWIN screen... Please help how to fix it...!
HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.
Maxxour said:
HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.
Click to expand...
Click to collapse
You need cwm recovery to factory reset from cm roms.
Also you need to be in FASTBOOT mode for it to detect your device.
Boot to fastboot, erase cache, reinstall twrp.
Next time reset/wipe from recovery.
ashyx said:
You need cwm recovery to factory reset from cm roms.
Click to expand...
Click to collapse
cwm recovery or cm recovery?
Hello guys, I've had a problem with my phone since flashing 5.0 firmware months ago but I'm just now getting to fixing it.
I have twrp recovery and some 5.0.1 rom that was in beta awhile ago. Everytime I boot into twrp in boots right into fastboot, whatever it's called, after about 5 seconds, so I can't flash any roms, which I think is the problem since it's pretty buggy.
Another thing is that Whenever I charge the phone while it's off, it boots into bootloader and therefore stops charging. Anyway I can fix my recovery without recovery?
This is Verizon htc one m8.
Thanks guys.
Edit: tried using twrp app to reinstall recovery but it boots into bootloader instead.
Fire n mage said:
Hello guys, I've had a problem with my phone since flashing 5.0 firmware months ago but I'm just now getting to fixing it.
I have twrp recovery and some 5.0.1 rom that was in beta awhile ago. Everytime I boot into twrp in boots right into fastboot, whatever it's called, after about 5 seconds, so I can't flash any roms, which I think is the problem since it's pretty buggy.
Another thing is that Whenever I charge the phone while it's off, it boots into bootloader and therefore stops charging. Anyway I can fix my recovery without recovery?
This is Verizon htc one m8.
Thanks guys.
Edit: tried using twrp app to reinstall recovery but it boots into bootloader instead.
Click to expand...
Click to collapse
Of course there's a way. Just like the way you first installed a custom recovery. I will give you instructions in case you've forgotten, or if the phone was pre-rooted when you got it.
Download the latest TWRP from here onto your PC.
When the download is finished, rename it to recovery.img and place it into your fastboot folder.
Hook up your phone to your PC, get into ADB/fastboot, and issue the command fastboot flash recovery recovery.img
Then when it's done fastboot reboot
You should now have a working TWRP recovery.
xunholyx said:
Of course there's a way. Just like the way you first installed a custom recovery. I will give you instructions in case you've forgotten, or if the phone was pre-rooted when you got it.
Download the latest TWRP from here onto your PC.
When the download is finished, rename it to recovery.img and place it into your fastboot folder.
Hook up your phone to your PC, get into ADB/fastboot, and issue the command fastboot flash recovery recovery.img
Then when it's done fastboot reboot
You should now have a working TWRP recovery.
Click to expand...
Click to collapse
Had to use my brother computer and set it up since I got a mac. Thanks for your reply, and sorry for the double post, I installed via fastboot, and I can confirm the most updated version was pushed to the device, but it still goes right into fastboot after booting into recovery.img
Edit: Did that fastboot erase cache thing in the command prompt and now it works. Thanks for telling me the commands for cmd again!
Fire n mage said:
Had to use my brother computer and set it up since I got a mac. Thanks for your reply, and sorry for the double post, I installed via fastboot, and I can confirm the most updated version was pushed to the device, but it still goes right into fastboot after booting into recovery.img
Edit: Did that fastboot erase cache thing in the command prompt and now it works. Thanks for telling me the commands for cmd again!
Click to expand...
Click to collapse
Oh Crap! I forgot to add that one. :silly:Erase cache is obviously needed. Sorry.
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