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
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 there !
I have a little problem with the JellyBean update on my rooted One X. I didn't know that I must go back to a stock recovery before doing the update so i discovered it when it refuse to do the update.
I have done some research and i find how to flash a stock recovery (i did it with fastboot) but now i'm stuck. I reboot with holding power+volume down to get acces to the recovery, then i choose it and the update icon appear but then i have an warning panel with a phone on his side (i hope you know what i'm talking about..). Now i have a boot loop and i don't know how to fix that..
I hope someone will be able to answer me !
And sorry for my english, tell me if something is not clear.
P.S: If possible, i would prefer not having to lose my data
Did you flash the stock recovery or were you stuck before that??
Yes i flash it and i get stuck after. Now when i boot i press power+volume down and when i am in the menu i choose "Recovery", a black screen with the icon update, and then the same black screen but with a phone and a warning panel on his side.
Popofthepop said:
Yes i flash it and i get stuck after. Now when i boot i press power+volume down and when i am in the menu i choose "Recovery", a black screen with the icon update, and then the same black screen but with a phone and a warning panel on his side.
Click to expand...
Click to collapse
Are you sure you got the right stock recovery, did u modify something in your rom, did u change the stock kernel to custom kernel ?
did u restore to fully stock (not just the recovery)
stock rom
stock kernel
stock recovery
I have a stock rom and a stock recovery (i guess, i have downloaded a file named endeavoru_recovery_signed.img) but i don't know for the kernel, how can i check it? The only thing i did was unlock the bootloader and root the phone, does it change the kernel?
it's much easier if you just relock the bootloader and run the RUU.
I would prefer to keep my data and installed data if it's possible.
Popofthepop said:
I have a stock rom and a stock recovery (i guess, i have downloaded a file named endeavoru_recovery_signed.img) but i don't know for the kernel, how can i check it? The only thing i did was unlock the bootloader and root the phone, does it change the kernel?
Click to expand...
Click to collapse
No that does not change the kernel.
Put the phone in Fastboot USB mode and Do
Fastboot getvar version-main
You might have a old recovery installed.
Ok i have the version 2.17.401.2, is it good or not?
Edit: It's the ICS version so it isn't the right recovery version, right? I have to search a 4.0.4 version? The higher version of recovery i have found is version 1.29.401.11
This is the 2.17 stock recovery
http://db.tt/U5CK4noo
If your main version says 2.17.***.** you need this recovery !
Thank you for the link, i flashed this recovery but i still have the same problem :-/
Edit: Now i can acces to the recovery menu when i press power+volume up on the screen with the warning panel. I have some error message:
E:Can't open /cache/recovery/command
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
Edit 2: I forgot to say that I wipe and format some things (don't remember which one, i try to find again the tutorial that i found) but nothing that delete data.
Edit 3: Ok i find it, that's what i did:
Wipe the cache partition
Go to Advanced and wipe dalvik and batt stats
Go to Mounts and Storage and format system, then data, then cache.
Popofthepop said:
Thank you for the link, i flashed this recovery but i still have the same problem :-/
Edit: Now i can acces to the recovery menu when i press power+volume up on the screen with the warning panel. I have some error message:
E:Can't open /cache/recovery/command
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
Edit 2: I forgot to say that I wipe and format some things (don't remember which one, i try to find again the tutorial that i found) but nothing that delete data.
Edit 3: Ok i find it, that's what i did:
Wipe the cache partition
Go to Advanced and wipe dalvik and batt stats
Go to Mounts and Storage and format system, then data, then cache.
Click to expand...
Click to collapse
The errors ...that's fine because the stock recovery can't mount the sdcard that's normal.
The wiping caused it that it not boots. You did practically a full wipe ! Do you have the RUU or a nandroid backup from the rom.
Give your cid here, we have the main version already ... going back with a ruu is the easiest now....
Popofthepop said:
Thank you for the link, i flashed this recovery but i still have the same problem :-/
Edit: Now i can acces to the recovery menu when i press power+volume up on the screen with the warning panel. I have some error message:
E:Can't open /cache/recovery/command
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
Edit 2: I forgot to say that I wipe and format some things (don't remember which one, i try to find again the tutorial that i found) but nothing that delete data.
Edit 3: Ok i find it, that's what i did:
Wipe the cache partition
Go to Advanced and wipe dalvik and batt stats
Go to Mounts and Storage and format system, then data, then cache.
Click to expand...
Click to collapse
OMG...
Dude, you better go RUU way, really.
I assume you have a Windows computer and HTC drivers are installed on it properly.
Looks like you've lost your data and cache but you may still have the data in your sdcard, so first, try to backup them...
Launch the CWM recovery... Connect your USB cable to the phone and then in the CWM custom recovery window, go to "mounts and storage" and select "mount USB storage".
This shall allow your computer to access the storage of your phone.
You shall see a drive on your computer named "HTC STORAGE".
That is your phone storage so copy everything you think that you need.
Then...
Download the correct RUU for your phone >> http://www.htcruu.com/?dir=Endeavor
Note: One X is called "Endeavoru", if international model. Otherwise "Endeavor".
When downloaded, power off the phone.
Press Vol down and Power buttons together till you reach the HBOOT screen.
Select fastboot.
Plug your USB cable and "fastboot" will change to "fastboot usb".
From your computer, which is on the other end of the USB cable, launch command line, from the folder which you keep your adb, fastboot files.
type "fastboot devices" and hit enter.
You shall see some serial number if you have correctly installed the drivers of the phone and if it is correctly plugged.
Now, you need to re-lock you bootloader.
This is required for RUU to perform; if your bootloader is not in "locked" or "relocked" state, RUU won't perform.
Next, type "fastboot oem lock" and hit enter.
Now, bootloader is "relocked".
Now, run the RUU executable you've downloaded and follow the instructions on the screen.
This will take you back to stock status, then, without messing with it, do the 4.1.1 update from system settings and right after your first boot of 4.1.1, go to CWM recovery again and get a BACKUP.
Good luck.
erol.savas said:
OMG...
Dude, you better go RUU way, really.
I assume you have a Windows computer and HTC drivers are installed on it properly.
Looks like you've lost your data and cache but you may still have the data in your sdcard, so first, try to backup them...
Launch the CWM recovery... Connect your USB cable to the phone and then in the CWM custom recovery window, go to "mounts and storage" and select "mount USB storage".
This shall allow your computer to access the storage of your phone.
You shall see a drive on your computer named "HTC STORAGE".
That is your phone storage so copy everything you think that you need.
Then...
Download the correct RUU for your phone >> http://www.htcruu.com/?dir=Endeavor
Note: One X is called "Endeavoru", if international model. Otherwise "Endeavor".
When downloaded, power off the phone.
Press Vol down and Power buttons together till you reach the HBOOT screen.
Select fastboot.
Plug your USB cable and "fastboot" will change to "fastboot usb".
From your computer, which is on the other end of the USB cable, launch command line, from the folder which you keep your adb, fastboot files.
type "fastboot devices" and hit enter.
You shall see some serial number if you have correctly installed the drivers of the phone and if it is correctly plugged.
Now, you need to re-lock you bootloader.
This is required for RUU to perform; if your bootloader is not in "locked" or "relocked" state, RUU won't perform.
Next, type "fastboot oem lock" and hit enter.
Now, bootloader is "relocked".
Now, run the RUU executable you've downloaded and follow the instructions on the screen.
This will take you back to stock status, then, without messing with it, do the 4.1.1 update from system settings and right after your first boot of 4.1.1, go to CWM recovery again and get a BACKUP.
Good luck.
Click to expand...
Click to collapse
I was already on it....... Now we have one big block of jungle info, that will come across as pretty confusing
MarcelHofs said:
I was already on it....... Now we have one big block of jungle info, that will come across as pretty confusing
Click to expand...
Click to collapse
sorry, I had to check the answers before posting. I'll double check next time.
Ok thank you guys, i guess i have no choice i will do it with RUU, I juste have a question, i don't know which RUU i have to download.. @MarcelHofs My cidnum is HTC_203. Don't worry for the jungle info, just tell me which RUU to download and i should be able to follow your tutorial
Popofthepop said:
Ok thank you guys, i guess i have no choice i will do it with RUU, I juste have a question, i don't know which RUU i have to download.. @MarcelHofs My cidnum is HTC_203. Don't worry for the jungle info, just tell me which RUU to download and i should be able to follow your tutorial
Click to expand...
Click to collapse
Gonna give it tonight . I'm at work right now
Is that one good?
http://htcruu.com/Endeavor/RUU_ENDE...Radio_2.1204.135.20_release_274900_signed.exe
If it's not i will wait tonight, don't worry i'm not in a hurry
Popofthepop said:
Is that one good?
http://htcruu.com/Endeavor/RUU_ENDE...Radio_2.1204.135.20_release_274900_signed.exe
If it's not i will wait tonight, don't worry i'm not in a hurry
Click to expand...
Click to collapse
Jep should be the one ! Lock the bootloader
Put the phone in bootloader Fastboot USB mode
Command
Fastboot oem lock
And then run the ruu from pc WITH admin rights :thumbup:
I will test that as soon as my phone will have at least 30% battery, i have reflash CWM to charge it but it's very very long -_-
I currently have a T-Mobile Galaxy S2 with CM10.1.
I flashed my phone to the STOCK ROM recently, and flashed the UVLE1 radio along with it. However, after I flashed it with CWM, my phone went into a boot loop.
I decided to flash back to CM10.1 but it freezes every time it reaches the cache. I also tried to DARKSIDE SUPERWIPE everything, but it freezes at the cache as well. I think my cache partition is corrupted, but I have no idea as to how I can fix it...
I tried to purchase a USB Jig in order to reflash the phone with ODIN. I can get into Downloading mode, but neither ODIN nor Kies can recognize my computer. I just don't know what to do now.
I hope someone can help me.
Thanks!
FosuBoy said:
I currently have a T-Mobile Galaxy S2 with CM10.1.
I flashed my phone to the STOCK ROM recently, and flashed the UVLE1 radio along with it. However, after I flashed it with CWM, my phone went into a boot loop.
I decided to flash back to CM10.1 but it freezes every time it reaches the cache. I also tried to DARKSIDE SUPERWIPE everything, but it freezes at the cache as well. I think my cache partition is corrupted, but I have no idea as to how I can fix it...
I tried to purchase a USB Jig in order to reflash the phone with ODIN. I can get into Downloading mode, but neither ODIN nor Kies can recognize my computer. I just don't know what to do now.
I hope someone can help me.
Thanks!
Click to expand...
Click to collapse
Have you installed your phone drivers on your computer? Did you try to fix permissions or format system then flash back CM10.1 and proper radio / gapps?
jonmassot said:
Have you installed your phone drivers on your computer? Did you try to fix permissions or format system then flash back CM10.1 and proper radio / gapps?
Click to expand...
Click to collapse
Yes, I've installed the phone drivers. I've also tried to fix permissions. I've formatted the system and data many times with Darkside's Superwipe, but it always freezes at the cache. I've even tried to flash to CM10.1. No avail. It just places CM10.1 on a bootloop.
Bump.... I am desperate to fix this...
I also noted that every time I go on recovery, I see this.
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
Every now and then it posts an error saying that it can't mount the sd-ext itself, but i am able to access it just fine.
FosuBoy said:
Bump.... I am desperate to fix this...
I also noted that every time I go on recovery, I see this.
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
Every now and then it posts an error saying that it can't mount the sd-ext itself, but i am able to access it just fine.
Click to expand...
Click to collapse
Have you tried plugin it to another computer? I remember when my computer crashed while I was doing a ODIN install, after reboot, my computer didn't recognized my smartphone... Might help!
---------- Post added at 09:17 AM ---------- Previous post was at 08:53 AM ----------
FosuBoy said:
Bump.... I am desperate to fix this...
I also noted that every time I go on recovery, I see this.
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
Every now and then it posts an error saying that it can't mount the sd-ext itself, but i am able to access it just fine.
Click to expand...
Click to collapse
Also, did you try to completly erase your internal sd card and completly reinstall everything? And if I'm not wrong, with CM10.1, latest, you don't need to use darkside cachewipe...
jonmassot said:
Have you tried plugin it to another computer? I remember when my computer crashed while I was doing a ODIN install, after reboot, my computer didn't recognized my smartphone... Might help!
---------- Post added at 09:17 AM ---------- Previous post was at 08:53 AM ----------
Also, did you try to completly erase your internal sd card and completly reinstall everything? And if I'm not wrong, with CM10.1, latest, you don't need to use darkside cachewipe...
Click to expand...
Click to collapse
I'll try and plug it into another computer. But how exactly do I go about erasing my internal sd card?
Plug in your phone to your computer and open up kies. Select "emergency firmware recovery", Kies will probably say it can't detect your phone and ask you to enter serial number. Enter serial number from under the battery.
Don't use dark side wipe unless you know for sure that it is required!! Otherwise it can mess up your phone.
Sent from my Nexus 7 using xda app-developers app
gc84245 said:
Plug in your phone to your computer and open up kies. Select "emergency firmware recovery", Kies will probably say it can't detect your phone and ask you to enter serial number. Enter serial number from under the battery.
Don't use dark side wipe unless you know for sure that it is required!! Otherwise it can mess up your phone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Kies doesn't ask for my serial number... just a recovery code. Is it possible for me to mount my storage to the PC through the CWM? Every time I try to do that, it doesn't work at all either.
------------
UPDATE! I found where to put my serial number!
Will keep you posted...
gc84245 said:
Plug in your phone to your computer and open up kies. Select "emergency firmware recovery", Kies will probably say it can't detect your phone and ask you to enter serial number. Enter serial number from under the battery.
Don't use dark side wipe unless you know for sure that it is required!! Otherwise it can mess up your phone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It tells me that the "SGH-T989" does not support 'initialising.' I'm devastated.
That's too bad it didn't work. Something similar happened to me. I remember kies couldn't recognize my phone either and asked me to input serial number... That was a while ago though, so I cant remember all of the details. I still think kies is your best bet, it took a while to work for me too.
Sent from my Nexus 7 using xda app-developers app
I think the problem here is that my computers cannot recognize the phone, no matter what. I think some part of the phone is corrupted to the point where it does not even want to boot a ROM. I've attempted to narrow the corruption down to the cache partition.
Is there anyway I can re-format the cache without using a PC? CWM Recovery cannot access the cache without freezing. Is there a ZIP file I can download that can format everything?
Better yet, is there a ROM that I can flash that will re-flash the cache as well? I tried re-flashing CM10.1 and nothing happens. Even restoring different nandroids makes the CWM Recovery freeze at the cache!
I've also wiped the Dalvik cache countless times, no avail. Will a TWRP recovery work? I have no idea what it is.
FosuBoy said:
I'll try and plug it into another computer. But how exactly do I go about erasing my internal sd card?
Click to expand...
Click to collapse
With TWRP, you can just erase everything in tools or advanced, can't remember wich one, but I don't know about CMW.
Try re-installing all you drivers, meaning uninstall, reboot, re-install and see if your computer recognize it again.
Never use Darkside Superwipe with CWM 6.x.x.x, you get a bootloop.
I just reinstalled the drivers on my computer and followed the right protocol. Nothing. To set things straight, I've probably used every method possible to fix this thing. Nandroid Recovery, ROM Flashing, and Kies have all been fruitless attempts to get this thing to work.
------------------------------
nivekx9 said:
Never use Darkside Superwipe with CWM 6.x.x.x, you get a bootloop.
Click to expand...
Click to collapse
Ugh, I know this. I have CWM 5.x.x.x.
FosuBoy said:
I just reinstalled the drivers on my computer and followed the right protocol. Nothing. To set things straight, I've probably used every method possible to fix this thing. Nandroid Recovery, ROM Flashing, and Kies have all been fruitless attempts to get this thing to work.
------------------------------
Ugh, I know this. I have CWM 5.x.x.x.
Click to expand...
Click to collapse
The only thing left, is to try it on another computer, worked for me.
FosuBoy said:
I just reinstalled the drivers on my computer and followed the right protocol. Nothing. To set things straight, I've probably used every method possible to fix this thing. Nandroid Recovery, ROM Flashing, and Kies have all been fruitless attempts to get this thing to work.
.
Click to expand...
Click to collapse
Odin back to stock.
Edit: sorry just reread your OP and Odin isn't working. Try flashing TWRP and see if it helps at all.
I'll get you the link.
Update! My computer seems to recognize the device, but it says that the 'device is malfunctioned' and lists it as an unknown device. However, I know where the Samsung USB drivers are located. Could I just manually install a driver onto the 'unknown device?'
I'll try and get a picture of the drivers because it seems like there is more than one that I can install...
TWRP 2.5.0.0
I've flashed the TWRP.. now it freezes on the teamwin logo. 5 steps backwards now.. I can't access the ROM nor do I have a way to recover any files.
FosuBoy said:
I've flashed the TWRP.. now it freezes on the teamwin logo. 5 steps backwards now.. I can't access the ROM nor do I have a way to recover any files.
Click to expand...
Click to collapse
It sounds like you have a NAND problem. I am searching Google but haven't found anything helpful yet. Have you tried using Odin on all the different USB ports? Or like someone else said, another computer?
Hi all, I ****ed up and didn't make a backup.
I wiped the phone clean from bootloader recovery, but then realized I had forgotten to move the new gapps and cm rom to my phone.
When I plug it in, it is recognized by my computer, but the HTC MTP Device fails to work.
I can't see the phone, and therefore can't put anything on it to flash. If I mount the phone via the bootloader, it pops up in Windows and wants to be formatted.
I have been looking around and trying different things for the past couple hours, and figured it was time to ask someone who might know..
Any ideas?
chriswcs said:
Hi all, I ****ed up and didn't make a backup.
I wiped the phone clean from bootloader recovery, but then realized I had forgotten to move the new gapps and cm rom to my phone.
When I plug it in, it is recognized by my computer, but the HTC MTP Device fails to work.
I can't see the phone, and therefore can't put anything on it to flash. If I mount the phone via the bootloader, it pops up in Windows and wants to be formatted.
I have been looking around and trying different things for the past couple hours, and figured it was time to ask someone who might know..
Any ideas?
Click to expand...
Click to collapse
I tried to take a screen shot, but it won't let me post it as I am noob-status.
Device Manager:
Android USB Devices
MyHTC
.
.
.
Portable Devices
J:/
<!> MTP USB Device
I don't understand why I can't mount or access the phone. Do I not have the right drivers installed?
Is there any way to get around this and put the files on my phone so I can install any old ROM so I can boot it up again??
You need to update the drivers on your PC, there's a few threads on how to do it. You should still be able to use adb push to add files, though.
Drivers are fine ! Go in recovery and mount the sdcard as a usb mass storage device ! In the title you speak of a HTC one......so is it a ONE or a ONE X ?
Thanks for replying!
It is an HTC One X. Should I just install the Android SDK bundle? Or are there other drivers?
Android sdk bundle is good. But you have MYHTC so that's correct. You need to go into the recovery and mount the sdcard as a usb storage device, it will show the drive in windows and then you can copy a rom onto it.
Mr Hofs said:
Android sdk bundle is good. But you have MYHTC so that's correct. You need to go into the recovery and mount the sdcard as a usb storage device, it will show the drive in windows and then you can copy a rom onto it.
Click to expand...
Click to collapse
Hi, so I installed the newest HTC driver (4.2) and all the SDK bundles. When I plug the phone it, it still won't recognize the HTC MTP Device. When I mount from the bootloader, it doesn't let me mount the sdcard (only the system data and cache), and Windows still shows a drive that needs to be formatted.
Do you think it's still a Windows driver I'm missing? If I go Terminal Command on phone it says
E: Unable to mount '/sdcard'
E: Unable to mount storage.
What's the option called you tap inside recovery. And what recovery are you using ?
If it's CWM you go to mounts and storage and tap the last option in that list.....then wait till it pops up on the pc
I'm using TWRP v 2.4.2.0 and I couldn't check the box for mount sdcard.
ADB push worked!
But the ROM failed. Is there anything else I'm missing?
It still says that E: can't mount.
Try this recovery please, i know this one blinded
https://db.tt/MNtVjpOJ
Mr Hofs said:
Try this recovery please, i know this one blinded
https://db.tt/MNtVjpOJ
Click to expand...
Click to collapse
Firstly thank you so much for taking time to help a lost stranger out!
What I did was reformat the J: drive that popped up on Windows, then I was able to put both the CM10.2 and GAPPS on the /sdcard/ (it would then mount)
I could then install both of them successfully, but I don't have a boot.img because my kernel is wiped. Will that file work as a boot.img?
chriswcs said:
Firstly thank you so much for taking time to help a lost stranger out!
What I did was reformat the J: drive that popped up on Windows, then I was able to put both the CM10.2 and GAPPS on the /sdcard/ (it would then mount)
I could then install both of them successfully, but I don't have a boot.img because my kernel is wiped. Will that file work as a boot.img?
Click to expand...
Click to collapse
Or how do I try your recover? Should I push it with adb? If so, to where?
I found two other boot.img files on the webs (boot.img and cm10.img), but I don't know how to get the phone to actually boot off them
The boot.img has to be flashed via Fastboot in the bootloader. So if you installed CM correctly via the recovery then flash the boot.img from the CM.zip ....
Fastboot flash boot boot.img
And a kernel can't be wiped via the recovery by the way. You can only delete/overwrite it via Fastboot commands
Mr Hofs said:
The boot.img has to be flashed via Fastboot in the bootloader. So if you installed CM correctly via the recovery then flash the boot.img from the CM.zip ....
Fastboot flash boot boot.img
And a kernel can't be wiped via the recovery by the way. You can only delete/overwrite it via Fastboot commands
Click to expand...
Click to collapse
Okay! That's good
I think it flashed correctly, now I am just waiting for the phone to boot up. It's been going for about 25 minutes though. Should it be that long?
Nope not good.......make a full wipe in recovery before installing the rom.
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts and storage-format cache,data,system
Then install CM and gapps then reboot because you already flashed its boot.img
Mr Hofs said:
Nope not good.......make a full wipe in recovery before installing the rom.
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts and storage-format cache,data,system
Then install CM and gapps then reboot because you already flashed its boot.img
Click to expand...
Click to collapse
None of the ROMs I've tried have worked! I think it's because my hboot is version 1.14.
Lol dude you have the evita go to the HTC one XL forum. You are in the completely wrong forum......sorry !!!
chriswcs said:
None of the ROMs I've tried have worked! I think it's because my hboot is version 1.14.
Click to expand...
Click to collapse
Stuck yet again.
I relocked the phone to flash new firmware, but I have CID 1111111, so I can't find anything to unlock the bootloader again.
Double sauced. Ahhhhhh
Unlock the bootloader by flashing the unlock_Code.bin file wich you got the first time when it's unlocked.
Fastboot flash token unlock_code.bin
But you really should continue this in the right forum. Flashing stuff from here may brick the phone !