So now on my evo, every rom i flash gets stuck in bootloop. Ive tried Meanrom,cm10.1,miui, and even the stock roms like JB 4.1. At first my backups would work, but that is no longer the case. Im not sure what else to include. Yes ive factory reset and wiped all cache. Yes i made sure the roms werent corrupt.
I tried using boot img flasher but that did not work.
I have no idea what else there is try.
Htc Evo 4g LTE
S-on RL
HBOOT- 1.19.0000
RADIO-1.12.11.0809
OpenDSP-v29.1.0.45.06.22
eMMC-boot
Rooted.
TWRP - 2.3.3.0
Maybe downgrade/upgrade your recovery. Some phones are having issues with newer or older twrp releases.
Good luck man
Edit....... Just saw your running 2.3.3.0
I would try upgrading to a newer version
Sent from my EVO using xda premium
Try a fresh install wipe cache/dalvik cache /factory reset/system then try to install the rom
Sent from my PoS MoPho
corcgaigh said:
Maybe downgrade/upgrade your recovery. Some phones are having issues with newer or older twrp releases.
Good luck man
Edit....... Just saw your running 2.3.3.0
I would try upgrading to a newer version
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thanks for the reply, ill try this first thing in the morning
bigdaddy619 said:
Try a fresh install wipe cache/dalvik cache /factory reset/system then try to install the rom
Sent from my PoS MoPho
Click to expand...
Click to collapse
Sadly , as many times as ive tried this, it hasnt worked
I no longer have any recovery at all. While following the boot loader method of updating Twrp found here. Bah, im not allowed to post links.
I just dug myself deeper into the hole it seems, Last thing in the world i want to do right now is have to pay lots of money to fix my mess
EDIT: I was able to get TWRP working again. Phew. Still have a alot of progress to make
ANOTHER EDIT: Out of some miracle, wiping everyhting for the 034612093612903126th time and then flashing worked, Superjelly booted and everything... Oh my god im relieved.
Close thread/delete thread
Sukhol said:
I no longer have any recovery at all. While following the boot loader method of updating Twrp found here. Bah, im not allowed to post links.
I just dug myself deeper into the hole it seems, Last thing in the world i want to do right now is have to pay lots of money to fix my mess
EDIT: I was able to get TWRP working again. Phew. Still have a alot of progress to make
ANOTHER EDIT: Out of some miracle, wiping everyhting for the 034612093612903126th time and then flashing worked, Superjelly booted and everything... Oh my god im relieved.
Close thread/delete thread
Click to expand...
Click to collapse
I'm having basically the exact same issues you had. Do you mind shedding some light my way? I've been in a soft brick for a while now. Although I almost had a rom go through, until my touchscreen was unresponsive (i think due to my bootloader showing S-ON and not S-OFF). I can access the bootloader and TWRP. I have no backups (this is my first time rooting and flashing, in case you haven't noticed). I don't know how to take the S-OFF or recover the old Sense 4 stock os. At this point i really would just like to use my phone. Any guidance would be greatly appreciated!
JosephAndrew said:
I'm having basically the exact same issues you had. Do you mind shedding some light my way? I've been in a soft brick for a while now. Although I almost had a rom go through, until my touchscreen was unresponsive (i think due to my bootloader showing S-ON and not S-OFF). I can access the bootloader and TWRP. I have no backups (this is my first time rooting and flashing, in case you haven't noticed). I don't know how to take the S-OFF or recover the old Sense 4 stock os. At this point i really would just like to use my phone. Any guidance would be greatly appreciated!
Click to expand...
Click to collapse
Check PM
Related
Hi guys. So here's my problem. I recently tried to update my phone to the latest version of NRG's Energy Rom using CWM. In the process I did a factory data wipe, and wiped the dalvik cache. I then flashed the rom as normal, but when I rebooted all I got was the white screen with the green HTC logo. It refuses to go any further. I can still get into recovery if needed, and I've tried a ton of different things, but to no avail. Anybody have any ideas as to what I need to do or is this thing hosed?
The phone is S-ON at the moment with an unlocked bootloader.
Any help is appreciated.
Mr.Moo52 said:
Hi guys. So here's my problem. I recently tried to update my phone to the latest version of NRG's Energy Rom using CWM. In the process I did a factory data wipe, and wiped the dalvik cache. I then flashed the rom as normal, but when I rebooted all I got was the white screen with the green HTC logo. It refuses to go any further. I can still get into recovery if needed, and I've tried a ton of different things, but to no avail. Anybody have any ideas as to what I need to do or is this thing hosed?
The phone is S-ON at the moment with an unlocked bootloader.
Any help is appreciated.
Click to expand...
Click to collapse
Flash the wipe script, flash the rom you wanted, when the phone boots up, let it sit for a few minutes, like 10 should be good.
Well I'll be damned. I could have sworn I tried that, but there we go. Thank you so much for the help.
Mr.Moo52 said:
Well I'll be damned. I could have sworn I tried that, but there we go. Thank you so much for the help.
Click to expand...
Click to collapse
Also, get rid of CWM and use 4ext recovery. It's in the dev section... And its the preferred recovery by most amaze users. I have a thread in Dev section
It allows you to flash kernel automatically when flashing ROM, that way you don't have to use a kernel flasher. Plus many other features.
Sent from my HTC_Amaze_4G using Tapatalk 2
Thanks for the info. I've been looking at recent posts and it seems I'm behind on a few things, including getting s-off.
Weird Problem
I had the same problem but I don't want to lock and re-unlock my bootloader. And this has never happened but my CWM Recovery isn't working. I didn't use 4ext bc this happened last time with that recovery. Is there any way to find the wipe script to use it from fastboot?
Tried kernel flashing; re-flashing recovery...second time this happened with s-on on speed rom
Had to re-wipe phone and re-flash everything...Got it working again! Weird problem though?!?!
I was rooted on MeanROM, and from TWRP I cleared the cache and delvic cache and did a factory wipe, then tried to install the cm10 nightly build, but it said failed, so I cleared and wiped again and tried installing the FreshEVO ROM that I had on it before the MeanROM, it never finished installing, just froze after a while. then TWRP restarted then went into the white HTC "quietly brilliant" screen with the red disclaimer and stuck there. When i hold the power down, it just reboots back to this screen. I cant get it into recovery or bootloader or anywhere but this. My computer isn't recognizing the phone, I tried to adb to it from cmd but its not showing up. I don't think i had the latest hboot or whatever on it, it's been probably two months since i first rooted it. any help would be great, please and thank you. I'm heading to work but i'll check this on my breaks and answer any questions i can about what ive done. I was about to trade the phone for an s3 this saturday, but im sure he wont want it like this! THANK YOU.
I'm just gonna say this and don't take it offensively... That is the risk you took rooting your phone.. if you can get into bootloader, try loading a current ruu on there and see If that works.
Sent from my EVO using Tapatalk 2
thlinx said:
I'm just gonna say this and don't take it offensively... That is the risk you took rooting your phone.. if you can get into bootloader, try loading a current ruu on there and see If that works.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
No offense taken, I understood the risks, and I accept the consequences, which is why I'm fairly calm and not freaking out. I'm going to read more into RUU's on my break, as I'm not completely sure how to do that. Does the computer have to recognize my device for that? I would think so. Is there a trick to getting from this white HTC screen back to TWRP other than trying to reboot or pwr+vol down? Everything just keeps going back here. It wont even turn off without the battery draining.. I'll keep reading on my break, any other helpful comments are definitely welcome. Thanks.
Hold down the power button for 10 seconds and the lights on the capacitive buttons will blink. As soon as the screen goes black wait about half a second then hold volume down and power to get into bootloader then go into recovery.
Hope that helps you. That's how I've always gotten back into recovery when I have a bad flash.
Sent from my EVO using xda premium
BrianBaker said:
Hold down the power button for 10 seconds and the lights on the capacitive buttons will blink. As soon as the screen goes black wait about half a second then hold volume down and power to get into bootloader then go into recovery.
Click to expand...
Click to collapse
This is correct and works. Couldn't boot after trying to install Chainfie 3D drivers but got to recovery this way.
Sent from my EVO 4g LTE on my 3g network.
Happened to me. You have to flash the boot image for cm10 if I recall correctly.
Sent from my EVO
themorningsleeve said:
I was rooted on MeanROM, and from TWRP I cleared the cache and delvic cache and did a factory wipe, then tried to install the cm10 nightly build, but it said failed, so I cleared and wiped again and tried installing the FreshEVO ROM that I had on it before the MeanROM, it never finished installing, just froze after a while. then TWRP restarted then went into the white HTC "quietly brilliant" screen with the red disclaimer and stuck there. When i hold the power down, it just reboots back to this screen. I cant get it into recovery or bootloader or anywhere but this. My computer isn't recognizing the phone, I tried to adb to it from cmd but its not showing up. I don't think i had the latest hboot or whatever on it, it's been probably two months since i first rooted it. any help would be great, please and thank you. I'm heading to work but i'll check this on my breaks and answer any questions i can about what ive done. I was about to trade the phone for an s3 this saturday, but im sure he wont want it like this! THANK YOU.
Click to expand...
Click to collapse
did you ever get this going? Sounds like from what i was seeing you got into your BL finally. I would try reinstalling TWRP like the second part of the OP http://forum.xda-developers.com/showthread.php?t=1794867 and then select reboot to recovery from the bootloader ot the button method. If you get back into twrp restore the last working rom setup you had which sounds like meanrom. If it works come back and let us know.
motcher41 said:
did you ever get this going? Sounds like from what i was seeing you got into your BL finally. I would try reinstalling TWRP like the second part of the OP http://forum.xda-developers.com/showthread.php?t=1794867 and then select reboot to recovery from the bootloader ot the button method. If you get back into twrp restore the last working rom setup you had which sounds like meanrom. If it works come back and let us know.
Click to expand...
Click to collapse
Hey guys, on my lunch break, i got it working! I couldn't get it to go into recovery last night for the life of me, but i tried this morning on my way to work and it worked just fine like it should. For some reason none of my roms would install though other than the jewel stock of the latest update with root that i had on here. It worked and I'm good to go. Thanks for the help though! Anyone know why the roms that i installed before are falling Everette i try to install them now? I always wipe and restore first..
themorningsleeve said:
Hey guys, on my lunch break, i got it working! I couldn't get it to go into recovery last night for the life of me, but i tried this morning on my way to work and it worked just fine like it should. For some reason none of my roms would install though other than the jewel stock of the latest update with root that i had on here. It worked and I'm good to go. Thanks for the help though! Anyone know why the roms that i installed before are falling Everette i try to install them now? I always wipe and restore first..
Click to expand...
Click to collapse
I'm willing to bet that you are not S-OFF, and on Hboot 1.15 or higher, and that was the issue when you tried to install CM10. Make sure you read the instructions for flashing CM10, because you have to do something special to flash a kernel when you are S-ON. Now, as far as the old roms not being able to flash, it may be that they were based on the original 1.13 software version with the 1.13 kernel, and it won't let you flash over your current kernel because the version is older. Essentially, if you are S-ON, you can't flash a kernel unless it matches or is a newer version than the one you have. Of course, you can follow one of the many guides on how to flash boot (kernel) with S-ON to get around this.
timtlm said:
I'm willing to bet that you are not S-OFF, and on Hboot 1.15 or higher, and that was the issue when you tried to install CM10. Make sure you read the instructions for flashing CM10, because you have to do something special to flash a kernel when you are S-ON. Now, as far as the old roms not being able to flash, it may be that they were based on the original 1.13 software version with the 1.13 kernel, and it won't let you flash over your current kernel because the version is older. Essentially, if you are S-ON, you can't flash a kernel unless it matches or is a newer version than the one you have. Of course, you can follow one of the many guides on how to flash boot (kernel) with S-ON to get around this.
Click to expand...
Click to collapse
Wow yes this all made perfect sense! I didn't think about my old roms not being compatible, and i also didn't realize i needed s-off for cm10. I have a bad habit of thinking i can just throw a zip on my card and flash it and it will magically work perfectly lol.. This kind of thinking is what gets me into trouble! Where can i read about turning s-off for installing cm10? Are there links on the download page?
themorningsleeve said:
Wow yes this all made perfect sense! I didn't think about my old roms not being compatible, and i also didn't realize i needed s-off for cm10. I have a bad habit of thinking i can just throw a zip on my card and flash it and it will magically work perfectly lol.. This kind of thinking is what gets me into trouble! Where can i read about turning s-off for installing cm10? Are there links on the download page?
Click to expand...
Click to collapse
S-OFF info is here, but because you are having this issue, you probably have HBoot 1.15 or higher, which means you can't achieve S-OFF until a new exploit is found.
http://forum.xda-developers.com/showthread.php?t=1737123
There are methods for flashing kernels here with S-ON here:
http://forum.xda-developers.com/showthread.php?t=1794867
Also, there's the newer twrp dumlock method if you install the latest version ot TWRP (2.2.1). http://teamw.in/project/htcdumlock
timtlm said:
S-OFF info is here, but because you are having this issue, you probably have HBoot 1.15 or higher, which means you can't achieve S-OFF until a new exploit is found.
http://forum.xda-developers.com/showthread.php?t=1737123
There are methods for flashing kernels here with S-ON here:
http://forum.xda-developers.com/showthread.php?t=1794867
Also, there's the newer twrp dumlock method if you install the latest version ot TWRP (2.2.1). http://teamw.in/project/htcdumlock
Click to expand...
Click to collapse
Ok thanks. My main goal is to not screw this phone up before Saturday when i trade it for an S3 so i may not bother, but i will definitely give it a look!
themorningsleeve said:
Wow yes this all made perfect sense! I didn't think about my old roms not being compatible, and i also didn't realize i needed s-off for cm10. I have a bad habit of thinking i can just throw a zip on my card and flash it and it will magically work perfectly lol.. This kind of thinking is what gets me into trouble! Where can i read about turning s-off for installing cm10? Are there links on the download page?
Click to expand...
Click to collapse
You dont have to have s-off though like he said for cm-10 you just need an extra step or two. I dont blame you for trading it in I did the same. Except I am going back to the Gnex.
motcher41 said:
You dont have to have s-off though like he said for cm-10 you just need an extra step or two. I dont blame you for trading it in I did the same. Except I am going back to the Gnex.
Click to expand...
Click to collapse
I had the gnex before this, why did you go back to that out of the other 2?
themorningsleeve said:
I had the gnex before this, why did you go back to that out of the other 2?
Click to expand...
Click to collapse
Well I'm going back cuz of the non htc clustscrew and the openess of the platform. No bs no s on or s off dev unlocks etc...its how a phone should be. Better camera functionality and I know the sammy platform. Imho it may be older but its a far superior device. Could afford any device out there and to me its hands down gnex
Sent from my SPH-M900 using Tapatalk 2
motcher41 said:
Well I'm going back cuz of the non htc clustscrew and the openess of the platform. No bs no s on or s off dev unlocks etc...its how a phone should be. Better camera functionality and I know the sammy platform. Imho it may be older but its a far superior device. Could afford any device out there and to me its hands down gnex
Sent from my SPH-M900 using Tapatalk 2
Click to expand...
Click to collapse
right on. I did enjoy that phone. I LOVE the camera on my EVO LTE though, that's the one thing ill miss about this one. I did just find out that the ass that was supposed to trade me on saturday already traded someone, so i'm stuck with the LTE for a while now, so i might venture into putting cm10 on it, but then again i might wait til a more stable version hits, just depends on how long that may take..
themorningsleeve said:
right on. I did enjoy that phone. I LOVE the camera on my EVO LTE though, that's the one thing ill miss about this one. I did just find out that the ass that was supposed to trade me on saturday already traded someone, so i'm stuck with the LTE for a while now, so i might venture into putting cm10 on it, but then again i might wait til a more stable version hits, just depends on how long that may take..
Click to expand...
Click to collapse
Ruu it back to stock locked and ebay it. Should get enough for nib sealed gnex. I found one for 319.00. Saw a couple s3 on swappa for about 430-440 nib sealed. Saw a bad esn one going for 290ish so yours should be 350ish or more
Sent from my SPH-M900 using Tapatalk 2
CM10 should be going completely open source with the camera very soon. Expect good things.
To the people complaining about HTC and leaving/trading for new phones.... cya.
That isnt helpful here... we dont need an announcement. Just go please.
Rxpert said:
CM10 should be going completely open source with the camera very soon. Expect good things.
To the people complaining about HTC and leaving/trading for new phones.... cya.
That isnt helpful here... we dont need an announcement. Just go please.
Click to expand...
Click to collapse
Me and the op are having a good clean conversation in his thread so.... cya
Sent from my SPH-M900 using Tapatalk 2
motcher41 said:
Me and the op are having a good clean conversation in his thread so.... cya
Sent from my SPH-M900 using Tapatalk 2
Click to expand...
Click to collapse
Take your private conversation to PM?
I have officially stressed myself to the brink. I try to be calm but nowhere do I find how to fix my problem. I have tried flash image gui, I have tried htc dumlock, and I have also tried flashing the .img manually through fastboot usb then flashing the entire zip with twrp 2.2.2.0. Almost every time, I must recover from my TWRP and then use bootimg flasher v1.1 to stop my evo from getting stuck at the boot screen.
Everytime I attempt, I wipe the system and cache, then flash the boot.img, then flash the zip, then the gapps and reboot and it gets stuck on the splashscreen. I must note also that when I had first rooted, and installed Rom toolbox pro, I picked out a boot animation and installed it, restarted the phone, and it didnt work. BUT NOW sometimes after i flash the CM10 that random boot animation appears. WTF? even after i wipe the memory and everything. So I turned off the boot animation, and even deleted them from the phone off the app and it still comes up. I believe this is part or maybe IS the problem. But either way, I do not know how to deal with it. I have had the Cyanogenmod 10 boot animation ONCE out of the many times I have tried flashing but it was stuck on that screen forever like I have read other users have had happen. I REALLY, REALLY would like to be able to use the rom, as it has the new google now voice and all the cool features that i would like to have now that I am rooted.
NOTES:
I am running my stock rom. I have not installed any other ROMS on my phone. The backup i created was after I installed the stupid boot animation. (In case thats another problem)
When i tested the "current" boot animation from within rom toolbox pro, the normal htc evo 4g lte Sprint one loaded but yet, the retarded one i chose for ****s and giggles is what keeps loading. FML (I shouldve chose at least a cool one.)
My backup works fine. I am damn glad i made it!!!
Sorry for any grammatical errors, lowercase i's and what not. im too lazy to press the shift key sometimes. (Caps lock is broken. FML.)
Also sorry for it being so long. I am trying to be thorough to give you experts what you need to help me out.
If you need anymore info as far as detail instructions i will be happy to write back on this forum.
PLEASE do not tell me that my answer is on another forum, because I believe that it is not due to the special situation I have. I have tried looking for days for an answer.
I will be periodically checking this forum for any replies and will reply ASAP, whenever i am available.
Thank you for your time and patience!
Here is my phone's specs. I tried to get as much as possible. Again, if there is more info that would be needed I will gladly get it and post it here.
I am running on booloader:
Tampered
Unlocked
Jewel PVT SHIP S-ON RL
HBOOT- 1.19.0000
Radio- 1.12.11.0009
OpenDSP-v29.1.0.45.0622
eMMc-boot
Aug 9, 2012, 15:14:25
About Phone:
Hardware Version 0003
Android Version 4.0.4
Sorftware 2.13.651.1 710RD
HTC Sense Version 4.1
HTC SDK API level 4.24
HTCExtension_403_1_GA_22
PRI Version 2.45_003
PRL Version 25006
Anyone?
Sent from my EVO using xda app-developers app
What happens when u fastboot the kernel? Does it say success?
Sent from my EVO using xda premium
Use fastboot to flash the kernel, if you still have trouble wipe the partion and try again
Fastboot flash boot boot.img extract it from the Rom and place in adb folder.
Fastboot erase boot to wipe partition
I had problems trying out CM10 also. This worked for me.
Edit:: I'm assuming you have TWRP recovery and are unlocked before you start this...
Buy Flash GUI from app store. Worth the 99 cents!
Open it and point it to the CM10 zip. It will extract the parts it needs and flash the kernel.
Once that is done have it reboot (it prompts you) into recovery and then wipe system, do factory reset, then flash the CM10 zip and gapps zip.
Reboot one last time
The CM10 animation went on for a couple/few minutes the first time, don't panic.
You should be good after that.
Make sure to install Flash GUI again though. You will need to use it to go back to a ICS/Sense ROM later (using same method). And my guess is you might want to.
CM10 is incredible on this phone but it's not quite ready. I have tons of data connection issues and NEVER get 4G in the places where I've always had good signal. Also, the camera is just about worthless. No disrespect to the devs working on it. I'd have no idea how to work the magic they are doing and I appreciate their time.
Good luck.
I did the very same thing earlier today. I flashed CM10 without paying attention tot he fact that I was unlocked but still had S-On so the phone would continually get stuck on the boot screen. I must have reflashed and formatted with TWRP 10 times before diving into it deeper.
In terms of workflow the only way I could make it work properly was to:
1. Use TWRP to flash CM10 and gapps (just add both zips)
2. Reboot into bootmanager using TWRP.
3. Use fastboot to flash boot.imgfrom the CM10 zip (fastboot flash boot /path/to/boot.img)
If I did the boot.img first it didn't seem to work, it should so maybe that wasn't the real issue but the above process worked and I'm now running CM10.
When I fast boot the kernel everything says success with no errors
Sent from my EVO using xda app-developers app
How do you partition? Do you think that is my problem?
Sent from my EVO using xda app-developers app
You don't need to partition anything, just flash kernel and reboot
Hey guys thanks to everyone replying! I'm currently at work as a delivery driver trying to write back.... Dangerous! Lol but also I have the 5 min limit to post so I will try and do some of these methods when I get home and report my findings to you all ASAP! But to anyone with more suggestions please keep bringing Em!
Thanks!
Sent from my EVO using xda app-developers app
Hey guys its me again. I just got home and I'm dead beat tired. I had to work later than I thought. Im gonna get some sleep but once again thank you everyone for giving me some answers that I can try tomorrow! I will, without a doubt, try some of them tomorrow after my classes. But first I would like to leave you all with a VERY important question that I did not think of. Is there a stable release of cm10 that has worked for you all that I can try? Perhaps that was the problem too? I was trying the nightly release that came out October 2. Once again thank you all for replying and i will try to do this ASAP after class. Sorry to leave you guys hanging so much!
Sent from my EVO using xda app-developers app
Thing is it's a nightly, some people have flashed back to earlier versions and others upgrade with out any issues. Ymmv
padrino121 said:
I did the very same thing earlier today. I flashed CM10 without paying attention tot he fact that I was unlocked but still had S-On so the phone would continually get stuck on the boot screen. I must have reflashed and formatted with TWRP 10 times before diving into it deeper.
In terms of workflow the only way I could make it work properly was to:
1. Use TWRP to flash CM10 and gapps (just add both zips)
2. Reboot into bootmanager using TWRP.
3. Use fastboot to flash boot.imgfrom the CM10 zip (fastboot flash boot /path/to/boot.img)
If I did the boot.img first it didn't seem to work, it should so maybe that wasn't the real issue but the above process worked and I'm now running CM10.
Click to expand...
Click to collapse
Which nightly did you use?
Hey guys so I used padrino121s suggestion for flashing. At first I tried flash gui again like you had suggested but it got stuck in the boot screen. So I decided to download a different nightly release (20121002) and it flashed perfectly and everything transferred over correctly! Thank you guys so much for all of your help! Now one more question... If I decide to get a new nightly build, do I have to flash everything all over again like I had to the first time? Or because I have flashed cyanogen mod already do I just do something else to update it?
Sent from my EVO using xda app-developers app
I have my Evo 3D and I decided I wanted to flash a ROM on it.
Basically I rooted it and went to flash a ROM on it, and ended up deleting the dalvik cache and cache.
The bad part is, I forgot (like a complete idiot) to do a Nandroid backup.
Is there any way to come back from this?
you could just run an RUU and get back to stock.
btw what problem do you have while flashing new roms?
deleting the dalvick cache and cache dousnt matter, it automatically creates it.
If you haven´t backup up your previous rom, then you cant recover it... that´s why it´s called a backup..
So whats the problem?
I think i read it wrong. do you mean you want to restore your previous stock rom + data? if so its not possible to restore the data without a nandroid.
EM|NEM said:
you could just run an RUU and get back to stock.
btw what problem do you have while flashing new roms?
Click to expand...
Click to collapse
That works even though I can only see the bootloader screen / TWRP recovery screen.?
And my problem was that I had an error while trying to flash room. I might have done it wrong.
But I just want my phone to work. I dont need my apps or contacts etc
.
Not sure what the problem is either. If you delete the dalvik turn the phone back on and it automatically recreates it. No problems what so ever.
It sounds like you flashed or tried to flash a ROM without doing a full wipe. However I'm not sure.
Perhaps you could tell us in more detail the problem and what you would like to do and we can help ya..
Sent from my PG86100 using Tapatalk 2
I know that you are trying to help, but all I wanted to know was how to make it back to normal. But seeing as I did it incorrectly, I could really use the help.
I did not do a Nandroid backup.
What I did was try to flash the rom without wiping my phone, like you said.
Then I selected the option of clearing both cache and dalvick cache.
Then tried flashing rom again. Did not work.
I am sorry I cant recall what the error was when doing it, but I will let you know when I try again in a second (if it doesnt work this time.) [ I also found a different tutorial and would like to give it a try.
There isn't a way to get back to the same state your phone was in before wiping it since you did not do a backup. If you are gsm then find the gsm RUU. If CDMA then find the CDMA version. That will get you back to the stock version but it will be as if you just turned it on for the first time ever.
It would be easier to just download a different ROM and put it on your SD card then flash it. Although it won't be stock...
But before doing any of that just boot recovery and do a full wipe. Then reflash the ROM you were trying to install.
I got back to stock with RUU. Then I figured out how to successfully back up and flash my phone with different roms.
Thank you for all your help.
Good luck in your flashing endeavours! Its addicting.
I actually am having an issue. I am trying to flash a rom on my phone and it says im extracting boot.img with a progress bar on the bottom. The progress bar seems to be staying at one point and not moving.
He said something about naming something to PG86IMG and wasnt clear to me what to name PG86IMG.
Any speculations?
Edit: was impatient.
zdirty said:
I actually am having an issue. I am trying to flash a rom on my phone and it says im extracting boot.img with a progress bar on the bottom. The progress bar seems to be staying at one point and not moving.
He said something about naming something to PG86IMG and wasnt clear to me what to name PG86IMG.
Any speculations?
Edit: was impatient.
Click to expand...
Click to collapse
Got it figured out? Phone working?
Sent from my PG86100 using Tapatalk 2
Are you still s-on btw? Since i saw you had problems with boot.img
Try gaining s-off, flash hboot 1.49.0007 and all of your flashing problems will be gone!
klect said:
Are you still s-on btw? Since i saw you had problems with boot.img
Try gaining s-off, flash hboot 1.49.0007 and all of your flashing problems will be gone!
Click to expand...
Click to collapse
Yes I am on s-on. I did not want to do the wire trick.
I didnt either, now having s off, i cant imagine using the evo 3d with s on.
Sent from my Evo 3D GSM using xda app-developers app
klect said:
I didnt either, now having s off, i cant imagine using the evo 3d with s on.
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
I tried the wire trick. Couldn't get it to work. Maybe because I used speaker wire which isnt a sold wire but strands. Do you think that makes a difference?
As long as there is a connection all the way through, no. Keep in mind i tried 20 times or so, you have to get the timing right.
Take another look at the demo vid and try again, if you're not sure about the wire, use a paperclip with some tape around it. (tape is important, you don't want your skin to touch the metal)
klect said:
As long as there is a connection all the way through, no. Keep in mind i tried 20 times or so, you have to get the timing right.
Take another look at the demo vid and try again, if you're not sure about the wire, use a paperclip with some tape around it. (tape is important, you don't want your skin to touch the metal)
Click to expand...
Click to collapse
I did the wire trick about a week or two ago and I couldnt time it just right so I just continuously tapped the SD card metal holder dealio with the paperclip about every second and it worked the fourth or fifth try.
Sent from my PG86100 using Tapatalk 2
Can somebody please provide me with a forum on how to unlock the bootloader, root the phone, and install a custom recovery on my droid dna. My software version is 2.07.605.1 710RD. Thank you.
http://forum.xda-developers.com/showthread.php?t=2437614
Sent from my dlx using Tapatalk
Or here.. http://forum.xda-developers.com/showthread.php?t=2314771
Sent from my HTC6435LVW using xda app-developers app
Looking for the same info...
gocool767 said:
Can somebody please provide me with a forum on how to unlock the bootloader, root the phone, and install a custom recovery on my droid dna. My software version is 2.07.605.1 710RD. Thank you.
Click to expand...
Click to collapse
I'm a complete n00b to rooting and have been trying to find an answer to the same question before diving in. I have looked through tons of info, including the 2 threads posted in responses, but can't seem to get a clear answer as to whether these methods work for 2.07... There seems to be a lot of conflicting reports. Would love to know if you confirm that either of these work.
May have answered my own question
It looks like there are further reports of moonshine working on 2.07.
http://forum.xda-developers.com/showthread.php?t=2510910
I'm going to give it a try tonight and will report back here.
I haven't seen anything about unlocking or rooting on 2.07, only s-off. I have a new DNA being shipped out thanks to my warranty, but I really don't want to go back to 4.1 after being on 4.3 for a few great months!
Moonshine works on recent dnas
schott12521 said:
I haven't seen anything about unlocking or rooting on 2.07, only s-off. I have a new DNA being shipped out thanks to my warranty, but I really don't want to go back to 4.1 after being on 4.3 for a few great months!
Click to expand...
Click to collapse
Yep, sorry for mixing up unlocking and rooting with s-off. I just thought getting s-off would better for a n00b like me as it seems to make the custom ROM / kernel process a bit more straight forward.
thayl0 said:
Moonshine works on recent dnas
Click to expand...
Click to collapse
I tried last night and ran into a few problems and then ran out of time. Got an error along the lines of [can't obtain temproot] during one of the moonshine steps... This may be due to the fact that I did not factory reset before moonshining. I will try again this evening (after factory reset).
Do you know I should go through the normal phone set-up after the factory reset? Or just reset then dive into moonshine?
Thanks!
GrzlyAdms said:
Yep, sorry for mixing up unlocking and rooting with s-off. I just thought getting s-off would better for a n00b like me as it seems to make the custom ROM / kernel process a bit more straight forward.
I tried last night and ran into a few problems and then ran out of time. Got an error along the lines of [can't obtain temproot] during one of the moonshine steps... This may be due to the fact that I did not factory reset before moonshining. I will try again this evening (after factory reset).
Do you know I should go through the normal phone set-up after the factory reset? Or just reset then dive into moonshine?
Thanks!
Click to expand...
Click to collapse
I'd think factory reset everything. I believe that is what I done. There is a support page for the moonshine program but I forget where it was.
---------- Post added at 06:12 PM ---------- Previous post was at 05:55 PM ----------
GrzlyAdms said:
Yep, sorry for mixing up unlocking and rooting with s-off. I just thought getting s-off would better for a n00b like me as it seems to make the custom ROM / kernel process a bit more straight forward.
I tried last night and ran into a few problems and then ran out of time. Got an error along the lines of [can't obtain temproot] during one of the moonshine steps... This may be due to the fact that I did not factory reset before moonshining. I will try again this evening (after factory reset).
Do you know I should go through the normal phone set-up after the factory reset? Or just reset then dive into moonshine?
Thanks!
Click to expand...
Click to collapse
I found the site..
I must had been on 2.06 when i done mine. I didn't even know there was another update.
I read on the moonshine site its only for 2.06
JUst type moonshine droid dna and you'll see it. I don't think I'm allowed to post links.
Well, I can 100% confirm that moonshine works for 2.07. It took several tries (4 to be exact, with factory reset between each), but I am now s-off! Woohoo! Now on to flashing twrp, and my first try at a custom ROM.
GrzlyAdms said:
Well, I can 100% confirm that moonshine works for 2.07. It took several tries (4 to be exact, with factory reset between each), but I am now s-off! Woohoo! Now on to flashing twrp, and my first try at a custom ROM.
Click to expand...
Click to collapse
Let me know if you need help flashing and ill tell you how.
thayl0 said:
Let me know if you need help flashing and ill tell you how.
Click to expand...
Click to collapse
Thanks for the offer! I was actually able to flash twrp and a custom ROM. It was much easier than I originally anticipated. My eyes are now open to a whole new world... Not sure I'll ever be able to go back to a stock Stock/manufacturer ROM.
Now running ViperDNA 2.0.1. I picked Viper as it sounds like this is one of the most stable/least buggy ROMs out there right now (plus it runs fine on the stock kernel). Do you have any other suggested ROMs for the DNA?
GrzlyAdms said:
Thanks for the offer! I was actually able to flash twrp and a custom ROM. It was much easier than I originally anticipated. My eyes are now open to a whole new world... Not sure I'll ever be able to go back to a stock Stock/manufacturer ROM.
Now running ViperDNA 2.0.1. I picked Viper as it sounds like this is one of the most stable/least buggy ROMs out there right now (plus it runs fine on the stock kernel). Do you have any other suggested ROMs for the DNA?
Click to expand...
Click to collapse
Looks good.
I too just had success with Moonshine. Just literally got my DNA, previous owner took the OTA. First time failed at "temproot", second time ran flawless.
Congratulations if u need help installing. SDK. Adb. Fastboot. Recovery and or a ROM. Message me
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Well, still troubleshooting some things. Successfully had root access and using the correct settings I could run wireless tether fine. I then proceeded to backup then install viper Rom. Set everything up fine however nothing I tried would get tether going. So I restored my backup (tether is a must) and still same issue. It starts but I cnt connect which is strange as I was using it fine earier.
So now I did a factory reset and flashed superuser, now tether won't start. Says "started with errors" using the exact same settings. So I'm going to try flashing the stock ota deodedex Rom see if that solves it.
Sent from my HTC6435LVW using xda app-developers app
GrzlyAdms said:
Well, I can 100% confirm that moonshine works for 2.07. It took several tries (4 to be exact, with factory reset between each), but I am now s-off! Woohoo! Now on to flashing twrp, and my first try at a custom ROM.
Click to expand...
Click to collapse
Did you use the Windows or Linux version?
Little Green Robot said:
Did you use the Windows or Linux version?
Click to expand...
Click to collapse
Windows (Vista believe it or not...). Make sure you have the correct device drivers installed first, and uninstall HTC Sync.
Sent from my dlx using Tapatalk