[Q] Oem unlock one plus one - ONE Q&A, Help & Troubleshooting

[Q] Oem unlock one plus one - ONE Q&A, Help & Troubleshooting

Hello
I just started the proces of unlocking the one plus one chinese version with cm11 on it but with color os recovery
I want to make it cwm or twrp
I did all the setup ok
When i did the comand fastboot oem unlock on the phone it shows a Chinese menu which i dont understand fastboot flash erase
As it is chinese language i dont know what to do on the phone.
I thought that smth went wrong so rebooted the phone and back to cm11 setup.
Any one can help what to do in this case what i have to do on the phone in this case. Where is yes or no in chinese( on the right or on the left)
The phone was disconected and I could not do fasboot reboot.
Any help is appreiciated.
I have prepared everything sdk platform supersu twrp.img
The only new thing which I never saw on guides is this chinese menu asking to flash erase.
But I dont know in this moment what to do.
Phone is ok back to Cm11.
Thanks

Can't say for sure but my guess is its asking yes or no to unlock, try one, if it doesn't reset your phone then try the other. Can't see any harm
Once unlocked you can flash all the cm firmware (bootloader, logo, etc) and you should end up with English in the bootloader from them on
Best of luck

How about to flash from colorOS recovery
demkantor said:
Can't say for sure but my guess is its asking yes or no to unlock, try one, if it doesn't reset your phone then try the other. Can't see any harm
Once unlocked you can flash all the cm firmware (bootloader, logo, etc) and you should end up with English in the bootloader from them on
Best of luck
Click to expand...
Click to collapse
Thanks for the reply but as I am new to this adb and fastboot I have seen in some posts that you can flash XPNH33R from colorOS recoery
I am not sure to do or not to do it. Will it have any damage to the phone??

To the best of my knowledge you can change just about everything from the Chinese version to the international. Here is a general tutorial for fastboot which should help you get your head around it
http://forum.xda-developers.com/showthread.php?t=2277112

Related

[Q] Boot Loop after touch screen change

Hi all,
I'm new on this forum, it's my first time here.
I have a problem with my son HTC ONE SV.
He has broken the touch screen, than I have find a complete replace touch screen in England for 45€, so I was happy because the assistence ask me 150 € and more for change the screen.
I have replace the Screen and I was very happy when I finish to assemble the phone and It's starts... but.... the Phone goes into a Boot Loop.
With volume down+ on button I can Enter into service menù and I have installa on my PC HTC driver, so when I attach the Phone to USB cabel from Fastboot I see "fastboot USB" on screen.
I have try to to a Factory Reset but nothig happen, the phone at every start goes into a Boot Loop.
I Have try to change back the original Screen (broken) and it's Boot loop also with the original screen (so I think the new screen is ok)
So the Phone is not Rooted and it's into original conditions with original Firmware branded TIM (Italy operator).
I have try to find some information about the possibility to flash the original Firmware or if possible a cutom Firmware, but I have found only information about Stok firmware or similar, and for this option I must have the Phone Rooted, S-OFF, unloked.
But my phone was not rooted or in s-off mode or unloked, or set into Debugmode from Settings (now is in boot loop and I can't acces to the settings menù).
Can someone help me with this problem?
I need only to do a factory reset with original firmware, or , if possible in this condition, install a custom firmware.
There is the possibility to flash original firmware (I have 2 HTC ONE SV, other 2 son where I could extract the original firmware if necessary)
Many thanx to all.
Massimo from Italy

Never had to do such things. But the only thing you can do is, unlock your device with htcdev.com, use custom (TWRP) recovery and flash back a backup or a stock rom.
Is your phone k2u or k2ul?

many thanx
old.splatterhand said:
Never had to do such things. But the only thing you can do is, unlock your device with htcdev.com, use custom (TWRP) recovery and flash back a backup or a stock rom.
Is your phone k2u or k2ul?
Click to expand...
Click to collapse
Many thanks,
what is k2u or k2ul?..... k2u is not LTE version and k2ul is LTE version
I have Unlook the bootloader, now is UNLOCKED.
For TWRP I have find this http://forum.xda-developers.com/showthread.php?t=2280241
So I have flash the recovery:
Recovery_TWRP_2.6.3.2_K2_UL.img Older version
Only for k2u & k2ul!
But After if I press recovery the phone boot and show a description:
This build is for developed purposes only
Do not distribuite outside of HTC
withot HTC's writeren permission.
Failture to comply may lead to legal action.
In attach 2 immage

That screen is normal after unlocking.
So you can't boot into recovery?
How did you flash?

old.splatterhand said:
That screen is normal after unlocking.
So you can't boot into recovery?
How did you flash?
Click to expand...
Click to collapse
I coonect the phone to usb and from Fastboot I flash with:
fastboot flash recovery recovery.img
Where recoveryimage.img is Recovery_TWRP_2.6.3.2_K2_UL.img
After the flash I back to main menù and run recovery but after the splash screen with the message the Phone enter into loop reboot

Did you rename Recovery_TWRP_2.6.3.2_K2_UL.img to recovery.img?
Whats written in your cmd window?

old.splatterhand said:
Did you rename Recovery_TWRP_2.6.3.2_K2_UL.img to recovery.img?
Whats written in your cmd window?
Click to expand...
Click to collapse
Yes I rename Recovery_TWRP_2.6.3.2_K2_UL.img to recovery.img and put it into the same folder with fastboot.exe
In CMD window i wrote
fastboot flash recovery recovery.img

Ok, but do you see in cmd window, that recovery is flashed successfully?

old.splatterhand said:
Ok, but do you see in cmd window, that recovery is flashed successfully?
Click to expand...
Click to collapse
Yes the message show me succefully flash ok

Then you should be able to boot into recovery.
Please give the 2.7 recovery a try.

old.splatterhand said:
Then you should be able to boot into recovery.
Please give the 2.7 recovery a try.
Click to expand...
Click to collapse
Nothing..... always loop reboot when lunch recovery.
I have also try to do:
fastboot reboot-bootloader
rhan
fastboot erase cache
then
lunch recovery but the phone show the HTC messagge and thena loop reboot

I'm running out of ideas
It seems, something else/more is broken on your phone, because as you are unlocked and flashing shows fine, you should be able to enter.
Last try from my side, hopefully this works: http://d-h.st/NXX

old.splatterhand said:
I'm running out of ideas
It seems, something else/more is broken on your phone, because as you are unlocked and flashing shows fine, you should be able to enter.
Last try from my side, hopefully this works: http://d-h.st/NXX
Click to expand...
Click to collapse
nothig, always the same.
thanx for your help.
I hope someone can suggest me a solution.
If I'll resolve the problem I'll let you know.
or as you suppose something is broken in my phone, because factory reset loopreboot like the Recovery
many thanx again.
bye
Massimo

polimarx said:
nothig, always the same.
thanx for your help.
I hope someone can suggest me a solution.
If I'll resolve the problem I'll let you know.
or as you suppose something is broken in my phone, because factory reset loopreboot like the Recovery
many thanx again.
bye
Massimo
Click to expand...
Click to collapse
Did you change the touchscreen only or the lcd along with the touchscreen as well? If you followed everything with how to flash recovery and firmware, maybe there is some mismatch with your screen assembly and the phone software. Some phones come with different revisions for the lcd screens. Maybe that is the problem. But I am not sure about One SV different LCD revs.
Before I was using galaxy wonder and it had three diffrent LCD revisions and one of them exhibited a bug with the Cyanogen OS where as the others did not.
I would take the phone to the shop where you got the touchscreen and ask them for help.
Sent from my HTC One SV using Tapatalk

Soft bricked shield tablet PLEASE HELP!

So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.

okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader

Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"

danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha

Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.

Okay will try that. Thanks man.

Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5

Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.

Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.

Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5

Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?

Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.

koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?

Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?

Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.

koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader

[Q] [HELP] Unable to succesfully install ANY recovery

After trying for over three hours, reading what seems like all threads on the whole of xda and some other sites... i am ready to eat my phone. Ok, must get myself together :-/ . Here we go.
Specs:
Moto G 4g on dutch carrier (vodafone), XT1039
Situation:
Came from completely stock lollipop system, then succesfully unlocked phone via motorola website using the fastboot proces. Intending to install custom rom, first need a recovery. I am now stuck at this step. When booting i now get a screen "warning bootloader unlocked" before the moto splash begins, this is normal as far as i understand.
Problem:
Unable to boot into recovery. Directly after flashing any recovery (with fastboot) and choosing "recovery" from the bootloader i get the message "boot up failed"
After restarting the phone and choosing "recovery" from the bootloader i get the android on its back picture stating "no command"
Already tried:
installed the android sdk, fastboot and mfastboot.
Am able to send commands to phone with (m)fastboot. Flashing works.
I flashed: openrecovery twrp 2850 xt1032, clockwork 6047 falcon, philz touch 6587 falcon, twrp 2870 falcon m stock, twrp 2801 titan v2 and twrp 2860 xt1032
all give exact same result
"fastboot boot NAME of IMAGE"
"fastboot erase userdata & cache"
"fastboot erase recovery"
did the above things in any imaginable combination
I hope someone has some fresh suggestions for me? Thanks for your time.

Bro as far as I know the recovery is not installed u should install twrp from this thread the one on the official site gave me soft brick
Now about the dead android with no command shows that you are on stock recovery and u have booted into it successfully to go further into stock u have to press power and volume up at the same time (like u lock ur phone) but it won't help in installing anything try the recovery I linked (first format your phone complete data and cache wipe from stock recovery not necessary actually) install it through fastboot command and let me know if it worked (with thanks button) BTW what's ur bl ver

thanks for your fast response faizxy, as stated i already tried the one from that thread (i did not use the identical interpunction to describe it but to be clear it is twrp-2.8.7.0.-falcon_M_STOCK.img)
Where do i find my bootloader version? It is the one that came with the device, factory issue...

Some extra info, that might anwser faiz' question: when i boot the bootloader it shows:
"AP Fastboot Flash Mode (S) 41.1A (sha-80481ae, 2015-04-10 14:30:28)

Hope you guys will forgive me for bumping a bit soon, but I really hope some one has a solution! Tomorrow I have time to tinker some more

Have you tried at least one recovery that is actually for your phone (peregrine)?

_that said:
Have you tried at least one recovery that is actually for your phone (peregrine)?
Click to expand...
Click to collapse
Ah. I guess not. Did not know that there where recovery's specifically for the peregrine/xt1039. I searched for "moto g" but apparently is wrong model. DOH!
Thanks for helping out! My problem is solved.
For future reference; finding working pergerine recovery was quite difficult; most mirrors are down. I found one here: https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine and then under header "installing recovery.." under step 2 the download link (i avoid deeplinking)
This one seems to work for me. Now lets find a nice custom rom!
The ones listed here http://forum.xda-developers.com/moto-g/4g-development/progress-twrp-2-7-1-0-source-t2807585 dont work for me. One gives black screen, the other one shows an unlock slider which is unresponsive.

Hi,
Try this one... With encryption abilities or without, your choice...
http://forum.xda-developers.com/showthread.php?t=2996266

Trying to flash TRWP Moto Z recovery - not working

Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork

spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar

the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork

spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.

the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:

Do you have the Verizon model?

samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03

spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.

The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?

I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?

What if fastboot boot twrpname.img
It's really weird anyway...

enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.

spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...

enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.

spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...

if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img

hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????

Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.

I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.

cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!

[CLOSED] Delete Thread

Due to the disrespect of certain members here I will no longer share the tutorials.

Hi Articul8Madness,
Seems very cool. I'm new with XDA, and just got this moto one 5G ace from Metro as well. Are you recommending to flash it with the US retail ROM? Will it actually unlock the phone?
Tkx,
MH

huayixin said:
Hi Articul8Madness,
Seems very cool. I'm new with XDA, and just got this moto one 5G ace from Metro as well. Are you recommending to flash it with the US retail ROM? Will it actually unlock the phone?
Tkx,
MH
Click to expand...
Click to collapse
I actually have the RETBRAZIL rom currently flashed to it, lol. But I've tried the RETUS, RETEU roms. The TMO and Sprint ROM will get you a MetroPCS load screen as its the same.
And no, it will not unlock the phone. MetroPCS ties the IMEI to the Sim Card. They will not unlock this phone even if you pay in full like I did for three consecutive months of service. This is why no one Sim Unlocks Metro phones.

This way I was able to clean flash without any problems.
Is there a dirty flash that doesn't erase user data?

Articul8Madness said:
I actually have the RETBRAZIL rom currently flashed to it, lol. But I've tried the RETUS, RETEU roms. The TMO and Sprint ROM will get you a MetroPCS load screen as its the same.
And no, it will not unlock the phone. MetroPCS ties the IMEI to the Sim Card. They will not unlock this phone even if you pay in full like I did for three consecutive months of service. This is why no one Sim Unlocks Metro phones.
Click to expand...
Click to collapse
Thanks, really appreciate the insightful reply.

PEACH-PIT said:
This way I was able to clean flash without any problems.
Is there a dirty flash that doesn't erase user data?
Click to expand...
Click to collapse
There is no dirty flash for stock since this isn't a ROM but firmware. I suggest you backup your texts, phone logs, pictures, and anything else before you flash.

PEACH-PIT said:
...Is there a dirty flash that doesn't erase user data?
Click to expand...
Click to collapse
Yes, but it's not really advisable, it could cause apps to not work as expected.
Skip data wipe post #6

sd_shadow said:
Yes, but it's not really advisable, it could cause apps to not work as expected.
Skip data wipe post #6
Click to expand...
Click to collapse
Thank you.
I'll give it a try.

Articul8Madness said:
This tutorial is for people like me than ran into problems rooting the Moto One 5G Ace XT2113 (MetroPCS Qualcomm Variant) running on stock Android 10. I got this today after my beloved Moto G7Power's usb/charging port melted and fell out the phone after two and a half years and MetroPCS would NOT honor my insurance and replace the phone. Long story there. So far, this phone's been a good replacement but I'm still early in the game.
Follow the following at your own risk! I am not responsible for any mishaps with your devices. I also don't know if this will work on other variants, as I only have these for MetroPCS, and from my understanding this will NOT obviously work for Verizon, AT&T, and Cricket phones because you have to have the bootloader unlocked.
I want to thank @sd_shadow for pointing the way for me. This phone is a bit different being a new OS and a different updated Moto, and sd_shadow helped me get through the curious WTF now moments. This guide is solely for people like me that jumped head first into this phone with our variant trying to root and ran into some problems.
Introduction/Preparation
First, go and prepare by READING EVERYTHING OF THE FOLLOWING. Very important. Don't even jump into this without reading this thread here all the way to the last page: Motorola Guide To Flashing (this is so you know start to finish the differences between this model and maybe your previous models, plus the differences now between flashing Android 9 to 10, having an A/B system versus the new fastbootd mode).
Second, unlock the bootloader. The MetroPCS variant can be unlocked by Motorola; follow their instructions, it's easy peasy. Use their data tool to get the code formatted correctly or you may have problems. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). I did it in Waterfox this go round and it sent the codes immediately . When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
***NOTES SO YOU DON'T FREAK OUT***
1. Every time you power up the phone after you unlock the bootloader Moto will try and make you feel like crap with a bad throwing shade with a message that your phone is not to be trusted and the bootloader is unlocked. :laugh: This is normal. Give it a minute, you havent broke it.
2. There is no custom recovery/TWRP for this variant as of yet, so flashing the stock roms via fastboot is the only way to reset.
3. OEM Unlocking toggle switch is interesting. On my first phone it was activated once the bootloader is unlocked and greyed out to where it couldn't be accessed anymore. Same thing happened with my Moto G7Power so I'm assuming that's the new normal.
Files
If you tried to root like me and lost ALL touchscreen usability, then this is what you're going to have to do to come back from the paperweight abyss. First, pull out your Sim Card flashing. Yes, pull it out and flash without it. Flashing with the sim card/SD card in can cause problems flashing.
1. Get Minimal ADB and Fastboot (it's easier to use than Android SDK and smaller). Or you can use the Fastboot software of your choice. I used Minimal ADB and Fastboot.
2. Download the Motorola Drivers from their site (if you run into problems you will have to uninstall and reinstall them through their utility.
3. Cpu-Z.apk (This is a good thing to have to know your hardware responsibly).
4. Stock Firmware. I used XT2113_KIEV_RETUS_10_QZK30.Q4-40-55_subsidy-DEFAULT_regulatory-DEFAULT_CFC_R1_CFC.xml which is the US Retail software instead of MetroPCS's firmware because I hate any branded US carrier bloatware and such and like that factory unlocked from the manufacturer feel. Both of my phones flashed fine with it and you can find it here: Moto One 5G Ace ALL Firmwares. It doesn't matter what your carrier is, they have them all there. Try them at your discretion and risk.
****Notes on Flashing The Stock Firmware****
The best way to find out what your codes are is to go to the flashfile.xml that is located in the rom you downloaded. Once you get that the best way to use it since it won't be legibile for flashing is to put it in the online flash converter here: Online FlashFile Converter And don't worry - flashing another stock won't relock the bootloader.
Also, just so you know, once you flash and boot the phone back up you MUST put the sim card back in or a message about the phone being locked once you begin to set it up will come up. Just pop it in enough to get past that screen then remove it. Last thing you want is your data updating the phone without your permission and you turning it off.
1. Extract the firmware to the folder where Minimal ADB & Fastboot are at on your computer.
2. Turn the phone completely OFF and back ON if you haven't done so yet. Make sure there is no Sim Card of SD card in it.
3. Press Volume Up and Power to boot into fastboot mode if you have no touchscreen access. If you do just reboot or turn the phone off and turn it back on the regular way.
4. Plug your phone via USB cable into the computer.
5. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure all your firmware files have been extracted in the Minimal ADB directory or it won't work.
7. Cut, Copy, and Paste in Fastboot All Together everything from the Online Flash File Converter. In my case since I used the RETUS version mine looked like this:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
echo -----------------------------------------------------------------------------------------------
echo English - Process concluded!
echo Português - Processo concluído!
echo English - Press any key to restart the phone!
echo Português - Pressione qualquer tecla para reiniciar o celular!
echo -----------------------------------------------------------------------------------------------
pause
fastboot reboot
exit
8. When it is done it will stop. Hitting enter did not reboot my phone so I did it manually by hitting the Power button on START while still in flashboot.
9. That's it! You should have your phone officially flashed to firmware of your choice.
Hope this helps my fellow MetroPCSers. I lost ALL functionality of my touchscreen trying to root and with a little help from my XDA friends brought them back with this method. Old girl is working and now I'm working on a proper root with a proper matching boot.img.
And please, tinker with the little tyke responsibly. ;-P
Click to expand...
Click to collapse
Nice walkthru . Does this phone support monitor mode? I dont wanna root this Beauty unless i can put this gear to work.
THANKS

majored said:
Nice walkthru . Does this phone support monitor mode? I dont wanna root this Beauty unless i can put this gear to work.
THANKS
Click to expand...
Click to collapse
Thanks. I don't know if it supports monitor mode or not as I haven't installed Kali Nethunter on it.

If I put the retailus firmware on my metro phone will it still recieve over the air security updates?

retrov said:
If I put the retailus firmware on my metro phone will it still recieve over the air security updates?
Click to expand...
Click to collapse
Most likely no, you may need to flash firmware manually.

sd_shadow said:
Most likely no, you may need to flash firmware manually.
Click to expand...
Click to collapse
Thank you, I was able to flash worked great. I flashed the latest retail us rom has security update for march. Any recomendations on relocking the boatloader without bricking it if I need to send in for repair or something?

retrov said:
Thank you, I was able to flash worked great. I flashed the latest retail us rom has security update for march. Any recomendations on relocking the boatloader without bricking it if I need to send in for repair or something?
Click to expand...
Click to collapse
If you need to relock your bootloader, you must flash back to the original stock firmware for your variant or you will find yourself stuck in EDL mode.

can someone tell me why i cant mount my moto 5g ace is rooted with magisk but adb mount not in /proc/mounts

seriously you should know that you are a good person. when i attempted to flash a custom rom which ive done many times before but failed this time and ended up with no touch capabilities i got really depressed. coming across your forum and seeing you had the same issue really made my day. keep it up man.

Articul8Madness said:
I actually have the RETBRAZIL rom currently flashed to it, lol. But I've tried the RETUS, RETEU roms. The TMO and Sprint ROM will get you a MetroPCS load screen as its the same.
And no, it will not unlock the phone. MetroPCS ties the IMEI to the Sim Card. They will not unlock this phone even if you pay in full like I did for three consecutive months of service. This is why no one Sim Unlocks Metro phones.
Click to expand...
Click to collapse
Not true, I paid an unlocking service and got my MeotroPCS Motorola One 5G Ace SIM unlocked. I can and do use other SIM cards from other carriers.

mewcatchew said:
Not true, I paid an unlocking service and got my MeotroPCS Motorola One 5G Ace SIM unlocked. I can and do use other SIM cards from other carriers.
Click to expand...
Click to collapse
Consider yourself lucky as it does not work for all branded Metro phones. Also, why pay when you could have waited 3 months of continuous service and got it unlocked by them for FREE.

Articul8Madness said:
Consider yourself lucky as it does not work for all branded Metro phones. Also, why pay when you could have waited 3 months of continuous service and got it unlocked by them for FREE.
Click to expand...
Click to collapse
Because it's 6 months, not 3.

Database Info

welcome