Database Users

New method to downgrade and root 183.46.15version of kitkat4.4.2 (for XT926 UNLOCKED)

This METHOD was developed ONLY for an UNLOCKED Motorola Droid Razr Maxx HD XT926m phone that is already updated to the last version of KitKat 4.4.2 (System version "183.46.15.XT926.Verizon.en.US").
IF YOU HAVE AN LOCKED BOOTLOADER AND TRY THIS METHOD IT WILL BE ONLY YOUR RESPONSABILITY IF YOU DAMAGE YOUR PHONE !!!
My Motorola XT926m had an UNLOCKED BOOTLOADER (ICS 4.0.4) and I flashed via RSD Lite the last stock firmware, "183.46.15"... After that, I was, of course, unhappy, because I read on different forums that this firmware version didn't support root... I tried to download the Hydrogen Peroxide xt926 application that others users recommended here on XDA forum, without success.
But now, after I applied this method, my phone is again rooted... Enjoy the steps, but be carefull, it was developed for XT926 phones with UNLOCKED BOOTLOADER!
1. Download the files "VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml" and "VZW_XT926_4.4.2-KDA20.62-15.1_CFC_1FF.xml" from the Motorola firmware site: "motofirmware.com/files/file/"...
2. Unpack the files...
3. Substitute/replace the "gpt", "tz" files (FROM the folder with "15.1" version TO the folder with "10.1" version)... You should replace all the files that "RSD Lite" will tell you that don't fit when you try to flash the new stock firmware. You will obtain a MODIFIED version of "183.46.10" stock KitKAt 4.4.2 firmware!!!
4. Flash this MODIFIED "10.1" firmware with "RSD Lite v6.1.5 Multi-Flash" (without using Rsd Script Generator.jar), but don't forget to remove the first two 'getvar' lines in the xml file.
5. Download and install the "Towel Root.apk" and root the phone...
6. Now your phone should be ROOTED.
What to do NEXT:
7.Download from the Play Store and install "Superuser.apk" made by ClockWordMode and after reboot the application will ask you to update SU binary. In my case, the SU binary didn't support an online update and I installed the "Superuser.zip" file downloaded from the ClockWorkMode site, via recovery method, in order to gain this update (you can do this as well, if you already have a TWRP or CWM recovery installed on your phone). With the other version of superuser, like "SuperSU.apk" or "Superuser.apk" ("eu.chainfire.supersu-2.apk", the last version, 5.6mb, for example) you will need to follow the same steps...
8. Using "Total Commander.apk", you can go to "File System root"/"Etc"/"installrecovery.sh", and finally rename this last file... Or you can use "ES3 File Explorer.apk" in order to rename the same "installrecovery.sh" file in "Device"/"Etc" folder (choose, for example, the name "installrecovery.shbak")...
9. Flash with "Flashify.apk" (downloaded form PLay Store) a new "recovery img.": "TWRP.img" (2.8.3.0) or "CWM.img" (6.0.4.8) for KitKat... You can find them on "rootjunkysdl.com/?device=Droid%20Razr%20HD&folder=Firmware"...
10. If you flashed "TWPR recovery.img" you will need to install "Stericson.busybox-1.apk" (from Play Store...), because TWRP works with this busy box... (You could install "TWRP.apk" as well, but you must be careful, because you will need to be able to boot into Recovery mode directly from your phone (with the combination key), not from this app... Many times, the phone is able to boot into recovery mode from TWRP application, but not from the bootloader... That's why it is better to uninstall TWRP application if you have this problem). If you flashed a "CWM.img" you can install "RomManager.apk".
11.Now it is the time to backup your system to SD card!
That's it. My phone was unlocked, and I didn't have any issue following all this steps... If you're locked don't try it.
But.. If you're locked you could instead use an application named 'Safestrap' for some purposes (read more here on XDA forum please), because is destinated for the phones with locked bootloader...

Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General

jackeagle said:
Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General
Click to expand...
Click to collapse
THANKS!

I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.

RikRong said:
I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.
Click to expand...
Click to collapse
Thank you, I wasn't able to find another downgrade method, could you give me the link, please?

http://forum.xda-developers.com/showthread.php?t=2789743

But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...

joel_sinbad said:
But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...
Click to expand...
Click to collapse
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.

RikRong said:
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.
Click to expand...
Click to collapse
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...

joel_sinbad said:
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...
Click to expand...
Click to collapse
This method is for an XT926 with UNLOCKED BOOTLOADER, with the last 183.46.15 update and the root access lost. I only described the steps that I already done with my phone. My Maxx HD is working and has root access again... I flashed custom recovery too (TWRP 2.8.3.0), I haven't any other problem.

RikRong said:
http://forum.xda-developers.com/showthread.php?t=2789743
Click to expand...
Click to collapse
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.

ciprianv. said:
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.
Click to expand...
Click to collapse
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.

RikRong said:
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.
Click to expand...
Click to collapse
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).

ciprianv. said:
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).
Click to expand...
Click to collapse
Thanks for doing that, I just want to make sure no one messes up their phone.

Moto Z Play Rooting Guide

As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
If this didn't work you can also try flashing this modified boot.img, it has only been tested with the Mexican AT&T variant, so I don't know if it will work properly with other variants.

Thanks!
I would try this if I was certain Flashfire would work...(don't want to reflash for an OTA)

diegochiva95 said:
where? I want to see him
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-z-play/help/unlocked-bootloader-t3459976/page4
Post number 34

I take it back, sadly it is stuck at boot for me I tried it yes. No other SuperSu? I think I had the 03 version and you have 02... I think?
EDIT: not true, I had 02 too, but it just wouldn't work.
EDIT: It forced somewhat of a factory reset on me when I tried the same SuperSU but no systemless, I didn't lose any media but I had to relog in my account and download and update all apps again.
I will just wait for nougat...

several people commented that password is required to enter the recovery......
Enviado desde mi XT1635-02 mediante Tapatalk

diegochiva95 said:
several people commented that password is required to enter the recovery......
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
The same password that you used to encrypt the phone while setting it up. If you're using a pattern you can use the numbers equivalent to the pattern you used.

FreedFromDeath said:
As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
Click to expand...
Click to collapse
Thanks for the tutorial. But was inquisitive to know why one cannot use systemless root on our Vertex??
Thanks!

great
just pick up my phone
btw 7 is not released yet right

hmnk said:
Thanks for the tutorial. But was inquisitive to know why one cannot use systemless root on our Vertex??
Thanks!
Click to expand...
Click to collapse
This isn't the Vertex though, this is the Addison.

FreedFromDeath said:
This isn't the Vertex though, this is the Addison.
Click to expand...
Click to collapse
http://www.gsmarena.com/moto_z_play...r_testing_55inch_screen_in_tow-news-19195.php
Anyways, coming back to the topic, why can't we use systemless root on our device?
Thanks,
Regards.

FreedFromDeath said:
As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
Click to expand...
Click to collapse
says it is not necessary to flash the .zip SuperSU only accept the root for the TWRP own. It is true?

diegochiva95 said:
says it is not necessary to flash the .zip SuperSU only accept the root for the TWRP own. It is true?
Click to expand...
Click to collapse
Isn't there a warning to never accept the root from the recovery?

Another thing, if deencryption doesn't work you can sideload the SuperSU zip using adb through TWRP.

Updated OP with a possible workaround.

FreedFromDeath said:
Updated OP with a possible workaround.
Click to expand...
Click to collapse
If you dont mind, could you provide the details of your device?

So I see there is a Chinese twrp for moto z play but is anyone working on a north American version? Same question for SuperSU? Will there be official versions with systemless root? I guess what I'm asking is should I wait a bit or go this route? I like otas. I also reeeeally like a rooted phone (exchange server BS needs to be bypassed for piece of mind).

Not enitrely sure what happened, but my phone wouldnt boot after flashing SuperSU, even after i restored stock system,boot, and EFS. The boot.img got me booting again though and now rooted. (US variant)
Edit: Can someone upload a stock boot.img for the US variant? I think my backup boot.img might be corrupt, as it causes my phone not to boot.

jon7701 said:
Not enitrely sure what happened, but my phone wouldnt boot after flashing SuperSU, even after i restored stock system,boot, and EFS. The boot.img got me booting again though and now rooted. (US variant)
Edit: Can someone upload a stock boot.img for the US variant? I think my backup boot.img might be corrupt, as it causes my phone not to boot.
Click to expand...
Click to collapse
My phone got frozen at boot, dual sim in the EU version.
I tried to flash the non-systemless SuperSU and that made it factory reset, still not rooted.
I will wait....

hmnk said:
Anyways, coming back to the topic, why can't we use systemless root on our device?
Thanks,
Regards.
Click to expand...
Click to collapse
Anyone??
Thanks

hmnk said:
Anyone??
Thanks
Click to expand...
Click to collapse
I tried to do systemless and it was unable to patch the boot image.
Also if someone could upload a US variant boot.img that would be very appreciated. On the mexican boot.img I cant get data or recieve calls. I can only make outgoing calls for some reason.

[OTA] Marshmallow Build MCG24.251-5-5

Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://www.androidfilehost.com/?fid=745425885120733909
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.

TheSt33v said:
Do not take this if your bootloader is locked and you'd like to unlock it at some point.
Click to expand...
Click to collapse
There, fixed it for you.
Gotta bold the important stuff.

ChazzMatt said:
There, fixed it for you.
Gotta bold the important stuff.
Click to expand...
Click to collapse
You're inhibiting natural selection.

TheSt33v said:
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://mega.nz/#!70Zh1BbS!cC_mZ8xouLVwvMlOZLKW2UyC-JXDS7SdnCjxDoafXbI
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
Click to expand...
Click to collapse
hweew ... new kernel ...
could you upload it?

3Dota said:
hweew ... new kernel ...
could you upload it?
Click to expand...
Click to collapse
TWRP flashable, including kernel, version will be up shortly.

TheSt33v said:
TWRP flashable, including kernel, version will be up shortly.
Click to expand...
Click to collapse
Any modem updates?

koftheworld said:
Any modem updates?
Click to expand...
Click to collapse
Yes. Will also be included in TWRP version.

Yee!

I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk

mustafu said:
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Have you done any modifications at all? Even in the past? For example, if you were rooted and then unrooted, if any files were left over from that process, the update will fail. If you had xposed and removed it, same deal. Even if you replaced your emoji file with an updated one, that will also cause it to fail. Did you modify build.prop? Fail.
The only way to be sure that it will pass is to reflash MCG24.251-5 with fastboot before taking the OTA. Or you could always do it the easy way and flash MCG24.251-5-5 with TWRP: https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795

I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia

I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app

g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Install titanium backup and freeze the app called Motorola Update Services.

Shtiff1 said:
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.

So I'm guessing it's for "security" issues. So I really don't need to take this, because it involves to much crap... Unrooting, cleaning cache, reflashing, having to do the phone over again, etc.... If that is all true, then how can I get rid of the system update?

g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Download "Disable Service" from the play store

TheSt33v said:
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
Click to expand...
Click to collapse
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Sent from my XT1254 using Tapatalk

mustafu said:
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Click to expand...
Click to collapse
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.

trial TWRP or temp TWRP custom recovery
trial TWRP or temp TWRP custom recovery
TheSt33v said:
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
Click to expand...
Click to collapse
Don't know if this would help someone install an update like this, but let me throw this out there. There's a way to boot to TWRP custom recovery and use TWRP without installing TWRP. Think of it as "temporary" TWRP.
Thus, you should still be able to flash stuff, including any TWRP-flashable updates, boot logos (to replace the unlocked bootloader warning, SuperSu, etc -- and when you reboot you still have stock recovery.
Now, I don't know why anyone would want to keep stock recovery when TWRP recovery does so much more... But I just recently helped someone with the same suggestion. He wanted to install SuperSu, get root, but keep stock recovery -- for some reason.
Anyway, think of it as "trial TWRP" or "temp TWRP".
I remembered when I made factory images for my Quark, in a variety of states, I used this temporary TWRP trick. I'd almost forgotten about it!
So, seems like you could flash THIS TWRP-flashable version of this update while temporarily booting to TWRP (but not actually installing it), and it wouldn't matter if everything "checked" out or not.
Of course, if you like it, then you can always install it permanently.
For reference, here's the most recent version of TWRP for our phone. (use the one with the most recent post date. @bhb27 updates it fairly often.)
TWRP FOR QUARK
https://www.androidfilehost.com/?w=files&flid=39562
Here's my complete reply:
______
Rahuld107 said:
@ChazzMatt,
Hi, can i root xt1225 using temporary twrp ( one time method). I don't need twrp/custom recovery. Just want root with stock recovery. I am on stock marshmallow, bootloader is unlocked .
Click to expand...
Click to collapse
TEMPORARY TWRP
OK, here's another suggestion. There is a way to boot to TWRP to install SuperSu but NOT install TWRP. You will not be flashing TWRP over stock recovery. You will STILL have stock recovery when you reboot. Think of it as "temporary" TWRP.
Put the TWRP file in your ADB folder and use this command. Your phone will boot to TWRP, but it will not be permanently installed. You can then flash SuperSu while booted into the TWRP interface and then reboot back to your system.
fastboot boot file-name.img (whatever your file name of TWRP is.)
Whereas, the command to permanently install TWRP is this:
fastboot flash recovery file-name.img (whatever your file name of TWRP is.)
___
Back when I first got this phone -- now over two years ago -- I made a bunch of backups in TWRP and posted the images online in various stages -- pure stock, stock + root, stock + root + TWRP. I made the first two with the "temporary" TWRP. People could flash them and already have root without having TWRP installed.
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
1) TWRP BACKUPS which I made in various stages, such as
stock, unrooted
stock + rooted
stock + rooted + permanent TWRP
Click to expand...
Click to collapse
See? Even just stock + rooted but with no TWRP. I made that backup with a "temporary" TWRP which did not overwrite the stock recovery.
But they were only for 4.4.4 Kitkat, which came with this phone. After we went to Lollipop, I posted some more images, but just pure factory. Still, the "temporary" TWRP trick is useful.

Is it just me or the Gallery app in 6.0.1 scrolls really slow? Btw i didnt do a clean update from LP in case that could be the reason

OnePlus 8 5G (T-mobile) [IN17] OTA and Boot.img for rooting

I was attempting to root my OnePlus 8 5G and it was a pain looking for the boot.img. Thankfully my friend squabbi from MaowDroid, found a OTA in a telegram channel (https://t.me/s/OPUpdatesTracker?q=11.0.1.1.IN55CB) and was able to extract the boot.img. From there the processes was the same as with any other phone with Magisk. I hope this helps out some people and prevents multiple headaches.
OTA Download link: https://android.googleapis.com/packages/ota-api/package/206cbccfa573a63d5ea59727de632f5ceb5a0107.zip
Software used to extract the boot.img: https://github.com/cyxx/extract_android_ota_payload
Boot.img Download: http://www.mediafire.com/file/o2ew9kv9mjafzja/boot.img/file

Micr0byte said:
I was attempting to root my OnePlus 8 5G and it was a pain looking for the boot.img. Thankfully my friend squabbi from MaowDroid, found a OTA in a telegram channel (https://t.me/s/OPUpdatesTracker?q=11.0.1.1.IN55CB) and was able to extract the boot.img. From there the processes was the same as with any other phone with Magisk. I hope this helps out some people and prevents multiple headaches.
OTA Download link: https://android.googleapis.com/packages/ota-api/package/206cbccfa573a63d5ea59727de632f5ceb5a0107.zip
Software used to extract the boot.img: https://github.com/cyxx/extract_android_ota_payload
Boot.img Download: http://www.mediafire.com/file/o2ew9kv9mjafzja/boot.img/file
Click to expand...
Click to collapse
Are you able to receive texts? Also do u have the .img file link for 11.0.1.2.IN55CB. Only the zip file in the telegram group...

Texts work. What img do you need in particular? The boot image is attached and you can download via Media Fire. If you need other imgs you can extract them with the tool provided. (https://github.com/cyxx/extract_android_ota_payload)

Micr0byte said:
Texts work. What img do you need in particular? The boot image is attached and you can download via Media Fire. If you need other imgs you can extract them with the tool provided. (https://github.com/cyxx/extract_android_ota_payload)
Click to expand...
Click to collapse
I need 11.0.1.2.IN55CB boot.img

ink718 said:
I need 11.0.1.2.IN55CB boot.img
Click to expand...
Click to collapse
Boot images for 11.0.1.2:
Stock Boot Image
Magisk Patched Boot Image

great info thanks

Micr0byte said:
Texts work. What img do you need in particular? The boot image is attached and you can download via Media Fire. If you need other imgs you can extract them with the tool provided. (https://github.com/cyxx/extract_android_ota_payload)
Click to expand...
Click to collapse
can you please post stock and patched boot.img for tmobile oneplus 8 5g (11.0.4.6 IN55CB) i am unable to find it anywhere. it would be a big help

aviator.OO7 said:
can you please post stock and patched boot.img for tmobile oneplus 8 5g (11.0.4.6 IN55CB) i am unable to find it anywhere. it would be a big help
Click to expand...
Click to collapse
It is already posted on this thread.

Micr0byte said:
It is already posted on this thread.
Click to expand...
Click to collapse
can you please post the download link again ..i cant find it in this post ...the ones mentioned have different build number ...

aviator.OO7 said:
can you please post stock and patched boot.img for tmobile oneplus 8 5g (11.0.4.6 IN55CB) i am unable to find it anywhere. it would be a big help
Click to expand...
Click to collapse
I am also looking for the payload or boot.img for 11.0.4.6IN55CB and would appreciate help finding either

bouyakasha said:
I am also looking for the payload or boot.img for 11.0.4.6IN55CB and would appreciate help finding either
Click to expand...
Click to collapse
havent been able to find it so far

aviator.OO7 said:
havent been able to find it so far
Click to expand...
Click to collapse
bouyakasha said:
I am also looking for the payload or boot.img for 11.0.4.6IN55CB and would appreciate help finding either
Click to expand...
Click to collapse
If you can't find the boot.img for a specific version, root using THIS method. No pathching boot.img required nice and simple.

FoxyDrew said:
If you can't find the boot.img for a specific version, root using THIS method. No pathching boot.img required nice and simple.
Click to expand...
Click to collapse
thanks man btw do you have any luck converting to global?

aviator.OO7 said:
thanks man btw do you have any luck converting to global?
Click to expand...
Click to collapse
Yes, but not using the guide on XDA. Not sure if that guy had an actual TMO device at all or if his method is just broken but of all the TMO users I've talked to including myself thats not how you succesfully end up on global.
The only way I've ever succesfully ended up on Global OOS11 is as follows.
1.) MSM back to TMO v10.7. No ther MSM version will work as thats the lowest TMO firmware that has a sequential update on global that we have fastboot files for.
2.) After flashing to TMO 10.7 don't take any OTA's. Go right into settings and enable OEM unlocking. Immedietly unlock your bootloader and flash the Global 10.9 ROM through fastboot.
3.) Once booted into the global ROM, take all OTA's (there will be more than one to take so double check)
After that your golden, and you can relock your bootloader if you don't plan on rooting.
Me and another TMO user went through a lot of these MSM flashes and fastboot updates. These are the only versions we could get working that didn't send us into crash dump mode. Feel free to do your own expirimenting.

thanks for the detialed guide bro.. ill stay in touch ..i may need further guidance.once i get my unlock token and unlock my bootloader ...another question ...do you recommend backing up persist or modem? did you face any fingerprint or connectivity issues? ive heard the eu rom supports dual sim and less conmection issues ..

FoxyDrew said:
Yes, but not using the guide on XDA. Not sure if that guy had an actual TMO device at all or if his method is just broken but of all the TMO users I've talked to including myself thats not how you succesfully end up on global.
The only way I've ever succesfully ended up on Global OOS11 is as follows.
1.) MSM back to TMO v10.7. No ther MSM version will work as thats the lowest TMO firmware that has a sequential update on global that we have fastboot files for.
2.) After flashing to TMO 10.7 don't take any OTA's. Go right into settings and enable OEM unlocking. Immedietly unlock your bootloader and flash the Global 10.9 ROM through fastboot.
3.) Once booted into the global ROM, take all OTA's (there will be more than one to take so double check)
After that your golden, and you can relock your bootloader if you don't plan on rooting.
Me and another TMO user went through a lot of these MSM flashes and fastboot updates. These are the only versions we could get working that didn't send us into crash dump mode. Feel free to do your own expirimenting.
Click to expand...
Click to collapse
Thanks for this method. I'm going to try it now.

FoxyDrew said:
1.) MSM back to TMO v10.7.
Click to expand...
Click to collapse
I figured out how to do this - important to choose "Other" on MSM login.

FoxyDrew said:
Yes, but not using the guide on XDA. Not sure if that guy had an actual TMO device at all or if his method is just broken but of all the TMO users I've talked to including myself thats not how you succesfully end up on global.
The only way I've ever succesfully ended up on Global OOS11 is as follows.
1.) MSM back to TMO v10.7. No ther MSM version will work as thats the lowest TMO firmware that has a sequential update on global that we have fastboot files for.
2.) After flashing to TMO 10.7 don't take any OTA's. Go right into settings and enable OEM unlocking. Immedietly unlock your bootloader and flash the Global 10.9 ROM through fastboot.
3.) Once booted into the global ROM, take all OTA's (there will be more than one to take so double check)
After that your golden, and you can relock your bootloader if you don't plan on rooting.
Me and another TMO user went through a lot of these MSM flashes and fastboot updates. These are the only versions we could get working that didn't send us into crash dump mode. Feel free to do your own expirimenting.
Click to expand...
Click to collapse
This worked great for me. Last step is downloading full 11.0.2.2.IN21AA OTA and extracting the boot.img so I can easily root it. From there, this is a great path and guide. Sorta a long process, but it's nice to have the phone clean without TMO bloat.

Micr0byte said:
I was attempting to root my OnePlus 8 5G and it was a pain looking for the boot.img. Thankfully my friend squabbi from MaowDroid, found a OTA in a telegram channel (https://t.me/s/OPUpdatesTracker?q=11.0.1.1.IN55CB) and was able to extract the boot.img. From there the processes was the same as with any other phone with Magisk. I hope this helps out some people and prevents multiple headaches.
OTA Download link: https://android.googleapis.com/packages/ota-api/package/206cbccfa573a63d5ea59727de632f5ceb5a0107.zip
Software used to extract the boot.img: https://github.com/cyxx/extract_android_ota_payload
Boot.img Download: http://www.mediafire.com/file/o2ew9kv9mjafzja/boot.img/file
Click to expand...
Click to collapse
How to Unlock Oneplus 8 tmobile Bootloader without unlock token​

farhansaeeddnp3021 said:
How to Unlock Oneplus 8 tmobile Bootloader without unlock token​
Click to expand...
Click to collapse
No, sorry there is no way to unlock it without a unlock token at the moment

[ROM][STOCK IN2011_11_C.21][FASTBOOT] Easily return method to OOS from custom ROMs or simply reflash OOS

Oneplus 8 Fastboot ROMs
DOWNLOADS:
https://www.androidfilehost.com/?w=files&flid=326825
Mirror:
Current version: IN2011_11_C.21_202205172355
PASSWORD: XDA2021 or XDA2022 (newest files)
​

infected_ said:
Made this little project using the script from @mauronofrio FASTBOOT ROMs to return OP8 to latest OOS, since I was always having issues doing so, and always ended up using the unbrick tool for OP8.
Enjoy! If you have any issues, just let me know using a post.
Regards.
Current FASTBOOT ROM 11.0.5.5 download link:
AFH Server:
OP8 OOS 11.0.5.5 FASTBOOT ROM
OP8 OOS 11.0.5.5 MAGISK PATCHED BOOT.IMG
Click to expand...
Click to collapse
I have a T-Mobile device, which I converted to Global and finally installed a custom ROM. For any updates, I have to follow the same route - go back to T-Mobile, then global and then any other ROM. Can I use this utility to go back directly to Global from custom or would I still need to first flash T-Mobile ROM?

sjgoel said:
I have a T-Mobile device, which I converted to Global and finally installed a custom ROM. For any updates, I have to follow the same route - go back to T-Mobile, then global and then any other ROM. Can I use this utility to go back directly to Global from custom or would I still need to first flash T-Mobile ROM?
Click to expand...
Click to collapse
Technically, this process would be the same as a conversion. Just see if you need to backup any other extra partition, like persist.img or other.
Regards.

thank you so much for this, ive been stuck or soft bricked for the last 4 days and this might just be my out.

Hi, thanks for this! Now I have a question, I have latest OOS with Magisk, but since upgrade to 11 i have System UI crashes and serious lags and freeze, I did 4 factory resets and its still there, I want to reflash all from 0, can I use this?

Thank you very much for the contribution

nikola1970 said:
Hi, thanks for this! Now I have a question, I have latest OOS with Magisk, but since upgrade to 11 i have System UI crashes and serious lags and freeze, I did 4 factory resets and its still there, I want to reflash all from 0, can I use this?
Click to expand...
Click to collapse
try reflashing on both slots.

infected_ said:
try reflashing on both slots.
Click to expand...
Click to collapse
Ok, so first I need to flash slot a, and right after that i am gonna flash b slot? Thanks man

showing my ignorance...where is the flash-all.bat script? Is that somewhere in this thread?

gloster2 said:
showing my ignorance...where is the flash-all.bat script? Is that somewhere in this t
Click to expand...
Click to collapse
There's a self extracting file (*.exe) inside the zip file. Have you run it, and checked the extracted files?

infected_ said:
There's a self extracting file (*.exe) inside the zip file. Have you run it, and checked the extracted files?
Click to expand...
Click to collapse
Thanks -- I didn't notice it was an executable. I think I'm ready to go, but just checking. Here's what I've done so far with my T-Mobile version OnePlus 8:
1. completed process to unlock the bootloader (unlocked phone, got token, applied token)
2. set up fastboot in a directory on my Windows PC
3. ran the self-extraction on OnePlus8Oxygen_15.E.35_OTA_0350_all_2103221815-FASTBOOT
Now I'm going to run flash-all.bat. Before I do that, do I need to back up any files, e.g. modem files? Thanks!

gloster2 said:
Thanks -- I didn't notice it was an executable. I think I'm ready to go, but just checking. Here's what I've done so far with my T-Mobile version OnePlus 8:
1. completed process to unlock the bootloader (unlocked phone, got token, applied token)
2. set up fastboot in a directory on my Windows PC
3. ran the self-extraction on OnePlus8Oxygen_15.E.35_OTA_0350_all_2103221815-FASTBOOT
Now I'm going to run flash-all.bat. Before I do that, do I need to back up any files, e.g. modem files? Thanks!
Click to expand...
Click to collapse
backup persist.img and modem.img just in case, and you should be ok to go.
PS: i'm going to upload the fastboot rom without the self extracting method to be easier for users.

Deleted

@infected_ Considering that I am coming from an unlocked bootloader, will this method re-lock the bootloader and is this carrier-branded compatible?

rodken said:
@infected_ Considering that I am coming from an unlocked bootloader, will this method re-lock the bootloader and is this carrier-branded compatible?
Click to expand...
Click to collapse
No, it won't relock the bootloader

infected_ said:
No, it won't relock the bootloader
Click to expand...
Click to collapse
Safe to use for Verizon OP8 5G UW or is this a method to go Global from a carrier-branded version?

infected_ said:
backup persist.img and modem.img just in case, and you should be ok to go.
PS: i'm going to upload the fastboot rom without the self extracting method to be easier for users.
Click to expand...
Click to collapse
sorry for another simple question; I haven't done system level things with Android in a long time. Where are instructions on how to backup those files? I did a little searching, but haven't found anything that works yet.

gloster2 said:
sorry for another simple question; I haven't done system level things with Android in a long time. Where are instructions on how to backup those files? I did a little searching, but haven't found anything that works yet.
Click to expand...
Click to collapse
There is an app for that.

rodken said:
There is an app for that.
Click to expand...
Click to collapse
Thanks! Now I realize that even though I have an unlocked bootloader, I don't have root access. Now I have to figure out how to get that. Sigh.

And...I see much conflicting information on how to root my bootloader unlocked T-Mobile version OnePlus 8. Any advice/pointers to info on the best/easiest way to root it?