Is my device soft bricked?
I flashed PhilZ-cwm6-XXLTA-ATL-5.15.0.tar which worked, then I started up the phone and tried to flash CWM 6.0.4.3 touch using ROMManager, the process was a "success" but after the reboot attempt the phone was unable to boot OS nor is it able to go to Recovery mod. I am still able to enter download mod.
I tried flashing PhilZ-cwm6-XXLTA-ATL-5.15.0.tar again, but it didn't work. I can detect my phone in ADB devices and in Odin3. I am currently searching for a stock ROM for my device.
If anyone has experienced this before and knows the result already, could you tell me whether my device is lost or I can revive it somehow? Thanks in advance.
EDIT: My phone doesn't seem to go into recovery, stuck at manufacturer Logo(Not restarting); but in ADB devices I can see it in recovery mod and can see its contents in adb devices.
Solved: It booted normally after deleting update.img and cache via ADB.
Thread completed as user already founded the solution.
Thread closed
Related
Hey guys, just wondering if any of you know a fix for this on my WIFI only xoom
Using the guide from here about Wifi Unlocking and rooting Ive unlocked the bootloader on my Xoom. Ive flashed Clockwork and am up to the part where I have to boot into clockwork recovery to install the root tool, however there is no option to enter 'Android Recovery' when I push the Down key on the dual core boot screen, during the first 3 seconds of the first boot after flashing. Theres NVFlash, fastboot and another but no recovery.
I am able to get into recovery via the ADB REBOOT RECOVERY command however I dont get into Clockwork and am stuck on a screen with a green android logo in the center. Pushing any manner of buttons does nothing and the tab automatically resets after 2 or 3 mins in that mode. Has anyone else seen this and know of a fix?? Ive since learned that if you allow the tab to boot into honeycomb it installs the stock recovery and you have to start over by reflashing clockwork, as stated tho no Android Recovery option appears. Any ideas?
recovery is not installed properly.
put your recovery file in fastboot folder
rename it to recovery.img
in fastboot run: fastboot flash recovery recovery.img
this recovery file is not zip file but .img file(rename it for ease of typing)
I've done it exactly like that, 3 times now. all the messages seem to indicate its flashed correctly. Heres what it says on the tab:
Flashing allowed for partition recovery
OneWire: Charger not connected
Battery Level 82%
Flashing Stormgr partition recovery Status:- done!
And i get the OKAY's in the terminal box as well. Still no Android recovery menu. I read in a dev post reguarding this same procedure a few other ppl had the same issue. I was hoping sum1 had a fix
So basically I rooted my LG p500h and installed a ROM through ROM manager, the thing is that when I rebooted the device I got stuck at the analog to the Android logo that shows up after the LG logo. I flashed an stock ROM through KDZ update software but after the program did it's thing, I did hard reset the phone and got the same problem: won't boot up and forever stuck at the android logo. I can get to emergency mode tho and when usb connected will show the battery charging up. I have searched solutions and I haven't reached one yet so everyone told me to post here and ask for some help! I hope it's not the end of my device Any help is sincerly appreciated!
Secretagogo said:
So basically I rooted my LG p500h and installed a ROM through ROM manager, the thing is that when I rebooted the device I got stuck at the analog to the Android logo that shows up after the LG logo. I flashed an stock ROM through KDZ update software but after the program did it's thing, I did hard reset the phone and got the same problem: won't boot up and forever stuck at the android logo. I can get to emergency mode tho and when usb connected will show the battery charging up. I have searched solutions and I haven't reached one yet so everyone told me to post here and ask for some help! I hope it's not the end of my device Any help is sincerly appreciated!
Click to expand...
Click to collapse
Much as I hate to say it, ROM Manager is not friendly to our devices. Secondly, stay away from KDZ too. But don't panic. You do have options. You will need to use either ADB and dd commands, or fastboot and fastboot mode. Since you can't boot, most likely the ADB way won't work ATM. Both methods require either the ADB binaries or the Android SDK. An alternate method would be Android Flash Recovery. There is a link in my signature. There are complete instructions in the download. On thing, put the device in fastboot mode before connecting it to the PC.
Enter into emergency mode, BACK+VOL UP+POWER
then follow this guide to flash recovery: http://forum.xda-developers.com/showpost.php?p=15217609&postcount=3
After that enter into recovery, HOME+VOL DOWN+POWER
then wipe data/factory reset, wipe dalvik cache, wipe cache, format system then flash a rom of your choice like oxygen, cm9 present in development section.
Then reboot
shinobisoft said:
Much as I hate to say it, ROM Manager is not friendly to our devices. Secondly, stay away from KDZ too. But don't panic. You do have options. You will need to use either ADB and dd commands, or fastboot and fastboot mode. Since you can't boot, most likely the ADB way won't work ATM. Both methods require either the ADB binaries or the Android SDK. An alternate method would be Android Flash Recovery. There is a link in my signature. There are complete instructions in the download. On thing, put the device in fastboot mode before connecting it to the PC.
Click to expand...
Click to collapse
Odd enough, I plugged in the device to the computer after the USB drivers got installed (following all the instructions given by the files provided), I went to the bathroom and left the cell phone unattended, just to find it boot up! weird. Anyways your advice was very helpful and very clear! Now I will figure out how to get my old ROM for my country. Thanks again!
Hello guys sorry about this I'm new to all this. Okay so I unlocked the boot loader and rooted my tablet successfully . I installed cwm and I updated to 6.0.3.1 because it said there was a new update. But when I try to boot my tablet in to recovery mode or boot menu it says entering recovery kernel image but just stays there . I am not able to go on fastboot boot menu recovery mode anything . I am able to use the tablet normally tho but I am not able to go on recovery mode. Did I do somethingwrong or what should i do? I would appreciate some help. Thanks
Re :
Hello,
Did you find a solution ? I have exactly the same problem. My A700 is stuck on this message : "entering recovery kernel image".
I've tried to reinstall Recovery with CMW but the problem is the same !
I hope you have a solution for me
pH
Well, I am going to guess, if you can't do a fastboot flash recovery xxxxxxx.img, and it says successful, but you can't boot immediately to recovery, then more than likely the recovery partition is damaged. And unfortunately, there is little you can do for it except mainboard replacement.
You can try fastbooting a stock recovery image (you can find them here in the forums, just search "stock recovery". Should be ICS and JB available.
If that don't work, Acer Service Center. Acer won't give us the SBK (secure bootloader key) to be able to use NVFlash to diagnose/possibly repair partitions.
I would always advise to NOT USE the Rom Manager app to do a recovery. Reason, you really have 0 idea what it is installing, or who made it.
Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?
stanglx said:
Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?
Click to expand...
Click to collapse
All has been fixed except for #2. Cant get CWM to stick... but for 1 and 3:
OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS
Same Problem
I'm having the same problem with CWM reverting to stock recovery after system boot. I didn't see your post until after I posted my own thread -- I probably should have titled it specifically about the stock recovery reversion so others will find it. Anyway, not that there's at least one other person besides me having this problem, I'm less worried that it's just me being stupid. Although that's always a possibility. Maybe someone will come along and help.
Recovery Reversion Problem Solved
Okay, I solved my recovery reversion problem -- I wasn't using either a custom boot.img or the Beta SuperSu (currently BETA-SuperSU-v2.42.zip), one of which is needed to keep root on Lollipop. (Apparently I knew this a month ago when I first went to 5.0.)
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?