FINAL EDIT: My problem has been solved. I kept trying the RUU.exe method over and over until it finally worked (more info in my last reply).
EDIT: My only issue now is that I cannot select "Mount data" in the Mount menu within TWRP recovery. Also, even when I have "mount system" and "mount cache" selected, I get an "Unable to mount system" or "Unable to mount cache" when I try to factory reset, wipe cache, install a ROM, or sideload ADB a ROM
Hello everyone. After recently purchasing an HTC DNA, I used the "HTC Droid DNA AIO Kit" to unlock the bootloader (HTCDev + unlock code), root the phone, and load TWRP recovery. From the recovery menu, I flashed the Viper custom ROM. I noticed some wifi problems, so I wanted to go back to stock to see if the problem (couldn't connect to wifi) was still there. The dumbass that I am used the "Wipe System" ("This will wipe your ROM") option within the recovery hoping it would boot back into stock. Obviously that didn't work (and has started me down a horrible path to bricking). I tried re-flashing the viper ROM, and half way through the setup it would reboot and stick on a white "HTC" screen. Every time. I googled and tried the RUU.exe method and got 155 error "Wrong RUU version" or whatever. I tried flashing the RUU.zip stock ROM using the All-in-one kit. No luck (error in command prompt saying "too many links"). I don't know what to do I just need to get back to Stock ROM, or anything similar that can help fix my situation. I appreciate all of your technical expertise and any help you give! I can provide more information about my phone and setup and version and such. I realize many of you will cringe at my methods, and I apologize for all of my stupid errors.
Mcsquizzy said:
Hello everyone. After recently purchasing an HTC DNA, I used the "HTC Droid DNA AIO Kit" to unlock the bootloader (HTCDev + unlock code), root the phone, and load TWRP recovery. From the recovery menu, I flashed the Viper custom ROM. I noticed some wifi problems, so I wanted to go back to stock to see if the problem (couldn't connect to wifi) was still there. The dumbass that I am used the "Wipe System" ("This will wipe your ROM") option within the recovery hoping it would boot back into stock. Obviously that didn't work (and has started me down a horrible path to bricking). I tried re-flashing the viper ROM, and half way through the setup it would reboot and stick on a white "HTC" screen. Every time. I googled and tried the RUU.exe method and got 155 error "Wrong RUU version" or whatever. I tried flashing the RUU.zip stock ROM using the All-in-one kit. No luck (error in command prompt saying "too many links"). I don't know what to do I just need to get back to Stock ROM, or anything similar that can help fix my situation. I appreciate all of your technical expertise and any help you give! I can provide more information about my phone and setup and version and such. I realize many of you will cringe at my methods, and I apologize for all of my stupid errors.
Click to expand...
Click to collapse
did you do flash boot.img image file before the rom? if not, flashing that then reloading your desired rom might get you back.
if you can still get to recovery you can use the sideload option and try flashing a rom that doesn't use the aroma installer.. there are a couple stock roms in the development section.
I flashed a boot.img using flash gui from playstore. Ended up disabling my WiFi. I can only use LTE now . I'm on stock right now. Any ideas?
Sent from my HTC6435LVW using xda app-developers app
In order to run the RUU you must be locked. Relock and give it a try.
D
.
dj2muchxx said:
I flashed a boot.img using flash gui from playstore. Ended up disabling my WiFi. I can only use LTE now . I'm on stock right now. Any ideas?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
If the kernel you flashed also came with it's modules.zip then you have to also install the modules .zip file from recovery. If the kernel came with the rom then the modules are probably already installed with the rom.
To flash the kernal manually (which is more reliable) use the following command:
fastboot.exe flash boot boot.img
make sure the boot.img is located in the same folder as the fastboot.exe file.
If you're on Windows 7 you can hold the SHIFT key and right click while in the folder containing fastboot.exe and select "Open command prompt here" to make sure you are in the right folder in the command window. Not sure which other versions of Windows lets you use that shortcut.
DSB is also correct that you have to lock the bootloader if you want to use RUU.
I think the bootloader lock command is (must be at bootloader):
fastboot.exe oem lock
rootntootn said:
did you do flash boot.img image file before the rom? if not, flashing that then reloading your desired rom might get you back.
Click to expand...
Click to collapse
Thank you for the reply. I used the HTC Droid DNA All-in-one program to flash a stock boot.img file BEFORE flashing the ROM. No luck. I have since been able to adb push a stock ROM, but when I try to wipe the cache or install the ROM.zip file using the recovery (TWRP) I get a "Unable to mount /data". When I go into Mount settings within the recovery, I am unable to select "Mount data". I can only check "Mount system" and "Mount cache". Any ideas?
Also, I did relock the bootloader (It says "***Tampered*** ***Relocked***) using the same All-in-one tool. I have also tried flashing Clockwork recovery, but I get stuck on the "HTC This is only for development purposes legal blah" white screen, so I have reflashed TWRP. I ran both the RUU.exe (relocked bootloader), and tried flashing the RUU.zip method. Thoughts?
I will try doing all of my previous methods manually (through command prompt, without the All-in-one tool) when I get home (as you said, it is more reliable).
Thank you so much for the help you guys!
dj2muchxx said:
I flashed a boot.img using flash gui from playstore. Ended up disabling my WiFi. I can only use LTE now . I'm on stock right now. Any ideas?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
If you are flashing stock RUU -the bootloader has to be relocked for it to work....
In general each rom other than that usually has it's own boot image which has to be loaded first before the rom is. Usually downloadable from where the rom is. The one click varieties have not worked so well for me. so I agree with using the adb command version-more involved but reliable...
lazarus2297 said:
if you can still get to recovery you can use the sideload option and try flashing a rom that doesn't use the aroma installer.. there are a couple stock roms in the development section.
Click to expand...
Click to collapse
I tried the ADB sideload option within recovery, but I get a message saynig "Unable to mount '/data'". I also get this message after trying to install a ROM through recovery. When I try to select "Mount data" in the Mount menu of the TWRP recovery, I am unable to check the box. I can only check "Mount system" and "Mount cache". This is the only hangup right now. I have the bootloader unlocked, and I have flashed the boot.img (the stock version), but I cannot install or ADB sideload any ROMs because of the "Unable to mount '/data'" message Any ideas?
Why not just fasbtboot the boot.img then boot into recovery and adb push romname.zip and then flash the zip?
Sorry...read your post backwards.
Dude...just relock and ruu
Btw...anyone have a ruu in zip format?
Like a PH98IMG.zip as an example..that file name correlates with the rezound nut ya know what I mean??
Sent from my HTC6435LVW using xda premium
andrewp3481 said:
Why not just fasbtboot the boot.img then boot into recovery and adb push romname.zip and then flash the zip?
Sorry...read your post backwards.
Dude...just relock and ruu
Btw...anyone have a ruu in zip format?
Like a PH98IMG.zip as an example..that file name correlates with the rezound nut ya know what I mean??
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I have relocked the bootloader, then tried the RUU exe method (followed all steps) and I get a "Error 155" message. What can I do to fix that?
I have even flashed ClockworkMod recovery and tried to mount the /data, but I get the same "Unable to mount /data" message
Someone else might know this more than me.. but is it possible to format partitions from fastboot? Maybe you could format data from there then try some of your other steps..
Sent from my HTC6435LVW using xda app-developers app
lazarus2297 said:
Someone else might know this more than me.. but is it possible to format partitions from fastboot? Maybe you could format data from there then try some of your other steps..
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah, it definitely sounds like I need to do some reorganizing/reformatting/file therapy. The only question I have is HOW :/
I appreciate your replies and your help Hopefully I can get this figured out. Is there some chat/irc channel or some other way to reach out for help? I want to exhaust all options.
Mcsquizzy said:
I tried the ADB sideload option within recovery, but I get a message saynig "Unable to mount '/data'". I also get this message after trying to install a ROM through recovery. When I try to select "Mount data" in the Mount menu of the TWRP recovery, I am unable to check the box. I can only check "Mount system" and "Mount cache". This is the only hangup right now. I have the bootloader unlocked, and I have flashed the boot.img (the stock version), but I cannot install or ADB sideload any ROMs because of the "Unable to mount '/data'" message Any ideas?
Click to expand...
Click to collapse
I think maybe it might be worth going back to re read how to return to stock posts carefully-link below. You should first have the phone locked again, the RUU is executable from your pc. You won't be using a recovery program and therefore shouldn't be doing any part from their menu to get it done. Everything your phone needs should get loaded up if correctly done.
http://forum.xda-developers.com/showthread.php?t=2011243
andrewp3481 said:
Btw...anyone have a ruu in zip format?
Like a PH98IMG.zip as an example..that file name correlates with the rezound nut ya know what I mean??
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
All you have to do is extract the RUU contents and put them in a folder called whatever.zip(THIS IS NOT THE NAME OF THE FOLDER) and bam you got a .zip
Sent from my HTC6435LVW using XDA Premium HD app
rootntootn said:
I think maybe it might be worth going back to re read how to return to stock posts carefully-link below. You should first have the phone locked again, the RUU is executable from your pc. You won't be using a recovery program and therefore shouldn't be doing any part from their menu to get it done. Everything your phone needs should get loaded up if correctly done.
http://forum.xda-developers.com/showthread.php?t=2011243
Click to expand...
Click to collapse
I HAVE relocked my phone, AND used the RUU.exe method. I get an "Error [155]" message.
I wonder if this has to do with anything, though. I have the HTC drivers installed, my phone is unlocked and in the fastboot usb bootloader screen. I am using the HTC Droid DNA All-in-one kit to relock the phone. When I do so, I get this message:
Code:
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
FAILED (status read failed (Too many links))
finished. total time: 1.267s
D:\Android\adt-bundle-windows-x86_64\sdk\Droid_DNA_All-In-One_Kit_v2.1\Droid_DNA_All-In-One_Kit_v2.1\data>
Then my phone reboots and says:
Code:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
If I were to reboot into bootloader again, the "Security Warning" goes away. Could that have anything to do with it?
Otherwise, even after relocking and following all steps, when I try the RUU.exe method, I get to "Verifying information on android phone" -> "Update image version" -> "Checking" -> Waiting for bootloader" -> "Sending" -> "Updating Signature" -> "Error [155]"
Could it be a CID thing? If my phone is the wrong CID might the RUU.exe not work? Maybe if I change the CID to a generic one?
SUCCESS!!! I kept trying the RUU.exe method over and over and over. Finally I redownloaded the same exact file. I entered Windows Task Manager and closed any program I suspected of interfering (Command prompts, driver software, All-in-one tool, etc.). I unplugged my phone from USB, booted into bootloader (fastboot), then connected the USB cable again. I ran the RUU.exe as an Administrator. The "Previous Version" or whatever was empty, with "New Version" as the 1.15.605.4 version. It went through all of the usual steps (Bootloader -> Wiping -> Sending -> Signature stuff) then (where it would usually give me the "Error [155]", it kept going. I was actually researching warranty Acts and packaging my cables and etc. back into the box to go plead a BS "Phone died during update" case to Verizon So excited right now. Thank you guys so much for all of your help, and I hope this thread can help other users in a situation similar to mine. As long as you can get into bootloader and recovery YOUR PHONE IS OKAY. Just keep at it
Glad to hear it!!
Sent from my HTC6435LVW using xda app-developers app
Related
UPDATE EASIEST WAY TO UNROOT PLACE THE PB00IMG-21-official.zip FILE ON YOUR SD CARD RENAME IT TO PB00IMG.zip AND FLASH!!!! REMOVES THE CUSTOM RECOVERY IMAGE AND THERES NO HASSEL. SERIOUSLY
DOWNLOAD FILE FROM
http://android.grdlock.net//index.php?&direction=0&order=&directory=PB00IMG Roms
How can I do this (^) Also how can I manually update to the newest OTA from 1.5
Search is there for a reason.
http://forum.xda-developers.com/showthread.php?t=652419
There's the link to downgrade and remove Amon Ra.
Thank you
Sent from my Eris using XDA App
Ok but how can I update to 2.1 now
Sent from my Eris using XDA App
iloveandroid said:
Ok but how can I update to 2.1 now
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Not to be a jerk, but how do you have 243 posts and not understand the "search" function? There are like 5011 threads about this EXACT subject already. You can either download the 2.1 update file from HTC, or, if you have truly sent your phone back to completely stock, the OTA should show up in a while. You can also "Check for Updates" from the settings menu. That worked for me the last time I took one back to stock.
Settings > About Phone > Check for Updates. That should give you the 2.1 OTA if my understanding is correct that you are on 1.5 stock.
OK update:
OK everything works right up until I try to flash the command
fastboot flash recovery recovery.img
I am on a mac and this is how I am trying to execute this command
Open terminal, type /Users/(my name)/android-sdk/tools, enter
then I try the command fastboot flash recovery recovery.img and I get
-bash: fastboot: command not found
HELP??
Why can't I remove my custom recovery
OK everything works right up until I try to flash the command
fastboot flash recovery recovery.img
I am on a mac and this is how I am trying to execute this command
Open terminal, type /Users/(my name)/android-sdk/tools, enter
then I try the command fastboot flash recovery recovery.img and I get
-bash: fastboot: command not found
HELP??
Boot into fastboot by holding down the red and green buttons first and then do that command. Or not. I don't know.
Check the tools folder to make sure it has fastboot. I know the windows sdk has it but it may be a seperate dl for Mac
Sent from my FroyoEris using XDA App
It IS Lupus said:
Check the tools folder to make sure it has fastboot. I know the windows sdk has it but it may be a seperate dl for Mac
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Oh it doesn't do you know where I can download it
Nevermind, but now i get the error
error: cannot load 'recovery.img'
Why is UNROOTING so hard?
Ok so as I am trying to flash the stock recovery image I keep having so many errors this is my latest one any help or feedback is welcomed
error: cannot load 'recovery.img'
http://forum.xda-developers.com/showthread.php?t=652419
iloveandroid said:
Ok so as I am trying to flash the stock recovery image I keep having so many errors this is my latest one any help or feedback is welcomed
error: cannot load 'recovery.img'
Click to expand...
Click to collapse
if your fastbooting stock recovery on your phone put it in the tools folder of adb
and then fastboot, it will send it to the phone and then flash, hope this helps.
What am I supposed be looking at I used these instructions and I got the error following them
jamezelle said:
if your fastbooting stock recovery on your phone put it in the tools folder of adb
and then fastboot, it will send it to the phone and then flash, hope this helps.
Click to expand...
Click to collapse
I did that's why I'm confused
Read this post and see if this will help, I believe I used this RUU with driver to unroot my phone.
If I remember correctly it also gives you the s-on bootloader
http://androidforums.com/htc-droid-eris/92096-verizons-ruu-official-2-1-droid-eris.html
jonathanphx1 said:
Read this post and see if this will help, I believe I used this RUU with driver to unroot my phone.
If I remember correctly it also gives you the s-on bootloader
http://androidforums.com/htc-droid-eris/92096-verizons-ruu-official-2-1-droid-eris.html
Click to expand...
Click to collapse
Oh ya I forgot to mention I am on a MAC
Just find the leaked 2.1 file put it on your sd card and flash it using fastboot I did it yesterday works like a charm
Sent from my Eris using XDA App
I was on S-off leaked RUU ICS running fine, I downloaded the latest speed rom and it gave me this error while trying to flash
Formatting partitions
(system is unmounted already)
E: Error in /sdcard/Speed Rom ICS 3.1.0.zip
(Status 1)
Installation aborted.
I downloaded it again and got the same error.
When i tried a third time i was no longer able to get into CWM.
I tried flashing CWM again using the all in one tool which pushed it fine but it still does not load CWM, I tried pushing 4ext and TWRP with the same results. 4ext was able to get to a screen where it said 4ext is loading 3..2..1.. but then back to the white HTC screen
is there a way i can push the RUU leak file via ADB so i can flash that again using the built in recovery?
Thanks,
kewlmonk2121 said:
I was on S-off leaked RUU ICS running fine, I downloaded the latest speed rom and it gave me this error while trying to flash
Formatting partitions
(system is unmounted already)
E: Error in /sdcard/Speed Rom ICS 3.1.0.zip
(Status 1)
Installation aborted.
I downloaded it again and got the same error.
When i tried a third time i was no longer able to get into CWM.
I tried flashing CWM again using the all in one tool which pushed it fine but it still does not load CWM, I tried pushing 4ext and TWRP with the same results. 4ext was able to get to a screen where it said 4ext is loading 3..2..1.. but then back to the white HTC screen
is there a way i can push the RUU leak file via ADB so i can flash that again using the built in recovery?
Thanks,
Click to expand...
Click to collapse
Download the ICS leak again, rename it to PH85IMG.zip, put it on your microSD card, boot into bootloader (vol down + power), let it do its thing
Also, may I recommend the 4ext recovery?
kered424 said:
Download the ICS leak again, rename it to PH85IMG.zip, put it on your microSD card, boot into bootloader (vol down + power), let it do its thing
Also, may I recommend the 4ext recovery?
Click to expand...
Click to collapse
Is there a way i can push it through adb?
i tried >adb push PH85IMG.zip /sdcard
but it gave me "failed to copy 'PH85IMG.zip' to '/sdcard': Is a directory"
I don't have a anything i can put my microSD in except my phone till tomorrow
kewlmonk2121 said:
Is there a way i can push it through adb?
i tried >adb push PH85IMG.zip /sdcard
but it gave me "failed to copy 'PH85IMG.zip' to '/sdcard': Is a directory"
I don't have a anything i can put my microSD in except my phone till tomorrow
Click to expand...
Click to collapse
I have no idea. Sorry.
The command should be...(put the PH85IMG.zip in your tools folder first)
Code:
adb push PH85IMG.zip /sdcard2/PH85IMG.zip
If sdcard2 doesn't work try sdext or sd_ext
Don't quote me on this...
Double0EK said:
The command should be...(put the PH85IMG.zip in your tools folder first)
Code:
adb push PH85IMG.zip /sdcard2/PH85IMG.zip
If sdcard2 doesn't work try sdext or sd_ext
Don't quote me on this...
Click to expand...
Click to collapse
I tried that way too later on. It gave me permission denied. I think because my rom was gone debugging was no longer enabled and write permissions to the SD card were gone. I was able to get back up and running by using a card reader.
Thanks everyone
kewlmonk2121 said:
I was on S-off leaked RUU ICS running fine, I downloaded the latest speed rom and it gave me this error while trying to flash
Formatting partitions
(system is unmounted already)
E: Error in /sdcard/Speed Rom ICS 3.1.0.zip
(Status 1)
Installation aborted.
I downloaded it again and got the same error.
When i tried a third time i was no longer able to get into CWM.
I tried flashing CWM again using the all in one tool which pushed it fine but it still does not load CWM, I tried pushing 4ext and TWRP with the same results. 4ext was able to get to a screen where it said 4ext is loading 3..2..1.. but then back to the white HTC screen
is there a way i can push the RUU leak file via ADB so i can flash that again using the built in recovery?
Thanks,
Click to expand...
Click to collapse
I wish I read this earlier...exact same thing happened to me! I'm s-on however , but just unlocked my boot loader to flash this rom.
Now I have to re-lock bootloader and load the stock rom again...so much work for literally no benefit. Disappointed!
amad99 said:
I wish I read this earlier...exact same thing happened to me! I'm s-on however , but just unlocked my boot loader to flash this rom.
Now I have to re-lock bootloader and load the stock rom again...so much work for literally no benefit. Disappointed!
Click to expand...
Click to collapse
Nobody made you flash it you know...just saying
Sent from my HTC_Amaze_4G using XDA
Spastic909 said:
Nobody made you flash it you know...just saying
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
Thanks for stating the obvious
I was on 4.0.3 and I flashed the zip through AromRa recovery.
Now, when booting up, its stuck at the 4G screen.
The update was the OTA update released to update radios to Global. THIS
It didn't gave any error at all, it said "Reboot to complete installation or update". But when I clicked the reboot option, I saw a line saying something like "Can't write....." then the screen went off and it rebooted. This line was not there, or atleast not visible before I clicked the reboot option.
I am new to rezound and android, so please let me know what I can do. I wasn't able to get a nandroid backup before doing this, had no ext. SD card.
All I did before flashing the zip was flashing the custom recovery. Nothing else. No SU or anything else.
Can I RUU 4.0.3 to fix this problem?
Yes you need to ruu to get it back. I'm assuming your s on. You need to be s off in order to flash radios by themselves.
Sent from my ADR6425LVW using xda app-developers app
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
lamborg said:
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
Click to expand...
Click to collapse
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
feralicious said:
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
Click to expand...
Click to collapse
I relocked but then tried flashing the zip twice.
Here's what comes in cmd:
sending....
OKAY
writing
<bootloader>adopting sig ....
<bootloader>checking sig
failed <remote: not allowed>
finished
After rebooting, it gets stuck on the white HTC screen.
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
mike7728 said:
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
Click to expand...
Click to collapse
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You have to fastboot oem rebootRUU first
then fastboot flash zip PH98IMG.zip
you may have to flash the zip twice.
Code:
androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
(I can't link yet)
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You don't flash this in fastboot since it's a zip file.
EDIT: Looks like you can flash in fastboot as mentioned in the above post. Cool, I like that. I would flash it twice as I've read several times that you need to to make sure it gets all the system files.
If htat doesn't work for whatever reason, just put it on the sd card of your phone, detach your phone from your pc and reboot. hboot should find it (it looks for the PH98IMG.zip file) and flash it. Flash it twice to be sure it gets all the system files.
When it's done and you're rebooted use a file explorer and delete the PH98IMG file so it doesn't flash again on the next reboot.
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
So I tried to flash a rom and hit some problems, now when I try to restart my phone it gets stuck on the "verizon 4g lte" screen and wont load past there. When I open bootloader there are 3 warnings at the very top:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
How can I get my phone back to stock? I need this IMMEDIATLY if possible!!
Also make it as simple as possible, I'm new to roms and roots and flashing.
BabyPenguin said:
So I tried to flash a rom and hit some problems, now when I try to restart my phone it gets stuck on the "verizon 4g lte" screen and wont load past there. When I open bootloader there are 3 warnings at the very top:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
How can I get my phone back to stock? I need this IMMEDIATLY if possible!!
Also make it as simple as possible, I'm new to roms and roots and flashing.
Click to expand...
Click to collapse
You need to unlock the boot loader again. Flash a recovery img again.
Sent from my Rezound using xda app-developers app
tburns said:
You need to unlock the boot loader again. Flash a recovery img again.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
What is a recovery img?
BabyPenguin said:
What is a recovery img?
Click to expand...
Click to collapse
as it was stated, you need to unlock your bootloader again. A recovery image is a image that we use to flash and wipe roms and the phone. Amon RA, TWRP and CW are the ones we can use for our phone. I personally use TWRP and Amon RA depending on my mood. You can find them here
http://forum.xda-developers.com/showthread.php?t=1425091
Towards the bottom of the list you will see recovery. You will need to flash one of those in order to flash a custom rom.
Also make sure to read the tutorials towards the bottom. before you start messing with your phone you should be familiar with everything. If you do something wrong and brick your phone, its hard to recover from if at all and you would have an expensive paper weight
clmowers said:
as it was stated, you need to unlock your bootloader again. A recovery image is a image that we use to flash and wipe roms and the phone. Amon RA, TWRP and CW are the ones we can use for our phone. I personally use TWRP and Amon RA depending on my mood. You can find them here
http://forum.xda-developers.com/showthread.php?t=1425091
Towards the bottom of the list you will see recovery. You will need to flash one of those in order to flash a custom rom.
Also make sure to read the tutorials towards the bottom. before you start messing with your phone you should be familiar with everything. If you do something wrong and brick your phone, its hard to recover from if at all and you would have an expensive paper weight
Click to expand...
Click to collapse
Alright, so I downloaded both the files here: http://forum.xda-developers.com/showthread.php?t=1339679
Two problems. First, I have no way of accessing my sd card now because it wont let me through my computer
Second, I don't know how to use these files and after reading the thread it still didn't help.
EDIT: After unlocking the only two notices on my hboot is
TAMPERED
and
UNLOCKED
EDIT2: I found my SD card adapter.
BabyPenguin said:
Alright, so I downloaded both the files here: http://forum.xda-developers.com/showthread.php?t=1339679
Two problems. First, I have no way of accessing my sd card now because it wont let me through my computer
Second, I don't know how to use these files and after reading the thread it still didn't help.
EDIT: After unlocking the only two notices on my hboot is
TAMPERED
and
UNLOCKED
EDIT2: I found my SD card adapter.
Click to expand...
Click to collapse
1. you need to download fastboot if you have not already. You can find that in the android sdk
2.) once fastboot is downloaded boot your phone into bootloader and select the fastboot option and plug your phone into your computer
3.) place the recovery image in the same directory as fastboot and use the command prompt (windows key +r then type cmd and hit enter)
4.) change directory to where fastboot is and run this command
fastboot flash recovery recovery.img
where recovery.img is the name of the recovery file that you downloaded
clmowers said:
1. you need to download fastboot if you have not already. You can find that in the android sdk
2.) once fastboot is downloaded boot your phone into bootloader and select the fastboot option and plug your phone into your computer
3.) place the recovery image in the same directory as fastboot and use the command prompt (windows key +r then type cmd and hit enter)
4.) change directory to where fastboot is and run this command
fastboot flash recovery recovery.img
where recovery.img is the name of the recovery file that you downloaded
Click to expand...
Click to collapse
Done, now what? Thanks for the help by the way!
BabyPenguin said:
Done, now what? Thanks for the help by the way!
Click to expand...
Click to collapse
yeah no problem.
If you go back into the bootloader and select recovery, this will bring you into the Amon Ra.
Download a rom from the forums, I personally like Neo's Roms, Infection 2.8.1 is a good choice. But download any rom and put it on your SD card.
1.) select USB-MS toggle and then select on of the options
2.) copy downloaded rom to mounted sdcard
3.) once copied, hit the power button to unmount and then return to the main menu
4.)select wipe from the main menu and then do each one of these 3 times
Wipe All data/factory reset
Wipe /data
Wipe /cache
Wipe /Dalvik-cache
Wipe /system
then go back to main menu and then select Fash zip menu and select where you placed your rom and then flash...once its flash go back to main menu and select Developers menu and selet reboot bootloader
open the rom using a zip program and pull the boot.img from the rom and place it in your fastboot directory
once you are in the bootloader it should go to fastboot usb automatically and then run these commands
fastboot flash boot boot.img
fastboot reboot
it should reboot and load your rom
clmowers said:
yeah no problem.
If you go back into the bootloader and select recovery, this will bring you into the Amon Ra.
Download a rom from the forums, I personally like Neo's Roms, Infection 2.8.1 is a good choice. But download any rom and put it on your SD card.
1.) select USB-MS toggle and then select on of the options
2.) copy downloaded rom to mounted sdcard
3.) once copied, hit the power button to unmount and then return to the main menu
4.)select wipe from the main menu and then do each one of these 3 times
Wipe All data/factory reset
Wipe /data
Wipe /cache
Wipe /Dalvik-cache
Wipe /system
then go back to main menu and then select Fash zip menu and select where you placed your rom and then flash...once its flash go back to main menu and select Developers menu and selet reboot bootloader
open the rom using a zip program and pull the boot.img from the rom and place it in your fastboot directory
once you are in the bootloader it should go to fastboot usb automatically and then run these commands
fastboot flash boot boot.img
fastboot reboot
it should reboot and load your rom
Click to expand...
Click to collapse
I have no idea why this isn't working
http://gyazo.com/2627f9963c95e7dc9a03cb118f139aac.png
I did your steps in order, but my phone has been stuck on rebooting... for over 15 minutes as you can see from the CMD. On my phone I just see the booting logo spinning.
I used this rom because I want jellybean: http://forum.xda-developers.com/showthread.php?t=2113140
Any ideas?
Also, what do I do with the MD5? I didn't use it.
BabyPenguin said:
I have no idea why this isn't working
http://gyazo.com/2627f9963c95e7dc9a03cb118f139aac.png
I did your steps in order, but my phone has been stuck on rebooting... for over 15 minutes as you can see from the CMD. On my phone I just see the booting logo spinning.
I used this rom because I want jellybean: http://forum.xda-developers.com/showthread.php?t=2113140
Any ideas?
Click to expand...
Click to collapse
the reboot step isnt 100% needed, its more for ease of use...just pull the battery and power on
Also did you flash the boot.img file?
---------- Post added at 07:22 AM ---------- Previous post was at 07:18 AM ----------
BabyPenguin said:
I have no idea why this isn't working
http://gyazo.com/2627f9963c95e7dc9a03cb118f139aac.png
I did your steps in order, but my phone has been stuck on rebooting... for over 15 minutes as you can see from the CMD. On my phone I just see the booting logo spinning.
I used this rom because I want jellybean: http://forum.xda-developers.com/showthread.php?t=2113140
Any ideas?
Also, what do I do with the MD5? I didn't use it.
Click to expand...
Click to collapse
Dont worry to much about the MD5,I havent used one if forever. Its basically just a security check to make sure that the file you downloaded didnt get corrupt. But with modern technology and internet, its less likely to mess up while downloading. Still possible, but not likely
clmowers said:
the reboot step isnt 100% needed, its more for ease of use...just pull the battery and power on
Also did you flash the boot.img file?
Click to expand...
Click to collapse
It's still just sitting on the boot screen.
If you didn't see my edit, there is an md5 file I can download, but I didn't use it because I don't know what to do with it.
BabyPenguin said:
It's still just sitting on the boot screen.
If you didn't see my edit, there is an md5 file I can download, but I didn't use it because I don't know what to do with it.
Click to expand...
Click to collapse
Just sent you a PM buds
maybe you can help me out quick im stuck on the lte logo also my bootloader is unlocked but when i open it to try and fix my problem its says i need an update. so i select update, it finishes, and makes me reboot which gets me stuck again.
i cant pick anything in the bootloader menu until i select yes or no for this update but both options require me to reboot after choosing then im back to stuck.
xcapeartist said:
maybe you can help me out quick im stuck on the lte logo also my bootloader is unlocked but when i open it to try and fix my problem its says i need an update. so i select update, it finishes, and makes me reboot which gets me stuck again.
i cant pick anything in the bootloader menu until i select yes or no for this update but both options require me to reboot after choosing then im back to stuck.
Click to expand...
Click to collapse
It sounds like you have a ph98img file on your sdcard. Remove the sdcard and Mount it in a PC and remove it. Then remount in the phone. Should allow to get into recovery and fastboot then
Sent from my ANDROFLY REZOUND using xda app-developers app
clmowers said:
It sounds like you have a ph98img file on your sdcard. Remove the sdcard and Mount it in a PC and remove it. Then remount in the phone. Should allow to get into recovery and fastboot then
Sent from my ANDROFLY REZOUND using xda app-developers app
Click to expand...
Click to collapse
thanks for the help, before i got your message i got around the issue in a different way just trying a few things. I figured out the phone would boot into recovery with no sd card in it but i couldnt flash the rom again without it installed so i put the sd in partially and then held the battery against the contacts with out inserting it completely then booted into recovery, push the sd in the rest of the way and i was golden for there.
but i happy that someone knew wat it was on the sd card that was giving me the problem ive got that deleted now thanks for the help
xcapeartist said:
thanks for the help, before i got your message i got around the issue in a different way just trying a few things. I figured out the phone would boot into recovery with no sd card in it but i couldnt flash the rom again without it installed so i put the sd in partially and then held the battery against the contacts with out inserting it completely then booted into recovery, push the sd in the rest of the way and i was golden for there.
but i happy that someone knew wat it was on the sd card that was giving me the problem ive got that deleted now thanks for the help
Click to expand...
Click to collapse
That works too, probably not the best thing for the phone, but it works, glad i could point you in the right direction