Related
(Because you try to install TWRP RECOVERY)
What you can do or can not do anything about it?
Device is lost?
Through Flashify
I clicked img TWRP
It worked entered RECOVERY
I did not know what to do where I could not find an installation file rom
I pressed WIPI think that was registered
I made a device Reset
Get stuck LG logo:crying:
[/COLOR]
haimmalka said:
(Because you try to install TWRP RECOVERY)
What you can do or can not do anything about it?
Device is lost?
Through Flashify
I clicked img TWRP
It worked entered RECOVERY
I did not know what to do where I could not find an installation file rom
I pressed WIPI think that was registered
I made a device Reset
Get stuck LG logo:crying:
Click to expand...
Click to collapse
I believe you can flash stock recovery though adb. Do a little research. Stock files are in G2 Mini General Android Developement (D620, right?).
haimmalka said:
(Because you try to install TWRP RECOVERY)
What you can do or can not do anything about it?
Device is lost?
Through Flashify
I clicked img TWRP
It worked entered RECOVERY
I did not know what to do where I could not find an installation file rom
I pressed WIPI think that was registered
I made a device Reset
Get stuck LG logo:crying:
Click to expand...
Click to collapse
This is exactly why I told you NOT to try things you don't know a thing about.
You can still recover your phone:
http://forum.xda-developers.com/showthread.php?t=2824479
jfpsb said:
[/COLOR]
I believe you can flash stock recovery though adb. Do a little research. Stock files are in G2 Mini General Android Developement (D620, right?).
Click to expand...
Click to collapse
Zaaap72 said:
This is exactly why I told you NOT to try things you don't know a thing about.
You can still recover your phone:
http://forum.xda-developers.com/showthread.php?t=2824479
Click to expand...
Click to collapse
It worked out fine for me I was able to install :good:
I'm having the same problem
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Fonku said:
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Click to expand...
Click to collapse
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
zinko_pt said:
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
Click to expand...
Click to collapse
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Fonku said:
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Click to expand...
Click to collapse
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
zinko_pt said:
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
Click to expand...
Click to collapse
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Fonku said:
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
You can use B130 as it is also Lollipop. But all the img from the same rom. You can update to B350 manually after, but first you need a stable rom working.
Let us know man if you fixed your phone. So if not, we can give firther recommendations.
Sent from my Galaxy Tab 3 using XDA Labs
Hi guys
Can't install any OS (tried via ADB commands and flashing custom roms via TWRP).
Whatever I try, it just boots to TWRP.
ADB commands do work because I managed to install TWRP 3.0 and 3.1 for the Moto Z Griffin
Bootloader is unlocked
This device was working fine on Stock Noughat (installed via ADB) and AOKP (installed via TWRP).
Problems began when the camera "failed to start" and in my frustration, I wiped everything via TWRP including system, so now I have no OS.
Not sure why I can't get anything to install.
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
grneyez said:
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
Click to expand...
Click to collapse
followed that guide
Had this working for months and needed to wipe so I did a factory reset and all my phone does is boot to twrp
I tried this process again and all goes good or so it seems but just boots to twrp
I tried a restore from my backup from twrp and get all the way done and it fails on "unable to wipe Fsg."
Above there is a bunch of red failed:
Could not mount /data and unable to find crypto foooter
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder
Failed to mount'/cache' (invalid argument)
failed to mount'/system'(invalid argument)
Failed to mount storage
failed to mount'/data'(invalid argument)
failed to mount'/cache'(invalid argument)
failed to mount'/data/media/twrp'(invalid argument)
unable to wipe fsg.
any ideas? right now just a brick here. i have tried flashing roms from twrp and still just boot to twrp
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
D13H4RD2L1V3 said:
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
Click to expand...
Click to collapse
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
royalflush5 said:
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
Click to expand...
Click to collapse
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
D13H4RD2L1V3 said:
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
Click to expand...
Click to collapse
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
royalflush5 said:
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
Click to expand...
Click to collapse
Again, there's sadly no TWRP-flashable firmware for 7.0 RETUS.
There's only one for TELUS. While it works on other XT1650-03s with unlocked BLs, can't guarantee that it's all stable.
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
raymccoy said:
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
Click to expand...
Click to collapse
thanks for the Rescue same trick work for me though as i was been stuck on TWRP after flashing stock firmware via fastboot , so i manage to flash irfan v4 stock rom and booted to factory image to get it resolved , But now i want to move to complete stock without twrp as i think Oreo update is near by but i get the same issue again, Just wanna ask can u help me out with the process to go back to stock Rom
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
that worked for me also, but it's not a fix, its a workaround. is there an actual fix for this? I've tried the Verity_FE_patcher but that didn't work also.
I unlocked the device bootloader thanks to Narender, and tried to flash Lineage OS 18.1. After flashing the ROM and vendor zip files, I switched the current slot and restarted to fastboot mode. Then I flashed the vbmeta image. Then I rebooted to recovery to check the current slot. Slot was as expected, so I rebooted the system.
Then, TWRP gave me an alert saying "No OS is installed" before rebooting. I was unsure what was the reason for it because the ROM was just installed, so I rebooted the system.
After that, device went straight into fastboot mode after "Android One" screen. No matter which option I choose from there, it keeps restarting the bootloader. I tried using "fastboot reboot recovery" but that did not work either. Then I tried to change the active slot of the device using fastboot commands. That did not help either.
Now I'm stuck with a Nokia 7.2 that can only be turned off or start in fastboot mode. Is it bricked beyond saving? I just want to install TWRP in any of the slots and install any usable ROM. Any help is deeply appreciated.
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Chevindu said:
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Click to expand...
Click to collapse
Follow this and DM if you have doubts
Edit: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
Follow this and DM if you have doubts
Click to expand...
Click to collapse
I actually installed few ROMs after my previous reply. But none of them had working WiFi, which is a deal breaker. Went back to stock ROM.
If you are interested I could help you
Ujwal2000 said:
If you are interested I could help you
Click to expand...
Click to collapse
Hey, thanks. But I thought it's not possible due how the signatures in security patches work. So I gave up. Maybe I misunderstood. Linking to Raghu's reply below.
Post in thread '[OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7.2 | Daredevil |'
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Ujwal2000 said:
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Click to expand...
Click to collapse
Yup, pretty much what I experienced too.
I haven't tried extracting boot image and flashing it manually. At this point to be honest, I'm reluctant to put my hands on it again without having a clear step-by-step guide about it.
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I realize I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I relaise I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Click to expand...
Click to collapse
Thanks Ujwal, appreciate it. I'll have a look.
Official TWRP is now available: https://twrp.me/asus/zenfone9.html
IMPORTANT NOTES:
CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6).
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2202
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Hermann2306 said:
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Click to expand...
Click to collapse
If you're not on stock kernel, then that's probably the problem. I know the custom kernel situation is different on this device than previous ones. This may be something that @Freak07 & I have to look into together. In the meantime, can you restore back to stock kernel and confirm that TWRP works, and then install Kirisakura and see if everything still works?
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Hermann2306 said:
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Click to expand...
Click to collapse
It doesn't sound like you followed the procedure in the Kirisakura thread FAQ to fully return to stock. Can you confirm exactly what you did?
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Hermann2306 said:
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Click to expand...
Click to collapse
I'm not familiar with that app, sorry. I just know that's not the process mentioned in his thread, so until you do that, I can't really confirm what the problem could be.
ok, im back on stock. flashing following files helped. i will test twrp again later and report. thanks for your replies.
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Hermann2306 said:
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Click to expand...
Click to collapse
From stock, I just flashed the Kirisakura zip in TWRP and my device booted up fine.
EDIT: While the above is true, TWRP no longer functions after installing the kernel, and the device won't reboot again after installing it. So something is definitely wrong somewhere.
For now, I can only suggest not using it with a custom kernel until we figure this out.
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Hermann2306 said:
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Click to expand...
Click to collapse
Yes, there seems to be an issue in the kernel that's preventing TWRP from working. I'm not sure what the issue is, unfortunately.
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
c19932 said:
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
Click to expand...
Click to collapse
Yes.
Quick PSA for anyone using this TWRP that also wants to use a custom kernel:
As of Kirisakura 2.0.6, the custom kernel and TWRP can now co-exist. This is due to the changes that allowed a monolithic kernel build. Presently, CleanSlate has not adopted those changes, but if/when it does, I will remove that disclaimer from the OP.
Thanks to @arter97, @Freak07, & @tbalden for supporting this device!
Is the twrp compatible with android 13?
NisseGurra said:
Is the twrp compatible with android 13?
Click to expand...
Click to collapse
There's a really easy way to find out...
Captain_Throwback said:
There's a really easy way to find out...
Click to expand...
Click to collapse
I getting decrypt errors that why the q
NisseGurra said:
I getting decrypt errors that why the q
Click to expand...
Click to collapse
Then you should post some logs
Will do