ok so I am s-off, my hboot says 2.21.0000 and I am running the latest stock ICS leak.
I am doing my darndest to flash RA and get some root going.
When I flash anything via ADB, I am getting
C:\android\platform-tools>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\android\platform-tools>fastboot flash recovery ra315.img
sending 'recovery' (7078 KB)...
OKAY [ 1.445s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.765s
I have tried renaming the recovery just "recovery.img", it is in the same folder as ADB.
I have even tried flashing the modified hboot again and got the same error message.
What is with the remote not allowed? I do have usb debugging on (I tried on and off)
So fine I figure I am smarter than all that. I figured I would flash it via the PH file, not, acts like it will, but will not.
THen I figured that I would do it via flashing the rooted stock ROM that scott has out....nope again it acts like it will but just will not do anything.
Anyone have any ideas? I did everything before without issue (just got this phone as a replacement)...
Try this....download, rename PH98IMG.zip place on sd card and flash in downloader.
http://db.tt/UuiVjcrb
This is the version of amon ra 3.15 I was able to get to flash while having the same issue.
Sent from my ADR6425LVW using Tapatalk 2
Adb commands may not work due to bootloader being locked. Do not HTC unlock. If you do your bootloader will always say relocated or unlocked. Basically this is why some people flashed eng hboots or had the jouponut bear hboot.
Most people can get by with flashing stuff as ph98img and not worry about messing stuff up and stay on the stock bootloader.
You may want to check the dev section for more info on hboots if you need to use Adb commands and want a modified hboot.
If you unlock after s off, and decide to return to stock its a lengthy process. Scotty has a thread on how to do it. Basically you need to s on, redo s off and then go s on again. After the steps the bootloader will be like Verizon shipped the phone.
When s off first came out, we thought running a ruu would return the bootloader to locked if you unlocked....sadly it didn't. I myself had to redo the process, since I unlocked after s off. Such is life for early adopters.....
Sent from my ADR6425LVW using Tapatalk 2
Thanks a ton for the help. I did flash your AR file, and that seemed to do the trick. I do not know what the difference was between that one and the other 50 I downloaded.
I wasnt really satisfied there though. I ended up nuking the whole thing and going back to GB, flashing RA, then ICS, then the modified Hboot. The whole process went as flawlessly this time as the first time...
Thanks again
piizzadude said:
Thanks a ton for the help. I did flash your AR file, and that seemed to do the trick. I do not know what the difference was between that one and the other 50 I downloaded.
I wasnt really satisfied there though. I ended up nuking the whole thing and going back to GB, flashing RA, then ICS, then the modified Hboot. The whole process went as flawlessly this time as the first time...
Thanks again
Click to expand...
Click to collapse
Glad to hear you got it working.
Sent from my ADR6425LVW using Tapatalk 2
Related
Ok like many I upgraded my phone and used HTC's S-Off Tool. That means no AOSP for me
The purpose of this thread is to discuss methods of downgrading the hboot to one that allows kernel flashing, as well as keep up to date regarding development in this area.
I attempted to flash the Eng Hboot through bootloader and no dice. I also tried
Code:
C:\Android>fastboot flash hboot hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.363s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.365s
I also tried RUU and it didn't work either
Now its up to you real devs to try and figure this out
EDIT:Thanks to JTNiggle we have a workaround for kernel flash
Edit:
Alright, it works. You can flash an older ROM, in my case Ava's V1, and then got to fastboot and flash the kernel for that rom. It will take, and so far everything works. Wifi, 4g, 3g, voice, bluetooth, all good.
This is pretty sweet news to me, seems like there wont be as many limitations with this as we thought.
So to do this for yourself, first, download your rom of choice.
Then use 7zip or another utility to open the archive and copy out the boot.img, put that boot.img on the root of your sdcard before you flash ur rom.
Boot into recovery and wipe as necessary, then flash ur rom. When finished, while still in recovery, go back to main menu and pick advanced menu, then reboot menu, then pick bootloader.
Once it boots to fastboot usb, you can do this from a command prompt from ur sdk tools folder,
Code:
fastboot flash boot boot.img
it will give you an output sbout being okay, and once finished, you can do,
Code:
fastboot reboot
And ur good to go, you should boot into your rom just as you would expect, happy as a clam. Hopefully this is something that will be able to be fixed along the way so that you don't have to do these steps. Heck, there may be an easier way now, but I'm no dev, so I'll leave it to someone who is.
For now, i've got an htc unlocked phone here running Ava's v1 with a 2.6.35.10 kernel and it's buttery smooth.
Click to expand...
Click to collapse
Reserved.....
reserved as well....
and just in case also reserved.....
Just so you know you can flash kernels with hboot 1.5.
Just saying...
Here is the link on how to: http://forum.xda-developers.com/showpost.php?p=17107369&postcount=32
I used alpharev and theres no AOSP for me either!
Really..?
Sent from my PG86100 using XDA App
Yea, u can flash everything but radios
Sent from my PG86100 using Tapatalk
Thats fine and all but I think its kinda ridiculous that HTC's s-off isn't really fully unlocked... The one time I decide to go the official methods I get screwed
Won't be making that mistake again..
This method also works and the flashes take:
Have your recovery image (I have cwm in the same directory as fastboot.exe to make things easier).
Boot into bootloader, choose fasboot, connect the phone via usb (turns into fastboot usb)
Command prompt, "fastboot boot whatever your recovery image name is.img" (obviously exclude the "")
So for me I.E. it will be "fastboot boot cwm-4.0.1.4.img"
The phone will boot into recovery, now, since you called recovery from fastboot, it will flash any rom or kernel like in the OP's method (i have tried it and sticks, it appears the sole fact of launching or using fastboot removes any lock HTC has left there). The advantage is, if you have a ROM that includes a modified kernel already (like overclocking and such), you don't have to extract the kernel and flash it separately.
Thanks Brandas!.
You can flash kernels via fastboot with hboot 1.5. I can confirm this I did it a few times on ny old 3d
sent from a double barreled shooter
i have discussed how to flash kernels on hboot 1.50 on here a few weeks ago...
it can be done - did it the other day as a matter of fact
fastboot flash boot boot.img
we had to do this on synergy, cause the installer script could not flash the ramdisk from the rom. after fastbooting the ramdisk..all the issues went away.
so you with hboot 1.5 we just dont have root yet?
armonwilson888 said:
so you with hboot 1.5 we just dont have root yet?
Click to expand...
Click to collapse
if you have 1.5 - what i walked someone thru on synergy's chat - (that someone else copied/pasted it on here and took credit for, spelling errors and all) is this:
they unlocked via HTCDEV.COM from a 1.40 bootloader - she did this under the advise of another forum (not xda). this process involved to updating to the latest RUU/firmware/hboot/radio package, then using htcdev.com to unlock the bootloader. after she did this, she was stuck.
we fastbooted clockwork recovery's IMG file to her phone, and flashed synergy
we noticed it wasnt working correcly, so i had her superwipe, and format w/ the ext4 optimization tool - it still wasnt working correctly.
*after the 1st flash of synergy, clockwork recovery broke and refused to work, even after being re-flashed via fastboot. we have since flashed TeamWin's recovery from a IMG file using fastboot, and have had no issues w/ the recovery tool.
after i looked in to it, i found the stock HTC kernel and ramdisk was still installed.
we fastbooted the ramdisk - and now she is 100% up and running.
i personally would wait for 1.50 to be cracked to get full S-OFF, but if u cant wait, you can still unlock, flash roms, root, and fastboot the ramdisk.
chad.goodman said:
if you have 1.5 - what i walked someone thru on synergy's chat - (that someone else copied/pasted it on here and took credit for, spelling errors and all) is this:
they unlocked via HTCDEV.COM from a 1.40 bootloader - she did this under the advise of another forum (not xda). this process involved to updating to the latest RUU/firmware/hboot/radio package, then using htcdev.com to unlock the bootloader. after she did this, she was stuck.
we fastbooted clockwork recovery's IMG file to her phone, and flashed synergy
we noticed it wasnt working correcly, so i had her superwipe, and format w/ the ext4 optimization tool - it still wasnt working correctly.
*after the 1st flash of synergy, clockwork recovery broke and refused to work, even after being re-flashed via fastboot. we have since flashed TeamWin's recovery from a IMG file using fastboot, and have had no issues w/ the recovery tool.
after i looked in to it, i found the stock HTC kernel and ramdisk was still installed.
we fastbooted the ramdisk - and now she is 100% up and running.
i personally would wait for 1.50 to be cracked to get full S-OFF, but if u cant wait, you can still unlock, flash roms, root, and fastboot the ramdisk.
Click to expand...
Click to collapse
Who is the op? Ill update the post with this information and give him/her credit.
chad.goodman said:
if you have 1.5 - what i walked someone thru on synergy's chat - (that someone else copied/pasted it on here and took credit for, spelling errors and all) is this:
they unlocked via HTCDEV.COM from a 1.40 bootloader - she did this under the advise of another forum (not xda). this process involved to updating to the latest RUU/firmware/hboot/radio package, then using htcdev.com to unlock the bootloader. after she did this, she was stuck.
we fastbooted clockwork recovery's IMG file to her phone, and flashed synergy
we noticed it wasnt working correcly, so i had her superwipe, and format w/ the ext4 optimization tool - it still wasnt working correctly.
*after the 1st flash of synergy, clockwork recovery broke and refused to work, even after being re-flashed via fastboot. we have since flashed TeamWin's recovery from a IMG file using fastboot, and have had no issues w/ the recovery tool.
after i looked in to it, i found the stock HTC kernel and ramdisk was still installed.
we fastbooted the ramdisk - and now she is 100% up and running.
i personally would wait for 1.50 to be cracked to get full S-OFF, but if u cant wait, you can still unlock, flash roms, root, and fastboot the ramdisk.
Click to expand...
Click to collapse
Thanks, I just switched to the 3vo from the atrix and ota'ed at first boot. should have researched first. I guess I will just have to wait...
You might see if you can get some help from the devs that hang out in #Thunderbolt on the andirc.com chat to help with downgrading hboot. We had to do it for the original Thunderbolt s-off method. It involved flashing the misc partition with an "unsecure boot image" I believe is what they called it. I don't really know how it works or if the same could be done with the Evo3D but it might be worth a shot.
Sent from my HTC Thunderbolt
JBO1018 said:
You might see if you can get some help from the devs that hang out in #Thunderbolt on the andirc.com chat to help with downgrading hboot. We had to do it for the original Thunderbolt s-off method. It involved flashing the misc partition with an "unsecure boot image" I believe is what they called it. I don't really know how it works or if the same could be done with the Evo3D but it might be worth a shot.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
I tried with the misc partition hack but it still doesnt work. IEF from revolutionary also tried on my friend's phone with the misc partition. Even after you flashed the edited one, hboot still reads the new version(IEF thought maybe the misc partition was being rewritten somehow at boot). We really tried everything everything he could think of. We couldnt get the hboot to downgrade no matter what trick we used
OK I understand that a kernel can be flashed after using HTC unlock method on HBOOT 1.50. That is good news. Even though I don't have the latest HBOOT and I used the REvolutionary tool to s-off my phone, I am very interested in the development of being able to downgrade the latest HBOOT. The reason? Well, if something were to happen and I have to get a replacement phone and it came with the latest update out of the box. Or, if I have to take it to a Sprint repair center and I have to unroot and go back to stock and they update to the latest firmware. I would use HTC's method to unlock, but would prefer to downgrade and use Revolutionary. I understand that they are working on supporting the latest HBOOT in Revolutionary, but from what I understand the updates patches the fr3vo exploit and other holes. I hope that just because kernels can be flashed that no one works on finding a way to downgrade the HBOOT after using HTC's unlock method.
In advance menu, there is no REBOOT MENU to boot to bootloader. is this for CWM Recovery ?
Full disclaimer - I am pretty much a noob at rooting devices. I got my first android phone which was a Rezound in december and I only just rooted it in May using the All in 1 tool. I read up on all the steps for unlocking, rooting and flashing ROMs, but I took the easy way out and used to AIO tool. I am S-OFF as well
Having said that, I've been running a few Sense 3.6 ROMs without issues for the last 2 months. I saw that Nils has his Sense 4.0 ROM out and decided to take the plunge at v2.2
Now I decided that I wanted to update to the 3.14.605.10 leak before just in case. I followed the instructions on Nils ROM page. Or at least I thought I did. I screwed up at step 1
I factory reset from bootloader when Nils had clearly mentioned that I needed to reboot into recovery and factory reset, wipe from there. I then went ahead and flashed the 3.14.605.10 leak. It took a while but finally went through.
I didn't realize something was wrong until I tried to reboot into recovery. I couldn't find Amon Ra. I tried to push it more than a few times and it just wasnt working. I kept on getting an error - error: cannot load 'recovery-ra-vigor-3.15-gnm.img'.
Now I tried to install Amon Ra using the All in One tool and got an error there too. Something like 'Remote access denied'.
Finally I installed Quick boot to just check for the heck of it and that's when I got the error that I don't have root access.
So from what I can tell, I have one or possibly both the problems listed below:
> I lost root access when I did the factory reset from bootloader and/or flashed the leaked RUU
> I'm screwing up in my efforts to flash Amon Ra
Since I'm a noob, I could be completely off base and it could be something else, but this is what I could guess. I need help. I need someone to tell me where I messed up. And I guess I really need someone to help me figure out how I get from where I am now, to where I was before i.e. being able to flash ROMs using Amon Ra
I do see that I'm still S-OFF on the bootloader screen, but it used to say 'Tampered' there, but doesnt now.
I hope I've provided all the information for someone to help me. I tried searching the forums but unless I missed it, I didn't find a thread addressing the scenario that I face.
sniles1 said:
Full disclaimer - I am pretty much a noob at rooting devices. I got my first android phone which was a Rezound in december and I only just rooted it in May using the All in 1 tool. I read up on all the steps for unlocking, rooting and flashing ROMs, but I took the easy way out and used to AIO tool. I am S-OFF as well
Having said that, I've been running a few Sense 3.6 ROMs without issues for the last 2 months. I saw that Nils has his Sense 4.0 ROM out and decided to take the plunge at v2.2
Now I decided that I wanted to update to the 3.14.605.10 leak before just in case. I followed the instructions on Nils ROM page. Or at least I thought I did. I screwed up at step 1
I factory reset from bootloader when Nils had clearly mentioned that I needed to reboot into recovery and factory reset, wipe from there. I then went ahead and flashed the 3.14.605.10 leak. It took a while but finally went through.
I didn't realize something was wrong until I tried to reboot into recovery. I couldn't find Amon Ra. I tried to push it more than a few times and it just wasnt working. I kept on getting an error - error: cannot load 'recovery-ra-vigor-3.15-gnm.img'.
Now I tried to install Amon Ra using the All in One tool and got an error there too. Something like 'Remote access denied'.
Finally I installed Quick boot to just check for the heck of it and that's when I got the error that I don't have root access.
So from what I can tell, I have one or possibly both the problems listed below:
> I lost root access when I did the factory reset from bootloader and/or flashed the leaked RUU
> I'm screwing up in my efforts to flash Amon Ra
Since I'm a noob, I could be completely off base and it could be something else, but this is what I could guess. I need help. I need someone to tell me where I messed up. And I guess I really need someone to help me figure out how I get from where I am now, to where I was before i.e. being able to flash ROMs using Amon Ra
I do see that I'm still S-OFF on the bootloader screen, but it used to say 'Tampered' there, but doesnt now.
I hope I've provided all the information for someone to help me. I tried searching the forums but unless I missed it, I didn't find a thread addressing the scenario that I face.
Click to expand...
Click to collapse
Ok, here is the deal. When you ran the RUU it reinstalls the stock recovery. It also leaves you with the stock hboot which will not allow you to use most fastboot commands! bummer. You can find the ICS jounuponut bear hboot (J hboot) and flash that, and then flash the recovery via fastboot. you can find it
http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/
I think it is the 4th one down.
OR.. flash this ph98img which contains the recovery file here:
https://docs.google.com/open?id=0B28uLCcMCyfRZDZVOWNXbE90eWc
ctrl-s to download.
From there flash a custom rom and that should also give you root.
Thanks!
Thank you so much for your reply. I tried out both the things you mentioned but it didn't quite seem to work, mostly because I couldnt get the JHBoot to flash properly. I wasn't sure what I was doing wrong but decided to put in some effort to research this before bothering you with more questions. I think I found the solution.
I went the Unlimited.io site directly and downloaded the Vifor JHBoot for ICS_3.14.605.5 from there
I then followed the instructions they had listed to flash JuopunutBear hboots
'Put the phone in fastboot mode, connected to the pc and enter the following commands
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip '
I then rebooted into bootloader using 'fastboot reboot-bootloader'
And flashed the Amon Ra 3.15 img file you had linked to earlier. That finally seemed to work. Ijust validated it. I managed to flash Amon Ra finally properly. I think I have root back. Flashing Nils Sense 4.0 v.2.2 ROM as I speak.
Thanks so much for the advice. I was really stuck without it. I hope this information helps anyone else if they get stuck the way I did.
topgun1953 said:
Ok, here is the deal. When you ran the RUU it reinstalls the stock recovery. It also leaves you with the stock hboot which will not allow you to use most fastboot commands! bummer. You can find the ICS jounuponut bear hboot (J hboot) and flash that, and then flash the recovery via fastboot. you can find it
I think it is the 4th one down.
OR.. flash this ph98img which contains the recovery file here:
ctrl-s to download.
From there flash a custom rom and that should also give you root.
Click to expand...
Click to collapse
Glad you were able to get things corrected
Sent from my ADR6425LVW using Tapatalk 2
So just got the phone yesterday and I wanted to S-off immediately. Me being the idiot I am I fully rooted through fireballas method rather than temp-rooting and that messes up dirtyracun. So I need to flash the stock RUU again. I re-locked my phone and tried flashing the RUU and each time I get "FAILED (remote: 99 unknown fail)". Maybe I'm missing something here. How do I flash back to stock?
Are you following the instructions on the unlimited.io website? Because all you need to do is run the fastboot command and it should run just fine.
Sent from my ADR6410LVW using xda app-developers app
Ikikaea said:
So just got the phone yesterday and I wanted to S-off immediately. Me being the idiot I am I fully rooted through fireballas method rather than temp-rooting and that messes up dirtyracun. So I need to flash the stock RUU again. I re-locked my phone and tried flashing the RUU and each time I get "FAILED (remote: 99 unknown fail)". Maybe I'm missing something here. How do I flash back to stock?
Click to expand...
Click to collapse
after you get that error retype the command and it will go though. all part of the process
fastboot flash zip RUU.zip.
Aldo101t said:
after you get that error retype the command and it will go though. all part of the process
fastboot flash zip RUU.zip.
Click to expand...
Click to collapse
No matter how many times I try it won't flash. I figure it's the TWRP recovery or the root that's causing the problem. I must be missing something since I should be able to flash back to stock.
Ikikaea said:
No matter how many times I try it won't flash. I figure it's the TWRP recovery or the root that's causing the problem. I must be missing something since I should be able to flash back to stock.
Click to expand...
Click to collapse
It is most likely the custom recovery that is the problem. Flash the stock recovery (found HERE), then try the RUU again.
Good news! A factory reset and redownloading the RUU.zip fixed the problem. I have my theories on what was messed up, but I'm just glad it worked out in the end. Thanks to all the people who tried to help.
Help! My DNA isn't working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldn't mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Edit: Phone is now fixed, I went to IRC and a guy named Beaups took remote control and fixed it. Im not sure if thats his XDA username or not but if you guys see him make sure to give him a thanks Night everyone
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Its ok its very fixable, at this point. Just be very careful and very patient.
The worst thing you can do with something like this is get in a hurry or try to fix it while you're still very stressed out.
I'm passing on this advice because I almost screwed up yesterday because I made a boo boo and was in a huge hurry.
I'm going to wait for someone who knows more about this particular issue to chime in, but you have my word, I will help you resolve it after I do some more research while I wait for someone with more information or experience to post some info.
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
In the original unlock downloader thread, there is a link to an irc chatroom, I would suggest you go there as well as look for help here, and be patient waiting for some one to respond ...
Sent from my HTC6435LVW using Tapatalk 2
rootntootn said:
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Click to expand...
Click to collapse
Thats pretty much what I did but I keep getting that error:178 image file problem when its trying to finish (I am using the RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed.exe RUU) Also my phone is recognized as 2.04 when I haven't flashed anything
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Re-Unlock your bootloader with your Unlock token (Unlock_code.bin) then do a fastboot flash recovery recovery.img and use the CWM recovery that is 6.0.2.8 (i believe is the most recent version) and you should be able to sideload your rom ... or if sideloading doesnt work just do an adb push rom.zip /sdcard/rom.zip and that will put the rom that you want to use on the root of the sdcard and then you can flash that there...
This should hopefully get you working again...
beasleyj62 said:
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Click to expand...
Click to collapse
I keep getting this when I flash the hboot
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
sending 'zip' (434 KB)...
OKAY [ 0.205s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.274s
and when I flash the Radio I get
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
error: cannot load 'PL83IMG.zip': Unknown error
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
beasleyj62 said:
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
Click to expand...
Click to collapse
I can unlock it at anytime....
see if you can flash after you unlock again
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
All I needed to run the RUU was the ENG Hboot. Flash it then you should be able to install the RUU provided you have the correct drivers installed.
Sent from my HTC6435LVW using xda app-developers app
He is still s-on.
Sent from my HTC Droid DNA
Andro X said:
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
How would I go about doing that?
beasleyj62 said:
see if you can flash after you unlock again
Click to expand...
Click to collapse
I didnt work. This is my 2nd DNA so I have done this before and it worked successfully(The first one had a screen problem)
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Halcyon7 said:
How would I go about doing that?
Click to expand...
Click to collapse
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
beasleyj62 said:
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
I only found 1 link on my computer doctors forum but that link wasn't it
.torrented said:
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
Click to expand...
Click to collapse
No I haven't. I used the s-off facepalm method and I did everything as it said and now when I went into recovery nothing will mount and my device when trying to use the RUU says its a 2.04. So I didnt take the ota but thats what it is recognized as
My phone was acting buggy with the radios and had HUGE performance issues. To be frank, i think a SNAIL was faster than this phone at the time... I am S-OFF, unlocked and i cannot flash recovery.
I get this output and error:
Code:
sending 'recovery' (8516 KB)...
OKAY [ 1.087s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.129s
here is the current HBOOT Config and display:
Code:
FIREBALL PVT SHIP S-OFF RL
CID-VZW__001
HBOOT-1.15.0000
OpenDSP-29.1.0.45.622
eMMC-boot
Just for good measure i re-wrote the CID to 11111111 and locked and unlocked the bootloader again to no avail, thinking it was possibly that being unlocked during an RUU. The thing is, while unlocked, the RUU still processed... Oh and the phone boots up fully. i have ZERO issues with actually using the phone, but i cant believe i am stuck on a stock rom and not allowed to flash a custom recovery... >_>
Other thing... just to see if this would help, i used junkmail9's ENG HBOOT with the RegawMOD Customizer to flash the ENG hboot to try my luck. STILL no good. i can flash hboot directly, and whatever else, but is recovery just stuck??
i really want to be free again, so can someone please explain to me why after an RUU even WHILE S-OFF and unlocked, that i cannot flash recovery?
cyberkeeper1 said:
I get this output and error:
Code:
sending 'recovery' (8516 KB)...
OKAY [ 1.087s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.129s
Click to expand...
Click to collapse
You did not mention either the recovery image you tried to flash, nor the command you used to try and flash it. There's no point in messing with bootloader lock/unlock if you're s-off. Just leave it alone.
my apologies... well basically, i cannot flash any custom recovery for this phone. CWM 6.0.3.1 which i had before the restore, and i just tried the philZ Touch 5 recovery which is basically the same thing as CWM... for some reason, the recovery partition became locked after the restore despite being s-off. i remember this error before while s-on and locked when I used to have the Wildfire S.
cyberkeeper1 said:
my apologies... well basically, i cannot flash any custom recovery for this phone. CWM 6.0.3.1 which i had before the restore, and i just tried the philZ Touch 5 recovery which is basically the same thing as CWM... for some reason, the recovery partition became locked after the restore despite being s-off. i remember this error before while s-on and locked when I used to have the Wildfire S.
Click to expand...
Click to collapse
alright, i am a dodo-bird... apparently, i really need glasses because i JUST noticed that i was flashing a zip file.... dang it... for whatever reason, it can flash zip files, but i guess i didnt have the right one. anyhow, no help needed now. Mods, you can close the thread... my apologies for the wasted space. If its any consolation, i havent really slept so.... yea. lol. thanks for the help thus far.
i wasnt flashing the IMG file like i should have been.
similiar issue
hello users of the almighty xda!
I have obtained s-off using dirtyracun and flashed between team venoms viper rom and cyanogenmod10.1 multiple times
this last time I tried to flash back to viper2.2.0 from cyanogenmod because of the problems with the m2 snapshot I wiped everything as usual including cache,data, and even a factory reset and installed the viper rom and said everything was good to go and now the phone wont boot past the htc screen
so I figured i'd reflash the viper boot.img to see if that would help and doesn't
not only will it not boot but when I go to the bootloader and try to enter recovery it flashes and I see the clockwork mod symbol and then it boot loops back to the htc logo endlessly
wtf! ugg! any ideas oh great xda users?
p.s im also under the impression that because im s-off I cant RUU back to stock is this the case?
styxking said:
im also under the impression that because im s-off I cant RUU back to stock is this the case?
Click to expand...
Click to collapse
This is not true. You may at any time run the RUU to restore borked programming. Besides, the dirtyracun method of flashing s-off is risky to say the least. I used facepalm s-off and it was stupid easy. Anyhow, run the RUU and then immediately run a factory reset. The RUU formats and repairs all partitions on the device and the factory reset restores the radio and baseband as described by mdmower.
Sent from my ADR6410LVW using xda app-developers app
Do the following to prepare for RUU-
Run these commands in order:
fastboot oem resetRUUflag (wait for reload)
Fastboot oem rebootRUU
Fastboot erase cache
Fastboot flash zip name_of_file.zip
Alternatively, you can run the automated HTC RUU utility, but it often fails vs. A manual reflash.
Sent from my ADR6410LVW using xda app-developers app
ignore please, came late and didnt notice
gonna try it
thanks for the response. I agree the dirtyracun method is pretty risky, but at the time I think it was the only s-off method I could find
well I will ruu then
thanks for the detailed fastboot commands and such
I don't have to relock the bootloader do I?