With the new recovery that allows selinux, is it possible to flash a boot.IMG now?
If it is now possible to get back to 905 fxz. Also if not I did find that the vendor and webtop partitions are symlinked, which is why when you try to boot an old ROM with the old webtop 2 that you get a boot loop, so even with out flashing a new boot.IMG, we could make custom Roms that unsymlink webtop and vendor partitins to allow old webtop v2 to run again
Related
Long time flasher here, but I'm trying to do something I often don't do - go back to a stock rooted setup.
When I try to flash the factory images (flash-all.sh) it always errors-out saying it can't find the system.img. So I fastboot flash each img manually. The system boots fine.
But as soon as I flash TWRP into the recovery partition, there is an error message at boot that the system is corrupted and to wipe the data.
What's the trick to get this working? Do I need to flash an insecure boot img first?
Thanks for the info!
That system corruption message is normal when totally stock. You need to flash a modified boot image or custom kernel, which can be found in the forums. That will resolve the corruption message.
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
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.
Hi! So a little while ago I unlocked my bootloader, rooted my device, enabled camera2api and installed gcam and modules. Is there any way I can go back to the original 8.1.0 in order to get the OTA updates and get the November patch that comes with andoid 9? Then unlock the bootloader again, enable camera2api and install gcam and modules?
I soft bricked my phone in my first attempt to unlock the bootloader so I decided to ask here for help first
mirunaa said:
Hi! So a little while ago I unlocked my bootloader, rooted my device, enabled camera2api and installed gcam and modules. Is there any way I can go back to the original 8.1.0 in order to get the OTA updates and get the November patch that comes with andoid 9? Then unlock the bootloader again, enable camera2api and install gcam and modules?
I soft bricked my phone in my first attempt to unlock the bootloader so I decided to ask here for help first
Click to expand...
Click to collapse
You don't need to lock bootloader to get OTA updates. Keep it unlocked if you want to get back to stock android.
First uninstall all the Magisk modules you've downloaded. Then flash stock boot.img and system.img (If you've edited build.prop without adb shell). After this you'll be on stock android and you'll get OTA updates.
Where do I find stock boot.img and system.img?
Also, will my phone factory reset after this procedure?
mirunacont said:
Where do I find stock boot.img and system.img?
Also, will my phone factory reset after this procedure?
Click to expand...
Click to collapse
Which version of Oreo are you on? Tell me the build number.
And your phone won't factory reset after this.
---------- Post added at 07:31 PM ---------- Previous post was at 07:23 PM ----------
[email protected] said:
Which version of Oreo are you on? Tell me the build number.
And your phone won't factory reset after this.
Click to expand...
Click to collapse
Download this - https://android.googleapis.com/pack.../f9b27203a7d6dd2c6709f238d9953c6d4e18c04b.zip
Then extract the files and then find the boot.img and system.img. Flash the images from fastboot using -
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
Extract the Images & Flash Them Individually
you have to flash the system images individually. This method takes some extra work, but it can be used to un-root, update, or un-brick your device without losing existing data.
Start by extracting any additional archives from the factory images package. Sometimes, factory images packages can contain a series of three or four nested archives, so make sure to unzip all of them. From there, copy all of the image files to the main platform-tools folder—in other words, don't leave them in any sub-folders. From here, there are two images that you can get rid of: cache.img and userdata.img. These are the images that will overwrite your data and cache with blank space, so if you don't flash them, your existing data will remain intact.
Of the remaining images, six make up the core elements of Android: boot, bootloader, radio, recovery, system, and vendor.
The boot image contains the kernel, so if you just want to get rid of a custom kernel that's causing issues with your device, you only have to flash this one. To do that, type the following command into the ADB shell window:
fastboot flash boot <boot image file name>.img
Next is the bootloader image—this is the the interface that you're using to flash images with Fastboot commands. So to update your bootloader, type:
fastboot flash bootloader <bootloader image file name>.img
Once you've done that, you should reload the bootloader so that you can continue flashing images on the newer version. To do that, type:
fastboot reboot-bootloader
After that, we have the radio image. This one controls connectivity on your device, so if you're having problems with Wi-Fi or mobile data, or if you just want to update your radio, type:
fastboot flash radio <radio image file name>.img
Then there's recovery. This is something you may or may not want to flash, depending on the modifications you've made. For example, if you've installed TWRP custom recovery, flashing this image will overwrite your modification and replace it with the stock recovery interface. So if you're just updating your modded device, you should skip this one. Otherwise, if you plan to keep your phone stock and want the newer version of stock recovery, type:
fastboot flash recovery <recovery file name>.img
Next up is the big one: The system image. This one contains all of the files that make up the actual Android OS. As such, it's the most essential part of any update.
However you may not be updating your phone. You may just be re-flashing the stock firmware to recover from a soft brick. If this is the case, the system image is often the only image you need to flash in order to fix everything, because it contains the entirety of Android. In other words, if you flash this image and nothing else, it will undo any changes you made with root access and put everything back the way it was.
So as a cure-all in most soft brick situations, or as a method for getting the core part of an Android update, type:
fastboot flash system <system file name>.img
Finally, there's the vendor image. This is only present on newer phones, so don't worry if it's not in your factory images package. But if it's there, it contains a few important files, so type the following line to get this partition updated:
fastboot flash vendor <vendor file name>.img
After you've sent any or all of the above commands, you'll be ready to restart your device and boot into Android. To do that, type:
fastboot reboot.
At this point, your device should be fully updated, or if you were trying to recover from a soft brick, it should be running flawlessly.
Hello everyone
Please i'm in France and would like to upgrade to Pie
When i try nby updater no update appear
i'm on 8.1 with Nov Sec Patch
After an android update i lost my root on my phone. I tried to flash Magisk back with the same patched boot image as i did last time.
fastboot flash boot_a "boot.img"
fastboot flash boot_b "boot.img"
But now It's in a bootloop,
I tried flashing the unpatched boot.img from redfin-rd1a.200810.021.a1-factory-cd18efdf but that didn't help.
Is there a way to solve this without loosing all my data?
fr0sty said:
After a firmware update i lost my root on my phone. I tried to flash Magisk back with the same patched boot image as i did last time.
Click to expand...
Click to collapse
You lost me there, you updated firmware and then tried to use the patched image from the previous version? That's your issue if I'm reading correctly.
You can try
fastboot --set-active=a
iand see if you can at least boot, if so you'll have to extract the new boot image, patch it and see. Every time you update you need to use the new boot image. Sadly, it looks like you patched both A and B..
Edit- you can try flashing over the previous version or reflash the current version. If those all fail, I'm not sure what to suggest and some one with a bit more knowledge maybe can suggest a fix.
Ducter said:
You lost me there, you updated firmware and then tried to use the patched image from the previous version? That's your issue if I'm reading correctly.
You can try
fastboot --set-active=a
iand see if you can at least boot, if so you'll have to extract the new boot image, patch it and see. Every time you update you need to use the new boot image. Sadly, it looks like you patched both A and B..
Click to expand...
Click to collapse
Used the wrong words, Android 11 prompted me with an update, it was 1.7Gb. After that magisk was gone. So i booted into fastboot and flashed the patched magisk boot image again. The one i used for installing it the first time.
But magisk was updated in Android in the meantime. So maybe the patched version is not compatible anymore with magisk causing the boot loop? But the untouched boot image is also causing a boot loop.
Changed the boot slot, and flashed to the according letter, but no changes.
Maybe i need to flash the boot.img with a newer version of magisk. I was running the latest canary version. But i dont know how to patch the image without the phone working.
fr0sty said:
Used the wrong words, Android 11 prompted me with an update, it was 1.7Gb. After that magisk was gone. So i booted into fastboot and flashed the patched magisk boot image again. The one i used for installing it the first time.
But magisk was updated in Android in the meantime. So maybe the patched version is not compatible anymore with magisk causing the boot loop? But the untouched boot image is also causing a boot loop.
Changed the boot slot, and flashed to the according letter, but no changes.
Maybe i need to flash the boot.img with a newer version of magisk. I was running the latest canary version. But i dont know how to patch the image without the phone working.
Click to expand...
Click to collapse
If you were promoted with an update, updated, then proceeded to flash the boot image you were running prior to updating, that's not going to work. You'll need to track down a patched boot image for your current version you have flashed or reflash the update via fastboot, you can follow the guide posted and it walks you through the steps to not wipe everything.
I'm in the same position. I took the OTA update, then downloaded the 11.0.0 (RQ1A.210105.003, Jan 2021) from Google. I patched the boot.img with Magisk, put it on my laptop, and flashed it in fastboot. Now I'm getting a bootloop. I tried flashing the unpatched boot.img to try to just get back in, but I'm still bootlooping.
Did you ever find a solution? FWIW, I'm on AT&T. I noticed that sometimes there is an AT&T specific file, but that did not appear to be the case this time.
I finally fixed it. At first I didn't see that the latest factory image was on the end of the list here https://developers.google.com/android/images
I picked 11.0.0 (RQ1A.210105.003, Jan 2021), then i extraced the boot.img file from it and flashed it in fastboot with fastboot flash boot boot.img --slot all.
That resulted in a no command screen when booting. But i was able to boot in safe mode. And from there i could patch the new boot.img file with the latest magisk. After that i patched that in fastboot and now everything is working again!
You guys know that you can extract the actual boot.img from your Device after it installed the update? Should solve all problems. After the Update you can change the active Partition using fastboot (to be able to use the second Partition with the older System) just root the older System and extract the boot.img from the inactive (updated) Boot Partition. From here just Flash the Stock boot.img to the old System to remove root. Patch the extracted boot.img and flash it to the updated Boot Partition. Reboot, done.
saturday_night said:
You guys know that you can extract the actual boot.img from your Device after it installed the update? Should solve all problems. After the Update you can change the active Partition using fastboot (to be able to use the second Partition with the older System) just root the older System and extract the boot.img from the inactive (updated) Boot Partition. From here just Flash the Stock boot.img to the old System to remove root. Patch the extracted boot.img and flash it to the updated Boot Partition. Reboot, done.
Click to expand...
Click to collapse
For me my solution is easier, because i don't know all the fastboot commands to do the things you write
Well, you are not the only one with the exact same Problem (wrong boot.img or maybe broken dl) and there are several threads already. Just answering here because it was the newest.
If you or anybody else use the boot.img from your own device there will never ever be a Problem with it. I already wrote a step by step guide (with fastboot comands) for this somewhere on xda for one of my older devices. Just need to find it and i will link it here.
Hi ALL,
any chance that anyone rooted the Pixel 5 or pixel4a 5G then get the NSG working?
the device i have is rooted correctly and checked by (Root checker) however the Diag port is silent and not producing any log, need to get the NSG working...
please help !
Thanks