So... I tried rooting the phone and now I'm stuck at fastboot mode, I already tried exchanging the phone with another and nothing, downloaded rds lite and tried flashing the brazil firmware but it won't let me and gives me the getvar error, I deleted the line and then I get another error, something about a gtp 1/11
Could anyone help me?
Dont install it with rsd lite, flash a homemade fastboot from development
Enviado desde mi XT890 usando Tapatalk 2
I was just reading that thread but it doesn't says how to flash the homemade fast boot D:
AW: [Q] Stuck at fastboot mode :( (Mexico-Telcel)
Your Bootloader is unlocked? If not you will have to do that first, before you can use the Homemades.
For me it sounds like you are locked.
People on JB hard bricked by downgrading to ICS with RSD. They would be happy, when there had been an message like gpt.bin fail.
If you where unlocked, the gpt.bin would pass, AFAIK
Sent from my XT910
HSD-Pilot said:
Your Bootloader is unlocked? If not you will have to do that first, before you can use the Homemades.
For me it sounds like you are locked.
People on JB hard bricked by downgrading to ICS with RSD. They would be happy, when there had been an message like gpt.bin fail.
If you where unlocked, the gpt.bin would pass, AFAIK
Sent from my XT910
Click to expand...
Click to collapse
I see, could you point me to a thread on how to unlock the boot loader?
Thanks in advance.
AW: [Q] Stuck at fastboot mode :( (Mexico-Telcel)
http://forum.xda-developers.com/showthread.php?p=32576654
Sent from my XT910
Ah, nice, I unlocked the bootloader and installed the homemade fastboot, thanks for your time and help.
So I guess the warranty is void now? Is there a way hide the fact that it has been unlocked?
Related
Hello guys this is my first post in XDA and I am a completely noob so I am here asking for help.
So this is my history.
I recently buy (cheap, about 20 dls) an Atrix HD MB886 (at&t), the reason of the cheap price is because the phone is in a boot loop and
the last owner don't want to deal with it, so it offers it to me, and I buy it with the hope that in this forum i will find the solution.
I have tried to flash it to the stock rom 4.1 posted by the Firmware team, using RDS Lite 6.1 and the process always finalize with no errors, sometimes with PASS
and other times with "Reboot the device manually", the problem is that the phone won't load the S.O and it reboot itself until the battery is dead.
Another observation is when the phone is in AP fastboot and the RSD reboot the fastboot during the process, a message appears saying :
Reason : sticky bit fastboot.
I am sure that the phone isn't rooted, and the bootloader is locked.
I hope that somebody can help me to flash this phone.
Thank you and sorry for my bad english.
you can try installing system.img using fastboot..
ai6908 said:
you can try installing system.img using fastboot..
Click to expand...
Click to collapse
Hello ai6908.
Thank you for your quick response,
You said to use the command
fastboot flash system system.img
and then
fastboot reboot?
Thanks again.
yes...
Nothing happened
Same boot loop.
Maybe a bad phone?
Sent from my MB886 using xda premium
the first question:
From fastboot, (or mfastboot,) I'm attempting to write and reflash my system. Would cyanogen mod have named the partitions anything other than what they are?
(example of command i attempted : mfastboot format system
Mfastboot replied something about variables, and system not being one of them)
Can someone tell me how to get a sort of cm11 device map, or diagram with all partitions and file path names?
So how did i get here?
I was running low on storage and decided to stop by my buddies place to use his pc and clear some space in my device. (recently unemployed, evicted, completely screwed, yea- REALLY.) Quickly after i plugged into the pc i had to unplug for a moment so i just pulled the usb cable from the port, like i have done many times before, bypassing the pc's directions to disconnect first... Immediately my phone started boot-looping only the "bootloader unlocked" screen over and over... The first thing i attempted to remedy the situation was hold the power button for 10 seconds in an attempt to restart the device. When it began doing things the same way, i went to recovery, via fastboot, and attempted to 'install zip from sdcard'. The reply was that recovery couldn't mount storage. I tried to reboot recovery and try again but got the same result. Next i rebooted to recovery and attempted to factory reset but it froze recovery after i confirmed the command. Had to hold power + volume down for 10 seconds and let it reboot to fastboot, choose recovery, then mounts/storage, format system, and that froze recovery again, so, now I'm realizing that recovery is broken.
I hooked up top the pc and went to fastboot mode, made sure my device was recognized, then read up on some commands, because, honestly, I've rarely used it outside of doing strictly what some tutorials told me to do. (Although, the last time i had to use it, i had great success using minimal reference and mostly luck, i saved my moto x from what i thought was certain death.)
Unfortunately, this time, I'm pretty certain. But at the same time- i can get to recovery, that's a great sign, right? To me, it means it's not dead yet!
First i used fastboot in an attempt to format the caché, just to 'feel it out.' I wish i could remember what it told me, but the gist of it sums up to the cache being erased, but the rest if the reply was negative.
I tried similar commands from formatting the system to the recovery in order to rewrite the recovery image, but no luck there... All commands give me responses regarding variables or they are bring denied by the device, which brings my next question, (which is not a cm question, but a general one... I only ask here because i began this post with a question regarding cm)
When a moto x with an unlocked bootloader boots to AP fastboot, at the end of the first line at the top there is
(S)
I believe on my past rooted devices that either (S-ON) or (S-OFF) would be there regarding their status as superuser.
With my device displaying only ' (S) ' in this place, does that indicate that I've lost superuser privileges our anything at all, for that matter?
I am so lost, friends... That device is everything to me, even without cellular service, when i get close to wifi, i contact my family, look for a job, read, and keep up with my medical requirements.
As i live to say at this point, any and all info and input will be greatly appreciated!!!
If you can enter to recovery or fastboot mode your phone isn't dead. Have you tried to flash the last STOCK FIRMWARE that you installed? Whit RSD. There is no problem if you've lost root privileges while BootLoader doesn't says "Device Locked".
You can save your phone. Good luck!
Enviado desde mi XT1053 mediante Tapatalk
Joseluize said:
If you can enter to recovery or fastboot mode your phone isn't dead. Have you tried to flash the last STOCK FIRMWARE that you installed? Whit RSD. There is no problem if you've lost root privileges while BootLoader doesn't says "Device Locked".
You can save your phone. Good luck!
Enviado desde mi XT1053 mediante Tapatalk
Click to expand...
Click to collapse
That's such good news! I'm not familiar with rsd, though. What is it all about? And no, I didn't try stock firmware...
Here's the solution.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Thanks to @TechSavvy2 for his guide.
Enviado desde mi XT1053 mediante Tapatalk
Have you tried mfastboot or fastboot erase instead of format?
Joseluize said:
If you can enter to recovery or fastboot mode your phone isn't dead. Have you tried to flash the last STOCK FIRMWARE that you installed? Whit RSD. There is no problem if you've lost root privileges while BootLoader doesn't says "Device Locked".
You can save your phone. Good luck!
Enviado desde mi XT1053 mediante Tapatalk
Click to expand...
Click to collapse
I've seen you help several users now by directing them to the "Return to Stock" thread. Excellent advice - thanks for helping out!!!!
Just FYI, you can flash the STOCK firmware even with a locked bootloader as long as it is the SAME firmware that came on the phone. This is because the stock firmware is signed with release keys, and the CID will match.
The only reason you need to unlock your bootloader to flash a STOCK firmware is if you are flashing a different carrier's firmware (which we don't recommend).
samwathegreat said:
I've seen you help several users now by directing them to the "Return to Stock" thread. Excellent advice - thanks for helping out!!!!
Just FYI, you can flash the STOCK firmware even with a locked bootloader as long as it is the SAME firmware that came on the phone. This is because the stock firmware is signed with release keys, and the CID will match.
The only reason you need to unlock your bootloader to flash a STOCK firmware is if you are flashing a different carrier's firmware (which we don't recommend).
Click to expand...
Click to collapse
Thanks! I am helping because I bricked my phone recently and I don't want that people do the same. I can't write too much (yet). My main language is Spanish and I'm just an English trainer. Greetings!
Enviado desde mi XT1053 mediante Tapatalk
Hello guys, I have unlocked the bootloader successfully a while ago. Without any reason my device won't load the system, instead it's stuck in the bootloader unlocked warning.
I'm able to access my AP FASTBOOT!
where to go from here? just can't find the right thread. can someone help me please?
Can u get in recovery mode?
Verstuurd van mijn XT890
unfortunately not. again the bootloader unlocked warning showing up.
I'm okay for a clean reinstallation, but how do I do that from this situation? everything was working perfect before I made a restart on that device.
crap
I got it solved. updating RSD to a recent ver. did the trick for me
Megamagma said:
I got it solved. updating RSD to a recent ver. did the trick for me
Click to expand...
Click to collapse
Hi, which version of RSD did you use? And which firmware?
I've a similar problem, stuck on the red moto logo, can access fastboot and recovery but data wipe and factory reset don't work.
All comments much appreciated.
Nick
Hello...im new here
Im with a xt1064 with bootloader unlocked, i can start on fastboot and flash a new rom with adb, the problem is:
It stucks on warning bootloader, i can't access recovery or any of the options on fastboot because it goes to warning bootloader message and still there until battery runs out.
Ps: i can flash a new rom without problem, but when the device reboot, it stills on warning. Is there any way to solve this? Thanks and sorry for the bad english.
ur able to into fastboot thats good try restoring to original stock firmwire and than if it goes succesful try to try the procedure again.. mayb u missed some step or so?
Sent from my Moto G 2014 using Tapatalk
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
sprays said:
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
Click to expand...
Click to collapse
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
sprays said:
You should be able to reflash the firmware
Use
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
Click to expand...
Click to collapse
have you tried unlocking your bootloader again?
sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
kewlzter said:
have you tried unlocking your bootloader again?
Click to expand...
Click to collapse
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
sprays said:
You should be able to reflash the firmware
Use
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
Click to expand...
Click to collapse
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
kewlzter said:
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
Click to expand...
Click to collapse
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
sprays said:
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
Click to expand...
Click to collapse
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
?
kewlzter said:
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
Click to expand...
Click to collapse
Ty for the advice... I will do that.
Yea, i can wipe data/factory reset, but its the same. Bootloop until stuck to "fastboot reason: fall-through from normal boot mode."
I've read about this scenario for months on several different model forums and I imagine my best chance is to use the blankflash in edl mode but i can't boot into edl mode. Wherever I connect it is always recognized as a Motorola PCS or Motorola ADB device. I'm thinking of buying the deep flash cable and see if it works ...
$ fastboot getvar current-slot
//Getting and setting the slot should not cause any harm, but you never know.
$ fastboot --set-active=<a/b - whichever "current-slot" isn't.>
$ fastboot reboot
EDIT0:
In addition, you should plan ahead if you do get in. Like doing everything it takes to allow you to unlock/flash (adb).
You don't want to miss anything critical and screw up that other slot too.
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Hazardous2u said:
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Click to expand...
Click to collapse
Aún no hay solución
To everyone who is having this problem, just run the command multiple times in a row and it works! I don't know why, but just running it a few times in a row (I had to do like 9 times) gave me the unlock code.
Same thing for applying the code after getting it from Moto. Had to do it like 9 times in a row again, but it worked.