Related
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.
.
Hi there,
I wanted to install the latest image of Nethunter (found on build.nethunter.com/nightly) but when I install it with TWRP I keep getting the message : "Unpacking boot image failed" in the log screen.
What I did in order:
- Unlock fastboot mode
- Flash TWRP recovery (found on build.nethunter.com/twrp)
- Reboot on TWRP
- Install kernel ( kernel-nethunter-oneplus3-nougat-3.15.4-20170126-2226 )
- Install ROM ( nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604 )
- Reboot
It is when I install the rom that I get the error message "Unpacking boot image failed". Even if at the end it says "install completed - Success", it keep loading (with the nethunter loading screen) indefinitely...
I tried many differents versions of TWRP and even different builds of Nethunter, I found nothing on the net, so what should I do ?
Should I post an issue on the kali-nethunter github ?
Hope you have some ideas of what I can try...
However if you need any other information (log file ...), tell me what.
Aiscargeauh said:
Hi there,
I wanted to install the last image of Nethunter (found on build.nethunter.com/nightly) but when I install it with TWRP (found on build.nethunter.com/twrp) I keep getting the message : "Unpacking boot image failed" in the log screen.
I tried many differents versions of TWRP and even different builds of Nethunter, I found nothing on the net, so what should I do ?
Should I post an issue on the kali-nethunter github ?
Hope you have some ideas of what I can try...
However if you need any other information (log file ...), tell me what.
Click to expand...
Click to collapse
What ROM are you using?
Last time i installed it i was on OOS 3.2.2. You have to flash kernel and then the big file (generic nethunter.....)
Found that in https://forum.xda-developers.com/showpost.php?p=68451978&postcount=6
It worked perfectly but since 3.2.2 i havent touched it again so not sure what rom is compatible atm
fuarkgl3 said:
What ROM are you using?
Click to expand...
Click to collapse
I'm trying with the "nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604.zip"
Also tried with the full version, instead of minimal but same result.
Aiscargeauh said:
I'm trying with the "nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604.zip"
Also tried with the full version, instead of minimal but same result.
Click to expand...
Click to collapse
I mean version of OOS, not nethunter overlay. See my screenshot. You have to download one of the following kernels depending if you are on MM or nougat. Flash it before flashing the nethunter overlay
fuarkgl3 said:
I mean version of OOS, not nethunter overlay
Click to expand...
Click to collapse
I'm trying with the latest OTA version, so actually the 4.0.2.
I also installed the kernel before, I'm gonna edit my first post with informations on what I did.
Aiscargeauh said:
I'm trying with the latest OTA version, so actually the 4.0.2.
I also installed the kernel before, I'm gonna edit my first post with informations on what I did.
Click to expand...
Click to collapse
Ok i just read it. And it seems strange indeed. Will try to install it today since i use also oos 4.0.2 and will report back asap
Just out of curiosity what twrp are you using?
fuarkgl3 said:
Ok i just read it. And it seems strange indeed. Will try to install it today since i use also oos 4.0.2 and will report back asap
Just out of curiosity what twrp are you using?
Click to expand...
Click to collapse
Thank's for the support anyway
I'm using the TWRP provided by Nethunter on build.nethunter.com/twrp/oneplus/
Also tried with official 3.0.3 for the OnePlus 3 from twrp.me/devices/oneplusthree.html
Aiscargeauh said:
Thank's for the support anyway
I'm using the TWRP provided by Nethunter on build.nethunter.com/twrp/oneplus/
Also tried with official 3.0.3 for the OnePlus 3 from twrp.me/devices/oneplusthree.html
Click to expand...
Click to collapse
Got it working. Only problem is i dont find the option to enable OTG-USB lol
fuarkgl3 said:
Got it working. Only problem is i dont find the option to enable OTG-USB lol
Click to expand...
Click to collapse
And I'm here sitting with my error and my infinite boot, lol.
Can you please put the installation process you did ? With the files you used ?
I'm getting my phone to full-stock.
Aiscargeauh said:
Can you please put the installation process you did ? With the files you used ?
I'm getting my phone to full-stock.
Click to expand...
Click to collapse
Sure. Just give me time to post what i did, currently restoring my nandroid because something went wrong when updating metapackages, so im going to download full version instead of minimal and enable OGT-USB to check if wifite works. I will post the steps asap :good:
meanwhile..... how the **** do i enable usb-otg? i dont find the option in settings/storage/3dot
Good and bad news: OTG does not work (it worked for me on MM) but nethunter runs "well" ... it stucks while rebooting and some weird things more. It runs laggy as well...
Steps and config i have
-Experience ROM v10.1(oos 4.0.2 with some adds) and custom TWRP by blu_spark v14
1-Download these 2 files from https://build.nethunter.com/nightly/3.15.4-20170202-1604/
-kernel-nethunter-oneplus3-nougat-3.15.4-20170202-1604.zip
-nethunter-generic-arm64-kalifs-full-rolling-3.15.4-20170202-1604.zip
2-Reboot to recovery and install nethunter-generic-arm64.....
3-Not sure if you have to reboot and then install kernel but i flashed nethunter+kernel without rebooting to system
4-Reboot to system and open supersu, then open nethunter app and grant superuser permissions
5-Done.
I Dont really know why my external adapter or pendrive are not recognized, because it did in MM with same hardware lol. Maybe now only works with official usb-c adapter, who knows
I will try this when I can, but it is close to what I already did.
I will edit this post when done.
I seen that you used the arm64 version, perhaps the problem is that I use the armhf ?
Aiscargeauh said:
I will try this when I can, but it is close to what I already did.
I will edit this post when done.
I seen that you used the arm64 version, perhaps the problem is that I use the armhf ?
Click to expand...
Click to collapse
may be, but im not sure. Finally got USB-OTG working but it runs very laggy and dont find any network. So problem is nh build or oos 4.0.2
fuarkgl3 said:
may be, but im not sure. Finally got USB-OTG working but it runs very laggy and dont find any network. So problem is nh build or oos 4.0.2
Click to expand...
Click to collapse
Do you think flashing another ROM before flashing nh-generic will help ?
Aiscargeauh said:
Do you think flashing another ROM before flashing nh-generic will help ?
Click to expand...
Click to collapse
Dont think so. But latest build i installed NH i didnt use arm64 version but armhf. So maybe try what i did but using custom TWRP by blu_spark v14 and armhf.... im not sure
Tested with 2 antennas and result is the same in both (see SS)
hi, i've never had probem updating my phone to oxygenOS. however the last 2 updates won't work : twrp says "zip signature verification failed error installing zip file" and even when i download and launch the OTA it does the same.
do you have an answer that doesn't envolve factory reseting of the phone?
bigben14 said:
hi, i've never had probem updating my phone to oxygenOS. however the last 2 updates won't work : twrp says "zip signature verification failed error installing zip file" and even when i download and launch the OTA it does the same.
do you have an answer that doesn't envolve factory reseting of the phone?
Click to expand...
Click to collapse
And manually re-downloading doesn't solve the issue?
Puddi_Puddin said:
And manually re-downloading doesn't solve the issue?
Click to expand...
Click to collapse
i've tried to download the beta 25 and 26 manually and flashed it with twrp and i've tried to update with the OTA of both version and none of thoses methodes worked
bigben14 said:
i've tried to download the beta 25 and 26 manually and flashed it with twrp and i've tried to update with the OTA of both version and none of thoses methodes worked
Click to expand...
Click to collapse
Make sure you are on the right version of twrp (latest). Take a backup of system and boot, then wipe system and flash the zip and see if it works. If it doesn't just revert system and you are back to normal.
Puddi_Puddin said:
Make sure you are on the right version of twrp (latest). Take a backup of system and boot, then wipe system and flash the zip and see if it works. If it doesn't just revert system and you are back to normal.
Click to expand...
Click to collapse
hi,
i am on the latest version of twrp and i tried what you told me, still doesn't work.
any ideas of the origin of the problem? any other ideas on how to fix it?
bigben14 said:
hi,
i am on the latest version of twrp and i tried what you told me, still doesn't work.
any ideas of the origin of the problem? any other ideas on how to fix it?
Click to expand...
Click to collapse
Perhaps this version requires a clean install? I havent really been on OOS. What is new in Open Beta 25?
Puddi_Puddin said:
Perhaps this version requires a clean install? I havent really been on OOS. What is new in Open Beta 25?
Click to expand...
Click to collapse
the open beta is the oreo one. but i just checked and tried to install some other zips (a bootloader and akt) and the same problem happens
Puddi_Puddin said:
Perhaps this version requires a clean install? I havent really been on OOS. What is new in Open Beta 25?
Click to expand...
Click to collapse
i think that i found the problem, but i have no idea as how to fix it : when i install the rom, the installer tells me : Warning : No file_contexts E3004: This package is for "OnePlus 3" devices;this device is a "".
bigben14 said:
i think that i found the problem, but i have no idea as how to fix it : when i install the rom, the installer tells me : Warning : No file_contexts E3004: This package is for "OnePlus 3" devices;this device is a "".
Click to expand...
Click to collapse
Hmm, try to wipe system and flash the OOS version you are currently on. That should overwrite the system partition and perhaps fix this issue.
Twrp OREO or
https://forum.xda-developers.com/showpost.php?p=74152902&postcount=3504
or
blu spark v.50 by eng stk.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Just checked for updates and this popped up. Enjoy.
Link for the download is: http://bigota.d.miui.com/V10.2.1.0.PEEMIXM/miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip
I just got this too! Do you know how I can update having twrp installed?
I just tried to install the smaller update above, it failed and now I'm downloading a 1.8gb version. Of you have TWRP installed, I'd probably just download the older OTA and fastboot flash boot boot.img from that OTA.
faddys123 said:
I just got this too! Do you know how I can update having twrp installed?
Click to expand...
Click to collapse
You should be able to install it like normal but ensure when your device reboots you enter your password to enter twrp. If that doesn't work just reboot into twrp and install it by selecting it from the downloaded ROM directory (I forget what the folder is called but it's not the normal download folder). You will have to reflash twrp afterwards.
xreactx said:
You should be able to install it like normal but ensure when your device reboots you enter your password to enter twrp. If that doesn't work just reboot into twrp and install it by selecting it from the downloaded ROM directory (I forget what the folder is called but it's not the normal download folder). You will have to reflash twrp afterwards.
Click to expand...
Click to collapse
This *should* would too.
Filename for the big file is: miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip we should be able to assemble the whole bigota.somethingsomethingsomething.darkside.xiaomi.downloads url using that, but I'm not at a computer and going to be late for work as is.
Sent from my Mi MIX 3 using Tapatalk
Ok got it installed i downloaded the 1.8gb flashed it via twrp then flashed twrp again and installed magisk all it working now ?
Noticed a few new things battery percentage text is now inside the battery icon!
Also there's a new 'suggestions' in the recents view, it can be turned off in the settings
faddys123 said:
Ok got it installed i downloaded the 1.8gb flashed it via twrp then flashed twrp again and installed magisk all it working now
Noticed a few new things battery percentage text is now inside the battery icon!
Also there's a new 'suggestions' in the recents view, it can be turned off in the settings
Click to expand...
Click to collapse
What version of Magisk did you install? I tried 17.3 and have a bootlooping phone.
The URL for the big OTA (1.8gb) is: http://bigota.d.miui.com/V10.2.1.0.PEEMIXM/miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip
PWn3R said:
What version of Magisk did you install? I tried 17.3 and have a bootlooping phone.
Click to expand...
Click to collapse
Using 17.3 as well mate
faddys123 said:
Using 17.3 as well mate
Click to expand...
Click to collapse
I just tried downloading a fresh copy of the Magisk zip. Same result. The phone starts booting then reboots into recovery. I don't know why this doesn't work. Did you have a "global" version of the phone? If so, can you backup your boot image with TWRP (the Magisk rooted one) and post it so we can try downloading and installing to see if it works on a Chinese phone?
Is it normal for the update size to not be displayed? This is my first update using a Xiaomi device & found it odd to not know how large a update was.
eseanq said:
Is it normal for the update size to not be displayed? This is my first update using a Xiaomi device & found it odd to not know how large a update was.
Click to expand...
Click to collapse
Mine showed the size for the small incremental which failed and for the full OTA which installed sucessfully. I have not been able to root this with Magisk, no matter what I tried. Every attempt at rooting with SuperSU or Magisk caused the device to bootloop and go back to recovery.
PWn3R said:
Mine showed the size for the small incremental which failed and for the full OTA which installed sucessfully. I have not been able to root this with Magisk, no matter what I tried. Every attempt at rooting with SuperSU or Magisk caused the device to bootloop and go back to recovery.
Click to expand...
Click to collapse
Where does the file size show up?
eseanq said:
Where does the file size show up?
Click to expand...
Click to collapse
It showed it in the text right below the MIUI logo on the updates page. Check the screenshot in the OP
PWn3R said:
It showed it in the text right below the MIUI logo on the updates page. Check the screenshot in the OP
Click to expand...
Click to collapse
Oh ****.. I'm guessing its the 599M? For some reason I thought that was part of the build. :laugh: Lmao.
eseanq said:
Oh ****.. I'm guessing its the 599M? For some reason I thought that was part of the build. :laugh: Lmao.
Click to expand...
Click to collapse
Yeah, that's the update download size. Don't be surprised when the 599 one fails to install (if you have stock recovery). It will download a 1.8GB one (the one I linked to in the OP now) and that one will install as expected. I think you can install either with TWRP if you want. GLHF
anyone figured how to root this? I flashed twrp then flash magisk 17.3 but it kept bootlooping to twrp.
No, I've tried everything. I have a suspicion we can root this on the Chinese device after we have fastboot images.
Sent from my Mi MIX 3 using Tapatalk
Great Update! Many things changed that are not mentioned in the changelog! Finaly notifications in the AOD! ?*?*
PWn3R said:
No, I've tried everything. I have a suspicion we can root this on the Chinese device after we have fastboot images.
Sent from my Mi MIX 3 using Tapatalk
Click to expand...
Click to collapse
I think this too.
I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?
boland said:
I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?
Click to expand...
Click to collapse
Flash magisk v18.1 and it will work fine. Don't update Magisk. Some roms have this bug.
boland said:
I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?
Click to expand...
Click to collapse
If you reboot it should reappear (it does for me).
I don't know what's the root cause, I'll just wait patiently for a fix. Unfortunately I don't have time to troubleshoot or provide logs to whoever to help the investigation.
PS: in your description be more accurate "latest version of xyz" means nothing. Specify exactly which version. Especially there is stable and beta!