I have device, kernel and vendor AOSP source available for my device. I'm trying to port LineageOS to my device. After a lot of work I was able to compile it. The kernel works just fine with the AOSP ROM but CWM only give black screen and the ROM not boot at all. It's just stop at the manufacturer splash screen, not even the boot animation comes in. It's mean no adb and no logcat. What's can cause this or how can I debug this problem ?
Try to fix the recovery first so you can debug the rom and isn't CWM discontinued already so try compiling TWRP or Cyanogen Recovery instead and it might boot.
3liteking148 said:
Try to fix the recovery first so you can debug the rom and isn't CWM discontinued already so try compiling TWRP or Cyanogen Recovery instead and it might boot.
Click to expand...
Click to collapse
I see thanks!
I have working TWRP recovery. Not my build but it's working. But how can I debug this?
And how can I found out what's wrong with the recovery?
Could found some info about the not working recovery by flashing a working one and getting last_kmsg after reboot.
"Untracked pid 280 exited with status 1"
Now how can I go deeper in debug? Is last logcat available somewhere just like last Kernel msg?
If you meet bootloop, you have to flash a rom which same android version like nougat. Allow ADB permission and reboot to recovery. Flash your rom without wiping data & cache. Get logcat with adb command and debug !
ps : i didnt read full, cant solve your problem
hiimpig1 said:
If you meet bootloop, you have to flash a rom which same android version like nougat. Allow ADB permission and reboot to recovery. Flash your rom without wiping data & cache. Get logcat with adb command and debug !
ps : i didnt read full, cant solve your problem
Click to expand...
Click to collapse
The main problem is the ROM I build not boots at all. It's mean no ADB and no logcat. Same with the recovery. Except it at least skip the manufacturer logo but still not ADB in recovery as well. Only the kernel works.
Gaboros said:
The main problem is the ROM I build not boots at all. It's mean no ADB and no logcat. Same with the recovery. Except it at least skip the manufacturer logo but still not ADB in recovery as well. Only the kernel works.
Click to expand...
Click to collapse
bump! ?
I have my answer from 3liteking148 at reddit. I write it down because it could be useful for someone and don't have to read through a lot of comment. This method required working recovery with adb or with file explorer. If the phone stuck at the manufacturer logo just reboot and get the files from /data/tombstones. The required information will be written there.
Gaboros said:
I have my answer from 3liteking148 at reddit. I write it down because it could be useful for someone and don't have to read through a lot of comment. This method required working recovery with adb or with file explorer. If the phone stuck at the manufacturer logo just reboot and get the files from /data/tombstones. The required information will be written there.
Click to expand...
Click to collapse
how do you get tumbstone
Related
I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].
I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.
I have also tried to use this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.
So at this point now I can only access bootloader and the recovery which does not show partitions.
At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.
SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img
This allowed TWRP to work.
Thanks to Batfink33 and lynnux
You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
lynnux said:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
Click to expand...
Click to collapse
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Batfink33 said:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Click to expand...
Click to collapse
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
lynnux said:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
Click to expand...
Click to collapse
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Batfink33 said:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Click to expand...
Click to collapse
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
a4abbas said:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
Click to expand...
Click to collapse
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Batfink33 said:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Click to expand...
Click to collapse
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
a4abbas said:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
Click to expand...
Click to collapse
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
theminikiller said:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
Click to expand...
Click to collapse
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
a4abbas said:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
Click to expand...
Click to collapse
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
theminikiller said:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
Click to expand...
Click to collapse
You must be right, it make sense.
I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.
You did the unlock bootloader bit in settings?
ReneX10 said:
You did the unlock bootloader bit in settings?
Click to expand...
Click to collapse
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.
GigahurtzUK said:
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.
Click to expand...
Click to collapse
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment
ReneX10 said:
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment
Click to expand...
Click to collapse
No other devices to test with.
I will have to try linux then. I just need a usb to make a linux live usb
Cheers
GigahurtzUK said:
I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.
Click to expand...
Click to collapse
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.
Is this the norm when changing recovery.img?
M_Kay said:
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.
Click to expand...
Click to collapse
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?
noob2016 said:
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?
Click to expand...
Click to collapse
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.
Thanks for the fast reply and help
M_Kay said:
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.
Click to expand...
Click to collapse
1st thanks for fast reply and help
im not in bootloop, thank goodness!
I'm currently in TWRP, when the recovery was in CM the gapp-arm64-aroma-5.1 it installed flawlessly following the cm12.1 flash but after the update 13.0 the gapp can't be installed even reverting back to 12.1 and using the same files. I did wipe all prior to change of rom also match it (i.e. cm13.0 to gapp 6.0).
Maybe this will solve it. I will try to erase recovery and re-install TWRP
i will report back after. Thanks
Works
Thanks it worked on pico gapp but not in aroma
followed the erase command and install TWRP again.
Many thanks
TWRP not working in Aroma Gapp need fix
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
noob2016 said:
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
Click to expand...
Click to collapse
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP
Thanks
robin0800 said:
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP
Click to expand...
Click to collapse
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb
noob2016 said:
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb
Click to expand...
Click to collapse
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial
I will try
robin0800 said:
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial
Click to expand...
Click to collapse
Thanks for the reply and also on my other post.
Since this is for swift, i will try to install but sadly i have given it back already. It was just here for the upgrade and when i got the chance to get hold of it again i will definitely try and report back.
Many thanks.
Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks
msiviter said:
Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
robin0800 said:
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
I think it was a windows 10 problem, I gave it all another try this morning firstly using the WinDroid Universal Android Toolkit to Unlock Bootloader and flash TWRP . I then rebooted into recovery and hey presto TWRP. Flashing CM13 nightly and pico gapps was then childsplay.
Any ideas why google play didnt offer to auto restore all my apps? Thats a bit of a pain.
Otherwise very pleased, phone seems a bit more responsive using CM13 than CyanogenOS. I tried to format my SD to use as internal storage too but i couldnt see them separately afterwards to free up device storage so I reverted back.
Thanks for trying to help.
Yey!!!
robin0800 said:
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
Confirmed!!! It works... i used TWRP 3.0. Works on both aroma and pico. Thanks so much!!!!
Got stuck in a TWRP loop after installation. Regardless which reboot option I choose, always TWRP 3.0.0 comes up. No idea what I did wrong but for me it is of more interest how to get rid of it. Accessible external SD contains cm14-zip and also Stock 6.0.1. Installed CM14 multiple times, but has no impact on what comes up after selecting reboot/reboot recovery/reboot fastboot - it is always TWRP. Tried it also via adb sideload from within TWRP, no change of behaviour. Same when I tried to install stock rom.
Bootloader issue? How to get it back? I have 2 further Swifts available so I can dump several necessary partitions from them, but I need to know which tools are required, since I usually deal with MTK-based androids. Backup of userdata and sdcards is available, so if a reset to stock is necessary, this is not a problem from that point of view - if I only would have the info, how to get back a working bootloader.
Even though I love this recovery, it is obviously annoying ... Any help appreciated. Tnx in advance!
Edit: Fixed. I removed the battery for several hours and without battery with plugged in USB cable (not the WF one, I have tons of them lying arround here) I was able to reboot to normal fastboot. From then on it was strraightforward:
checked OEM lock status via fastboot command on PC
flashed newest TWRP
rebooted to TWRP
installed Stock ROM to get all partitions reinitialized correctly
rebooted to OS - YEAH, the swift lives again
Rebooted to recovery
Installed CM14 and OpenGApps Nano (ARM, not ARM64, since it produces an error)
Reboot to OS - YEAH, here we are.
Hello,
I have been trying to go trhough google searches and this forum for a while now
Situation,
Had a working OP3 completely stock until this afternoon (not sure which ROM but latest OTA from stock)
- I currently dont have access to a windows PC and I am using ubuntu on a chromebook (chrubuntu)
Steps
I unloacked bootloader - successfully
I installed TWRP - successfully
Installed latest CM14.1 - successfully
After first boot Phone stopped rebooting. I tried to wipe everything and after this, I dont have a partition in my file explorer (on Ubuntu) therefore can't copy files to install
I tried to adb sideload. I get "error: Protocol (no status)"
Only thing that seems to work is fastboot
I have tried to install CM-14.1 recovery or original recovery but only CM14.1 works
It seems complete phone (system/boot/img) are wiped and therefore can't start.
Do you have any ideas? would like to unbrick the phone
Thank you
BeerFreek said:
Hello,
I have been trying to go trhough google searches and this forum for a while now
Situation,
Had a working OP3 completely stock until this afternoon (not sure which ROM but latest OTA from stock)
- I currently dont have access to a windows PC and I am using ubuntu on a chromebook (chrubuntu)
Steps
I unloacked bootloader - successfully
I installed TWRP - successfully
Installed latest CM14.1 - successfully
After first boot Phone stopped rebooting. I tried to wipe everything and after this, I dont have a partition in my file explorer (on Ubuntu) therefore can't copy files to install
I tried to adb sideload. I get "error: Protocol (no status)"
Only thing that seems to work is fastboot
I have tried to install CM-14.1 recovery or original recovery but only CM14.1 works
It seems complete phone (system/boot/img) are wiped and therefore can't start.
Do you have any ideas? would like to unbrick the phone
Thank you
Click to expand...
Click to collapse
Flash this recovery in fastboot
https://www.androidfilehost.com/?w=...cb8f6e7e3ae3b22eeb701f45ff43773a7ebdfe1009fa9
Enter recovery and flash
https://www.androidfilehost.com/?fid=529152257862675332
Then flash cm14.1 + gapps
Dont forget to wipe system data cache before
nadejo said:
Flash this recovery in fastboot
https://www.androidfilehost.com/?w=...cb8f6e7e3ae3b22eeb701f45ff43773a7ebdfe1009fa9
Enter recovery and flash
https://www.androidfilehost.com/?fid=529152257862675332
Then flash cm14.1 + gapps
Dont forget to wipe system data cache before
Click to expand...
Click to collapse
Thank you, just recoevered the phone with the modded TWRP from this post http://forum.xda-developers.com/one...mate-guide-t3497940/post69566175#post69566175
Question is, what are the mods on the recovery? can modded recoveries give 3rd parties access to your system?
Thanks for the quick reply, I would just like to understand what is going on so it doesn't happen again. When will it be ok to flash official TWRP?
BeerFreek said:
Thank you, just recoevered the phone with the modded TWRP from this post http://forum.xda-developers.com/one...mate-guide-t3497940/post69566175#post69566175
Question is, what are the mods on the recovery? can modded recoveries give 3rd parties access to your system?
Thanks for the quick reply, I would just like to understand what is going on so it doesn't happen again. When will it be ok to flash official TWRP?
Click to expand...
Click to collapse
No, dont be afraid of that. The recovery is simply modded to allow booting 3.5.5 based operating systems.
The recovery partition cannot share any information to any third parties because its limited to a partition that is only active when you boot to recovery and the operating system is not running. And the operating system is running independent from the recovery you are using. There is no activity between your recovery and your system/data/cache or watever partition. Because they are complete different boot states. Only action is durring the installation or wiping processes in recovery. Or if you are flashing mods/roms/kernels or changing&updating your recovery with root apps like flashify. But again it only gives a command for a flash process or wipe process to the recovery. A recovery is not able to run any kind of service app so it is not able to share any kind of information to anyone.
nadejo said:
No, dont be afraid of that. The recovery is simply modded to allow booting 3.5.5 based operating systems.
The recovery partition cannot share any information to any third parties because its limited to a partition that is only active when you boot to recovery and the operating system is not running. And the operating system is running independent from the recovery you are using. There is no activity between your recovery and your system/data/cache or watever partition. Because they are complete different boot states. Only action is durring the installation or wiping processes in recovery. Or if you are flashing mods/roms/kernels or changing&updating your recovery with root apps like flashify. But again it only gives a command for a flash process or wipe process to the recovery. A recovery is not able to run any kind of service app so it is not able to share any kind of information to anyone.
Click to expand...
Click to collapse
Thanks that is quite explanatory... Running smoothly so far. It's good to learn something every day...
Big thumbs up
Hi,
I made a CM14 update yesterday, but since then, my phone boots in recovery mode. I tried to reinstall TWRP, in current and previous versions, and other roms (I can flash), but nothing works; each time I reboot, TWRP appears...
Any hint ?
Thanks very Much !
gdoucou said:
Hi,
I made a CM14 update yesterday, but since then, my phone boots in recovery mode. I tried to reinstall TWRP, in current and previous versions, and other roms (I can flash), but nothing works; each time I reboot, TWRP appears...
Any hint ?
Thanks very Much !
Click to expand...
Click to collapse
Try to install my latest BETA (check my signature)
steadfasterX said:
Try to install my latest BETA (check my signature)[/QUOT
Hi, thanks for your answer. I tried, but it still reboots on TWRP... (tried to install AICP).
There's an error message when installing :
patching system image unconditionnally
E:unknown command [log]
But it keeps going on with "dectected filesystem ext4 for /dev/boot [...]
Then it reboots in recovery...
Click to expand...
Click to collapse
gdoucou said:
steadfasterX said:
Try to install my latest BETA (check my signature)[/QUOT
Hi, thanks for your answer. I tried, but it still reboots on TWRP... (tried to install AICP).
There's an error message when installing :
patching system image unconditionnally
E:unknown command [log]
But it keeps going on with "dectected filesystem ext4 for /dev/boot [...]
Then it reboots in recovery...
Click to expand...
Click to collapse
Please try build 186
Click to expand...
Click to collapse
dont work for me same Probleme
TooThPicK said:
dont work for me same Probleme
Click to expand...
Click to collapse
Try my latest beta and if that is not working build 186
And which nightly causes that problem?
i think its not the recovery i test the cyanogen and this dont work
test installing stock but dont work
testet both not working
no Rom is working evrytime its boot to recovery
TooThPicK said:
i think its not the recovery i test the cyanogen and this dont work
test installing stock but dont work
testet both not working
no Rom is working evrytime its boot to recovery
Click to expand...
Click to collapse
Which cm version? tell exact build date.
Try to reflash stock kdz
Is there a way to Flash kdz from fastboot or recovery lgup dont find my device
ok i find the download mode now lgup find my device i downloading 20g and test
The issue is due to change in Google code not being compatible with TWRP.
I had the same issue, I flashed stock ROM with LGUP and then flashed CM14.1 after that.
Once your back up and running you can't use the in built updater, you have to download the update, manuay reboot to recovery and then flash.
Lgup dont find my device i only have recovery and fastbood
ceanth said:
The issue is due to change in Google code not being compatible with TWRP.
I had the same issue, I flashed stock ROM with LGUP and then flashed CM14.1 after that.
Once your back up and running you can't use the in built updater, you have to download the update, manuay reboot to recovery and then flash.
Click to expand...
Click to collapse
The change in Google code was the reason for one of the beta series I made. I was able to fix that in twrp even when this is no twrp issue. The internal updater worked fine afterwards when using any build after 15 of dec while using my latest beta.
That's why I ask several times what cm build they used (both do not answered this yet).
This is important so I can reproduce the issue and may can release a new twrp workaround if possible.
.
TooThPicK said:
Lgup dont find my device i only have recovery and fastbood
Click to expand...
Click to collapse
Not sure dude, best to post in the dedicated TWRP or cm14.1 thread.
its fixt thank you for your help the trick is turn off the g4 hold the + button and plugin the cabel now the device comes to downloadmode and now lgup is working
---------- Post added at 02:30 PM ---------- Previous post was at 02:28 PM ----------
steadfasterX said:
That's why I ask several times what cm build they used (both do not answered this yet).
This is important so I can reproduce the issue and may can release a new twrp workaround if possible.
.
Click to expand...
Click to collapse
on my is the nigtly from 23.12
I got the same problem booting permanently in TWRP.
Flashing the build (02.12.) I had before also doesn't work.
Some kind of tips here?
xXfreshXx said:
I got the same problem booting permanently in TWRP.
Flashing the build (02.12.) I had before also doesn't work.
Some kind of tips here?
Click to expand...
Click to collapse
Install my latest beta. I know that this do not solve the problem but then after flashing it try to boot into system. This will fail. Then pull the recovery log and provide it on http://paste.omnirom.org
If you don't know how to get that log it is easy. Check my FAQ #4 A.
http://forum.xda-developers.com/showpost.php?p=68249027&postcount=3
.
steadfasterX said:
Install my latest beta. I know that this do not solve the problem but then after flashing it try to boot into system. This will fail. Then pull the recovery log and provide it on http://paste.omnirom.org
.
Click to expand...
Click to collapse
Thanks for your reply
https://paste.omnirom.org/view/6e5948df
xXfreshXx said:
Thanks for your reply
https://paste.omnirom.org/view/6e5948df
Click to expand...
Click to collapse
Hm . This is really after a boot into system??...
Ok as I cannot see relevant data pls do the same again but with build 186 now. Provide the log again. The reason is that this build handles the bootloader commands in an other way and I may see then what I wanna see.
Thx
.
Hm . This is really after a boot into system??...
Ok as I cannot see relevant data pls do the same again but with build 186 now. Provide the log again. The reason is that this build handles the bootloader commands in an other way and I may see then what I wanna see.
Thx
.
Click to expand...
Click to collapse
Here you are.
https://paste.omnirom.org/view/594df4ce
xXfreshXx said:
Here you are.
https://paste.omnirom.org/view/594df4ce
Click to expand...
Click to collapse
Hm the reason for that reboot lays somewhere else...
Please tell me exactly what you had done to produce that loop:
Which exact version of cm installed before upgrading?
Upgraded with internal cm updater or by flashing new zip in twrp?
The above would help me to reproduce the issue.
Besides the short questions above it would be great if you could test 2 things for me and if not skip to 3 (if you're in hurry):
1. The hw key combo test
2. The force twrp test
3. Last resort LG up
1. The hw key combo test
Flash the latest beta twrp and reboot into this twrp
Create a full backup if not already done so!!!
Power off the device and pull out the battery
Use the hardware key combo to get into factory reset screen (press vol down + power and keep them pressed. plugin battery. Wait until you see the LG logo and then release only the power button for 1 sec then press it again and keep both pressed until you see the factory reset screen)
Follow through this process and twrp will showing up without resetting anything
Grab the recovery log and paste it again
Then try to reboot to system
2. The force twrp test
If the first method hasn't worked it would be great to see the log anyways but then try the the following:
Boot into twrp (doesn't matter how for this test)
Flash again the latest twrp beta with twrp itself (choose img button at the bottom) and now when getting asked flash it to BOOT partition! Yes this is no problem or causes any damages. Just do it.
Then choose reboot into system and twrp will popup again (but now it starts from boot partition)
Now install the cm version of your choice or any other rom
Do NOT reboot yet
before rebooting grab the recovery log again and paste it again
3. LG up
If the above does not work and as I believe you need your device back soon the best bet would be do a full backup with the latest twrp beta version. Then use LG up to flash stock kdz again to get a working device.
.
My ZE551ML is unlocked/rooted running the stock MM from asus, everything worked fine for a long time now.
This morning my phone booted in TWRP, and whatever I try, it always boot in TWRP. The only thing I know has changed is that yesterday Magisk installed an update.
How can I recover my phone? adb is working, I can go in TWRP, but what else?!?
Try wiping your misc partition:
Code:
adb shell dd if=/dev/zero of=/dev/block/by-name/misc
Problem was Magisk v11.5 that updated itself, it is not signed. I restored a previous boot backup and back in business.
So people, do not update Magisk using their builtin updater!
Hi, I have same problem. Can anyone please post an step by step to do that adb thing?? I mean, my ZF is stucked in recovery (via fastboot I installed TWRP) but I don't know how to execute that line posted before. I can only get my device as adb sideload so that line posted returns an error... please help or tell me how to find that info.
Thank you in advance!
michi6278 said:
Hi, I have same problem. Can anyone please post an step by step to do that adb thing?? I mean, my ZF is stucked in recovery (via fastboot I installed TWRP) but I don't know how to execute that line posted before. I can only get my device as adb sideload so that line posted returns an error... please help or tell me how to find that info.
Thank you in advance!
Click to expand...
Click to collapse
hello, same problem here. i update the magisk and all go wrong.
i fixed the problem only flashing the magisk again, in the TWRP.
and boot works fine
https://forum.xda-developers.com/an...igning-boot-images-android-verified-t3600606/
Flash this and your problem will be solved
itizar1 said:
https://forum.xda-developers.com/an...igning-boot-images-android-verified-t3600606/
Flash this and your problem will be solved
Click to expand...
Click to collapse
Hey, my phone randomly stopped booting, and I can't seem to get it to work. It boots to TWRP and I have full root access, with an unlocked bootloader. Do you have any idea how to fix this? I don't know what to do with this.
ZE552KL
Kaisogen said:
Hey, my phone randomly stopped booting, and I can't seem to get it to work. It boots to TWRP and I have full root access, with an unlocked bootloader. Do you have any idea how to fix this? I don't know what to do with this.
ZE552KL
Click to expand...
Click to collapse
You dirty flashed your rom then. Everytime you update, first wipe your system (not data!), then flash everything you need (not sure about gapps and stuff, just flash them to make sure)