Related
I had installed TNT Lite v 4.3.0 a couple of weeks ago and it was working pretty good. But today my tablet has gone into a bad state. Every app that I run results in FC. Even the ADW launcher EX that I had selected default is crashing. It then gives me the options: ADW Laucher, ADW Launcher EX, and the regular Launcher. The plain ADW Launcher also fails, but fortunately the regular Launcher still works so I can access the apps.
But unfortunately almost every app that I am trying fails. The only one that doesn't fail is the Web browser. The Settings starts and I can access Applications menu but once I choose say System Applications, after that if I try to choose some other option such as Installed Application, it crashes as well.
Last night however when I started the tablet the battery was probably down and while it was powering it up, it turned off and then restarted by itself and then turned off, without reaching the lock screen. I don't know if it has something to do with all this.
What do I do now? Any help will be appreciated.
Thanks.
A well known issue.
http://forum.xda-developers.com/showthread.php?t=896395
This is why I'm an advocate of people doing the partitioning right before they flash their first custom rom. This way, they won't have to wipe everything later on.
I could only wonder why people aren't mentioning this in every custom rom thread.
Thank you so much. Will try it out tonight.
Unfortunately it seems I have run into a worse issue (without even doing anything yet). Now when I power it on, it starts and shuts off within a few seconds, just shows the birds for like 5 secs and bang, black screen.
The tablet is fully charged (if I put it on charge the light turns green in no time). Looks like the battery is dead.
You might be dropping into APX mode. Do you know how to use nvflash?
Thanks for the reply. You are absolutely right. After multiple tries it did boot up and I was able to install clockworkmod and it all worked great. It wiped off everything but I could live with that. And I turned it off and back on and it was working fine.
But then it went back into the same mode - shutting off immediately after turning on. I decided to return this tablet thinking that it is bad. But before I would do that I thought to restore it or else Viewsonic won't honor the warranty. So I started reading the thread about restoring the tablet to stock using nvram flash. In that procedure it requires me to put the tablet in APX mode and that's when I thought that maybe it is going into APX without pressing the volume - button.
Anyway I was successfully able to flash nvram. Or so it said. I still have the output from the batch file. But now my tablet is totally bricked. It does not boot at all. No pretty birds for me.
I hope there is some way out of it. Please help.
Edit: After re-flashing and using a different file, it seems to have made it a little better. At least I am seeing the birds again. But the original problem of shutting off, or going into the APX mode without pressing Volume button, has returned. All I am getting is the birds for a few seconds and then black screen. I will continue to retry, and if I see it booting up successfully to the stock, this thing is going back to the factory.
1) What image did you use to nvflash?
2) What happened when the flash was finished? Did it boot normally at least once?
3) Does the screen just stay dark all the time now?
1) First time nvflash_gtablet_46_2010112600.zip and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Later I flashed nvflash_gtablet_2010110500.zip. This at least recovered it enough that it shows the birds, but soon after the screen turns black. I have confirmed that it is going in APX mode. If I have USB cable connected to my PC, the PC reports discovering the NVIDEA APX device.
2) It hasn't booted normally since I flashed nvram.
3) No I get the birds, but after that it turns dark.
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Thanks for your response. I tried it. Did not work. When you say Replace part9.img with the recovery.img, does it mean copy recovery.img into the NVFlash directory and rename it to part9.img or leave it as recevery.img. I renamed it to part9.img and backed up the original part9.img to part9.img.tmp. The size of recovery.img and the original part9.img are very different. I am confused. Please help.
K J Rad said:
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Click to expand...
Click to collapse
Yes, that is exactly what I meant.
Are you sure you're holding the volume UP key? Birds and then black screen is APX mode which is normally entered by holding volume DOWN.
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Any ideas?
I was thinking about formatting the gtablet. Please let me know if this is the right move, or there is something else I could try first.
shah123 said:
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Click to expand...
Click to collapse
A little more than "It did not work" would be helpful.
What step failed? Please tell me what happened after each step.
Did you get into CWM and repartition?
Did you get everything cleared?
What happened when it rebooted?
What was the original filename of the image you tried to flash?
What version of clockworkmod do you have installed?
Have you ever used ROM Manager?
All of this is important and no one can help you if you don't provide enough information.
Oh, I am sorry. Here are the answers to the questions you asked:
What step failed? Please tell me what happened after each step.
Ans: Out of the 7 steps you provided, the steps 1, 2 and 3 worked fine. It is the step 4 that failed (and of course I can't proceed with the steps anymore). In other words I cannot go into clockworkmod recovery.
Did you get into CWM and repartition?
Ans: No I was not able to do so. If I press power and Volume Up key at the same time, nothing happens, screen remains black, not even birds come up.
Did you get everything cleared?
Ans: I believe you are referring to step 6. No, I could not get to that step.
What happened when it rebooted?
Ans: Nothing showed up. Because when Volume Up is pressed while it is powered on, nothing shows up on the screen.
What was the original filename of the image you tried to flash?
Ans: Actually first time nvflash_gtablet_46_2010112600.zip (and this is before you provided the 7-step recipe - see post #6, 7, 8 of this thread) and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Maybe that was my mistake. I chose a wrong file. Later I flashed nvflash_gtablet_2010110500.zip. This recovered it enough that it shows the birds now, but soon after the screen turns black (goes into APX mode).
What version of clockworkmod do you have installed?
Ans: v08
Have you ever used ROM Manager?
Ans: No. What is it?
I really appreciate your help.
What happened at the end of step 3?
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 seconds after the flash starts.
When the flash was done did it say "Recovery Key detected" on the screen? If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
It sounds to me like you did the nvflash then tried to reboot into recovery.
Its unbelievable. Tonight when I powered it on it started booting up normal instead of going into the APX mode. I was glad. The stock UI came up, but some of my apps like Quadrant, File Expert etc were still there. It also notified me of the Update 3588. So I downloaded it and started installing it. Pretty soon it rebooted itself (sooner than I thought - I don't know if the remaining installation was supposed to happen after the reboot).
But instead of booting up into 3588 it is unfortunately gone back to the same old issue - the birds followed by black screen - aka APX mode. It never booted up after that. No matter how many times I tried to reboot, it goes into APX mode just like before. I don't know what caused it to complete bootup. One thing I noticed was that the battery was totally drained when I started tonight. I don't know if the drained battery somehow took it out of the APX mode. But now it has a little bit of charge because of hooking up to power supply. I have disconnected the power supply and will leave it in APX mode over night and try it again tomorrow when the battery would be totally drained and see if it boots up fully.
To answer your questions though:
What happened at the end of step 3?
The screen went black and after that it stayed black. No CWM.
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Yes, I did.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 secondsafter the flash starts.
Yes, I continued to hold it all the way until the flash completed and the screen went black and quite some time after that.
When the flash was done did it say "Recovery Key detected" on the screen?
I don't think it did.
If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
So I guess I need to give it another try. Tomorrow I will try to reboot the tablet again and if it continued to go into APX I will do the nvflash one more time.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
A black dark screen. No CWM or stock recovery.
It sounds to me like you did the nvflash then tried to reboot into recovery.
No at the time of nvflash I held the Volume UP button and nothing happened. Since then I have been trying to bootup or put it in CWM Recovery but only thing the tablet wants to do is go into APX mode.
So I guess my theory of "drained battery takes it out of the APX mode" is correct. I tried to reboot the tablet several times but it just kept on going into the APX mode until the battery was completely drained. And then it started booting up normally but it went into some installation (probably the stock 3588 that I had downloaded in the previous successful bootup). And then the green android with the exclamation sign came and the exclamation sign was rotating for a second or two and then stopped. And it looked like it was hung. I waited for a minute or two but nothing happened, so I pressed one of the buttons, I don't know if it was Menu or Back button, and all of a sudden clockworkmod recovery screen came up.
I have attached the picture of the screen. It still shows the green android with the exclamation sign in the middle of the screen, along with the CWM Recovery.
One other thing I noticed and I am not sure if it is normal is that if I choose say Reboot System Now from CWM menu and it shows like 10 entries with many No's and only one Yes. I can only use the volume Up + button to go down, if I try to go up using volume Down - button it does not go up. Is that normal? Is the only way to go is go down using Voume Up button in CWM menus? I have a feeling that my Volume Down button has gone crazy and it is not functioning properly and that is what is causing it to go into APX mode at the startup as well.
Anyway I first attempted "Apply SDCARD:update.zip" hoping that it might continue with the stock 3588 installation, but that failed. You can see the messages in the picture. Then I tried the Factory Reset and it was successful. I then rebooted the tablet. But now again it keeps on going up into APX mode. I will have to wait until tomorrow for it to completely drain battery again and then try to reboot again.
Any ideas? I know it is overwhelming and the behavior is very weird. At this point I am trying to bring it back to the stock firmware so that I can get this tablet replaced under warranty.
There are quite a few things that are not acting normal from what I see here.
Did you try to repartition 2048 and 0? If not, I would start with that then I would format everything and re-nvflash a stock ROM onto it. That might clear things up. If not you could be looking at a hardware reset.
Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
ergotelis said:
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
Click to expand...
Click to collapse
You'll probably need to flash a new recovery partition. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1950307
RaiderDuck said:
You'll probably need to flash a new recovery partition. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1950307
Click to expand...
Click to collapse
Thanks, but the problem is that this guy can get into the recovery with powering up+holding volume down button, if i understood well.but I can't!
ergotelis said:
Thanks, but the problem is that this guy can get into the recovery with powering up+holding volume down button, if i understood well.but I can't!
Click to expand...
Click to collapse
flasing a recovery is done via fastboot so you don't have to enter recovery but fastboot (hold power and volume down till it shows fastboot, then press up) .
look at this post: http://forum.xda-developers.com/showpost.php?p=33137046&postcount=10
Fix
ergotelis said:
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
Click to expand...
Click to collapse
hello i had this problem yesterday, it happens in neutrino rom to alot of people!
and btw i could not open recovery either
ill explain what i had to do
i had to use moto-fastboot and install a new recovery, basically your recovery is dead and your rom is unbootable
heres the steps
download the moto drivers and install
http://forum.xda-developers.com/attachment.php?attachmentid=1381183&d=1349549067
then download the motofastboot zip http://forum.xda-developers.com/attachment.php?attachmentid=1381414&d=1349555102
and create a new folder in C: (computer) called Android and then drag the files from the moto zip into android
Then download a new recovery http://www.mediafire.com/?6ww8wrjrdqq9m97
place the recovery.img into the android folder
now you have all the files needed to reflash your new recovery and fix your phone the whole idea is to reinstall recovery so you can access it and wipe and install the rom fresh again
now you need to do these steps
1) Attach your phone to the PC via USB (use a port closest to the power supply)
2) Reboot phone while holding volume down until you see "fastboot"
3) Press volume up to initiate fastboot
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type the following commands (no quotes, hit enter after each command)
6a) "cd c:/android"
6b) "moto-fastboot devices"
your CMD promt should show something like this
C:\Users\Me>cd c:/android
c:\Android>fastboot devices
TA20703SX9 fastboot
c:\Android>
now if that has all worked type the following phrases
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-clockwork-6.0.1.4-maguro.img
moto-fastboot reboot
now the phone should reboot, unplug the usb and pull battery out.
put battery back in and then try to boot into recovery like you normally would (power button + Vol Down)
and your new recovery should load!
from here you can wipe your whole system which i would reccomended as your current one is corrupt and install a new rom or reflash your current on onto a clean wipe. if you dont understand how to clean wipe do all of these steps, factory reset, clear cache, clean dalvik cache then go to mounts > storage and format data + format cache + format system
now install new rom and let it boot up, should bootloop a couple of times then start! if not unplug battery from phone and ask for further assitance
Pixelguy said:
1) Attach your phone to the PC via USB (use a port closest to the power supply)
2) Reboot phone while holding volume down until you see "fastboot"
3) Press volume up to initiate fastboot
Click to expand...
Click to collapse
Thank you for your help, the problem is exactly here, i put on the usb, i power up the phone by pressing the volume down, and the phone does nothing,doesn't show the fastboot,and after 10-15 secs starts rebooting again. This is my problem!
The only response from my phone is when powering up, and pressing the volume up, it says "starting rsd protocol support"
Is there any case that my volume down is dead?
ergotelis said:
Thank you for your help, the problem is exactly here, i put on the usb, i power up the phone by pressing the volume down, and the phone does nothing,doesn't show the fastboot,and after 10-15 secs starts rebooting again. This is my problem!
The only response from my phone is when powering up, and pressing the volume up, it says "starting rsd protocol support"
Is there any case that my volume down is dead?
Click to expand...
Click to collapse
unplug usb
remove battery, then put battery back in make sure phone off (no green light)
then hold power button and vol down at the same time for a few seconds
Fastboot should appear in white writing then press up volume and it should say starting rsd protocal or something similiar
then plug in usb and follow the steps i have written above
i do exactly what you said, but doesn't show fastboot. from switched off, if i press volume up with power button, i see the message "starting rsd protocol support" .but no fastboot option!
Is there any chance that you can access adb after bootscreen? than you can use "adb reboot recovery" to get there...
jorno88 said:
Is there any chance that you can access adb after bootscreen? than you can use "adb reboot recovery" to get there...
Click to expand...
Click to collapse
When i start up phone, the only combination possible to stop restarting is by pressing power+vol up to show that with RSD. There is no other option then selectable. Power + volume down does not work, doesn't show anything, has anyone of you experienced this thing?
If the only working option you have is RSD, then I'm afraid you're stuck with having to flash a stock SBF. I hope you know/remember exactly what stock version you had installed before any modding or flashing, because the SBF has to match exactly. Choose wisely and read up as much as you can before flashing.
I have over a year now with custom roms, and i can't remember which version i had. Why do i have to find exactly the version that i had? The latest stock version won't work with rsd? It will make it hard brick?If i manage at least to recover the fastboot menus etc it would be great!
I will later also try to open it, to see if the side button "volume down" is not working,.
I have another question, in your moto atrix, if you press on startup power+vol up, are you also seeing the "starting RSD" etc option??
ergotelis said:
I have over a year now with custom roms, and i can't remember which version i had. Why do i have to find exactly the version that i had? The latest stock version won't work with rsd? It will make it hard brick?If i manage at least to recover the fastboot menus etc it would be great!
Click to expand...
Click to collapse
Yes, flashing a wrong SBF will most likely hardbrick your device.
ergotelis said:
I have another question, in your moto atrix, if you press on startup power+vol up, are you also seeing the "starting RSD" etc option??
Click to expand...
Click to collapse
Can't try right now, but as far as I know, yes, that is a standard way to enter RSD mode.
thank you, so, i know that at least my phone responds to some instructions.
Is there anyone else to suggest me to do anything else?
IN rsd mode, (other than flashing a stock random rom with chance of hardbricking,)the phone can be read by usb, can i do anything there?
ergotelis said:
IN rsd mode, (other than flashing a stock random rom with chance of hardbricking,)the phone can be read by usb, can i do anything there?
Click to expand...
Click to collapse
Sadly no. The RSD mode can only ever be used to flash SBFs. That's it. Nothing less, nothing more.
I will now try to open it to see if vol down is not working well. If it does work, i will select a stock rom 1 year old and i will flash it using rsd, and whatever happens....:good:
I disassembled the phone, the button seems to operate fine(?).
I flashed with RSDlite the 2.3.6 version, the RSD stuck to waiting for phone to restart.
The phone restarted, the "unlocked" logo disappeared.
Starts normally, passes the red motorola logo, shows the graphic of AT&T, and after ~10sec starts restarting again. Bootloop again!
At boot, pressing power+vol up, i can still get the RSD support. Pressing power+vol down does nothing, I don't see any error messages, like the ones in hard brick.
What can i do now, any ideas please!!!
try this
ergotelis said:
I disassembled the phone, the button seems to operate fine(?).
I flashed with RSDlite the 2.3.6 version, the RSD stuck to waiting for phone to restart.
The phone restarted, the "unlocked" logo disappeared.
Starts normally, passes the red motorola logo, shows the graphic of AT&T, and after ~10sec starts restarting again. Bootloop again!
At boot, pressing power+vol up, i can still get the RSD support. Pressing power+vol down does nothing, I don't see any error messages, like the ones in hard brick.
What can i do now, any ideas please!!!
Click to expand...
Click to collapse
Yesterday I had a hard time getting my phone into fastboot mode, after loading a bad SV kernel,it only wanted to start the RSD protocol mode. I eventually got into fastboot by plugging into the wall charger, then removing and installing the battery while holding the vol button. When fastboot appears, unplug the charger to allow sd access.
Thanks for the suggestion, i tried even this,it didn't work. The funny thing is that it shows the battery charging level full screen if i connect the charger, as it starts.
I noticed also that when i press vol down now, it takes longer to start and continue to the moving red logo, it stays for a while stable red,feels like it is thinking whether to start or not lol (if i don't press vol down, on the power up the red moto logo immediately starts the classic "waving" effects)
Anyone having any kind of suggestion?I guess you don't, right?
Hello everybody,
since saturday I have a really big problem. Until now I tried to find a similar problem from an other person in the internet in order to fix mine but that was not possible.
So in my last hope I am now writing it down here. Hopefully someone can help me:
The phone was/is rooted and has TWRP as recovery installed (v3.21). The software is still the original EMUI.
On saturday my Huawei Honor 5x (Model KIW-L21) gave me the notification that there is an software update avaible. So I backuped everything with TWRP to my sd-card and copied it to the computer. After this I ran th eupdate. The update downloaded the new software, then rebootet to the recovery, installed the update.zip automaticly and rebootet again. Then there was written on the screen "Huawei software installing ... DO NOT unplug usb or press any key!". Also there was "0%" all the time. It did nothing. also the phone was not connected with usb.
After an hour I long pressed the power button. after two seconds there was the text "Warning: The powerkey is long pressed, please release powerkey to avoid system crash" displayed. I pressed it longer and the phone turned off.
Now I have the following problem. When the phone is turned off, I can:
press the power button: the phone starts, the "honor ... android" logo is shown but nothing more happens. ("fastboot devices" -> no devices found, "adb devices" -> device found but no permission to enter commands)
press the power button and the volume up button and the volume down button at the same time: normally this should take me in the recovery mode, mut it doesn't anymore. Instead the "EMUI" update screen is shown (see above "huawei software installing ..." with "0%") ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
press the power button and the volume up button at the same time: I get a huawei menu with three buttons: "reboot", "wipe user cache" and "factory reset". I tried both (wipe and reset) wich both finished without an error. But nothing changes ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
press the power button and the volume down button at the same time: I get an "eRecovery" menu from huawei with three buttons: "Reboot", "power off" and "Recover with latest software". The last button lets me connect to my wifi and then "searching for packages", with failes all the time. ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
This problem occures with and also without the sd-card. Also there is no "update.zip" or "update.app" on the sd-card.
I really hope somebody can help me. I only need to get into the recovery. If I am there I can recover the backup or install a new ROM. That would be no problem for me. But at the moment I get nothing :crying:
Or maybe a tool to reset the phone completly? to start over from the beginning?
greetings,
Christopher
PS.: Thanks for your efford.
PSS.: Sorry for my bad english, I really try my best and hope that you understand what I am trying to say.
Same problem here... Please help us :'(
christopher2007 said:
Hello everybody,
since saturday I have a really big problem. Until now I tried to find a similar problem from an other person in the internet in order to fix mine but that was not possible.
So in my last hope I am now writing it down here. Hopefully someone can help me:
The phone was/is rooted and has TWRP as recovery installed (v3.21). The software is still the original EMUI.
On saturday my Huawei Honor 5x (Model KIW-L21) gave me the notification that there is an software update avaible. So I backuped everything with TWRP to my sd-card and copied it to the computer. After this I ran th eupdate. The update downloaded the new software, then rebootet to the recovery, installed the update.zip automaticly and rebootet again. Then there was written on the screen "Huawei software installing ... DO NOT unplug usb or press any key!". Also there was "0%" all the time. It did nothing. also the phone was not connected with usb.
After an hour I long pressed the power button. after two seconds there was the text "Warning: The powerkey is long pressed, please release powerkey to avoid system crash" displayed. I pressed it longer and the phone turned off.
Now I have the following problem. When the phone is turned off, I can:
press the power button: the phone starts, the "honor ... android" logo is shown but nothing more happens. ("fastboot devices" -> no devices found, "adb devices" -> device found but no permission to enter commands)
press the power button and the volume up button and the volume down button at the same time: normally this should take me in the recovery mode, mut it doesn't anymore. Instead the "EMUI" update screen is shown (see above "huawei software installing ..." with "0%") ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
press the power button and the volume up button at the same time: I get a huawei menu with three buttons: "reboot", "wipe user cache" and "factory reset". I tried both (wipe and reset) wich both finished without an error. But nothing changes ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
press the power button and the volume down button at the same time: I get an "eRecovery" menu from huawei with three buttons: "Reboot", "power off" and "Recover with latest software". The last button lets me connect to my wifi and then "searching for packages", with failes all the time. ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
This problem occures with and also without the sd-card. Also there is no "update.zip" or "update.app" on the sd-card.
I really hope somebody can help me. I only need to get into the recovery. If I am there I can recover the backup or install a new ROM. That would be no problem for me. But at the moment I get nothing :crying:
Or maybe a tool to reset the phone completly? to start over from the beginning?
greetings,
Christopher
PS.: Thanks for your efford.
PSS.: Sorry for my bad english, I really try my best and hope that you understand what I am trying to say.
Click to expand...
Click to collapse
suzushima said:
Same problem here... Please help us :'(
Click to expand...
Click to collapse
to enter fastboot mode
1. Place the device in fastboot mode:
Turn off the device. (then wait for at least 2 seconds) For a mobile phone, press and hold the volume down and power keys simultaneously for at least 10 seconds (for a tablet, press and hold the volume up and power keys).
2. If the above operations do not switch the device to fastboot mode, please try the following steps:
Turn off the device. (then wait for at least 2 seconds) Then insert the USB cable and press and hold the volume down and power keys simultaneously for at least 10 seconds.
Step 2 worked for me every time
Arobase40 said:
AGAIN AND AGAIN, when you receive an update notification you MUST first flash back to stock recovery or it won't update with TWRP !!!
- To recover a stock recovery you need to boot onto download mode/your bootloader mode (Power+Volume Down) : plug your phone to your computer and type "fastboot flash recovery recovery.img".
From there you will loose your connexion with your computer. So unplug your phone and reboot manually holding down the Power button for some seconds.
If the system ever update your phone, BE VERY PATIENT !
The above note should probably part of a sticky !!!
If you don't get back to your Home screen and if you need TWRP back, reboot again onto download mode/your bootloader mode (Power+Volume Down) : plug your phone to your computer and type "fastboot flash recovery twrp.img" (or whatever the custom recovery name).
Click to expand...
Click to collapse
The problem a lot of people were having is TWRP flashed enough of the update that they lost custom recovery and had no way to get to the bootloader / fastboot ... that's why I posted the instructions above and in about 4 other threads.
Did you ever get your phone updated ?
Arobase40 said:
AGAIN AND AGAIN, when you receive an update notification you MUST first flash back to stock recovery or it won't update with TWRP !!!
Click to expand...
Click to collapse
I did not knew this one. Thanks a lot.
Thanks to @clsA I found the stock recovery here and I will try it:
https://www.androidfilehost.com/?w=files&flid=49383
clsA said:
1.Turn off the device. (then wait for at least 2 seconds) For a mobile phone, press and hold the volume down and power keys simultaneously for at least 10 seconds (for a tablet, press and hold the volume up and power keys).
2. If the above operations do not switch the device to fastboot mode, please try the following steps:
Turn off the device. (then wait for at least 2 seconds) Then insert the USB cable and press and hold the volume down and power keys simultaneously for at least 10 seconds.
Click to expand...
Click to collapse
Working great thanks a lot!
"fastboot & rescue mode" with a working usb connection.
What is the next step? If I now flash the stock recovery, does the phone manages to finish the system update?
Or should I flash the twrp recovery and not the stock revocery?
greetings,
Christopher
EDIT:
I flashed the stock recovery and also the twrp recovery. both times i startet the phone and hoped the installation of the new software will go on. But it didn't.
So my problem is still resistant. so what can I do? How do I stop the update from blocking my recovery? I do not need the update. maybe I can reset my device with the fastboot access somehow?
christopher2007 said:
I did not knew this one. Thanks a lot.
Thanks to @clsA I found the stock recovery here and I will try it:
https://www.androidfilehost.com/?w=files&flid=49383
Working great thanks a lot!
"fastboot & rescue mode" with a working usb connection.
What is the next step? If I now flash the stock recovery, does the phone manages to finish the system update?
Or should I flash the twrp recovery and not the stock revocery?
greetings,
Christopher
EDIT:
I flashed the stock recovery and also the twrp recovery. both times i startet the phone and hoped the installation of the new software will go on. But it didn't.
So my problem is still resistant. so what can I do? How do I stop the update from blocking my recovery? I do not need the update. maybe I can reset my device with the fastboot access somehow?
Click to expand...
Click to collapse
All the full updates are in the file depot
Use stock recovery plus the full update for your version.
You have to hold volup + voldown + power to start the update
Refresh TWRP / Root and your good to go
Sent from my KIW-L24 using Tapatalk
clsA said:
All the full updates are in the file depot
Use stock recovery plus the full update for your version.
You have to hold volup + voldown + power to start the update
Refresh TWRP / Root and your good to go
Click to expand...
Click to collapse
I found the stock recovery at https://www.androidfilehost.com/?w=files&flid=51004 but I have no idea what update I must use and how to use it.
Could you please give me a concrete link with a little introduction? Do I have to copy the update file to my sd-card? or do I have to use the "fastboot update *" command?
(Most of the files are for "KIW-L24" but I have a "KIW-L21" ... is there a significant difference? Od do I can use also the other files?)
Also, don't I have to stop the wrong update first?
greetings,
Christopher
EDIT:
I tried these "UPDATE.APP":
http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684
http://www.androidvillaz.com/2016/0...honor-5x-to-stock-lollipop-firmware-b130.html
both did not work. I copied them into the "dload" folder in the root of the sd-card and started the phone with volup+coldown+power.
The only thing the phone said was "Software install failed! ... Press powerkey to conrifm ... Shutdown system now".
christopher2007 said:
I found the stock recovery at https://www.androidfilehost.com/?w=files&flid=51004 but I have no idea what update I must use and how to use it.
Could you please give me a concrete link with a little introduction? Do I have to copy the update file to my sd-card? or do I have to use the "fastboot update *" command?
(Most of the files are for "KIW-L24" but I have a "KIW-L21" ... is there a significant difference? Od do I can use also the other files?)
Also, don't I have to stop the wrong update first?
greetings,
Christopher
EDIT:
I tried these "UPDATE.APP":
http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684
http://www.androidvillaz.com/2016/0...honor-5x-to-stock-lollipop-firmware-b130.html
both did not work. I copied them into the "dload" folder in the root of the sd-card and started the phone with volup+coldown+power.
The only thing the phone said was "Software install failed! ... Press powerkey to conrifm ... Shutdown system now".
Click to expand...
Click to collapse
if the update.app doesn't work you'll have to flash TWRP and the Stock Rom and wait like everyone else that's stuck trying to update the L21
clsA said:
if the update.app doesn't work you'll have to flash TWRP and the Stock Rom and wait like everyone else that's stuck trying to update the L21
Click to expand...
Click to collapse
The only way I know to flash a ROM, is to go over TWRP.
So I now did the following:
Phone power off
connect to pc
voldown+power
in the fastboot flash the recovery from twrp
shutdown
copy the "customromtemplate-5x-plk21-b130-r3.zip" to the sd-card
volup+coldown+power what normally starts twrp, but only the huawei update manager is shown
I only need twrp, no update and nothing else.
What options do I have left, because "flash a ROM" is not working ...
How can I stop this terrible update that is blocking my twrp?
greetings,
Christopher
christopher2007 said:
The only way I know to flash a ROM, is to go over TWRP.
So I now did the following:
Phone power off
connect to pc
voldown+power
in the fastboot flash the recovery from twrp
shutdown
copy the "customromtemplate-5x-plk21-b130-r3.zip" to the sd-card
volup+coldown+power what normally starts twrp, but only the huawei update manager is shown
I only need twrp, no update and nothing else.
What options do I have left, because "flash a ROM" is not working ...
greetings,
Christopher
Click to expand...
Click to collapse
are you flashing TWRP ?
you enter recovery with Volume up and Power
in TWRP you choose Install then choose customromtemplate-5x-plk21-b130-r3.zip
swipe to flash when it's done reboot
and your rom should load
clsA said:
are you flashing TWRP ?
you enter recovery with Volume up and Power
in TWRP you choose Install then choose customromtemplate-5x-plk21-b130-r3.zip
swipe to flash when it's done reboot
and your rom should load
Click to expand...
Click to collapse
I flashed TWRP using "kiwi_twrp_3-21_recovery.img". I also used this one last time (one month ago) and it worked then and also now.
Flashing was successful, but when I press volup+power I get a huawei menu.
At the top there is the "EMUI" circle and below there are three buttons:
Reboot system now
Wipe data/factory reset
Wipe cache partition
I can move around in this little menu by using the volume keys.
But this is not TWRP.
And normally I enter the recovery by using volup+voldown+power. But this is currently blocked by the update progress from huawei.
greetings,
Christopher
christopher2007 said:
I flashed TWRP using "kiwi_twrp_3-21_recovery.img". I also used this one last time (one month ago) and it worked then and also now.
Flashing was successful, but when I press volup+power I get a huawei menu.
At the top there is the "EMUI" circle and below there are three buttons:
Reboot system now
Wipe data/factory reset
Wipe cache partition
I can move around in this little menu by using the volume keys.
But this is not TWRP.
And normally I enter the recovery by using volup+voldown+power. But this is currently blocked by the update progress from huawei.
greetings,
Christopher
Click to expand...
Click to collapse
You still have stock recovery
Flash TWRP -
fastboot flash recovery kiwi_twrp_3-21_recovery.img
Do not reboot the phone
Hold power plus volup and TWRP should load.
Now flash your rom
Sent from my KIW-L24 using Tapatalk
clsA said:
You still have stock recovery
Flash TWRP -
fastboot flash recovery kiwi_twrp_3-21_recovery.img
Do not reboot the phone
Hold power plus volup and TWRP should load.
Now flash your rom
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
C:\adb>fastboot flash recovery kiwi_twrp_3-21_recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (45196 KB)...
OKAY [ 1.442s]
writing 'recovery'...
OKAY [ 0.703s]
finished. total time: 2.148s
I now flashed this more then ten times ... but with power+volup I still get the EMUI menu.
christopher2007 said:
C:\adb>fastboot flash recovery kiwi_twrp_3-21_recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (45196 KB)...
OKAY [ 1.442s]
writing 'recovery'...
OKAY [ 0.703s]
finished. total time: 2.148s
I now flashed this more then ten times ... but with power+volup I still get the EMUI menu.
Click to expand...
Click to collapse
Are you rebooting from the fastboot screen?
From the white boot loader screen hold volume up and power for 15 seconds
Sent from my KIW-L24 using Tapatalk
clsA said:
Are you rebooting from the fastboot screen?
From the white boot loader screen hold volume up and power for 15 seconds
Click to expand...
Click to collapse
The last six hours I tried to fix my phone ... again. One thing I did really helped a little:
Target1920 said:
http://forum.android.com.pl/topic/205126-instalacjaodzyskiwanie-systemu-rom-za-pomoca-fastboot/
This is the polish version of manual, I will write you how to do it:
1. Download ADB and Fastboot
2. Extract to c:/adb
3. Download from this thread firmware for you (extracted version!) http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684 If you have problem what firmware you have to install, take look at the back side of phone, at the down you will se KIW-L21 or 24 (or another). Copy all files to adb folder
4. Rund adb program
5. Write in the command line: cd c:/adb
6. Connect phone to usb to download mode (power and vol- combination)
7. Write in fastboot command: fastboot flash recovery recover.img (or recovrey .img, see the file and type it name) - wait for install
8. And now: If the flash is succesfull, reboot the phone to recovery (power and volume+) and wipe all data. Phone have to work.
But if flash is not succesfull, plug again usb with download mode
9. Write this commands: fastboot flash cust cust.img -wait for install
and: fastboot flash system system.img -also wait, system.img can took a while
10. Now you will enter recovery and wipe all data
11. Again plug usb cable and install firmware with those commands:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
With this I am not able to start my phone again. It will boot normally and I have a clean android. No userdata and no root.
So I now did the same like last month:
Unlock OEM -> not necessary, because it is already unlocked
install twrp with fastboot
reboot to twrp and there it is again
I did exactly what you said and also I did exactly the same thing I did last month but both times there is the same result: TWRP will not show up.
The "stock recovery" is blocking twrp in some sort of way. I can do whatever I whant ... volup+power out of the fastbook mode, or with "adb reboot recovery", or other ways ... twrp will not show up.
How is this possible? I also tried different twrp images. (The "kiwi_twrp_2-27_recovery.img" and "kiwi_twrp_3-21_recovery.img" out of your repository, and also the "twrp-3.0.0-0-kiwi.img" and "twrp-3.0.2-0-kiwi.img" from the twrp website itself ... always the same result: no twrp)
I am really at the end of my knollage
greetings,
Christopher
christopher2007 said:
The last six hours I tried to fix my phone ... again. One thing I did really helped a little:
With this I am not able to start my phone again. It will boot normally and I have a clean android. No userdata and no root.
So I now did the same like last month:
Unlock OEM -> not necessary, because it is already unlocked
install twrp with fastboot
reboot to twrp and there it is again
I did exactly what you said and also I did exactly the same thing I did last month but both times there is the same result: TWRP will not show up.
The "stock recovery" is blocking twrp in some sort of way. I can do whatever I whant ... volup+power out of the fastbook mode, or with "adb reboot recovery", or other ways ... twrp will not show up.
How is this possible? I also tried different twrp images. (The "kiwi_twrp_2-27_recovery.img" and "kiwi_twrp_3-21_recovery.img" out of your repository, and also the "twrp-3.0.0-0-kiwi.img" and "twrp-3.0.2-0-kiwi.img" from the twrp website itself ... always the same result: no twrp)
I am really at the end of my knollage
greetings,
Christopher
Click to expand...
Click to collapse
First off thanks for the very informative post.
Without actually having the phone in my hands I'm also stumped at what to try next.
After flashing TWRP and still in the boot loader unplug the USB before you reboot with power and volume up.
That's all I can think of right now
Sent from my KIW-L24 using Tapatalk
--
clsA said:
First off thanks for the very informative post.
Without actually having the phone in my hands I'm also stumped at what to try next.
After flashing TWRP and still in the boot loader unplug the USB before you reboot with power and volume up.
That's all I can think of right now
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
I must thank you for all your help
So I now read some more articles and tried some things. So there are old problems solved, but also new problems came up:
For me it is no longer possible to flash a recovery that is permanent. I have no idea why but I am ignoring it, because I can start the phone with voldown+power into bootloader and then use a usb-connection to enter the following command:
fastboot boot twrp-3.0.2-0-kiwi.img
Click to expand...
Click to collapse
So i can enter twrp temporary and because I do not need TWRP this often, that is ok for me.
BUT:
with the extracted "UPDATE.APP" and flashing some "*.img" files manually (see my last post), I have a more or less working "L21C432B130" version of android.
So now there is everything original (recovery, system, ...).
The update to "L21C432B140" is still not working. But that is also something I can live with.
So now I whant to restore my old system in order to have my old data/apps/... .
So I enter my temporary TWRP, go to Restore and select my old backup. Then the restore starts. Restoring EFS, Restoring efs2, Restoring Recovery, Wiping System and Formatting System using make_ext4fs. All of this in this order are successful. But the last operation "Restoring Data" failes with the following error message:
extractTarFork() process ended with error 255
Click to expand...
Click to collapse
So I searched on xda and found out, that this could be ANYTHING. I tried five or six different methods in order to fix it. In the end I am not sure what really fixxed it, but now I can restore my old update without any error. The phone now runs and I have all my old data.
There are four main differences on my phone to the time before I tried that damn update:
1. I have less internal storage
2. I have no TWRP permanently avaible
3. I can not Factory-Reset
4. I can not use a "UPDATE.APP" inside a "dload" folder on the sdcard
(the last two things always failes)
But as long as the android system now runs smooth again I can live with these things.
Is there maybe anything else I should be careful? maybe a known bug/problem that I have not seen yet?
The reason why I wanted to update in the first place was, that I have problems with my sd-card.
Some Apps do not allow to use the external storage. Easy Voice Recorder is the main problem. But also the Call Recorder has problems with it.
Is this a well known bug? Does a update helps? And if so, how do I update? (Now I know how to rescue my phone, so I could try it again xD )
Or does this problem gets solved with an custom ROM? If so, what good custom ROMs are out there for the honor 5x?
Or is this a problem that is not possible to fix on the honor 5x? Because these apps does not have this problem on my HTC One M9 ...
And thanks again so much for all your help
greetings,
Christopher
christopher2007 said:
I must thank you for all your help
So I now read some more articles and tried some things. So there are old problems solved, but also new problems came up:
For me it is no longer possible to flash a recovery that is permanent. I have no idea why but I am ignoring it, because I can start the phone with voldown+power into bootloader and then use a usb-connection to enter the following command:
So i can enter twrp temporary and because I do not need TWRP this often, that is ok for me.
BUT:
with the extracted "UPDATE.APP" and flashing some "*.img" files manually (see my last post), I have a more or less working "L21C432B130" version of android.
So now there is everything original (recovery, system, ...).
The update to "L21C432B140" is still not working. But that is also something I can live with.
So now I whant to restore my old system in order to have my old data/apps/... .
So I enter my temporary TWRP, go to Restore and select my old backup. Then the restore starts. Restoring EFS, Restoring efs2, Restoring Recovery, Wiping System and Formatting System using make_ext4fs. All of this in this order are successful. But the last operation "Restoring Data" failes with the following error message:
So I searched on xda and found out, that this could be ANYTHING. I tried five or six different methods in order to fix it. In the end I am not sure what really fixxed it, but now I can restore my old update without any error. The phone now runs and I have all my old data.
There are four main differences on my phone to the time before I tried that damn update:
1. I have less internal storage
2. I have no TWRP permanently avaible
3. I can not Factory-Reset
4. I can not use a "UPDATE.APP" inside a "dload" folder on the sdcard
(the last two things always failes)
But as long as the android system now runs smooth again I can live with these things.
Is there maybe anything else I should be careful? maybe a known bug/problem that I have not seen yet?
The reason why I wanted to update in the first place was, that I have problems with my sd-card.
Some Apps do not allow to use the external storage. Easy Voice Recorder is the main problem. But also the Call Recorder has problems with it.
Is this a well known bug? Does a update helps? And if so, how do I update? (Now I know how to rescue my phone, so I could try it again xD )
Or does this problem gets solved with an custom ROM? If so, what good custom ROMs are out there for the honor 5x?
Or is this a problem that is not possible to fix on the honor 5x? Because these apps does not have this problem on my HTC One M9 ...
And thanks again so much for all your help
greetings,
Christopher
Click to expand...
Click to collapse
from your current state you can try flash recovery with TWRP by choosing install / image / your version of TWRP / choose recovery / swipe to flash
Now choose reboot / recovery
As for the sdcard try the sdcard fix for kit Kat in the play store. It works for some older apps.
Sent from my KIW-L24 using Tapatalk
Arobase40 said:
If you mean getting my phone updated to KIW-L21 B140, no I still don't get it !
But I did try with KIW-L24 B151 with the result I already mentioned previously : almost bricked... ^^
But I always managed to get into Bootloader/Fastboot to flash back any kind of recovery...
Click to expand...
Click to collapse
clsA said:
All the full updates are in the file depot
Use stock recovery plus the full update for your version.
You have to hold volup + voldown + power to start the update
Refresh TWRP / Root and your good to go
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
So i have this issue too. im so stupid for doing this. I can go into fastboot mode and i flashed stock recovery and when i rebooted into recovery it still said that it was updating the firmware. I flashed twrp after that and it had the same message. am i doing something wrong or is it my phone? I tried rebooting into bootloader using adb but only fastboot will reconize my phone so adb also wont work. could you guys maybe help me?
Edit: Yessss. i got it using the temporary command. Thank you guys all for your help. it was so stupid of me to flash it with twrp still on it. Thank you all very much
I am new to android and this forum and viola, within few days, i was successfully able to practically ruin an android TV box. I did something wrong with the build.prop, and now it is stuck at android logo. Logcat shows signs of a loop. Something regarding memory allocation. I restored the build.prop and still the problem remains. I have no clue why that happens.
.
Luckily I found a matching update.zip file. But all the tutorials to flash it needs me to have something to be done from the device’s side. But my device wont get to recovery mode by any way. (Don't know exact key combo, tried the usual combos. None works. Tried “reboot recovery”. Reboots to that android logo again and stuck.
.
So, in short, the device is like dead and all that I can get right now is adb access. Can I use that update.zip just with this?
.
This forum has been really awesome, go to try many things. Thank you.
@nirmalscaria
Phone must be successfully booted into Recovery Mode to flash an Update.Zip via ADB what requires phone's boot-loader got already unlocked.
jwoegerbauer said:
@nirmalscaria
Phone must be successfully booted into Recovery Mode to flash an Update.Zip via ADB what requires phone's boot-loader got already unlocked.
Click to expand...
Click to collapse
That is sad. I tried all that I know to get to recovery mode.
1. There is no reset button.
2. The key press combo method :
——— Don’t know the exact combo for recovery
——— Tried the normal key codes, no response.
——— Is there any way to figure out the combo using adb? Is there any chance that
——-- there is some file in the device that indicate the combo? (I can do push and pull)
3. “reboot recovery” and “reboot fastboot” does restart the device but its again normal boot attempt.
.
Anything to do now? It is sad to throw it away.