Related
I know this may seem like a dumb question but here it goes...I have unlocked my Prime with the unlock tool. I am trying to install custom recovery using fastboot but cannot get it to work. I get "error: cannot load (recovery here)" I've tried twrp and cwm with the same results. I'm on .21 (not rooted) and attempting this in osx 10.7.2 Lion.
When I put the tablet into fastboot it says "starting fast boot mode USB download protocol" and just sits there. Is that normal?
Anyone out there complete this process running OSX Lion? I've read that there are issues with this os and adb though I don't comprehend if this applies to me or not...
Sent from my SAMSUNG-SGH-I717 using XDA
I don't know about your error but it's normal that your prime just sits there in fastboot mode
Sent from my sgs2 running cm9
Try this:
transformerprimeroot com/transformer-prime-recovery/how-to-install-clockworkmod-recovery-5-8-2-0-on-transformer-prime/
There is also a video to make it even easier
That's the tutorial I followed. I'm going to try it with a PC from work today. Maybe I'll have better luck with that. Thanks
Sent from my SAMSUNG-SGH-I717 using XDA
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
jerseybizzle said:
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
Click to expand...
Click to collapse
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
wikdNoob said:
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
Click to expand...
Click to collapse
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
If it was an ics Rom and you are having bootloops, it is most likely because you are s-on. I recommend getting s-off. The wire trick is easy to do, but you need to be careful.
http://forum.xda-developers.com/showthread.php?t=1585846
Sent from my ICS 3VO with Tapatalk 2
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
I'm guessing it was the ics version of vipermod, and since you're s-on your boot image didn't flash. So you're trying to boot an ics rom with a gingerbread kernel.
If you want to use an ics rom, you have a few choices. My favorite... Put a recovery image in the folder on your computer that has fastboot in it. Put the phone in fastboot mode and type in the command window, fastboot boot recovery.img, make sure that you name the recovery image on your comp. to "recovery.img". It should boot to recovery and you can flash away.
Something that's easier is to use 4ext recovery smart flash. I'm sure it works but I've never used it.
If you want to get back to your stock rom unrooted rom you could run an ruu.
Also, take coals advice and s-off that phone, you won't have nearly as many issues once you s-off, and you can use one of the splash screens in my Sig
flonker said:
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
wikdNoob said:
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
Click to expand...
Click to collapse
Where would I find the stock Kernel?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
Where would I find the stock Kernel?
Click to expand...
Click to collapse
Inside the rom that you flashed, just choose that rom with flash image GUI and it'll pull the kernel out for you
flonker said:
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
jerseybizzle said:
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
Click to expand...
Click to collapse
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
flonker said:
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
jerseybizzle said:
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
Click to expand...
Click to collapse
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Wikd said:
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Click to expand...
Click to collapse
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
flukeSG2 said:
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
Click to expand...
Click to collapse
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
RayTrue04 said:
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yes I do, I was looking for information and I read the entire thread. Just because they posted it a year ago doesn't make the info any less wrong.
I went to OTA update MeanRom from 3.1 to 3.2 and after the rom install and reboot my phone kept rebooting, I waited for about 45 minutes just make sure it wasnt going to take.
I then used fastboot to install my last recovery however, the recovery install froze at installing /system for over an hour. I had no choice but to try and reboot as none of the buttons worked. I am now stuck at the HTC screen and can not get into fastboot or phone.
I've tried searching for a solution for a day and still have had no luck. Cant run RUU as it has a USB error which I expected as the phone never boots.
Any help is greatly appreciated.
I am/was on latest radio/firmware/s-off.
Thanks for looking!
evoman said:
I went to OTA update MeanRom from 3.1 to 3.2 and after the rom install and reboot my phone kept rebooting, I waited for about 45 minutes just make sure it wasnt going to take.
I then used fastboot to install my last recovery however, the recovery install froze at installing /system for over an hour. I had no choice but to try and reboot as none of the buttons worked. I am now stuck at the HTC screen and can not get into fastboot or phone.
I've tried searching for a solution for a day and still have had no luck. Cant run RUU as it has a USB error which I expected as the phone never boots.
Any help is greatly appreciated.
I am/was on latest radio/firmware/s-off.
Thanks for looking!
Click to expand...
Click to collapse
Have you tried getting into recovery from the boot loader and flashing a rom
Sent from my EVO using xda premium
evoman said:
I went to OTA update MeanRom from 3.1 to 3.2 and after the rom install and reboot my phone kept rebooting, I waited for about 45 minutes just make sure it wasnt going to take.
I then used fastboot to install my last recovery however, the recovery install froze at installing /system for over an hour. I had no choice but to try and reboot as none of the buttons worked. I am now stuck at the HTC screen and can not get into fastboot or phone.
I've tried searching for a solution for a day and still have had no luck. Cant run RUU as it has a USB error which I expected as the phone never boots.
Any help is greatly appreciated.
I am/was on latest radio/firmware/s-off.
Thanks for looking!
Click to expand...
Click to collapse
I'm confused...You were flashing a recovery from fastboot? Or were you doing a nandroid restore? You tried holding volume down + power to get into the bootloader right?
Sent from my EVO LTE
I can not get past the first HTC screen. Holding power and volume down wont work as it wont get past the first screen. I was using a Nandriod.
Thank you.
evoman said:
I can not get past the first HTC screen. Holding power and volume down wont work as it wont get past the first screen. I was using a Nandriod.
Thank you.
Click to expand...
Click to collapse
Did you do the restore from recovery (TWRP) or did you use fastboot? I ask because fastboot isn't typically used to restore from a nandroid backup, so just trying to understand your description. Do you have adb on your pc?
Sent from my EVO LTE
premo15 said:
Did you do the restore from recovery (TWRP) or did you use fastboot? I ask because fastboot isn't typically used to restore from a nandroid backup, so just trying to understand your description. Do you have adb on your pc?
Sent from my EVO LTE
Click to expand...
Click to collapse
I apologize I really wasnt clear. I was using TWRP. I just uninstalled it a couple of weeks ago I will go grab it again right now.
evoman said:
I apologize I really wasnt clear. I was using TWRP. I just uninstalled it a couple of weeks ago I will go grab it again right now.
Click to expand...
Click to collapse
Gotcha...then this is very strange. Once you have adb installed, try plugging the phone into your pc, power it on and when it's at the HTC screen try the "adb reboot recovery" command and see if that gets you into TWRP. I've never tried using adb from that screen so not sure if the phone is capable of communicating at that point, but worth a shot...
Sent from my EVO LTE
Ok installed r20.0.3 of Andriod SDK. I installed Andriod SDK platform tools REV 14. Now what should I do?
premo15 said:
Gotcha...then this is very strange. Once you have adb installed, try plugging the phone into your pc, power it on and when it's at the HTC screen try the "adb reboot recovery" command and see if that gets you into TWRP. I've never tried using adb from that screen so not sure if the phone is capable of communicating at that point, but worth a shot...
Sent from my EVO LTE
Click to expand...
Click to collapse
Premo, I tried that but I get an error device not found. However, I do hear my laptop make the usb connecting noise when I plug in my phone.
Any other suggestions?
Thank you
evoman said:
Premo, I tried that but I get an error device not found. However, I do hear my laptop make the usb connecting noise when I plug in my phone.
Any other suggestions?
Thank you
Click to expand...
Click to collapse
That's what I was afraid of...the only other thing I can think of is to maybe try flashing a new boot image, but you may have the same problem you had with adb in not being able to communicate with the phone. What you would need to do is pull the boot.img file out of the MeanROM zip, put it somewhere on your PC, then with your phone plugged in open the command prompt and type:
Code:
fastboot flash boot <path_to_boot_img>boot.img
It's basically the same process as installing a new kernel on the new hboot version, which is outlined here:
http://forum.xda-developers.com/showthread.php?t=1794867
Typically you have to be in the bootloader for this, but it's worth a try from the HTC screen. I've been successful with the fastboot command when adb does not see the device, so may work in this case as well. If not, then I'm out of ideas. Since you can't get to the bootloader, you should be able to take it into sprint or best buy without them knowing you tampered with it. Just tell them you took the latest OTA and the battery died during the installation or something. Hopefully they will exchange it, but you run the risk of getting one with the new hboot and losing S-OFF Better than no phone at all though, I suppose...
Not too sure if u have a recovery installed but regardless you should be able to simulate a battery pull by holding power button for 10 seconds or until the captive button lights flash 12 times I think. When the phone powers down press and hold volume down only and you should boot into boot loader. From here you should have a better chance of using adb or fastboot or recovery if you have twrp installed. If you can get to boot loader you have options especially since your s-off.
Good luck man
Sent using my LTEVO
Ok I was able to get into bootloader and tried to flash MeanRom after wiping cache/dalvik/factory reset/system three times each with a new download of MeanRom and it said it flashed successfully. I rebooted and it keeps getting almost to setup then reboots. Should I try an RUU again? If so what version should I use?
Bootloader says:
Jewel PVT SHIP S-OFF RL
CID-SPSC_001
HBOOT-1.12.111
RADIO-1.05.11.0606
Thanks again!
evoman said:
Ok I was able to get into bootloader and tried to flash MeanRom after wiping cache/dalvik/factory reset/system three times each with a new download of MeanRom and it said it flashed successfully. I rebooted and it keeps getting almost to setup then reboots. Should I try an RUU again? If so what version should I use?
Thanks again!
Click to expand...
Click to collapse
That's good you can get into the bootloader, as previous poster said, you have a lot more options. I would save RUU as a last resort. See if you can flash a different ROM, like viper 4g or clean ROM. Or maybe an older version of mean ROM.
Sent from my EVO LTE
That's odd that after a full wipe mean ROM won't boot. Wasn't there issues with mean ROM if your recovery wasn't up to date. I would do a full wipe and try to restore a nandroid. Someone with more knowledge than me can defo help you . You can access bootloder, you have a recovery installed so you should be fine.
Sent using my LTEVO
are you on the latest version of TWRP? version 2.2.2, mean rom has had some issues with older versions...
bog3nator said:
are you on the latest version of TWRP? version 2.2.2, mean rom has had some issues with older versions...
Click to expand...
Click to collapse
No I wasnt so I just updated and will try again. Let you know soon. Thank you
Ok upgraded to the latest TWRP and tried MeanROM again. No go so now I will try CM10 to see if that works
Great news CM10 works and so does an old version of MeanROM guess I just cant run version 3.2 or 3.3. Thanks again for all of the help everyone! This place is the best.
Your phone must not like the new kernel.
Sent from my EVO using Tapatalk 2
thicklizard said:
Your phone must not like the new kernel.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I am not sure if that is all it is. I tried to install 3.3 and then flashed the stock kernel over it and still couldn't boot properly. Its ok it forced me to try CM10.
I am running jelly bean and have an unlocked bootloader. Never been rooted either. I'm trying to install twrp but can't seem to get past the part where I put it into fasboot. I boot into the bootloader and go over to the USB symbol and select it. I then go to adb and try to run the command to install twrp and it can't find my prime. I can get adb to work fine when my prime is running normally. I've tried different drivers and USB ports but still can't get to work. Any suggestions?
Sent from my HTC One XL using xda app-developers app
kmankin5344 said:
I am running jelly bean and have an unlocked bootloader. Never been rooted either. I'm trying to install twrp but can't seem to get past the part where I put it into fasboot. I boot into the bootloader and go over to the USB symbol and select it. I then go to adb and try to run the command to install twrp and it can't find my prime. I can get adb to work fine when my prime is running normally. I've tried different drivers and USB ports but still can't get to work. Any suggestions?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=34359560&postcount=5497
Thanks a ton. I tried to solve this problem for hours. Took me two minutes with that.
Ooooook.... Issues issues issues...
This was what I did... I downloaded the CM11 nightly for the DNA, and Gapps. No issue there. Put them on the sdcard. Then booted to CWM... I wiped and formatted system for cleanest install. Flashed both CM11 and Gapps. Rebooted... bootloop. Ok so something went wrong. Repeated. Same. Ok so I guessed I got a bad copy of CM11. Went to go restore from sdcard, no files.... No clue what happened there, just couldnt access my backup. No issue there I thought, I'd just sideload. Downloaded HTCSync, and HTC DNA all in one tool. Installed drivers on my computer with them... Nothing. Wouldn't recognize my device. Tried 3 other ways to install the drivers, same issue. It recognizes it as "Other device HTC6435LVW" Yellow exclamation. So I tried to update manually. Pointed to the folder. Says nothing there, pointed to a different folder with the drivers, says they werent there again. Tried the 3rd, nothing. So I can't get my drivers to install and that makes me not able to use the All in one tool, or any other sideload method that I've looked at. So I am stumped.
Here's the basics of everything:
I have droid DNA. I have it unlocked and rooted. I have NO ROM on it at all. The internal Sdcard was formatted, so is completely empty. I can't get my computer to install the DNA drivers. I am so screwed since this isn't my phone! My girl is gonna be pissed if I can't fix this.
PLEASE someone help. I have 4 hours from right now to fix this. I hope someone is on that can help....
Update: Managed to find a way to sideload a rom. had to download pdanet. Allows me to see my device while in recovery. No where else... so very little use... but I can sideload... I have so far installed 2 different roms. Illusion and SlimKat. Neither have gone passed the HTC Logo. SlimKat I am not even sure fully installs because it never says complete. When I reboot with it, it stays on HTC logo and then reboots. Over and over. Tried wiping cache and data, reinstalling it, and everything else I could think of. Nothing with that. With illusion I got farther. Illusion installed and I got a completed message, but when I rebooted it stays on the HTC logo. Orange light up top flashes some, but no other activity. I left it for 10 minutes. I tried wiping cache and data, and reinstalling... again nothing helped. I am so stumped. I am downloading viperdna right now. That was the rom I just had when the mess happened. plus it has aroma installer. I am hoping it works. If not, I have no idea, and I am out of luck. Any help would be appreciated!
w4rped said:
Update: Managed to find a way to sideload a rom. had to download pdanet. Allows me to see my device while in recovery. No where else... so very little use... but I can sideload... I have so far installed 2 different roms. Illusion and SlimKat. Neither have gone passed the HTC Logo. SlimKat I am not even sure fully installs because it never says complete. When I reboot with it, it stays on HTC logo and then reboots. Over and over. Tried wiping cache and data, reinstalling it, and everything else I could think of. Nothing with that. With illusion I got farther. Illusion installed and I got a completed message, but when I rebooted it stays on the HTC logo. Orange light up top flashes some, but no other activity. I left it for 10 minutes. I tried wiping cache and data, and reinstalling... again nothing helped. I am so stumped. I am downloading viperdna right now. That was the rom I just had when the mess happened. plus it has aroma installer. I am hoping it works. If not, I have no idea, and I am out of luck. Any help would be appreciated!
Click to expand...
Click to collapse
I believe the CM11 based roms require CWM 6.0.4.5, are you running the latest version? Are you S-OFF, or do you need to flash the boot.img manually? Otherwise do you have a back-up to go to?
From my experience, it sounds like you need to start from scratch by running the RUU... But I'll warn you, MAKE SURE YOU INSTALL THE CORRECT FIRMWARE! Meaning, you can't run the RUU of a different firmware than you have... Good luck! Btw, I have successfully brought my dna back to life after completely removing EVERYTHING! After FINALLY getting the RUU to run I was back to "out the box" stock
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 01:28 PM ---------- Previous post was at 01:20 PM ----------
Although you may be able to fix a simpler way to resolve the issue, I jus always start from scratch
Sent from my BEAST MODE DROID DNA running CM11 ReBorn themed kitkat protected by my new (used) tempered glass screen protector/otterbox combo
durgis said:
I believe the CM11 based roms require CWM 6.0.4.5, are you running the latest version? Are you S-OFF, or do you need to flash the boot.img manually? Otherwise do you have a back-up to go to?
Click to expand...
Click to collapse
I am S-On so I think I messed up something. I thought i was S-off. I do remember flashing the boot.img manually last time and I didnt this time. So I'm not sure what todo now. I was running the latest CWM.
How should I know which RUU to go back to? And How do I install the RUU when I can't get the drivers to recognize my device outside CWM?
OP your problem has been solved a million times, its pretty much the only problem our dna has frequently
90% of the posts in the help section are this exact scenario and the fix for it
but here is the answer anyway,
use a usb2.0 port not 3.0
your phone will be detected by your pc if you installed the drivers and switch between fastboot in the bootloader
you can sideload a rom with adb or you can ruu, .torrented has all the files and guides you need in his sig
w4rped said:
I am S-On so I think I messed up something. I thought i was S-off. I do remember flashing the boot.img manually last time and I didnt this time. So I'm not sure what todo now. I was running the latest CWM.
Click to expand...
Click to collapse
Choose a rom and extract boot.img on your computer, boot into recovery and flash the image.zip. Reboot the phone using adb reboot-bootloader then use fastboot flash boot boot.img
Sent from my HTC6435LVW using Tapatalk
hyphydragon said:
OP your problem has been solved a million times, its pretty much the only problem our dna has frequently
90% of the posts in the help section are this exact scenario and the fix for it
but here is the answer anyway,
use a usb2.0 port not 3.0
your phone will be detected by your pc if you installed the drivers and switch between fastboot in the bootloader
you can sideload a rom with adb or you can ruu, .torrented has all the files and guides you need in his sig
Click to expand...
Click to collapse
thanks for your post. I managed to get it figured out. Windows 8 DOES NOT like the DNA for some reason. I went to a windows 7 machine and had no fastboot issues. I used the RUU to get back to stock, updated to latest, used rumrunner, and flashed a proper rom. I am doing good now, thanks for your replies, I really appreciate it. I ended up finding all the posts on various things that were wrong with the DNA but none were quite right. I pieced together all the problems I had from many posts. Either way, I got it.
w4rped said:
thanks for your post. I managed to get it figured out. Windows 8 DOES NOT like the DNA for some reason. I went to a windows 7 machine and had no fastboot issues. I used the RUU to get back to stock, updated to latest, used rumrunner, and flashed a proper rom. I am doing good now, thanks for your replies, I really appreciate it. I ended up finding all the posts on various things that were wrong with the DNA but none were quite right. I pieced together all the problems I had from many posts. Either way, I got it.
Click to expand...
Click to collapse
W8.1 has problems with adb and fastboot. If you do a Google search there's various solutions on how to get it working properly. Glad to hear you got your issue resolved.
Sent from my Droid DNA using Tapatalk