Related
First:
Hoping someone can provide some assistance. I would like to get back to stock ICS 4.0.4 on my Verizon Xoom 4G LTE since i am hoping that 4.1.1 will be released soon OTA. Does anyone have stock 4.0.4 download? With or without root is fine. Stock 3.X would be ok to. I just want to get back to stock.
Second: In case anyone has any ideas
I have several 4.0.4. Nandroids that will not restore for me in CWM. Very recently I did two things that I am wondering if might have caused part of the problem:
1) Upgraded to new CWM 6.0.1.9
2) Flashed a test 4.2 ROM
Thoughts?
puothy said:
First:
Hoping someone can provide some assistance. I would like to get back to stock ICS 4.0.4 on my Verizon Xoom 4G LTE since i am hoping that 4.1.1 will be released soon OTA. Does anyone have stock 4.0.4 download? With or without root is fine. Stock 3.X would be ok to. I just want to get back to stock.
Second: In case anyone has any ideas
I have several 4.0.4. Nandroids that will not restore for me in CWM. Very recently I did two things that I am wondering if might have caused part of the problem:
1) Upgraded to new CWM 6.0.1.9
2) Flashed a test 4.2 ROM
Thoughts?
Click to expand...
Click to collapse
Nevermind....finally found files I was looking for. just took some digging!
Care to share the process? I'm thinking of doing the same thing
nbajwill55 said:
Care to share the process? I'm thinking of doing the same thing
Click to expand...
Click to collapse
I started with MZ602_HLK75D (trying to find where I downloaded from. If you can't find let me know and I will put it on drop box)
You will lose everything on you internal SD card so make sure to pull anything you want off your Xoom before you start. USB Debugging needs to be enabled as well
Extract the MZ602_HLK75D zip file so you have: boot.img, system.img, recovery.img, userdata.img and place these files in your SDK folder
Open a command prompt by SHIFT + RIGHT CLICK on your SDK FOLDER
Adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
After it reboots and you sign in etc it will check for upgrade and there will be a few Honeycomb upgrades before you get back up to 4.0.4 (locked and w/out root & w/out CWM but you can just redo that part too)
I cannot find the file MZ602_HLK75D.zip. Could you provide a link? Thanks.
Let me know if this works:
https://www.dropbox.com/s/cstj6gwxhcfaxm7/MZ602_HLK75D.zip?n=95544115
tselling said:
I cannot find the file MZ602_HLK75D.zip. Could you provide a link? Thanks.
Click to expand...
Click to collapse
puothy said:
Let me know if this works:
https://www.dropbox.com/s/cstj6gwxhcfaxm7/MZ602_HLK75D.zip?n=95544115
Click to expand...
Click to collapse
Thanks
tselling said:
I cannot find the file MZ602_HLK75D.zip. Could you provide a link? Thanks.
Click to expand...
Click to collapse
Motorola has put them back up at -> https://motorola-global-portal.custhelp.com/app/standalone/rom-images
KidJoe said:
Motorola has put them back up at -> https://motorola-global-portal.custhelp.com/app/standalone/rom-images
Click to expand...
Click to collapse
thank you for sharing. Wish I had this several months ago. Took my hours to find a live link so I could download the file.
puothy said:
Let me know if this works:
https://www.dropbox.com/s/cstj6gwxhcfaxm7/MZ602_HLK75D.zip?n=95544115
Click to expand...
Click to collapse
Thanks for the files and instructions. Not planning to return to stock anytime soon but these are good to have just in case.
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.
Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Click to expand...
Click to collapse
Ok thanks! I had a few people give me the wrong command line that's prolly why it wasn't working. I'll give this a shot later!!
Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.
Click to expand...
Click to collapse
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??
mpetruzz said:
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??
Click to expand...
Click to collapse
If you get that error message it sounds like you don't have the right path for it to find that file. With the phone in bootloader mode I type in the command then drag the bit image into the terminal window and execute. I use a Mac so I don't know if you can drag the file in on a Windows machine. You'll have the same issue with the flash all if you don't have the right path.
mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.
bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
OK so i'm in the system image file for 7.1 and am not seeing the recovery.img. Must be doing something wrong, but it's def not there. Anywhere else I can grab it from?
Also once I get it what would the adb command line be to flash it?
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
I got it and am all set!! Used the skipsoft tool to flash the stock recovery, then sideloaded the OTA!!
Thanks brother for all the help!!!!
Click to expand...
Click to collapse
Hey I'm pretty new to this but is there a way I can update without a computer, I dont mind losing root as long as I'm still unlocked... I'm using a Verizon phone on at&t if that matters... If not I can always to it tomorrow when I can get to a computer..
bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse
Got it, man this pixel is crazy different than what I'm used too. Thanks all for the help!
Click to expand...
Click to collapse
10i for T-Mobile V20 H918 is out.
It's still anti-rollback v00. :good:
Android Security Patch: 2016-12-01 (dirtycow/recowvery patched)
Download Link
UPPERCUT should work if using LGUP/KDZ.
If you flash this KDZ there is no current root method for 10i... so no TWRP etc (at this very moment anyway).
Everyone who can only boot to download mode.. this should save you.
those w/TWRP already can use the images (or wait for someone to make a flashable "rom" zip.
H91810-system.img.zip is just the system.img compressed, not a flashable zip.
if flashing the stock system.img/boot.img be careful not to lose TWRP..
delete the "recovery-from-boot.p" in system while still in TWRP if you want to be extra safe.
I don't have a V20 and won't be supporting this thread. Just providing files.
Thanks for this. Wonder what the changes from v10d are (other the exploit patch)
If and when someone creates a flashable zip, can we flash SuperSU after we flash the ROM to still have root?
Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..
I love you daddi
Is this also OTA? I see nothing
kyledowling said:
If and when someone creates a flashable zip, can we flash SuperSU after we flash the ROM to still have root?
Click to expand...
Click to collapse
yes, that's how it works. tho.. idk if it's user-error or what... sometimes people flash supersu and it doesn't patch the boot.img and when they boot into android they lose twrp. hasn't happened to me but ¯\_(ツ)_/¯ . so that's why I also suggested removing the recovery-from-boot.p as an option.
people could also just dd the images manually if they don't want to wait for a zip... but I guess those comfortable with dd already know that.
Swizzle82 said:
Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..
Click to expand...
Click to collapse
lol just don't put a sim in or connect it to wifi before you use recowvery.
autoprime said:
yes, that's how it works. tho.. idk if it's user-error or what... sometimes people flash supersu and it doesn't patch the boot.img and when they boot into android they lose twrp. hasn't happened to me but ¯\_(ツ)_/¯ . so that's why I also suggested removing the recovery-from-boot.p as an option.
people could also just dd the images manually if they don't want to wait for a zip... but I guess those comfortable with dd already know that.
lol just don't put a sim in or connect it to wifi before you use recowvery.
Click to expand...
Click to collapse
Great idea.. Sometimes you're smart, lol
Swizzle82 said:
Great idea.. Sometimes you're smart, lol
Click to expand...
Click to collapse
altho now that i think about it.. they may force you on the setup screen. but theres no way it'll download/install in the time it takes to get through setup. so just disable internet as soon as you're setup. :good:
autoprime said:
altho now that i think about it.. they may force you on the setup screen. but theres no way it'll download/install in the time it takes to get through setup. so just disable internet as soon as you're setup. :good:
Click to expand...
Click to collapse
What I usually do is make a twrp back up from my old phone and restore it on the new phone after making a fake backup and moving the old one in the new folder the fake backup created. Theoretically this should restore my google account without ever having to initially setup my account when I turn on the new phone. Right? Or do you think it'll cause authentication issues?
Swizzle82 said:
Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..
Click to expand...
Click to collapse
As long as it isn't preloaded you should be able to get around it...
Common sense isn't all that common
ZDeuce2 said:
As long as it isn't preloaded you should be able to get around it...
Common sense isn't all that common
Click to expand...
Click to collapse
I'm sure I'll get it figured out.
Hopefully @Eliminater74 will make part 1 & 2 ROM for H918 users.
mingkee said:
Hopefully @Eliminater74 will make part 1 & 2 ROM for H918 users.
Click to expand...
Click to collapse
Is he coming to the v20. Plz say yes.
System.img.zip, do I just rename it to system.img? Cause I extracted from zip file and system.img did not flash. But when I renamed it, it flashed but wouldn't boot.
kcsevo said:
System.img.zip, do I just rename it to system.img? Cause I extracted from zip file and system.img did not flash. But when I renamed it, it flashed but wouldn't boot.
Click to expand...
Click to collapse
If you really want this, just use the LG Bridge and update it through that. It's much easier than flashing manually and accomplishes the same thing.
kibmikey1 said:
If you really want this, just use the LG Bridge and update it through that. It's much easier than flashing manually and accomplishes the same thing.
Click to expand...
Click to collapse
Oh sweet! But for the file itself do I need to extracted or rename the file? I flashed the system.img and boot in twrp but it hung in LG logo. And I'm also trying to retain root.
kcsevo said:
Oh sweet! But for the file itself do I need to extracted or rename the file? I flashed the system.img and boot in twrp but it hung in LG logo
Click to expand...
Click to collapse
You don't need the file at all. Just download the LG Bridge from the LG website, install the LG Universal mobile drivers, plug in your phone and use the software update option. It does it all by itself, and will restart your phone on it's own.
kibmikey1 said:
You don't need the file at all. Just download the LG Bridge from the LG website, install the LG Universal mobile drivers, plug in your phone and use the software update option. It does it all by itself, and will restart your phone on it's own.
Click to expand...
Click to collapse
Do i need to be back factory stock including recovery to use this option? And I'm guessing this way would make me lose root? Thank you for your responses.
kcsevo said:
Do i need to be back factory stock including recovery to use this option? And I'm guessing this way would make me lose root? Thank you for your responses.
Click to expand...
Click to collapse
You only need to plug in your phone and let it work. Since this is a stock image, you will lose root. Also, the as described in the original post on page 1, the December security patch also patches the dirty cow exploit used to achieve root, so once you flash this, you'll be stock unrooted until a new method comes along.
Hi everyone! By any chance someone has the stock recovery of U11+ EMEA/Europe version? 1.24.401.7 version..
stock recovery U11+ 1.24.401.7
ShinGaiven said:
Hi everyone! By any chance someone has the stock recovery of U11+ EMEA/Europe version? 1.24.401.7 version..
Click to expand...
Click to collapse
Have a look here if thats what you're looking for
Here is another link, if that helps you. Good Luck
freebsd124 said:
Have a look here if thats what you're looking for
Here is another link, if that helps you. Good Luck
Click to expand...
Click to collapse
Thanks for trying mate! Unfortunately the link is giving me the OTA RUU file, basically what I'm trying to find is only the stock recovery.img file for the specific version.
ShinGaiven said:
Thanks for trying mate! Unfortunately the link is giving me the OTA RUU file, basically what I'm trying to find is only the stock recovery.img file for the specific version.
Click to expand...
Click to collapse
Ok, I understand; still wanna give you a heads up. If you download the RUU file representing your version (1.24.401.7) you need to use the RUU_decrypt_tool to be able to extract the recovery.img
This link might give you the information you possibly need.
I hope it helps you; I know what it feels like not having the .img-files if you, sort of, stuck
freebsd124 said:
Ok, I understand; still wanna give you a heads up. If you download the RUU file representing your version (1.24.401.7) you need to use the RUU_decrypt_tool to be able to extract the recovery.img
This link might give you the information you possibly need.
I hope it helps you; I know what it feels like not having the .img-files if you, sort of, stuck
Click to expand...
Click to collapse
Wow! Thanks for this one when I'm free I'll try that and will update you. In fact the phone I'm using is working out fine. This is a Demo unit for commercial purposes and by default demo content keeps running in the background and wipe out Data agressively..I unlocked bootloader, flashed TWRP, and mount system partition and deleted the Demo file manually. The reason why I need the img file is for me to restore the stock recovery and try if it's gonna work. I've done on my U11 and wanted to give it a try on my plus version..
recovery.img file
ShinGaiven said:
Wow! Thanks for this one when I'm free I'll try that and will update you. In fact the phone I'm using is working out fine. This is a Demo unit for commercial purposes and by default demo content keeps running in the background and wipe out Data agressively..I unlocked bootloader, flashed TWRP, and mount system partition and deleted the Demo file manually. The reason why I need the img file is for me to restore the stock recovery and try if it's gonna work. I've done on my U11 and wanted to give it a try on my plus version..
Click to expand...
Click to collapse
If you extracted the recovery_signed.img file rename it to recovery.img, just to be shure (I did) from there on its just "fastboot flash recovery recovery.img" (without the quotes)
can someone help me get the stock recovery for htc u11 plus 2.19.401.2 EU.
Thanks
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Gregbmil1 said:
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Click to expand...
Click to collapse
Hey, thanks for your reply. I am really eager to root it. I almost just went for it. However, then I thought about it. If something went wrong I would not have any way to recover the phone since there is not a system image available yet. I have not given adb removal a try yet as I figure it would just be easier to go with rooting since it will help me with everything I am trying to achieve. If I cannot root it then I will go the adb route. Hopefully someone will come along and help me out. Fingers crossed
Let us know what you end up doing. Are you expected to send the phone back after the beta testing? If you are responsible for any damages done to it, I would not try it.
You could send it back bricked and say you have no idea what happened to it, lol. That or say you were "testing" the security of the device and that it passes
bigroc2223 said:
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
Click to expand...
Click to collapse
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
dladz said:
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
Click to expand...
Click to collapse
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
bigroc2223 said:
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
Click to expand...
Click to collapse
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
dladz said:
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
Click to expand...
Click to collapse
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
bigroc2223 said:
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
Click to expand...
Click to collapse
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
dladz said:
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
Click to expand...
Click to collapse
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
bigroc2223 said:
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
Click to expand...
Click to collapse
You're very welcome.
Chances of it not booting after doing that? Absolutely zero.
It's a copy not a cut, so you're fine.
The only problem you may encounter is the ability to access the device on that level.
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
I would advise against flashing it, just boot it.
dladz said:
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
Click to expand...
Click to collapse
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
jwoegerbauer said:
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
Click to expand...
Click to collapse
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
bigroc2223 said:
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
Click to expand...
Click to collapse
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It's a phone for testing which I am allowed to keep.
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It is a phone for testing which I am allowed to keep. Specs are Snapdragon 750g, Adreno 619, and 4gb of ram. Not too shabby for a free phone. It is a lot snappier than the moto e6 I was previously using.
dladz said:
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Click to expand...
Click to collapse
This method requires TWRP. So this will not work.
bigroc2223 said:
Nvm
Click to expand...
Click to collapse
dladz said:
Again!!!? What's your problem??
You're just trying to (for whatever reason) prove me wrong and yet again I wasn't being descriptive of an ADB pull!!!
You're pulling the boot.img off the device by whatever means.
To be clear for the final time, I'm not stating to use twrp, a script or anything else I said look it up / Google it!
Now if you've helped the chap then that's great, looking at what I said and attempting to put me straight when you clearly don't have to, is no help to you or the chap needing help it's just making you look like you're on a power trip.
Click to expand...
Click to collapse
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
bigroc2223 said:
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
Click to expand...
Click to collapse
Sorry I got the wrong end of the stick, I thought you was a second person posting..
Forget what I said