My thoughts on booting this custom system.img with no custom recovery for those of us on the Snapdragon CPU. Is We need a way to load a custom recovery, if we are loading a custom rooted system we need a kexec Kernel to load from the new system.img to boot in say a two stage Boot, this isn't the cleanest or fanciest ways, but it was used a long time ago on the Droid Bionic. The bionic didn't have an unlocked boot loader, but we were able to load a custom system.img. eventually they had the new kexec load a recovery before the system, then a choice boot straight to system or hold on the menu button for recovery, after 10 seconds if you didn't press the menu button your system.img would load.
This also allowed for dual boot an untouched system.img/partition
and a rooted system.img/partition, data.img/partition on the sdcard
Some people even partitioned their internal memory for these partitions.
I think this would be the easiest way until someone finds a way to unlock the bootloader would be to create a custom kexec to run once the rooted system.img is booted to load a two stage boot,
first load a custom recovery then a custom in it.rc pointing to new system/data/cache partition/.img
This would at least allow us to have twrp or another custom recovery and better availability for flashing roms.
Related
Hi Nexus 6 Community
Im new to own a Nexus 6 but Im an "enthusiastic flasher" per say. I've being looking around with no luck so I was hopping someone will point me to the right direction:
Usually whenever I flash anything on my previous phones I like to flash TWRP again in case of boot loops or something flashing bad that could delete or corrupt my custom recovery. I'm rooted and installed the latest TWRP through fastboot, but as I previously said, I would like to have a flashable zip to ensure my recovery will be installed and have a higher chance of not being locked out of my phone.
Or I'd notice you can flash images through TWRP, will this re-install my recovery using the TWRP .img file?
I really appreciate all for your help, thanks
Once you boot into twrp for the first time it patches /system to prevent the stock rom from replacing it unless you choose the "keep system mounted as read-only." This option is only offered to you if you boot into twrp with an untouched /system. And as for worrying about being locked out of your phone, as long as you have an unlocked bootloader you can always use a google factory image to get back to stock w/o a custom recovery.
I'd assume no one's made a flashable zip for twrp because reflashing it wouldn't accomplish much of anything if you already have twrp to flash it in.
I am now planning to switch to Official LOS on my wife's Android G1 a.k.a. SEED,
is there a way to restore everything to its original form like official rom, recovery, boot and even relock bootloader?
I was a previous Nexus 5 user and I can eflash the rom image file from google and relock bootloader in just a few type on CMD but I can't seem to find image rom for official SEED(G1).
You'll find most of the stuff you need here. But it's kinda outdated. No factory image for flashing through fastboot though and the latest zip is marshmallow MRA58Y
Basically you'll want to
1. Flash the MRA58Y zip thru TWRP
2. Flash the OEM.img of your G1
3.. If you changed splash screen you can also flash stock splash screen from fastboot
After that your almost all stocked and ready to go
Just need to get rid of the custom recovery. Which is kinda tricky, the stock rom flashes stock recovery all by itself, the tricky part is triggering it as TWRP tries to disable it from happening. One way to stop TWRP from blocking it is to mount system partition and read only reboot to stock then try to reboot to recovery to check it if it's back to stock . Good luck and here's the link
https://drive.google.com/folderview?id=0B9_eDTtTcnv1a25ERUxGcm9CSzA&usp=sharing#list
You mean when flashing MRA58Y I need to mount System partition then flash to restore stock recovery?
By the way i already downloaded OTA of nougat
So I was restoring the stock boot image so I could flash magisk, and I ran into a bit of a problem. I tried booting it up after flashing, and it's stuck on the boot screen so I'm assuming I flashed a bad boot. This wouldn't normally be a problem, except that my volume up button doesnt work meaning I can't boot back into recovery mode/bootloader. Is there a way to get to the bootloader or recovery screen without using the volume up button?
I think you might have accidentally flashed the stock boot image to your recovery. Have you checked the option to flash the boot image and not recovery?
frosted.efizzle said:
I think you might have accidentally flashed the stock boot image to your recovery. Have you checked the option to flash the boot image and not recovery?
Click to expand...
Click to collapse
I'm pretty sure I flashed to boot, I can turn it on and it just shows the blu logo. Before I had a custom boot image though and it's not showing that anymore though.
I'm assuming that custom boot image came prerooted right? You might need to flash the rom that came with the custom image to boot. An easier way to get Magisk which I've done is to flash rom, then flash the unSU zip to remove traces of root then you can flash Magisk like normal.
frosted.efizzle said:
I'm assuming that custom boot image came prerooted right? You might need to flash the rom that came with the custom image to boot. An easier way to get Magisk which I've done is to flash rom, then flash the unSU zip to remove traces of root then you can flash Magisk like normal.
Click to expand...
Click to collapse
I would do that, except with the volume up button broken I'm unable to get to recovery mode, and without being able to boot into the system I can't use adb
Solution: Not sure why or how, but I got it to actually boot into the new system that I flashed. Now all is good and working as it should
So rooted stock ROM, but with TWRP, unlocked boot loader and USB debugging enabled... I'm No stranger to flashing custom ROMs in TWRP and flashing stock ROMS longhand by fastboot commands.
Using MacOS with latest platform-tools...
So today I decided to flash resurrection remix. Downloaded it to storage as usual for flashing via TWRP, flashed it successfully. Only it would not boot. It started going to the stock boot screens and said it could not decrypt... or something.
Anyway where I am right now is that I can boot into TWRP or boot loader just fine. But in boot loader I can't get get it to see my phone using
Code:
./adb devices
Only... for some reason in TWRP if I do ./adb devices, it sees my phone and reports back the correct device ID.
What now? I want to flash back to stock again, but I don't know how to flash line by line without being in boot loader. But in boot loader I can't see the phone?
I know there has to be hope if I can see it in TWRP. But I have no system I can boot to.
-Peter
Great that it works for you now.
For what it's worth, I think that the reason it didn't boot was that the stock rom had encrypted your phone. Current custom roms unfortunately use a different encryption, so that the whole data partition needs to be formatted. I assume that's what you ended up doing.
As to the bootloader, it was never intended to work with adb, only with fastboot.
I have my phone rooted. I have the twrp image on my phone and can fastboot into it. But it does not flash as my recovery. I have no recovery at all. Phone boots fine but has screen I have to press the power button twice on before it will boot. Saying unlocked bootloader and unsafe phone don't have any personal data.. Ect. I downgrade from a13 to a12 and an currently running the fsociety kernel. What can I do to A. Get my recovery back and B. Get rid of the boot error screen everutime I boot.
The Pixel series do not have a recovery partition; you cannot permanently install a custom recovery. If you are not using a custom ROM, there is no reason to use TWRP.
Do not try to remove the bootloader warning screen. It is part of Android functioning as intended, and trying to remove it may corrupt your bootloader.