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
Related
Hi people, I have a big problem with my friend's Razr i, I was trying to root it, but i didn't want to unlock my bootloader so tried several methods but not a single one worked, So i tried the one for unlocked bootloaders and ended up bricking my device, Now It's stuck on fastboot mode.
I've tried to flash some brazilian firmwares via RSD lite, but it get stuck on "6/9 flashing radio_signed" SO PLEASE SOMEONE GUIDE ME TO THE SOLUTION WHAT AM I DOING WRONG?
PS: Also tried to flash an argentinian Firmware but it didn't even let me start flashing bringing the error "Faled flashing process. Unknown fastboot command. (getvar)"
PS2: Also tried the eternityprj Alternate method without RSD, and it gets stuck on flashing recovery... and it also prompts some errors you can see in the attached file.
HELP ME PLEASE AS I SAID THE RAZR IS A FRIEND'S PHONE NOT MINE, I NEED TO SAVE IT.
Vaizen said:
Hi people, I have a big problem with my friend's Razr i, I was trying to root it, but i didn't want to unlock my bootloader so tried several methods but not a single one worked, So i tried the one for unlocked bootloaders and ended up bricking my device, Now It's stuck on fastboot mode.
I've tried to flash some brazilian firmwares via RSD lite, but it get stuck on "6/9 flashing radio_signed" SO PLEASE SOMEONE GUIDE ME TO THE SOLUTION WHAT AM I DOING WRONG?
PS: Also tried to flash an argentinian Firmware but it didn't even let me start flashing bringing the error "Faled flashing process. Unknown fastboot command. (getvar)"
PS2: Also tried the eternityprj Alternate method without RSD, and it gets stuck on flashing recovery... and it also prompts some errors you can see in the attached file.
HELP ME PLEASE AS I SAID THE RAZR IS A FRIEND'S PHONE NOT MINE, I NEED TO SAVE IT.
Click to expand...
Click to collapse
your secure level was to high for a non bootloader method and if you done a method with a unlocked bootloader and your bootloader was locked thats bad.
unlock your bootloader >>WARRANTY VOID<< install cwm and use any backup. or flash the 39 gb fw but i think you have yet to unlokc the bootloader to safe it.. and be patient dont try to much stuff if your battery goes low you need a factory adapter or something like this to charge ur razr i if the battery is down.
regards hope you get it waorking again
I solved my problem this way
Vaizen said:
Hi people, I have a big problem with my friend's Razr i, I was trying to root it, but i didn't want to unlock my bootloader so tried several methods but not a single one worked, So i tried the one for unlocked bootloaders and ended up bricking my device, Now It's stuck on fastboot mode.
I've tried to flash some brazilian firmwares via RSD lite, but it get stuck on "6/9 flashing radio_signed" SO PLEASE SOMEONE GUIDE ME TO THE SOLUTION WHAT AM I DOING WRONG?
PS: Also tried to flash an argentinian Firmware but it didn't even let me start flashing bringing the error "Faled flashing process. Unknown fastboot command. (getvar)"
PS2: Also tried the eternityprj Alternate method without RSD, and it gets stuck on flashing recovery... and it also prompts some errors you can see in the attached file.
HELP ME PLEASE AS I SAID THE RAZR IS A FRIEND'S PHONE NOT MINE, I NEED TO SAVE IT.
Click to expand...
Click to collapse
Hello good morning
I brick 2 phones trying to get one of them and in the process did fail at 2, how the recovery?
1. - Use RSD Lite version 6.1.4
2. - Use 1 extra phone (htc wildfire root and backup CWMR in case of failure)
3. - Use a GB retail rom (CFC_8.7.1I-110_IFW-39_S7_UCASMI01E1017.0R_USASMIICSRTGB_P042_A005_S1FF_fb.xml)
4. - The phone to unbrick, put fastboot mode, switching on via the power button and vol (-) until the fastboot mode screen read "fastboot reason:" if it does not, re-try until there is
5. should not say "fastboot reason: flash failure, or anything else xxxxxx xxxx xxxxx ............"
6. - Boot rsd lite 6.1.4, select retail rom, and indicate that only "unzip" connects your motorola razr I, and it connects back to the other phone (in my case htc wildfire), which has a debug mode enabled.
7. - Note, that in the window of the Rsd Lite in row 1, the Razr I phone is detected, then you start flashing in RSD Lite 6.1.4, see screenshot of your razr I to see that data is being sent, (the other phone should not be affected and only serves as a decoy to usb drivers, Rsd lite at least do not damage to my phone)
8. - Remember flashing erase the card was in your internal Razr I therefore will lose programs, photos or music you had or downloaded to the SD or internal virtual
9. - Flashing can stop and have to do everything again, but remember that no fastboot mode screen should read:
"fastboot reason: flash failure or otherwise else xxxxxx xxxxxxx ......." must be clean that is just:
"fastboot reason: "
luck : Good:
Warning, do not take responsibility for any damage to your cell involved in the process, ......... the lure of the phone can be found on youtube and just suits the way because of my need to get my phone ........ in no way am programmer or software developer, for which only comment what turned out ok to me
excuse my bad English
jacbarahona72 said:
Hello good morning
I brick 2 phones trying to get one of them and in the process did fail at 2, how the recovery?
1. - Use RSD Lite version 6.1.4
2. - Use 1 extra phone (htc wildfire root and backup CWMR in case of failure)
3. - Use a GB retail rom (CFC_8.7.1I-110_IFW-39_S7_UCASMI01E1017.0R_USASMIICSRTGB_P042_A005_S1FF_fb.xml)
4. - The phone to unbrick, put fastboot mode, switching on via the power button and vol (-) until the fastboot mode screen read "fastboot reason:" if it does not, re-try until there is
5. should not say "fastboot reason: flash failure, or anything else xxxxxx xxxx xxxxx ............"
6. - Boot rsd lite 6.1.4, select retail rom, and indicate that only "unzip" connects your motorola razr I, and it connects back to the other phone (in my case htc wildfire), which has a debug mode enabled.
7. - Note, that in the window of the Rsd Lite in row 1, the Razr I phone is detected, then you start flashing in RSD Lite 6.1.4, see screenshot of your razr I to see that data is being sent, (the other phone should not be affected and only serves as a decoy to usb drivers, Rsd lite at least do not damage to my phone)
8. - Remember flashing erase the card was in your internal Razr I therefore will lose programs, photos or music you had or downloaded to the SD or internal virtual
9. - Flashing can stop and have to do everything again, but remember that no fastboot mode screen should read:
"fastboot reason: flash failure or otherwise cuarquier xxxxxx xxxxxxx ......." must be clean that is just:
"fastboot reason: "
luck : Good:
Warning, do not take responsibility for any damage to your cell involved in the process, ......... the lure of the phone can be found on youtube and just suits the way because of my need to get my phone ........ in no way am programmer or software developer, for which only comment what turned out ok to me
excuse my bad English
Click to expand...
Click to collapse
Could PM Me with the instructions in spanish, there are some things that i do not understand in your english
Tried to use your method but RSD lite got stuck on "4/11 erase userdata" and the phone says "program dummy sp block for userdata" I don't thin I understood well the part of the second phone, does it have to be on, i mean normal on, or does it have to be in flashmode aswell?
Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English
Well you tried to flash a rom through stock recovery with a locked bootloader. Not the best decision. Go look at the tutorial in general.
Sent from my PACMAN MATRIX HD MAXX
iv-med said:
Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English
Click to expand...
Click to collapse
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
i have the same problem but flashing back to stock rom with rsd will not work
I get a 1/23 partition type erro
and myth will now work due to fastboot, adb and attrib is not known as and internal or external command
skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
Having this same problem when trying ota Kit Kat update from T-Mobile. The only way I can get back into 4.2.2 is to use Minimal Fastboot and give the command 'fastboot erase cache'. Even when I do this the phone never says if the cache erasure is complete but Minimal Fastboot says that it is. I have RSD lite installed on my CPU but can't seem to find a working link to the stock T-Mo images. Any help would be appreciated.
Just to add...if I attempt ota I get 'failed to hab check boot'. When trying to boot into recovery I get 'failed to hab check recovery'.
Edit: could I just unlock and root to solve this problem? If so, would someone point me to a different method than the Moto Toolkit found here? It doesn't recognize my moto even though all drivers and Motorola Device Manager are installed.
Sent from my XT1053 using Tapatalk
Ota KitKat update?
What phone do you have?
I have the T Mobile motomaker. Solved the problem with RSD Lite and factory Kit Kat images.
Sent from my Galaxy Nexus using Tapatalk
How to repair my bricked moto x xt 1052
Hi everybody...
Im new here.
I hope someone resolve it.
My moto x xt 1052 is bricked, means it is not powerup normally, no any screen displayed, no boot image, boot animation, but goes into fastboot mode sometimes on trying to go in it using hardware key pressing i.e. Power and volume down keys.
Here is the brief description what was happened......
My moto was on stock kitkat 4.4.4 for upgrading it to lollipop On 19th jan i was tried to flash cm12 over cm11 nightly as described in that thread , for that i was unlocked my bootloader, rooted it, flashed CWM touch recovery, flashed superSu zip file and flashed cm12 nightly over cm11 as described. But my device was stucked at boot logo. For resolving that issue i was flashed boot.img of prev nightly release(i.e. 1/15) through command promp using commands '' cd Downloads... cd fastboot... fastboot flash boot boot.img.
It flashesh image file successfully and device is booted successfully. I was used it till last 4days and regularly updated cm12 nightly via cmupdater.
But 4days back i was tried to remove warning message of device is ulocked bootloaded which was irritated me using same flash method and logo.bin files which was given in another thread by other members. But my BOOTLOADER IS DAMAGED and no any display was seen. I read many threads to repair it but no anyone give easy step by step guide. I was tried to repair it using motoflasher given in 1 thred. But as shown there no my device was not shown in device manager asQUSB****9** THERE is only adb interface in device manager. Also it says in motoflasher that no device was connected and output was incorrect COM port, which was refused to flash bootloader. Another thred of rescurrection of bootloader is not so easy and also download links are not useful,shows item was removed.
There is no another way, i thought bootloader is a kernel, so i was flashed zwiel kernel by same flashing method by cmd.
The problem remaims same, moto care told thay it will cost 6k for repairong which is too high. The descreltion is given in details for anyone who finds my mistakes and tell me angd give me suggestion. Xda is big deveopers forum, i know someone will help me.. So plzzz help me.
HOW CAN I REPAIR MY BOOTLOADER AND SAVE MY MOTO which will not useful then usable as a paperweight.
Have you tried to simply re flash your stock 4.4.4 firmware via fastboot since you say you can get into fastboot mode? Or rsd your 4.4.4 firmware. If you can get into fastboot mode I think you should be able to fastboot your stock 4.4.4 and be back up and running.
When in fastboot mode and phone plugged in and you type "fastboot devices" does it display a string of numbers for your device? If yes then you are good to go.
I am having a similar issue with a Sprint Moto X (1st Gen). I am able to get to fastboot mode and I have flashed the stock image for 4.4.4 using mfastboot (also re-did it using RSD lite as the boot.img gave errors using mfastboot) but the phone only still boots to a dark screen and vibrates roughly every 15 seconds.
Anyone have an idea on what else I can try? I've been scouring the boards and youtube, but haven't really come across anything on this type of issue.
Has been RDS flashing process totally completed without any errors?
The flash finishes with no errors when it goes to reboot the phone I end up at the same spot of a black screen that vibrates like its powering on then repeats every 15 seconds like its stick in a loop. Odd... I never get the smallest hint to a picture on the screen.
chousue said:
The flash finishes with no errors when it goes to reboot the phone I end up at the same spot of a black screen that vibrates like its powering on then repeats every 15 seconds like its stick in a loop. Odd... I never get the smallest hint to a picture on the screen.
Click to expand...
Click to collapse
Your symptom I'm quoting is what I've seen when a bad logo.bin has been flashed to the phone.
Can you try another? Some are in http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395
Thanks for the suggestion.
I tried a dew different logos but the end result is still the same. Vibrates on power up, no display at all and repeats until I hold the volume down and count to like 10 when the next buzz cycle would happen so I can get into fastboot mode again. I should note that I can't see anything in this screen as well. I was starting to wonder if it was the screen that was the issue but the bootloop has me thinking otherwise.
I have another one with a bad screen and a replacement is on the way. I guess I can test it on this one as well but I'm sure the result will be the same.
I took a gamble on this one thinking I could bring i back to life, I figured the last owner just soft bricked it and flashing the latest stock would override what mess they did. I'll tinker around some more if there are some other options otherwise I can just flip it for parts i guess.
If I run the fastboot getvar all I get all the phone info so it gives me hope that something can be done, I just don't know what, it seems like I keep cycling through the same few processes hoping for a different result. I even tried the power + Volume down for two minutes thing that's supposed to bring up the "other" recovery menu, but with no display, i don't know what happening.
In a last ditch effort I did a tear down and connection check for all the parts so everything has been removed and firmly re-attached, certainly was nice to do that there instead of on the one I know will work once I replace the screen, but it sucks to still come up empty handed. Sorry for the long rant, it's just been a long few days of trying to find ways to bring this phone back to life.
Solved with downgrading
Sorry for bad english.
I had same issue.
But solved prev saturday hole day.
Using manual method instead of rsd.
Make sure u properly installed adb and mfastboot. For that open cmd and type adb. It shows command lines and then mfastboot. It also shows command lines then you are ready to go. If not, google it for how to install adb and also for mFastboot
Then download proper stock firmware for ur device. unzip it, u will get files of system, boot etc. Copy all this files and paste into mfastboot folder. Open command prompt in that folder by pressing shift and right key of mouse.
Then boot your moto into fastboot mode by pressing power and volume down key for a seconds. If u will not get in to fastboot mode try for many times unless u get it. I will get it after trying half hour.
Connect ur device to pc and run commans given in the following link. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
End with-- fastboot adb reboot. It will reboot ur device.
Enjoy.
Thanks for the steps, I feel like I have done that already save for the few end steps with the oem commands.
So I flashed the print image using that guide and it still vibrates every 15 seconds and no display. I grabbed the retail file from the motorola site (oddly enough they only have TMO on the file name for some reason) and I flash this and it doesn't vibrate every 15 seconds, but still no display... Maybe in the end the display is bad after all...
Like mentioned before, I already have one coming in black for the one that works for sure...so I guess I'll test it on this one as well. Just wish it was as easy to disconnect/connect as my Nokia Lumia was, that took less than 10 minutes!
So, in the end it was the display afterall. I ended up getting another replacement screen as I really did not feel like attaching it and detaching it (yeah, I'm lazy sometimes). After setting up the new screen I plugged it in to charger and what do you know, battery at 0% then the motorola bootloader unlock screen after 5 or so minutes.
Now I have two phones, lol. One screen came without the speaker on the to fro some reason... And I think I just messed up my main phone removing the frame to add in that piece so lint and such doesn't get into the phone so easily... Dang it!
Edit - Yep, now it has a nice rainbow line display across the bottom where the navigate soft button would be... Guess I have to get one more screen!
could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app
sadik2112009 said:
could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
Go to the General Forum there's a dedicated thread with official roms for your particular model. Use download the ROM and flash through rsdlite. Always make a backup since it will wipe your internal storage clean.
Sent from my XT1058 using Tapatalk
sadik2112009 said:
could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
If you installed 5.1 by using one of the TWRP backups, and did NOT flash the leaked OTA zip files, then you should have only touched /system and /boot partitions.. in that case, it would be safe to flash 4.4.4.
thank u so muchh......
KidJoe said:
Your symptom I'm quoting is what I've seen when a bad logo.bin has been flashed to the phone.
Can you try another? Some are in http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395
Click to expand...
Click to collapse
thank you so much... this post saved my moto x...... i am facing this issue from last 15 days. so many pages visited but nothing help, but, after doing this it rebooted. may god bless you!:angel::angel::angel::angel:
Having same problem.
Please help if anyone can!
I can't resolve it by Fastboot in cmd.
I also tried typing mfastboot in all commands.
Having same problem.
Please help if anyone can!
I can't resolve it by Fastboot in cmd.
dont display anything
not charging not boot not start anything
Travisdroidx2 said:
Have you tried to simply re flash your stock 4.4.4 firmware via fastboot since you say you can get into fastboot mode? Or rsd your 4.4.4 firmware. If you can get into fastboot mode I think you should be able to fastboot your stock 4.4.4 and be back up and running.
When in fastboot mode and phone plugged in and you type "fastboot devices" does it display a string of numbers for your device? If yes then you are good to go.
Click to expand...
Click to collapse
I have a moto x of my friend xt1053, dont not what he has done with it.
but
it is in Encryption Unsuccessful Condition.
When I connect to pc. Windows show that motorola xt1053 is connected. device manager shows MTP device under portable devices.
Mototrola USB drivers have been installed successfully.
I can not boot xt1053 into fastboot mode or recovery. Neither by adb/fastboot nor by buttons. (volume down + Power).
adb devices command does not show any numbers as it normally does when device is connected.
how get it back to working condition. any expert to help or happen to be in the same boat?
Hello everyone, just get frustrated right now my brand new 5X Half-Bricked after trying to flash stock fastboot firmware of the A1 through EDL with mi flash. just over excited of this devices, as i'm not a new one on this stuff and things, so that i ignoring some post said that the mi A1 rom won't run/boot compatible with 5X. (some interesting post right here about 3 Variants Hacked Bootloader http://en.miui.com/thread-840402-1-1.html)
I put whole things needed togather (fastboot firmware of A1, and Mi5X, also Twrp and some of unbrick zip from the thread above) so i was thinking when everythings gone crazy and bad i just need to reverting back to stock fastboot firmware of MI5X and everything works fine.
i do backup my QCN file so the worst thing i losted the imei and baseband i just need to restore that backup. Then i start the stupid things with proud.
flashing the Mi A1 sucessfully without any error on mi-flash then power it on boom, as i predicted it won't be as easier and simple as that step. some error text appeared on my screen some related to bootloader things, okay i just go into fastboot and unlocking with type "fastboot oem unlock" done with success and thats also said in terminal. okay then i rebooted (no panic at all), so the warning text still, then appeared your system has been destroyed, okay than i put the mi A1 recovery and flashing that through the fastboot, its said error no such partitions "recovery"??? (bit panic here) but trying to type "fastboot boot tissot.img" (tissot the codename of A1) its boot and send me into recovery, flashing some A1 rom for 5X from xda still won't boot at all (start panic here ).
so everything i try here flashing stock miui also won;t even boot and see the homescreen. I give up and OK i just need to flash the stock 5X through EDL, rebooting to edl and then flashing the stock 5X and success flashing done without any error, so i rebooted but its only stuck at MI logo then restart itself (really PANIC), so i get into recovery (stock MIUI) and mybe wiping whole data and cache will help, but there's no changes still restart/rebooting itself , okay i need to flash again this time i downloding Develover versions, and put the devices into edl through test point this time (as now the bootloader are relocked after flashing the stock one).
after flasing done the device still won't even boot at all just stuck at MI logo, now i really need help anyone any advices will really help, thanks
SH1M4BD3 said:
Hello everyone, just get frustrated right now my brand new 5X Half-Bricked after trying to flash stock fastboot firmware of the A1 through EDL with mi flash. just over excited of this devices, as i'm not a new one on this stuff and things, so that i ignoring some post said that the mi A1 rom won't run/boot compatible with 5X. (some interesting post right here about 3 Variants Hacked Bootloader http://en.miui.com/thread-840402-1-1.html)
I put whole things needed togather (fastboot firmware of A1, and Mi5X, also Twrp and some of unbrick zip from the thread above) so i was thinking when everythings gone crazy and bad i just need to reverting back to stock fastboot firmware of MI5X and everything works fine.
i do backup my QCN file so the worst thing i losted the imei and baseband i just need to restore that backup. Then i start the stupid things with proud.
flashing the Mi A1 sucessfully without any error on mi-flash then power it on boom, as i predicted it won't be as easier and simple as that step. some error text appeared on my screen some related to bootloader things, okay i just go into fastboot and unlocking with type "fastboot oem unlock" done with success and thats also said in terminal. okay then i rebooted (no panic at all), so the warning text still, then appeared your system has been destroyed, okay than i put the mi A1 recovery and flashing that through the fastboot, its said error no such partitions "recovery"??? (bit panic here) but trying to type "fastboot boot tissot.img" (tissot the codename of A1) its boot and send me into recovery, flashing some A1 rom for 5X from xda still won't boot at all (start panic here ).
so everything i try here flashing stock miui also won;t even boot and see the homescreen. I give up and OK i just need to flash the stock 5X through EDL, rebooting to edl and then flashing the stock 5X and success flashing done without any error, so i rebooted but its only stuck at MI logo then restart itself (really PANIC), so i get into recovery (stock MIUI) and mybe wiping whole data and cache will help, but there's no changes still restart/rebooting itself , okay i need to flash again this time i downloding Develover versions, and put the devices into edl through test point this time (as now the bootloader are relocked after flashing the stock one).
after flasing done the device still won't even boot at all just stuck at MI logo, now i really need help anyone any advices will really help, thanks
Click to expand...
Click to collapse
I think you should not unlock the bootloader using the command fast boot OEM unlock,you should go to http://en.miui.com/unlock/ here and download the app to unlock it, and when you flash a new rom which is not miui,you must keep it unlock,do not fastboot OEM lock,that will cause it can not go into system and stuck in logo
linjike said:
I think you should not unlock the bootloader using the command fast boot OEM unlock,you should go to http://en.miui.com/unlock/ here and download the app to unlock it, and when you flash a new rom which is not miui,you must keep it unlock,do not fastboot OEM lock,that will cause it can not go into system and stuck in logo
Click to expand...
Click to collapse
Nope, that's the basic things and i really know how it works, As for now i''ve no ways to go / reach the homescreen at all, so i can't put my mi account in setting and linked the device into my acccount, its useless using the miunlock tools. And i can only do that commands right after i converted mine to A1 firmwares.
hi, finally, i know what problem you met, because i have met the same problem, the solution is ,you go to the fastboot ,first unlock the devices, then fastboot reboot,then you find you go to the system, then you go back to fastboot,and last ,you need to use the miflash to flash the rom,and it should work fine now,it seem when you are locked,the miflash can not really work
Last news, damn lucky bastard i'am got replaced units, lets see does we'll have some aosp goodies soon..
linjike said:
hi, finally, i know what problem you met, because i have met the same problem, the solution is ,you go to the fastboot ,first unlock the devices, then fastboot reboot,then you find you go to the system, then you go back to fastboot,and last ,you need to use the miflash to flash the rom,and it should work fine now,it seem when you are locked,the miflash can not really work
Click to expand...
Click to collapse
Hi, it happened to my mi note 3. But not able to unlock in fastboot or mi unlock tool (prompted me adb been blocked by other program) . It's good if you able to help me. Thanks in advance.
Sent from my Redmi Note 4 using Tapatalk
samgcw said:
Hi, it happened to my mi note 3. But not able to unlock in fastboot or mi unlock tool (prompted me adb been blocked by other program) . It's good if you able to help me. Thanks in advance.
Click to expand...
Click to collapse
Use the mi unlock tool ,you can only unlock the phone when you are in fastboot mode,,turn off the phone,press the power and volume down bottom simultaneously,and you will be in fastboot mode
I have a xiaomi mi a2 device which had bootloop all the time. I was not able to get into device at all. So in other words oem unlock and usb debugg was not active at all. I tried so many times to get into the phone just to activate those. Now since some other phones doesnt really need those to flash because they use different kind of flashing i asumed i wouldnt need those.
when i tried to flash using adb sideload which was available it couldnt flash it went to 47% and then it just failed or stopped with some message and 1.00x at the end. I did try couple of times without any luck. I was never awared that thus phone had project treble rom wich in turn have 2 partitions. I acted on impuls. Then i tried fastboot commands with error about failed not able to flash restriction. Then i found that you could flash using emergency download mode which is in my mind something lg has with shorting the pins. There you dont have any issues because emergency download mode in lg dont require any permission or any problem for you to make your degice alive again. You could do that how often you will.
now i assumed it was the same with mi a2 that it would write rom the same but automatically because in lg you need to flash particular files in order to make that method work. I did flash mi a2 in edl and it did flash but the result was catastrophic. I got message about some partition something while flashing was a success. Then i thought how can edl fail even if oem is locked. It shouldnt work like that. Then i tried and tried to unlick bootloader through fastboot but its impossible. From start it was impossible to activate those settings. Then now i figure it out that it must do something with project treble and those 2 partitions. Is there any way to make this phone alive again?? Is there any way to flash partitions and partitions table manually
P. S I flashed it with what i thought was the anwser about my problem. I flashed it with mi x6 recovery rom from xda which made whole situation worse. Now i dont even have adb option nor do i have option to roll back to stock.
Just for comparison, in google pixel phone you dont even need unlocked bootloader or anything for that matter to flash pixel phone as long the rom is stock rom. Adb sideload works flawlessly
Any help is appreciated