Hello there!
I received my Poco F1 yesterday and set it up with all the apps and settings I wanted to use (including WhatsApp and Signal Backups with private keys). Unfortunately the phone didn't survive the day - after less than three hours the screen went black and since then stayed like that. Additionally, it heats up like nothing else whenever it is turned on. I tried holding power, power + vol up etc. - the phone seems to reboot and booting up again but the screen stays dark. As I live in the EU and bought the phone here I contacted the seller, who agreed on shipping a new device, but I still have to send back the old and broken one. That's where my problem begins:
- There's already a load of private data and information on the phone I do not want to give to the seller and everyone who might gets the phone in their hands afterwards
- The phone itself still seems to work. I can reach it via adb, reboot to bootloader, reach it via fastboot and reboot back to the operating system
-
Code:
adb shell pm clear xxx
and
Code:
adb shell am broadcast -a android.intent.action.MASTER_CLEAR
both yield a SecurityException
-
Code:
fastboot -w
yields
Code:
FAILED (remote: 'Erase is not allowed in Lock State')
- I do not want to unlock the device, as I don't want to give anyone any reasons to refuse this guarantee case.
Do you have an idea?
Thanks in advance!
Your warranty doesn't void on this device. It was confirmed by CEO Jai Mani. If you still concern for warranty you can later relock it. Use this command - "fastboot oem lock". So stay calm and try this.
Hi and thanks for your suggestion! It looks like I don't have any other choice. Could maybe anyone guide me through what happens when (my screen is completely dark after all )?
So, I can easily go into fastboot mode by doing a "adb reboot bootloader". I will then use the unlock tool to unlock the phone. Does anyone have an exact idea of what will happen next?
Will it reboot automatically or do I have to do it by myself? Will it stay in fastboot mode?
Will it try to set something up or anything else I should not abort after rebooting? How long will this take approximately?
Will all data be lost by only unlocking the phone or will I still be able to "adb shell" into the system after unlocking (w/o accepting the computer's key again of course)?
In case I got stuck, is there a reliable way to go from anywhere into fastboot mode again (to "fastboot -w" and relock)? Which button combo can I use for "completely turn the phone off" - is it the "3min power button" or the "power button and volume up" one? After "fastboot -w", how does the phone behave? Does it reboot automatically and does it do something after that I should not abort? If yes, how long will it take approximately?
I see that these are kind of difficult questions for people who could see what's going on, but after all it's pretty important for me because I can't
Thanks for your help!
robo1337 said:
Hi and thanks for your suggestion! It looks like I don't have any other choice. Could maybe anyone guide me through what happens when (my screen is completely dark after all )?
So, I can easily go into fastboot mode by doing a "adb reboot bootloader". I will then use the unlock tool to unlock the phone. Does anyone have an exact idea of what will happen next?
Will it reboot automatically or do I have to do it by myself? Will it stay in fastboot mode?
Will it try to set something up or anything else I should not abort after rebooting? How long will this take approximately?
Will all data be lost by only unlocking the phone or will I still be able to "adb shell" into the system after unlocking (w/o accepting the computer's key again of course)?
In case I got stuck, is there a reliable way to go from anywhere into fastboot mode again (to "fastboot -w" and relock)? Which button combo can I use for "completely turn the phone off" - is it the "3min power button" or the "power button and volume up" one? After "fastboot -w", how does the phone behave? Does it reboot automatically and does it do something after that I should not abort? If yes, how long will it take pictures approximately?
I see that these are kind of difficult questions for people who could see what's going on, but after all it's pretty important for me because I can't
Thanks for your help!
Click to expand...
Click to collapse
First unlocking bootloader takes 3 days. Then after unlocking your all data will be wiped and you automatically boot into the system. If anything goes wrong you can use Mi flash tool to flash miui again in fastboot mode. The most reliable way to boot into fastboot mode is to boot into recovery by pressing volume+ button + power button at the same time and then boot from there. I have never encountered that prob so I can't surely tell about that. Please tell me if it works.
robo1337 said:
Hi and thanks for your suggestion! It looks like I don't have any other choice. Could maybe anyone guide me through what happens when (my screen is completely dark after all )?
So, I can easily go into fastboot mode by doing a "adb reboot bootloader". I will then use the unlock tool to unlock the phone. Does anyone have an exact idea of what will happen next?
Will it reboot automatically or do I have to do it by myself? Will it stay in fastboot mode?
Will it try to set something up or anything else I should not abort after rebooting? How long will this take approximately?
Will all data be lost by only unlocking the phone or will I still be able to "adb shell" into the system after unlocking (w/o accepting the computer's key again of course)?
In case I got stuck, is there a reliable way to go from anywhere into fastboot mode again (to "fastboot -w" and relock)? Which button combo can I use for "completely turn the phone off" - is it the "3min power button" or the "power button and volume up" one? After "fastboot -w", how does the phone behave? Does it reboot automatically and does it do something after that I should not abort? If yes, how long will it take approximately?
I see that these are kind of difficult questions for people who could see what's going on, but after all it's pretty important for me because I can't
Thanks for your help!
Click to expand...
Click to collapse
As you seem to be interested in only removing the data (not recovering it), the bootloader unlock will wipe your phone completely and it will automatically boot again into the initial Setup screen where the first screen will be asking for the country. At that point simply power off the phone and you will be done. I am saying this from the personal experience of unlocking the bootloader of this phone.
Hi and thanks for your help! The unlocking & relocking process was completely flawless. Vol + Power Up seems to be the "Turn off"-Combo, by the way
Thanks again!
SamyakJ said:
First unlocking bootloader takes 3 days. Then after unlocking your all data will be wiped and you automatically boot into the system. If anything goes wrong you can use Mi flash tool to flash miui again in fastboot mode. The most reliable way to boot into fastboot mode is to boot into recovery by pressing volume+ button + power button at the same time and then boot from there. I have never encountered that prob so I can't surely tell about that. Please tell me if it works.
Click to expand...
Click to collapse
nokia c100 doesnt seem to recovery.img to boot recovery only fastboot mode
Related
I own many nexus devices, a heavy terminal user and I know about things like adb, fastboot etc.
This device Huawei mediapad 7 lite is driving me mad, I wanted to install CM 10.1 on it but I am unable to enter into fastboot mode. I have searched enough and tried all the methods like "adb reboot bootloader" and "volume up + power", but no luck at all.
Is there anything that I am missing? I am able to use 'adb' but rebooting into bootloader just power offs the device and sometimes just displays the battery charging icon on screen.
If I try "adb reboot recovery", it enters into recovery mode but within 2 seconds reboots. I somehow need to get into bootloader mode(fastboot mode) so that I can flash recovery and custom rom.
Your help is highly appreciated!
Thanks in advance
smartdipu said:
I own many nexus devices, a heavy terminal user and I know about things like adb, fastboot etc.
This device Huawei mediapad 7 lite is driving me mad, I wanted to install CM 10.1 on it but I am unable to enter into fastboot mode. I have searched enough and tried all the methods like "adb reboot bootloader" and "volume up + power", but no luck at all.
Is there anything that I am missing? I am able to use 'adb' but rebooting into bootloader just power offs the device and sometimes just displays the battery charging icon on screen.
If I try "adb reboot recovery", it enters into recovery mode but within 2 seconds reboots. I somehow need to get into bootloader mode(fastboot mode) so that I can flash recovery and custom rom.
Your help is highly appreciated!
Thanks in advance
Click to expand...
Click to collapse
Hi,
I am having similar problem for different reasons. I am in a reboot loop and if I try power+volume up I get this: Enter into fastboot mode. You can press POWER key for more than 10 seconds to reboot device.
Power for 10 seconds will reboot and go back to reboot loop, but anything else I try to push does not get me anywhere. In this state the tablet will not show through USB on the computer. I was trying to google how to enter bootloader, but I am not able to find any info plus screenshots. So if you find a solution, I would VERY happy.
I would keep you informed if I find something myself. Here is my post: http://forum.xda-developers.com/showthread.php?p=37646468#post37646468
Good luck.
Karel
kolibrik said:
Hi,
I am having similar problem for different reasons. I am in a reboot loop and if I try power+volume up I get this: Enter into fastboot mode. You can press POWER key for more than 10 seconds to reboot device.
Power for 10 seconds will reboot and go back to reboot loop, but anything else I try to push does not get me anywhere. In this state the tablet will not show through USB on the computer. I was trying to google how to enter bootloader, but I am not able to find any info plus screenshots. So if you find a solution, I would VERY happy.
I would keep you informed if I find something myself. Here is my post: http://forum.xda-developers.com/showthread.php?p=37646468#post37646468
Good luck.
Karel
Click to expand...
Click to collapse
Then you see on your tablet: Enter into fastboot mode. You can press POWER key for more than 10 seconds to reboot device. - then it means that you are already in fastboot mode. Holding power for 10 s needed to exit from fastboot (to reboot).
after_silence said:
Then you see on your tablet: Enter into fastboot mode. You can press POWER key for more than 10 seconds to reboot device. - then it means that you are already in fastboot mode. Holding power for 10 s needed to exit from fastboot (to reboot).
Click to expand...
Click to collapse
Thanks for the reply. Sorry if I sound like a novice, but what can I fo in fastboot mode? The computer does not recognize the device in this fastboot, so I can do anything from computer, and the tablet does not respond to anything pressed while in this mode.So how do I install recovery or do anything sensible? Sorry if I missed something obvious, it is my first Mediapad.
kolibrik said:
Thanks for the reply. Sorry if I sound like a novice, but what can I fo in fastboot mode? The computer does not recognize the device in this fastboot, so I can do anything from computer, and the tablet does not respond to anything pressed while in this mode.So how do I install recovery or do anything sensible? Sorry if I missed something obvious, it is my first Mediapad.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=37665946&postcount=51
All operations with fastboot should be performed via terminal.
Hello after_silence, any help for me? When I do "adb reboot bootloader", it shuts down and NOTHING comes up on screen. If usb cable is connected, it shows the battery charging symbol. When I do "sudo fastboot devices", nothing comes up. That means I am not entering into fastboot mode. Any other workaround?
Thanks!
Help
smartdipu said:
I own many nexus devices, a heavy terminal user and I know about things like adb, fastboot etc.
This device Huawei mediapad 7 lite is driving me mad, I wanted to install CM 10.1 on it but I am unable to enter into fastboot mode. I have searched enough and tried all the methods like "adb reboot bootloader" and "volume up + power", but no luck at all.
Is there anything that I am missing? I am able to use 'adb' but rebooting into bootloader just power offs the device and sometimes just displays the battery charging icon on screen.
If I try "adb reboot recovery", it enters into recovery mode but within 2 seconds reboots. I somehow need to get into bootloader mode(fastboot mode) so that I can flash recovery and custom rom.
Your help is highly appreciated!
Thanks in advance
Click to expand...
Click to collapse
Is There Any Solution To This? I've Been At It All night and No results
STUCK
JaleelAJames said:
Is There Any Solution To This? I've Been At It All night and No results
Click to expand...
Click to collapse
Been up tonight on The Evervolv screen, rebooted, still Evervolv screen
Sounds similar to your problem, cannot get any PC link, power and volume controls gets me to fastboot but the PC does not see the device
Retry, Retry, EvervvolLLLLL screen, nothing else
Any suggestions or tips
thxs
---------- Post added at 05:29 AM ---------- Previous post was at 05:15 AM ----------
hillbillie said:
Been up tonight on The Evervolv screen, rebooted, still Evervolv screen
Sounds similar to your problem, cannot get any PC link, power and volume controls gets me to fastboot but the PC does not see the device
Retry, Retry, EvervvolLLLLL screen, nothing else
Any suggestions or tips
thxs
Click to expand...
Click to collapse
Managed to pull back TWRP screen, wiped Dalvik, cannot mount external_sd, now waiting on "rm - rf on external_sd"
I would like to get on the developer board, to ask directly, how I could fix this.
regards
Phew!
hillbillie said:
Been up tonight on The Evervolv screen, rebooted, still Evervolv screen
Sounds similar to your problem, cannot get any PC link, power and volume controls gets me to fastboot but the PC does not see the device
Retry, Retry, EvervvolLLLLL screen, nothing else
Any suggestions or tips
thxs
---------- Post added at 05:29 AM ---------- Previous post was at 05:15 AM ----------
Managed to pull back TWRP screen, wiped Dalvik, cannot mount external_sd, now waiting on "rm - rf on external_sd"
I would like to get on the developer board, to ask directly, how I could fix this.
regards
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=25468368&postcount=5&nocache=1&z=8663575234822929
Sorry for the simple posting, but the above thread fixed the problem.
The original failure was caused by missing the factory reset after flashing, before unzipping.
Wow , XDA saved the tab for xmas, although the 2 steps flash cust and flash tombstones didn´t
work, it rebooted to an older version just fine!
Then restored backup, I´ll try again after xmas.
Happy Xmas !!
i soft bricked my phone when installing the cyanangen 12 rom, it quit during the setup wizzard. The button combination of down and power release when seeing lg and repressing is not working. PleASE TELL ME i can enter twrp without having to restore my phone to stock. The phone will receive phone calls but that is all it does. otherwise it says setup wizzard quit and endlessly says this when you press ok. please help, despite being in los angeles, i have not found anybody capable of helping me.
Patrick--in so much need...
What is the repressing step? I've never heard of that. Isn't it just vol down and power, then release power while still holding vol down until recovery boots?
Also, do you have adb or fastboot installed on a pc? If so, adb reboot recovery from CMD if in android, or fastboot reboot recovery if in bootloader. Have you tried those?
patrick73csun said:
i soft bricked my phone when installing the cyanangen 12 rom, it quit during the setup wizzard. The button combination of down and power release when seeing lg and repressing is not working. PleASE TELL ME i can enter twrp without having to restore my phone to stock. The phone will receive phone calls but that is all it does. otherwise it says setup wizzard quit and endlessly says this when you press ok. please help, despite being in los angeles, i have not found anybody capable of helping me.
Patrick--in so much need...
Click to expand...
Click to collapse
You don't have to release the buttons, idk why so many people keep saying this. Should be the same as mine.. With the phone off just hold both power and volume down until you see it say Recovery Mode loading, then release. If that doesn't work then try the adb command while plugged in to your computer.
Barshalen said:
You don't have to release the buttons, idk why so many people keep saying this. Should be the same as mine.. With the phone off just hold both power and volume down until you see it say Recovery Mode loading, then release. If that doesn't work then try the adb command while plugged in to your computer.
Click to expand...
Click to collapse
Yup. Thats the same thing i was wondering. I had to use it last night. Just hold both. Easy.
Sent from rotary technology Phone
"Also, do you have adb or fastboot installed on a pc? If so, adb reboot recovery from CMD if in android, or fastboot reboot recovery if in bootloader. Have you tried those? "-----------
How do you get into bootloader if phone is bricked? It sees the phone, but it won't open up and let me look inside? Thank you
A window comes up and says that the kernal cracked.. My phone is having a hard time getting charged, could this be related?
Hi. My sons HDX is stuck in fastboot mode. Amazon support only offered him a discount to replace it. I thought maybe I could do something to wake it up or reflash it but from what I'm reading this is a difficult device. I have been able to get it to respond to the fastboot reboot command in linux but nothing else. This device has never been rooted/flashed/modded and I don't know how it got this way. Is there anything I can do at this point besides throw it away?
Thanks.
when you are at the fastboot screen...
press the power button for 10-20 sec. and it will shut down...
than try to power it on again.... (try it with unplugged usb)
maybe this helps...
If possible, I would unlock the bootloader and then try this guide: http://forum.xda-developers.com/showpost.php?p=22077057&postcount=11
This device has never been rooted/flashed/modded and I don't know how it got this way.
Click to expand...
Click to collapse
Just thought this means the HDX is on 4.5.2(3)
thanks for the responses. I have tried rebooting the device many times with or without usb plugged in. I've held the power button for 25 seconds until it starts rebooting again. It always boots to a gray kindle fire logo and says fastboot. I've tried the fastboot -i 0x1949 oem idme bootmode 4000 command but it says the hw is locked. From what Ive read, the bootloader cant be unlocked right?
ianedward said:
From what Ive read, the bootloader cant be unlocked right?
Click to expand...
Click to collapse
Do you recall the firmware level (eg: 3.2.6; 4.5.2)?
Edit: After shutting down (completely off) have you tried power+volume up to access Amazon's crippled recovery? From there you might be able to initiate a factory reset.
i have tried to power it on with different button combinations. I can only get to the same fastboot screen.
oh and I have no idea what firmware it was on.
ianedward said:
i have tried to power it on with different button combinations. I can only get to the same fastboot screen.
oh and I have no idea what firmware it was on.
Click to expand...
Click to collapse
Yeah, it was a long shot. At this point you may be hosed unless someone knows of a way to recover in fastboot given the state of your device (locked, unrooted, version unknown). Might want to try Amazon again. A different rep may be more accommodating. Sorry, mate.
I have successfully installed ROMs on Nexus devices, but this one has me stumped. When I issue, "adb reboot bootloader" I get the FASTBOOT and RESCUEMODE screen telling me to use HiSuite to fix it (which didn't help, btw). No options (and I've seen other threads with this issue but no answers). I'm new so can't post a link, but picture is here i.imgsafe.org/d1da047.jpg
- If I try to "adb reboot recovery", It just reboots normally
- If I hold down power and vol down, I get eRecovery, but it will only let me download over wifi (which ultimate fails getting package details) or reboot/shutdown. No options to wipe anything.
- If I hold power and vol up (or both vol up/down) it just constantly restarts with "<vibrate>Honor, for the brave" screen but never boots anything.
My niave hunch is that my normal bootloader got replaced with some kind of OTA upgrade loader and is now stuck. I can otherwise use the phone but I'd like to apply my OEM unlock code I worked so hard to get.
lmatter2 said:
I have successfully installed ROMs on Nexus devices, but this one has me stumped. When I issue, "adb reboot bootloader" I get the FASTBOOT and RESCUEMODE screen telling me to use HiSuite to fix it (which didn't help, btw). No options (and I've seen other threads with this issue but no answers). I'm new so can't post a link, but picture is here i.imgsafe.org/d1da047.jpg
- If I try to "adb reboot recovery", It just reboots normally
- If I hold down power and vol down, I get eRecovery, but it will only let me download over wifi (which ultimate fails getting package details) or reboot/shutdown. No options to wipe anything.
- If I hold power and vol up (or both vol up/down) it just constantly restarts with "<vibrate>Honor, for the brave" screen but never boots anything.
My niave hunch is that my normal bootloader got replaced with some kind of OTA upgrade loader and is now stuck. I can otherwise use the phone but I'd like to apply my OEM unlock code I worked so hard to get.
Click to expand...
Click to collapse
Also (I'm at work so doing this from my crappy memory), I sometimes do get the phone into an OTA update screen which either stays stuck at zero percent (and I have to hold power down to restart) or successfully "installs" and then just boots normally.
Hey guys. I have the Huawei Ascend XT and I thought I was hard bricked and I started to mess around with some of the commands with Fastboot. I was able to get my phone back up and running. I am currently on the B180 but I am assuming it will work for any version between B140 and B180. What happened with me was I wiped my system partition but I had an unlocked bootloader. I could not get TWRP to boot up or I wasn't able to flash it because of the "FRP Lock", which is also known as Factory Reset Protection so a lot of commands were disabled such as "fastboot -w" to do a factory reset so I thought the worst case scenario.
1. Make sure you can access the "Rescue & Fastboot Mode" by holding down the Volume Down button and Power Button. Mine boot looped for a few screen flashes but it eventually booted into it.
2. Download the stock B140 recovery from here, post #7. (Special Thanks to clsA) https://forum.xda-developers.com/huawei-ascend-xt/help/stock-ascend-xt-recovery-t3572924
3. Assuming you have already downloaded the Minimal ADB and Fastboot files, open up a command prompt navigating to the fastboot folder and type in the following commands: "fastboot boot recovery.img"
4. After it boots, you can go ahead a do a factory reset via the recovery. It will be stuck on 99% and it wont go to 100%. Give the phone 5 minutes on 99% before doing anything. It gives it a chance to wipe everything completely.
5. Reboot your phone by holding the Volume Down and Power button until it boots into "Recovery & Fastboot Mode" and then flash TWRP as you like. As you can now see that "FRP Lock" disappeared thus allowing you to flash recoveries and use commands again.
It helped me so I hope it helps you out, saved me a lot of stress. Press thanks if this helped and feedback is always welcome.
Always been a great feature - can use fastboot to boot into any recovery, especially useful for testing if a new one works before flashing it. Fairly certain it's fully functional too, so you can do whatever changes you like or make backups without changing your stock recovery.
TheShwksFan86 said:
Hey guys. I have the Huawei Ascend XT and I thought I was hard bricked and I started to mess around with some of the commands with Fastboot. I was able to get my phone back up and running. I am currently on the B180 but I am assuming it will work for any version between B140 and B180. What happened with me was I wiped my system partition but I had an unlocked bootloader. I could not get TWRP to boot up or I wasn't able to flash it because of the "FRP Lock", which is also known as Factory Reset Protection so a lot of commands were disabled such as "fastboot -w" to do a factory reset so I thought the worst case scenario.
1. Make sure you can access the "Rescue & Fastboot Mode" by holding down the Volume Down button and Power Button. Mine boot looped for a few screen flashes but it eventually booted into it.
2. Download the stock B140 recovery from here, post #7. (Special Thanks to clsA) https://forum.xda-developers.com/huawei-ascend-xt/help/stock-ascend-xt-recovery-t3572924
3. Assuming you have already downloaded the Minimal ADB and Fastboot files, open up a command prompt navigating to the fastboot folder and type in the following commands: "fastboot boot recovery.img"
4. After it boots, you can go ahead a do a factory reset via the recovery. It will be stuck on 99% and it wont go to 100%. Give the phone 5 minutes on 99% before doing anything. It gives it a chance to wipe everything completely.
5. Reboot your phone by holding the Volume Down and Power button until it boots into "Recovery & Fastboot Mode" and then flash TWRP as you like. As you can now see that "FRP Lock" disappeared thus allowing you to flash recoveries and use commands again.
It helped me so I hope it helps you out, saved me a lot of stress. Press thanks if this helped and feedback is always welcome.
Click to expand...
Click to collapse
How were you able to flash the recovery in FRP Lock???
I've tested to flash on that mode and got the same error "Command Not Allowed"
How have you flashed the recovery??
What am i missing??
Thanks
RSGI said:
How were you able to flash the recovery in FRP Lock???
I've tested to flash on that mode and got the same error "Command Not Allowed"
How have you flashed the recovery??
What am i missing??
Thanks
Click to expand...
Click to collapse
Same
TheShwksFan86 said:
Hey guys. I have the Huawei Ascend XT and I thought I was hard bricked and I started to mess around with some of the commands with Fastboot. I was able to get my phone back up and running. I am currently on the B180 but I am assuming it will work for any version between B140 and B180. What happened with me was I wiped my system partition but I had an unlocked bootloader. I could not get TWRP to boot up or I wasn't able to flash it because of the "FRP Lock", which is also known as Factory Reset Protection so a lot of commands were disabled such as "fastboot -w" to do a factory reset so I thought the worst case scenario.
1. Make sure you can access the "Rescue & Fastboot Mode" by holding down the Volume Down button and Power Button. Mine boot looped for a few screen flashes but it eventually booted into it.
2. Download the stock B140 recovery from here, post #7. (Special Thanks to clsA) https://forum.xda-developers.com/huawei-ascend-xt/help/stock-ascend-xt-recovery-t3572924
3. Assuming you have already downloaded the Minimal ADB and Fastboot files, open up a command prompt navigating to the fastboot folder and type in the following commands: "fastboot boot recovery.img"
4. After it boots, you can go ahead a do a factory reset via the recovery. It will be stuck on 99% and it wont go to 100%. Give the phone 5 minutes on 99% before doing anything. It gives it a chance to wipe everything completely.
5. Reboot your phone by holding the Volume Down and Power button until it boots into "Recovery & Fastboot Mode" and then flash TWRP as you like. As you can now see that "FRP Lock" disappeared thus allowing you to flash recoveries and use commands again.
It helped me so I hope it helps you out, saved me a lot of stress. Press thanks if this helped and feedback is always welcome.
Click to expand...
Click to collapse
Yeah, it seemed like it was gonna work, got boot.img downloaded, but it sat there trying to boot for a half an hour with nada happening. Bummer.