I messed up my recovery - G2 Q&A, Help & Troubleshooting

So I wanted to upgrade to twrp 2.6.3.3 and I dont know why for some reason when I went to their page I saw these instructions and thought I'd try them
_______________________________________________________________
Download the above file and place it in /sdcard on your device. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Make certain that you get this command right. Typing the wrong number could result in a brick!
_______________________________________________________________
Now everytime i try to reboot into recovery it does some kind of boot verification check errors and just turns off. I flashed cwm and it says it flashed recovery ok but I cant boot into recovery. What have I done? :0
Not even my lg flash tool works right. I get to the ready part and click the arrow, I put my device in download mode and plug in the usb cable to the pc and then in the lg flash tool it says download fail, device model is different?

Try reflashing 2.6.3.2...I'm having issues with new version too.
Sent from my VS980 4G using xda app-developers app

Related

OTA upgrade problem

Hi
I have an international version 802 version with ROM of g.lewarne inside (rooted)
I've received and accepted the new OTA upgrade, and now i'm stick in the Clockworckmod Recovery.
I've flashed my LG back to the g.lewarne ROM but each time i restart my phone it goes directly to the CWM recovery Mode.
Any suggestion of what to do to get my phone starting normally?
Partager.info said:
Hi
I have an international version 802 version with ROM of g.lewarne inside (rooted)
I've received and accepted the new OTA upgrade, and now i'm stick in the Clockworckmod Recovery.
I've flashed my LG back to the g.lewarne ROM but each time i restart my phone it goes directly to the CWM recovery Mode.
Any suggestion of what to do to get my phone starting normally?
Click to expand...
Click to collapse
You have to flash back to stock...theres a thread in general forum....
RubbleTea said:
You have to flash back to stock...theres a thread in general forum....
Click to expand...
Click to collapse
I can't get into download mode using up volum and pluging in the usb.
Partager.info said:
I can't get into download mode using up volum and pluging in the usb.
Click to expand...
Click to collapse
Try holding vol up then plugging it again...
RubbleTea said:
Try holding vol up then plugging it again...
Click to expand...
Click to collapse
I'm trying but it keeps getting me back to the CWM recovery mode.
Partager.info said:
I'm trying but it keeps getting me back to the CWM recovery mode.
Click to expand...
Click to collapse
Oh forgot .....the phone has to be off...the hold vol up only then plug in USB chord try that...it shouldn't boot to recovery if it doesn't work
RubbleTea said:
Oh forgot .....the phone has to be off...the hold vol up only then plug in USB chord try that...it shouldn't boot to recovery if it doesn't work
Click to expand...
Click to collapse
Still the same problem.
Partager.info said:
Still the same problem.
Click to expand...
Click to collapse
Damn really?.....maybe check the thread for back to stock...they'll prob be more help or check around somebody around here o that thread has had the same problem as you.....hope this helps
RubbleTea said:
Damn really?.....maybe check the thread for back to stock...they'll prob be more help or check around somebody around here o that thread has had the same problem as you.....hope this helps
Click to expand...
Click to collapse
thank you anyway.
Now it keeps rebooting on lg logo with the error: secure booting error
Any idea?
Update:
A new situation here.
Once i plug my phone to the computer i get the lg logo with the famous error: secure booting error
then the phone screen goes black, however the phone is still on with black screen. on my compyter a new drive is detected with only one folder inside called image with many files inside:
- adsp.b00, adsp.b01, adsp.b02.......adsp.b12, adsp
- cmnlib.00, cmnlib.01, cmnlib.02, cmnlib.03, cmnlib
- dxhdcp2.b00.....until b03, dxhdcp2
- isdbtmm.b00.....until b03, isdbtmm
- mlserver.....
- modemb00....... untill modem.b26, modem
and other files.
PS: i've made a factory reset.
I don't know what can i do now to get my phone alive.
i have the same problem, i got an update yesterday for my german vodafone lg g2 und cant get out of my CWM, i dont know what to do, cant get into download mode
i tryed to transfer a rom.zip to my phone via adb , but my adb doesnt know the command sideload and push does nothing
http://forum.xda-developers.com/showthread.php?t=2569237
See if this help you... tip: use lg g2 flash tool to go back because you are not going to fix it ! Only by going back to stock.
Sent from my LG-LS980 using xda premium
Nicamarcel1 said:
http://forum.xda-developers.com/showthread.php?t=2569237
See if this help you... tip: use lg g2 flash tool to go back because you are not going to fix it ! Only by going back to stock.
Sent from my LG-LS980 using xda premium
Click to expand...
Click to collapse
It doesn't go to download mode.
What you need to do to fix this
If you´re stuck in CWM you CAN´T enter in download mode...in this case you have one Option.
download a T/zip file WRP Recovery
and
Plug the usb cable to a computer and enter in cwm recovery
next
adb push "name of recovery".zip /sdcard
next
install the new recovery
open a terminal commando and put this:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Reboot
If you´re stuck in TWRP you have 2 options.
Enter in download mode and restore the firmware from LGMobile or from ADB command to restore your boot.
sorry for bad english
the same here...
I now have the stable version of Cyanogen tested install.
Supposedly he is fertig.Als Note is only: Checking if loki - fying is needed, Updating partition details ...
Otherwise Zip Install Complete
After the wipe reboot and again in TWRP.
In the file manager of TWRP is not to be understood that an installation place hätte.Den Downloadmod tried (the button is held down the top of the lens and USB cable plugged in to it) always comes only the LG logo and then again TWRP.
This helped me
http://forum.xda-developers.com/showthread.php?t=2451696
ChaseRxx said:
What you need to do to fix this
If you´re stuck in CWM you CAN´T enter in download mode...in this case you have one Option.
download a T/zip file WRP Recovery
and
Plug the usb cable to a computer and enter in cwm recovery
next
adb push "name of recovery".zip /sdcard
next
install the new recovery
open a terminal commando and put this:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Reboot
If you´re stuck in TWRP you have 2 options.
Enter in download mode and restore the firmware from LGMobile or from ADB command to restore your boot.
Click to expand...
Click to collapse
I don't have access to download mode. Now i don't have either access to CWM recovery. All i get when i plug it to my PC is LG logo with the error: secure booting error.
Also adb does not detect my device.
Thank you for your answer.
It seems many people have encountered the same problem with the latest fota from LG.
then my phone goes to black screen while still on.
I have this problem ;(
I have only black screen, I can't go to twrp or download mode. I can't do nothing! :<

[Q] stuck on recovery screen.

Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!
sander-w said:
Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!
Click to expand...
Click to collapse
I'm going to be cautious replying here because I'm a noob, but did you try using ADB to issue commands through adb sideload in cwm? If you go to "load zip" (or something along those lines) then "load using adb" (or something similar) in CWM, you can use adb to issue these commands with your computer and it should fix it (at least, it fixed a boot loop for me when I was stuck with TWRP). Here's the link:
http://forum.xda-developers.com/showthread.php?t=2451696
First of all. DON'T PANIC!
And even before that - make a nandroid backup! Go in CWM and make a full backup.
You have recovery working so you should be able to load System on it ok.
I am not an expert but let me try to guide you step by step.
1. Make a backup!
2. Download a rom on your computer. MAKE SURE ITS FOR YOUR MODEL # of LG G2
List of roms here:
3. Make sure you have over 70% battery
4. Go into recovery CWM
5. Use Wipe > Swipe to Factory Wipe
(go back on bottom right corner)
6. Go Advanced from HOME screen of CWM
7. Click ADB sideload
7b. (I assume you have the drivers loaded. If not make sure ADB is loaded in windows and device manager shows it. Download basic ADB package so you have "adb.exe" file in it)
8. put your rom in the same folder where you have "Adb.exe"
9. Open command prompt on windows. Goto the folder where ADB.exe is. Then Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
10. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
11. Wait for a while or reboot your cwm so that the filename will appear
12. just reflash the file in CWM (Install > choose file). Wipe after again.
13. Voila!
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!
sander-w said:
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!
Click to expand...
Click to collapse
Basically what you need is a root shell whether it's via adb or built into recovery (cwm or twrp)
Searching the forum for "cwm bootloop ota" might give you detailed instructions for your case
Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.
sander-w said:
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.
Click to expand...
Click to collapse
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."
Drachenminister said:
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."
Click to expand...
Click to collapse
It seems that my device was in sideload mode. when I disabled sideload mode I followed the instructions on this pag
http://forum.xda-developers.com/showthread.php?t=2451696
And it worked!!!
Thanks for your help all!!!!

Help, possible brick!!!!!!!!

I am/was rooted with custom recovery. I was running stock ROM with minor tweaks (g3 notification panel, etc). I downloaded the "knock code" update that just came out for the LG G2 (AT&T), not even thinking about the root/custom recovery, and then when I went to install it, it booted into TWRP recovery. I had no idea what to do from there (it would just reboot back to recovery if I rebooted), so I wiped the system then flashed my backup. Still nothing, it still booted into recovery. So then, being the smart guy that I am, I did a complete wipe of everything (internal storage and everything), and now I'm stuck at recovery with absolutely nothing. No backups or anything.
How do I get my phone back up and running?
brian85 said:
I am/was rooted with custom recovery. I was running stock ROM with minor tweaks (g3 notification panel, etc). I downloaded the "knock code" update that just came out for the LG G2 (AT&T), not even thinking about the root/custom recovery, and then when I went to install it, it booted into TWRP recovery. I had no idea what to do from there (it would just reboot back to recovery if I rebooted), so I wiped the system then flashed my backup. Still nothing, it still booted into recovery. So then, being the smart guy that I am, I did a complete wipe of everything (internal storage and everything), and now I'm stuck at recovery with absolutely nothing. No backups or anything.
How do I get my phone back up and running?
Click to expand...
Click to collapse
Try this..
What worked for me was from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Bigsky40 said:
Try this..
What worked for me was from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
What exactly is this supposed to do? I have absolutely nothing on my phone now- no backups or anything. I'm assuming I need to download a rom and flash it via recovery. Is it possible to get a rom on my phone if it just boots into recovery?
brian85 said:
What exactly is this supposed to do? I have absolutely nothing on my phone now- no backups or anything. I'm assuming I need to download a rom and flash it via recovery. Is it possible to get a rom on my phone if it just boots into recovery?
Click to expand...
Click to collapse
I thin you can ADB push a rom file to your phone, flash it in twrp, then enter those terminal commands which will allow it to boot normally
brian85 said:
What exactly is this supposed to do? I have absolutely nothing on my phone now- no backups or anything. I'm assuming I need to download a rom and flash it via recovery. Is it possible to get a rom on my phone if it just boots into recovery?
Click to expand...
Click to collapse
You took ota while having custom recovery ?
This will enable you to boot (if you didn't mess up another things on your system)
you may also: "adb push rom.zip /sdcard/rom.zip"
-where rom.zip is the name of your rom.
Can't figure out how to get ADB to recognize my phone. I downloaded SDK and all that. When I do "adb devices" I get "no devices found"
There's a bug in TWRP 2.7.0.0 that you can't activate ADB.
I suggest to boot into download mode (plug your phone to your computer USB while pressing volume UP key), open LG PC Suite, go to Mobile Device > Restore upgrade errors, and it will flash the latest stock firmware
Sent from my LG-D802 using XDA Premium 4 mobile app

No acess to bootloader/Recovery

Hi Guys,
I had some problems with my beloved zenfone 2. Now i can´t enter in bootloader and recovery, but phone boots normaly.
The thing is it seems the partitions are cracked. My last hope was flashing a new recovery and bootloader with the images i got from this thread: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835 using some programs to flash direct from phone (Tried with "recovery flasher" and "rom installer") but on "rom installer" app shows #ERROR: cannot locate recovery partition:
The history was : I rooted my phone using the zenfone toolkit, then started a wipe cache partition, which didn´t work and i forced off. After that i can´t made any adb connection - i can go to bootloader but doesn´t find my device and can´t write anything - , but i made TWRP recovery work using the "tethered recovery" as show in http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532 and flash the original stock rom. ADB/fastboot still don´t work. After that i entered in TWRP again using the same method and inserted Superuser.zip there, rooting my device. After root i lost Bootloader, but still can go to recovery (using TWRP and CVM programs which have the option "reboot to recovery"), which was still useless since it recognize my phone but adb sideload still don´t work. I even tried the MOFD_update thing - copying the entire rom to sd card and renaming to MOFD update but it shows it can´t update. Then i tried to flash TWRP using the TWRP app and the only thing i did it was lost my recovey too.
Now when i try to go to bootloader only shows the UsB logo (the trident), The same happen if i try to go to recovery by apps.
I think i´ll have to fix partitions mannually, using only phone, but i have no ideia how. Can anyone know what can i do?
Thanks in advance
You broke your recovery. Cleaning cache from stock recovery take a LONG time on the ZF2. You have to be patient.
You're still good if you can get into fastboot though. Just execute
Code:
fastboot format cache
then boot back into recovery. When you're in fastboot, you need to run
Code:
fastboot devices
not adb. Recovery = ADB, bootloader = fastboot
Scratch all that. Reread your post. You've done some very inadvisable things. You should have just formatted from the bootloader instead of bothering to re-root. I have no idea what you've done now.
Trident logo means brick phone...be careful nextime
Mononon said:
You broke your recovery. Cleaning cache from stock recovery take a LONG time on the ZF2. You have to be patient.
You're still good if you can get into fastboot though. Just execute
Code:
fastboot format cache
then boot back into recovery. When you're in fastboot, you need to run
Code:
fastboot devices
not adb. Recovery = ADB, bootloader = fastboot
Scratch all that. Reread your post. You've done some very inadvisable things. You should have just formatted from the bootloader instead of bothering to re-root. I have no idea what you've done now.
Click to expand...
Click to collapse
Thanks Anyway. One thing i don´t understand is why my phone is booting normal. I know i´ll have issues when an update come, but it´s booting normaly
pato2015 said:
Trident logo means brick phone...be careful nextime
Click to expand...
Click to collapse
I hope i will have nextime...
you solved that? just need to reflash recovery.img if you can normally boot and use.
Sent from my ASUS_Z00A using XDA Free mobile app
ityoung said:
you solved that? just need to reflash recovery.img if you can normally boot and use.
Sent from my ASUS_Z00A using XDA Free mobile app
Click to expand...
Click to collapse
i´m trying to flash recovery.img from android. I can boot only for sistem. I can´t boot to bootloader or recovery. I´m trying a lot of apps which says it can flash a recovery from a running android, but none of them works
I also tried the Shuame like you said on another thread, but it doesn´t work. Thanks for your help
It might be possible to do something from a terminal window on your phone, but you would need to take advice from someone who knows what they are doing as I'm only theorizing rather than speaking from any position of knowledge.
Sent from my ASUS_Z00AD using Tapatalk
Is your bootloader unlocked?
dodongobongo said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No. The problems started on my second boot after rooting, i had no chance to unlock bootloader too. I think if i had i can flash a custom recovery using TWRP or CVM apps and flash everything else again, but no, i can´t do that either.
As said above use the terminal app to flash stock recovery by dd command
Make sure u give su before issuing dd
Copy stock recovery to sdcard
Open terminal give these commands one by one
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
reboot recovery
& u r done
Sent from my ASUS_Z008D using XDA Free mobile app
yakub234go said:
As said above use the terminal app to flash stock recovery by dd command
Make sure u give su before issuing dd
Copy stock recovery to sdcard
Open terminal give these commands one by one
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
reboot recovery
& u r done
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
Thank you Sooo much.
Now i have my recovery back, is there a way i can get bootloader back again using commands like that ? (and one bootloader i can use adb\fastboot ?)
I assume now i can use adb/sideload or MOFUPDATE.zip way (inserting an flashable rom with this name in my memory card so the system will flash like an update when i enter in recovery), but i don´t know what exactly i need to do (and what archives i have to use) to have a bootloader again, considering all ways to unbrick zenfone 2 needs fastboot. If i do that with stock Asus rom i can download from asus site will i have bootloader (and acess to fastboot) again? I´m afraid to do that and lose my root acess and still have no fastboot option. With root at least i can use terminal. I´m really afraid of flashing something that really hardbrick my phone since i have no fastboot, only root.
Can i unlock bootloader using terminal ? Maybe it´s safe if i unlock bootloader and then wipe TWRP using only TWRP app. After that i can flash other rooms and always have TWRP to fix if something goes wrong.
Sorry if i´m bothering. And thank you soo much for your help
I assume u now have recovery working
adb sideload full stock rom
Download the one which is bootloader unlockable from the Asus website & make sure u r download the right file for device
Never flash anything with bootloader locked
Sent from my ASUS_Z008D using XDA Free mobile app
yakub234go said:
I assume u now have recovery working
adb sideload full stock rom
Download the one which is bootloader unlockable from the Asus website & make sure u r download the right file for device
Never flash anything with bootloader locked
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
Thank you again. Sorry about my insecurities, but i´m still worry. I rooted my phone at first time using the rootkit, one step there says i have to click "checkbeforeaction.bat" which will say i can go with root if i see 1234567ABCDEF as my phone. After that i can´t use adb anymore.
I don´t know why my phone changed to 1234567ABCDEF, i´m not sure if this is the reason i can´t use ADB. After recover my recovery yesterday (thanks for you) i checked "adb devices" on sideload and still shows 1234567ABCDEF. Still afraid to flash a stock rom and the only thing will change is i lost my root.
Maybe it´s a silly questions, but To use sideload i need a .img or a .zip file ? the stock room will flash stock recovery and stock bootloader again? Will i see 1234567ABCDEF again? Can i sideload a pre-rooted room ?Can i sideload just droidboot.img, boot.img and recovery.img? will it be placed on correct place on my phone? I´m really afraid of doing something wrong again.
Sideload the zip file
It should be a full firmware not an ota
adb sideload thezipfilepathonthepc
& wait for it to finish (it takes long time)
& abt that serial no i think its fine
Sent from my Karbonn A1+ Super using XDA Free mobile app
yakub234go said:
Sideload the zip file
It should be a full firmware not an ota
adb sideload thezipfilepathonthepc
& wait for it to finish (it takes long time)
& abt that serial no i think its fine
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
i don´t understand your last phrase "&abt that serial no i think its fine"
You said never flash anything with your bootloader locked. I didn´t unlock my bootloader
Can i flash the image from this thread (item 3.1 method 1) ? http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
yakub234go said:
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
Didn´t work to...
Shows on computer:
"error: protocol fault <no status>
On phone
"you need adb 1.0.32 or newer to sideload to this device.
installation aborted.
E:file path: /cache/recovery/log
E:file path: /cache/recovery/last_log
E:file path: /cache/recovery/last_install
E:file path: /cache/recovery/last_locale
E:file path: /cache/recovery/log
E:file path: /cache/recovery/last_log
E:file path: /cache/recovery/last_install
E:file path: /cache/recovery/command
I´m pretty sure i have the correct adb
yakub234go said:
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
Other thing that can be important:
When on adb sideload, if i request adb devices shows :
Emulator-5554 offline
0123456789ABCDEF sideload
Thats not my phone, again. What is that 012345ABCDEF thing ? can i fix that ?
Try using diff pc
& i forgot to mention u should unroot before flashing
Sent from my Karbonn A1+ Super using XDA Free mobile app

Always booting to TWRP

I've installed TWRP last weekend and installed LineageOS 14.1 for my LG G6 H870.
I was tinkering with Magisk and Magisk Manager to be able to use Netflix, I didn't restart my device after this step.
Last night LineageOS offered an OTA update and afterwards it restarted to recovery mode.
I assumed I had to install the new image manually so that's what I did.
After the installation the phone rebooted back to TWRP Recovery so I wiped cache, data and dalvik.
It still rebooted back to TWRP recovery so I tried to reinstall LineageOS again by following these steps: https://wiki.lineageos.org/devices/h870/install#installing-lineageos-from-recovery
The phone still only boots to recovery so my assumption, after some reading on XDA, is that something is wrong with the bootloader.
This could have happened when I was tinkering with Magisk, I think I've seen a notice that I tried to make changes to the bootloader.
To fix the bootloader the main suggestion is to flash the stock rom so i've started that path.
I've installed Uppercut and LG Up use links from this thread: https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295/
I found a stock rom at https://lg-firmwares.com/lg-h870-firmwares/#firmwaresList and I assume I need the "NEU/NORTHERN EUROPE" rom.
When I open Uppercut it says "There is no handset connected".
I've got no clue what steps to take at this point.
FYI I'm able to get in to the bootloader mode and the recovery mode but havent been able to get into the download mode.
If you still have twrp just flash stock from there.
basicreece said:
If you still have twrp just flash stock from there.
Click to expand...
Click to collapse
I didn't know it was possible to flash a kdz file using twrp.
According to this reply it isn't possible using kdz files https://forum.xda-developers.com/showthread.php?t=2650569
Do you know for sure that this is possible?
I think I need to flash the bootloader using fastboot but I don't know what source to use, and I hardly found bootloader files on the web.
I don't think Magisk is modifying the bootloader, but I could be wrong.
You can find the H870_v10T and US997_v14A bootloaders here:
https://forum.xda-developers.com/showpost.php?p=73161240&postcount=2
ahk31 said:
I don't think Magisk is modifying the bootloader, but I could be wrong.
You can find the H870_v10T and US997_v14A bootloaders here:
https://forum.xda-developers.com/showpost.php?p=73161240&postcount=2
Click to expand...
Click to collapse
Thanks for pointing out that thread!
I downloaded the bootloader and succesfully installed it using `adb sideload LG-H87010f-Flashable.Bootloader.zip`
But the phone still only boots to TWRP.
So I tried to flash a complete stock rom from https://forum.xda-developers.com/lg-g6/development/rom-eu-lg-h870-10t-rom-t3654134
I did wipe Dalvik/ART, Cache, System and Data and afterwards installed that rom.
Unfortunately these steps didn't make any difference to the boot sequence.
I've been trying again to get into the download mode using key combo's and using `adb reboot download` but it reboots to TWRP instead.
What should I try now?
I finally managed to enter download mode!
In the end I figured that I confused the key combo from my previous phone with this one.
I should only hold the volume up button and then plugin in the usb cable.
What I tried numerous times was a combo of volume up and power button.
for reference and people showing up here later. Doing lineage OTA updates on the G6 forces the device into that endless boot loop into recovery. You get out there by entering the shell in TWRP and dd'ing some zeros somewhere. I had it once but sadly did not write down how I solved it. Google for boot loop and twrp you will find hits here on xda where you see a dd if=/dev/zero line and explaining what todo. It is a bit different for each device, but the article tells you what to look for. As I understood it, writing some zeros at the start of a partition ends the loop, but I am no expert there, it just worked for me.
Oh yes, and stay away from lineage OTAs
Edit: ok, not xda but reddit, anyway here is the link
https://www.reddit.com/r/LineageOS/comments/5riech/how_fix_twrp_recovery_boot_loop_after_lineageos/
The life saving post is a comment further down by muniak
I'm using TWRP 3.1 and still had this issue.
Despite thinking my phone was rooted, I couldn't su, adb as root or anything, so I couldn't /fstab. I ended up looking around and comparing the path I was in with other's. So if you're having this problem just keep going around typing ls and pressing tab like below. Basically you're looking for "by-name/misc" in "/dev/block/platform/".
ls /dev/block ls /dev/block/platform ls /dev/block/platform/[dir or two] ls /dev/block/platform/[dir or two]/by-name ls /dev/block/platform/[dir or two]/by-name/misc
Then the dd if=/dev/zero of=/dev/block/platform/[dir or two]/by-name/misc count=1 bs=32
Good luck and thanks so much for the help!
Click to expand...
Click to collapse
ikbentomas said:
I didn't know it was possible to flash a kdz file using twrp.
According to this reply it isn't possible using kdz files https://forum.xda-developers.com/showthread.php?t=2650569
Do you know for sure that this is possible?
I think I need to flash the bootloader using fastboot but I don't know what source to use, and I hardly found bootloader files on the web.
Click to expand...
Click to collapse
Then flash the stock zip.....
If you had searched the forum you would see the stock zips and bootloaders all complied for twrp.
ikbentomas said:
I've installed TWRP last weekend and installed LineageOS 14.1 for my LG G6 H870.
I was tinkering with Magisk and Magisk Manager to be able to use Netflix, I didn't restart my device after this step.
Last night LineageOS offered an OTA update and afterwards it restarted to recovery mode.
I assumed I had to install the new image manually so that's what I did.
After the installation the phone rebooted back to TWRP Recovery so I wiped cache, data and dalvik.
It still rebooted back to TWRP recovery so I tried to reinstall LineageOS again by following these steps: https://wiki.lineageos.org/devices/h870/install#installing-lineageos-from-recovery
The phone still only boots to recovery so my assumption, after some reading on XDA, is that something is wrong with the bootloader.
This could have happened when I was tinkering with Magisk, I think I've seen a notice that I tried to make changes to the bootloader.
To fix the bootloader the main suggestion is to flash the stock rom so i've started that path.
I've installed Uppercut and LG Up use links from this thread: https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295/
I found a stock rom at https://lg-firmwares.com/lg-h870-firmwares/#firmwaresList and I assume I need the "NEU/NORTHERN EUROPE" rom.
When I open Uppercut it says "There is no handset connected".
I've got no clue what steps to take at this point.
FYI I'm able to get in to the bootloader mode and the recovery mode but havent been able to get into the download mode.
Click to expand...
Click to collapse
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers
Boneface Johnson said:
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers
Click to expand...
Click to collapse
I had the same problem, this command worked for me, thanks!
Boneface Johnson said:
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers
Click to expand...
Click to collapse
Worked for me too. Many thanks.
Boneface Johnson said:
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers
Click to expand...
Click to collapse
Thanks, your solution worked for me too
Same happend to me, there are some post that say you have to boot to bootloader and send bootloader continue command with your PC, however that didn't work for me. To flash with LG UP you have to have your phone off, connect USB cable to PC, press Vol+ on phone and connect the USB cable to the phone, it should start in a mode called download mode, then LG UP should find your device

Categories

Resources