Hello!
The Poco M3 of my aunt was and still is not rooted and the bootloader was never unlocked. After powering the device off over night, it now does not boot to the system anymore but to "POCO-Recovery 3.0", offering
Reboot
Wipe Data
Connect with MIAssistant
When we select 1. Reboot, it offers:
Reboot to System
Back to Main Menu
When we select 1. Reboot to System, the Poco M3 reboots back to its Recovery screen. Pressing and holding Volume-Up + Power or Volume-Down + Power for a while and/or releasing one of the buttons (we tried all combinations), does not help, as it always comes back to its Recovery screen, so we are stuck.
We did not do any "special" things like rooting or unlocking the boatloader (as written at the beginning), nor are we aware of a recent system OTA update, but maybe she simply did not observe or rembers it (if it happened). She told me that she powered the Poco M3 off because it was getting a bit slow and she read that powering it off might help. So much for that. As we discussed all this over another phone (I am not at her place), I currently cannot connect her phone to my PC via USB and thus cannot try anything in this regard. I am not sure if that could help anyway, though.
I would like to avoid registering with Xiaomi for an account only for being able to reflash the device. Likewise, I do not want to unlock the bootloader or even root the device, unless these are necessary options, of course.
Do you guys have any helpful hints we could follow-up with? Thank you so much for your help!
7wells said:
Hello!
The Poco M3 of my aunt was and still is not rooted and the bootloader was never unlocked. After powering the device off over night, it now does not boot to the system anymore but to "POCO-Recovery 3.0", offering
Reboot
Wipe Data
Connect with MIAssistant
When we select 1. Reboot, it offers:
Reboot to System
Back to Main Menu
When we select 1. Reboot to System, the Poco M3 reboots back to its Recovery screen. Pressing and holding Volume-Up + Power or Volume-Down + Power for a while and/or releasing one of the buttons (we tried all combinations), does not help, as it always comes back to its Recovery screen, so we are stuck.
We did not do any "special" things like rooting or unlocking the boatloader (as written at the beginning), nor are we aware of a recent system OTA update, but maybe she simply did not observe or rembers it (if it happened). She told me that she powered the Poco M3 off because it was getting a bit slow and she read that powering it off might help. So much for that. As we discussed all this over another phone (I am not at her place), I currently cannot connect her phone to my PC via USB and thus cannot try anything in this regard. I am not sure if that could help anyway, though.
I would like to avoid registering with Xiaomi for an account only for being able to reflash the device. Likewise, I do not want to unlock the bootloader or even root the device, unless these are necessary options, of course.
Do you guys have any helpful hints we could follow-up with? Thank you so much for your help!
Click to expand...
Click to collapse
If the bootloader is not unlocked, this is a problem.
@rotoko
Well, it was a new device bought from a serious seller, and we have not unlocked it.
Could it be that it is unlocked nevertheless?
And if it is not unlocked, why is it a problem? And what could I do now?
Thank you!
7wells said:
@rotoko
Well, it was a new device bought from a serious seller, and we have not unlocked it.
Could it be that it is unlocked nevertheless?
And if it is not unlocked, why is it a problem? And what could I do now?
Thank you!
Click to expand...
Click to collapse
The problem is that when the bootloader is locked, you do not install a new rom via fastboot.
@rotoko
So can I only solve the problem by wiping and then hopefully being able to boot into system and then to unlock the bootloader?
With an unlocked bootloader, at least in the future it would make live a bit easier, right?
But what else can I do when after wiping, she still cannot boot her M3 into system? Going to a service point or contacting the seller? Or are there any other options?
BTW, is it possible to save some files from that device by connecting it to a PC (via ADB)? I am not sure if these are all encrypted.
7wells said:
@rotoko
So can I only solve the problem by wiping and then hopefully being able to boot into system and then to unlock the bootloader?
With an unlocked bootloader, at least in the future it would make live a bit easier, right?
But what else can I do when after wiping, she still cannot boot her M3 into system? Going to a service point or contacting the seller? Or are there any other options?
BTW, is it possible to save some files from that device by connecting it to a PC (via ADB)? I am not sure if these are all encrypted.
Click to expand...
Click to collapse
The system will probably no longer boot and nothing can be done without the bootloader unlocked, all that remains is to find an authorized service where they are equipped for it.
rotoko said:
The system will probably no longer boot and nothing can be done without the bootloader unlocked, all that remains is to find an authorized service where they are equipped for it.
Click to expand...
Click to collapse
Your aunt probably canceled aktualict the system, which is wrong.
@rotoko
You mean she wiped system? Well, I do not know if she did, but how could a stock recovery let system wiped?
Anyway, I hope we still can do some kind of factory reset.
Related
Hi there !
I just switched from a Windows Phone to a Huawei P9 Lite (VNS-L31), my first Android phone (never too late, I guess?).
I was following the instructions provided in this toolkit (https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873) to unlock the dual SIM support, as this phone is from Orange and locked to single SIM.
I successfully unlocked the bootloader, installed TWRP and rooted the phone. I got to the stage when updating the phone from the SD card is requested. Stock firmware was L31C109B120, new firmware is L31C432B130.
The update seemed to progress well, but actually no, as the phone is now bricked (black screen, screen will not power on, does not display anything).
Powering the phone with any combination of Vol+, Vol- and Power depressed results in nothing at all.
So I installed adb + fastboot and at least the phone is recognized in fastboot. I successfully unlocked the bootloader (again?) within fastboot with my unlock code.
Now I am able to manually flash the boot, recovery and system partitions from the B130 firmware. Unfortunately, this results in nothing, the phone will still not boot to anything else than fastboot mode.
I have limited knowledge/experience with Android phones, so I am kind of stuck now. I have read several topics and fastboot definitely seems to be the way to go, but there must be something that I am doing wrong.
I was wondering whether someone would be willing to give me some insight, please?
Any help would be highly appreciated!
Many thanks in advance,
Regards,
Eric.
[Edit]: I was able to flash the stock VNS-L31C432B130 firmware but not with fastboot... I had to use DC-Phoenix and pay 15€ to do so. Is there a free equivalent to DC-Phoenix yet?
Hello
I think you should disconnect the cable and press on volume + and power erevovery wipe factory, cache. Restart
If it does not work, start again.
With the toolkit, bootloader code, installs twrp,
Go download c432oeminfo double sim.zip Badwolf
Fashe c432oeminfo.zip.
switch off.
Doad b130.
Yes, this solution saved my phone... And u can try flash with fastboot any partition (recovery, system....)
Odoslané z VNS-L21 pomocou Tapatalku
Thank you for your help, guys!
Yet, nothing happens when I disconnect the cable and try to reboot the phone while holding Vol+ and Power. Vol- and power or Vol+, Vol- and Power do not deal any better result unfortunately. The screen remains off.
I believe I should delete/flash something through fastboot, but I do not know what! I believe I have tried everything I could think of, and I am running out of ideas...
Yet the phone is accessible through fastboot, so all hope is not lost, right?
Well, I have good news: I managed to reflash my phone by following this thread: https://forum.xda-developers.com/hua...green-t3485836
You have to download and use DC-Phoenix to flash a stock firmware to the phone.
The bad part is that it is a paid service that will cost you 15€... but for me it was worth it in comparison with having a dead phone.
I wonder why no one has come up with a free equivalent to DC-Phoenix yet?
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
Super easy to fix.
Download the newest Full OTA image for angler: https://developers.google.com/android/ota
Then reboot to recovery by holding VOL-DOWN and powering on, then selecting recovery from the boot menu. Then choose "Apply Update from ADB", and use adb sideload /path/to/filenameofotaimage.zip to revive it.
Hey!
Thanks for your fast reply and your helpful tone.
However, when I choose Recovery mode it once again stucks in bootloop resulting in me never accessing recovery mode
npjohnson said:
Super easy to fix.
Download the newest Full OTA image for angler: https://developers.google.com/android/ota
Then reboot to recovery by holding VOL-DOWN and powering on, then selecting recovery from the boot menu. Then choose "Apply Update from ADB", and use adb sideload /path/to/filenameofotaimage.zip to revive it.
Click to expand...
Click to collapse
I am not sure my first reply was sent (having an unstable connection) so trying again:
When in bootloader and pressing recovery mode it goes straight back to bootloop. Hence, I cannot access recovery mode. Feels like a catch-22.
robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
maybe if you posted it in the correct forum, you would get an answer...
Moved to the correct board...
If you can't boot the phone and you can't boot to recovery and Android debugging and oem unlocking are not enabled, there isn't much (read anything) you can do. Maybe take it to a local repair shop and see if they can replace the motherboard for you.
robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6p/general/confirmed-hardware-defects-nexus-6p-t3610405
Heating the phone temporarily boots the phone. (You can also check videos for saving data in bootlooped LG phones)
Hi, I bought a second hand zte axon 7 a2017. I want told it was rooted or anything. Power button is squashed in so got it for cheap so bought it. Phone runs fine on stock rom and for restarting etc I use mi pop and power button can still be used by poking it hard at an angle with stick etc. I'm familiar with rooting, flashing etc but it is the first time I'm using zte so it's bit different.
Issue is I want to root it to get rid of bloatware etc. I downloaded Root Check app and it says it is rooted and busybox is installed but there is no super user app. Funny thing is I have no means to check if bootloader is unlocked and can't even boot to bootloader mode as it just gets stuck at zte logo when I try to boot to bootloader mode from recovery mode. I get to recovery mode by restarting the phone from mi-pop and holding the volume up button. I don't even think there is custom recovery installed too which I don't know how that's possible as my understanding was custom recovery needs to be installed earlier in order to root.
Can someone please throw some light and give me some guidance. I want to go full stock but rooted and want custom recovery too just so that i can make a nandroid back up.
I'm on Mi favor 4.0
ZTE_A2017V1.0.0.B07.0
Thank you in advance
I'm on the US variant so I'm not too familiar with yours. I would suggest starting from stock, and downloading MiFlash, and the latest MiFlash edl package for your variant.
Jay_Nz said:
Hi, I bought a second hand zte axon 7 a2017. I want told it was rooted or anything. Power button is squashed in so got it for cheap so bought it. Phone runs fine on stock rom and for restarting etc I use mi pop and power button can still be used by poking it hard at an angle with stick etc. I'm familiar with rooting, flashing etc but it is the first time I'm using zte so it's bit different.
Issue is I want to root it to get rid of bloatware etc. I downloaded Root Check app and it says it is rooted and busybox is installed but there is no super user app. Funny thing is I have no means to check if bootloader is unlocked and can't even boot to bootloader mode as it just gets stuck at zte logo when I try to boot to bootloader mode from recovery mode. I get to recovery mode by restarting the phone from mi-pop and holding the volume up button. I don't even think there is custom recovery installed too which I don't know how that's possible as my understanding was custom recovery needs to be installed earlier in order to root.
Can someone please throw some light and give me some guidance. I want to go full stock but rooted and want custom recovery too just so that i can make a nandroid back up.
I'm on Mi favor 4.0
ZTE_A2017V1.0.0.B07.0
Thank you in advance
Click to expand...
Click to collapse
Okay, couple o' things:
- If your bootloader is unlocked, there should be a screen when your turn on the phone that says 'Your phone can't be checked for corruption. Please lock the bootloader' which is there for around 10 secs. If you use the volume buttons from there you should be able to select recovery or bootloader
-It is possible that you don't even have a working bootloader mode. IN CASE THAT YOU DON'T HAVE THE SCREEN I PREVIOUSLY TALKED ABOUT, try with adb: install adb, enable usb debugging, authenticate in the phone, "adb reboot bootloader". If it reboots into the bootloader (Should say START in green plus some text) then you can unlock the bootloader. But follow a guide before attempting that, or you'll risk a brick
-Having the stock recovery doesn't necessarily mean that the phone is not rooted. If you have the stock recovery it could be because the previous owner simply rooted it, used it, then flashed the stock recovery and sold the phone like that. Which is really weird in itself
-What you should do to recover from this mess is use MiFlash. Find a package called "A2017_NOUGAT_FULL_EDL" (might have a version number somewhere, just use the most recent). Enable OEM unlocking and USB debugging, then issue "adb reboot edl". The phone seems off but it's not. Now unpack the file and install it to the phone with MiFlash.
After you reflash the system you can proceed with a guide. If you get the warning screen when you turn on the phone then your bootloader is already unlocked and you can proceed with installing TWRP (maybe via axon7tool) then flashing Magisk.
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.
tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?
My HTC U Ultra suddenly froze past nigth, then it rebooted... and never came back, it won't go past the HTC logo over and over. I am not able to enter in recovery mode either, the only thing I can do is, by pressing both volume buttons and power, entering in what seems to be fastboot menu. In that state I can send the phone fastboot commands (no adb commands though) but If i try to wipe it it says "unable to do in s-on" or similar. I was pretty happy with this phone, and spent a few bucks in a new battery not two months ago.... anything I can do?
Thanks.
PS: I failed to state that the phone is stock, not unlocked or rooted.
If it has just happened out of the blue and you haven't been doing anything with your phone, have you tried a simple reset? (Press and hold volume down and power button until your phone vibrates - Usually about 20 seconds for me)
If not, and you are struggling to get into recovery etc, see if you can follow the method in the thread linked below if you are currently on stock rom!?
(Not sure if this would delete all your data or not, so perhaps only use as a last resort....)
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
spikey001 said:
If it has just happened out of the blue and you haven't been doing anything with your phone, have you tried a simple reset? (Press and hold volume down and power button until your phone vibrates - Usually about 20 seconds for me)
If not, and you are struggling to get into recovery etc, see if you can follow the method in the thread linked below if you are currently on stock rom!?
(Not sure if this would delete all your data or not, so perhaps only use as a last resort....)
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
Click to expand...
Click to collapse
Reset doesn't work, and the other procedure didn't work either.
If I leave it plugged to the charger, it will fall into an endless reboot loop. Sometimes (few) it will end up booting, but If i try to do something with the phone it doesn't respond and reboots again.
Thanks.
As you can send fastboot commands, can you flash a recovery.img (i.e. TWRP), and then wipe cache and dalvik/art to see if that helps, but if not, flash corresponding rom to that which you already have?
spikey001 said:
As you can send fastboot commands, can you flash a recovery.img (i.e. TWRP), and then wipe cache and dalvik/art to see if that helps, but if not, flash corresponding rom to that which you already have?
Click to expand...
Click to collapse
I tried that, too, but didn't work. If I do a fastboot devices it detects the phone, but if I do a fastboot getvar all it doesn't give me any information, it doesn't admit adb commands, when I try to flash a rom or a recovery, it fails, I suspect it needs to have the USB debugging enabled, but I can't enable it in this state.
As I said before, if I leave it plugged to the charger, It will randomly end up booting (it can happen in the third loop or in the 50th), but it will freeze or reboot again in few seconds.
Ah I see, if you haven't got USB debugging enabled then I am unsure how to help sorry. Have you got your media backed up, or stored on micro sd? If so, might have to bite the bullet and do a factory reset. Sorry I couldn't be of any help. Maybe someone else would be able to help you further?
spikey001 said:
Ah I see, if you haven't got USB debugging enabled then I am unsure how to help sorry. Have you got your media backed up, or stored on micro sd? If so, might have to bite the bullet and do a factory reset. Sorry I couldn't be of any help. Maybe someone else would be able to help you further?
Click to expand...
Click to collapse
The data is not a problem, every important file has been backed up.
Regarding factory reset, since the device won't go to recovery, I can't see how can I do it.
-- Edit --
I noticed that when the phone is cold, those few times it boots, it lasts a little bit more (a matter of seconds) until it freezes again, so I tried to leave it in the freezer for a few minutes, and tried to boot it, and had enough time to do a factory reset. The factory reset worked, because now, when it boots, it goes straight to the intial setup, but keeps hanging after a few seconds. I suspect that the internal memory was somehow damaged, I don't think there is much left to do...
Is it possible to skip setup in order to get to settings and enable USB debugging so you can install a recovery?
If you can, then it might be an idea to try performing a repair of all the partitions and install a fresh ROM... Just to ensure it isn't a hardware issue!!
spikey001 said:
Is it possible to skip setup in order to get to settings and enable USB debugging so you can install a recovery?
If you can, then it might be an idea to try performing a repair of all the partitions and install a fresh ROM... Just to ensure it isn't a hardware issue!!
Click to expand...
Click to collapse
I can't see how to skip initial setup... and I don't have time enough to go through it, the phone will hang in 30 seconds or less. At this point, I really needed a working phone, so I bite the bullet and bought a new one... I will deal with the old one later, or I might sell it for parts.
Thanks everybody for the help.
No worries, enjoy your new phone