Related
Hello,
I'm quite noob [totally newbie] in android installation and all, but I have been experiencing some problem on my atrix :
- after each reboot, all that have been erased reappeared, and all that have been installed/created disappeared... like a reset at a given date, or if nothing was really persisted in memory..
=> I tried a factory reset (via menu or hard reset) : after reboot, everything is like before
=> I tried to root the phone (found tuto with 4 differents tools) ; the tools don't fail, but after reboot, rootcheck tells me 'im not rooted
So last thing to do : change rom. I've found that link
http://forum.xda-developers.com/showthread.php?t=1336232
It seems fit my needs, just wondering :
- as the tuto talks about cyanogen 7, can follow the steps and install a 7.2 instead ?
- the cyanogemod 7.2 seems to be the latest very stable rom for atrix, no ?
- the atrix 4G is called olympus on cyanognemod site right ? i'm always wondering if I pick the good stuff
- for all that tuto i won't need any root permissions ? cause as I explained above, i can't manage to get them :/
- last question, do you think I have good weapons to initiate fire ?
Thanx a lot,
any advice/help is welcome,
quentasil said:
Hello,
I'm quite noob [totally newbie] in android installation and all, but I have been experiencing some problem on my atrix :
- after each reboot, all that have been erased reappeared, and all that have been installed/created disappeared... like a reset at a given date, or if nothing was really persisted in memory..
=> I tried a factory reset (via menu or hard reset) : after reboot, everything is like before
=> I tried to root the phone (found tuto with 4 differents tools) ; the tools don't fail, but after reboot, rootcheck tells me 'im not rooted
So last thing to do : change rom. I've found that link
http://forum.xda-developers.com/showthread.php?t=1336232
It seems fit my needs, just wondering :
- as the tuto talks about cyanogen 7, can follow the steps and install a 7.2 instead ?
- the cyanogemod 7.2 seems to be the latest very stable rom for atrix, no ?
- the atrix 4G is called olympus on cyanognemod site right ? i'm always wondering if I pick the good stuff
- for all that tuto i won't need any root permissions ? cause as I explained above, i can't manage to get them :/
- last question, do you think I have good weapons to initiate fire ?
Thanx a lot,
any advice/help is welcome,
Click to expand...
Click to collapse
yeah CM 7.2 is the stablest build the Artix got (Yes the codename for the Atrix is olympus) download the file at the bottom of this http://download.cyanogenmod.org/?device=olympus and flash it normally in your custom recovery without wiping the data.
Trozzul said:
yeah CM 7.2 is the stablest build the Artix got (Yes the codename for the Atrix is olympus) download the file at the bottom of this http://download.cyanogenmod.org/?device=olympus and flash it normally in your custom recovery without wiping the data.
Click to expand...
Click to collapse
Thanx Let's try, i'll give here my feedback ... well if i'm in trouble, i'll come here to scream and cry
Okay, so I'm back, and I need help :/
I well execute the steps until RSD Lite : i've seen the work on progress, the status was PASS (I assume it's good, even if my english sometimes sucks )
So i've done the next step : at the "starting fastboot protocol support" state, i tried to run the command moto-fastboot.exe oem unlock, and got the message
INFOOEM unlock is not implemented
Click to expand...
Click to collapse
So i googled the problem, and found the topic
http://forum.xda-developers.com/showthread.php?t=1185939&page=2
Click to expand...
Click to collapse
BUT the problem, the solution seems to be exactly what i previously did, i.e use http://diamantephoto.com/IHOP_Bell.rar with RSD Lite ...
So I tried a second time, just to check, but still same... Tell me PASS, but next step remains "INFOOEM unlock is not implemented" ...
I don't know what I am missing ?
quentasil said:
Okay, so I'm back, and I need help :/
I well execute the steps until RSD Lite : i've seen the work on progress, the status was PASS (I assume it's good, even if my english sometimes sucks )
So i've done the next step : at the "starting fastboot protocol support" state, i tried to run the command moto-fastboot.exe oem unlock, and got the
message "INFOOEM unlock is not implemented"
So i googled the problem, and found the topic
BUT the problem, the solution seems to be exactly what i previously did, i.e use http://diamantephoto.com/IHOP_Bell.rar with RSD Lite ...
So I tried a second time, just to check, but still same... Tell me PASS, but next step remains "INFOOEM unlock is not implemented" ...
I don't know what I am missing ?
Click to expand...
Click to collapse
i wanna say the bootloaders still locked, you should only have to open up ADB and type (be sure to go into fasboot mode first)" fastboot oem unlock " if your problem still persists, what guide are you using? i would recommend cyanogenmods if you want to flash their rom http://wiki.cyanogenmod.org/w/Install_CM_for_olympus
Is it because it's a tutorial for a locked phone AT&T, whereas mine isn't locked ?
quentasil said:
Is it because it's a tutorial for a locked phone AT&T, whereas mine isn't locked ?
Click to expand...
Click to collapse
carrier locked? or the bootloader
Trozzul said:
carrier locked? or the bootloader
Click to expand...
Click to collapse
carrier locked ... cause I guess you are right, the RSD Lite step I did doesn't seem to unlock my bootloader
Maybe it's the same cause why I didn't manage to root the mobile, as I explained in first posrt :/
I'm gonna try your link, but the one I had seemed very well
HTML:
http://forum.xda-developers.com/showthread.php?t=1336232
quentasil said:
carrier locked ... cause I guess you are right, the RSD Lite step I did doesn't seem to unlock my bootloader
Maybe it's the same cause why I didn't manage to root the mobile, as I explained in first posrt :/
I'm gonna try your link, but the one I had seemed very well
HTML:
http://forum.xda-developers.com/showthread.php?t=1336232
Click to expand...
Click to collapse
yup cant Root your devices with a locked bootloader carrier lock does not matter towards all this nerd entities
Trozzul said:
yup cant Root your devices with a locked bootloader carrier lock does not matter towards all this nerd entities
Click to expand...
Click to collapse
yes, but that is weird cause I'm NOT locked carrier ... So i should have been able to root without problem :/
quentasil said:
yes, but that is weird cause I'm NOT locked carrier ... So i should have been able to root without problem :/
Click to expand...
Click to collapse
well if you unlocked the boot-loader before you wouldn't have had a problem.
Ok i begin to understand a little Well, i'm slow, but it's late
So the tuto I had was for locked carrier so I guess this is why they expected to get a number when calling moto-fastboot.exe oem unlock...
Since mine is not, INFOOEM unlock is not implemented is the expected result Means my bootloader is unlocked, i'm right ?
The link you gave me is more clear to me
So i tried the next step, to flashClockworkMod Recovery
fastboot flash recovery your_recovery_image.img
Click to expand...
Click to collapse
but i have a beautiful
Failed to process command flash:recovery error (0x180002)
Click to expand...
Click to collapse
Googled a little, tried to change the name and path of the recovery, but didn't work :/
Ok, i just get a little confused now ...
On the tutorial of cyanogenmod, they say
On the computer, open terminal and run the following command:
fastboot oem unlock
If a message appears claiming that "INFOOEM lock is not implemented", you are done.
Click to expand...
Click to collapse
So I assumed that my bootloader was unlocked
But when i search on google the error Failed to process command flash:recovery error (0x180002), i often find that it means that the bootloader isn't unlocked ...
More crazy, sometimes I read that on Motorola Atrix 4G soemtimes bootloader isn't unlockable, and the solution is to flash a sbf with RSD Lite .... What I also did when i followed the first tutorial http://forum.xda-developers.com/showthread.php?t=1336232
So now, i'm totally confused
quentasil said:
Ok, i just get a little confused now ...
On the tutorial of cyanogenmod, they say
So I assumed that my bootloader was unlocked
But when i search on google the error Failed to process command flash:recovery error (0x180002), i often find that it means that the bootloader isn't unlocked ...
More crazy, sometimes I read that on Motorola Atrix 4G soemtimes bootloader isn't unlockable, and the solution is to flash a sbf with RSD Lite .... What I also did when i followed the first tutorial http://forum.xda-developers.com/showthread.php?t=1336232
So now, i'm totally confused
Click to expand...
Click to collapse
the bootloader should be unlockable as for the "[GUIDE] A detailed step-by-step "Dummies Guide" to installing CM7 on your ATRIX" its from 2011 so its a little old, i would stay with the cyanogenmod guide. about all of the time they are very clear with their guides.
if you get INFOOEM lock is not implemented that should mean your bootloader is unlocked,
INFOOEM unlock is not implemented would be a locked bootloader.
Trozzul said:
the bootloader should be unlockable as for the "[GUIDE] A detailed step-by-step "Dummies Guide" to installing CM7 on your ATRIX" its from 2011 so its a little old, i would stay with the cyanogenmod guide. about all of the time they are very clear with their guides.
if you get INFOOEM lock is not implemented that should mean your bootloader is unlocked,
INFOOEM unlock is not implemented would be a locked bootloader.
Click to expand...
Click to collapse
oh yes of course, makes so much sense now but i didn't notice INFOOEM lock/unlock variant
so I have INFOOEM unlock, so my bootloader is still locked, so the message I get when trying to flash the recovery is logical.
Thanx for making it obvious
Now I need to find why my bootloader is still locked, since I used RSD Lite with a sbf, which told me "PASS" after procedure :/
quentasil said:
oh yes of course, makes so much sense now but i didn't notice INFOOEM lock/unlock variant
so I have INFOOEM unlock, so my bootloader is still locked, so the message I get when trying to flash the recovery is logical.
Thanx for making it obvious
Now I need to find why my bootloader is still locked, since I used RSD Lite with a sbf, which told me "PASS" after procedure :/
Click to expand...
Click to collapse
Ok, seems RSDlite doesn't achieve to install new unlockable bootloader ... The process is very quick compare to a tuto i've seen, and at the end i have always the INFOOEM unlock ....
Is there any way to check the bootloader version once boot up ? But I suspect that, as the factory reset didn't work, the same thing happen when I try to put a new boatloader....
quentasil said:
Ok, seems RSDlite doesn't achieve to install new unlockable bootloader ... The process is very quick compare to a tuto i've seen, and at the end i have always the INFOOEM unlock ....
Is there any way to check the bootloader version once boot up ? But I suspect that, as the factory reset didn't work, the same thing happen when I try to put a new boatloader....
Click to expand...
Click to collapse
theres a mode like Hboot for htc devices on motorola phones, i dont know how to get into it though, mess witth the combinations.
---------- Post added at 01:57 PM ---------- Previous post was at 01:45 PM ----------
if we run out of ideas you can try this method i found http://www.atrixforums.com/forum/mo...ocking-bootloader-installing-custom-roms.html
Trozzul said:
theres a mode like Hboot for htc devices on motorola phones, i dont know how to get into it though, mess witth the combinations.
---------- Post added at 01:57 PM ---------- Previous post was at 01:45 PM ----------
if we run out of ideas you can try this method i found http://www.atrixforums.com/forum/mo...ocking-bootloader-installing-custom-roms.html
Click to expand...
Click to collapse
Ok, i'll check this tomorrow ... but at first look the flash of sbf seems the same, except maybe for the sbf file itself...
For an easy way to unlock & root your X2 here are the steps you need to take. This has been requested by a number of you so here it goes:
1) Unlock your bootloader. There are three steps you can take. The first two are free. The third method requires you to pay a few dollars but it works and is the fastest way. I would highly recommended this method. This is confirmed working on all models.
Option 1: Send an email to [email protected] Email them the following. They usually email you back and tell you to do option 2 or never email you back:
Hello. I keep getting an error when trying to unlock my phone on the unlock page.
Model: GEM-703L (Or whatever model you have)
Serial: Put in your phones serial number here. (You get this in About phone, Status)
IMEI: Put in your phones IMEI number here. (You get this in About phone, Status, it's IMEI1)
Product ID: (Go into your phone dialer and dial *#*#1357946#*#* and it will give you your Product ID)
Thank you for your help
(Your name here)
Option 2: Make a Huawei ID on your phone and stay signed in for 14 days and then go online to unlock your bootloader and it should work on the website.
Option 3: If you want to unlock your phone immediately and don't mind paying a few dollars this is the best and easiest way. Thanks to kpcheang2 for the original information. Visit here:
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
- Download the DC Unlocker Software
- On their site buy 4 credits. https://www.dc-unlocker.com/buy I used PayPal. It cost me around $4.38 USD.
- Follow the instructions in their tutorial. Make sure you put the phone in Manufacture Mode. Choose "Read Bootloader Code" in DC-Unlocker to get your bootloader code.
- Put your phone in bootloader mode (plug into the computer and hold in power and volume down with the phone off) and do a fastboot oem unlock xxxxxxxxxxxxxxxx where x is your bootloader unlock code the DC Unlocker program gave you.
2) Download TWRP recovery from here if you're already on Android 5.1.1
https://www.androidfilehost.com/?fid=529152257862716585
2b) Download this TWRP if you're on Android 5.0 (Now in English!)
https://www.androidfilehost.com/?fid=457095661767151055
Put your phone into Bootloader Mode and fastboot flash the TWRP recovery file you downloaded. (extract the img file from the rar file first) I'm not gonna go over how to use Fastboot here as there are many guides on many different websites on how to use it. Then do a fastboot reboot. When your phone reboots shut it back down and then hold in volume up and power until it turns on and keep holding in volume up until the phone boots into TWRP recovery.
3) Root your phone.
In TWRP flash SuperSU:
After flashing, reboot your phone and you will be rooted. If you want to manually upgrade to a specific Huawei build or flash back to stock, flash one of my modded Kangvip ROMS or visit bark1234's or eenapps thread for the downloads and instructions. Thanks to bark1234 and eennap for their threads and downloads.
Still nothing
So I've been trying to root since I was able to unlock my bootloader, which I was able to do from the website method.
I could not get adb to work with the other method listed on here.
Now with fastboot, my device is identified per the fastboot devices
I am able to run command fastboot flash recovery twrp_cn.img and it looks successful
so I restart and shut down
hold vol up and power and it vibrates and restarts and vibrates and restarts.....
I go back and flash the default recovey and am able to access this with the vol up and power, but cannot get to the twrp recovery. I have tried flashing a couple of versions and no custom recovery can I boot to.
Any help would be appreciated.
t69broken said:
So I've been trying to root since I was able to unlock my bootloader, which I was able to do from the website method.
I could not get adb to work with the other method listed on here.
Now with fastboot, my device is identified per the fastboot devices
I am able to run command fastboot flash recovery twrp_cn.img and it looks successful
so I restart and shut down
hold vol up and power and it vibrates and restarts and vibrates and restarts.....
I go back and flash the default recovey and am able to access this with the vol up and power, but cannot get to the twrp recovery. I have tried flashing a couple of versions and no custom recovery can I boot to.
Any help would be appreciated.
Click to expand...
Click to collapse
What model are you using? Also, what are you on, B106? When you boot into TWRP, I'm sure you already know this but make sure there is no cable plugged into the phone. Mine vibrates once after installing TWRP but I remain holding in volume up and it boots into TWRP the second time.
ajsmsg78 said:
What model are you using? Also, what are you on, B106? When you boot into TWRP, I'm sure you already know this but make sure there is no cable plugged into the phone.
Click to expand...
Click to collapse
I ended up flashing another version of twrp, with your theme for language and ended up working. Thank you for your help!!
t69broken said:
I ended up flashing another version of twrp, with your theme for language and ended up working. Thank you for your help!!
Click to expand...
Click to collapse
If you want, send me a link to that version of TWRP and I'll add it to the OP.
I wrote to [email protected] several times but they did not reply.
I do not understand why.
vuhongduong said:
I wrote to [email protected] several times but they did not reply.
I do not understand why.
Click to expand...
Click to collapse
Do you have the 703L?
ajsmsg78 said:
Do you have the 703L?
Click to expand...
Click to collapse
Yes, 703L.
vuhongduong said:
Yes, 703L.
Click to expand...
Click to collapse
I don't know why they aren't responding to you. I'm starting to worry that when my new X2 comes (I ordered a second one) they won't respond to me either. I'm sure there will be a workaround.
I've been e-mailing them for almost two months and I haven't received one reply from them. I have the 703L and I've tried their website over and over with Google Translate's help. I always get the same error about the log books not being older than 14 days. I just can't get anywhere with Huawei and it's super frustrating that they don't support the U.S. that well.
What I did
Just signed up for the huawei cloud service. And after 14 days I was able to get the unlock code. Worked first time after trying the email way and waiting.
t69broken said:
Just signed up for the huawei cloud service. And after 14 days I was able to get the unlock code. Worked first time after trying the email way and waiting.
Click to expand...
Click to collapse
How were you able to sign in to the cloud service, every time I try I get that the Network is not available.
I went to this page with chrome http://www.emui.com/plugin.php?id=unlock&mod=detail and let it translate for me. It took mrme to a login page and I bit the bullet and signed up. 14 days later I got my unlock code from the same page.
Can anyone confirm that dual sim works after using this root method. When i use boot.img root method, dual sim stops working.
Thanks in advance guys.
bark1234 said:
Can anyone confirm that dual sim works after using this root method. When i use boot.img root method, dual sim stops working.
Thanks in advance guys.
Click to expand...
Click to collapse
I'm not rooted on the new X2 yet. I'm waiting for my unlock code. If I were rooted I'd let you know.
Updated the OP with a link to unlock your bootloader. It worked for me.
ajsmsg78 said:
Updated the OP with a link to unlock your bootloader. It worked for me.
Click to expand...
Click to collapse
Thanks very much.
I can use new OP to succesfully unlock my phone.
Does anyone know if these instructions would work on the Mediapad M2? They both use the same SoC and the display resolution is the same, though the M2 is 8" and the X2 is 7". The M2 ships with Lollipop 5.1 instead of 5.0, but I don't know if that makes any difference here.
WereCatf said:
Does anyone know if these instructions would work on the Mediapad M2? They both use the same SoC and the display resolution is the same, though the M2 is 8" and the X2 is 7". The M2 ships with Lollipop 5.1 instead of 5.0, but I don't know if that makes any difference here.
Click to expand...
Click to collapse
DC Unlocker should work to unlock your bootloader but I'm not sure about everything else. I would imagine if you could find a build of TWRP for the M2 you can use the root method in the OP and it should work.
ajsmsg78 said:
DC Unlocker should work to unlock your bootloader but I'm not sure about everything else. I would imagine if you could find a build of TWRP for the M2 you can use the root method in the OP and it should work.
Click to expand...
Click to collapse
I have been trying to look, but I have yet to find TWRP for M2. I guess it's just too new yet and/or not popular enough to have garnered much support from the community. Thanks anyways, I'll just proceed with unlocking the bootloader for now.
Introduction
This is the bootloader unlock from ZTE. It was provided to me in private email by a ZTE engineer.
Warning
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Note
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool's unlock are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot, which provides a way to flash a custom boot and recovery (among other things).
Flashing Instructions
Place axon_mini_unlock.zip on the root of your sdcard.
Reboot into recovery.
Select "Apply update from SD card".
Select axon_mini_unlock.zip.
Usage Instructions
After the package is flashed, you may boot into the bootloader:
adb reboot bootloader
Once in the bootloader, you will see an on-screen menu. Additionally, you may access the typical fastboot commands:
fastboot oem device-info
fastboot oem unlock
fastboot flash ...
... etc ...
Download
axon_mini_unlock.zip
md5: ea8f1a21c8a46b3045d00f17a37fe359
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Yes, that is correct.
JoeGatto said:
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Click to expand...
Click to collapse
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Click to expand...
Click to collapse
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot.
Click to expand...
Click to collapse
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Yeah...verdandi is stuck on Marshmellow. But since it has different hardware it could brick if this is tried.
The ZTE engineer is USA based, he is not on the China development team (read: probably a support engineer). He said: "I attached the unlock update zip package, please try it. It is based on B14 build."
Sorry, that's all I have to go by for "official" information.
I do not want to be responsible for anyone bricking their device, so I cannot claim that this bootloader will work with anything other than a tulip device running 7.1.1 b14.
If you want to try and report back, I'm sure others will appreciate it. But I can't be responsible for the results.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Oh, and here is some more information to help you decide...
The volume key combo to enter EDL is handled by aboot (bootloader, eg. the thing we are flashing). This means even if you aren't currently able to use the key combo, you should be able to use it with the new aboot here. And if you can get to EDL, you can never really brick the device.
The volume key combo is detected very early in the aboot code. Like, first thing after basic platform init. So even if this isn't compatible with your device, it's likely we could restore the old aboot (assuming you back it up first, of course).
I'm convinced that the tulip is not locked based on my investigation today. So I have no idea if this aboot is properly signed. If your device is locked and this aboot is not signed properly, the lower boot loader won't load it. I'm not quite sure if that kicks you into EDL or not.
Not sure if that makes the decision easier or harder...
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
So here's the deal...
I initially assumed the bootloader was locked because... well... it's supposed to be. So I found the place in aboot code where it checks the lock flag in the devinfo partition. I used the firehose to write unlocked to that flag. Then I built TWRP, flashed it and it booted. So I assumed everything was working just as I expected.
Today, I flashed the aboot with fastboot support and ran "fastboot oem device-info". It said that my device was locked. So I went to look and, sure enough, my devinfo partition flag was still set. Hmm, that's odd.
So I wrote locked back to the flag. TWRP still booted. Now things are looking pretty suspicious.
But maybe the new aboot doesn't even support locking? So I flashed the original b14 version of aboot and TWRP still booted.
That's pretty hard evidence that aboot is ignoring the lock flag. I don't know what they did -- whether they just removed the code that reads the lock flag or introduced a bug or what.
This does not necessarily mean that the lower layers are unlocked. That is, the lower boot loader may still required a properly signed aboot. I don't know, and I'm not ready to brick my device trying to find out.
trpn111 said:
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
Click to expand...
Click to collapse
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Ah, yes, you have the euro model. See the "calling all mini owners" thread, posts #76 and #77.
maestromony said:
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Click to expand...
Click to collapse
i get a message saying "cant update from sd card?"
yeshivabachur said:
i get a message saying "cant update from sd card?"
Click to expand...
Click to collapse
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
JoeGatto said:
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
Click to expand...
Click to collapse
My battery was 80%+ mine still said can't update from sdcard
Aries2010 said:
My battery was 80%+ mine still said can't update from sdcard
Click to expand...
Click to collapse
Try turning on the OEM unlock setting in developer settings.
JoeGatto said:
Try turning on the OEM unlock setting in developer settings.
Click to expand...
Click to collapse
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Aries2010 said:
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Click to expand...
Click to collapse
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
JoeGatto said:
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
Click to expand...
Click to collapse
Thank you sir I appreciate it I shall try it tomorrow.
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
The "standard" (not Samsung) method of updating via OTA is to ship:
1. Full images of any firmware partitions (rpm, tz, aboot, etc.)
2. Full image of boot.
3. A delta (patch) to system.
Also note that custom recoveries generally do not work with vendor OTA's.
This means that if you wish to apply an OTA, you must first have stock recovery and a completely pristine, unmodified system partition. The rest doesn't matter.
yeshivabachur said:
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
Click to expand...
Click to collapse
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.
Hi guys I downloaded the REtail version of my firmware for my device here https://mirrors.lolinet.com/firmware/motorola/denver/official/RETUS/
But when I patched and installed it via adb it seems to be a success
HOWEVER
I am STILL get the metro by tmobile splash screen on booting and I still have metro by tmobile apps pre installed on my phone. AND THAT Annoying metro news screen when you swipe to the left.
Am I not installing the correct firmware xda bros? TIA
Futtbucker34 said:
Hi guys I downloaded the REtail version of my firmware for my device here https://mirrors.lolinet.com/firmware/motorola/denver/official/RETUS/
But when I patched and installed it via adb it seems to be a success
HOWEVER
I am STILL get the metro by tmobile splash screen on booting and I still have metro by tmobile apps pre installed on my phone. AND THAT Annoying metro news screen when you swipe to the left.
Am I not installing the correct firmware xda bros? TIA
Click to expand...
Click to collapse
You flashed it using the flash_file.xml as a reference for flash commands?
These are my recommended steps If you have a Windows machine.
How to Change Software Channel
sd_shadow said:
You flashed it using the flash_file.xml as a reference for flash commands?
These are my recommended steps If you have a Windows machine.
How to Change Software Channel
Click to expand...
Click to collapse
sd_shadow said:
You flashed it using the flash_file.xml as a reference for flash commands?
These are my recommended steps If you have a Windows machine.
How to Change Software Channel
Click to expand...
Click to collapse
Thank you sir I can confirm the flash_file.xml reference was followed in the commands. I double checked.
I LMSA says it can't verify my software and won't let me continue . I got the new september update and i think lmsa don't have it yet. idk why else it would say this.
bump. Anyone?
update: I Reflashed 3 times successfully only the SOFTWARE CHANNEL still shows Universal SKU
This picture i found from ebay is from the same model I have. Yet they have no metro bloatware and North America Retail under software channel, Mine says Universal SKU.
https://mirrors.lolinet.com/firmwar...T_regulatory-DEFAULT_cid50_CFC_R3_CFC.xml.zip Is the firmware I used to flash\
THanks in advanced!
Futtbucker34 said:
Thank you sir I can confirm the flash_file.xml reference was followed in the commands. I double checked.
I LMSA says it can't verify my software and won't let me continue . I got the new september update and i think lmsa don't have it yet. idk why else it would say this.
Click to expand...
Click to collapse
Your best bet is honestly to just either use a custom rom or to remove all the bloatware either manually or systemlessly.
Long Story - Short:
Just got home with an Unlocked sofiap XT2043 - Moto G Stylus , networked unlocked, and I am able to toggle the OEM Unlock switch in Developer Options, However:
how did y'all unlock the Bootloader to start with ?
fastboot flashing unlock = FAILED
fastboot oem unlock = FAILED
is there a method to discern my oem unlock code ?
Thanks in Advance for any assistance !
barguybrady said:
Long Story - Short:
Just got home with an Unlocked sofiap XT2043 - Moto G Stylus , networked unlocked, and I am able to toggle the OEM Unlock switch in Developer Options, However:
how did y'all unlock the Bootloader to start with ?
fastboot flashing unlock = FAILED
fastboot oem unlock = FAILED
is there a method to discern my oem unlock code ?
Thanks in Advance for any assistance !
Click to expand...
Click to collapse
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com