Hi guys,
After an update to 30th March nightly on Lineage OS (had only migrated from CM 12.1 OS to Lineage OS a day before with the 23rd March nightly), the boot got stuck to TWRP.
I could get into the Fastboot mode while TWRP was accessible.
Tried reverting back to stock ROM manually (& with a lot of guesswork) and the "fastboot flash system system.img" command was stuck too long on sending; I rebooted manually and the Cyanogen recovery showed up next with a error message. I pressed a button by mistake and since then the phone is stuck on the Zuk+powered by Android boot screen. Would appreciate help as it is no longer entering Fastboot or Recovery.
Update: somehow got into Cyanogen recovery after I had kept the phone away after trying many times. Have connected the phone to the computer but have no clue what to do next. Would appreciate exact steps with commands to get out of this mess.
Badly screwed this up. Was only beginning to enjoy the new Lineage OS when this series of mishaps and errors happened. :crying:
Connect your Lenovo ZUK Z1 device to your computer via USB and run this command as root: adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
(try this in recovery mode)
You can also go to the TWRP terminal and run: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
This solves your problem..
Thank you
First somehow you will need to find a way to switch your phone off and then follow this : https://www.youtube.com/watch?v=9t1HMXfO5ic
thanks srk, bhattyash.
i couldn't figure out how to do your method; couldn't locate = on the twrp screen and didn't know how to exactly give the adb shell command; so didn't attempt your methods.
i however tried flashing again manually; this time the system flash command changed into something that breaks up the system img into files less than 512 kb/mb or so. can't locate that very helpful flash command; but that's what helped me boot back to stock ROM
Hello there,
I have exactly the same issue, cant get in fastboot or recovery mode, just the black screen with "ZUK powered by android" logo. i tried connecting the phone to my computer and it recognize my zuk as " ShenQi Composite ADB Interface " . When i run power shell in my adb folder, after type adb devices i get "List of devices attached" but no devices at all in that list just an empty line.
The YouTube link doesn't work and I can't fully undesrtand how did you fix your phone, I don't know what to do.
Thanks and excuse my bad English !
Related
Fixed using the same method as post 13 in this thread http://forum.xda-developers.com/lg-g2/help/vs980-twrp-bootloop-botched-lollipop-t3072133/page2
Hello phone gurus- sorry for my noobiness!
So- I HAD my phone working great- rooted- hotspot (I'm still on unlimited plan)
ACCIDENTALLY installed the OTA (after many weeks of ignoring it)
Then my phone wouldn't boot BUT I could get into TWRP
I tried using the console as posted in another thread (sorry can't post the link- I'm too new!)
but I entered this at the TWRP console:
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
At this point I received a message that I didn't have enough disk space after typing the commands as shown.
Then I rebooted and my TWRP is gone...
Now I'm stuck at the LG logo, with no TWRP. Hold vol up, vol down, rebooted many times nothing seems to work, just the LG logo.
I have ADB on my win machine and it was recognizing the phone, but now it doesn't.
In device manager I show three devices when I boot phone with USB attached:
CDC ECM- No driver
CDC SERIAL- recognized as modem
LGE ANDROID PHONE- No driver
Its been at the LG logo for about 30 minutes now.
Help Please!:crying:
the problem is that you have the phone rebooted to twrp ,but the screen is black and seems adb
1.Wait for 5 to 10 minutes until the phone goes into twrp
2.You can check the "back"button if it vibrates,then you are on the right track
3.To find adb sideload ,I personally enjoyed another device to see where it is
4.Further connected to the computer and write
Adb kill-server
Adb usb
Adb devices(if written sideload means you entered)
And the team flash a Rom (better than the usual stock(not twrp))adb sideload rom name.zip rom name=the name of your .zip)Any LP stock Rom(if you finish early,it's nothing)
5.Further prescription adb reboot
6.Your phone reboots and then you'll be able to go to fastboot by holding the+button to zoom.volume
7.Then fastboot flash a greenshank sorg
And oops,there bootanimation and logo asus
Go into Rom and enjoy,if you want then reboot
8.in fastboot And flash twrp:
Adb kill-server
Fastboot flash recovery recovery.img
9.Next, choose Twrp in fastboot.And rejoice
Tested in Z008 and Z00A
P. s This is how I coped with such a problem
PS.s In twrp ,the device may be blocked,if it was there,you just have to swapnote from left to right to unlock the device
PS.s.IMPORTANT: after upgrading, even with a clean 184, then make a full reset in the settings, after a couple of minutes you may find that your phone becomes unresponsive, but it isn't! After a couple of minutes it reboot in recovery and do factory reset! After that, missing a sufficient number of bugs ranging from drop google services, and what's not sincenot contacts, not the arrival notification and so on.
Russiamen said:
the problem is that you have the phone rebooted to twrp ,but the screen is black and seems adb
1.Wait for 5 to 10 minutes until the phone goes into twrp
2.You can check the "back"button if it vibrates,then you are on the right track
3.To find adb sideload ,I personally enjoyed another device to see where it is
4.Further connected to the computer and write
Adb kill-server
Adb usb
Adb devices(if written sideload means you entered)
And the team flash a Rom (better than the usual stock(not twrp))adb sideload rom name.zip rom name=the name of your .zip)(if you finish early,it's nothing)
5.Further prescription adb reboot
6.Your phone reboots and then you'll be able to go to fastboot by holding the+button to zoom.volume
7.Then fastboot flash a greenshank sorg
And oops,there bootanimation and logo asus
Go into Rom and enjoy,if you want then reboot
8.in fastboot And flash twrp:
Adb kill-server
Fastboot flash recovery recovery.img
9.Next, choose Twrp in fastboot.And rejoice
Tested in Z008 and Z00A
P. s This is how I coped with such a problem
PS.s In twrp ,the device may be blocked,if it was there,you just have to swapnote from left to right to unlock the device
PS.s.IMPORTANT: after upgrading, even with a clean 184, then make a full reset in the settings, after a couple of minutes you may find that your phone becomes unresponsive, but it isn't! After a couple of minutes it reboot in recovery and do factory reset! After that, missing a sufficient number of bugs ranging from drop google services, and what's not sincenot contacts, not the arrival notification and so on.
Click to expand...
Click to collapse
giving this a crack now -- seems to be my case -- a few beer tokens going your way if this does it
Russiamen said:
the problem is that you have the phone rebooted to twrp ,but the screen is black and seems adb
1.Wait for 5 to 10 minutes until the phone goes into twrp
2.You can check the "back"button if it vibrates,then you are on the right track
3.To find adb sideload ,I personally enjoyed another device to see where it is
4.Further connected to the computer and write
Adb kill-server
Adb usb
Adb devices(if written sideload means you entered)
And the team flash a Rom (better than the usual stock(not twrp))adb sideload rom name.zip rom name=the name of your .zip)(if you finish early,it's nothing)
5.Further prescription adb reboot
6.Your phone reboots and then you'll be able to go to fastboot by holding the+button to zoom.volume
7.Then fastboot flash a greenshank sorg
And oops,there bootanimation and logo asus
Go into Rom and enjoy,if you want then reboot
8.in fastboot And flash twrp:
Adb kill-server
Fastboot flash recovery recovery.img
9.Next, choose Twrp in fastboot.And rejoice
Tested in Z008 and Z00AOk so
P. s This is how I coped with such a problem
PS.s In twrp ,the device may be blocked,if it was there,you4 just have to swapnote from left to right to unlock the device
PS.s.IMPORTANT: after upgrading, even with a clean 184, then make a full reset in the settings, after a couple of minutes you may find that your phone becomes unresponsive, but it isn't! After a couple of minutes it reboot in recovery and do factory reset! After that, missing a sufficient number of bugs ranging from drop google services, and what's not sincenot contacts, not the arrival notification and so on.
Click to expand...
Click to collapse
In Step 4, Can i flash the stock lp rom? Will it work?
Ravi Kumawat said:
In Step 4, Can i flash the stock lp rom? Will it work?
Click to expand...
Click to collapse
Yes
Can I downgrade to lollipop with this method?
If yes, I think you should make a new thread how to downgrade from Marshallow to lollipop, some people want to downgrade but they don't know how to do it.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
BesFen said:
Can I downgrade to lollipop with this method?
If yes, I think you should make a new thread how to downgrade from Marshallow to lollipop, some people want to downgrade but they don't know how to do it.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Click to expand...
Click to collapse
No,use AsusFlashTool and Raw stock rom
I'm unable to understand your english ;-;
I'm stuck with the same problem. I originally had a ResurrectionRemix rom running on my Zenfone and then tried to flash one of the stock Marshmallow roms provided by Asus.
Hi,
i tried to update my phone via the integrated updater. It did not start the update and now fails booting into android. it boots every time into twrp.
i tried several possible solutions:
reflash other version
reflash the latest version
flashed fulmics
factory wipe
reflashed twrp
tried to
inshadesofgrey said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
but failed
now i am out of knowledge...
has anyone an idea?
Regards!
Christian
did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM
one_ctrl said:
did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM
Click to expand...
Click to collapse
Is there any better solution for this problem?
I solved it once with a full reinstall an this uppercut tool.
On reddit for other phones there is the solution to boot to bootloader and do
Code:
fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.001s
But this does not work.
It seems my phone boots to twrp because the lineage os updater app set s.th. to automatically boot to twrp. How can we remove this auto-boot to twrp flag?
Sorry for bringing up this again. I did an OTA update on lineageos on my lg g6. The phone booted correctly in twrp, I installed the update but now the phone boots directly to twrp without any way to let it boot the os. How did you resolve this?
Thanks
Only solution back to stock & after install LOS and wait until bug is fixed.
I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted
Someone else has had this problem @gnackwatschn, you can find a way to fix the boot loop here https://forum.xda-developers.com/lg-g6/help/twrp-bootloop-lineageos-ota-update-t3746014/post75488796#post75488796
WARNING [brick]
eng3 said:
I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted
Click to expand...
Click to collapse
WARNING! I ran into the same problem on the LG G6 with the nightly update dated Nov 1, 2018. Did what you did, but wrote down the command.
After navigating to the TWRP > Advanced > Terminal, first do
Code:
ls /dev/block/platform
Mine had one entrie: soc, which had two entries: 624000.ufshc and 74a4900.sdhci
only 624000.ufshc had a by-name directory containing fota and misc, so my commands ended up being:
Code:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
The commands run, saying:
Code:
dd: writing '/dev/block/platform/soc/624000.ufshc/by-name/fota': No space left on device
8193+0 records in
8193+0 records out
4194304 bytes (4.0MB) copied), 2.783000 seconds, 11.5MBs
and similar for misc.
Reboot to system gives a warning, Your device has failed a routine safety check and will not boot.
Now I'm stuck.... guess its time to start another thread.
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
Hello, I need your help, if possible.
I have a Galaxy Note 8.0 N5120 (LTE Model), which was running rooted stock rom 4.4.2.
Then, I wanted to update it to a newer Android version, and I found RR (=Resurrection Remix) , which is 7.1.2. I updated Recovery to TWRP and started testing (RR 5.8.4 and 5.8.5).
During testing, I changed versions of TWRP, too.
The main reason for testing is that in the beginning, USB OTG was not working, and with 5.8.5 usb otg was working and I was happy!! However, at some time later, USB OTG started not working, So, I thought it must be a harware issue. Then I noticed I had no baseband, no IMEI!! (I must have lost it sometime in the process of testing, because with 4.4.2 everything was working!!)
SO, I did a lot of search, and I tried the following.
First, I flashed back to original stock rom (4.4.2)
As I had "efs.img" (which I probably made with Philz Touch many years ago). I changed recovery to Philz Touch, but could not restore. So, I searched and I found a way to flash it with Philz Touch. (Before flashing I deleted all the folders and files in efs dirtory, and after flashing, I checked that the folders and files were there.)
But, still no baseband, no IMEI....
So, I searched again and I found out that erasing modemst1 and modemst2 could solve the issue.
First, I tried in TWRP (advanced - Terminal)
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
gives "no such file or directory"
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
gives "no such file or directory"
So, I setup adb in my PC (Windows 7 64bit), and started testing.
1) adb devices
gives "xxxxxx unauthorrized"
On the phone, I authorized and, then it gives "xxxxxx device"
So, I presume the connection is establed with the phone.
2) adb reboot bootloader
The phone reboots but in normal android mode (4.4.2)
I searched again, and I found out Samsung phones don't support fastboot...(I can not use fastboot commands...)
Just to check, I put the phone in Download mode (home + volume up and power on). Then I connected it to my PC, but the phone is not detected.
As adb seems to work, I tried the following.
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
gives "cannot open for write: No such file or directory"
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
gives "cannot open for write: No such file or directory"
(So, it does seem like adb works, but maybe modemst1 and 2 are in a different location...)
I have no more idea...
Is there anything I can try?