[/SIZE][/SIZE]Start Updated on 7-20-2012
****** Due to heavy download from wordwide users, Dropbox has temporay disabled my Public share because the traffic. ******
I had to created a new PRIVATE share to keep ALL files alive
In-order to download the files you need to have account with DropBox and click here to download
To help keep all links alive, please open new account with Dropbox by click here http://db.tt/AxpJcW9F , you will receive 2.5 GB of FREE cloud storage which can acces anywhere, anytime.
End Updated on 7-20-2012
After spend days reading hundred threads on multiple sites, I have come up with a quick instruction in 1 page on how to unbrick D2G and unlock the band to use on CDMA, GSM network such as Verizon, AT&T and T-Mobile. (Sim must be unlocked by calling Verizon or using third parties unlocked from internet search)
All credit will go to the original posters; I'm just combined all together to create an instruction easy for new users plus all the files download are in one place too.
Copy files from step 5, 6, 7, 9 and 18 to SD card before perform "How to" steps below:
How to un-bricked and band-unlock Droid 2 Global:
1. Flash 608 SBF using RSDLite (VRZ_A956_4.5.608_1FF_01.sbf) (press up arrow on keyboard while power up to enter flash mode)
2. Flash Repack_629 SBF using RSDLite (BL=2 BOOT REC CDTf__Repack_629.sbf)
3. Reboot, wipe data and cache (press x on keyboard while power up then press volume Up+Down at the same time )
4. Enable Unknown Source and Development features in Setting (To Bypass activation, press TopLeft, TopRight, BottomRight, BottomLeft (above Emergency))
5. Root D2G withSuperOneClick v2.3.3
6. InstallOtaRootKeeper, Run Protect-root then temp-unroot
7. Reboot to recovery then install 629 OTA update.zip then reboot(Blur_Version.4.5.608.A956.Verizon.en.US.zip)
8. Open OtaRootKeeper and restore Root
9. InstallDroid 2 Recovery Bootstap.apk then Reboot to Recovery
10. At Clockwork Recovery, run Backup the nan-droid
11. Flash 330 SBF suing RSDLite (VRZ_A956_2.4.33_1FF_01.sbf) --> After flash completed, phone will BRICKED, don’t worry
12. Flash 608 using EzSBF on USB stick (1KDStaz_D2G_4.5.608.iso) --> After flash completed, phone will BRICKED, don’t worry
13. Flash Repack_629 SBF using RSDLite (2_BL=2 BOOT REC CDTf__Repack_629.sbf)
14. Reboot, wipe data and cache
15. Enable Unknown source and Development features in Setting
16. Root D2G with SuperOneClick v2.3.3
17. Install Droid 2 Recovery Bootstap.apk then Reboot to Recovery
18. At Clockwork Recovery, Wipe Cache and install band unlock (TBH_Band_Unlock_v2.0.zip)
19. At Clockwork Recovery, run RESTORE the nan-droid (the one that backup on step 10)
20. Reboot phone then it should be able to us AT&T, T-Mobile and Verizon and enjoy
If you have any questions or problems, please post it here so we can help.
Please post your feedback here after your phone is unlocked.
Also, please select your RATING :good: at the Top Right of this post
Regard,
KEY
It worked!!
I am one of the (un)lucky owners of a non-unlockable D2G. I was able to use it to make calls with a SIM interposer (i-smartsim), but wasn't able to get data working on the 850Mhz band (900Mhz worked fine on EDGE, with another carrier). After following this how-to, now I get full speed 3G (H+) on my "locked" D2G using i-smartsim!
I know that I shouldn't use data with the interposer, that it will probably burn out, but I just feel better knowing that I can use data now if I need to
Hope this helps, and thank you for the post, key5000!
Key5000, thanks for posting this over here. BEH from rootzwiki here, and I was just looking here to see if this topic had been covered here yet.
I also wanted to add a little explanatory note explaining why the different flashing methods need to be used, for those who might wonder why use Rsdlite one time, and EzSbf another.
Rsdlite flashes the radio baseband, and sbf_flash (used by EzSbf) does not flash the radio. So, by flashing 330 with RsdLite, we flash the Froyo band unlock-able radio (actually the complete system, but all we are interested in is the radio). If you try flashing 330 with EzSbf, the radio will not be flashed, Rsdlite must be used.
Now that we have the radio we want, we need to get back to Gingerbread, but if we flash GB with Rsdlite, we will overwrite the radio we need be able to do the band unlock. Since sbf_flash flashes everything except the radio, we are able to use it to get back to a recoverable state (608+629-repack). the 629 repack contains no radio baseband, so it is able to be flashed from Rsdlite.
At this point, if we were to take the OTA update, we would overwrite the radio we are trying to preserve again, so we need to restore a nandroid backup to prevent doing that.
Incidentally, I have a clean nandroid backup of 629, if someone has somewhere to host it. This would effectively eliminate all of the initial rooting steps (1-10) other than the copying of files to the SD card. Let me know, and I can get the file to you.
Hope this is helpful or interesting to someone.
This trully works, I rooted My D2g on 2.3.4
Thank you Key 5000 for the final summary.
I just rooted, unbanded and now am on AT&T on my Droid 2 Global. and this is my very first attempt at the bootloader of android. Everything works now.
Thank s to everyone, starting from someone from china "my wife got milk", shadow, etc.
Let me contribute from my own experince working on my 2.3.4 version od D2g.
I had issues with:
Rooting with item #5, Superone click and the zip files on #10 and #12.
I had to download a program to run the superoneclick on my computer with the phone attached,
I also had to download clockworkmod from google play store, and finally,
for #12, using the usb method, you need to look up the instruction on booting your computer on USB.
Key5000, please double check the zip files, EZsbf and the band unlock. i had to get them elsewhere, they appear to be invalid. the same files though.
Also double check the item #11 zip file. I had to get it from Shadow's post.
Thanks again. You've made my day.
All files has been re-upload again.
Nice job! Convoluted but it has to be to accomplish the right sequence of flashes.
Very clever work.
Thanks for the How-To easy to follow and was able to unbrick one of my two phones.
The other phone already has the Band Unlock and is running on .608 I was wondering to upgrade to .629 do I just follow the same instructions but start at step 13, skip the Band Unlock, and use the nandroid from the recovered bricked phone?
By the way can't thank you enough for the unbrick solution.
Not sure if there is any benefit to updating to 629 if you don't have to, I don't know what the real differences between .608 and .629 really are (I got my phone with 629 already on it). One advantage to doing this that I can think of would be not accidentally taking the OTA update and getting the baseband overwritten at a later date. There are other ways to prevent the OTA update, such as renaming the updater file.
I am thinking, and someone else might be able to correct me if I am wrong, that in order to update from 608 to 629, without updating the baseband, the proper way would be to flash an updated kernel file, much as the method mentioned at
http://forum.xda-developers.com/showthread.php?t=1345071
and then flash the nandroid backup. I am not sure of the differences between the kernels of 608 and 629, but am thinking that they are different, and that it might cause issues to simply flash the Nandroid backup, without also updating the kernel. For some reason, I am thinking I read that one of the reasons that wifi etc don't work during the unbricking step of 629 is that 608 is running with the 629 kernel, and they aren't completely compatible. In your case, you would be running 629 with the 608 kernel, and you would probably be the first one to ever try that combination.
Someone else can likely fill more in, hope this helps.
Hello, thank u 4 the info, I don't even know how to sbf :s... I really want to unlock the bands but when you say it will brick. Don't worry, I actually worry lol, you mean that rsdlite will brick after flashing and rebooting? Then I have to enter in bootloader again? How it is? Am sorry for my ignorance
First off, if you are wanting to unlock the bands, is your phone sim-unlocked? If not, unlocking the bands will not sim-unlock the phone, it just allows an already unlocked phone to work on AT&T or T-Mobile.
Regarding to worry or not to worry, as with anything, there is a potential danger anytime the phone is flashed. The same is true when the phone receives an OTA update from Verizon, it is rare, but there is the potential for mishaps.
In this case, we are deliberately "bricking" the phone temporarily, as it is the only way to get the it rooted and band-unlocked.
After the latest ota update, the .629 update, any attempt to flash the phone to a previous version will "brick" the phone, but since there is a method to recover from the bricking, he says don't worry.
When we flash 330 to the phone, it flashes the software to the phone, but then the bootloader recognizes that it isn't the proper software, so it won't boot past the bootloader. It is necessary to flash 330, as that gives us the unlockable radio. Then, we have to flash .608 using ezsbf (or another method to flash without using rsdlite), to flash back to a recoverable state, without losing the radio. It is still bricked at this point and won't boot past the bootloader, but now recoverable with the repacked .629 sbf. We don't flash the whole 629 sbf, just enough parts of it to enable the phone to work.
After this, the phone is back to a partially usable state, where we can root it, and then restore the backup file, bringing it back to a fully usable state.
Hope this answers your questions.
dabigserver said:
Hello, thank u 4 the info, I don't even know how to sbf :s...
Click to expand...
Click to collapse
It is not difficult. Follow this how-to: http://droid.koumakan.jp/wiki/SBF
hi
I think i followed the instruction to do this. But my phone does not work for sim card and I need some help. My phone acts little weird. Can I start this steps all over from #1? Please help. Thanks
What do you mean by your phone doesn't work for SIM card?
Does your phone have a SIM card slot, and if so, is it SIM unlocked for global use?
If your phone doesn't have a SIM slot, then this isn't for you.
You can start the instructions over from the beginning, but in order for this to help your phone has to be SIM unlocked first. If you get an Enter Unlock Code message when you put a SIM in, then this won't really help you, other than for rooting your phone.
Thank you
I did every steps all over again and my phone works.
a question, these steps be discharged the phone to accept any telephone company?
These steps allow your phone to use AT&T or Tmobile, if your phone is already unlocked to use Foreign SIM cards. If your phone is still SIM locked, it won't unlock it for you.
By default Verizon blocks the use of the phone (even when unlocked) on AT&T and Tmobile, and this bypasses that block.
bhigham said:
These steps allow your phone to use AT&T or Tmobile, if your phone is already unlocked to use Foreign SIM cards. If your phone is still SIM locked, it won't unlock it for you.
By default Verizon blocks the use of the phone (even when unlocked) on AT&T and Tmobile, and this bypasses that block.
Click to expand...
Click to collapse
and is there anyway to unlock it to any company?
Yes, just get an unlock code from Verizon. Or, if you aren't on VZW and willing to bet/feeling adventurous, use those unlock services on the internets.
My D2G always goes into Bootloader whatever i do adn shows
"Bootloader
D0.11"
I flashed it with VRZ_A956_4.5.608_1FF_01.sbf then BL=2 BOOT REC CDT.sbf but again the same problem. Couple of times phone got started but for only some time, after some time when i reboot the phone it goes into bootloader. i need immediate help guys...
One thing more i have another D2G which got bricked after .629 but when unbrick method was discovered it got fixed with no issues. the reason i am sharing this is that it was going into bootloader straightaway when i press power button BUT this new one shows M logo for some time and then goes into bootloader...
plz help me out....
Gasai Yuno said:
Yes, just get an unlock code from Verizon. Or, if you aren't on VZW and willing to bet/feeling adventurous, use those unlock services on the internets.
Click to expand...
Click to collapse
I'm not really in the U.S. so that he could not apply the code, I know a website is legal and recommended that I can get the unlock code paying?
Related
Hello all
I purchased a Droid 2 Gloabal unlocked on eBay, got it today, thankfully everything works (well atleast for now).
Currently it's running 2.2 Froyo.
I was prompted to download the OTA software (GB), and I did. The phone then asked me to reboot, and install it, I hit okay.
The next thing is the update progress bar, all goes well, and then all of the sudden, I get a little exclamation mark on the screen, and it reboots.
Now, for some reason I have CW Recovery Mod alway running at startup, never encountered this before om another phone (non Droid, this is my first 'verizon' droid).
Oh, I live in Canada and use Virgin mobile.
Anyway, I select "reboot phone", and then it goes back into 2.2 Froyo, tells me that "Update failed".
I was looking at different roms, just can't figure out which one is the best for my setup - Canada.
The phone looks like it's rooted, I also have the Droid 2 Bootstrapper on it, however the tool gives me an error no matter what button I press in it.
Can someone point me in the right direction please
I am somewhat of a noob.
Also, does nandroid backup the whole system, kernel and all, if things go belly up, will it always fix my issue?
Thanks!
----------------EDIT----------------
So, I found out that the phone is actually not rooted, so I rooted it, using Z4root.
Now, I am at a loss. The phone that I flashed before was quite straightforward to do, this one is stragne.
As mentioned above, I can't upgrade to 2.3 since the phone is rooted (also, I renamed blurupdater.apk so now I don't get the pesky warning message to update).
What do I do to go to 2.3.x?
Since, from what I read on the forums, you can't go 2.2 -> custom rom 2.3, you have to go 2.2 -> 2.3 official rom -> 2.3 custom rom?
Any ideas?
Gingerbread Full SBF 4.5.608
http://forum.xda-developers.com/showthread.php?goto=newpost&t=1437177
Thanks for that link.
So, I can flash that over my current install of Foryo + root + Clockwork?
Also, what about the unlocked status of the phone?
I have no idea how it is unlocked (perhapps a rom that does not honor provider locks?), is there any way I can tell if the phone has been truly unlocked?
If I go to the menu to enter the unlock code (I forget what menu it is, but you get to it by dialing some number), the "Enter unlock code" still pops up?
What could this mean?
I don't want to brick my phone xD
Thanks again!
vlambrecht said:
Thanks for that link.
So, I can flash that over my current install of Foryo + root + Clockwork?
Also, what about the unlocked status of the phone?
I have no idea how it is unlocked (perhapps a rom that does not honor provider locks?), is there any way I can tell if the phone has been truly unlocked?
If I go to the menu to enter the unlock code (I forget what menu it is, but you get to it by dialing some number), the "Enter unlock code" still pops up?
What could this mean?
I don't want to brick my phone xD
Thanks again!
Click to expand...
Click to collapse
Yes you can flash it with what ever you have or don't have
You will have to reroot after with petes root tools
Once unlocked the phone is always unlocked can't be locked again
Sbfs and roms don't touch that part of phone
Sent from my DROID2 GLOBAL using xda premium
Thanks, and lastly, about Clockwork Recovery, will it need to be reinstalled as well?
Consider reading this: http://droid.koumakan.jp/wiki/SBF
The intro part should probably provide the answer to your question.
vlambrecht said:
Thanks, and lastly, about Clockwork Recovery, will it need to be reinstalled as well?
Click to expand...
Click to collapse
As I'm sure it was covered in the link from the post above mine, I'll just say this to make sure.
Yes, you will need to reroot and then flash CWM.
Hello again all!
Finally got the time to try to SBF the D2G to Gingerbread.
One question still lingers in my mind.
The phone was sold to me as unlocked, and for all intents and purposes, it is. I use my Virgin mobile SIM, and it works.
However, here is my concern. Is there only 1 way to unlock the phone? A code unlock?
Why I am wondering, it's because if you enter "#073887*" the code entry dialog still appears. Is that supposed to happen?
My fear is, that once I SBF from Froyo to GB, my phone will be locked (unless it was really code unlocked).
So, my question is twofold:
a) would entering "#073887*" ALWAYS show the code entry dialog, even if the phone has been unlocked?
b) Is there a way to determine if the phone has been code-unlocked, v.s. some sort of custom/moded rom that does not honour the provider lock?
Thanks!
Yes, the code input dialogue is displayed no matter what state the phone is in in terms of SIM lock.
There is no ROM or software tool that can avoid the SIM lock on a DROID2 GLOBAL device.
If the phone is unlocked, it stays that way. With a locked phone, all you can do to use it on GSM (besides unlocking normally) is use a TurboSIM. If you can use non-VZW/VodafoneNL SIM cards, your phone is unlocked.
You cannot enter unlock codes while on custom firmware; only stock ROM supports unlocking.
Flashing does not reset the SIM lock status. An unlocked phone stays unlocked even after flashing an SBF image.
you should add that to your wiki, good info
Thanks, that's great info!
I will SBF the phone later and let you guys know
Hello.I'm sure this has been posted a 1000 times because I've seen tons of threads on it in my searches...
I've got a Droid 2 A956 that I need to use with At&t.I've already got the SIM unlock code,just need some guidance
unlocking the radio for use with GSM carriers in America.
The phone is running Android version 2.3.4.
I'm confused because the tutorial on Rootwiki talks about bricking the phone but does not explain how.
If someone could please post the most up to date and full tutorial,I would greatly appreciate that.Thanks.
Quoting http://rootzwiki.com/topic/25828-in...-and-band-unlock-droid-2-global-with-629-rom/
1. Flash 608 SBF using RSDLite (VRZ_A956_4.5.608_1FF_01.sbf) (press up arrow on keyboard while power up to enter flash mode)
Click to expand...
Click to collapse
This bricks the phone.
Some other steps also brick it.
PassingThruLife said:
I'm confused because the tutorial on Rootwiki talks about bricking the phone but does not explain how.
Click to expand...
Click to collapse
It just means that some of the steps in the band-unlocking procedure will temporarily brick the phone. If you follow all the steps, in the order listed, you should end up with a rooted, band-unlocked, fully functional phone.
Note: If I were you, I'd apply the SIM unlock code first and make sure it works (can read your AT&T SIM, even though it won't connect to the network) before I put in the time and effort to modify the radio baseband.
jabberwockish said:
It just means that some of the steps in the band-unlocking procedure will temporarily brick the phone. If you follow all the steps, in the order listed, you should end up with a rooted, band-unlocked, fully functional phone.
Note: If I were you, I'd apply the SIM unlock code first and make sure it works (can read your AT&T SIM, even though it won't connect to the network) before I put in the time and effort to modify the radio baseband.
Click to expand...
Click to collapse
how do i do this exactly,no screen pops up when i stick my att sim card in?
I tried the" Enter 74663# [Menu] [Menu] " , nothing happens.
Thanks for the help,much appreciated,.
Try switching the device to GSM mode.
If the Network Unlock PIN dialog doesn't show up, your device might be already unlocked.
Sorry for making another thread so soon, but I've got new issues now. TL;DR, I'm just trying to get my Moto G7 Power to detect my sim card at *all* anymore. I've been told that installing an OTA will make the phone detect the sim card again, but... I can't re-lock my bootloader.
I've spent pretty much all day looking for ways to re-lock it, but not a single one has worked. I always get the same "Still waiting for signed boot.img" message, even when I try fixes that worked for others. At this point, I give up on trying to re-lock. I just rooted using a guide here and connected to WiFi.
The next best thing would be for me to find another way to install OTAs. I've heard Magisk used to be able to hide your bootloader status and let you do that, but can't anymore, so...
1. Is there a way for me to install official android updates manually? If so, how?
2. If there is, *where* do I find the updates?
T-Mobile [PCO29.114-54-2]
XT1955-5
Tsukomasi said:
Sorry for making another thread so soon, but I've got new issues now. TL;DR, I'm just trying to get my Moto G7 Power to detect my sim card at *all* anymore. I've been told that installing an OTA will make the phone detect the sim card again, but... I can't re-lock my bootloader.
I've spent pretty much all day looking for ways to re-lock it, but not a single one has worked. I always get the same "Still waiting for signed boot.img" message, even when I try fixes that worked for others. At this point, I give up on trying to re-lock. I just rooted using a guide here and connected to WiFi.
The next best thing would be for me to find another way to install OTAs. I've heard Magisk used to be able to hide your bootloader status and let you do that, but can't anymore, so...
1. Is there a way for me to install official android updates manually? If so, how?
2. If there is, *where* do I find the updates?
T-Mobile [PCO29.114-54-2]
XT1955-5
Click to expand...
Click to collapse
Retus one u need to flash do u have the bat file? Try flashing the modem non -hlos.bin in fastboot mode
You can install OTAs with unlocked bootloader, but you'll need to unroot your device first
Sorry for being 2 weeks late, but you look like you're in the exact same position I once was. Flashing an official update for my channel, available at https://mirrors.lolinet.com/firmware/moto/ocean/official/ was what solved it for me, for whatever reason. (my SIM also wasn't recognized at all, nor did I have any IMEIs outside of bootloader. Also, the option to enable OEM unlocking never became available to me, despite instantly being available when I solved it)
We're technically able to install OTAs with unlocked bootloaders? But for some reason mine throws up an error at step 3/6 every time, so I'm dependant on Lolinet to install them.
On relocking bootloader, you had to re-flash boot.img, run the command 3 times, re-flash and run the command again or something, I was also going to try that on one of my threads, but since I couldn't enable OEM unlocking.
Hyoretsu said:
Sorry for being 2 weeks late, but you look like you're in the exact same position I once was. Flashing an official update for my channel, available at https://mirrors.lolinet.com/firmware/moto/ocean/official/ was what solved it for me, for whatever reason. (my SIM also wasn't recognized at all, nor did I have any IMEIs outside of bootloader. Also, the option to enable OEM unlocking never became available to me, despite instantly being available when I solved it)
We're technically able to install OTAs with unlocked bootloaders? But for some reason mine throws up an error at step 3/6 every time, so I'm dependant on Lolinet to install them.
On relocking bootloader, you had to re-flash boot.img, run the command 3 times, re-flash and run the command again or something, I was also going to try that on one of my threads, but since I couldn't enable OEM unlocking.
Click to expand...
Click to collapse
Every OTA zip first verifies your entire system by checksums. Is there any modified partition the verifier fails and the update process ends with an error.
WoKoschekk said:
Every OTA zip first verifies your entire system by checksums. Is there any modified partition the verifier fails and the update process ends with an error.
Click to expand...
Click to collapse
Probably my Magisk then, but meh
Prerequisites:
Your G 5G/One 5G has bootloader unlocked
LMSA installed
ADB is up to date
Your phone battery should be at least 60%
Your phone is wiped during bootloader unlock process
It's recommended to run LMSA rescue in order to have build version up to date, and you will get required boot.img for patching. Observe the ROM download process, and when it's close to finishing, go to the folder link on the bottom right, and go to ROM files. It's recommended to copy entire .zip file to download folder, and make sure you get boot.img and copy to the phone (set USB mode to file transfer) Download folder, and set USB mode to charging after it's done
Install Magisk Manager and update to the latest, and patch boot.img.
Change USB to file transfer and get patched_boot.img back to host computer
Open command, and go to ADB folder
Reboot the phone to bootloader
Code:
adb reboot bootloader
Code:
fastboot flash boot
Press spacebar once, and drag and drop patched boot to command window and press enter
Before doing restoration, make sure you do the following
1. Setup Magisk Manager and enable Magisk Hide and Systemless Hosts. You will be prompted to run "environmental setup" and the phone reboots during process. Check CTS and it should pass
2. Wipe Google Play Store
3. Reboot and install AdAway
4. Reboot again
5. Restore your phone
You should be able to install Netflix but you will lose L1
Update: you need these additional steps in Magisk to pass
1. Install latest riru in Magisk
2. Download and install Safetynet fix https://github.com/kdrag0n/safetynet-fix
Your phone will reboot twice
Apparently the us version is not able to be rooted as the bootloader cannot be unlocked . Device not supported for bootloader unlock according to the portal.
Can anyone confirm that this bootloader is locked and cannot be unlocked? Anyone else have the US unlocked version and went to the motorola portal and tried to unlock theirs with the same results?
swes013 said:
Apparently the us version is not able to be rooted as the bootloader cannot be unlocked . Device not supported for bootloader unlock according to the portal.
Click to expand...
Click to collapse
You can not trust the official supported unlock list, it's never been complete.
You can check if the device's CID is eligible for unlocking, and if the OEM unlocking is greyed out you cannot.
If the CID is good and OEM can be toggled, you need to request the unlock code to be sure.
sd_shadow said:
You can not trust the official supported unlock list, it's never been complete.
You can check if the device's CID is eligible for unlocking, and if the OEM unlocking is greyed out you cannot.
If the CID is good and OEM can be toggled, you need to request the unlock code to be sure.
Click to expand...
Click to collapse
Well I have enabled developer settings. In that I have enabled usb debugging as well as oem unlocking. I tried to unlock the bootloader. No joy. I talked to a moto rep who said in a chat it was not available for unlock at this time according to the list. The usual B.S.
swes013 said:
Well I have enabled developer settings. In that I have enabled usb debugging as well as oem unlocking. I tried to unlock the bootloader. No joy. I talked to a moto rep who said in a chat it was not available for unlock at this time according to the list. The usual B.S.
Click to expand...
Click to collapse
Correction Folks I got it. Apparently I had bad format. Sorry.
swes013 said:
Apparently the us version is not able to be rooted as the bootloader cannot be unlocked . Device not supported for bootloader unlock according to the portal.
Click to expand...
Click to collapse
Mine is US unlocked version and rooted
Okay so I have been down the road and back again folks. I now have my Moto one 5g ace fully bootloader unlocked as well as Magisk root installed and my root explorer and titanium backup are being granted Super user permissions. Yes Finally. Now If anyone and I mean anyone needs help or has a issue please message me. i have created a list of fastboot commands in order specific to the Moto one ace 5g that WILL RESTORE THE FACTORY IMAGES IN PROPER ORDER FOR THE ROM. FORGIVE ME i AM STILL NEEDING TO MAKE A FLASH ALL.BAT FOR THIS. HOWEVER, IT WORKS FLAWLESSLY IF DONE INDIVIDUALLY TO RESTORE YOUR ONE ACE 5G BACK TO STOCK. So I am a very happy One ace 5g owner with unlocked bootloader and, Root privilege's. Now awaiting some further development for the Recovery image and some custom Roms from some Developers smarter than Me. Ha Ha Ha. So for now I wait. I will update if i get the Flash all.bat file accomplished.
Thanks to XDA for their years of instruction and direction.
swes013 said:
Okay so I have been down the road and back again folks. I now have my Moto one 5g ace fully bootloader unlocked as well as Magisk root installed and my root explorer and titanium backup are being granted Super user permissions. Yes Finally. Now If anyone and I mean anyone needs help or has a issue please message me. i have created a list of fastboot commands in order specific to the Moto one ace 5g that WILL RESTORE THE FACTORY IMAGES IN PROPER ORDER FOR THE ROM. FORGIVE ME i AM STILL NEEDING TO MAKE A FLASH ALL.BAT FOR THIS. HOWEVER, IT WORKS FLAWLESSLY IF DONE INDIVIDUALLY TO RESTORE YOUR ONE ACE 5G BACK TO STOCK. So I am a very happy One ace 5g owner with unlocked bootloader and, Root privilege's. Now awaiting some further development for the Recovery image and some custom Roms from some Developers smarter than Me. Ha Ha Ha. So for now I wait. I will update if i get the Flash all.bat file accomplished.
Thanks to XDA for their years of instruction and direction.
Click to expand...
Click to collapse
That's why you have original ROM or boot in order to revert.
Should everything get messed up, you can fully restore with LMSA rescue (data will be wiped during process)
mingkee said:
That's why you have original ROM or boot in order to revert.
Should everything get messed up, you can fully restore with LMSA rescue (data will be wiped during process)
Click to expand...
Click to collapse
FYI I DID NOT USE LMSA TO RESTORE I USED FASTBOOT. HENCÈ THE POST THAT SAID IF ANYONE WANTED HELP OR HIT A ROADBLOCK OR SNAGS PER SAY TO MESSAGE ME. THANKS. I COULD NOT USE LMSA AFTER ATTEMPTING THE PROCESS YOU STATED. WHEN I DID YOURS EXACTLY I GOT A BOOT UP WITH A DISABLED TOUCHSCREEN. HERE TO HELP. THANKS AGAIN
swes013 said:
Okay so I have been down the road and back again folks. I now have my Moto one 5g ace fully bootloader unlocked as well as Magisk root installed and my root explorer and titanium backup are being granted Super user permissions. Yes Finally. Now If anyone and I mean anyone needs help or has a issue please message me. i have created a list of fastboot commands in order specific to the Moto one ace 5g that WILL RESTORE THE FACTORY IMAGES IN PROPER ORDER FOR THE ROM. FORGIVE ME i AM STILL NEEDING TO MAKE A FLASH ALL.BAT FOR THIS. HOWEVER, IT WORKS FLAWLESSLY IF DONE INDIVIDUALLY TO RESTORE YOUR ONE ACE 5G BACK TO STOCK. So I am a very happy One ace 5g owner with unlocked bootloader and, Root privilege's. Now awaiting some further development for the Recovery image and some custom Roms from some Developers smarter than Me. Ha Ha Ha. So for now I wait. I will update if i get the Flash all.bat file accomplished.
Thanks to XDA for their years of instruction and direction.
Click to expand...
Click to collapse
Could you please post the CA combo data for your variant?
Went to try out this phone, had no idea would be able to root it, was just looking for a basic phone with a decent display and battery. Thanks for the guide @mingkee! My first device borked on the LMSA update, it broke the wifi on it. Returned for a new phone, unlocked the BL and this one working just fine. Nice and rooted and no more ads.
What's the CA combo data exactly.?
swes013 said:
What's the CA combo data exactly.?
Click to expand...
Click to collapse
Its the carrier aggregation configuration for the different bands supported by the hardware and ths software of the phone. It usually differs by region for the same phone model.
The following site is a good reference point for this information.
https://cacombos.com/
swes013 said:
What's the CA combo data exactly.?
Click to expand...
Click to collapse
Its the carrier aggregation configuration for the different bands supported by the hardware and ths software of the phone. It usually differs by region for the same phone model.
The following site is a good reference point for this information.
https://cacombos.com/
Reporting that bootloader unlock works PERFECTLY on the MetroPCS variant. But don't format the string yourself, use the Moto Data Scrub Tool they have on the unlock page. If you do it yourself it will come up error.
swes013 said:
Okay so I have been down the road and back again folks. I now have my Moto one 5g ace fully bootloader unlocked as well as Magisk root installed and my root explorer and titanium backup are being granted Super user permissions. Yes Finally. Now If anyone and I mean anyone needs help or has a issue please message me. i have created a list of fastboot commands in order specific to the Moto one ace 5g that WILL RESTORE THE FACTORY IMAGES IN PROPER ORDER FOR THE ROM. FORGIVE ME i AM STILL NEEDING TO MAKE A FLASH ALL.BAT FOR THIS. HOWEVER, IT WORKS FLAWLESSLY IF DONE INDIVIDUALLY TO RESTORE YOUR ONE ACE 5G BACK TO STOCK. So I am a very happy One ace 5g owner with unlocked bootloader and, Root privilege's. Now awaiting some further development for the Recovery image and some custom Roms from some Developers smarter than Me. Ha Ha Ha. So for now I wait. I will update if i get the Flash all.bat file accomplished.
Thanks to XDA for their years of instruction and direction.
Click to expand...
Click to collapse
Please Post the Commands for the Restore from Factory image as they are slightly different than the G series prior to 2019. Thanks.
swes013 said:
FYI I DID NOT USE LMSA TO RESTORE I USED FASTBOOT. HENCÈ THE POST THAT SAID IF ANYONE WANTED HELP OR HIT A ROADBLOCK OR SNAGS PER SAY TO MESSAGE ME. THANKS. I COULD NOT USE LMSA AFTER ATTEMPTING THE PROCESS YOU STATED. WHEN I DID YOURS EXACTLY I GOT A BOOT UP WITH A DISABLED TOUCHSCREEN. HERE TO HELP. THANKS AGAIN
Click to expand...
Click to collapse
My touchscreen is indeed fronzen after boot.img flash. Please again, post the commands. It is much appreciated.
Articul8Madness said:
Please Post the Commands for the Restore from Factory image as they are slightly different than the G series prior to 2019. Thanks.
Click to expand...
Click to collapse
The flash commands are included in the flashfile.xml, which should always be referred to because the commands do change from time to time.
I suggest using the online flash file convertor.
Then copy the commands to a text file, save, rename the file extension to .bat
done you have your own flashall.bat
only exception is if your device uses the new fastbootd mode.
sd_shadow said:
The flash commands are included in the flashfile.xml, which should always be referred to because the commands do change from time to time.
I suggest using the online flash file convertor.
Then copy the commands to a text file, save, rename the file extension to .bat
done you have your own flashall.bat
only exception is if your device uses the new fastbootd mode.
Click to expand...
Click to collapse
Well I definitely have an issue since I can't use the touchscreen I can't boot into fastboot right now or reboot the phone manually.
Update for the challenged: Hold the power button with the up volume rocker for forced reboot.
DO NOT LOCK THE BOOTLOADER WHILE ROOTED!
When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader.
Locking the bootloader will not fix most issues. It will allow you to use apps that check for an unlocked bootloader without the need for any additional modification. That is the ONLY benefit.
If you still want to lock your bootloader, make sure you can say yes to each of the following:
1. Have you restored the stock boot.img / vendor_boot.img and the phone functions normally?
Spoiler: Restore Stock Boot
Boot / DTBO Images [Root / Stock] - 5 / Pro / Ultimate (NOT S)
These images are NOT built from source. These are the stock images from the firmware provided by Asus that are extracted with payload dumper and uploaded without modification. 18.0840.2202.231 18.0840.2201.226 18.0840.2112.211...
forum.xda-developers.com
Follow the instructions in the thread above.
Use only the boot and vendor_boot images.
Do NOT flash any images that end with "-magisk.img"
2. Have you made a backup of everything you do not want to lose when wiping the phone?
Spoiler: Make a Backup
The sdcard is part of the internal storage and is cleared by a factory reset
Copy everything you want to keep to a computer or USB-C storage device
Apps and settings can be backed up by enabling the Google Backup option
Open Settings
Select Google
Select Backup
Select Back up now
Wait for the backup to complete
3. Have you flashed raw firmware and made sure the phone and updates function normally?
Spoiler: Flash Raw Firmware
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Follow the instructions in the thread above.
If you perform a wipe, you may skip step 4.
4. Have you performed a factory reset and made sure the phone functions normally?
Spoiler: Factory Reset
Open Settings
Select System
Select Reset options
Select Erase all data (factory reset)
Follow the instructions
Once you have verified all of the above requirements, you are now ready to lock the bootloader.
Spoiler: Lock Bootloader
From the bootloader (volume up + power):
Code:
fastboot oem asus-csc_lk
Reserved for QA information
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
falhumai96 said:
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
Click to expand...
Click to collapse
Based on new information, it does seem possible to repair the issues caused by converting.
That said, this guide is still quite relevant. After all, most of the issues people were having were caused by unlocking the bootloader, converting, rooting, and locking the bootloader. The warning for possibility of not being able to unlock have been removed, but the info about restoring to stock before locking has been left.
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
chairman011 said:
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
Click to expand...
Click to collapse
@chairman011 what variant of the phone it is (e.g. CN or WW or US, ...etc.)? Also, when they returned it to you and you were able to unlock it again, was it on the original firmware (or any version in its lineage (i.e. not a ROM that's not original))?
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
nexusnerdgeek said:
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
Click to expand...
Click to collapse
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
falhumai96 said:
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
Click to expand...
Click to collapse
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
twistedumbrella said:
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
Click to expand...
Click to collapse
So, basically the bootloader unlock for tencent devices will always locked unless asus uodate their unlock app or has their been another way around it yet?
The unlock app should unlock the bootloader at least once. Unlocking it a second time has mixed results.
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
0v3rkill said:
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
Click to expand...
Click to collapse
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Andrologic said:
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Click to expand...
Click to collapse
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
0v3rkill said:
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
Click to expand...
Click to collapse
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Andrologic said:
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi there, I did follow and did the raw setup it did got me through the boot loop. However, its stuck on the system start up updating screen and stays in 0%.
Darn i thought im already dead! i didn't even know how i fixed it hahahaha! but its working now successfully downgraded to android 11 because its the only firmware i found and managed to make it work again combination of alot of research in google and here xda. working 100% imei two of them, finger print and sn are all intact. thanks guys
For these few reasons I have to give up root & lock the boot-loader: 1. Financial apps stop working from time to time causing much grief; 2. I've used root functionality precisely for nothing for a year I've had it; 3. It was getting all too complicated to keep up with it all.
(The original intention for unlocking/rooting was to get some sort of unofficial VoLTE and VoWiFi for the mobile operator of my choice; however, it didn't help. Then a newer firmware implemented VoLTE and VoWiFi! So my impatience, admittedly couldn't be known at that point in time, backfired.)
I've nothing to preserve on the phone, due to having a Moto G 5G backup phone. I only had it working with adb & fastboot in my Linux laptop (up to date Fedora 36). I had no working Windows laptop then. But I do now. However, adb on Windows says the device is "unauthorised" (as expected); fastboot in it doesn't list the device. So I might be limited to my Linux laptop only. The phone was previously working on the last A11 WW firmware fine.
I've tried to follow the steps from the original post of this thread. First one worked with vendor_boot, dtbo & boot images (used only 18.0840.2202.231 versions of them). Second N/A. With third step, flash_raw_and_wipe_data.sh fails by core dumping.
Right now, the phone boots to fastbootd & not further. Any help is much appreciated.
(I think I'm inching towards fully bricking this phone. I'm not there yet, but getting closer . It'd be nice to get it working again without root & with locked boot loader. Any help is much appreciated.)
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
nexusnerdgeek said:
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
Click to expand...
Click to collapse
Confirm that you can send fastboot commands to the device. It's a prerequisite for flashing the original boot img back or doing a RAW flash if boot looped. That's the very first step you need sorted and confirmed. Sounds like you may not be in the right Fastboot mode. The RAW version doesn't matter too much as long as it's in line with your device version, you just need it to get back up and can upgrade normally to other versions.