Hi everyone.
I tried to update LineageOS today on my G6. The phone rebooted to TWRP but didn't install the upade. I navigated to the downloaded update zip and flashed it manually and flashed dalvik and cache after that. Sadly the phone got stuck on TWRP and I couldn't boot to the system. I searched the forums and found a few posts saying that doing:
dd if=/dev/zero of=/dev/block/platform/<some folder>/by-name/misc
dd if=/dev/zero of=/dev/block/platform/<some folder>/by-name/fota
should solve the problem. Sadly after rebooting my phone got stuck in a loop saying "Your device is corrupt. It cannot be trusted and will not boot." I can't boto to TWRP. Only download mode is available it seems. I tried to install lgup but sadly is lists my phone model as unknown and I can't get to the main screen to flash a factory rom and start over. I'm no pro in flashing/customizing phones so I supposedly missed something.
Any help appreciated
You need to install uppercut for it to recognise your phone
Related
Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks
Skroutz said:
Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks
Click to expand...
Click to collapse
are u stuck in cmw recovery??
Stock recovery.... :/
Sent from my GT-I9100 using XDA Free mobile app
Same Problem here! Exact Same
Also having this issue, stuck in the secure boot loop, can't get to download mode.
Im exactly the same - im stuck in TWRP and cant boot into Download mode at all - just get the LG Bootscreen then straight into TWRP Recovery no matter what i do
Did we all except some kind of update from LG........ i wonder if this the link here and is now a common problem?
Mine was this and i thought it was just an app update for the stock apps and now im stuck big time
Any luck guys or solutions then please post here so we can keep it together and help each other!
Yeah I got an OTA update for my D803-Bell model, upon restart entered the secure boot error loop.
Sounds like, via this thread that it's commonly happening to people who had TWRP or CWM (or even aborted / possibly never completed installs like me) got nailed.
As per that thread, and everything else, I've tried every option possible -- no download mode. Recovery mode doesn't restore anything, just resterts to lg logo -> secure boot error -> black screen. Shows as QSHSUSB_BULK in windows/linux, and I can see those 25 partitions in linux (but reflashing openrecoverytwrp__.img over the recovery partition didn't help. I'm waiting to find out how I can make my own copies of those various partitions listed, from another D803-Bell model I have access to. All the D803 .img files on those links in that thread, appear to not contain D803 Bell stuff, just Telus, Rogers, etc... so I'll likely have to source my own.
I just took a shot in the dark recommended by a friend -- and fixed my phone.
I zeroed out the 'fota' partition on the phone. As seen in this thread ; http://forum.xda-developers.com/showthread.php?t=2451696
Just did a dd if=/dev/zero overtop of the fota partition, which was 25 for me from my linux box. One quick power cycle later, and I'm fully functional again, and the OTA update that killed me is still showing as available again.
Hi guys,
I am using Samsung Galaxy Note 3 N9005 with v4.3 (Jelly Bean) and 4.3 bootloader. I have been using TWRP version 2.8.0.2-hlte-4.3 for quite a while.
Decided to update to twrp-2.8.7.0-hlte-4.3 today. I followed the "DD Install method (terminal)" mentioned in http://teamw.in/devices/samsunggalaxynote3internationalqualcomm.html and installed the new version without any problem. Rebooted into recovery, cleared cache and delvik and restarted to go to system.
However it is showing the following message and rebooting into recovery, and not system -
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING...
Set Warranty bit : recovery
Recovery is working fine. I have put lastest TWRP image file in Sd card and flashed again from recovery. I have restored 'boot' from an old backup. But still no go.
My gut feeling is that everything is fine and there is an easy solution to this problem, without factory reset. May be a command line, something similar to the one found here - http://forum.xda-developers.com/showthread.php?t=2451696 will do the trick. I tried this very command, didn't help.
Could someone help? Thanks in advance.
In case it helps, this is the command I used to update TWRP -
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Then rebooted into recovery and cleared delvik and cache.
anyone solve this problem? I have the same issue.
TWRP 2.8.7.0
Once I'm in recovery, rebooting system reboots back into recovery. I can only get back into system by booting into download mode then cancel out of it
Hey, sorry for the ignorance!
I flashed this ZUI (Nougat) rom on top of CM 13 data, phone did boot with old apps. When i pressed factory reset from settings menu the phone went to recovery and since then its only booting into recovery and not into system! everytime i get into TWRP system is not checked. even after mounting system and flashing stock zip. The phone isn't booting into system but recovery only. Tried flashing system.img by Fastboot.
Solved by using QFIl
Flash stock recovery, then boot into recovery.
It will automatically do factory reset, after that your system partition will boot.
Then flash TWRP again.
And do remember, not use Factory reset option from OS while on custom recovery.
Had the same issue, went to fastboot and then flashed through adb. Worked as a charm.
Hi there,
I installed RR os nougat on my phone about a month ago
Since then it was working perfectly fine ,
But today when I tried to interchange my sims the disaster happened
Now my phone is not booting
1st after pressing power button it shows zuk logo and then boots in twrp recovery
And I tried wiping and installing the ROM again but still the problem is there ....
It is not booting in system partition
Please someone help ......
GOKU07 said:
Hi there,
I installed RR os nougat on my phone about a month ago
Since then it was working perfectly fine ,
But today when I tried to interchange my sims the disaster happened
Now my phone is not booting
1st after pressing power button it shows zuk logo and then boots in twrp recovery
And I tried wiping and installing the ROM again but still the problem is there ....
It is not booting in system partition
Please someone help ......
Click to expand...
Click to collapse
Try the above mentioned solutions as flashing stock recovery and then stock OS and then TWRP!
I used QPST method to flash Chinese ZUK ROM through QFIL , and then flashed CM 13 later on. :good:
I flashed stock firmware through fastboot and it booted and then flashed twrp and due ROM !! Now working perfectly fine !! Thanks for help
any idea where i can find stock firmware and recovery? the urls which i find via google are no longer online -_-
akshaybjp said:
Hey, sorry for the ignorance!
I flashed this ZUI (Nougat) rom on top of CM 13 data, phone did boot with old apps. When i pressed factory reset from settings menu the phone went to recovery and since then its only booting into recovery and not into system! everytime i get into TWRP system is not checked. even after mounting system and flashing stock zip. The phone isn't booting into system but recovery only. Tried flashing system.img by Fastboot.
Solved by using QFIl
Click to expand...
Click to collapse
I had the same issue. Solved?
SOLVED!
Go to : https://www.youtube.com/watch?v=vSWC5MAB5cE
For TWRP
If You have TWRP follow this thread https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the terminal is in advanced menu.......
drtarga said:
any idea where i can find stock firmware and recovery? the urls which i find via google are no longer online -_-
Click to expand...
Click to collapse
Can be found here https://forum.xda-developers.com/showpost.php?p=71415281&postcount=6
How to switch off the phone stuck in zUK logo with no recovery installed. I tried long pressing the home button but it reboots to zuk logo ,is there any way to switch off the phone
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.
Hello,
I am into a TWRP boot loop.
- I can boot into TWRP
- I can update ROMs
- I can update TWRP
- I can connect to the computer and send files using mtp://[usb:001,003]/
- I can Wipe ...
But when I reboot into the system, regardless of the ROM that I use, I get again into recovery
I have read in some posts that from the TWRP command one could try to clear the first sectors of the misc partition
For instance for a Lenovo ZUK Z2 (Plus) in https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14 it is said that this could help
"dd if=/dev/zero of=/dev/block/platform/soc/7464900.sdhci/by-name/misc"
but ... I cannot find the misc partition in /dev from the TWRP shell ("find /dev -name misc") !
Could someone help me with this one ? I would appreciate it a lot !
Regards
Same problem on MadOS 8.1 (MT6752)!
TWRP loop
Just flash old stock 5.1 Android ROM through Flash Tool. Its pretty easy. Then turn it, turn it off and wipe data. restart TWRP, upgrade TWRP and install new Android 8.1 and gapps. Turn the phone on and its finished. You can do recovery now for the next instalation if you want. I am doing this often because I have same problem for several months. Fortunetaly google backup works pretty fine so its not problem with installing apps again. The command you wrote above doesnt work for me.
I'm having the same problem. I was using my phone today, when it started to show wifi problems (couldn't connect); so, I rebooted it and its screen started to blink; when I rebooted it again, it automatically entered into recovery mode (TWRP). After this, the phone didn't boot normally (MadOS Android 8.1) anymore - only TWRP. Even when I try to charge it, it boots into TWRP mode instead of showing the battery animation.
In my attempts to solve the problem, I firstly reinstalled the MadOS 8.1 ROM but it kept booting into TWRP mode. So I flashed an old Android 5.1 ROM I got (connected and uploaded the device successfully with SP Flash Tools) but it also kept booting into TWRP (now an older version from the 5.1 ROM). Then I uptadated the TWRP and the OS again to MadOS 8.1 but the result was the same.
With any other alternative, I came accross this topic and tried the steps described above (practically identical to what I just did), but again I hadn't any positive results.
What else could I do?
Hello,
I have finally resolved my issue !!!
a) Using "SP_Flash_Tool_v5.1824_Win" and the "RC5_S3_16GB.zip" stock rom I flashed it using ---->>>>> "firmware upgrade" mode <<<<-------.
The option you can find it in Smart Phone Flash Tool, between the "Authentication File" and the table with the partitions.
b) Once done with the flasshing, boot the telephone into the Stock fimware
c) Boot into recovery (power + volume up) and flash the latest TWRP
d) Flash you new ROM
Do not hesitate to ask me if you have questions.
imascara said:
Hello,
I have finally resolved my issue !!!
a) Using "SP_Flash_Tool_v5.1824_Win" and the "RC5_S3_16GB.zip" stock rom I flashed it using ---->>>>> "firmware upgrade" mode <<<<-------.
The option you can find it in Smart Phone Flash Tool, between the "Authentication File" and the table with the partitions.
b) Once done with the flasshing, boot the telephone into the Stock fimware
c) Boot into recovery (power + volume up) and flash the latest TWRP
d) Flash you new ROM
Do not hesitate to ask me if you have questions.
Click to expand...
Click to collapse
Thanks! With this method, I solved the problem, identical to yours !!
Hello guys,
I broke my Suez - I need some help.
I went through all the pain of opening up and unbricking it with amonet-suez-v1.1.2.zip from https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/.
Then I was in TWRP, I think 3.2.sth.
I tried to adb sideload the latest lineage for my device from this thread: https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/
The installation finished with a red error message like /data partition not found.
I restarted the tablet, which is now stuck in a lineage os bootloop.
I thought the problem might be not having the most recent TWRP. So I brought the tablet into hacked-fastboot, and flashed TWRP 3.6.1.2, from https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/, which succeeded.
Not I can not even access my recovery anymore. When I try to with volume and pwr, the screen stays black and the tablet resets, ending in the TWRP bootloop.
A) why is the lineage in a bootloop
B) What about the /data partition missing error
C) How to get my TWRP to work again?
I can redo the unbricking stuff, but I would lang in the exact same situation. Where should I try different stuff?
I could think of replacing the old TWRP of amonet-suez with the most recent version, and then do the unbrick procedure with shorting again.
Push. I need help.