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
Related
Hi XDA. I did post a topic to do with the same handset but I've requested for it to be deleted as I'm going to post all the current details on my handset and the status of it, just so it's easier to look at the problems.
Modes the phone can run in: Fastboot, System Recovery and USB-MS toggle.
Through backup and restore, nothing works, requests everything through ADB despite having tried that also. Flashing new ROMs after wiping the phone and SD entirely doesn't work, it still gets stuck in the loop no matter what ROM I use.
I have extracted the ROM and system/boot.img's from an Orange RUU via and tried installing the rom and the img files separately but the ROM came up as "bad" and I don't know how to use the .img as they don't come up. I think if I flashed the fresh boot and system images it might work, but that's just me. I have also tried installing the RUU from fastboot, but that doesn't work either, it just searches for images and reverts to the fastboot menu with no indication for the RUU install. I've tried wiping the SD and using a fresh SD and still nothing, still looping.
I'm at my wits end with this and I don't want to have to sell it faulty if it's fixable or "not" bricked..
Its not bricked, if it was then nothing would happen at all.
Although I have never heard of this problem before and the only possible solution i can think of is to connect try and update to the official ROM, which would remove your root access and most likely not let you root again, but this is still better than having a non-working hero.
Hope you find a solution
Its not bricked, if it was then nothing would happen at all.
Although I have never heard of this problem before and the only possible solution i can think of is to connect try and update to the official ROM, which would remove your root access and most likely not let you root again, but this is still better than having a non-working hero.
Hope you find a solution
twiztedvvv said:
Its not bricked, if it was then nothing would happen at all.
Although I have never heard of this problem before and the only possible solution i can think of is to connect try and update to the official ROM, which would remove your root access and most likely not let you root again, but this is still better than having a non-working hero.
Hope you find a solution
Click to expand...
Click to collapse
Good to know it's not bricked, it means that it CAN be fixed somehow.
I have said in the post that I can't get into Android at all expect the boot modes and USB-MS toggle. This means I can't get into sync to install an RUU, which I couldn't do before anyway. I have extracted the ROM from an official RUU but that and the sys.img and boot.img won't flash either. The .img files don't even show, since you can only flash .zip files.
Thanks anyway!
Sorry guys, i need to bump this... :-(
Any suggestions?
Sent from my HTC Legend using XDA App
I'm not sure I 100% understand the problem you are having here. I guess you are trying to root essentially, since you are trying RUUs and zips (whilst rooting might not be your end goal, it sounds like you're trying to just now).
Make a gold card, and use the HEROIMG.zip method to flash the ROM.zip out an RUU. At work so can't explain fully, but search on these terms for help.
It's already rooted, it's just stuck in a boot loop, and I can get into the states I mentioned above. And I've tried a few ROMs off here and that doesn't seem to work. Tried extracting the ROM from an official RRU as well, which is why I mentioned it.
Sent from my HTC Legend using XDA App
When you hold Home and Press power do you get into the recovery screen?
Which recovery screen have you got installed?
Have you waited more than 5 minutes for a new ROM to load the first time?
Have you run logcat and watched the output whilst it is loading a fresh rom?
Have you wiped everything before flashing the rom's update.zip?
I get into recovery, I have RA Hero installed on it. And it's sat for over 5 minutes..
Sent from my HTC Legend using XDA App
And I ran all the wipe options before flashing yeah.
Sent from my HTC Legend using XDA App
And I ran all the wipe options before flashing yeah.
Sent from my HTC Legend using XDA App
You have two options, leave it for an hour and see if it boots. Make sure you do a full wipe and then flash VillainROM or another established ROM. Don't use any beta's or alpha builds.
Alternatively you can get a logcat report going and post that up.
I'll try the first option when I finish work, I'll try Villain as it's what the Hero had on it before this happened.
Are there any guides to doing a logcat report? I tried doing,one once but I didn't seem to get much out of the instructions I was given. Thanks for your help so far .
Sent from my HTC Legend using XDA App
00Sparrow said:
I'll try the first option when I finish work, I'll try Villain as it's what the Hero had on it before this happened.
Are there any guides to doing a logcat report? I tried doing,one once but I didn't seem to get much out of the instructions I was given. Thanks for your help so far .
Sent from my HTC Legend using XDA App
Click to expand...
Click to collapse
http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
there is info on setting up adb. Then do "adb logcat > logfile.txt" and send logfile.txt
Anon I'll try that at the weekend sometime when I get a chance.
Btdag I left the Hero on until it died, nothing but the Hero screen. Guess I need to bump here again once logcat is done..
Sent from my HTC Legend using XDA App
Hi, i'm new here and i got a big problem! after instaling RCMIX_3D_EVO_kernel_v2.2.3.zip my phone kept rebooting on the htc logo, i tried various ways to solve this like instaling a new kernel, restore from a previous backup, changing roms, and do a factory reset. Nothing worked and now my problem is even bigger cause i cant go to the recovery mode ...
If someone can help me on this pleeaase :/
mikick said:
Hi, i'm new here and i got a big problem! after instaling RCMIX_3D_EVO_kernel_v2.2.3.zip my phone kept rebooting on the htc logo, i tried various ways to solve this like instaling a new kernel, restore from a previous backup, changing roms, and do a factory reset. Nothing worked and now my problem is even bigger cause i cant go to the recovery mode ...
If someone can help me on this pleeaase :/
Click to expand...
Click to collapse
If your on 2.3.4 that's your issue.those kernels won't work for it.pull battery.hold power and volume down go into recovery when battery is put back in..
sent from my badass EVO 3D running Kaos Hybrid 4.20 using tapatalk
I did that but when i choose recovery it boots to the htc logo and then keeps rebooting ...
no one knows what i can do ? :/ is there a way to reset the phone without recovery ?
You pulled the battery? Cause if you don't and fastboot is on.its would do that.
sent from my badass EVO 3D running Kaos Hybrid 4.20 using tapatalk
yes i did it just as you said ...
If you still can't get into recovery or the phone continuously bootloops after the battery pull, just run the latest RUU.
What is a RUU and how do i run it ? Do you have a link ? Thanks for the replies.
Have you taken the latest OTA, or have you ran revolutionary on your phone?
yes i have revolutionary on the phone
Go here, download the .exe with the 1.13.651.7, and run it as admin.
thanks, Is it a problem if i'm not on sprint? cause i'm in france and got the gsm version.
Yes, that would be a problem...try this thread and see if your version is listed.
i guess i'll try the "europe" one... if i dont risk to brick my phone by doing so ...
Tried and didn't work wasn't the good one... I hope i will find the good one soon i'll bookmark your link hoping that my version will be upped...
Thank you for your help.
Did you solve the problem?
Hi I just have the same problems like you ... I am in France, and after installing a new kernel, the phone is an a restarting loop.
I can go to the recovery mode (revolutionary) , I have tried to install different kernel and different ROM, but it alwas failed...
Thanks
MikRunny problems
I have a similar problem.
I tried installing MikRunny, (I flashed the boot.img multiple times, and did a full wipe, multiple times), but I keep getting a bootloop.
I fastbooted the boot.img, and I replaced the boot.img in the kernel map in MikRunny.zip.
My phone is (according to recovery) S-OFF, Revolutionary, 1.49 HBOOT, GSM.
That was the problem, the boot.img was not for GSM, but for CDMA.
But yet, I replaced it, and it still doesn't work...
mikick said:
Tried and didn't work wasn't the good one... I hope i will find the good one soon i'll bookmark your link hoping that my version will be upped...
Thank you for your help.
Click to expand...
Click to collapse
Search Google, Rootzwiki, and XDA for an SD bootable CWM or TWRP recovery image for the phone. Use all terms for the Evo 3D (shooter, 3vo, E3D, and even the HTC model number, which is PG86100). Write it to a microSD with dd in Linux or Win32DiskImager in Windows. After it's done writing, just drop your zips onto the card as you normally would and place it back into the phone. Proceed to recovery as you normally would. Wipe system, data, cache, dalvik cache, and battery stats. Now flash your ROM zip and follow it with your GAPPS zip. Reboot system and pray for the best. If you need any more assistance or help, feel free to PM me. Hope this helps, I know how bricking a phone feels. Just remember that there's no such thing as a permanent brick, unless you hit it with a real brick .
Sent from my PG86100 using xda premium
MikeyCriggz said:
Search Google, Rootzwiki, and XDA for an SD bootable CWM or TWRP recovery image for the phone. Use all terms for the Evo 3D (shooter, 3vo, E3D, and even the HTC model number, which is PG86100). Write it to a microSD with dd in Linux or Win32DiskImager in Windows. After it's done writing, just drop your zips onto the card as you normally would and place it back into the phone. Proceed to recovery as you normally would. Wipe system, data, cache, dalvik cache, and battery stats. Now flash your ROM zip and follow it with your GAPPS zip. Reboot system and pray for the best. If you need any more assistance or help, feel free to PM me. Hope this helps, I know how bricking a phone feels. Just remember that there's no such thing as a permanent brick, unless you hit it with a real brick .
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Hey i ran into this problem yesterday flashing this Kernel...i used the flash gui app...what happened was it booted after it flashed....and it stuck in bootloop...i tried reflashing it the regular way just through cwm and it wasnt doing anything...so i did a google search on how to flash kernels on hboot 1.5 this is what i got...http://youtu.be/HclYpo0ZR3s that youtube video shows how to flash the kernel....THE WAY I KNEW HOW TO....but he says at the end there is a backup way to flash kernels..he says its longer but it also works just as good he says that you fastboot flash it via command prompt...so this gave me an idea...he says open up command prompt and prompt it to the folder you have used to unlock the device...unzip the boot.img file from the kernel your using in command prompt youd type fastboot flash boot boot.img....THIS NEXT PART I THOUGHT OF MYSELF. i removed the boot.img from the rom i was using and flashed that first AND FLASHED THE EXACT ROM I REMOVED THE BOOT.IMG FROM TO GET IT ROOTED. Not only did i solve my original kenel problem where my radios were jacked up BUT, i also got this kernel to work, and my synergy rom to work with the kernel, everything works and i was unbricked...I HOPE ANYBODY WHO RUNS INTO THIS PROBLEM DOES THIS AND THEY ARE OK.
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.
Hiya!
Got my hands on HOX+ yesterday and after giving Sense a try I decided I still hate it... Not to mention all the bloatware. So I went ahead and downloaded the all-in-one toolkit and Llior's CM10.1 with blade's kernel.
Now, I did give FAQ and instructions a look, everything seemed clear, especially since I've been nuking/flashing my Desire almost monthly for god knows how long.
Everything went as expected, got drivers, got token, unlocked, flashed CWM from the toolkit, proceeded with a full wipe/format to be sure no old stuff is laying around somewhere. And this is where I understood something is wrong. When I tried to sideload the ROM via the toolkit, it yelled at me that no device is detected. I tried unplugging/plugging the USB to no avail...
Tried searching around forums and while I did find some info, nothing seems to solve my problem.
Any and all help will be greatly appreciated. Thanks in advance!
Suddenly feeling noob again,
v1ks_
Sent from my HTC Desire using Tapatalk 2
It is a known issue that sideload can take up to 5 mins to work when in recovery. You could also flash back to stock with the proper RUU and when you unlock the bootloader boot the phone and after the initial setup copy the rom to the storage. After you flash recovery.img and boot.img and boot into recovery you will see that the rom is on the memory now. GL&HF
Thanks!
So am I understanding this correctly that the USB problems (where it fails to detect load USB master while in bootloader will be solved if I flash a RUU boot.img so I can actually get adb to work, so I can get that stock ROM unto the phone?
Also, about the sideload and it taking up to five minutes. I don't even get to sideloading, the toolkit just curses it has no device, because of USB not working properly...
Cheers and thanks!
Sent from my HTC Desire using Tapatalk 2
Not positive, but it sounds like your drivers aren't installed. Did you install the htc syncmanager on your pc? and the second problem I see is that I believe the pizza kernel is the only one currently working for Lloir's cm10
v1ks_ said:
Thanks!
So am I understanding this correctly that the USB problems (where it fails to detect load USB master while in bootloader will be solved if I flash a RUU boot.img so I can actually get adb to work, so I can get that stock ROM unto the phone?
Also, about the sideload and it taking up to five minutes. I don't even get to sideloading, the toolkit just curses it has no device, because of USB not working properly...
Cheers and thanks!
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Hiya!
Well, I'm still not entirely what I'm messed up, but going back to stock obviously fixed the problem. So thanks for that...
As far as Lloirs CM goes, the required kernel, at least as per his post, is the blade one, which I did flash. Got stuck on first boot, which was taking way longer than it should... IMHO (well over 20mins, so I just returned to stock for now).
Thanks for the help. Now I have another issue to try and solve... My Debian box doesn't really like my hox+, file transfer are plain weird...
Sent from my HTC One X+ using Tapatalk 2
Ah, are you by chance on the international HOX+?
v1ks_ said:
As far as Lloirs CM goes, the required kernel, at least as per his post, is the blade one, which I did flash. Got stuck on first boot, which was taking way longer than it should... IMHO (well over 20mins, so I just returned to stock for now).
Thanks for the help. Now I have another issue to try and solve... My Debian box doesn't really like my hox+, file transfer are plain weird...
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Indeed I am, yes... Obviously, I'm trying to flash and run the international ROM. Will keep on trying once I get back home in the evening.
Sent from my HTC One X+ using Tapatalk 2
Okay, so I installed the latest version of the carbon ROM. Every time I install it (I've uninstalled and reinstalled it multiple times) I cannot view any files in my sdcard. I know they are still there, as they are accessible through Recovery, however in the ROM they cannot be accessed. None of the files, there's nothing on my phone according to the ROM.
Also, when I plug the phone into my PC it does not find anything. I find it strange that I can find files in recovery mode, but not in Windows, or the ROM itself. I'm so confused and I'm leaving for something tomorrow where I won't be able to access a computer and I'm starting to get nervous any help would be great.
EDIT: Also, I can download apps, so it's not the SD Card. What sucks is since no files are showing I can't put anything on my phone to re-flash and I have no other ROMs on there to flash, and sideload isn't working, it's not recognizing the device.
gypsy6slayer said:
Okay, so I installed the latest version of the carbon ROM. Every time I install it (I've uninstalled and reinstalled it multiple times) I cannot view any files in my sdcard. I know they are still there, as they are accessible through Recovery, however in the ROM they cannot be accessed. None of the files, there's nothing on my phone according to the ROM.
Also, when I plug the phone into my PC it does not find anything. I find it strange that I can find files in recovery mode, but not in Windows, or the ROM itself. I'm so confused and I'm leaving for something tomorrow where I won't be able to access a computer and I'm starting to get nervous any help would be great.
EDIT: Also, I can download apps, so it's not the SD Card. What sucks is since no files are showing I can't put anything on my phone to re-flash and I have no other ROMs on there to flash, and sideload isn't working, it's not recognizing the device.
Click to expand...
Click to collapse
What recovery are you using to flash the Rom? Make sure it's a kit Kat based one. Twrp 2.7 worked for me. Try a reinstall with that. Wipe the system, factory rest, and clear the dalvik cache and cache. See if that makes a difference.
Hole this helps.
Let me know how it goes and of its not fixed we can try something else.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
What recovery are you using to flash the Rom? Make sure it's a kit Kat based one. Twrp 2.7 worked for me. Try a reinstall with that. Wipe the system, factory rest, and clear the dalvik cache and cache. See if that makes a difference.
Hole this helps.
Let me know how it goes and of its not fixed we can try something else.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks a lot for the quick answer, and yes I'm using a KitKat based one because I've been on and off of ROMs for a while now. I'll try reinstalling it, and everything you said and I'll get back to you.
EDIT: I don't know why but my ADB just started working wow okay, we're on a good run here, let's see how it turns out. I'm installing a different ROM just to at least get off this (I'm gonna call it broken because ever since I installed it, it's just been messing up) one, and install a different one. I've wiped and everything.
EDIT Again: OMG IT'S FIXED I'M SO HAPPY I CAN FINALLY GO TO BED! But thanks for the help, I was about ready to give up until you answered I got my motivation back. It was just the ROM, something was wrong with it. It was on the website, but not on the thread and I decided to just download it cause, hey, it was the latest version. Maybe it was all the ROM's fault or maybe it corrupted while downloading or something weird, but either way it's fixed now I'm running a previous version and it WORKS!