I am trying to use MultiROM v5, however, I do not know how to patch my installed stock 4.2.1 ROM with the "kexec_kernel_42.zip" patch. I have so far done:
1. Flashed "multirom....zip" via recovery
2. Flashed "twrp modified recovery.img" via recovery
3. Attempted to install Ubuntu (Not working, keeps throwing error)
How do I flash the kernel?
Flashing The Kernel
Okay this is my first post but I have been through the process myself and now dualboot ubuntu 13.04 and android.
The kernel is flashed in the same way as the multirom zip. Hope this helps.
Also two questions, what recovery are you using and where in that recovery did you flash the modded twrp image?
Last I remember you couldn't flash a custom recovery from recovery...
Also just have to makes sure; your tab is rooted right?
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/
So I my A2017G had RR-20170314 with TWRP 3.1.0-0 and AX7 R6 installed. Everything was working fine until today my phone rebooted while it was in my pocket. I didn't change anything before and haven't used it for some time and only noticed this through 2 short vibrations. Since then the phone refused to boot into system, TWRP was still accessible though. Three short blinks by the led directly after the bootloader screen and then the phone shut itself down.
Back in recovery I made a full backup and tried booting with deleting cache etc and installing the latest RR. Nothing worked.
When I went back to stock I was finally able to boot. Flashed TWRP 3.1.0-0 through axon7tool and installed RR again. And again only those 3 led blinks
Used "disemmcwp" to make sure write protection is disabled and noticed that when I rebootet the recovery got replaced by the stock one. Only if I enable write protection through "emmcwpenab" the recovery isn't replaced
Just checked the status of the bootloader and it still says unlocked.
I found two threads with a similiar issue but unfortunately nothing helped:
https://forum.xda-developers.com/axon-7/help/boot-recovery-boot-t3569364
https://forum.xda-developers.com/axon-7/help/3-flashes-reboot-phone-shuts-off-t3574324
Never experienced such a thing before. Any help is really appreciated ?
I'm really out of ideas what to do. And stock isn't really a permament solution
Are you using latest G bootstack? Is the device in dfu, or edl mode (check device manager on pc)?
Be very careful with that G version.
Yes since I was on RR before. Using the stock bootstack nor the one provided in the Los thread makes a difference.
Fortunately I'm not stuck in DFU mode. Booting to stock works, so does edl and twrp. But twrp only without using disemmcwp
I would try using older twrp. I've encountered this before but usually a reboot fixes it. I have not gone to twrp 3.1 yet, i think 3.0.4 was the one before.
lafester said:
I would try using older twrp. I've encountered this before but usually a reboot fixes it. I have not gone to twrp 3.1 yet, i think 3.0.4 was the one before.
Click to expand...
Click to collapse
Tried it with TWRP 3.04-1 and it's the same result.
Reboot diseemcwp -> recovery gets replaced by stock recovery after reboot
Reboot emmcwpenab -> recovery gets not replaced
In both cases I am unable to boot with a modified system or kernel.
Seems like the write protection is screwed up
Cyb3rzombi3 said:
Tried it with TWRP 3.04-1 and it's the same result.
Reboot diseemcwp -> recovery gets replaced by stock recovery after reboot
Reboot emmcwpenab -> recovery gets not replaced
In both cases I am unable to boot with a modified system or kernel.
Seems like the write protection is screwed up
Click to expand...
Click to collapse
If you disable write protection you inadvertently end up tripping dm-verity, which causes the device not to boot (security feature).
The reason you feel that disabling system write protection through TWRP causes TWRP to get overwritten by the stock recovery, could be because of the reboot rather than anything else.
I.e. When you install the stock system and reboot, the system overwrites the recovery partition, installing the stock recovery.
My suggestion:
- Make a backup.
- Wipe dalvik cache, cache, system, and data through recovery (under Wipe-> Advanced Wipe).
- Check that the filesystem of the partitions are ext4 (through the "file system" button under Wipe->Advanced Wipe menu), and change them if necessary.
- Reboot recovery.
- Don't swipe to allow system modifications.
- Install the stock bootstack, stock system (I'm assuming that you are using DrakenFX's image zips), and reboot.
- If it fails to install, just reboot recovery, and try to install once again.
Let me know if this works for you.
Erahgon said:
If you disable write protection you inadvertently end up tripping dm-verity, which causes the device not to boot (security feature).
The reason you feel that disabling system write protection through TWRP causes TWRP to get overwritten by the stock recovery, could be because of the reboot rather than anything else.
I.e. When you install the stock system and reboot, the system overwrites the recovery partition, installing the stock recovery.
My suggestion:
- Make a backup.
- Wipe dalvik cache, cache, system, and data through recovery (under Wipe-> Advanced Wipe).
- Check that the filesystem of the partitions are ext4 (through the "file system" button under Wipe->Advanced Wipe menu), and change them if necessary.
- Reboot recovery.
- Don't swipe to allow system modifications.
- Install the stock bootstack, stock system (I'm assuming that you are using DrakenFX's image zips), and reboot.
- If it fails to install, just reboot recovery, and try to install once again.
Let me know if this works for you.
Click to expand...
Click to collapse
Already did those steps but instead of using DrakenFX's files I used the official stock zip.
Shouldn't make a difference right?
Gonna try it once more...
Edit:
I'm stock now, TWRP installed without allowing system modifications.
Edit2:
Just rebootet and the recovery is gone again. This happened after I dlashed the recovery again after reverting to stock.
Edit3:
So what I tried so far after reverting to stock after each fail:
- flash SuperSU 2.65 -> unable to boot
- flash SuperSU 2.97 -> unable to boot
- flash Magisk 11.6 -> boot successful, Magiks installed and showing root but unable to request root permissions
- flash latest Los -> unable to boot
- flash latest RR -> unable to boot
- flash latest tool to disable dm-verity (from TWRP thread: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/) -> unable to boot
- flash AX7 R1 -> unable to reboot
Did the above steps with allowing system modifications and without.
Same for rebooting with disemmcwp and reformatiing partitions.
Tried using the universal bootloader from Los thread and still wasn't able to boot except using the stock rom.
I'm really out of ideads what I could try next.
Recovery seems to stick for now.
Could it be that the problem is not dm-verity but something else?
When I rooted the device I encountered no problem with that security mechanism. Custom roms and kernels worked as well without ever having to worry abou that.
Finally managed to boot into RR!
Here is what I did:
1. Went back to B10
2. Relocked bootloader
3. Booted into system -> developer settings -> Oem Unlock
4. Unlocked bootloader
5. Flashed recovery through fastboot
6. Booted directly into TWRP (when I did a restart it was overwritten immediately that's why I booted directly into it one the second try)
7. Allowed system modifications inside TWRP and flashed SuperSU 2.65
8. Successfully booted into system and had root
9. Flashed Universal Bootloader and Modem from Los thread
10. Flashed RR + Gapps
I really don't know which step the crucial one was but I hope if someone else manages to get into the same situation as I did those steps will help.
Thank you guys for helping me out
Hi,
a User in an other Thread here in xda said that i can't flash twrp on my TabZ with the command 'fastboot flash recovery twrp.img' because there is no recovery partition on the TabZ. All i've tried, flashing twrp 3.x failed. I can install XZDualRecovery, but here the Recovery thinks my Tablet is the LTE version (SGP321) and not the Wifi version. So i can't install custom Roms because if the "wrong" device.
Is there a Kernle with buildin Recovery out there that i can flash on my Tablet? I'll tried LineageOS 14.1 and for that i need twrp 3.x, XZDualRecovery is TWRP 2.8.x. The DoomKernel Downloads doesn't work, instead of downloading the files it opens some pages to casinos and online dating services.
PiereMallao said:
Hi,
Is there a Kernle with buildin Recovery out there that i can flash on my Tablet? I'll tried LineageOS 14.1 and for that i need twrp 3.x, XZDualRecovery is TWRP 2.8.x.
Click to expand...
Click to collapse
Hello,
All latest custom ROMs have built-in TWRP recovery (3.0.2.0 or 3.0.3.0).
flash boot.img of any latest custom firmware like LA/RR/CR by "fastboot flash boot boot.img", reboot and enter recovery from where you can flash any custom ROM, gapps, etc.
as i've written 'fastboot flash boot boot.img' doesn't work on my xperia device. i've tried this more then twenty times with two xperia tablet z. thats why i'm asking for an alternative. a user here posted that on some xperia devices there is no boot partition so the only way is to flash a kernel with custom rom.
the only way for my to flash a recovery is XZDualRecovery. But here i have the problem that twrp and philz think they are installed on a xperia tablez z lte (sgp321) and not a xperia tablet z wifi (sgp311). i have this problem with both tablets.
PiereMallao said:
as i've written 'fastboot flash boot boot.img' doesn't work on my xperia device. i've tried this more then twenty times with two xperia tablet z. thats why i'm asking for an alternative. a user here posted that on some xperia devices there is no boot partition so the only way is to flash a kernel with custom rom.
the only way for my to flash a recovery is XZDualRecovery. But here i have the problem that twrp and philz think they are installed on a xperia tablez z lte (sgp321) and not a xperia tablet z wifi (sgp311). i have this problem with both tablets.
Click to expand...
Click to collapse
I too am having issues flashing a recovery. A lot of the posts are old. There are posts that say to install the newest TWRP on the fota partition but I have not found a good tutorial on how to do that. I can root and unlock the bootloader. Just the dang recovery. Anyone have any suggestions? Thanks
This post is old but i found a solution. Not for flashing the recovery partition. It fails (command not allowed) despite the bootloader is unlocked.
The solution is first to flash the boot partition with TWRP V3.2 using "fastboot flash boot twrp-3.2.3-0-pollux_windy.img".
Reboot the device and you shoul'd be under TWRP.
Wipe data and dalvik cache (important !)
Using TWRP, install Lineage.
Reboot and Lineage starts.
The problem is that TWRP disapears after installing Lineage because the boot partition is re-formated by the install of Lineage. So, you can't install other Zips, like gapps for example. But what i made was using aptoid and i can do everything i need. The SGP311 under Lineage is a real pleisure except the fact that the IR connector is no more recognized.
Zadig74 said:
This post is old but i found a solution. Not for flashing the recovery partition. It fails (command not allowed) despite the bootloader is unlocked.
The solution is first to flash the boot partition with TWRP V3.2 using "fastboot flash boot twrp-3.2.3-0-pollux_windy.img".
Reboot the device and you shoul'd be under TWRP.
Wipe data and dalvik cache (important !)
Using TWRP, install Lineage.
Reboot and Lineage starts.
The problem is that TWRP disapears after installing Lineage because the boot partition is re-formated by the install of Lineage. So, you can't install other Zips, like gapps for example. But what i made was using aptoid and i can do everything i need. The SGP311 under Lineage is a real pleisure except the fact that the IR connector is no more recognized.
Click to expand...
Click to collapse
You can flash TWRP to FOTA partition, and it will stay there permanently (=forever). Also you can use kernel for LOS with built-in kernel, so you can install zips whenever you want.
Succeed
Rootk1t said:
You can flash TWRP to FOTA partition, and it will stay there permanently (=forever). Also you can use kernel for LOS with built-in kernel, so you can install zips whenever you want.
Click to expand...
Click to collapse
Thank you.
Considering the TWRP zip is on /sdcard i used :
adb root (important)
adb shell
dd if=/sdcard/twrp-3.2.3-0-pollux_windy.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
And success !
adb reboot recovery starts automaticaly TWRP.
---------- Post added at 01:12 PM ---------- Previous post was at 01:08 PM ----------
Zadig74 said:
Thank you.
Considering the TWRP zip is on /sdcard i used :
adb root (important)
adb shell
dd if=/sdcard/twrp-3.2.3-0-pollux_windy.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
And success !
adb reboot recovery starts automaticaly TWRP.
Click to expand...
Click to collapse
I forgot a question. Under LineageOS, no infrared connector detected. Any idea ?
Zadig74 said:
I forgot a question. Under LineageOS, no infrared connector detected. Any idea ?
Click to expand...
Click to collapse
Might not be implemented. I do not use it though ...
Ask the maintainer in the LineageOS thread.