Related
I accidentally flashed TWRP to the boot instead of recovery. Whenever I turn on the phone it goes straight to TWRP. As it stands the phone is unsuable! AS far I understand it the way to fix this is to flash the phone's original boot.img to the boot. Is this correct? If so my phone is MT2L03 with the 5.1 update. Does anynone know of any link or could anyone PLEASE share their stock boot.img with me. I really need help!
Thank You.
Boot image is part of OS. If you want to install CM12, while you are in twrp, just transfer the cm12 rom and gapp from pc to your sdcard, then flash both. You get complete cm12 with its boot image.
But if you want stock boot image back, you can just flash the stock firmware using the 3 button boot. It is available in the "official stock firmware" section in the INDEX page: http://forum.xda-developers.com/showthread.php?t=3149530
If you have difficulties doing that, let us know. I maybe can find it somewhere, but to be honest, I don't use stock anymore once CM is out.
Thanks. CM12 flash problem
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
fcbfan2k said:
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
Click to expand...
Click to collapse
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Moody66 said:
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Click to expand...
Click to collapse
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Also twrp, have you install the twrp listed in that same page? other twrp version doesn't work.
Edit, saw you mentioned already that install twrp error using app. So try install the correct twrp in bootloader.
fcbfan2k said:
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Click to expand...
Click to collapse
If you flashed b321 boot image you are not on b322 boot... And the correct twrp is found in the same OP....
Hi,
i was on exodus and recently moved to oos 3.1.4 after flashing he new bootloader and then the debloated rom that i found here for OOS3.1.4.After that i cud boot into the modified twrp but when i faced freezes i thought of going back to fully stoock.However even after flashing OOS3.1.4 stock i am unable to see OOS recovery.When i move into \bootloader mode i end up with just a one plus symbol.
i tried flashing OPX recovery using adb and fastboot but to no avail.I then tried flashing modified twrp.That worked but no matter what i do i can neither install OPX recovery nor can i use the mega unbrick guide as my phone shows up as relink USB.....
Could somebody please guide me?
sand87ch said:
Hi,
i was on exodus and recently moved to oos 3.1.4 after flashing he new bootloader and then the debloated rom that i found here for OOS3.1.4.After that i cud boot into the modified twrp but when i faced freezes i thought of going back to fully stoock.However even after flashing OOS3.1.4 stock i am unable to see OOS recovery.When i move into \bootloader mode i end up with just a one plus symbol.
i tried flashing OPX recovery using adb and fastboot but to no avail.I then tried flashing modified twrp.That worked but no matter what i do i can neither install OPX recovery nor can i use the mega unbrick guide as my phone shows up as relink USB.....
Could somebody please guide me?
Click to expand...
Click to collapse
Go through the mm bootloader update threads and you will find your answer.
Thing is I have now installed OS 2.2.x.still the recovery is missing
Exodusche said:
Go through the mm bootloader update threads and you will find your answer.
Click to expand...
Click to collapse
Do u mean the mega unbrick guide?
sand87ch said:
Do u mean the mega unbrick guide?
Click to expand...
Click to collapse
No don't think you need that just issue with how you updated your bootloader. Go through similar threads as yours and you will find your answer.
havent found an answer.Thats because very thread speaks of installing twrp modified etc.i already said i am able to do that.What i am unable is that even after flashing OOS3.1.4 without root i am not able to see oos recovery.also flashing oos recovery seperately doesnt fix it.it just then gives me the one +logo on vol down+power...until i flash twrp bluspark again.how to return my phn to factory condition?can somebody who has faced this help me?
This is now resolved.the mega unbrick guide is good but there's a catch.smtimes u don't get the qusb_bulk.i have seen one for one plus two to fix the RELINK_USB issue but that too never worked.what finally worked was one written for mui for Xiaomi in particular and for devices in general.
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.
Hello,
Since MIUI 10.3.1.0 (PEIMIXM) was launched, I tried to update my device. After the update, when the smartphone rebooted it kept stuck in Mi logo sreen (Android loading wasn't also appearing). I tried to use MiFlash to reflash the ROM and the same happended.
Thinking it was a random problem of MIUI I decided to move to Pixel Experience because I had used it before and I liked. In the same day of MIUI 10.3.1.0 (PEIMIXM) launch, Pixel Experience also launched a new whyred version (in the beggining of June, i think).
I did what was needed to successfully install the ROM according to the dev's thread:
-I downloaded all the needed files (MIUI 10.3.1.0 PEIMIXM firmware, Pixel Experience ROM, recommended modified TWRP version of the developer);
-Initially, I installed TWRP via fastboot mode;
-I flashed the firmware;
-I wiped the partitions Cache Dalvik / ART, System, Cache, Data, vendor;
-I flashed Pixel Experience ROM;
-I wiped Internal Storage;
-I rebooted the device.
After those steps, I couldn't get access to my "homescreen". Basically, my phone stays stuck at the Mi logo screen. And nothing happens.
Considering it could be a recovery problem, I tried to use Pitch Black Recovery (the latest version available for whyred) that supports Oreo and Pie. I used TWRP to flash this one, and after that I made all the steps above again and the same happened.
I'm now only available to flash MIUI (if it is Android 8.1). I can only flash Pixel experience versions that were released before the MIUI Pie stable for this device.
I really appreciate if you could help me!
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
htchd2sucks said:
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
Click to expand...
Click to collapse
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
floater3 said:
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
Click to expand...
Click to collapse
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
htchd2sucks said:
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
Click to expand...
Click to collapse
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
floater3 said:
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
Click to expand...
Click to collapse
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
htchd2sucks said:
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
Click to expand...
Click to collapse
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
floater3 said:
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
Click to expand...
Click to collapse
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
htchd2sucks said:
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
Click to expand...
Click to collapse
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
floater3 said:
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
Click to expand...
Click to collapse
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
htchd2sucks said:
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
Click to expand...
Click to collapse
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
floater3 said:
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
Click to expand...
Click to collapse
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
htchd2sucks said:
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
Click to expand...
Click to collapse
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
floater3 said:
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
Click to expand...
Click to collapse
It's clearly not related to recovery, at least, not directly.
-Check what "wipes" you have done, and ideally do all of them + format data (you can always reencrypt later). Then, reboot, and redo the flashing of everything.
-Another option would be to flash with "miflash" which I think will also restore some boot things. In that scenario, you are on your own because I don't know about ARB in your case and all potential issues.
I can only say that I did a "miflash" when I used to have ARBv3, and it went fine (I had to redo the recovery, etc... after).
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.