Related
UPDATE:
OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
so I received a new Nexus 6 device from T-Mobile for my girlfriend.
In our area unfortunately Wi-Fi calling is a must, so she went ahead and did both of the OTA updates. After doing the second update the phone was stuck optimizing apps, and then the screen wouldn't work...
So I then hooked the phone up to the PC and through ADB did the following commands
fastboot erase userdata
fastboot erase cache
That was supposedly the commands I had found on the internet to go ahead and factory reset the phone.
Now the phone is stuck at the balls swirling and it won't stop. Try and hold the power button down and the phone just restarts itself, won't shut down so I can't even get back into the recovery.
I tried to first load up a factory image before doing something silly like that but when I tried to run the command "fasboot oem unlock" it says I need to enable developer options in Android... which I couldn't get to anyways...
Can someone please help with this issue. Her old phone got stolen and now she has this one which is completely messed up.
Thank you for anyone who can help me!
none
You have to hold power and down on the bottom button, or since you have adb, you can do "adb reboot recovery". Push volume down first then power. After that you can enable MTP and toss a rom on the phone. Do a complete wipe with the exception of the internal storage ( I did storage one time accidentally, yuk) flash a ROM and you should be good
I can't even turn off the device at this point.... It is just stuck at the balls spinning and won't go any further.
When trying to shut the phone off the power button just restarts the phone, doesn't shut it down. Not sure what is going on.....
jwleonhart said:
I can't even turn off the device at this point.... It is just stuck at the balls spinning and won't go any further.
When trying to shut the phone off the power button just restarts the phone, doesn't shut it down. Not sure what is going on.....
Click to expand...
Click to collapse
It should shut down if hold the power button long enough. Takes like 20 seconds or so.
OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
jwleonhart said:
OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
Click to expand...
Click to collapse
As far as I know with stock recovery about all you can do is try to format cache and try to factory reset again. Otherwise will have to take back to T-Mobile and RMA. Make them update it. Lot of OTA updates have been failing.
I'm just curious to know if there is someway. Maybe I can force TWRP recovery or something like that on the phone by at least getting in the bootloader... There is a fix for bricking if it is like that.
Why the bootloader just doesn't come unlocked I will not understand. It would prevent motorola from having a heap of useless devices, as i'm sure probably even motorola themselves cannot fix the device.
Seems like a whole pile of sh*t if you ask me.
Anyone have any ideas? Worst part is T-Mobile won't ship a phone over the weekend either, so thats just 3 more days without a phone which is just wonderful.
jwleonhart said:
I'm just curious to know if there is someway. Maybe I can force TWRP recovery or something like that on the phone by at least getting in the bootloader... There is a fix for bricking if it is like that.
Why the bootloader just doesn't come unlocked I will not understand. It would prevent motorola from having a heap of useless devices, as i'm sure probably even motorola themselves cannot fix the device.
Seems like a whole pile of sh*t if you ask me.
Anyone have any ideas? Worst part is T-Mobile won't ship a phone over the weekend either, so thats just 3 more days without a phone which is just wonderful.
Click to expand...
Click to collapse
There is no way to flash a recovery without the bootloader unlocked. On these devices it is best to unlock bootloader first thing before trying to update so have some control if things go bad. Moto has the ability to reflash them like J-Tag. TMobile store may replace it.
Messed up part about T-Mobile is the fact this was an exchange for a stolen phone. They actually waived the insurance fee of $175 and the tax on the phone... which was extremely nice of them since I still owed about $350 on the LG G3 my girlfriend had.
So since the exchange was done over the phone or I should say since the new handset would bought over the phone the store won't replace it... it's weird they operate that way because the store should be able to replace anything that is sold via phone or internet and vice versa.
jwleonhart said:
Messed up part about T-Mobile is the fact this was an exchange for a stolen phone. They actually waived the insurance fee of $175 and the tax on the phone... which was extremely nice of them since I still owed about $350 on the LG G3 my girlfriend had.
So since the exchange was done over the phone or I should say since the new handset would bought over the phone the store won't replace it... it's weird they operate that way because the store should be able to replace anything that is sold via phone or internet and vice versa.
Click to expand...
Click to collapse
Yea. It a bad situation. We have seen a lot of them choke on the OTA flash. Best to unlock upfront and fastboot the updated factory image. You are always safe once it is unlocked.
Still begs the question as to why they don't just unlock the bootloader from the factory to avoid all this crap. I mean imagine how much money and time they would save if they just did it? I completely forgot about unlocking the bootloader even because I figured hey just OTA it and be done.... remember it's my girlfriend so I wasn't going to put some ROM on there that might have something broken or whatever... can't believe this **** though.
jwleonhart said:
Still begs the question as to why they don't just unlock the bootloader from the factory to avoid all this crap. I mean imagine how much money and time they would save if they just did it? I completely forgot about unlocking the bootloader even because I figured hey just OTA it and be done.... remember it's my girlfriend so I wasn't going to put some ROM on there that might have something broken or whatever... can't believe this **** though.
Click to expand...
Click to collapse
I understand. They look at unlocked bootloader as a security problem. It even tells you it disabled security when you flip the unlock switch. From the many OTAs we have seen brick it is best to just unlock even if running stock. Once it is up and running can always relock. Do not relock if have custom recovery or kernel tho. It will more than likely bootloop. I tried it for grins but made sure the unlock option was enabled and was able to unlock and reflash. Many have flashed new software and relocked before first boot to find out it bootloops and can't unlock again. Best to have TWRP so that if is locked have a adb/MTP option. We pretty much discourage OTA. I haven't tried but have seen a post that says must be locked to OTA. If that is the case you always have the chance of a bad OTA flash and end up same place you are now. With TWRP there are also OTA files that have been converted to flashable zip and can be flashed in recovery.
So i successfully rooted my Moto G 2nd Gen using KingRoot. Not too long after i had finished downloading Adblocker, a messaged popped up saying i had to "reboot" the phone and that's exactly what i ended up doing. That's when the phone wouldn't boot
.........later, after a bit of research i had found that my phone was stuck in a bootloop.
So i took it to Wind (the company i'm with) and without knowing that the phone was rooted, they told me that they could fix it only if i bring the receipt. I purchased this phone on August 14, 2015, the one year warranty still stands. But the receipt was long gone. No receipt, no warranty service.
I went back to the store where i bought the phone....but they can't seem to pull up the receipt. They said because it's been almost a year since i bought the phone.
Anyways, i am here for help. The phone is in a bootloop and not only that but USB Debugging is not on (i believe). I don't remember turning it on. But i want you guys to understand that I AM A NEWBIE.
I also tried to Factory reset it from Recovery but that didn't help. Btw, since i did a factory reset is the phone still rooted? Isn't KingRoot supposed to be deleted from the factory reset?
One more thing, the phone is a Moto G 2nd Gen, Model: XT1064 (if that helps). :good:
Please Help.
After this i don't thing i will ever root another phone again.
You can try to flash your system with adb
Is your bootloader locked or unlocked?
If unlocked, you could easily recover your phone. If locked, first you'll need to unlock the bootloader.
Did the OP ever find a solution? If bootloader still locked you need to go onto Motorola website, (haven't checked if it's still active since Lenovo bought Motorola???) But if it is still active go on that website after doing search engine search for "how to unlock Motorola bootloader?" Once youre on the right page just follow the instructions. Being a noob I will assume you don't have adb or adb fastboot installed on your computer, great tool to have if you want to make your life easier when it comes to all things rooted. It will also help you to get the unlock code which you will need to unlock the bootloader of your phone, like I said do the search first, then follow the instructions in the tut. It's very noob friendly, good luck! Remember too you may need all the drivers for your specific model depending on whether you're on win, osx or Linux.
I have never had a phone that has caused headaches like this one!!!
I have a jeter xt1922-2 and for nearly a month now.....suffered problems galore..... Ill explain....so take a seat.....and listen
I unlocked the bootloader the official way, all went swimmingly, then i followed quiksilvers guide to twrp....etc
but suffered problems with the phone in a reboot loop....
so, i thought, as its early days, i will flash a stock rom (i could only find a ALIJETER image, which was the only firmware i could find.....
So i did all the fastboot commands but the bootloader.img and partition thing said fail (phone said BAD KEY) but phone booted, after encrypting......
so for a week or so, I disabled a lot of items, and used non-root adblocker......was enjoying using the phone...
after a bit more time....I thought i would do the ota.....well that installed, and funnily enough, my OEM locking in dev settings was usable again.....so i did that, and installed twrp and root (phone now saying N/A), and had the phone purring like a cat.....but.......
i started to see firmware images becoming available, including JETER firmware, so naturally i downloaded the only one for my region - the UK.... file name : JETER_RETAIL_8.0.0_OPP27.91-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
so i tried flashing, but after the same sort of errors as before, it booted into the blue moto screen, and stayed there...
I saw somewhere, that if you relocked bootloader, it should be okay.....
so i tried fastboot oem lock ......... it gave a lot of errors and didnt lock........so i read a few more forums
and was told to try 'fastboot flashing lock' ......... and it worked.....locked again! but when trying to flash anything it failed.....so i tried everything to unlock again, but spent 6 hours trying to sort it, no luck....so i went to bed....
this morning, i thought to myself.........try unlocking via the way i did before, get code from motorola, so did all that, still not unlocked, and thought i would try fastboot flashing unlock .... it unlocked again!!!
and that brings me to the present time.......
tried the jeter firmware.....still the same as before........
tried the original alijeter firmware as i first tried, it boots and works, albeit with the BAD KEY message.....
How did i get that OEM option NOT GREYED OUT in dev settings???
How can i get the OTA to update again, as when i try again, it downloads, but when updating, it goes straight to the BOOTLOADER ...... ?!?!?!
I just want the phone to get back to normal......working twrp, root....etc like i did have it....
Fellow Moto G6 play users....please help a old man!!!!
biggary said:
I have never had a phone that has caused headaches like this one!!!
I have a jeter xt1922-2 and for nearly a month now.....suffered problems galore..... Ill explain....so take a seat.....and listen
I unlocked the bootloader the official way, all went swimmingly, then i followed quiksilvers guide to twrp....etc
but suffered problems with the phone in a reboot loop....
so, i thought, as its early days, i will flash a stock rom (i could only find a ALIJETER image, which was the only firmware i could find.....
So i did all the fastboot commands but the bootloader.img and partition thing said fail (phone said BAD KEY) but phone booted, after encrypting......
so for a week or so, I disabled a lot of items, and used non-root adblocker......was enjoying using the phone...
after a bit more time....I thought i would do the ota.....well that installed, and funnily enough, my OEM locking in dev settings was usable again.....so i did that, and installed twrp and root (phone now saying N/A), and had the phone purring like a cat.....but.......
i started to see firmware images becoming available, including JETER firmware, so naturally i downloaded the only one for my region - the UK.... file name : JETER_RETAIL_8.0.0_OPP27.91-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
so i tried flashing, but after the same sort of errors as before, it booted into the blue moto screen, and stayed there...
I saw somewhere, that if you relocked bootloader, it should be okay.....
so i tried fastboot oem lock ......... it gave a lot of errors and didnt lock........so i read a few more forums
and was told to try 'fastboot flashing lock' ......... and it worked.....locked again! but when trying to flash anything it failed.....so i tried everything to unlock again, but spent 6 hours trying to sort it, no luck....so i went to bed....
this morning, i thought to myself.........try unlocking via the way i did before, get code from motorola, so did all that, still not unlocked, and thought i would try fastboot flashing unlock .... it unlocked again!!!
and that brings me to the present time.......
tried the jeter firmware.....still the same as before........
tried the original alijeter firmware as i first tried, it boots and works, albeit with the BAD KEY message.....
How did i get that OEM option NOT GREYED OUT in dev settings???
How can i get the OTA to update again, as when i try again, it downloads, but when updating, it goes straight to the BOOTLOADER ...... ?!?!?!
I just want the phone to get back to normal......working twrp, root....etc like i did have it....
Fellow Moto G6 play users....please help a old man!!!!
Click to expand...
Click to collapse
Bad key is on all Moto devices after you unlock the bootloader. Once you get rid of dmverity it should change to n/a. Don't know why you keep flashing things like that. Your lucky the bootloaders didn't flash.
Good day all. Long time lurker of these forums, and I am officially throwing in the towel on my amateur attempts to update my P20 Pro (CLT-L29 C636) from Android 8 to something newer. I've managed to soft brick the thing, getting stuck in a boot loop. I can get to fastboot, and I can (sometimes) get it to enter dload mode with an OTG cable and a thumb drive. I messed something up early on in the process and I am completely unable to go any further. Dload gets to 5% then fails every time, with every thumb drive I've used.
I am willing to accept that I just don't have the technical ability to take this journey any further. Being that I live in the US (Western New York), Huawei lists no official repair centers in the states. Are there any trusted 3rd party repair services I could send my phone to and have an expert attempt to repair the software? At this point it's been bootlooping so long the Huawei logo is ghosted onto the AMOLED screen. I would love to have this phone operational again.
Any thoughts I would greatly appreciate it!
Hold Both Vol + Power until Emergency Rescue pops up.
After that, restore Stock, unlock Bootloader, install any android 10/11/12 GSI u want.
Tried that. It's stuck in bootloop and only occasionally responds to boot prompts. On the couple of times it got past dload failed and prompted me with invalid install and offered to boot to Emergency Recovery, it fails to load the recovery dialog and drops back into a boot loop.
I promise, I have been back and forth with attempts on this phone for four months, and if I thought there was any new surface level tip or trick I haven't tried, I would still be searching. I feel like it's at a point where only specialized software or a physical test point, or something else beyond my technical ability will fix this phone.
I do appreciate the suggestion, though.
Unlocked Phone? So it *might* be possible to recover i imagine if u get twrp running, might need some dirty work, but not impossible.
Edith did forget to mention; Can u see ur Phone via adb/fastboot on your PC?
aLcaTr4z said:
Unlocked Phone? So it *might* be possible to recover i imagine if u get twrp running, might need some dirty work, but not impossible.
Edith did forget to mention; Can u see ur Phone via adb/fastboot on your PC?
Click to expand...
Click to collapse
Sorry if I sent the wrong impression. The bootloader is still locked. It is only carrier unlocked.
I can locate it on DC-Unlocker on fastboot but it won't let me load any files to it.
With locked BL is not much hope left i guess. Hisuite Recovery fails too i imagine?
aLcaTr4z said:
With locked BL is not much hope left i guess. Hisuite Recovery fails too i imagine?
Click to expand...
Click to collapse
Oh yeah. HiSuite recovery states that this model isn't compatible with eRecovery and to take the phone to a service center.
I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldnât do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help
i think this vid will help
Greetings everyone. Sorry if I posted this in the wrong forum. Please move this in appropriate forum if I made a mistake. Believe me, for the last 7 days I have searched all of xda and internet, followed innumerable guides, FAQs and workarounds and none worked. So, as a last resort I am starting this thread
Device: Motorola Moto G5s Plus XT1804 ......4GB _64GB variant
Problem: 1) Baseband not found (unknown) Original Baseband: M8953_52.61.07.98R SANDERS_INDIADSDS_CUST
2) IMEI 0 (Sim cards are not detected).
I bought this refurbished phone about an week ago after my last LG went kaput. I was happy by the build quality of the phone. But it only ran Android 8.1 Oreo. So, I decided to put a custom ROM in it. I am not exactly a newbie to the world of CyanogenMods, Lineage OSes and Pixel Experiences. Or, so I thought. Anyways, after a lot of searching I finally decided on Dot OS 5.2 Official Android 11 version. The ROM looked very pleasing and the reviews looked positive. So, I got the unlock key from Motorola website, unlocked the bootloader, put in official TWRP recovery in it. Everything went like a breeze and in all that excitement I forgot to take a backup of the persist, efs and other partitions. A very costly mistake it seems. DotOS booted fine and looked really fresh till I found that there is a small cross near the SIM card network signal triangle up righthand side corner and the signal is only LTE and not VOLTE. I was using a Vodafone Sim card at the time. Although VOLTE option was enabled in SIM settings. To confirm my doubts regarding VOLTE I switched to a JIO Simcard and alas I was not able to make a call without redirecting through the horrid JIO calling app. VOLTE was indeed not working. So, I looked up for a fix and I found a Volte ZIP file from here https://www.google.com/url?sa=t&sou...0QFnoECBAQAQ&usg=AOvVaw0YgJvCjQWXXV8WQSJkxBOK . This was the starting of my troubles. I flashed the universal VOLTE fix zip from TWRP and it flashed fine. On rebooting, I found to my shock that my phone was not turning on. I pressed and held the power key and there was no sign of life. I couldnât go to the fastboot bootloader or recovery. Only the white led blinked at the top when connected to the charger. My phone was apparently hard bricked. I searched frantically for a solution in this forum and YouTube wherein I found that one can bring it back to life by doing a blankflash. Found the blankflash file here https://www.google.com/url?sa=t&sou...wQFnoECAsQAQ&usg=AOvVaw1eVdBWGVFr8aiqLdP-ZkeT followed the instructions and it flashed my bricked device back to fastboot. I was relieved for a moment but the next I found that the Bootloader version has downgraded from BL C2 07 to BL C0 05. I knew something was wrong as bootloader downgrade shouldn't be possible. Also the unlock and rooted status were also lost and the baseband was unknown at this point. Anyways the device was recognised as a fastboot device and I tried to flash the stock ROM latest version using the fastboot. But, only then I realised there was something wrong with the bootloader. It gave errors like security downgrade, permission denied, preflash validation failed, remote command failed. At this point I was truly confused and worried. Why would it think the latest bootloader to be a security downgrade to a supposedly old bootloader and prevent me from flashing it. However it did flash the other files like gpt.bin for partition, oem.img, boot.img, system.img sparsechunks and everything else. I booted back to Android 8.1 Oreo and everything seemed working except my IMEI now read zero and my Simcard was not recognised by the device. After that I again unlocked my bootloader. Somehow the original unlock key worked and the bootloader screen said flashing unlocked but the bootloader didn't behave like an unlocked bootloader. The TWRP installed fine but couldnât install the latest Pixel Experience. The flash screen said PE 11 was for Sanders and my device is (blank no name). I tried both the normal and plus and both behaved similarly. Lineage OS unofficial builds behaved similarly. I again tried Dot OS and Arrow OS and both installed fine except there was no signal. For a moment I tried to forget about the bootloader but concentrated on recovering my IMEI and Baseband but I couldnât. For nearly 5 days I tried different guides including a detailed guide using Validus Sanders ROM but none worked. My EFS folder has files around 12 megabytes but my Persist seems deleted at zero bytes. The IMEI keeps changing between null, zero and unknown depending on the 20 something ROMs I tasted on this device. At this point, I am at a loss. This was to be my main phone and I am financially crunched. I can't buy another phone right now. I think that blankflash bootloader is corrupted and it is giving me permission denied errors. Even Magisk won't work properly. I even tried using the official rescue and smart assistant tool by Lenovo and it failed at 47 percent. I tried in different computers and Win7 to Win 11 OSes but it was of no use. I also tried getting a QCN file but I couldnât get one for the device to recover the IMEI. Please suggest something if anyone of you can save this poor device of mine. Thanks in advance
Raghaov said:
i think this vid will help
Click to expand...
Click to collapse
Thanks for the quick reply but my phone is soft bricked now. It was hardbricked and I uses a faulty blankflash bootloader to bring it back to life. My device is softbricked now. I have lost my baseband and I have no IMEI. I cannot take calls and no mobile data. Can you show me a way to go to edl mode in my device. Thanks again.
can your phone turn on if yes can you root it with magisk
if yes then pls tell me i will tell you
I can do everything except calling and mobile data. Yes, I have rooted with Magisk and have root access. But my baseband is unknown and my IMEI is showing zero. I can't call or access mobile data. Although I can use wifi
I have tried what is shown in this video already. Didn't work
I think the blank flash bootloader was corrupt or of a different region.
so go to magisk manager and on top-right corner you will see setting click the button right next to it and click on reboot to edl
I didn't even knew that. Trying asap. Will update
Doesnât work. Reboots back to system.
Updated Magisk to latest and tried both edl and download mode like you said brother. Everytime boots back to system. Am I missing something. The phone was not connected to the PC at the time
I am on stock Oreo now. Rooted and twrp installed
An interesting observation while installing Xposed, it gave an error that the device is not rooted properly
I have an untouched dump file for my model. The whole thing. Could you please guide me how I can restore my smartphone from that.
can you flash it through adb sideload fastboot twrp etc
I don't know but I sold the device. I bought a new one. Thanks @Raggaov for the help.
you're welcome