Related
Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,
Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351
Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.
I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk
Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!
?
Any other ideas?
Thanks!
Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!
Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*
"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results
Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!
Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work
So, I recently acquired an Incredible, the second one I've owned. The first one I rooted, turned S-off and installed CM7 with zero difficulties, after that I rooted/flashed my Xperia Play CDMA with all the issues that accompany that device. (after the ease with which I modded my first DINC, the hoops through which I had to jump to unlock my bootloader blew my mind)
This DINC, though, refuses to clear user data. Even after multiple wipes via CWM, and multiple updates using the PB31IMG method, user data remains. Attmepts to preform a factory reset via HBOOT result in a balck screen with a red triangle and exclamation point.
I tried to install MIUI, thinking maybe a fresh rom would fix it, but it gets stuck at the room splash screen.
I've even tried recovering a clean CM7 install from my old incredible, but it gets stuck in a bootloop at the rom splash, same story trying to flash the .zip in recovery.
I've seen a few threads that deal with a few of these symptoms, but not the issue as a whole
Thanks in advance for any answers you guys have!
Cheers
I found a solution, finally. Admittedly, it was a bit drastic, but it worked, nonetheless.
I ended up disassembling both DIncs and putting the motherboard of the working device (with the smashed screen) into the device that was unable to format /data.
It was a bit touch and go for a bit, but my new DIY refubished phone is up and running.
Thanks for the help guys!
What error do you get? Can you upload the logs from /cache/ recovery after trying to wipe?
Sent from my Galaxy Nexus using Tapatalk 2
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
mattdubuc said:
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
Click to expand...
Click to collapse
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
tiny4579 said:
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
The red triangle happens when you try to do a factory reset from hboot wile on cwm recovery. If you really need to do a factory reset, you will need to flash to the stock recovery first. http://dinc.does-it.net/Recoveries/Stock_4.08.605.15/PB31IMG.zip Then if it works or even if not flash back to cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.
The weird thing is, that even after flashing PBG31IMG via HBOOT I'm retaining all the previous user data. I've tried formatting the internal drive, using a few different versions of the image, even manual formatting of /data via CWM, which only gives me an error. the same error as when I tried to restore a nandroid from my functioning DINC.
tiny4579 said:
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
mattdubuc said:
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
Click to expand...
Click to collapse
That should be fine. Try to wipe data in cwm again just so it logs it.
Sent from my Galaxy Nexus using Tapatalk 2
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
zslashy said:
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
Click to expand...
Click to collapse
Same error if you flash stock GB sense and factory reset from recovery? You have the errors when booting and the apps are still there?
Sent from my Nexus 7 using Tapatalk 2
Thank you for reply, I solved reset issue by installing Amon Ra recovery. But the problem with apps still exists, it looks like system is restoring back up after reboot, I can do everything with system but after reboot it's like it was before with no changes made. Additionally, it seems that the problem is with emmc, just because when I delete EVERYTHING on it, after restart all files appear again!
I'm also getting an error when I try to manually format the data partition under >mounts and storage in CWM, I'm assuming that may be to blame for retained user data?
When I run show log after running only a manual /data format it displays:
6 black groups
32768 blocks per group. 32768 fragments per group
8112 inodes per group
superblock backups stored on blocks:
32768. 98304. 163840
The filesystem already has a journal,
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Failure while running mke2fs
Error formatting /data!
mtd: succesfully wrote block at 0
I:Set boot command ""
I have no idea what that means really, or even if it's pertinent.
I had to remove the user info (owner data, phone number, etc) from my inc after canceling my contract with verizon. After about 25 different attempts to wipe it, I finally found something that worked (at least for me)
Tried running the RUU, could not reboot into HBOOT (version error)
Tried the RUU again, this time starting it after manually booting the phone to HBOOT. Got a little farther than before, but still errored out. Did not work. Disconnected phone, pulled battery, rebooted to HBOOT.
Factory reset in HBOOT got me stuck on the stock recovery screen. Battery pulled, could not boot.
Flashed CWM in HBOOT (by renaming to PB31IMG.zip), was able to get into CWM recovery.
Tried to flash the 2nd GB OTA in CWM, did not take. Every option I clicked in CWM gave me about 7 errors after sitting on the logo for a moment. Battery pull, reboot. Boots into CM9. >.<
Booted to my rom, saw about 300 force closes. Tried to reflash CWM from Rom Manager, got a bunch of force closes. Updated Rom Manager from market, reflashed CWM, and this time it worked.
Rebooted to CWM, wipe data/cache/dalvik, reboot.
This time I booted in CM9, but to the initial ICS set up (click next to begin, wireframe pic of Andy)
After skipping thru initial setup, I checked Settings>About Phone>Status. My phone number was removed, network is Unknown, and all my data was removed. Activation prompt appears on each boot.
Not sure if this will help, but worth a try. I think that the HBOOT factory reset is what cleared my data, and then I just needed to fix CWM so I could get back to a working ROM.
Yeah that's what I did in june except I just got service on mine but I would think that would help getting your data out forever. If that does not work I wouldn't know what to tell u besides grab a magnet. Lol
Sent from my Droid Incredible using xda premium
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
BigEdgar said:
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
Click to expand...
Click to collapse
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
cmlusco said:
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
Click to expand...
Click to collapse
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
BigEdgar said:
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
Click to expand...
Click to collapse
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
cmlusco said:
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
Click to expand...
Click to collapse
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
BigEdgar said:
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
Click to expand...
Click to collapse
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
BigEdgar said:
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
Click to expand...
Click to collapse
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
BigEdgar said:
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
Click to expand...
Click to collapse
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Are you able to use adb now? If you can, i have another sugestion i came across in another thread. A guy said he could not access, format, or use his data partition. He claims he fixed it by adb pulling the file system from a working inc, and adb pushing the files to the borked inc, fixing it. If you can get adb to stay connected long enough to push the files it might be worth a try.
cmlusco said:
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Click to expand...
Click to collapse
Thanks again for the suggestions.
I tried that but it's pretty much the same results.
HBOOT--> Factory Reset --> Screen with green arrows --> Red triangle with Exclamation point --> - Power button + Up Volume to get to the System Recovery menu --> Reboot:
Phone hangs on the black/white "htc Incredible" splash screen
One other odd note - if I do this same factory reset process with the USB cable *unplugged*, the instead of hanging on the black/white splash screen, it just goes into an infinite loop (black/white splash screen --> HTC quietly brilliant screen --> droid eye --> back to the black/white splash screen). FWIW this isn't new behavior, I just forgot to mention it earlier. In fact this is what the phone started doing once Verizon pushed the OTA update that screwed up the phone in the first place (there are a number of threads on this over at HTC and VZW forums, but their solutions aren't working for me).
I think this thing is a brick. If anyone has any recommendations for tools that can be used to analyze the partitions on a phone that won't boot, let me know. Otherwise this thing is getting sold for parts : )
Ok, some more progress. Most importantly, I learned that adb has a shell! I obviously didn't RTFM well enough.
Anyways, with the shell I was able to verify that the partitions on the phone are accessible (at least from a Windows machine) and I can, in fact, write files to the device (using "adb push" to push files to /sdcard, for example). That's great as it proves that the storage on the device *is* accessible, but just not from CWM. I followed some instructions that I followed partially before (http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html) in an attempt to see if I could get S-OFF. This tutorial is nice because most of the actions are via adb and fastboot instead of using the UI on the phone, which I couldn't get to. I was able to do most of the work I needed to get S-OFF via adb instead of using CWM or some other recovery tool, which was key, since CWM always tells me that it can't read or write any partitions.
I was actually able to get Froyo installed and boot into it! That's the first time this POS has booted into anything in almost a month!!
Now to my current problem - the last few steps of the tutorial linked above require that I install superuser and unrevoked, and suggest that this be done via CWM. Unfortunately, CWM can't read any of my data partitions, so this doesn't work for me. Not many others seem to have this problem, so googling it doesn't turn up any help.
Is there any way I can use ADB to install superuser and unrevoked forever? I also have access to the UI via Froyo and could conceivably install apks as well.
Here are the instructions from the tutorial that don't work for me, as they rely on CWM:
******************
use the recovery menu on your phone to:
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-install zip from sd card(chose your forever file)
******************
Those last two steps - install zip from sd card - are the ones that completely fail for me. CWM just gives me a bunch of "E:can't mount /sdcard/" errors.
If anyone has any ideas on how to install superuser and unrevoked using ADB, I'm all ears : )
Thanks!
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
nschiwy said:
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
BigEdgar said:
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
Click to expand...
Click to collapse
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
cmlusco said:
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried this a few times and while Unrevoked is reporting success, I'm still S-ON and BusyBox and ROM Manager report that I'm not rooted. Back in CWM, CWM still reports errors mounting all drives and is basically crippled. In addition to the "can't mount SD card" errors, I'm also seeing "E:cant mount /dev/block/mmcblk0p2" and "E:Can't mount /cache/recovery/command". Weird. Can't tell if the mount errors are causing my inability to root or my inability to root is causing the mount errors.
(I also tried using AmonRa and got the same "can't mount" blah blah issues). Time for a drink : )
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
eljean said:
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
Click to expand...
Click to collapse
Eljean - that link's a 404...
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
eljean said:
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
BigEdgar said:
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
Click to expand...
Click to collapse
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
eljean said:
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
I appreciate the thoughts, but I think we're talking about different issues here. One of your issues seemed to be that you couldn't access the device at all via USB. I don't have that problem. My USB connection has always been fine. My problem is that CWM can't mount the SD card (or any other drives, for that matter). Everything mounts fine in Froyo, so I'm guessing it has to do with the way the drives are mounted in Recovery vs. Froyo.
The thread you referenced stated that the fix for not being able to access the SDcard was the fastboot oem enableqxdm 0 fix. I tried that a few times but it didn't make any difference.
Thanks for the thoughts!
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!
Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .
enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.
Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).
Hi,
I have Samsung Galaxy S4 Mini (serrano3gxx). I was using this ROM and CWM recovery. I really don't know how it happened. My phone shut down and when I booted it, I saw this message "Encryption Unsuccessful", so I was not able to access my storage. Then, I've searched how to fix this. I tried to backup storage in recovery and I got this error every time "Can't mount /system, /cache, /data", even while trying to mount them manually. After a few try (flashing etc.), I've become to not access ROM (also bootloader) and CWM recovery. When I tried to access them, I only got "Black screen" and nothing appeared on screen. Then, I could access "Download Mode". At this point, I've tried to flash another ROMs (including stock ROM) and recoveries via Odin. Firstly, Odin detected my phone but ADB not. Secondly, when I tried to flash something that I mentioned, Odin's log screen stuck on "Initialization" step. I've waited 1 hour only for flashing recovery... Nothing flashed and still stuck same step...
Now, actual situation is that I can't access even Download Mode! Before this, phone was shaking when I plugged it to charger or USB port and tried to power it on. Now, this is also changed, it is not shaking...
Guys, I am saying "wth is it" now. These occurred step by step:
1. Shut down and message "Encryption failed/unsuccessful".
2. Can't mount /system /cache /data.
3. Can't access both of ROM (bootloader) and recovery // Black screen
4. Can't access Download Mode.
Note that, all of required drivers installed, even Kies. By the way, Kies detected my phone but it could not complete loading to recognize.
I've found this article but I don't know if it is solution.
I guess phone's storage is corrupted.
So, my phone's storage is fried? What should I do? Thanks for helps I will get.
Try flashing the complete stock rom not just the recovery. Or find a fix and flash it!!
Maybe you should get a pit file and flash that. Reanimated a S3 mini with that.
kurtn said:
Maybe you should get a pit file and flash that. Reanimated a S3 mini with that.
Click to expand...
Click to collapse
As I wrote, I can't access/reach recovery and download mode. How can I do that if you know it? I am still searching how to fix this but it is hopeless case I guess. "getting a pit file" is ok. I found it for a few roms including stock rom. But how can I flash it? I could not find this.