Related
Hi,
i use a international version of motorola xoom mz601 in india and have updated to android 3.1 and use the latest baseband n_01.83.35p. my stupidity changed the seeting to USA band
after this band changed to USA band 800Mhz? i cannot use any network 2G or 3G and the motorola doesn't show any network operators.
i really want to revert back the settings.now how can i downgrade my baseband and what commands i need to execute also i have tried moving to stock 3.0.1 but no change in baseband.
any apk file that would help me change the band?
thank you.
Please help
Solution: Backup everything in external sd as everything in internal memory will be erased by the proceeds
1)Download and keep the instructions from (be sure to check your exact model no)https://developer.motorola.com/products/software/
2)extract all the zip contents to android sdk folder otherwise download it from Android sdk
3)Fully charge your device
4)Power off your device.
5)While holding the volume down button, press the power button for about 1 second and release the power button. The device will power-up and display AP Fastboot Flash Mode. At this point you can release the volume down button.
6)Attach your device to your computer with a USB cable and install the Motorola Device Drivers.
7)INSTRUCTIONS TO FLASH & RE-LOCK YOUR MOTOROLA XOOM:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock(Remember this will relock your xoom although you can unlock afterwards)
8)Reboot and let it load
9)turn on wifi and get the OTA updates for the second update I got my 3g & 2g signal Back
10)Wish u good Luck
Sorry for Bad Bad Bad English I am uneducated
just found a little tool http://forum.xda-developers.com/showthread.php?t=1052745
called baseband switcher but thats only for motorola defy
am no hardcore developer but someone please help
also i did try to flash that using cwm but error 0 occured
You can also unlock after that and install any Custom rom you prefer
You're a life saver, thanks for this!!! I too did the same thing as you ... *#*#4636#*#* > Tablet Information > Select Radio Band ... "Oh, only USA Band is available?" ... *click* ... "Damn, Data connection is gone... knew I shouldn't have clicked that..."
Your steps to resolve fixed the issue after the baseband update ... Now, I think this all could have been much simpler if we could have just reloaded the Baseband, but I couldn't find any to download.
Root Guide
** Root will void the warranty and disable OTA updates **
boot.img patch method
I don't recommend updating the firmware OTA before rooting. There is a chance you will update your phone to a firmware that hasn't been released yet on the ASUS website. New updates are released OTA first and then about a week or two later they are posted on the ASUS website. If by chance you updated the firmware OTA and the firmware isn't on the ASUS website, you'll have to wait for the firmware to be posted before you can root.
If already rooted and updating firmware skip to 5b
1. Make a folder called ROG Phone to store all files needed
2. Download the following to the ROG Phone folder
-- Unlock Tool, aka Unlock Device App
---- https://dlcdnets.asus.com/pub/ASUS/..._SIGNED_UnlockTool_9.1.0.7_180912_fulldpi.apk
-- Latest Firmware - Under Firmware click on See All Downloads | Look at version number, not dates
---- Match SKU/Region - Example: WW->WW, CN->CN, JP->JP
------ Settings > System > About phone > Software information
-------- https://www.asus.com/us/Phone/ROG-Phone/HelpDesk_BIOS/
-- Minimal ADB and Fastboot - Portable
---- https://devsjournal.com/download-minimal-adb-fastboot-tool.html
-- Payload Dumper
---- Attatched image_extrator.zip script
-- Python
---- https://www.python.org/downloads/
-- Magisk Manager
---- https://github.com/topjohnwu/Magisk/releases
3. Unlock bootloader
-- Connect the phone to the PC via the side port on your phone
-- Select USB File Transfer on the phone; If problems connecting, update drivers on the PC
-- Copy the Unlock Tool to your phone's Downloads folder
-- This voids the warranty and disables OTA updates
-- This will force a factory reset, so backup your data
-- Use File Manager (in ASUS folder) on your phone to run the Unlock Tool from the Downloads folder
-- If asked for Pin select "Use your Google account" in white text (can't see) below the Pin request
---- Pin request YouTube: https://www.youtube.com/watch?v=aPKAEGptfas
4. Enable Developer on the phone
-- Settings > System > About phone > Software information
---- Tap "Build number" 7 times
5. Update phone to latest downloadable firmware
-- 5a
-- Open the ROG Phone folder and enable view file extensions
---- File > Change folder and search options > Click View tab > Uncheck Hide extensions for known file types > Click OK
-- Unzip Minimal ADB and Fastboot - Portable file
-- 5b
-- Copy the firmware to the Minimal ADB and Fastboot folder and rename firmware.zip
-- Turn on USB debugging
---- Settings > System > Developer options
------ Enable "USB debugging"
-- Connect the phone to the PC via the side port on your phone
-- Select USB debugging on your phone.
-- From the Minimal ADB and Fastboot folder run cmd-here.exe
-- From the command prompt (black window) type the following:
adb devices
-- To check the connection
adb reboot recovery
-- Select ADB on phone
adb sideload firmware.zip
-- Check that your phone was updated to the latest firmware
---- Settings > System > About phone > Software information
If by chance adb sideload doesn't work, try copying the firmware to the root directory (folder) on the phone and then reboot to install. Don't change the name of the firmware while using this method and you can't skip updates. So if there are two updates out from your current version, you'll have to install both.
6. Extract the boot.img file from the firmware using Payload Dumper
-- Use the attached image extractor script
---- Requires Python; Look at readme.txt
7. Patch boot.img using Magisk Manager
** Make sure that boot.img is from the same firmware version that is on the phone **
-- Turn off USB debugging
---- Settings > System > Developer options
------ Disable "USB debugging"
-- Connect the phone to the PC via the side port on your phone
-- Select USB File Transfer on the phone
-- Copy Magisk Manager and boot.img to your phone's Downloads folder
-- Use File Manager (in ASUS folder) on your phone to run Magisk Manager from the Downloads folder
---- Magisk Manager requires access to the Internet via wifi or mobile network
-- More Information
---- https://www.google.com/search?q=How...Methods)&ie=utf-8&oe=utf-8&client=firefox-b-1
------ Look at Method 2
-- Copy patched_boot.img from the phone's Downloads folder to the Minimal ADB and Fastboot folder
8. Flash patched_boot.img
** Make sure that patched_boot.img is from the same firmware version that is on the phone **
-- Put phone into fastboot mode
---- While the phone is off, hold down volume up and power buttons
-- Connect the phone to the PC via the side port on your phone
-- From the Minimal ADB and Fastboot folder run cmd-here.exe
-- From the command prompt (black window) type the following:
fastboot devices
-- To check the connection
fastboot flash boot patched_boot.img
fastboot reboot
--------------------------------------------------------------------------------
Some users couldn't get a connection to a PC via a PC's Type-C USB port and had to use a Type-C to Type-A USB cable.
https://www.amazon.com/gp/product/B...00__o00_s00?tag=detailedview-20&ie=UTF8&psc=1
If by chance something went wrong and your phone locks up on boot, this raw WW firmware install will get you back up and going (so far it has worked for everyone). This can also be used to relock the bootloader, but it will not restore OTA updates.
https://drive.google.com/file/d/155ZDnBjHeknppthFtNpGadicSNvBGokP/view?usp=sharing
Download and unzip
Reboot phone into fastboot mode
Run flashall_AFT.cmd
..
Tesla74 said:
Quick Root Guide
1. Unlock bootloader
https://dlcdnets.asus.com/pub/ASUS/..._SIGNED_UnlockTool_9.1.0.7_180912_fulldpi.apk
2. Download unofficial TWRP by shakalaca (Doesn't fully work, but can flash files from USB drive)
Download the TWRP that matches your firmware version and rename twrp.img
https://mega.nz/#F!pst3URCQ!l_N503AsNmytaErhmuiwqg
3. Put phone into fastboot mode (volume down + power button)
Connect to the computer using the side USB port
4. Download Minimal ADB and Fastboot and flash twrp.img
https://devsjournal.com/download-minimal-adb-fastboot-tool.html
fastboot flash boot twrp.img
5. Download Magisk Manager, Magisk, and Magisk Unistaller onto a USB drive
https://github.com/topjohnwu/Magisk/releases
6. Flash Magisk with TWRP and install Magisk Manager to root
I don't have the phone yet, but if anyone wants to add to this guide to make it more accurate, I'll update this post.
Click to expand...
Click to collapse
Before running the fastboot command run: "fastboot devices" without quotations. To make sure the device is recognized and connected.
Nice write up!. By the way there is an update to the system a small one maybe 70+ MB. Minor stability update.
Rashad83 said:
Before running the fastboot command run: "fastboot devices" without quotations. To make sure the device is recognized and connected.
Nice write up!. By the way there is an update to the system a small one maybe 70+ MB. Minor stability update.
Click to expand...
Click to collapse
Thanks, I updated post. I was wondering after the system update, does TWRP still work because of encryption? Or does TWRP need to be updated for every system update?
Does the unlock bootloader tool REALLY erases all everything, or it's just ASUS warning so they cover their end if user data is lost?
Tesla74 said:
Thanks, I updated post. I was wondering after the system update, does TWRP still work because of encryption? Or does TWRP need to be updated for every system update?
Click to expand...
Click to collapse
Once you flash TWRP you will not be able to update through OTA. You will have to download the update manually and then flash it, once you do that i believe it flashes the stock boot.img which removes TWRP. When that happens you will have to flash a compatible TWRP for the new update.
That's how i understand it, personally i haven't rooted yet so i can't be 100% certain.
Also it's recommended by TWRP team to return to stock before updating the system and then flashing TWRP.
---------- Post added at 08:04 AM ---------- Previous post was at 07:49 AM ----------
mbze430 said:
Does the unlock bootloader tool REALLY erases all everything, or it's just ASUS warning so they cover their end if user data is lost?
Click to expand...
Click to collapse
It's not just ASUS, Any Android device once you unlock the bootloader the user data is erased. So better backup!. By the way ASUS has a backup tool for all your apps and data i haven't tried it yet, give it a try.
That is correct. When I had my Pixel 2 XL (or any phone for that matter). When you flash TWRP on to the recovery the OTA update will always fail. You will have to either find the original recovery or the whole rom and reflash it.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
---------- Post added at 08:04 AM ---------- Previous post was at 07:49 AM ----------
[/COLOR]
It's not just ASUS, Any Android device once you unlock the bootloader the user data is erased. So better backup!. By the way ASUS has a backup tool for all your apps and data i haven't tried it yet. so check it out.[/QUOTE]
Dang it! I just setup the phone exactly the way I wanted it too.
Rashad83 said:
Once you flash TWRP you will not be able to update through OTA. You will have to download the update manually and then flash it, once you do that i believe it flashes the stock boot.img which removes TWRP. When that happens you will have to flash a compatible TWRP for the new update.
That's how i understand it, personally i haven't rooted yet so i can't be 100% certain.
Also it's recommended by TWRP team to return to stock before updating the system and then flashing TWRP.
Click to expand...
Click to collapse
Thanks! I hope shakalaca keeps updating TWRP with the new firmwares. Sounds like recovery.img will have to be extracted from the firmware and flashed before updating.
You will not find any file under the name of recovery.img. I tried looking for it in the stock firmware before no such file exists. The only way I think to do it is by flashing all of the boot.img where it resides I think.
Fastboot flash boot boot.img
Rashad83 said:
You will not find any file under the name of recovery.img. I tried looking for it in the stock firmware before no such file exists. The only way I think to do it is by flashing all of the boot.img where it resides I think.
Fastboot flash boot boot.img
Click to expand...
Click to collapse
I wasn't able to find either recovery.img or boot.img in the firmware.
boot.img vs recovery.img always confuses me. I wonder if updating with the update.zip method really needs stock recovery?
Tesla74 said:
I wasn't able to find either recovery.img or boot.img in the firmware.
boot.img vs recovery.img always confuses me. I wonder if updating with the update.zip method really needs stock recovery?
Click to expand...
Click to collapse
You need the payload dumber app on windows to extract the payload file which contains all the .img files which boot.img is one of them.
The boot.img contains the kernel and other important files needed to boot the device, while the recovery contains all the recovery settings responsible for reseting the device and updating, wiping actions.
From the comments i saw about recovering the phone after a bootloop it seems stock recovery isn't needed but i could be wrong. We will need input from others who have done it.
On my previous phone i could go back to stock rom without stock recovery as long it's the same rom build. So you will need to flash the same stock rom you are currently on and then flash the update.
I ran into some trouble. after running bootloader unlocker apk. it is now asking for a PIN. I tried the PIN I used when setting up the fingerprint reader and it doesn't work. It won't let me setup the phone again now.
Also got into the stock Recovery and did a user/data factory reset
Anyone suggestions?
Tesla74 said:
4. Put phone into fastboot mode (volume down + power button)
Connect to the computer using the side USB port
Click to expand...
Click to collapse
By pressing volume down + Power button, the phone goes into recovery mode not fastboot.
It's easiest doing it by adb:
Adb devices
If the phone Is found:
Adb reboot bootloader
That's what I did when I root my Rog
mbze430 said:
I ran into some trouble. after running bootloader unlocker apk. it is now asking for a PIN. I tried the PIN I used when setting up the fingerprint reader and it doesn't work. It won't let me setup the phone again now.
Also got into the stock Recovery and did a user/data factory reset
Anyone suggestions?
Click to expand...
Click to collapse
I was in the same situation, but if you check carefully you will see "use your account Google" it's just below of the pin request.
(It's written in White )
I was in the same situation, but if you check carefully you will see "use your account Google" it's just below of the pin request.
(It's written in White )
Click to expand...
Click to collapse
OMG! You are right! after staring at the screen I can finally see it! THEY NEED TO FIX THAT! I spend the past 2 hours erasing all the partitions! I wanna kill ASUS!
Marco589 said:
By pressing volume down + Power button, the phone goes into recovery mode not fastboot.
It's easiest doing it by adb:
Adb devices
If the phone Is found:
Adb reboot bootloader
That's what I did when I root my Rog
I was in the same situation, but if you check carefully you will see "use your account Google" it's just below of the pin request.
(It's written in White )
Click to expand...
Click to collapse
Thanks! I"ve updated the guide for both issues.
Tesla74 said:
Thanks! I"ve updated the guide for both issues.
Click to expand...
Click to collapse
To go to fastboot mode the hardware method will be by:
1. Holding (Power+Volume Up) until you see "Republic of Gamers" logo then release.
2. If the phone is turned off; hold the volume up only and connect the usb c to the phone(make sure the usb wire is connected to the PC already "It's basically the same as holding the power button except you'r getting the power from the usb"). You will go directly to "fastboot mode/ bootloader mode" i used to do this before on my phones, will also work on the ROG phone.
Rashad83 said:
To go to fastboot mode the hardware method will be by:
1. Holding (Power+Volume Up) until you see "Republic of Gamers" logo then release.
2. If the phone is turned off; hold the volume up only and connect the usb c to the phone(make sure the usb wire is connected to the PC already "It's basically the same as holding the power button except you'r getting the power from the usb"). You will go directly to "fastboot mode/ bootloader mode" i used to do this before on my phones, will also work on the ROG phone.
Click to expand...
Click to collapse
Thanks! I updated the guide and added link to your post.
I loaded TWRP but I can't flash Magisk on it. Can't read the /system partition.
Worse off, I am stuck at the ROG logo even after reboot.
what can I do to get the phone to at least boot back to the OS?
-----Update------
Nevermind I extracted the payload.bin and fastboot flash boot boot.img from there and it booted up again.
mbze430 said:
I loaded TWRP but I can't flash Magisk on it. Can't read the /system partition.
Worse off, I am stuck at the ROG logo even after reboot.
what can I do to get the phone to at least boot back to the OS?
-----Update------
Nevermind I extracted the payload.bin and fastboot flash boot boot.img from there and it booted up again.
Click to expand...
Click to collapse
In order to flash Magisk v17.3, you need to load Magisk and magisk unistaller on a USB drive, then boot into recovery , select USB storage then flash magisk.
Thanks to mbze430 posting the boot.img patch method of rooting, I've updated the guide. This works without the need for TWRP.
Need info on flashing twrp. Are all attempts done on firmware version 23 (where latest shakalaca version of TWRP is supported)? Is there no way to get TWRP working on firmware version 43?
make sure you take a backup becuase this will wipe the device!!!!
1. reboot device to fastboot mode
2. run the flashall.bat file in NMK24B folder. this will downgrade everything to android N.
3. let it do its thing, once finished reboot device.
4. go through setup process then re enable usb debugging and reboot back to fastboot mode.
5. run fastboot command : "fastboot flashing unlock_critical" it should return device already unlocked.
6. place the 2 modem files in where you have adb/fastboot installed.
7. run command: fastboot flash modemst1 modemst1.img
8. run command: fastboot flash modemst2 modemst2.img
9. after both are flashed reboot device back to OS and you should be unlocked now.
10. you can now take the most recent update via ota and still be unlokced.
https://drive.google.com/file/d/1vRTRFMQEgblI3luGy1pEJC_WgW8LQrua/view?usp=drivesdk
Does this work while the phone is on Pie?
Hypnosis4U2NV said:
Does this work while the phone is on Pie?
Click to expand...
Click to collapse
Yes it reverts it to Android 7
Got Sprint locked Essential phone, you saved my day! Was getting "invalid SIM card" message, apparently seller didn't unlock it at Sprint. Your method worked from first time. OTA updated back to Pie, July 2019 patch, relocked bootloader, still carrier unlocked!
alex.vinarskis said:
Got Sprint locked Essential phone, you saved my day! Was getting "invalid SIM card" message, apparently seller didn't unlock it at Sprint. Your method worked from first time. OTA updated back to Pie, July 2019 patch, relocked bootloader, still carrier unlocked!
Click to expand...
Click to collapse
Your welcome!
I did this and now the screen is unresponsive to touch
357MagColt said:
I did this and now the screen is unresponsive to touch
Click to expand...
Click to collapse
While in TWRP screen or the phone boots into Nougat or PIE or Q and then this? We need more info.
HueyT said:
While in TWRP screen or the phone boots into Nougat or PIE or Q and then this? We need more info.
Click to expand...
Click to collapse
I got it to work now when I flash the modem files they don't seem to unlock it still shows invalid sim
357MagColt said:
I got it to work now when I flash the modem files they don't seem to unlock it still shows invalid sim
Click to expand...
Click to collapse
Sometimes it takes 1 day for this to work
Thank you so much for these instructions.... :highfive:
It's been so long since I used adb, it took me 10 minutes to hunt everything down again.
I completed all the steps, a few questions.. (observations really)
It pulled all OTAs and is now Android 10.
The phone does seem to work (data and voice).
It's also displaying my Verizon number.
However under "About Phone", the SIM still displays as Sprint. :silly:
It does not bother me. Just wanted to bring it up in case it turns out to be a broader issue.
alex.vinarskis said:
Got Sprint locked Essential phone, you saved my day! Was getting "invalid SIM card" message, apparently seller didn't unlock it at Sprint. Your method worked from first time. OTA updated back to Pie, July 2019 patch, relocked bootloader, still carrier unlocked!
Click to expand...
Click to collapse
Is this supposed to unlock sprint version ?
eishra said:
Is this supposed to unlock sprint version ?
Click to expand...
Click to collapse
This amazing tool does exactly that. Even a Sprint Locked phone with the Nag screen can be fixed.
---------- Post added at 11:36 PM ---------- Previous post was at 11:31 PM ----------
enigma2446 said:
make sure you take a backup becuase this will wipe the device!!!!
1. reboot device to fastboot mode
2. run the flashall.bat file in NMK24B folder. this will downgrade everything to android N.
3. let it do its thing, once finished reboot device.
4. go through setup process then re enable usb debugging and reboot back to fastboot mode.
5. run fastboot command : "fastboot flashing unlock_critical" it should return device already unlocked.
6. place the 2 modem files in where you have adb/fastboot installed.
7. run command: fastboot flash modemst1 modemst1.img
8. run command: fatsboot flash modemst2 modemst2.img
9. after both are flashed reboot device back to OS and you should be unlocked now.
10. you can now take the most recent update via ota and still be unlokced.
Please correct the spelling in step 8. fastboot is wrong
Click to expand...
Click to collapse
No luck!
Tried 10 thousands times with no luck! still saying network is not available / insert SIM card!
Any help?
Thanks
n2locarz said:
This amazing tool does exactly that. Even a Sprint Locked phone with the Nag screen can be fixed.
---------- Post added at 11:36 PM ---------- Previous post was at 11:31 PM ----------
enigma2446 said:
make sure you take a backup becuase this will wipe the device!!!!
1. reboot device to fastboot mode
2. run the flashall.bat file in NMK24B folder. this will downgrade everything to android N.
3. let it do its thing, once finished reboot device.
4. go through setup process then re enable usb debugging and reboot back to fastboot mode.
5. run fastboot command : "fastboot flashing unlock_critical" it should return device already unlocked.
6. place the 2 modem files in where you have adb/fastboot installed.
7. run command: fastboot flash modemst1 modemst1.img
8. run command: fatsboot flash modemst2 modemst2.img
9. after both are flashed reboot device back to OS and you should be unlocked now.
10. you can now take the most recent update via ota and still be unlokced.
Please correct the spelling in step 8. fastboot is wrong
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Verizon change to AT&T
Hello will this work for a Samsung s9 plus?. I bought it from eBay, which was booting up to the Verizon carrier unlocked but after doing 8 system updates (13-20) it now boot with AT&T and it is now network locked, NO SIM CARD
Need Help Sprint Locked
Does this require device bootloader to be unlocked ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:12 PM ----------
I need help - i am getting "getting FAILED (remote: Flashing is not allowed in Lock State)" when i try to run the flashall.bat
andril said:
Does this require device bootloader to be unlocked ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:12 PM ----------
I need help - i am getting "getting FAILED (remote: Flashing is not allowed in Lock State)" when i try to run the flashall.bat
Click to expand...
Click to collapse
Here is a couple of posts that have outlined the process better:
https://forum.xda-developers.com/showpost.php?p=75994498&postcount=360
https://forum.xda-developers.com/showpost.php?p=75507693&postcount=221
However, I have to caution you: you will be altering critical partitions on your phone and if you don't understand what you are doing and just blindly follow the posts you can make a minor mistake and brick your phone.
If any of those phrases sounds unfamiliar to you then don't try this method or at least ask someone with more experience to help you:
Unlocking bootloader
Flashing factory image via fastboot
Backing up and restoring modemst partitions
my adb says waiting ''for any device''
enigma2446 said:
make sure you take a backup becuase this will wipe the device!!!!
1. reboot device to fastboot mode
2. run the flashall.bat file in NMK24B folder. this will downgrade everything to android N.
3. let it do its thing, once finished reboot device.
4. go through setup process then re enable usb debugging and reboot back to fastboot mode.
5. run fastboot command : "fastboot flashing unlock_critical" it should return device already unlocked.
6. place the 2 modem files in where you have adb/fastboot installed.
7. run command: fastboot flash modemst1 modemst1.img
8. run command: fastboot flash modemst2 modemst2.img
9. after both are flashed reboot device back to OS and you should be unlocked now.
10. you can now take the most recent update via ota and still be unlokced.
https://drive.google.com/file/d/1vRTRFMQEgblI3luGy1pEJC_WgW8LQrua/view?usp=drivesdk
Click to expand...
Click to collapse
Dear, I wanted to thank you for your contribution and I wanted to know if you could help me with your knowledge to do a procedure similar to the PH-1. but to an LG G8 ThinQ
It's been 7 days since I came back to stock already and OEM unlocking is still greyed out. Is there any way to force it true so I can relock bootloader? That happened when I first tried to unlock bootloader, but I could allow it in like 4 days
If you wanna know reasons I tried installing Custom ROMs, and on the one successful installation (AOSP Extended) it's bugged so I returned to stock and kept on trying to install CrDroid, but one day it just stopped recognizing SIMs. (After some time on stock being able to)
・It can't be a number block, since it still works on another Custom ROM+Magisk Phone
・And I'm not sure if an IMEI block would mess with a SIM from another carrier that's never touched a rooted phone. (I tested both SIMs on both slots)
・That same SIM (my original one) stopped working on an unrooted G7 Play too
・Also I can't check any of my 2 IMEIs on settings, though I could retrieve IMEI1 through "fastboot getvar all"
Hyoretsu said:
It's been 7 days since I came back to stock already and OEM unlocking is still greyed out. Is there any way to force it true so I can relock bootloader? That happened when I first tried to unlock bootloader, but I could allow it in like 4 days
If you wanna know reasons I tried installing Custom ROMs, and on the one successful installation (AOSP Extended) it's bugged so I returned to stock and kept on trying to install CrDroid, but one day it just stopped recognizing SIMs. (After some time on stock being able to)
・It can't be a number block, since it still works on another Custom ROM+Magisk Phone
・And I'm not sure if an IMEI block would mess with a SIM from another carrier that's never touched a rooted phone. (I tested both SIMs on both slots)
・That same SIM (my original one) stopped working on an unrooted G7 Play too
・Also I can't check any of my 2 IMEIs on settings, though I could retrieve IMEI1 through "fastboot getvar all"
Click to expand...
Click to collapse
What does getvar all say are the codename and software channel?
Sent from my perry_f using XDA Labs
sd_shadow said:
What does getvar all say are the codename and software channel?
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
I didn't find those specifically, but it's ocean XT1955-1 and RETBR (product/board and sku, and ro.carrier) Tried reflashing NHLOS.bin, erasing modem and flashing FSG today, didn't work and I never ran "fastboot erase all" too (by not working I mean the phone doesn't recognize a SIM is in the tray, I don't even have the emergency calls only message)
Re-flashed stock around 4 times a week ago or so, the only thing I didn't do was relock bootloader since I'm unable to
Here's the full output of getvar all if needed. (that's not the actual IMEI that's output'd) Also between those tries I sometimes could get device ID to show up instead of bad key, no idea why though
Brazil also has a site from ANATEL, the organization that manages product quality, authenticity, restrictions, user things and such, (All devices need to pass through a check from them) that allows us to see if IMEI has any restrictions (It shows if the IMEI is blocked, at least "Informed IMEI is banned by loss or theft" on a video I saw), mine has "Until now, the IMEI has no restrictions on use"
Hyoretsu said:
I didn't find those specifically, but it's ocean XT1955-1 and RETBR (product/board and sku, and ro.carrier) Tried reflashing NHLOS.bin, erasing modem and flashing FSG today, didn't work and I never ran "fastboot erase all" too (by not working I mean the phone doesn't recognize a SIM is in the tray, I don't even have the emergency calls only message)
Re-flashed stock around 4 times a week ago or so, the only thing I didn't do was relock bootloader since I'm unable to
Here's the full output of getvar all if needed. (that's not the actual IMEI that's output'd) Also between those tries I sometimes could get device ID to show up instead of bad key, no idea why though
Brazil also has a site from ANATEL, the organization that manages product quality, authenticity, restrictions, user things and such, (All devices need to pass through a check from them) that allows us to see if IMEI has any restrictions (It shows if the IMEI is blocked, at least "Informed IMEI is banned by loss or theft" on a video I saw), mine has "Until now, the IMEI has no restrictions on use"
Click to expand...
Click to collapse
Did you check the flashfile.xml
For the official flash commands?
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Did you check the flashfile.xml
For the official flash commands?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
https://pastebin.com/X5TD77YS As far as I remember (just downloaded firmware file on phone) they're the same from the eraseandupdate.bat I was using
EDIT: Yeah, aside from it erasing modemst1 and modemst2 after flashing everything as opposed to after flashing FSG and reflashing FSG after that it's the same commands
Hyoretsu said:
OEM unlocking is still greyed out.
Click to expand...
Click to collapse
OEM unlock toggle is greyed out as long as your bootloader is unlocked, Magisk is not installed and you run the stock rom. That's quite normal. You must relock the bootloader to activate it. On my Moto g6 plus you find an info text there that this option is deactivated because the bootloader is already unlocked.
WoKoschekk said:
OEM unlock toggle is greyed out as long as your bootloader is unlocked, Magisk is not installed and you run the stock rom. That's quite normal. You must relock the bootloader to activate it. On my Moto g6 plus you find an info text there that this option is deactivated because the bootloader is already unlocked.
Click to expand...
Click to collapse
Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)
Hyoretsu said:
Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)
Click to expand...
Click to collapse
Usually that error is caused from using the wrong relocking commands
Are you using
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
And mine is greyed out too
Hyoretsu said:
Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)
Click to expand...
Click to collapse
Did you try to install Magisk via TWRP? Maybe older versions will work like v19.3... On my Moto g6 v20.3 leads to a bootloop, too. But v19.3 runs without any problems. Maybe it's worth a try.
I red that it's necessary to run the oem lock command a few times to make it work.
sd_shadow said:
Usually that error is caused from using the wrong relocking commands
Are you using
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
Click to expand...
Click to collapse
I actually thought this was it, but no, I was using this thread, which has the same commands, and still got the error (2x, then 3x, reflash boot.img and oem lock)
WoKoschekk said:
Did you try to install Magisk via TWRP? Maybe older versions will work like v19.3... On my Moto g6 v20.3 leads to a bootloop, too. But v19.3 runs without any problems. Maybe it's worth a try.
Click to expand...
Click to collapse
Installing Magisk on TWRP bootable, since installing TWRP would bootloop too. Didn't try older versions though, but I might try re-writing my IMEI first, who knows if that'll work. Being able to successfully relock bootloader without a working SIM wouldn't do much good, since I'd have to format the phone to try anything afterwards.
Hyoretsu said:
I actually thought this was it, but no, I was using this thread, which has the same commands, and still got the error (2x, then 3x, reflash boot.img and oem lock)
Installing Magisk on TWRP bootable, since installing TWRP would bootloop too. Didn't try older versions though, but I might try re-writing my IMEI first, who knows if that'll work. Being able to successfully relock bootloader without a working SIM wouldn't do much good, since I'd have to format the phone to try anything afterwards.
Click to expand...
Click to collapse
Did you try to install TWRP with the .zip provided by twrp.me? This .zip flashes the ramdisk inside the boot.img as Magisk does. So first you must install TWRP and after that you must install Magisk. Ignoring this order causes a bootloop because the twrp.zip overwrites Magisk! The twrp.zip flashes a complete new ramdisk while Magisk patches only some parts of it.
I loose my IMEI on my Moto g6 plus, too. You won't be able to overwrite it because it is linked with your device and encrypted by Motorola. The location of these files is /persist/rfs.
If your IMEI is broken or corrupt you won't be able to restore it. Except you have a backup of your persist partition.
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
Try to relock your bootloader with the command provided in the screenshot (source: https://source.android.com/setup/build/running)
Screenshot
https://ibb.co/f2LzMzS
WoKoschekk said:
Did you try to install TWRP with the .zip provided by twrp.me? This .zip flashes the ramdisk inside the boot.img as Magisk does. So first you must install TWRP and after that you must install Magisk. Ignoring this order causes a bootloop because the twrp.zip overwrites Magisk! The twrp.zip flashes a complete new ramdisk while Magisk patches only some parts of it.
Click to expand...
Click to collapse
I get a bootloop when I install TWRP alone and when I install Magisk from bootable TWRP, been using the official one from twrp.me this whole time since the screen is bugged on unofficial one. I only ever installed both (in that order) when I was still trying to install Custom ROMs, but I kept getting bootloops for other reasons.
Do t even use twrp. Just install Magisk Manager and then patch a copy of the boot image from the firmware you installed.
So install Magisk Manager
Copy the boot image from the firmware that you installed to your phone.
Run Magisk Manager, click update Magisk and Select patch boot.img
Navigate to the folder on you phone that you copied the boot image to
Wait until Magisk Manager patches it
Copy Patched_boot.img to your adb folder on your PC
From your PC command prompt:
adb reboot bootloader
Then
fastboot devices
If your phone serial # shows, then:
fastboot flash boot patched_boot.img
fastboot reboot
You should now have root and the unlock bootloader option in developer settings will not be greyed out.
There is another thread with these same instructions. That is what allowed me to relock my bootloader.
Sent from my moto g(7) power using Tapatalk
Also,
Now that you are able to relock your bootloader, you could hold off until 10 is out.
If you don't like the unlocked bootloader message on startup, flash the attached logo.img fileView attachment BootLogo_mg7p.zip
Sent from my moto g(7) power using Tapatalk
MrCamby said:
Do t even use twrp. Just install Magisk Manager and then patch a copy of the boot image from the firmware you installed.
So install Magisk Manager
Copy the boot image from the firmware that you installed to your phone.
Run Magisk Manager, click update Magisk and Select patch boot.img
Navigate to the folder on you phone that you copied the boot image to
Wait until Magisk Manager patches it
Copy Patched_boot.img to your adb folder on your PC
From your PC command prompt:
adb reboot bootloader
Then
fastboot devices
If your phone serial # shows, then:
fastboot flash boot patched_boot.img
fastboot reboot
You should now have root and the unlock bootloader option in developer settings will not be greyed out.
There is another thread with these same instructions. That is what allowed me to relock my bootloader.
Sent from my moto g(7) power using Tapatalk
Click to expand...
Click to collapse
Ty, this was the only way in which I could get root in stock. Although the Allow OEM Unlock is still greyed out it now has the same message as before I unlocked the bootloader for the first time, though if it acts the same way it'll be available in a few days. IMEIs and SIMs still aren't working though, but eh. At least I can try testing the locking bootloader theory to get them working again (IMEI not working = can't even see any of them in settings)
MrCamby said:
Also, now that you are able to relock your bootloader, you could hold off until 10 is out.
Click to expand...
Click to collapse
Also Motorola still allows unlocked users to receive OTA for some reason, my device updated and it's still working
To repair your IMEI on a G7 power, this is what worked for me:
Remove your sim card.
Pull NON-HLOS.bin and fsg.mbn from the firmware that was flashed on the phone.
Startup in bootloader mode:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot phone. Once it is back up, powerdown, put sim card back in and start back up.
Sent from my moto g(7) power using Tapatalk
MrCamby said:
To repair your IMEI on a G7 power, this is what worked for me:
Remove your sim card.
Pull NON-HLOS.bin and fsg.mbn from the firmware that was flashed on the phone.
Startup in bootloader mode:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot phone. Once it is back up, powerdown, put sim card back in and start back up.
Click to expand...
Click to collapse
No luck unfortunately, still don't have IMEI/SIM. Once I can I'll try relocking bootloader and maybe sending it to warranty, since apparently using a tool to re-write IMEI won't work on this phone. (Followed to the T, unless unlocking it after flashing and waiting for microSD messes it up)
Did you try the LMSA software to try and fix it. There are two options: update and repair.
Sent from my moto g(7) power using Tapatalk
MrCamby said:
Did you try the LMSA software to try and fix it. There are two options: update and repair.
Click to expand...
Click to collapse
I tried using it back when I was trying to go back to stock "the right way" (to try and solve the lost IMEI, go back stock and re-lock bootloader) but it couldn't even recognize my phone so that I could download anything
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
aktiv8d said:
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Whoareyou said:
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Click to expand...
Click to collapse
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
aktiv8d said:
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
Click to expand...
Click to collapse
They're only sent out by OnePlus when someone needs to restore their phone due to malfunction, not released on any regular basis, but this one has been around for a while.
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
---------- Post added at 03:51 AM ---------- Previous post was at 03:37 AM ----------
mimat1 said:
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
Click to expand...
Click to collapse
UPDATE: I flashed it by starting the MSMDownloader while in EDL mode. Much thanks for this method and fix. My phone thanks you for revival!
Narwhal73 said:
Ok so for future people who run into the same problem and are clueless like me! The RAR file contains the system image and an MSM Tool. Unrar it, open the tool, put your phone in EDL mode, make sure the tool recognizes the device, then click "start".
Cheers!
Click to expand...
Click to collapse
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
---------- Post added at 07:36 PM ---------- Previous post was at 07:22 PM ----------
Narwhal73 said:
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
Click to expand...
Click to collapse
Ok, I was really spooked by the Android 9 ROM saying my device was SIM locked when I bought it unlocked.
On point with answering my own questions: applying the OTA update now shows that my phone is unlocked (as it should be!) under Settings > System updates > UICC unlock.
My phone always reboots to fastboot. I've opened MSM tool and my phone doesn't appear there. It does appear using fastboot devices command on CMD though. How can I flash this? Restart recovery or restart bootloader does nothing, always back to fastboot.