Related
Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
common issue at this point. It appears recovery isnt sticking for some reason.
kokotron said:
Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?
Click to expand...
Click to collapse
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.
sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Click to expand...
Click to collapse
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
kokotron said:
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
A solution for auto swpan defualt recovery, the file is there only rename it
DJBhardwaj said:
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.
Click to expand...
Click to collapse
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!
sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
Click to expand...
Click to collapse
Just Install a Custom Kernel with modified ramdisk. Install Hellscore kernel and then install SuperSU. You will be able to experience Root.
I think unleashed kernel has also been updated with the same, but I can only confirm it with Hellscore.
It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.
kokotron said:
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!
Click to expand...
Click to collapse
It is weird. I am pretty much sure you're either missing something or using a corrupted img file. Confirm that the file has been downloaded completely by verifying the md5 checksum and I am sure it will mismatch
hp420 said:
It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.
Click to expand...
Click to collapse
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?
kokotron said:
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?
Click to expand...
Click to collapse
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?
sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
Ok thank you, this seems to have worked. When I booted back into Android though root didn't work any more. I re-rooted using your link (which was what I used the first time as well), and I guess I'll know how it goes the next time I reboot the phone.
hp420 said:
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?
Click to expand...
Click to collapse
Not the boot loader because I have the new bootloader that came with L and TWRP working perfectly, so both can coexist.
The problem comes from within the rom as I said, the file is in /system/etc/install-recovery.sh is responsible to clear the custom recovery and return to default android recovery. The solution is to remove (or rename) that file, what I saw is that the TWRP and SuperSU (both try to) can not rename it, and the solution was to rename it manually from the file manager included in the TWRP (mounting /system as explained before).
The same problem to can not overwrite files (should be modified in any command in library ) prevents install from a flashable zip SuperSU, so the solution http://forum.xda-developers.com/nexu...- root-t2025274 initiating its own operating system booting own image solves the problem that can not be overwritten (or modified) files from the TWRP (at least until a specified version for L see the light).
Probably whoever the new bootloader prevents TWRP modify files in /system, but bootloader not erases the custom recovery. Surely people of TWRP is working to fix this issue (or sleeping sometimes you have to sleep) but the problem can be solved by keeping the new booloader.
Conclucion, I have stock L Last bootloader, root and TWRP everything working perfectly and hellsCore Kernel
sidVici0us said:
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
you installed via the SuperSU binaries from flashable zip in TWRP or use the method http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274 ?
With the CF-auto-root you should have no problems, I did so and I read that many people do so, use this method to root.
On the other hand, I was thinking that having a recovery that can not flash zip is not something useful
---------- Post added at 03:16 PM ---------- Previous post was at 02:52 PM ----------
samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
You can not use the superSU flasheable zip, the recovery is not working to modify /system partition, use the other method.
samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
CF autoroot works perfectly!! http://www.xda-developers.com/android/chainfire-releases-cf-auto-roots-for-nexus-line/
I own the mediatek variant of the Moto e4 (xt1760).
I flash twrp as the recovery through fastboot.
I flashed a custom rom and then gapps and then booted into the rom (XenonHD rom). Then when I went to recovery and then clicked on reboot, then on system, the splash screen showed up and then it booted into recovery again. Im freaking out rn. No matter what I do, i cannot boot into System. Any kind of rebooting throws me into TWRP recovery!!
Try booting in to bootloader and choose factory mode....it should boot in to os
Same thing happened to me but I have the Qualcomm Chipset. Just boot into the bootloader from TWRP and select if you have a Qualcomm, qcom but not sure what that would be for you.
just wipe , flash the rom again , wipe cache and dalvik , flash magisk 14.5 , reboot to system
* you have the wrong gapps or another conflict with gapps
why freak out ? you can flash so many roms from recovery ...are you sure your recovery is a good recovery ?
also try to make data ext4 to get past magisk amd xposed errors about failed to mount data and install any modules
Please provide working link of Moto e4 twrp recovery mediatek version
sourav khan said:
Please provide working link of Moto e4 twrp recovery mediatek version
Click to expand...
Click to collapse
use this recovery by XNLOGOS
https://mega.nz/#!00AC0bzL!I0qi5MEveYSNeCYBxStIC8TaDZc3BPSaryTwR7JC_zw
everything you need can be found here :
https://forum.xda-developers.com/moto-e4/development/moto-e4-woods-xt1762-build-nma26-42-75-t3688609
Thanks​ for providing me this one
KevMetal said:
just wipe , flash the rom again , wipe cache and dalvik , flash magisk 14.5 , reboot to system
* you have the wrong gapps or another conflict with gapps
why freak out ? you can flash so many roms from recovery ...are you sure your recovery is a good recovery ?
also try to make data ext4 to get past magisk amd xposed errors about failed to mount data and install any modules
Click to expand...
Click to collapse
I have this this recovery flashed. I did what you said and flashed ColtOS but w/o gapps and after rebooting it still went back into twrp. Does it have to do something with dmverity? I had flashed it after installing supersu the first time. Also, not able to go to the menu where you can select between RECOVERY MODE, START, etc. When I boot into bootloader, this comes on the bottom of the screen -
=> FASTBOOT mode...
=>device unlocked
that's it. I wiped everything but still boots into twrp.
Error unable to load TWRP.img please tell how to solve this error
yashburshe007 said:
I have this this recovery flashed. I did what you said and flashed ColtOS but w/o gapps and after rebooting it still went back into twrp. Does it have to do something with dmverity? I had flashed it after installing supersu the first time. Also, not able to go to the menu where you can select between RECOVERY MODE, START, etc. When I boot into bootloader, this comes on the bottom of the screen -
=> FASTBOOT mode...
=>device unlocked
that's it. I wiped everything but still boots into twrp.
Click to expand...
Click to collapse
i don't know this recovery bro .. i sugggest you flash another recovery or restore from stock ..
you can try to flash no verity .zip again to check but i think your problem is a different one
---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------
sourav khan said:
Error unable to load TWRP.img please tell how to solve this error
Click to expand...
Click to collapse
error when & where ?
KevMetal said:
i don't know this recovery bro .. i sugggest you flash another recovery or restore from stock ..
you can try to flash no verity .zip again to check but i think your problem is a different one
---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------
error when & where ?
Click to expand...
Click to collapse
I flashed your recovery. Your recovery showed up. Wiped, flashed a newly downloaded rom, gapps, wiped dalvik and cache again, rebooted to system. No luck. Thanks anyway! Rip my phone
yashburshe007 said:
I flashed your recovery. Your recovery showed up. Wiped, flashed a newly downloaded rom, gapps, wiped dalvik and cache again, rebooted to system. No luck. Thanks anyway! Rip my phone
Click to expand...
Click to collapse
just try one last thing bro ..go to my thread and download the modded boot.image i have uploaded and flash that ...try that
the very last thing is download stock boot from my thread and flash it , then flash rom , then flash gapps , then flash magisk 14 , then flash no verity
if that doesnt work restore stock rom using scatter loading and sp flash tools ..
go look here ...
https://forum.xda-developers.com/moto-e4/development/moto-e4-woods-xt1762-build-nma26-42-75-t3688609
this post in soecific has the files
https://forum.xda-developers.com/mo...t1762-build-nma26-42-75-t3688609/post74154048
FIRST FLASH CLEAN ROM NO RESTORE
1. flash modified boot.image as boot
2. flash recovery image as recovery
3.flash magisk
4.flash no verify
5.clear cache&dalvik
6.reboot
USE FILES IN THE BOTTOM OF POST 74154048 link i attached above
KevMetal said:
just try one last thing bro ..go to my thread and download the modded boot.image i have uploaded and flash that ...try that
the very last thing is download stock boot from my thread and flash it , then flash rom , then flash gapps , then flash magisk 14 , then flash no verity
if that doesnt work restore stock rom using scatter loading and sp flash tools ..
go look here ...
https://forum.xda-developers.com/moto-e4/development/moto-e4-woods-xt1762-build-nma26-42-75-t3688609
this post in soecific has the files
https://forum.xda-developers.com/mo...t1762-build-nma26-42-75-t3688609/post74154048
FIRST FLASH CLEAN ROM NO RESTORE
1. flash modified boot.image as boot
2. flash recovery image as recovery
3.flash magisk
4.flash no verify
5.clear cache&dalvik
6.reboot
USE FILES IN THE BOTTOM OF POST 74154048 link i attached above
Click to expand...
Click to collapse
The first method you sent didn't work, HOWEVER, THE SP METHOD DID!!:good::good: I don't know how else I can thank you. TYSM!!!:laugh::good::good: You saved my money and my time and I owe my phone's recovery entirely to you. Thank you so much brother!
yashburshe007 said:
The first method you sent didn't work, HOWEVER, THE SP METHOD DID!!:good::good: I don't know how else I can thank you. TYSM!!!:laugh::good::good: You saved my money and my time and I owe my phone's recovery entirely to you. Thank you so much brother!
Click to expand...
Click to collapse
no worries bro:good:
*you can just click on the thanks button
*just remember cos people are posting stuff on XDA doesn't mean it is correct or working guides and make sure to alwaya get stock rom or stock dump first to avoid brick
KevMetal said:
no worries bro:good:
*you can just click on the thanks button
*just remember cos people are posting stuff on XDA doesn't mean it is correct or working guides and make sure to alwaya get stock rom or stock dump first to avoid brick
Click to expand...
Click to collapse
just clicked the thanks button!:good:
btw, could you give me the necessary files for rooting xt1760 and a small guide maybe?
yashburshe007 said:
just clicked the thanks button!:good:
btw, could you give me the necessary files for rooting xt1760 and a small guide maybe?
Click to expand...
Click to collapse
well the files and process is as posted above ...did you have success with custom recovery twrp or are you 100% stock right now ?
KevMetal said:
well the files and process is as posted above ...did you have success with custom recovery twrp or are you 100% stock right now ?
Click to expand...
Click to collapse
I went 100% stock using SP tools. Then i flashed twrp you gave me by stupdroid and then i installed the dotOS and stock gapps 7.1.1. Now i want to use substratum so i need root. The guide u linked above should work right?
IF YOU ARE ON STOCK DO THIS * NOT FOR dotOS check below :FIRST PUT MAGISK 14.5 FROM OFFICIAL SOURCE ON SD AND PUT NO DM VERITY ZIP FROM MY POST ON SD THEN:
you can download modified boot.image and custom recovery files from my thread ...load the scatter file in SP flashtool but manually unselect all the check boxes ...manually select the custom recovery and modified boot image by clicking to the right of the check box in the line with the writing...a file select window will appear so just select the downloaded file ...as before switch off phone ..press download only ..connect usb ..wait for green tick to say done ...now
VERY IMPORTANT Don't switch on phone . hold volume down + power until you get to bootloader ...move your selection up or down using vokume keys until it says recovery NOT FASTBOOT then select yes with power button ..
in twrp flash first no verity
then flash magisk 14.5
then reboot
*if you brick you know how to fix :highfive:
---------- Post added at 05:13 PM ---------- Previous post was at 05:12 PM ----------
yashburshe007 said:
I went 100% stock using SP tools. Then i flashed twrp you gave me by stupdroid and then i installed the dotOS and stock gapps 7.1.1. Now i want to use substratum so i need root. The guide u linked above should work right?
Click to expand...
Click to collapse
IF YOU ARE ON dotOs do this :
if you have dotos just put magisk on your sd card
boot into recovery
flash magisk
reboot :highfive:
SUCCESS
I try alot to flash TWRP but PC show error cannot load TWRP .IMG
---------- Post added at 04:44 PM ---------- Previous post was at 04:16 PM ----------
sourav khan said:
I try alot to flash TWRP but PC show error cannot load TWRP .IMG
Click to expand...
Click to collapse
Bootloader unlock successfully
sourav khan said:
I try alot to flash TWRP but PC show error cannot load TWRP .IMG
Click to expand...
Click to collapse
You must be typing the command wrong, or you don't have the twrp.img in the same directory your opening a terminal in. Make sure you type:
fastboot flash recovery name_of_twrp_file.img
Sent from my Moto E (4) Plus using XDA Labs
I unlocked my ZTE Bootloader, then flashed twrp-3.2.1-0-ailsa_ii and rooted by flashing SR2-SuperSU-v2.79-SR2-20170103215521.zip. So far soo good.
However, then I installed the following:
A2017X_BootStack_B32+B10.zip (got constant Error 7 with Universal Bootloader)
AospExtended-v5.4-axon7-20180504-1942.zip Oreo 8.1
Open Gapps 8.1 ARM64 Stock
A2017G_N_Modem.zip
Now there are several problems:
Can't boot into Bootloader, phone will just hang at the Startup Logo. When I start with Vol Down+Power I get into Safe Mode.
When starting TWRP it asks for a PIN, that I gave as a lock PIN in the ROM
There is an error message in TWRP saying "unable to mount storage"
When starting Android it also asks the PIN before starting the ROM
Root is gone and I'm unable to root again by flashing SR2-SuperSU-v2.79-SR2-20170103215521.zip. It will flash, but Root is still gone
The Gapps camera forcecloses
I have already wiped everything and reinstalled, but it didn't help. Anyone an idea?
When I flashed AEX Oreo, I used NFound's TWRP 3.2.1-7 from this link.
But that doesn't solve that I can't boot into Bootloader, right?
You can't get into bootloader and recovery?
No, just bootloader. But a new recovery won't help that, right?
When I start with Vol Down+Power I get into Safe Mode.
Also, do you have to give your PIN for the ROM to start?
According to this, in B32 it doesn't allow you to access bootloader not sure about B35.
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
You might have to format your internal storage, it sounds like it got encrypted. I had that before when I foolishly uninstalled magisk root and twrp couldn't access storage as well.
Are you revering to my Build Number? I'm on OPM2.171019029
Do I have to flash an No Encrypt File afterwards? I have read about people flashing no-verity-opt-encrypt-5.0.zip on TWRP.
ro-mann said:
Are you revering to my Build Number? I'm on OPM2.171019029
Do I have to flash an No Encrypt File afterwards? I have read about people flashing no-verity-opt-encrypt-5.0.zip on TWRP.
Click to expand...
Click to collapse
The B32 is the bootloader version, what I did was go to twrp and Wipe>Advanced Wipe>Format Data then flash everything again. I don't have experience with the no-verity zip, I just format and flashed bootloader, modem, ROM, GApps and Magisk.
Wiped everything, still PIN prompt in TWRP and "unable to mount storage" error
This is out of my league (I'm out of ideas) but give this a try. If you can boot into the rom, try using the EDL Tool to flash a stock edl package and then read through here on what to do next.
Reflashed TWRP now I have a second error: "E:recv error on uevent"..
If I'm not mistaken, and according your first post, it looks like you're not flashing root after the ROM. If one flashes and boots ROM without rooting it things like encryption and/or filesystem change happens.
Note on the gapps. Best to use something smaller like pico or nano for the time being. Usually recommended. Larger packages like stock and full may cause issues.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Been running twrp 3.2.1-r1 for a while now with resurrection remix on my Perry. Today it fraged itself, so I decided to try the new 3.2.3 twrp. After booting it, it seemed to flash without issue. Upon reboot, it wouldn't load. I flashed the 3.2.1 twrp I tried flashing the ROM, but the data partition wouldn't take it. I discovered that the partition size was 0. I fixed the partition size, and flashed the ROM. Everything seems to be fine, except booting. The phone defaults to twrp instead of booting the ROM. I have to reboot to boot loader, the click start to get the ROM to load. Not critical, but VERY annoying. Any help resolving this is appreciated. Thanks
Tried the fastboot OEM fb_mode_clear command, which flashes, but no change. Tried the adb wipe /misc partition, which returns invalid file.
HigherStateD said:
Been running twrp 3.2.1-r1 for a while now with resurrection remix on my Perry. Today it fraged itself, so I decided to try the new 3.2.3 twrp. After booting it, it seemed to flash without issue. Upon reboot, it wouldn't load. I flashed the 3.2.1 twrp I tried flashing the ROM, but the data partition wouldn't take it. I discovered that the partition size was 0. I fixed the partition size, and flashed the ROM. Everything seems to be fine, except booting. The phone defaults to twrp instead of booting the ROM. I have to reboot to boot loader, the click start to get the ROM to load. Not critical, but VERY annoying. Any help resolving this is appreciated. Thanks
Tried the fastboot OEM fb_mode_clear command, which flashes, but no change. Tried the adb wipe /misc partition, which returns invalid file.
Click to expand...
Click to collapse
TW RP is not clearing the BCB correctly. The boot loader control block. I'll post the commands you need to fix it in a minute when I pull over. Driving right now
---------- Post added at 01:40 AM ---------- Previous post was at 01:37 AM ----------
This version of TWRP is not reading and clearing the bootloader control block (BCB). So, if you do a factory reset via Settings->Backup & Reset->Factory Data Reset, you'll be stuck in a TWRP bootloop.
The quick workaround is to reboot to bootloader, then proceed from there to Start. However, you'll need to do this *every* time until the BCB is cleared.
To clear the BCB manually, issue this command in TWRP terminal:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M
The quick workaround is to reboot to bootloader said:
Thanks for the reply. I tried the command to zero out misc, it returns misc not found, which is of, as I can clearly see the file in an ls file list.
Click to expand...
Click to collapse
Got it by CD to the dir misc is located then executing the following: dd if=/dev/zero of=misc
Could use some help flashing the latest twerp, but since no ROMs need the added 64 bit support, I don't see it as necessary yet.
HigherStateD said:
Got it by CD to the dir misc is located then executing the following: dd if=/dev/zero of=misc
Could use some help flashing the latest twerp, but since no ROMs need the added 64 bit support, I don't see it as necessary yet.
Click to expand...
Click to collapse
The old twrp has the same issue. Just go ahead and Flash the new one. It's just a problem that May come up when you format or if you do a factory reset
madbat99 said:
The old twrp has the same issue. Just go ahead and Flash the new one. It's just a problem that May come up when you format or if you do a factory reset
Click to expand...
Click to collapse
Tried flashing the new twrp from within the old one. I get a kernel error when trying to load after successful flash.
HigherStateD said:
Tried flashing the new twrp from within the old one. I get a kernel error when trying to load after successful flash.
Click to expand...
Click to collapse
Are you flashing it to the recovery partition? Try flashing it with Flashify. but it should work if you choose select install image in TWRP and select the recovery partition.
madbat99 said:
Are you flashing it to the recovery partition? Try flashing it with Flashify. but it should work if you choose select install image in TWRP and select the recovery partition.
Click to expand...
Click to collapse
Yes.. Phone boots fine. Only issue is with recovery. New twrp flashed either in twrp or fastboot generates kernel error. After flashing old twrp, recovery works fine
HigherStateD said:
Yes.. Phone boots fine. Only issue is with recovery. New twrp flashed either in twrp or fastboot generates kernel error. After flashing old twrp, recovery works fine
Click to expand...
Click to collapse
Which version of the E4 do you have?
madbat99 said:
Which version of the E4 do you have?
Click to expand...
Click to collapse
XT1765 by metro
HigherStateD said:
XT1765 by metro
Click to expand...
Click to collapse
I've seen other people with the Metro version and the T-Mobile one which have the same model number and it works fine for them. Don't know exactly why it's not working for you I sse you resized some partitions and had trouble clearing the BCB. So you may have done some other things that I don't know about. All I can say is that if the previous version was working you should stick with that one.
madbat99 said:
I've seen other people with the Metro version and the T-Mobile one which have the same model number and it works fine for them. Don't know exactly why it's not working for you I sse you resized some partitions and had trouble clearing the BCB. So you may have done some other things that I don't know about. All I can say is that if the previous version was working you should stick with that one.
Click to expand...
Click to collapse
I tried to flash the 3.2.3 after my system went into a boot loop for an unknown reason. I was able to eventually clear the BCB with a modified command in the twrp terminal. Is there a way of checking the size of the recovery partition? I'm thinking the added 4~MB of the 3.2.3 twrp might be causing an issue. Perhaps overrunning the size of the partition. Can't think of any other reason it wouldn't work.
HigherStateD said:
I tried to flash the 3.2.3 after my system went into a boot loop for an unknown reason. I was able to eventually clear the BCB with a modified command in the twrp terminal. Is there a way of checking the size of the recovery partition? I'm thinking the added 4~MB of the 3.2.3 twrp might be causing an issue. Perhaps overrunning the size of the partition. Can't think of any other reason it wouldn't work.
Click to expand...
Click to collapse
I flashed it on mine no problem. the recovery partition is bigger than it needs to be. Don't go messing around changing partition sizes or you're asking for trouble.
Very stupid question. ive never had a A/B device before so how would i go about flashing twrp and a custom rom with the 2 partitions
TWRP installer, installs to both A and B [emoji6]
---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------
If you read the log as it is flashing you should see it being flashed to both.
Sobreally it's just the same as before
What version of TWRP are you using? The latest?
RevTheory said:
Very stupid question. ive never had a A/B device before so how would i go about flashing twrp and a custom rom with the 2 partitions
Click to expand...
Click to collapse
It's not stupid at all actually. I've been having the same question and concerns myself regarding the A/B partition slot setup and would love a descriptive tutorial on the differences between this and prior OP devices when it comes to flashing/installing custom ROMs, mods and other zip files.
RevTheory said:
Very stupid question. ive never had a A/B device before so how would i go about flashing twrp and a custom rom with the 2 partitions
Click to expand...
Click to collapse
Daskalman said:
It's not stupid at all actually. I've been having the same question and concerns myself regarding the A/B partition slot setup and would love a descriptive tutorial on the differences between this and prior OP devices when it comes to flashing/installing custom ROMs, mods and other zip files.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
When I reboot recovery after flashing a new rom and also flashing TWRP again (newest version), why are all my files "missing" and replaced with a bunch of weird looking files? Mind you, when I boot system and then go back to recovery, all the proper files are showing again.
Right now I flashed a new rom and TWRP and rebooted recovery and then tried to boot into system, but it keeps booting back to recovery and isn't showing my proper files, so I can't fix by flashing something else or using one of my backups.
Lochman79 said:
When I reboot recovery after flashing a new rom and also flashing TWRP again (newest version), why are all my files "missing" and replaced with a bunch of weird looking files? Mind you, when I boot system and then go back to recovery, all the proper files are showing again.
Right now I flashed a new rom and TWRP and rebooted recovery and then tried to boot into system, but it keeps booting back to recovery and isn't showing my proper files, so I can't fix by flashing something else or using one of my backups.
Click to expand...
Click to collapse
The same is happening to me trying to flash the latest OOS I'm on slot a, I flash the Magisk uninstaller, then OOS, then TWRP installer.. when I boot back to TWRP everything is just a garbled mix of file names.. I go to the reboot menu and select boot from "a" slot, and it's back to normal... Haven't tried anything else, still getting used to the whole a/b partition thing..
That is nice though, if the flash doesn't work, just go into recovery and boot from the other slot and it's the device as it was before flashing...
I also want to say if you wipe data it should boot.. if that doesn't work, you can format data in twrp.. clears your internal storage but it should boot...