Develop Bugs

[?] Can't flash the HTC EU ROM because of CID

I've searched the forum and Google high and low to solve this and have come up with the following:
1. Running the RUU. Result: "Wrong customer" error.
2. Grabbing rom.zip from RUU temp files, renaming PK76IMG.zip, flashing from bootloader. Result: No dice.
3. Repeat step 2 on a Goldcard. Tried MMC0 and MMC2 (GoldCard generator got errors with MMC1). Result: "CID incorrect! Update Fail!"
4. Flashing zip from command line as follows:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Result: "CID error"
5. Relocking bootloader and repeating #4. Result: same.
6. Change CID as follows: fastboot oem writecid HTC__001. Result: COMMAND ERROR!
7. Downloaded various other fastboot.exe and re-run step 6. Result: COMMAND ERROR!
8. Flashing with fastboot: fastboot flash system system.img. Result: "FAILED (remote: data length is too large)." This one boggles me because the extracted system.img for the HTC UE ROM (what I'm trying to flash) is identical to the HTC Asia ROM (what I have).
9. What's your idea???????
BTW, can I replace the android-info.txt in the HTC EU ROM with the one from the HTC Asia ROM without negative ramifications?

Bump.

So using Goldcard and flash RUU also not working ?
I used to use Goldcard to flash RUU which is not meant for my Desire before.

Thread moved to Q&A.
Sent from my Galaxy Note (i717), using XDA Permium.
•••••••••••••••••••••••••••••••••••••••••••••••••
XDA Rules:
http://forum.xda-developers.com/announcement.php?a=81
Ten post rule:
http://www.xda-developers.com/android/10-post-rule-explained/
Marketplace Rules (updated):
http://forum.xda-developers.com/announcement.php?f=476

ckpv5 said:
So using Goldcard and flash RUU also not working ?
I used to use Goldcard to flash RUU which is not meant for my Desire before.
Click to expand...
Click to collapse
Yes. The same works for Wildfire S. But to change my Wildfire S from Asian to European I ultimately had to flash from fastboot.
I only tried MMC0 so I'm going to try MMC1 and MMC2 next.

I tried MMC1 and MMC2 tonight.
MMC1 didn't work. SimpleGoldCard.exe reported errors and couldn't produce the GoldCard.
MMC2 produced a different CID and successfully generated a GoldCard, but the install failed again: "CID incorrect! Update Fail!"
Any ideas? It can't be impossible to do this!

When we connect our phone as usb drive, with sdcard inserted, there are two removable storage, so patch the sdcard alone with the goldcard won't work as the other is not patched. Anyway this is my guess only.

Delete.

My next approach to changing to CID to the Super CID comes from the AT&T One X forum:
[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev
Thoughts???

CafeKampuchia said:
My next approach to changing to CID to the Super CID comes from the AT&T One X forum:
[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev
Thoughts???
Click to expand...
Click to collapse
Any idea what is mmcblk0p4 referring to ? As we know for one v, our dev/block is numbered differently.

Actually, I don't. I don't think retrieving this block is going to work on the One V, but the method he used will. He found the block containing the CID by searching a dump. I don't (yet) know how to do that.

CafeKampuchia said:
Actually, I don't. I don't think retrieving this block is going to work on the One V, but the method he used will. He found the block containing the CID by searching a dump. I don't (yet) know how to do that.
Click to expand...
Click to collapse
Hi,
I'm trying to figure out how to do the same thing. I can't revert to stock because I have a One V on Three, and the radio is a later version than the RUU online. I found a similar guide to changing the CID on a One S that you did:
http://forum.xda-developers.com/showthread.php?t=1674202
This thread shows how to look at the contents of those blocks:
http://forum.xda-developers.com/showthread.php?t=1694700
And this one gives the purpose of each partition, at least for the primoc, probably same for primou:
http://forum.xda-developers.com/showthread.php?t=2156415
I wrote a BASH script to search through the blocks for a given bit of text, which you can use if you're on Linux by making sure it has execute permission, and running it with the search string (change .txt to .sh if you like). For my CID (H3G__001), I used ./findinblock H3G__001. It is case sensitive. I found my CID in partitions 7, 18, 23, 25 & 26.
Maybe 7 is the one to change. I'm not sure I'm quite ready to just blindly experiment, even if it may be possible to revert. I wonder if someone more experienced can weigh in?

I tried overwriting the CID in mmcblk0p7 but it didn't "take":
Code:
C:\adt-bundle-windows-x86\sdk\platform-tools>adb shell
[email protected]:/ # strings -n 8 /sdcard/mmcblk0p7MOD
strings -n 8 /sdcard/mmcblk0p7MOD
HTC__001
<snip>
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p7
strings -n 8 /dev/block/mmcblk0p7
H3G__001
<snip>
[email protected]:/ # dd if=/sdcard/mmcblk0p7MOD of=/dev/block/mmcblk0p7
dd if=/sdcard/mmcblk0p7MOD of=/dev/block/mmcblk0p7
4096+0 records in
4096+0 records out
2097152 bytes transferred in 0.393 secs (5336264 bytes/sec)
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p7
strings -n 8 /dev/block/mmcblk0p7
H3G__001
<snip>
Perhaps using a goldcard would help. I've only ever done this putting the goldcard directly in the phone. In this case we'd need to use a Y cable to allow a working sdcard in the phone (unless you can store the modded CID partition somewhere else) and I don't have the hardware to hand.
Can anyone else help?

Ok, I tried this with a gold card, sorting this modified block in internal storage instead of SD card. Still no joy.
Sent from my Nexus 7 using XDA Premium HD app

>_<''
Hey everyone
I got the same Problem.
I've found my CID, which is O2___102, on partition 7, 18, 23, 29 and 32.
I made some screenshots of it.
Maybe anyone can help.
P.S.:
Does anyone now the filesize of the mmcblk0p4 partition of the AT&T One X??
Maybe this information can be helpful
- greetings, animeryumyu
EDIT:
I just find out, that the needed partition for modding is the bootloader itself.
At least I read it in the "how to SuperCID" for the HTC One SV (K2_U / K2_UL)
For the One SV it is the same partition as for the AT&T One X.
And before the CID and IMEI of both, the X and the SV is a little text that reads "HTC-BOARD-INFO!".
Maybe this is important to.
Does anyone now any other indicators to find out, which partition is the bootloader??
Maybe, when we get SuperCID, we are one step closer to S-OFF our device

Help a Newbie to rid GPE RUU

Hi folks
I have recently bought a HTC One M8 on ebay which was converted to play edition by the seller using GPE RUU. I know very little about this but would like to attempt to return to stock whilst ensuring no flagged messages are left on.
I have searched and only come across guides that are specific to specific circumstances. Does anyone have or know of a general and safe guide that would work in my case?
Any help greatly appreciated.
Thanks in Advance
Sid

Do you have any idea what version the phone was running before GPe? Can you see the model number at the bottom of the back of the phone?

EddyOS said:
Do you have any idea what version the phone was running before GPe? Can you see the model number at the bottom of the back of the phone?
Click to expand...
Click to collapse
model: OP6B100
No idea what it was running before.

OK, going by that ID we can assume it's an EU unbranded handset. Or we can at least we can treat it as such. So, assuming you want to go back to 100% stock Sense (but keep S-OFF) do the following:
First, download the following to your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip)
htc_fastboot.exe - https://www.androidfilehost.com/?fid=95897840722646249
1.54.401.5 FW ZIP - http://www.androidfilehost.com/?fid=23329332407589439 (rename it firmware.zip)
TWRP - http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.8.4.0-m8.img (rename it to recovery.img)
HTC Sync Manager (for the drivers) - http://www.htc.com/uk/support/software/htc-sync-manager.aspx (install it and then uninstall Sync Manager but leave the drivers)
1. First things first, change the CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader to confirm it's showing the Super CID - fastboot reboot-bootloader
3. Once confirmed it's set, we now need to set the right MID in case this was changed by the seller. To do this, we can use TWRP. Flash TWRP (downloaded earlier) - fastboot flash recovery recovery.img
4. Once flashed, boot into TWRP and connect the phone to your PC
5. Once the drivers are installed, make sure the PC sees the phone by typing adb devices
6. So long as it's been shown as a connected device, type adb shell
7. We can now change the MID to the EU unbranded one by using the following command (copy/paste this as it has to be exact)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
8. Once done, we can now 'lock' the bootloader using the following command (whilst still in adb shell)
Code:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
9. And we can also reset the tamper flag at the same time
Code:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
10. Once all that is done, type exit to leave adb shell and then reboot the phone into the bootloader through the reboot menu in TWRP
11. Once back at the bootloader, you should find the phone is now 'LOCKED' and it shouldn't say 'TAMPERED' at the top either but should still have the black bootloader interface that the GPe has. We can now set it all back to Sense
12. Reboot the phone into RUU mode - fastboot oem rebootRUU
13. Once in RUU mode, flash the firmware ZIP - fastboot flash zip firmware.zip
14. The process will fail the first time and reboot. Run the same command again once it's rebooted - fastboot flash zip firmware.zip
15. Once finished, reboot the phone to the bootloader to confirm you now have the white 'Sense' bootloader - fastboot reboot-bootloader
16. Assuming it's correctly flashed, reboot back into RUU mode - fastboot oem rebootRUU
17. We can now flash the RUU using the htc_fastboot package - htc_fastboot flash zip ruu.zip
18. Once finished, reboot back to the bootloader one last time - fastboot reboot-bootloader
19. Once back in the bootloader, change the CID to HTC__001 - fastboot oem writecid HTC__001
20. Reboot the bootloader to confirm the change has been successful - fastboot reboot-bootloader
21. Once back at the boot loader, disconnect the phone and boot into recovery and do a factory reset
22. Once the reset finishes, reboot the phone
That should get it all working but any issues obviously let us know

Fastboot folder? I did say i was a newbie! thanks

OK, perhaps it might be worth reading up on fastboot/adb before doing anything as the above isn't for the faint-hearted!
EDIT: I've attached my 'fastboot' folder. Extract it to the root of your C: drive so it's easy to get to. All the commands in my guide are done through a command prompt in Windows starting in that folder, e.g. C:\platform-tools\fastboot oem rebootRUU
https://drive.google.com/file/d/0B8L4pkbzdlR3Z3dsNGZfSWhCeTA/view

ok, I have installed fastboot adb andi have a folder called adb in my c:. I am now downloading all the items listed above and renaming as appropriate and moving to the folder named adb. am I on the right track?

Getting there. You could've just downloaded/extracted the folder I linked to on your C: drive but as long as the contents is somewhere you can easily find you should be OK

i have the same problem but mine is in a loop.... my htc m8 is an 0P6B700, ive tried to convert it to a lollipop GOOGL001 but it didnt work... and i am stuck in bootloader.... i have already installed the twrp 2.8... and i have the working the fastboot in my pc... but i dont know what to do....
i want to install a lollipop rom.. but its ok if i need back to stock.
Any help will be appreciated
thanks.

tonytdc1000 said:
i have the same problem but mine is in a loop.... my htc m8 is an 0P6B700, ive tried to convert it to a lollipop GOOGL001 but it didnt work... and i am stuck in bootloader.... i have already installed the twrp 2.8... and i have the working the fastboot in my pc... but i dont know what to do....
i want to install a lollipop rom.. but its ok if i need back to stock.
Any help will be appreciated
thanks.
Click to expand...
Click to collapse
Please start your own thread rather than hijacking someone else's, and also post your output from fastboot getvar all so we can work out what's best to get you back up and running

I know your getting help here, but...Can I ask..
When you bought the One M8 on eBay, did the ad or photos say you were buying an M8 unlocked and Converted from Sense to GPE.
If Not, you do know youve been sold an incorrect product and you have a case against the seller for false advertising, so save yoursewlf the issues, exersize your rights and send it back.
Plus, you say you are new to flashing / unlocking, so if you brick this M8, you dont have any returns room.
Just wanted to say that and hope it helps. Good Luck

EddyOS said:
Please start your own thread rather than hijacking someone else's, and also post your output from fastboot getvar all so we can work out what's best to get you back up and running
Click to expand...
Click to collapse
Ok i will... thanks

EddyOS said:
Getting there. You could've just downloaded/extracted the folder I linked to on your C: drive but as long as the contents is somewhere you can easily find you should be OK
Click to expand...
Click to collapse
Hi Eddy
Thanks for all your support, i have successfuly completed step 1, 2 and 3. Now I need some assistance in flashing TWRP. How do i do this and what do i use?
regards

3 was flashing TWRP so if you've done that you now enter recovery via the bootloader.

[GUIDE] How to manually upgrade firmware

First of all, this guide expects you to have some basic knowledge how to use fastboot, have working ADB/fastboot connection on your computer and understand the fact that this may brick your phone if you mess up.
I am NOT responsible for anything! This will wipe everything on your phone, so get backups if needed.
This guide is written for X720 and supplied files are ONLY for X720. Same procedure will work on X727, but you will have to get right files yourself.
All files are from stock 23S, just extracted, converted and repacked for your convenience.
Read the whole guide before doing anything. If you're unsure about anything, don't do it.
Here we go:
1. Download .zip containing files from Mega: https://mega.nz/#!5boxDYrL!_O-oD05yhiU5FbCmYuf47VH4Qar5RhV5LKwyHa39bWM
2. Extract files to path where you are able to flash them using fastboot (ie. same folder with fastboot)
3. Boot your phone to bootloader (Vol- & Power)
4. Flash everything:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format data <-- THIS WILL WIPE YOUR PHONE INCLUDING INTERNAL STORAGE
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash ddr ddr.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash hyp hyp.mbn
fastboot flash pmic pmic.elf
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash xbl xbl.elf
fastboot flash keymaster keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash bluetooth BTFM.bin
fastboot flash devinfo devinfo.bin​5. Reboot, and let it boot up (takes some time)
6. Flash TWRP, wipe everything and install ROM (you have done this before, won't write a guide)
Credit for this guide goes to @darkobas

get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi

I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.

Presterin said:
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Click to expand...
Click to collapse
thx
i will try again.

Does anyone know which ones are safe to flash over the existing rom? I do not wish to wipe or break current rom.

I flashed everything except system and boot on top of Omni rom. Everything works great.

Does anyone know where I can get all of the files for my x727, I considered using the files from these OTA zips but I think some of the files are missing like the modem firmware and system.img.

On x720 some of the files were divided into scatter files, had to do some research to get them sorted.

Which fastboot is compatible with system.img? Because of me too :"target reported max download size of 536870912 bytes
Invalid sparse file format at header magi". minimal fast boot 1.42
Edit: ok..as long as the post I wrote started installation

Should/Can we install the latest fastboot? Mine is on shop altered 17s from over a year a go, which to be fair runs great; i just fancy a change.
Thanks

write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do

Any solution?
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
Stuck here as well

Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished

Great guide Thanks.
It saved me from a system wipe and a nightly not recognized by TWRP...:crying:

tsongming said:
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Click to expand...
Click to collapse
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.

jackpollard said:
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720

amdol said:
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
Click to expand...
Click to collapse
Thank you! My flaw was looking on https://lineageos.org/ and not on here.

ajegile said:
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
get the same. iam not shure if i have the x722 or x720. they look same

XT1955-5 bootloader unlock install TWRP & Root with Magisk

So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear

Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.

Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
---------- Post added at 08:30 PM ---------- Previous post was at 08:29 PM ----------
toxinburn said:
Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
Click to expand...
Click to collapse
I am gonna check one thing I had it all working another method before but after installing something thru magisk it soft bricked I think it was vanced youtube maybe also cant seem to find a way to get vipre to work sadly.

Question
Does this method bypass the screen lock password on the phone? I have this phone that is locked with a passcode, so I can't easily get it into developer mode. Sorry, I'm a total newbie to this but am trying to learn. Thanks in advance!

A tip for linux users. If you are getting "< waiting for any device >" after the "fastboot oem get_unlock_data". Ctrl-c to exit the command. Su to root and then "fastboot oem get_unlock_data".

I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone

Hyoretsu said:
I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone
Click to expand...
Click to collapse
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?

Linux-Lord said:
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
The thing is, "stopped working" literally, it doesn't have out of service, phone number, no signal, not even the "emergency calls only", heck I can't even find my IMEI in settings nor *#0606#, I think that's what's causing the problem. This SIM also came from that Custom ROM device (originally inserted there, but bought as a standalone data plan)
Linux-Lord said:
and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
If you're talking about how it showed up like that on the G7 Play it used to work just fine in there, and no, that's not the original phone, it's just a phone I used to test if my SIM was still working
Linux-Lord said:
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
Click to expand...
Click to collapse
In this phone, G7 Power, it doesn't even recognize a card is in the tray anymore (unlike the G7 Play which at least knows there's one and G5+Custom ROM, in which it works)
Linux-Lord said:
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?
Click to expand...
Click to collapse
Not that it's gonna help much but OI (Brazil), and if that's on Motorola support page my G7 Power is main phone already.

Is the force encrypt disable necessary? And what does it do?

So, I have successfully rooted my Moto G7 Power by using the method above, but i tried not doing the "format data" and fortunately, I have rooted my phone. For the 1st attempt, I kinda soft-bricked my device by doing the steps briefly, my phone would always bootloop back to recovery mode, but after not doing the "format data" step, it led to a success. So for anyone who are currently experiencing bootloop, flash the stock firmware to your phone and root it again by using the method above but don't do the "format data" step. (flashing the stock firmware would not re-lock the bootloader, so you can try to root your phone again easily.)

error
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
---------- Post added at 08:07 AM ---------- Previous post was at 07:49 AM ----------
gladiatorbong said:
Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.
Click to expand...
Click to collapse
same here

brokenlocked22 said:
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
Click to expand...
Click to collapse
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)

Hyoretsu said:
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)
Click to expand...
Click to collapse
same thing as always.. no matter what lol

brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
If it's same thing as always then you're still using "adb push magisk adb push Magisk-v20.1(20100).zip /tmp/". There's no "but I'm not", if it's indeed the same error as before you're messing up on the syntax. Make sure you've put Magisk inside Minimal ADB folder, rename it to magisk.zip and run "adb push magisk.zip /tmp/"

why is magisk pushed to tmp and not to internal storage . Why not just push magisk to internal sotrage and just install that way through twrp or that wont work. just wondering.

Anyone tried this on XT1955-4?

dirtyscout said:
So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
IM a bit confused should I flash a fresh installed firmware first right after i unlock the boot loader?
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.

[Redacted]

Excellent guide, rooted my Moto G7 from Metro PCS.

brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
I LOVE IT!!! :good:

Question T-Mobile USA Oneplus 9 pro how to turn into Global Oneplus 9 pro

Good day to us all and terribly sorry for posting this question. I have tried to follow all the steps in the T-mobile Oneplus 9 pro change to Global but I'm unsuccessful, I have ADB tool to make this work but I'm not unable to get to the unlock bootloader. I have tried fastboot OEM unlock command and fastboot flashing unlock. Here is what I get when trying both comands:
PS C:\platform-tools> fastboot oem unlock
...
FAILED (remote: Please flash unlock token first.)
finished. total time: 0.008s
PS C:\platform-tools> fastboot devices
57295106 fastboot
PS C:\platform-tools> fastboot oem unlock
...
FAILED (remote: Please flash unlock token first.)
finished. total time: 0.007s
PS C:\platform-tools> fastboot flashing unlock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\platform-tools>
Please, someone, advise what I'm doing wrong?

First, you need to have your phone PERMANENTLY unlocked, you can check this in settings > about phone > click the lock, do a permanent unlock.
Afterwards, you need to enable developer settings, in about phone keep tapping build number until it says dev options enabled, then go to settings > system > developer options > check OEM unlock.
I would suggest you use the MSM here at this point https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/ to convert to EU, it's better than global IMO, but if you want global lemme know.

razercortex said:
First, you need to have your phone PERMANENTLY unlocked, you can check this in settings > about phone > click the lock, do a permanent unlock.
Afterwards, you need to enable developer settings, in about phone keep tapping build number until it says dev options enabled, then go to settings > system > developer options > check OEM unlock.
I would suggest you use the MSM here at this point https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/ to convert to EU, it's better than global IMO, but if you want global lemme know.
Click to expand...
Click to collapse
Would this work to convert to Global as this instructions are for Europe convertion??

The MSM tool provided has EU conversion. You could try using the EU MSM, downloading the global upgrade package and doing a local upgrade to convert to global.

razercortex said:
First, you need to have your phone PERMANENTLY unlocked, you can check this in settings > about phone > click the lock, do a permanent unlock.
Afterwards, you need to enable developer settings, in about phone keep tapping build number until it says dev options enabled, then go to settings > system > developer options > check OEM unlock.
I would suggest you use the MSM here at this point https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/ to convert to EU, it's better than global IMO, but if you want global lemme know.
Click to expand...
Click to collapse
I check the phone as you instructed and yes it says that the device is permanently unlocked and can be used with any carrier.

Ok, I downloaded both files, now what?

baracuda1974 said:
Ok, I downloaded both files, now what?
Click to expand...
Click to collapse
Run the MSMDownloadTool.exe, make sure it says other, continue, make sure phone is connected, press start and it'll convert it.
After you pass setup, download the global zip, move to internal storage and go to upgrade > local upgrade.

razercortex said:
First, you need to have your phone PERMANENTLY unlocked, you can check this in settings > about phone > click the lock, do a permanent unlock.
Afterwards, you need to enable developer settings, in about phone keep tapping build number until it says dev options enabled, then go to settings > system > developer options > check OEM unlock.
I would suggest you use the MSM here at this point https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/ to convert to EU, it's better than global IMO, but if you want global lemme know.
Click to expand...
Click to collapse
Is the permanent sim unlock really necessary? I was able to get the bin to unlock my bootloader which, to my understanding, is said to not be possible without first being sim unlocked.

If you already have the bin, you can just do `fastboot flash cust-unlock unlock-code.bin`, replacing unlock-code.bin with the path to your file.
Then, just run `fastboot flashing unlock` and unlock your phone that way. You will lose your data, so make sure to back it up.

razercortex said:
If you already have the bin, you can just do `fastboot flash cust-unlock unlock-code.bin`, replacing unlock-code.bin with the path to your file.
Then, just run `fastboot flashing unlock` and unlock your phone that way. You will lose your data, so make sure to back it up.
Click to expand...
Click to collapse
Yeah, I did that. I would like to convert to global or EU if it's better, but I want to make backups of my modem/persist and haven't really found an answer on how to do that.
EDIT: Found out that I need to root first, but my phone recently updated to version 12 and there's no official build release to pull a boot image from. Is there another way to get the boot image?

You don't need to root. Open up any MSM, press F8, select modem_a and modem_b, enter password "oneplus" and put your phone in EDL mode, then press the read back button.

Use the T-Mobile MSM to return to Android 11

razercortex said:
Use the T-Mobile MSM to return to Android 11
Click to expand...
Click to collapse
Hello, my T-mobile 9 pro just updated to android 12 and its messing with my work. I cannot get it to connect with my work network now so I'm trying to downgrade back to 11. Would you mind clarifying a bit, I've done a bit of searching but every downgrade tutorial is for a global 9 pro. Am I able to use any MSM tool to rollback to 11?

mahnameisjaime1 said:
Hello, my T-mobile 9 pro just updated to android 12 and its messing with my work. I cannot get it to connect with my work network now so I'm trying to downgrade back to 11. Would you mind clarifying a bit, I've done a bit of searching but every downgrade tutorial is for a global 9 pro. Am I able to use any MSM tool to rollback to 11?
Click to expand...
Click to collapse
Here's your MSM https://www.androidfilehost.com/?fid=2188818919693804752
And here are all of the MSMs
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com

razercortex said:
Here's your MSM https://www.androidfilehost.com/?fid=2188818919693804752
And here are all of the MSMs
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, I appreciate it! For future reference, is there a thread or how could I find this myself?

I literally just posted the thread lol

razercortex said:
I literally just posted the thread lol
Click to expand...
Click to collapse
ah yes I see that now lol, thought it was a link to the android file host site lmao thanks again!