Hello.
I have a strange issue here.
So, I wanted to factory reset my tablet and, for the reason that I always prefer the "factory reset" from the Recovery Mode (instead of the one that is available in the Android OS), I booted (for the first-ever time) into the Recovery Mode.
However, I got the error message that you can see at the attached picture.
Any ideas on how I may can fix that?
I assume that it has to do with the recovery and not with the actual Android OS.
Thanks!
Same here
giorgos147 said:
Hello.
I have a strange issue here.
So, I wanted to factory reset my tablet and, for the reason that I always prefer the "factory reset" from the Recovery Mode (instead of the one that is available in the Android OS), I booted (for the first-ever time) into the Recovery Mode.
However, I got the error message that you can see at the attached picture.
Any ideas on how I may can fix that?
I assume that it has to do with the recovery and not with the actual Android OS.
Thanks!
Click to expand...
Click to collapse
It's normal for it to do that
Related
Please see Update 5 at/near the top of:
http://forum.xda-developers.com/showthread.php?t=2176452
Basically, a bad USB cable was making fastboot operations flakey, and by the time I discovered it, the recovery program was wrecked. Everything else seems to work fine. The Nexus is running 4.2.2, and I have toolkit 4.3.5, running on win7x64.
I've tried reflashing various recovery programs, including the stock one. No error flashing is reported (with the now-good cable), but going into recovery mode fails, showing the android image with a red triangle and exclamation point in it.
[Edit: To be clear, I have NO recovery menu at all - when I select recovery in the bootloader, I get the regular boot "X" in the middle of the screen, then it is replaced with the android lying on its back with the alert notice above it]
The bootloader appears successfully unlocked, and in fact the entire unlock/root process was fine, once the cable was replaced. That is, no errors were reported, everything seems to be ok, but I can't use the recovery option. Note that the unlock wiped all data, so it was as clean as possible.
Should I completely reflash 4.2.2? Will that even matter?
Is there anything else I can try? I'm not keen to try sideloading 4.2.2, but will, if there are instructions some place.
If this is no go, I'm going to have to try restoring everything to the basic original state and asking for a replacement from Amazon. I don't know how that will go, and this was to be a gift due in about a week, that I was setting up for the recipient. I've spent literally 8 hours on this today, before realizing the flakeyness was due to the USB cable being bad. Any help is very appreciated.
stickplayer said:
Please see Update 5 at/near the top of:
http://forum.xda-developers.com/showthread.php?t=2176452
Basically, a bad USB cable was making fastboot operations flakey, and by the time I discovered it, the recovery program was wrecked. Everything else seems to work fine. The Nexus is running 4.2.2, and I have toolkit 4.3.5, running on win7x64.
I've tried reflashing various recovery programs, including the stock one. No error flashing is reported (with the now-good cable), but going into recovery mode fails, showing the android image with a red triangle and exclamation point in it.
[Edit: To be clear, I have NO recovery menu at all - when I select recovery in the bootloader, I get the regular boot "X" in the middle of the screen, then it is replaced with the android lying on its back with the alert notice above it]
The bootloader appears successfully unlocked, and in fact the entire unlock/root process was fine, once the cable was replaced. That is, no errors were reported, everything seems to be ok, but I can't use the recovery option. Note that the unlock wiped all data, so it was as clean as possible.
Should I completely reflash 4.2.2? Will that even matter?
Is there anything else I can try? I'm not keen to try sideloading 4.2.2, but will, if there are instructions some place.
If this is no go, I'm going to have to try restoring everything to the basic original state and asking for a replacement from Amazon. I don't know how that will go, and this was to be a gift due in about a week, that I was setting up for the recipient. I've spent literally 8 hours on this today, before realizing the flakeyness was due to the USB cable being bad. Any help is very appreciated.
Click to expand...
Click to collapse
So you've tried using fastboot to flash a custom recovery image? The command fastboot is a part of the Android SDK.
fastboot flash recovery <name of recovery .img>
There's plenty of stickies and information in this forum, which I won't re-hash here.
The stock recovery WILL show the android with the red triangle. To get into recovery from there, I believe you need to hold the up volume key. Other recoveries shouldn't do this though. Perhaps you should try using ROM Manager or Goomanager to flash a recovery from within android.
It took several attempts - flashing stock, then cwm, from the toolkit, before cwm finally "took". It's all working now.
hi-
i recently got a notification for the Kit Kat upgrade on my Nexus 7. i tried to apply the upgrade but it failed (see attached image). when it rebooted afterwards, i could see the new Kit Kat splash/loading screen (the green + blue + yellow + red droplets coming together), but it never progress beyond that point (that screen will run until the battery drains).
i'm not quite sure how to recover from this, and the worst part is that i have pictures stored locally on the device that i'd _really_ like to keep (a running diary of a daily picture i'd taken for over 150 consecutive days).
two questions:
1) is there any way to recover my pictures?, and...
2) how can i restore my device (or preferably, upgrade to Kit Kat).
fwiw - Clockworkdmod is installed.
hsl43 said:
hi-
i recently got a notification for the Kit Kat upgrade on my Nexus 7. i tried to apply the upgrade but it failed (see attached image). when it rebooted afterwards, i could see the new Kit Kat splash/loading screen (the green + blue + yellow + red droplets coming together), but it never progress beyond that point (that screen will run until the battery drains).
i'm not quite sure how to recover from this, and the worst part is that i have pictures stored locally on the device that i'd _really_ like to keep (a running diary of a daily picture i'd taken for over 150 consecutive days).
two questions:
1) is there any way to recover my pictures?, and...
2) how can i restore my device (or preferably, upgrade to Kit Kat).
fwiw - Clockworkdmod is installed.
Click to expand...
Click to collapse
While it's booting, you need to hold down power+vol up+vol down to boot the device into fastboot mode. Hold it until you see Andy lying on his back.
Then you need to select recovery and in there, wipe cache partition and reboot.
That should fix it.
iBolski said:
While it's booting, you need to hold down power+vol up+vol down to boot the device into fastboot mode. Hold it until you see Andy lying on his back.
Then you need to select recovery and in there, wipe cache partition and reboot.
That should fix it.
Click to expand...
Click to collapse
hi iBolski-
i tried your suggestion but the boot sequence still doesn't advance past the four swirling dots. any other ideas?
(what's really important to me is getting my pictures off the device. beyond that, i'm happy to wipe the entire thing clean...)
can anybody else out there offer any suggestions on how to recover my data?
If you se the boot sequence you allready failed at launching the fastboot mode.
https://www.youtube.com/watch?v=MoNEVRvBU4E
As you can see in this video. As soon as you can enter the mode go along whith what iBolski said.
SHadowral said:
If you se the boot sequence you allready failed at launching the fastboot mode.
As you can see in this video. As soon as you can enter the mode go along whith what iBolski said.
Click to expand...
Click to collapse
that's precisely what i did, and while in the recovery i wiped the cache partition (and the dalvik cache). when i reboot afterwards, it still won't advance past the point i described.
I once had a similar problem and I had to reflash the stock rom via fastboot. But with this method your photos will be deleted and I don´t know any other.
Hi
Yesterday I got my axon 7 and it worked perfect.
Now I was wanted to change the language
So I downloaded as file that in my language
And I tried to install him .
And it worked by the adb software when the axon connected to the computer
So I went to the application in my phone and changed it to my language after USB debugging and developer option is worked
Then the phone was changed to my language and crashed
Now the axon just show the start logo and stuck in restart loop. so I tried to do few thing through your forum , but nothing helped ..
I also cleared the cache through recovery mode but it also didn't help
Its like the axon can't upload the operating system
Thanks a lot for who will help me here.
Also if it possible to send money through PayPal
And if it's legal I will send 30$ to the first that will help me solve this problem
Can you share the link to the file you downloaded ?
Is it compatible with the version of your phone ?
If you can enter in recovery it's enough to save it.
billy_boolean said:
Can you share the link to the file you downloaded ?
Is it compatible with the version of your phone ?
If you can enter in recovery it's enough to save it.
Click to expand...
Click to collapse
Yea the reason it happened is because I installed wrong adb language on my axon through USB debugging and external app
Now it possible to get into recovery
I just don't know what to do next
I tried few things but I always keep getting errors
You can try to install TWRP.
You will have a lot of option.
There is no option to restor the phone in the official recovery ?
billy_boolean said:
You can try to install TWRP.
You will have a lot of option.
There is no option to restor the phone in the official recovery ?
Click to expand...
Click to collapse
I tried to use twrp but the computer doesn't recognize My axon
You need to install driver first...
billy_boolean said:
You need to install driver first...
Click to expand...
Click to collapse
I tried but after the install the drivers and cheak them in the device manager in my computer
The name of the driver was London marshesll something
And not what I saw in the guide - adb something
And it didn't recognize my device
I wrote also adb reboot bootloader
And it gives me error massage
I would be more then happy to give someone 30$ now..
Just that my axon will work
Did you root your phone, or just use ADB to sideload a file? If it's wasn't rooted/unlocked, then a factory reset should take care of it, as nothing done via ADB in that setup would impact the system partitions.
If you used the unofficial bootloader unlocking, then you'll have to follow other people's restore guides.
As @TeutonJon78 mention, a factory reset will do the job youan boot to stock recovery using adb
Code:
adb reboot recovery
Or doing it manually,
- Completely Power off your device
- Press and HOLD Volume UP and Power button.
- once you boot to recovery just use your volume buttons to navigate FACTORY RESET.
- Reboot System
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
liron lev said:
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
Click to expand...
Click to collapse
I will be honest man. I bricked mine too. Everybody has a step by step guide that they say works. I followed them step by step. They did not work. I have an RMA open on my phone and fedex is taking it to ZTE. Use the warranty. Until Zte puts online the full factory images for us to use there is no real way to fix these things.
liron lev said:
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
Click to expand...
Click to collapse
Are you from Israel?
---------- Post added at 11:40 PM ---------- Previous post was at 11:38 PM ----------
I know how to help you if you can tell me which bootloader version you have? Did you unlocked it? did you use Tenfar's method to root it?
tabletalker7 said:
I will be honest man. I bricked mine too. Everybody has a step by step guide that they say works. I followed them step by step. They did not work. I have an RMA open on my phone and fedex is taking it to ZTE. Use the warranty. Until Zte puts online the full factory images for us to use there is no real way to fix these things.
Click to expand...
Click to collapse
Were you playing around with the rooting/unofficial bootloader? It should be very hard to actually brick the device without doing those things, and nothing a factory reset shouldn't fix.
If one's playing around with unofficial modifications, then they should take all precautions to make sure to know how to recover the device before hand. There's still a lot of moving pieces between potentially faulty TWRP bugs and no image file.
liron lev said:
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
Click to expand...
Click to collapse
Did you let it sit for awhile? First runs after a factory reset can take up to even 10 minutes to boot fully. If it still doesn't work again, check if the recovery menu has another option like wipe cache/davlik, which maybe also needs to run if they have a bug in the recovery code about resetting data. If you hadn't touch anything using the tools on this forum, and none of the factory reset/wipe data/wipe cache stuff helps, then you probably have a faulty phone. Just sideloading an app shouldn't be able to corrupt a locked system partition.
The OP of this thread hasn't yet clarified if he was just sideloading files on a normal system (which should be totally fixable unless his phone has an actual flash problem) or if he had been tinkering with other things first.
TeutonJon78 said:
Were you playing around with the rooting/unofficial bootloader? It should be very hard to actually brick the device without doing those things, and nothing a factory reset shouldn't fix.
If one's playing around with unofficial modifications, then they should take all precautions to make sure to know how to recover the device before hand. There's still a lot of moving pieces between potentially faulty TWRP bugs and no image file.
Did you let it sit for awhile? First runs after a factory reset can take up to even 10 minutes to boot fully. If it still doesn't work again, check if the recovery menu has another option like wipe cache/davlik, which maybe also needs to run if they have a bug in the recovery code about resetting data. If you hadn't touch anything using the tools on this forum, and none of the factory reset/wipe data/wipe cache stuff helps, then you probably have a faulty phone. Just sideloading an app shouldn't be able to corrupt a locked system partition.
The OP of this thread hasn't yet clarified if he was just sideloading files on a normal system (which should be totally fixable unless his phone has an actual flash problem) or if he had been tinkering with other things first.
Click to expand...
Click to collapse
The factory reset made my phone lose it's IMEI. Everyone said follow this certain guide. After following that guide and getting more help after that I had an AXON 7 that wouldn't turn on at all. Without full factory images from ZTE I won't touch the software. ZTE can fix it.
tabletalker7 said:
The factory reset made my phone lose it's IMEI. Everyone said follow this certain guide. After following that guide and getting more help after that I had an AXON 7 that wouldn't turn on at all. Without full factory images from ZTE I won't touch the software. ZTE can fix it.
Click to expand...
Click to collapse
Which guide did you follow? A Factory reset form within the stock software or stock recovery shouldn't cause that problem at all, as it should only be wiping data, cache, Davlik, and potentially the "media" portion of the internal storage.
TeutonJon78 said:
Which guide did you follow? A Factory reset form within the stock software or stock recovery shouldn't cause that problem at all, as it should only be wiping data, cache, Davlik, and potentially the "media" portion of the internal storage.
Click to expand...
Click to collapse
The factory reset that made it lose the IMEI - it was completely stock then!
liron lev said:
Hi
Yesterday I got my axon 7 and it worked perfect.
Now I was wanted to change the language
So I downloaded as file that in my language
And I tried to install him .
And it worked by the adb software when the axon connected to the computer
So I went to the application in my phone and changed it to my language after USB debugging and developer option is worked
Then the phone was changed to my language and crashed
Now the axon just show the start logo and stuck in restart loop. so I tried to do few thing through your forum , but nothing helped ..
I also cleared the cache through recovery mode but it also didn't help
Its like the axon can't upload the operating system
Thanks a lot for who will help me here.
Also if it possible to send money through PayPal
And if it's legal I will send 30$ to the first that will help me solve this problem
Click to expand...
Click to collapse
I could help you, please pm.
i tried to use the appliction "morelocale2" to chnge my phone language.
i did turn on the usb debugging option through Developer Options.
it all went good until i tried to choose my language from the app (morelocale2) it change to my language got stucked and start looping over and over. (start up and shut dowm).
after that i cleand evrything such as: wipe data/factory and cache data, and then i restart the phone. it is stoped looping but got stucked on logo zte. and after i cleaned the data i waited few houres.
i also think i used an old version of "morelocale2".
and yes im from israel...
liron lev said:
i tried to use the appliction "morelocale2" to chnge my phone language.
i did turn on the usb debugging option through Developer Options.
it all went good until i tried to choose my language from the app (morelocale2) it change to my language got stucked and start looping over and over. (start up and shut dowm).
after that i cleand evrything such as: wipe data/factory and cache data, and then i restart the phone. it is stoped looping but got stucked on logo zte. and after i cleaned the data i waited few houres.
i also think i used an old version of "morelocale2".
and yes im from israel...
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.wanam
download this app
install it
search hebrew in hebrew
choose hebrew (iw)
accept the root prompt
reboot your phone
everything will be fine
If you have bootloop issues these are not related to the app!
if you need help with this contact me!
you have my info in pm.
Hello,
before I get into detail with my current problem at hand, I want to say that I'm extremely new to flashing/rooting my tablet and in most cases am very dependent on guides and how-tos. That being said, I've search through this forum among others in order to get my problem solved but had no success so far. So your expertise is basically my last resort and hope.
I have a Lenovo Yoga 2 1050L, as stated above, and tried to root it yesterday using this guide. Unfortunately, I messed up when it came to the system's image from the custom ROM because I downloaded the original firmware for the 10'' version L instead of the further below mentioned recovery firmware in step 3 (though that link was dead anyway). Moreover, I also included the recovery.img in the custom flash process and not only the system.img and I think the error occurred while flashing the recovery partition.
Long story short, the flashing process failed and I was left with a non-booting tablet.
The status-quo is I can boot into the bootloader mode (power button + volume down) where it'll say "normal boot", "recovery mode" etc. at the top with the android figure lying on the ground with an open stomach.
With the help of the Fastboot Tethered Recovery Launcher I can use the T3 option to change the device status to "fastboot-online". From what I understood I can then enter recovery mode if pressing volume up (so I can do a data/cache wipe) but it says
"could not open sys/devices/virtual/backlight" and I couldn't figure out what that's supposed to mean or how I can solve it.
I also tried to flash it again with the stock rom downloaded from here with the Intel Phone Flash Tool 4.4.4.
But that always failed at the "fastboot -s <device> oem wipe ESP" operation. It failed to execute that command resulting in a timeout only to try it once again. After that second attempt ended in a timeout too, it went on to the next step "fastboot -s <device> oem start_partitioning" but that also failed, ultimately making the whole flash process fail.
The curious thing (for me, anyway) was that I could flash the boot.img, system.img and recovery.img individually (by going to "Custom Flash" in the Phone Flash Tool and then selecting only one of those images) and all three processes succeeded. However, I only got the success message on the Phone Flash Tool, the tablet itself got stuck during the first reboot during or after the flash process.
In fact, every boot/reboot results in the tablet being stuck at the display of the Lenovo Logo. Nothing happens after that, it just stays there.
This happens whenever I try to boot normally or boot straight into recovery mode (Power + Volume Up). The only way I can boot my tablet and actually do something with it is the bootloader mode (Power + Volume Down) but as stated above, from there I didn't manage to get anywhere else so far.
Another thing I have tried is to enter fastboot mode because I read that I can also recover from there. But whenever trying to enter fastboot mode the tablet's display goes black, then a small text says "Fastboot starting..." and that's it. Nothing happens after that, no additional text or new screen.
What I also noticed is that whenever the tablet reboots itself or if I try to boot/reboot it, the tablet is not in the list of available devices anymore if I enter "adb devices" or "fastboot devices" in my command line (with connected tablet). Only when I redo the process with the Fastboot Tethered Recovery Launcher (option T3), can I access the device with those commands again (at first I could access it with "adb devices", later on only with "fastboot devices" and to be honest, I don't know why that is).
I actually just want to wipe the data of the tablet and install the stock ROM again because I think there's just some corrupt data that keeps my tablet from booting normally. But right now I don't even know how to do that because everything I've tried so far didn't work. Not even starting the tablet with the so-called "hard reset" (Power + Volume Down + Volume Up) worked, I only got a black screen in that case.
Because I tried to solve this problem myself all day yesterday, my tablet is now also down to about 20% of battery and I don't know if I can charge it up without a proper ROM installed (probably not). So that's another factor that's hindering me from trying out other steps.
I know this is a lot of text but I still hope there's someone out there who can help me with my problem. I am at my wit's end and would highly appreciate anyone who has knowlegde about this situation with this tablet helping me.
Best regards and thank you in advance
XShunyaX
Hi Everyone -
Last night when I went to sleep I left my PH-1 plugged in and charging, and when I woke up this morning the phone had frozen with a black screen and status light still blinking. I restarted the phone and end up at a screen with "Cannot Load Android System. Your data may be corrupt". The boot cycle goes "Powered by Android" --> circles to square dot rotation --> restarts to "Powered by Android" --> to screen mentioned before with corruption. I have options to "Try Again" or "Factory Reset" and have selected "Try Again" about 20 times now with no luck.
Some pertinent facts:
Running latest official OS from Essential
Bootloader unlocked
Phone is encrypted
When I flashed the latest official OS about a year ago I used TWRP, but forgot to re-install TWRP after the flash
I am able to get to the Bootloader --> "Recovery" --> "No Action Screen" and then get to the actual recovery from there; I am now kicking myself for not reinstalling TWRP. My options on the recovery screen are "apply update from ADB option", "mount /system", or "Factory Data Reset" (as well as review logs and some other tests).
Most of the data on the phone is backed up, however there are still some items not backed up that I'd like to attempt to retrieve.
My Question - What are my options to try and salvage the data off the phone provided it is encrypted? I've seen some references to using ADB update to re-flash the original OS (I assume this is a dirty flash) but not wipe the data and my data would still be there after the install. I've seen references for that approach but not confident enough to know if it would apply for my case. In example, would this work even with the encryption? Alternatively, I expect I could reinstall TWRP via ADB update and try to work something out from there.
Thank you in advance for reading this! I appreciate any and all insight or recommendations of an approach to take. As you can see, I'm clearly a novice who has followed some tutorials, but definitely not advanced enough to have strong knowledge of all of Android's innards. Thanks again.