Help!! Full wiped LG G4 - G4 Q&A, Help & Troubleshooting

Hi. Im new to rooting and on the attempt to install lineageos, i got stock in full wipe.
First i unlocked my bootloader and then installed twrp. everything went well so far, but in twrp i made the mistake of doing a full wpe. now i dont know how to boot into custom recovery, if it even still exists on my phone. i also tried the lg flash tool, but i always get the connection to server error. would be really gratefull if someone would help me out. thxs

so... you don't tried enter to recovery via key-combo? (Vol Down+Power).
If you can enter to Download Mode, try to flash a KDZ with LGUP.

I can't flash kdz because lgup not recognized the device because i flashed a old marshmallow system on my lg4 with v30 port ..any help

fijuu said:
Hi. Im new to rooting and on the attempt to install lineageos, i got stock in full wipe.
First i unlocked my bootloader and then installed twrp. everything went well so far, but in twrp i made the mistake of doing a full wpe. now i dont know how to boot into custom recovery, if it even still exists on my phone. i also tried the lg flash tool, but i always get the connection to server error. would be really gratefull if someone would help me out. thxs
Click to expand...
Click to collapse
ebusuhejbi said:
I can't flash kdz because lgup not recognized the device because i flashed a old marshmallow system on my lg4 with v30 port ..any help
Click to expand...
Click to collapse
Try connecting to your phone in Android SDK/Platform Tools.
Type adb reboot recovery and see if it will boot into TWRP. If it works, you have choices to restore a backup or flash a new rom.
If it doesn't boot into TWRP, make sure your TWRP recovery.img is in the same folder and try re-installing by typing fastboot flash recovery TWRP.img (using the file name of your TWRP image).

solved
sdembiske said:
Try connecting to your phone in Android SDK/Platform Tools.
Type adb reboot recovery and see if it will boot into TWRP. If it works, you have choices to restore a backup or flash a new rom.
If it doesn't boot into TWRP, make sure your TWRP recovery.img is in the same folder and try re-installing by typing fastboot flash recovery TWRP.img (using the file name of your TWRP image).
Click to expand...
Click to collapse
Thanks a lot. i finally got it done with the lg bridge software.

Related

recovery install problem

Hello
i've just installed the twrp recovery on my lg g4 (after unlock the bootloader of course)
and when i try to boot in recovery mode it doesnt work (it shows me an android logo with an exclamation mark)
plz help me :S
thanks
It did not install properly. Same happened to me. Try
fastboot erase recovery
fastboot flash recovery twrp.img
Then try to boot to recovery using twrp manager app
jkoljo said:
It did not install properly. Same happened to me. Try
fastboot erase recovery
fastboot flash recovery twrp.img
Then try to boot to recovery using twrp manager app
Click to expand...
Click to collapse
thanks for your comment!
but i still have this problem...
jkoljo said:
It did not install properly. Same happened to me. Try
fastboot erase recovery
fastboot flash recovery twrp.img
Then try to boot to recovery using twrp manager app
Click to expand...
Click to collapse
After you have installed TWRP via adb you must boot (or stay there) into revocery and falsh the twrp-xxxx.img as "revocery" (buton down right to change from image to recovery).
hannsheinz said:
After you have installed TWRP via adb you must boot (or stay there) into revocery and falsh the twrp-xxxx.img as "revocery" (buton down right to change from image to recovery).
Click to expand...
Click to collapse
thanks man but i cant boot into recovery... this is the problem... Instead of boot into recovery, it shows me a android logo with exclamation mark..
daniel1803 said:
thanks man but i cant boot into recovery... this is the problem... Instead of boot into recovery, it shows me a android logo with exclamation mark..
Click to expand...
Click to collapse
Try this:
adb reboot bootloader
fastboot.exe flash recovery twrp-xxxx.img
fastboot.exe boot twrp-xxxx.img (same filename as above)
Then flash the same twrp-xxx.img file via "install"
After this you can direct boot into revocery with apps like quickboot, or via Vol-Down, Power-On, or direkt via reboot meneu if you use G4 Tweak Box.
If you are on 6.0 the recovery will never boot up. But don't worry, all you need to do is just download kernel package like SimpleGX, from this package copy the boot.img, then flash it via fastboot. After that let the phone boot up, reboot it to bootloader again and flash twrp.img. If you did it properly the twrp will boot up. REMEMBER to flash full kernel package otherwise you can have problems with your device.
Adam Myczkowski said:
If you are on 6.0 the recovery will never boot up. But don't worry, all you need to do is just download kernel package like SimpleGX, from this package copy the boot.img, then flash it via fastboot. After that let the phone boot up, reboot it to bootloader again and flash twrp.img. If you did it properly the twrp will boot up. REMEMBER to flash full kernel package otherwise you can have problems with your device.
Click to expand...
Click to collapse
is it save to flash the SimpleGX kernel without the included modules in the zip file?
because i only manged to flash twrp for h811 on my h815 with v20d and unlocked bootloader... i am confused
the-erazer said:
is it save to flash the SimpleGX kernel without the included modules in the zip file?
because i only manged to flash twrp for h811 on my h815 with v20d and unlocked bootloader... i am confused
Click to expand...
Click to collapse
Never flash recovery for H811 on H815, there is reason why they are different.. You could have bricked your device. Yes flashing this boot.img is completely safe as long as you flash full package later, otherwise you might have problems with software. I've done so many times without any issue, anyway it's not a softbrick, you always reflash the firmware however be aware of that if you do it wrong and get your phone bricked without access to custom recovery there is no way to recovery your data. My G4 is dead but this is caused by the well know bootloop issue (hardware fail).
Adam Myczkowski said:
Never flash recovery for H811 on H815, there is reason why they are different.. You could have bricked your device. Yes flashing this boot.img is completely safe as long as you flash full package later, otherwise you might have problems with software. I've done so many times without any issue, anyway it's not a softbrick, you always reflash the firmware however be aware of that if you do it wrong and get your phone bricked without access to custom recovery there is no way to recovery your data. My G4 is dead but this is caused by the well know bootloop issue (hardware fail).
Click to expand...
Click to collapse
Thanks for the quick answer... I got a replacement and it ships with v20d twrp for h811 was the only solution to get root... Now i have seen your post... Will try it later... I hope it works
Do you know the reason why we have to flash the kernel? Some poeple can flash twrp without...
edit: i have flashed the kernel but flashing twrp dont want to flash...
the result of fastboot is positive but if i want to boot in recovery the screen stays black and then the phone boots up normal to os...
woult it help to kdz the phone to lolipop?
Gesendet von meinem LG-H815 mit Tapatalk
Adam Myczkowski said:
If you are on 6.0 the recovery will never boot up. But don't worry, all you need to do is just download kernel package like SimpleGX, from this package copy the boot.img, then flash it via fastboot. After that let the phone boot up, reboot it to bootloader again and flash twrp.img. If you did it properly the twrp will boot up. REMEMBER to flash full kernel package otherwise you can have problems with your device.
Click to expand...
Click to collapse
the-erazer said:
Thanks for the quick answer... I got a replacement and it ships with v20d twrp for h811 was the only solution to get root... Now i have seen your post... Will try it later... I hope it works
Do you know the reason why we have to flash the kernel? Some poeple can flash twrp without...
Gesendet von meinem LG-H815 mit Tapatalk
Click to expand...
Click to collapse
Install Twrp Manager from the Play Store and then install Twrp 2.8.7.0 from it.
It's working fine on my H815 v20d
Sent from my LG G4
welder73 said:
Install Twrp Manager from the Play Store and then install Twrp 2.8.7.0 from it.
It's working fine on my H815 v20d
Sent from my LG G4
Click to expand...
Click to collapse
I have no idea how did you manage to install TWRP recovery on official 6.0 firmware since TWRP manager requires root and to root android 6.0 you have to have modified boot image...
the-erazer said:
Thanks for the quick answer... I got a replacement and it ships with v20d twrp for h811 was the only solution to get root... Now i have seen your post... Will try it later... I hope it works
Do you know the reason why we have to flash the kernel? Some poeple can flash twrp without...
Gesendet von meinem LG-H815 mit Tapatalk
Click to expand...
Click to collapse
As I mentioned above in android 6.0 google have modified it as the stock kernel does not allow to use unsigned stuff even though your bootloader is unlocked. So only way to root/install recovery on android 6.0 smartphones is to flash modified boot.img that allows to load unsigned things. If you flash recovery without changing stock kernel you'll not brick your device but the recovery will never open, but flashing superSU might brick your device, Autoprimes flashable zips include modified boot.img I suppose.
Adam Myczkowski said:
I have no idea how did you manage to install TWRP recovery on official 6.0 firmware since TWRP manager requires root and to root android 6.0 you have to have modified boot image...
As I mentioned above in android 6.0 google have modified it as the stock kernel does not allow to use unsigned stuff even though your bootloader is unlocked. So only way to root/install recovery on android 6.0 smartphones is to flash modified boot.img that allows to load unsigned things. If you flash recovery without changing stock kernel you'll not brick your device but the recovery will never open, but flashing superSU might brick your device, Autoprimes flashable zips include modified boot.img I suppose.
Click to expand...
Click to collapse
i have no more idea what to do... i have flashed the kernel... and then recovery but when i want to enter recovery nothing happens it doesnt load. after some seconds the phone boots up normal.
before that i have tried twrp manager but the app crashes every time i want to select the recovery to install.
flashify is same as flashing over fastboot.
what is the difference between the 2 versions of twrp? h811 got another kernel than h815 but why can i load this one but the right for h815 not?
the-erazer said:
i have no more idea what to do... i have flashed the kernel... and then recovery but when i want to enter recovery nothing happens it doesnt load. after some seconds the phone boots up normal.
before that i have tried twrp manager but the app crashes every time i want to select the recovery to install.
flashify is same as flashing over fastboot.
what is the difference between the 2 versions of twrp? h811 got another kernel than h815 but why can i load this one but the right for h815 not?
Click to expand...
Click to collapse
I have no idea honestly, try to reflash the firmware. Recovery doesn't load only if you don't flash boot.img properly.
Adam Myczkowski said:
I have no idea how did you manage to install TWRP recovery on official 6.0 firmware since TWRP manager requires root and to root android 6.0 you have to have modified boot image...
As I mentioned above in android 6.0 google have modified it as the stock kernel does not allow to use unsigned stuff even though your bootloader is unlocked. So only way to root/install recovery on android 6.0 smartphones is to flash modified boot.img that allows to load unsigned things. If you flash recovery without changing stock kernel you'll not brick your device but the recovery will never open, but flashing superSU might brick your device, Autoprimes flashable zips include modified boot.img I suppose.
Click to expand...
Click to collapse
Sorry,I thought he already have root.
Btw,you can't root H815 on MM without unlocking the bootloader...
Sent from my LG G4
the-erazer said:
i have no more idea what to do... i have flashed the kernel... and then recovery but when i want to enter recovery nothing happens it doesnt load. after some seconds the phone boots up normal.
before that i have tried twrp manager but the app crashes every time i want to select the recovery to install.
flashify is same as flashing over fastboot.
what is the difference between the 2 versions of twrp? h811 got another kernel than h815 but why can i load this one but the right for h815 not?
Click to expand...
Click to collapse
just for information i have tested to kdz back to lollipop v10b... downgrade was really easy using lgup but the result was twrp doesnt work... same as marshmallow... btw github had a bug ticket for h811 there was the same only vice versa...
daniel1803 said:
Hello
i've just installed the twrp recovery on my lg g4 (after unlock the bootloader of course)
and when i try to boot in recovery mode it doesnt work (it shows me an android logo with an exclamation mark)
plz help me :S
thanks
Click to expand...
Click to collapse
how do u unlock the bootloader on a LG G4 H811 ver 20i

Phone and TWRP won't start, stuck in bootloader

Tried to install 11/16 version of Project Nexus and vendor image via flashify but forgot that I needed to update TWRP to the latest version first to fix that it was asking me for an encryption password that I had never set.
Now i'm stuck in the bootloader. If I try to go to recovery, the TWRP splash screen displays but never loads further.
I attempted to use ADB to re-install but i get error: device '(null)' not found. I've tried several different drivers but can't get any to work.
Any ideas?
Salled said:
Tried to install 11/16 version of Project Nexus and vendor image via flashify but forgot that I needed to update TWRP to the latest version first to fix that it was asking me for an encryption password that I had never set.
Now i'm stuck in the bootloader. If I try to go to recovery, the TWRP splash screen displays but never loads further.
I attempted to use ADB to re-install but i get error: device '(null)' not found. I've tried several different drivers but can't get any to work.
Any ideas?
Click to expand...
Click to collapse
fastboot erase recovery
fastboot flash recovery recovery.img ?
icrunchbanger said:
fastboot erase recovery
fastboot flash recovery recovery.img ?
Click to expand...
Click to collapse
I renamed the recovery file for ease of use (as you can see in the screenshot). It appeared to work but now the TWRP splash screen doesn't show after reboot when I select recovery.
Salled said:
I renamed the recovery file for ease of use (as you can see in the screenshot). It appeared to work but now the TWRP splash screen doesn't show after reboot when I select recovery.
Click to expand...
Click to collapse
TWRP version your using?
Have you tried formating the device ?
icrunchbanger said:
TWRP version your using?
Have you tried formating the device ?
Click to expand...
Click to collapse
I'm using v3.0.2-2 of TWRP
I'm attempting to wipe and install system image via fastboot now.
Salled said:
I'm using v3.0.2-2 of TWRP
I'm attempting to wipe and install system image via fastboot now.
Click to expand...
Click to collapse
Wipe all and than try with flashing twrp
Use 3.0.2.3
https://mega.nz/#!bB5W0ahZ!F3N1NAEA7VHfORgjfZBLC2NWyCj8CFWVw4lUMiKK0Rs
icrunchbanger said:
Wipe all and than try with flashing twrp
Use 3.0.2.3
https://mega.nz/#!bB5W0ahZ!F3N1NAEA7VHfORgjfZBLC2NWyCj8CFWVw4lUMiKK0Rs
Click to expand...
Click to collapse
I wiped everything and tried to flash that, it flashed but after a restart I still can't open recovery.
[Resolved] I was able to flash the system image after wiping and boot the phone. Thank you for the help.
Reflash the twrp recovery 3.0.2.3 2 or 3 perhaps the adb installation don't work for me too i reflash and reflash when i reboot in twrp
Or try "fastboot flash recovery recovery.img"
And. "fastboot boot recovery.img
Salled said:
Tried to install 11/16 version of Project Nexus and vendor image via flashify but forgot that I needed to update TWRP to the latest version first to fix that it was asking me for an encryption password that I had never set.
Now i'm stuck in the bootloader. If I try to go to recovery, the TWRP splash screen displays but never loads further.
I attempted to use ADB to re-install but i get error: device '(null)' not found. I've tried several different drivers but can't get any to work.
Any ideas?
Click to expand...
Click to collapse
EXACT same situation. For me windows 10, won't recognize bootloader. Nexus 7 2012, it had 3.0.0 0, was trying to upgrade to 3.0.2.0, stupidly used FlashFire since bootloader not seen in Windows. Now can't boot into Recovery.
Sent from my Nexus 5X using Tapatalk
Win10 didn't work for me, too. On Ubuntu it was easy (or older Windows)
1st for repairing go back to firmware.

[H815] I think I screwed up my phone's software

Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Peshyy said:
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Click to expand...
Click to collapse
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
steadfasterX said:
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
Click to expand...
Click to collapse
twrp-3.0.2-1-h815.img, H815 as the title says and from the official website as I've always done. As for the thread - I don't have TWRP and I can't even flash it as I've written in my post. That's what I'm struggling with.
Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!

M8s stuck in bootloader

Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Hi McBad,
you could try the following. I also had some problems to access the recovery.
- Again bring the phone into fastboot, flash the 2.8 recovery and access it
- Do a wipe for factory reset, not just only cache
- after that try to flash the twrp-3.0.1-0-m8ql.img version, the other one worked for me neither
- the try to install the custom ROM LOS13
I hope this will help you.
clone
It would be great if that would work, but flashing a recovery does not work. I flash it, success message, try to access it, vibrates and bootloader pops back instantly. That is the problem.
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Have you tried sideloading twrp ?
McBad said:
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Click to expand...
Click to collapse
Did you use HTC fastboot ?
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Is there any way you could flash twrp 2.8 again? Once in that recovery you have sideloading option which you could use to transfer latest recovery onto your device. Are we talking about the same process?
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Sideload as follows ....
McBad said:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Click to expand...
Click to collapse
You can't install lineage if you haven't upgraded your device with latest official update. I would try reinstaling twrp 2.8, do a wipe of cache, dalvik cache and system, Sideload CM 12; and see how it goes. As well, while in twrp I would try relocking bootloader but only after an unsuccessful attempt to flash said rom. I don't know what your experience with soft bricked devices is, but sometimes it takes a while, different usb cable or usb slot on your PC, correct files in adb folder, re-download of rom or recovery because it easily gets corrupted while downloading. And obviously a fully charged device. Let us know how it goes.

Normal boot always ends up in TWRP

Hello everyone,
I have a problem regarding the start-up of my phone. Yesterday I unlocked my bootloader and flashed TWRP (twrp-3.1.1-0-addison.img) with the help of the thread located here.
Everything worked fine, I could boot into TWRP afterwards. I continued by wiping the needed partitions and flashing the newest Lineage OS ZIP alongside with the GApps Nano ZIP.
The problem I face now is that when I reboot in TWRP by selecting the “System” option, I end up again in TWRP (same happens if I shut down the phone and make a normal boot).
However, if I boot to the bootloader and select there the normal “start” option, the phone boots up just fine using the installed ROM.
Any ideas what’s wrong here and how I cloud fix that?
This happens with me, i don't know If its gonna work with you but works for me, i just flash a older twrp image from the same thread you use, ( i install from bootloader, not flashing a img in twrp), then you boot on twrp, and then you install the latest recovery
Note: This works for me, i don't know if its work for you
{Sorry for my poor english, my native language is porruguese }
jst98 said:
This happens with me, i don't know If its gonna work with you but works for me, i just flash a older twrp image from the same thread you use, ( i install from bootloader, not flashing a img in twrp), then you boot on twrp, and then you install the latest recovery
Note: This works for me, i don't know if its work for you
{Sorry for my poor english, my native language is porruguese }
Click to expand...
Click to collapse
Thanks a lot, I will give it a try!
and then you install the latest recovery
Click to expand...
Click to collapse
Do you mean TWRP or a recovery image of the OS?
When i say to intall the latest version is for twrp
Unfortunately, it did not work ....
I flashed twrp-3.0.2-0-addison.img via fastboot, booted to TWRP and installed the newest image with the 'install' option from TWRP.
Phone is still booting to the recovery if I restart ....
_Hope_ said:
Unfortunately, it did not work ....
I flashed twrp-3.0.2-0-addison.img via fastboot, booted to TWRP and installed the newest image with the 'install' option from TWRP.
Phone is still booting to the recovery if I restart ....
Click to expand...
Click to collapse
Aww ! It's just a simple thing. Use this simple command "fastboot oem fb_mode_clear" and it will boot to normal system.
I was also facing this in my previous htc device.
That was tha problem of tge twrp version that i was using.
Try using the different twrp.

Categories

Resources