After grabbing the boot image matching my current version, patched with magisk, I am told by 2 different tutorials, one in this forum and one on youtube, quote: "Open a terminal in the directory your patched boot img file is and type 'fastboot flash boot magisk_patched.img".
No Problem, both tutorials instruct to type fastboot flash boot magisk_patched.img. My worry is that my file is labeled "magisk_patched-22100_xlAUj" as opposed to just "magisk_patched.img".
I assume I either did something wrong, or the file names have changed since the instructionals. Wanted to make sure before rooting with this patched file since I only have a very surface understanding of what I'm doing, and don't want to brick my phone.
FYI I did try the suggested 'fastboot flash boot magisk_patched.img' command but obviously didn't worry I assume because the file names are different.
I don't know what you already did, but if you can locate where you are along in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
It worked for me if you follow the steps as described.
the file name basically doesn't matter. as long as what you type into terminal matches what magisk gave you, you're fine. to be more specific to your case: since your file is called magisk_patched-22100_xlAUj.img, your terminal command has to be fastboot flash boot magisk_patched-22100_xlAUj.img. to explain further: what you're doing is that you're telling the program fastboot that it's supposed to flash (copy) a specific file to the boot partition on your phone. that specific file here is the one magisk created (magisk_patched-22100_xlAUj.img).
another solution would be to rename magisk_patched-22100_xlAUj.img to magisk_patched.img
Hey thanks so much, just wanted to make sure before I went through went it. However, I am getting a "disc image file is corrupted" message after hitting enter. I transferred the file by just drag and drop onto my pc. Couldn't get the adb pull command to work.
I even re-patched the boot img via magisk and retried, still getting same message. Every thing I'm doing appears to line up with the youtube tutorial. Would this be a case where I would try canary magisk build instead to patch? Or maybe I should make a new thread....
huh, that certainly is odd. no idea why that would happen. which version of magisk are you using and where did you get the boot.img?
Used this guide https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Got the boot.img from here https://developers.google.com/android/images?hl=en#sunfish (made triple sure it matched my current version)
Using Magisk 22.1 patched file in beta mode as instructed
i'm not sure is this is going to work, but here's a boot.img i patched. it's version sunfish-rq2a.210405.005-factory-ab0ba039. maybe try it, see if it works. just to cover my own ass: i'm not responsible if anything goes wrong. anyhow, it's probably a good idea to familiarise yourself with how to restore your phone to factory before flashing anything and keep a backup of the stock boot.img somewhere.
THEGAZINGVOID said:
i'm not sure is this is going to work, but here's a boot.img i patched. it's version sunfish-rq2a.210405.005-factory-ab0ba039. maybe try it, see if it works. just to cover my own ass: i'm not responsible if anything goes wrong. anyhow, it's probably a good idea to familiarise yourself with how to restore your phone to factory before flashing anything and keep a backup of the stock boot.img somewhere.
Click to expand...
Click to collapse
Is the patched image a 0b file? This is happened to me before too. The work around I do is to rename the boot image to something like boot_april.img before patching it in Magisk. Then check to make sure that the patched image isn't a zero byte file before copying it to your PC and flashing in fastboot.
breacherman said:
Hey thanks so much, just wanted to make sure before I went through went it. However, I am getting a "disc image file is corrupted" message after hitting enter. I transferred the file by just drag and drop onto my pc. Couldn't get the adb pull command to work.
I even re-patched the boot img via magisk and retried, still getting same message. Every thing I'm doing appears to line up with the youtube tutorial. Would this be a case where I would try canary magisk build instead to patch? Or maybe I should make a new thread....
Click to expand...
Click to collapse
See post above this one.
THEGAZINGVOID said:
i'm not sure is this is going to work, but here's a boot.img i patched. it's version sunfish-rq2a.210405.005-factory-ab0ba039. maybe try it, see if it works. just to cover my own ass: i'm not responsible if anything goes wrong. anyhow, it's probably a good idea to familiarise yourself with how to restore your phone to factory before flashing anything and keep a backup of the stock boot.img somewhere.
Click to expand...
Click to collapse
Ok, thanks, I might try that, but I'm not sure atm how to backup this stock rom without twrp.
buffal0b1ll said:
Is the patched image a 0b file? This is happened to me before too. The work around I do is to rename the boot image to something like boot_april.img before patching it in Magisk. Then check to make sure that the patched image isn't a zero byte file before copying it to your PC and flashing in fastboot.
Click to expand...
Click to collapse
Thanks for your suggestion but no, it's about 65mb in size.
breacherman said:
Ok, thanks, I might try that, but I'm not sure atm how to backup this stock rom without twrp.
Click to expand...
Click to collapse
I actually tried magisk canary build to patch the boot.img, and it failed, like before at first, I tried a second time to get a screeshot, and it worked for some reason.
You can follow this ↑↑↑ It's worked.
Related
I was able to change my splashscreen once, but changing it again doesn't seem to work. I place the PD98IMG.zip in the root of my SD card, overwriting the previous, and when I boot into bootloader I just see something come up like "parsing PD98IMG.zip" and it just finishes without giving me the option to volume up or down to actually change/load the new PD98IMG.zip file. Any ideas?
1.
I've tried deleting it completely/loading new file and I still have the same splashscreen.
Are you rooted? I've seen this behavior when S-ON is still active
Symmetric said:
Are you rooted? I've seen this behavior when S-ON is still active
Click to expand...
Click to collapse
Yes, I am rooted.
Sent from my Inspire 4G using XDA App
When you put the file in the PD98IMG.zip, did you unzip and then re-zip? If so, you should just open the zip file with 7zip/winrar/whatever so you can see inside, and then just paste your .img file inside. Then close it.
Other than that, we need more details. What process exactly are you doing. Are you creating your own .img with nbimg, or using someone else's already made .img
I am using some one else's .img file (mainly from the splashscreen emporium post) and I just move the file from my download folder to the root of my sdcard and click OK to overwrite with root explorer. I havent tried zipping and unzipping yet on the computer, but ill let you know if it works.
what i meant was don't unzip/rezip. Just browse the zip file and drop your .img in it. But since you're going with someone else's zip, i have no idea where the problem could be.
if you really want the splash screen, have a look at this thread http://forum.xda-developers.com/showthread.php?t=1059520
it's more difficult than just grabbing someone else's, but it's honestly not too bad, especially since he gives step-by-step instructions
Lost root after installing 9ZGgDXDi.zip.
This of course installed JB 4.1.1 but then when I go to recovery after entering fast boot menu I see a supine green robot with a red triangle with an exclamation point spilling out of its guts. (truly a horrible sight)
It also installed recovery-from-boot.p in System folder.
I know the solution is to rename recovery-from-boot.p file to recovery-from-boot.p.bak or renaming to something else or deleting, however since I lost root I don't see how I can rename or delete this file.
When I use root explorer I cannot mount r/w so cannot rename the file
Using ES File Explorer I rename the file but get the message that rename failed.
Connecting the phone via usb and turning on usb storage I can only access files from sd card and so cannot get to system folder in the parent directory.
Please can someone help destroy or rename the .p file.
If I'm reading it right, you lost your root and recovery after installing the OTA, right? You can still flash a custom recovery and install SU from said recovery after flashing CWM. You would then have the ability to rename the script which replaces the custom recovery with the stock. The file, if IIRC, is called recovery.sh or something along those lines.
Refer to this guide and re-root. Probably the easiest way to solve it. http://forum.xda-developers.com/showthread.php?t=1789216
chronophase1 said:
If I'm reading it right, you lost your root and recovery after installing the OTA, right? You can still flash a custom recovery and install SU from said recovery after flashing CWM. You would then have the ability to rename the script which replaces the custom recovery with the stock. The file, if IIRC, is called recovery.sh or something along those lines.
Click to expand...
Click to collapse
you are reading me right.
However I cannot flash anything thanks to recovery-from-boot.p file.
Whenever I try to flash anything I get message that "installation aborted"
Kitch16 said:
Refer to this guide and re-root. Probably the easiest way to solve it. http://forum.xda-developers.com/showthread.php?t=1789216
Click to expand...
Click to collapse
Tried that site, but the links to software are broken
edited to add:
oops, yes the links to software work, just didn't see the correct download for all the advertizements.
Thanks for your help but I have solved my problem by adb flash of cwr
koyanishi said:
you are reading me right.
However I cannot flash anything thanks to recovery-from-boot.p file.
Whenever I try to flash anything I get message that "installation aborted"
Click to expand...
Click to collapse
You get this from the fastboot screen?
chronophase1 said:
You get this from the fastboot screen?
Click to expand...
Click to collapse
I think its after fastboot screen - that is when I go to apply zip from sd card
However I have since solved the problem by using adb to install cwr again so I am now back to root
thanks to both of you for trying to help
Hi,
I tried the trickdroid ROM but i dont see any benefits, instead there are downsides, like wifi disconnecting and so on. I would like to go back to the original Stock ROM but i do not have the boot.img and nandroid does not back it up along with my backup. Without it, my wifi does not work.
Where can i get this boot.img, or can someone give it here? Thanks!
onlinechi said:
Hi,
I tried the trickdroid ROM but i dont see any benefits, instead there are downsides, like wifi disconnecting and so on. I would like to go back to the original Stock ROM but i do not have the boot.img and nandroid does not back it up along with my backup. Without it, my wifi does not work.
Where can i get this boot.img, or can someone give it here? Thanks!
Click to expand...
Click to collapse
http://www.4shared.com/file/k-UJs2Eo/RUU_VILLEC2_U_ICS_40_hTC_Asia_.html?aff=7637829
You can try this stock. by the way , I'm using Trickdroid V1.0,I do not have WiFi problem at all.You have to manually flash the boot img using fastboot.
i have strange problems where my 3g or wifi will stop connecting on TD. Even if i go to airplane mode it does not recover. I have to reboot phone. But last time i did not do a backup of my boot.img.. thats why i need it now
Is it possible that i just get the boot.img instead of downloading the whole giant file? thanks!
onlinechi said:
Is it possible that i just get the boot.img instead of downloading the whole giant file? thanks!
Click to expand...
Click to collapse
RUU file is a install script setup launcher where you can install onto your window then connect your phone to usb , execute this file , then follow the instruction on the screen . I do not have the boot img.
onlinechi said:
Is it possible that i just get the boot.img instead of downloading the whole giant file? thanks!
Click to expand...
Click to collapse
Possible to extract only the boot.img but not without downloading the whole big file.
Open the .exe and make sure that it fully started.
Don't click anything, just go to windows icon and search for %temp%.
You will now find some folders, just search through these folders for the ROM.zip.
If you found it, you can copy it to your desktop or somewhere else.
Extract it with WinRar,7-zip or something like that and take the boot_signed.img.
Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
Plug in your One S, go into the bootloader and go into fastboot mode.
Navigate with the cmd in the folder with the fasboot.exe and the two .img's.
Now type in that:
Code:
fastboot flash boot boot_signed.img
-----------------
This was copied from a thread in One X made by Setsuna666 and pasted there from user: torxx (http://forum.xda-developers.com/showthread.php?t=1609190), but applies for any RUU file extraction. It is not from me, but this method works.
So I changed the boot animation to something different. The animation is so heavy the phone lags halfway in between and now my phone can't even get past the boot animation screen. It's stuck at the boot animation. Anyway to revert this?
Download the default boot animation from here: http://forum.xda-developers.com/google-nexus-5/themes-apps/bootanimation-nexus-5-animations-t2789918
Scroll down a bit and you'll find the default Lollipop animation. Download the zip which is supposed to be manually installed.
Put it in system/media/bootanimation.zip
You can use Aroma File Manager for this. AromaFM is a flashable zip which brings up a file manager in your recovery
experience7 said:
Download the default boot animation from here: http://forum.xda-developers.com/google-nexus-5/themes-apps/bootanimation-nexus-5-animations-t2789918
Scroll down a bit and you'll find the default Lollipop animation. Download the zip which is supposed to be manually installed.
Put it in system/media/bootanimation.zip
You can use Aroma File Manager for this. AromaFM is a flashable zip which brings up a file manager in your recovery
Click to expand...
Click to collapse
I can't even access my phone's storage so how am I suppose to use the zip? Are you saying I can flash the zip file while the phone is in fastboot/recovery?
If you're using TWRP as a recovery you can access your storage. It does support MTP.
Yeah, the file manager has to be flashed just like a ROM.
experience7 said:
If you're using TWRP as a recovery you can access your storage. It does support MTP.
Yeah, the file manager has to be flashed just like a ROM.
Click to expand...
Click to collapse
And that's the problem. I'm running a stock rom (4.4.2) with no TWRP or CWM.
The phone is rooted and the boot-loader is unlocked.
Bootloader unlocked. So where's the problem?
Download latest TWRP and execute
fastboot flash recovery twrp.img
to flash it.
Or simply
fastboot boot twrp.img
to launch it once. You don't even need to flash it.
experience7 said:
Bootloader unlocked. So where's the problem?
Download latest TWRP and execute
fastboot flash recovery twrp.img
to flash it.
Or simply
fastboot boot twrp.img
to launch it once. You don't even need to flash it.
Click to expand...
Click to collapse
AYEEEEE!!! I see where you're going with this now. I think I get it now. I'll try tonight or maybe in a couple of hours and then I'll come back if any problems. Once finished I'll let you know with a thanks
By the way: After copying the new (default lollipop) bootanimation.zip to /system/media do a 'fix permissions' in TWRP. Not quite sure if the option is available in TWRP but if it is, just do it. It won't do any harm
Alright I flashed TWRP and it's working but the file manager kinda sucks. I mean it's picking up the files and their aren't any options to copy and paste. The boot animation is stored in /system/media and when I go into the system folder all I see is "bin" and nothing else. I don't understand what's the problem
Man, the file manager does not suck. A little more respect to the developer! You should be thankful, not disrespectful!
Enable hidden files in the file manager and you'll see them. And it also does provide copy/paste functionality. I've used it several times.
EDIT: If you still don't see them after enabling hidden files you have to mount the system partition.
experience7 said:
Man, the file manager does not suck. A little more respect to the developer!
Enable hidden files in the file manager and you'll see them. And it also does provide copy/paste functionality. I've used it several times.
Click to expand...
Click to collapse
I searched everywhere and I don't see an option to enable hidden files. How did you enable hidden files?
It's in the lower right corner if I remember correctly. Three dots which will bring up a menu.
...
experience7 said:
It's in the lower right corner if I remember correctly. Three dots which will bring up a menu.
Click to expand...
Click to collapse
What version of TWRP are you using? I don't see three dots anywhere. The bottom always has a back button on the right, a button to launch terminal in the center and a home button on the left
Dude. It has nothing to do with TWRP version at all. You didn't even launch Aroma File Manager... that's the point.
Read my previous posts again, take your time & don't double post (there's an option to edit if you have to).
experience7 said:
Dude. It has nothing to do with TWRP version at all. You didn't even launch Aroma File Manager... that's the point.
Read my previous posts again, take your time & don't double post (there's an option to edit if you have to).
Click to expand...
Click to collapse
Sorry for being impatient.
Do I flash Aroma the same way I flashed TWRP? If so will this cause any problems or anything? TWRP can't install Aroma from SD because my computer won't even pick up my phone
If you're in TWRP, connect your phone to your computer. It should be detected just like any Android phone since it's also using MTP.
Aroma File Manager has to be flashed in TWRP (install zip). That's why you had to flash TWRP in the first place.
experience7 said:
If you're in TWRP, connect your phone to your computer. It should be detected just like any Android phone since it's also using MTP.
Aroma File Manager has to be flashed in TWRP (install zip). That's why you had to flash TWRP in the first place.
Click to expand...
Click to collapse
Better yet as soon as I connected my phone to my PC, TWRP's file manager started working. I deleted the corrupted bootanimation.zip that made my phone lag in the first place. However it keeps failing to move the other bootanimation.zip into /system/media (I backed up the stock boot in /system/media by renaming it
EDIT: Never-mind I got it. I renamed the file from 0bootanimation.zip to "android" and then to bootanimation.zip
I restarted my phone and it's just stuck in the boot loop. The animation is occurring forever and nevermind it just started.
Thank you experience7!!! Massive vouch for you man. You saved me so much trouble. Much love from me =D
As said before... TWRP uses MTP to enable file transfer between your computer and your phone. However, you'll only see your internal storage (pictures, videos and stuff like that) - not the system partition. That's why you should use Aroma File Manager! It lets you access the system partition directly on the phone and provides everything you need (copy/paste/delete and so on).
I have no idea what file you actually deleted. But I'm pretty sure it was not the one in /system/media.
experience7 said:
As said before... TWRP uses MTP to enable file transfer between your computer and your phone. However, you'll only see your internal storage (pictures, videos and stuff like that) - not the system partition. That's why you should use Aroma File Manager! It lets you access the system partition directly on the phone and provides everything you need (copy/paste/delete and so on).
I have no idea what file you actually deleted. But I'm pretty sure it was not the one in /system/media.
Click to expand...
Click to collapse
And that's the most weird part of all...
1) TWRP file manager started working as soon as I connected my phone to my PC. I didn't need to flash AromaFM. TWRP worked like a charm
2) I deleted the laggy bootanimation.zip and replaced it with the stock one I backed up. I backed up the stock animation by renaming it to a different file. However TWRP always failed to rename the stock animation to bootanimation.zip. So I renamed it entirely different (to android) and then back to bootanimation.zip and it worked like a charm.
Does that make sense now? I don't know what the hell just happened but I ain't complaining
It ends up in recovery mode so I just turn it off and boot up again and it says update failed. I realize it will lose root so I'll have to reroot but will it lock the bootloader again also? I'm just tired of seeing it everyday want to update so figured I'd let it do it but it does't seem to work. Is there a manual update file somewhere? I googled but I can't find it. Should I find the complete rom and re-install the newest version?
jeffrimerman said:
It ends up in recovery mode so I just turn it off and boot up again and it says update failed. I realize it will lose root so I'll have to reroot but will it lock the bootloader again also? I'm just tired of seeing it everyday want to update so figured I'd let it do it but it does't seem to work. Is there a manual update file somewhere? I googled but I can't find it. Should I find the complete rom and re-install the newest version?
Click to expand...
Click to collapse
Bootloader will stay unlocked. If it's an OTA it's trying to install it will fail IF it wants to patch ramdisk as you're rooted.
You can restore stock ramdisk and it should update correctly, but I'd use FullOTA instead for best compatibility.
You can install FullOTA either using HWOTA or installing TWRP (by Pretoriano80 as it has decryption support) and use HuRUpdater script to update.
ante0 said:
Bootloader will stay unlocked. If it's an OTA it's trying to install it will fail IF it wants to patch ramdisk as you're rooted.
You can restore stock ramdisk and it should update correctly, but I'd use FullOTA instead for best compatibility.
You can install FullOTA either using HWOTA or installing TWRP (by Pretoriano80 as it has decryption support) and use HuRUpdater script to update.
Click to expand...
Click to collapse
I have TWRP 3.2.1-0 since I installed Oreo. Is the full ota downloaded into my phone somewhere since it seems to download it fine then I can install it with TWRP? Or do I need to find it online somewhere. Since it ends up in TWRP after trying to install if it was someplace I can find then maybe I can just install whie in TWRP. I'll google for HuRpdater script or is it on here somewhere? I just googled but nothing came up.
jeffrimerman said:
I have TWRP 3.2.1-0 since I installed Oreo. Is the full ota downloaded into my phone somewhere since it seems to download it fine then I can install it with TWRP? Or do I need to find it online somewhere. Since it ends up in TWRP after trying to install if it was someplace I can find then maybe I can just install whie in TWRP. I'll google for HuRpdater script or is it on here somewhere? I just googled but nothing came up.
Click to expand...
Click to collapse
Updates go to /data/update/
But you can download it from http://pro-teammt.ru/firmware-database/ (download update.zip, public zip and data zip for your firmware. You can click the File list link after you have searched to find the public and hw data)
And HuRUpdater is found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
TWRP can't install huawei update.zips by default, so you'd have to download firmware then use HuRUpdater to flash it.
ante0 said:
Updates go to /data/update/
But you can download it from http://pro-teammt.ru/firmware-database/ (download update.zip, public zip and data zip for your firmware. You can click the File list link after you have searched to find the public and hw data)
And HuRUpdater is found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
TWRP can't install huawei update.zips by default, so you'd have to download firmware then use HuRUpdater to flash it.
Click to expand...
Click to collapse
I found the files where you said, thanks. update_data_public.zip, update_MHA_L29_hw_usa.zip, and update.zip
When I read the instuction it calls for 3 files 2 of which are already spelled out correctly but looks like I need to rename the MHA file to update_all_hw.zip is this correct?
It also says to put the recovery image in the same folder if I want to keep custom recovery so sounds like it will wipe it if I don't. I'll have to download twrp 3.2.1-0 again
Ok this is interesting, I have 2 files in data with 6 digit names 151465 and 161808 and both have the 3 files but they are of different sizes but the exact same names as I mentioned before. Maybe better to go to the website you mentioned or I'll screw something up with them.
Figured out how to open the file list and can see the 3 files now so I'll get all 3. Update.zip is 2gb is that right? It's gonna take like 5 hours it says.
jeffrimerman said:
I found the files where you said, thanks. update_data_public.zip, update_MHA_L29_hw_usa.zip, and update.zip
When I read the instuction it calls for 3 files 2 of which are already spelled out correctly but looks like I need to rename the MHA file to update_all_hw.zip is this correct?
It also says to put the recovery image in the same folder if I want to keep custom recovery so sounds like it will wipe it if I don't.
Ok this is interesting, I have 2 files in data with 6 digit names 151465 and 161808 and both have the 3 files but they are of different sizes but the exact same names as I mentioned before. Maybe better to go to the website you mentioned or I'll screw something up with them.
When I click on the "update" hyperlink it just opens a new page and doesn't seem to start downloading. Maybe I need to do something else?
Click to expand...
Click to collapse
Rename the zip with HW in its name to update_all_hw.zip and Public to update_data_public.zip.
If recovery.img is present in the same dir as guru it will flash it back to recovery_ramdisk after update is flashed. It's to save a step so you don't have to reboot to fastboot to flash it again.
/data/update includes old/partial downloads too. So if you for example have used eRecovery before to download, but cancelled it, the update is still there. Same goes for system update. I would rather use firmware finder/teammt because you know those are completed zips.
On the site you can click on file list to show links to downloads, the update link rarely works anymore. It just parses data from hicloud but for some reason the update link always points to front page (or to search results if you have searched).
So just copy paste the update, public and Hw l29 links into a new tab to download.
jeffrimerman said:
Figured out how to open the file list and can see the 3 files now so I'll get all 3. Update.zip is 2gb is that right? It's gonna take like 5 hours it says.
Click to expand...
Click to collapse
That's correct.
It's going to erase everything isn't it? Rename the TWRP to "recovery" right? Since it's already a .img file I imagine I don't need to add ".img" right?
jeffrimerman said:
It's going to erase everything isn't it? Rename the TWRP to "recovery" right? Since it's already a .img file I imagine I don't need to add ".img" right?
Click to expand...
Click to collapse
Updating doesn't wipe. And HuRUpdater will tell you if it should wipe, it will also tell you if it will lock bootloader.
Yes, if you don't have "show extentions" turned on in Windows just rename it to recovery.
ante0 said:
Updating doesn't wipe. And HuRUpdater will tell you if it should wipe, it will also tell you if it will lock bootloader.
Yes, if you don't have "show extentions" turned on in Windows just rename it to recovery.
Click to expand...
Click to collapse
It didn't erase anything woooo hoooo. Thank you. I did loose root which will be easy to put back on. At the end if installing everything automatically there were 2 buttons on the bottom. One was erase cache/dalvik I think and the other was reboot so I just rebooted to be safe. Figured if it was buggy I could always go back and erase the cache/delvik but looks fine. Just checked and my TWRP is there so all is good