I don't have much experience rooting, but what I did was unlock hboot 2.09.0000 so far, with twrp installed to recovery, but I tried to flash beanstalk and grappa subsequently without rebooting and I think that might have caused it to not work. In the process of trying to fix the boot loop, I also wiped all data, including my backup for the stock rom. Therefor I do not know how to get a new rom onto my phone. I have a folder with adb, fastboot, adbwinapi.dll, and the beanstalk and grapps. I tried typing adb push "beanstalk file name here" /sdcard and that doesn't seem to do anything. It just gives me a big list of adb commands. Any ideas?
bposch said:
I don't have much experience rooting, but what I did was unlock hboot 2.09.0000 so far, with twrp installed to recovery, but I tried to flash beanstalk and grappa subsequently without rebooting and I think that might have caused it to not work. In the process of trying to fix the boot loop, I also wiped all data, including my backup for the stock rom. Therefor I do not know how to get a new rom onto my phone. I have a folder with adb, fastboot, adbwinapi.dll, and the beanstalk and grapps. I tried typing adb push "beanstalk file name here" /sdcard and that doesn't seem to do anything. It just gives me a big list of adb commands. Any ideas?
Click to expand...
Click to collapse
It looks like you didn't get S-off yet. If you haven't, your issue is that you didn't push the kernel in with ADB. There is no real reason to not go S-off, go get it and then flash whatever you want. If you don't want to do the S-off then you need to learn how to push the kernel in before you flash a ROM that requires it, and Beanstalk requires it since it is CM based.
Since you're on hboot 2.09 there are two you could use for S-off:
http://forum.xda-developers.com/showthread.php?t=2321072
http://forum.xda-developers.com/showthread.php?t=2498684
To get a working Rom on your phone, download meanbean (s-on friendly) to your pc. Boot your phone into recovery and connect to your pc. Select mount in TWRP and mount usb storage. You should see your phone on your pc. Drag the Rom to your phone then unmount, install the Rom with TWRP. That should get you up and running. Then get yourself s-off. Life is easier.
EVOlved human
Related
so I have the latest software, used the HTC unlock method, was rooted and had the TWRP recovery working just fine, I'm an idiot and flashed the CM recovery through RM and of course it didn't work, so I've tried every which way I can find to re-flash the TWRP and even tried flashing AMON but it will not go into recovery with any of them after it says it successfully wrote the recovery.
TWRP and CM just wait for a minute then reboot normal, AMON reboots then sits at the HTC screen... forever and i have to pull the battery.
I tried uninstalling RM to see if it was F'ing with it, didn't matter.
not sure what to try next to get a working recovery back onto the phone, I'm still rooted just running the stock ROM, I had loaded an alternate ROM successfully last week, just didn't like it. So I know all is 'working' as expected I just F'd up the recovery part now
any help??
afaik if you used the HTC unlock you need to fastboot flash it, or maybe hboot zip it? What have you tried so far?
I've tried using fastboot to flash amon and TWRP, same result
tried doing TWRP as a zip as well
what's weird is each method seems to "work" i get that it's pushing, writing, completed, no errors with any of them but then it just won't go into recovery and if i change to different recoveries I get different reboot behaviors just none of them work.
that's where I'm stuck, I feel like I've tried all the methods it just refuses to actually go into recovery when it's loaded.
another thing I thought was weird though, when I reflashed TWRP, and then go into RM it would say at the top that I had the latest version of CM installed like it didn't take? I uninstalled RM and tried it all again, same result.
morellox said:
I've tried using fastboot to flash amon and TWRP, same result
tried doing TWRP as a zip as well
what's weird is each method seems to "work" i get that it's pushing, writing, completed, no errors with any of them but then it just won't go into recovery and if i change to different recoveries I get different reboot behaviors just none of them work.
that's where I'm stuck, I feel like I've tried all the methods it just refuses to actually go into recovery when it's loaded.
another thing I thought was weird though, when I reflashed TWRP, and then go into RM it would say at the top that I had the latest version of CM installed like it didn't take? I uninstalled RM and tried it all again, same result.
Click to expand...
Click to collapse
*my opinion*
delete rom manager
boot into recovery using adb
"adb reboot recovery"
or terminal emulator
"reboot recovery"
or the app "quickboot"
does that work?
I've tried all those except Quickboot... *trying now......*
annnnnd
same thing with the app...
I'm thinking at this point I almost need to just write everything over again? use a flashable zip in the bootloader and just have it write everything over again, I was going to do a new rom anyways bored with the stock again.
so I need to find that I guess? re-write everything go back to fresh and start over
1. Make sure u r not flashing CDMA recovery over a GSM device, or vice versa.
2. How did u get ur device rooted in the first place?
3. Last resort, relock ur device and apply the correct RUU, then unlock and root again.
Sent from my HTC EVO 3D X515m using XDA App
1) good there
2) I followed a tutuorial where I pushed the recovery and the SU file after doing the HTC official unlock method, worked great at first, I'm the idiot that pushed the CM recovery over top of it and now I can't get a working recovery back on.
3) do I really have to relock first, I've seen the simple tutorial on doing so, I was hoping maybe I could find an all in one flashable ROM that would at least get me back to operational on all partitions and then re-work that one with a new ROM later or something, not possible?
This is of no help to you but - I had the same error. TWRP v1.0.3. I tried everything in the book to get it to work... but got stuck at the HTC splash screen like you. And I tried installing the 1.13 PG86IMG and then my device turned off while installing the PG86IMG (it was fully charged during flashing, I checked). Be careful with what you do.
I was unlocked with AlphaRev's tool, running my own ROM.
mine hung like that if i flashed AMON, but i could still pull the battery and go back into the bootloader to flash at least TRWP using FastBoot so I could get back into the phone
ugh
morellox said:
mine hung like that if i flashed AMON, but i could still pull the battery and go back into the bootloader to flash at least TRWP using FastBoot so I could get back into the phone
ugh
Click to expand...
Click to collapse
htc unlock method has proven to be a bit shady for the community in that it doesnt allow all the features/functions the revolutionary (and prior unrevoked) unlock method does.
most developers unlocked with revolutionary and haven't performed the htc unlock method so it has been hard to gather technical details on the htc unlock method.
one item we can eliminate in the effort to narrow down your issue: there is no working Amon RA recovery for the EVO 3D. not sure where you obtained Amon RA recovery. TWRP was created to pick up the torch from the Amon RA recovery as he retired from developing his recovery to support emmc devices.
stick to either flashing the twrp or cwm recovery images. there are only a handful of ways to load a custom recovery and only a handful of ways to boot the device into recovery mode.
i'd follow a logical pattern and work your way through the avaiable options. by following the available options one step at a time you should be able to narrow down which methods work and don't work. sorry it has been difficult as this htc unlock method is newer to the community we aren't as familiar with it as we are the revolutionary method.
ways to flash a custom recovery:
1) fastboot - fastboot flash recovery c:\downloads\recovery.img
2) bootloader - PG86IMG.zip file containing recovery.img and android-info.txt
3) flash_image - while in normal android mode (my app Flash Image GUI works well for this)
ways to boot into recovery mode:
1) turn device completely off and unplug USB. vol down + pwr loads bootloader. select recovery from the menu
2) from android mode: adb shell reboot recovery
3) from android mode: use a 3rd party app like quick boot.
this is all off the top of my head so it might not be an *exhaustive* list but it should cover all the common approaches. hope that helps and keep us updated! good luck!
damn...
I really appreciate everyone's help here I've been a part of various forums for a REALLY REALLY long time... from the days of Nextel, then I was a Palm Lover for a few years and now Android.
this obviously isn't urgent as my phone is working just fine, I just can't flash a new ROM since I can't get any recoveries working.
unfortunately I'm pretty sure I've tried all the methods listed above, I'm going to probably sit down sometime this weekend and systematically go through each method one more time just to be sure. TWRP worked for me just fine in the beginning, I flashed a ROM more than once, reverted back to my old ROM, made back ups, cleared cache's all the stuff I'd need to do.
thanks everyone, I'll keep trying
and no one knows of a flashable 'rom' that would have all the different partitions included in a zip or something like that? like.... what is in place of recovery in a stock phone? I can always unroot and start over but I did use the HTC unlock method so I hope that even works
got one to work! followed this method
http://forum.xda-developers.com/showthread.php?t=1239455
i have been searching these forums for the past few days and have come up dry.. i have an htc rezound and I want the OTA BUT i have perm rooted it and removed most (if not all) the bloat... how do i go about rebloat and relocking my phone? i have tried using cleantool and it keeps waiting for the phone or it just fails all over itself repeatedly
edit: i have it set to charge only, sync is off and closed, and it is in fastboot mode. I have also tried something I found on here which seems like it is very similar to cleantools with less functionality and it just says <waiting for device> indefinitely
twich12 said:
i have been searching these forums for the past few days and have come up dry.. i have an htc rezound and I want the OTA BUT i have perm rooted it and removed most (if not all) the bloat... how do i go about rebloat and relocking my phone? i have tried using cleantool and it keeps waiting for the phone or it just fails all over itself repeatedly
edit: i have it set to charge only, sync is off and closed, and it is in fastboot mode. I have also tried something I found on here which seems like it is very similar to cleantools with less functionality and it just says <waiting for device> indefinitely
Click to expand...
Click to collapse
There are a few different ways to do it. Easiest way I did it to make it foolproof, is flash stock recovery if your on a custom recovery and relock phone and run the RUU. It will put you back to stock and you can just download the OTA and update it, then Unlock and flash Amon Ra recovery and from the developer menu install SU and superuser to reroot.
If you need more instructions , just ask otherwise to me that was the easiest way.
P.S. Just be aware the internal SD card gets wiped after you unlock again so move anything off the internal SD to the external SD that you want to save prior to unlocking again.
I didnt take the ota, I used cons ota rom.. this was my steps for that
1) download rom from here http://forum.xda-developers.com/showthread.php?t=1467329
2) boot into recovery, flash rom....
here you can go two ways, if you dont want the new baseband, it will flash the ph98img and not do anything, if you want the new radios I will tell you how I did it, then tell you where you need to start if you wont want them.
3)perform nandroid
4)via adb (thing you used to unlock originally) fastboot oem lock YOU ARE NOW LOCKED.
5)boot into hboot it will flash the ph98img
6) Unlock bootloader (find the email with the unlock.bin code and follow those instructions)
7)Reboot phone
8)connect to pc, charge only usb debugging enabled
9)run one click root
Proceed with this if you get the mainver error ONLY otherwise if having wifi issues, proceed to step 13
10) after rooted follow this post http://forum.xda-developers.com/showthread.php?t=1467099 NOTE, op in the thread supplied his miscnew.img USE IT!
11)Read this thread http://forum.xda-developers.com/showthread.php?t=1459347&highlight=mainver it will explain how to get the ph98s to work.
11a) do the ph98 file thing to the ph98 img in amon ra to get it to flash in bootloader
12) after amon ra is restored, perform restore nandroid.
If wifi is not working, even if you dont have mainver issues do step 13
13) If having wifi issues as in not working go to this thread http://forum.xda-developers.com/showthread.php?t=1467793 and follow instructions EXACTLY!!!
Now you should be running new radios, hb2.11, the 2.6 kernel etc.
You will have to follow the post in step 11 to get any ph to work from now on.
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, BURN YOUR HOUSE DOWN OR ABDUCTED BY ALIENS BY FOLLOWING THE ABOVE INSTRUCTIONS.
im having some trouble getting into recovery because clockworkmod says it does not have an officially supported recovery... how do i manually install one?
Assuming you installed a recovery, just boot to Hboot. Pull the battery, then hold the power button and volume down button. Once in Hboot you can choose Recovery.
twich12 said:
im having some trouble getting into recovery because clockworkmod says it does not have an officially supported recovery... how do i manually install one?
Click to expand...
Click to collapse
To flash a recovery do the above steps to get into hboot (power down, pull battery, hold volume down and power buttons) and once you are in hboot, choose fastboot. Then connect to your pc and in the pc cmd prompt type:
fastboot flash recovery nameofrecovery.img (name of stock recovery you need to download, trying to find a link for you...)
That will put the stock recovery on the phone, then you can run RUU to get the rest back to stock and you can then accept the OTA.
feralicious said:
To flash a recovery do the above steps to get into hboot (power down, pull battery, hold volume down and power buttons) and once you are in hboot, choose fastboot. Then connect to your pc and in the pc cmd prompt type:
fastboot flash recovery nameofrecovery.img (name of stock recovery you need to download, trying to find a link for you...)
That will put the stock recovery on the phone, then you can run RUU to get the rest back to stock and you can then accept the OTA.
Click to expand...
Click to collapse
got it! OTA and everything.. debating on rerooting for a bit thanks a lot everyone! +rep
All you have to do to reroot now is flash Amon Ra and then install su from within that. So it's super easy at this point.
su seems to have remained installed.... no root but su is definitely still installed! the only reason i am going to wait on rerooting is so i can learn more about it before i flash or anything
Yeah, it will show up in your apps but it doesn't work properly until you reinstall. I thought I had remained rooted but when I went to use Titanium Backup it couldn't get root access, then after I reinstalled su it worked fine.
But yeah, if you don't need it yet don't worry about it. The only good reason to do it is to use TiBU to save all your settings and if you have Amon Ra you can make a nandroid of your phone so that if something happens you have a backup image of everything and can restore it very easily via Amon Ra. You can still stay on stock ROM etc... the only thing you would need to flash is the Amon Ra recovery.
ya i see what you mean... I also want to get rid of this unbelievable amount of bloat... geez their are a ton of useless verizon apps never mind the stupid games
[FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-13
My friend's phone had the annoying bootloop problem. I'm posting this because after a lot of searching, I found nothing to fix the bootloop, just people asking about it. Here's a simply fix.
BOOTLOOP FIX:
If you already tried unlocking/ and you're still S-On, then set everything back to stock:
Flash the attached stock recovery,
fastboot oem lock to be locked again.
Use the latest RUU to update the phone.
At this point the stock, locked phone should function normally.
I have busted this phone a ton of times trying to get different recoveries and roms to work, and this method has always fixed the bootloop.
At this point you can try whatever tutorial you like to downgrade or customize the phone...and if it breaks, hopefully this method will still work for you. If it doesn't work the first time, try running the RUU a second time. Or third.
CUSTOM RECOVERY:
If you want to unlock and install custom stuff:
Use the HTC Dev unlock method.
Fastboot install CWM Recovery v5.8.0.1 from their website -
The ONLY recovery that I've found to be compatible with HBOOT 1.58 is CWM v5.8.0.1. Everything else leaves the phone in an infinite bootloop. Maybe others have had different experiences.
To fastboot install the CWM recovery, rename the file to recovery.img (for simplicity) and type in a command prompt (same directory as fastboot and recovery.img):
fastboot flash recovery recovery.img
Then, to enter into recovery, either pull the battery and enter recovery through the bootloader menu, or type in:
fastboot boot recovery.img
This should get you into the working CWM recovery. If it doesn't, it's because HTC hates people that buy their phones.
If you feel like giving up and running stock, all you need to do is reflash the stock recovery, and relock the phone using fastboot oem lock - and now it should run the stock rom...and if it doesn't, then rerun the RUU. Tedious.
HBOOT Downgrade & S-Off:
If you have: Stock 2.89 RUU / Locked / S-On
Unlocked with HTC Dev method
Flash CWM 5.8.0.1 from the CWM website:
fastboot flash recovery recovery.img - then
fastboot boot recovery.img (to enter recovery)
Flash the SetMainVersionLOW.zip file attached (thanks ramjet73)
Relock the phone with: fastboot oem lock
Use the Unknownforce/closeone hboot downgrade with live CD using the 2.89 RUU's rom.zip (from windows temp folder) renamed to PG86IMG.zip - go to the Unknownforce/closeone thread for this part: http://forum.xda-developers.com/showthread.php?t=1563342
Then flash the standard 1.13 RUU on your windows system (may also work with the PG86IMG.zip method, have not tested)
Then use revolutionary 0.4pre4 to S-Off
Finally, you need to flash a custom recovery which you can do from revolutionary, or from fastboot as listed above. Once the recovery is installed, you should be able to install a compatible custom rom and kernel.
You bootloader screen should now say REVOLUTIONARY on top instead of UNLOCKED or RELOCKED etc... and show HBOOT 1.40.1100.
Thanks to Unkownforce, closeone, and ramjet73 for making this possible.
PS. Screw up your phone at your own risk.
In case anybody was wondering, the RUU I've been using is the latest one at the time of this post: RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to be one of the stock versions I guess, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
mnomaanw said:
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to one of the stock versions, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
Click to expand...
Click to collapse
Yeah, don't ever do the write secure flag command. That's bad news. Running a ruu will not s- on, and you're better staying s-off
Sent from my PG86100 using xda app-developers app
Reset s-on, and
fastboot oem lock to be locked again.
Click to expand...
Click to collapse
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
xHausx said:
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
Click to expand...
Click to collapse
@xHausX
Totally agree. The only reason to set S-ON once S-OFF is achieved is to return to 100% stock for warranty service or to sell the phone.
Nice to see you in these parts again and Happy New Year!
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
I updated the OP. I read somewhere else that it was necessary, this phone was never S-Off, so I wasn't sure.
Thanks
Everytime i run the ruu for my 3d it will finish as it has completed and boot. But whenever i remove my battery to switch it with a secondary, i used to do this before bed every night, i get a bootloop and cant boot untill i boot into bootloader and select the recovery option which wipes the phone and boots untill then next time i remove the battery. Why wont the RUU fix this? ive ran it multiple times. And also whenever im in the stock recovery and i select factory reset or any of the options i get "invalid option" "sucess rebooting by reason oem-00" what does this mean!?! can this be my sd? cause i cant mount cache recovery command or mount anything in recovery for that matter. if i need an sd ill buy one. just dont wanna find out its not my sd. and ive run the RUU about 7 times in total and nothing helps. thanks
ramjet73 said:
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
Click to expand...
Click to collapse
Yeah, I put WIP because it still never worked right, it was just the only one that ever actually loaded. I still hate this phone, I wish HTC was as nice as Samsung. It's so easy to work with Samsung, I always get mad trying to work around HTC's crippling B.S. Still better than Motorola though.
bootloop in my Htc Evo 3D hboot 1.53.007
How do you flash the stock recovery?
jcthelight said:
How do you flash the stock recovery?
Click to expand...
Click to collapse
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
i have hboot 1.53 with s-on stuck on bootloop and i did as u said i flashed stocked recovery from temp folder from ruu-ics-35-ara.exe still my phone is in boot loop. Even i tried oem lock and run ruu.exe file upto 65% process goes fine then suddenly shows 100% process complete and reboot device(still stuck on bootloop).... plz give me suggestion to get rid of this thing.....
"RUU_SHOOTER_U_ICS_35_S_HTC_ARA_3.28.415.2_Radio_11.77.3504.00U_11.25.3504.06_M_release_264795_signed.exe"
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
I'm a little confused. I've never rooted this phone so it's completely stock. My phone keeps powercycling. When I type in "fastboot flash recovery recovery.img" my cmd prompt tells me FAILED (remote: signature verify fail).
Any suggestions?
Re: [FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-
Dang it! Why does it seem like developers have quit developing fully functioning roms for this phone? I live in a good 4g area so those roms without it are out of the question for me. And the others are having major issues with cameras, video playing, text messaging that keep it from being a daily....
And after using jellybean these ICS roms feel very incomplete even though they're more functional. I know you developers are busy people but please, can ICS get freshened up. Or just ignore me if y'all think the camera/text thing will be resolved very soon.
Sent from my PG86100 using xda premium
Hi there everyone!
My main problem is flashing hboot 1.15
I misinterpreted a sentence of instructions over at ViperDNA ROM thread, and attempted to flash Viper 1.3.0 with a custom kernel (it had been so long, I forget which. Cubed or DSB, idk) and after getting through aroma and successfully installing, it was stuck at a bootloop. Well I went back and read the instructions and comment again and apparently installing with anything other than Stock boot.img is a big no no. Anyways, I am stuck here without any type of ROM (relocking the bootloader to attempt to RUU.exe left my internal storage wiped) and unable to get the RUU.exe method to work (Error 155 most likely because I have hboot version 1.33.0001 and not 1.15). I cannot get the RUU.exe or the RUU.zip flash method to work. I have flashed a stock boot.img since then and have gone through different locked/relocked stages and tried ADB sideloading a stock ROM ("unable to mount /data /system" etc.). Right now, I am trying (using the HTC Droid DNA Toolkit program) to flash the 1.15 hboot, but it is stuck at "<waiting for device>". I have also tried "fastboot.exe fastboot oem rebootRUU" and got the same response. I don't know what else to do and I am deeply worried that I have bricked my DNA. I understand that I am completely responsible for attempting these things and for my errors, but I need help in getting back to any form of android so that I can reinstall Viper 1.3.0 with a stock boot.img (like I should have in the first place).
I appreciate all of your help and I hope someone knows what can be done here! Thank you guys!
Mcsquizzy said:
Hi there everyone!
My main problem is flashing hboot 1.15
I misinterpreted a sentence of instructions over at ViperDNA ROM thread, and attempted to flash Viper 1.3.0 with a custom kernel (it had been so long, I forget which. Cubed or DSB, idk) and after getting through aroma and successfully installing, it was stuck at a bootloop. Well I went back and read the instructions and comment again and apparently installing with anything other than Stock boot.img is a big no no. Anyways, I am stuck here without any type of ROM (relocking the bootloader to attempt to RUU.exe left my internal storage wiped) and unable to get the RUU.exe method to work (Error 155 most likely because I have hboot version 1.33.0001 and not 1.15). I cannot get the RUU.exe or the RUU.zip flash method to work. I have flashed a stock boot.img since then and have gone through different locked/relocked stages and tried ADB sideloading a stock ROM ("unable to mount /data /system" etc.). Right now, I am trying (using the HTC Droid DNA Toolkit program) to flash the 1.15 hboot, but it is stuck at "<waiting for device>". I have also tried "fastboot.exe fastboot oem rebootRUU" and got the same response. I don't know what else to do and I am deeply worried that I have bricked my DNA. I understand that I am completely responsible for attempting these things and for my errors, but I need help in getting back to any form of android so that I can reinstall Viper 1.3.0 with a stock boot.img (like I should have in the first place).
I appreciate all of your help and I hope someone knows what can be done here! Thank you guys!
Click to expand...
Click to collapse
I can tell you that it's not bricked just having a bit of bad luck.
First off try a different USB port, second there really isn't a need to RUU if all you are doing is trying to reflash a rom correctly.
you didnt happen to flash the boot.img to the hboot partiton? cause that would be bad. (DO NOT DO THIS)
try this: boot into recovery and plug the device into the computer then try adb devices and see if the device ID pops up if in fact it does do a:
adb push romzip.zip /sdcard/romzip.zip
or
adb push \path\to\romzip.zip /sdcard/romzip.zip
and it will push it to the /sdcard directory, then reboot the recovery and flash the rom and it should just work
.torrented said:
I can tell you that it's not bricked just having a bit of bad luck.
First off try a different USB port, second there really isn't a need to RUU if all you are doing is trying to reflash a rom correctly.
you didnt happen to flash the boot.img to the hboot partiton? cause that would be bad. (DO NOT DO THIS)
Click to expand...
Click to collapse
I have tried on another (Windows 7 64-bit laptop with correct drivers) computer and multiple USB ports. In the process of unlocking/relocking using an AllInOne Toolkit, it wiped everything from my internal storage (as it said it would). I can flash kernels and recoveries (using TWRP atm) but when I try to flash a ROM (installing using the TWRP recovery) I get messages saying "unable to mount /data" or "unable to mount /cache" and I am unable to check the boxes "Mount Data" and "Mount Cache" within the recovery (I can only check "Mount System" and thus I am unable to wipe/ factory reset/flash a ROM. I have no idea if I flashed a boot.img to the hboot partition, but I have only flashed a boot.img using the Droid DNA All in One Toolkit and also by using the "fastboot flash boot boot.img" command. How can I tell if I flashed it to the hboot partition? I am able to get into bootloader and reboot into RUU using the "oem rebootRUU" command, if that helps determine whether or not I messed up. I recieve a "Error [155]" message every time I use the RUU.exe on both computers, and I read on another post that this could be caused by the wrong hboot version (RUU.exe 'wants' a 1.15 hboot version, but my bootloader is saying I have the 1.33.0001 hboot version) on my DNA. Perhaps this is the cause? In any case, I have been working to flash the 1.15 hboot so that I can successfully flash the RUU.
Thank you for your help and patience!
Mcsquizzy said:
I have tried on another (Windows 7 64-bit laptop with correct drivers) computer and multiple USB ports. In the process of unlocking/relocking using an AllInOne Toolkit, it wiped everything from my internal storage (as it said it would). I can flash kernels and recoveries (using TWRP atm) but when I try to flash a ROM (installing using the TWRP recovery) I get messages saying "unable to mount /data" or "unable to mount /cache" and I am unable to check the boxes "Mount Data" and "Mount Cache" within the recovery (I can only check "Mount System" and thus I am unable to wipe/ factory reset/flash a ROM. I have no idea if I flashed a boot.img to the hboot partition, but I have only flashed a boot.img using the Droid DNA All in One Toolkit and also by using the "fastboot flash boot boot.img" command. How can I tell if I flashed it to the hboot partition? I am able to get into bootloader and reboot into RUU using the "oem rebootRUU" command, if that helps determine whether or not I messed up. I recieve a "Error [155]" message every time I use the RUU.exe on both computers, and I read on another post that this could be caused by the wrong hboot version (RUU.exe 'wants' a 1.15 hboot version, but my bootloader is saying I have the 1.33.0001 hboot version) on my DNA. Perhaps this is the cause? In any case, I have been working to flash the 1.15 hboot so that I can successfully flash the RUU.
Thank you for your help and patience!
Click to expand...
Click to collapse
Well... I just kept trying the RUU.exe over and over and over again and it finally worked I don't believe I did anything different, but I have tried so many different things I completely lost track Anyways, thank you for your help and patience, again
Mcsquizzy said:
Well... I just kept trying the RUU.exe over and over and over again and it finally worked I don't believe I did anything different, but I have tried so many different things I completely lost track Anyways, thank you for your help and patience, again
Click to expand...
Click to collapse
I flashed Viper 1.3.0 with BeastMode 5.9 and it's running fine no bootloops of any sort
I tried to install a KitKat Rom but ended up having my One boot up and reboot to recovery. Unfortunately I decided not to make a backup because I felt I had gone through the motions enough times to know what I was doing, and now I can only boot to the Rom that won't work. I found another rom that I used before sitting in my computer, but I can't seem to use adb to push it (unless I'm doing it wrong) into my phone's storage so I can use recovery to boot into it. Help!
TunedTimbre said:
I tried to install a KitKat Rom but ended up having my One boot up and reboot to recovery. Unfortunately I decided not to make a backup because I felt I had gone through the motions enough times to know what I was doing, and now I can only boot to the Rom that won't work. I found another rom that I used before sitting in my computer, but I can't seem to use adb to push it (unless I'm doing it wrong) into my phone's storage so I can use recovery to boot into it. Help!
Click to expand...
Click to collapse
First kitkat roms require s-off and the newest version of TWRP 2.6.3.3
so you can update your recovery and get s-off and reflash the kitkat or you can push the old rom you have to the phone.
http://rumrunner.us/ for s-off
recovery is here - http://techerrata.com/browse/twrp2/m7
ADB Push from Recovery
adb push rom.zip /data/media/0/
the file you push must be in the same directory as ADB