Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
08G8V8 said:
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
Click to expand...
Click to collapse
First, Status code 3 is normal - that indicates an unlocked bootloader.
You should be able to use the 4.4.4 FXZ to flash back to 100% stock. Afterwards, you can flash TWRP, and re-root. Use the latest TWRP from here: http://techerrata.com/browse/twrp2/ghost
The important thing about TWRP is that immediately after flashing it, you have to "fastboot reboot-bootloader" and immediately boot into recovery - otherwise it doesn't 'stick'. We don't know why, but as long as you do it that way, you will be fine.
Here is the link for the 4.4.4 FXZ: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you follow the instructions, you will be on stock, rooted 4.4.4 in less than 20 minutes.
Good Luck, and let me know if you need additional assistance :good:
Also, please remember to post your questions to Q&A - not General. Don't worry as I have already requested that the Mods move it to the appropriate sub-forum.
EDIT: The problem I see with "rootjunky"s video is that first, he advises that "Status code 1" is required to flash recovery -- this is incorrect. Status code 3 works fine for custom recovery.
Additionally, he did not "fastboot reboot-bootloader" before booting into recovery. This is necessary. I'm not sure why he left that step out....likely he already had custom recovery flashed when he made the video.
Thanks for the quick response. Sorry about posting in the wrong section. I should have known better.....
I will look at this, but probably won't do it until after work tomorrow. I will post back tomorrow, hopefully with success.
Thanks!
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
08G8V8 said:
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
Click to expand...
Click to collapse
Either will work fine. If you don't care about keeping your data, you can use RSD Lite (will wipe everything). If you use one of the tools in the thread I linked you to, make absolutely sure you follow the instructions -- you can't have any spaces in any folder-names. If you use RSD Lite, you just select the zip file and flash (no worries about directory structure).
Ok, I just assumed those were the methods to flash it. I will look into the RSD Lite method, as if don't mind wiping the data.
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
08G8V8 said:
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
Click to expand...
Click to collapse
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
samwathegreat said:
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
Click to expand...
Click to collapse
Sorry, the "adb reboot bootloader" sends me into the bootloop.
I hadn't tried the "fastboot reboot bootloader" or "fastboot reboot-bootloader". Now when I try that, with USB debugging checked I just get "<waiting for device>" It does nothing.
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Travisdroidx2 said:
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
Click to expand...
Click to collapse
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
08G8V8 said:
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
Click to expand...
Click to collapse
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Once you are in the boot loader screen does "fastboot devices" recognize your device?
samwathegreat said:
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Click to expand...
Click to collapse
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
samwathegreat said:
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Click to expand...
Click to collapse
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Travisdroidx2 said:
Once you are in the boot loader screen does "fastboot devices" recognize your device?
Click to expand...
Click to collapse
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
08G8V8 said:
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Click to expand...
Click to collapse
OK, glad you didn't flash to bootloader. That is tricky to fix...but I've dealt with people who have done it before.
Try another PC...or re-install the drivers. Also, DO NOT use a usb 3.0 port, always use 2.0.
Bootloader = AP fastboot mode. They are one and the same. Try to get it recognized with "fastboot devices", on any PC. If you can get to that point, you can flash back to stock and recover everything. The FXZ can actually FIX a corrupted or damaged filesystem. It replaces all the relevant partitions.
Remember you do NOT use adb or usb debugging. They have nothing to do with fastboot.
---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------
08G8V8 said:
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
Click to expand...
Click to collapse
YES!!!!
It seems you were confusing adb and fastboot. As long as "fastboot devices" recognizes your device, SO WILL RSD LITE!!!
Now follow my initial instrucitons, and you will be up and running in no time...
Thanks guys! I am going to do this tomorrow, but I feel pretty good that it is going to work.
Yes, I got VERY confused, and definitely need to go study up some more. I thought I had it, but obviously not.
Will report back tomorrow.
Happy to help
Absolutely get the Dev Edition for the same price. While Safestrap is out for other Galaxy devices with locked bootloaders (not sure if the S5 got SS yet) it allows customs Roms....but not kernel changes. With a Dev edition, there may be less development, but I'm sure there will still be some development out there.
Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic
So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
As far as I know the only fix is the one in that link but it does require custom recovery. I'm assuming the fastboot boot command doesn't work when locked but I've never tried, if it does then you could temp boot into twrp. Worth a shot I guess.
Hindsight's 20/20 but NEVER touch anything other than your data or cache partition with a locked bootloader. Google's security jump with lollipop has caused nothing but havoc for us.
ChaosDr0id said:
So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
Click to expand...
Click to collapse
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
or, you can grab the factory image of whatever version of android that you were on, "unzip" it, grab the system.img, and flash it via fastboot. its the same thing as if was a "custom recovery", youre just reflashing the rom, and wont lose your data
first thing id do is flash a custom recovery and unlock my bootloader, and make a backup in recovery.
AlkaliV2 said:
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
Click to expand...
Click to collapse
Hi, thanks for the reply.
It says
'device info' is not a supported oem command. See fastboot oem help.
FAILED <remote failure>
However I'm fairly certain the bootloader is still locked as I was unable to flash TWRP, or a stock image of android, as it tells me to unlock before doing those things.
AFAIK when you have this problem together with a stock recovery and a locked bootloader means bricked. >repair
Your bootloader is lock and you can't boot android to enable OEM unlock to unlock it. You have ruined your phone and there is no known fix.
RMA time for you.
Literally no solution unless you can invent one on your own.
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
yes
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc?
Click to expand...
Click to collapse
Absolutely. Otherwise anybody with a notebook could swipe your phone, download everything you've got on it, then return it without you knowing, and that would mean more nekkid selfies on reddit.
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
The entire concept of a locked bootloader is that you can't flash images through it.
Hey guys, I have a problem here. I unlocked the phone, flashed with twrp 3.01 and supersu. Then I installed Resurrection remix, flashed twrp 4.0.1 and supersu again. My phone works, but always had the initial screen "dm-verity". So I searched about it, and I figured out I have to go to bootloader and enter 2 commands. Now, when I enter in cmd and type "adb devices" while op3t in bootloader, my phone is not recognized. (0 devices found). Instead, when in twrp -> advanced-> adb sideload, my phone is listed with serial number. How can I make my phone recognisible by Windows while in bootloader mode, so that I can enter the 2 commands and get rid of dm-verity message? Everything inside the phone and the rom itself work perfect.! Also, when I go to settings/developer, I'm not able to change "oem unlock", it stays forced on OFF... Is that normal? Thank you very much in advance.
Magic Tmac1 said:
Hey guys, I have a problem here. I unlocked the phone, flashed with twrp 3.01 and supersu. Then I installed Resurrection remix, flashed twrp 4.0.1 and supersu again. My phone works, but always had the initial screen "dm-verity". So I searched about it, and I figured out I have to go to bootloader and enter 2 commands. Now, when I enter in cmd and type "adb devices" while op3t in bootloader, my phone is not recognized. (0 devices found). Instead, when in twrp -> advanced-> adb sideload, my phone is listed with serial number. How can I make my phone recognisible by Windows while in bootloader mode, so that I can enter the 2 commands and get rid of dm-verity message? Everything inside the phone and the rom itself work perfect.! Also, when I go to settings/developer, I'm not able to change "oem unlock", it stays forced on OFF... Is that normal? Thank you very much in advance.
Click to expand...
Click to collapse
Did you installed the drivers? I had the same issue and I installed the OP3T USB drivers afterward it shows me the device.
Yes I did. But I can also reinstall them, can you please provide me the driver's link which fixed the same problem? Thanks
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.
try the "fastboot continue" command
dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not