Please help. I have unlocked this phone through HTC Dev. I have flashed a custom recovery. Somewhere through this process, the original installation of the factory rom from VM was deleted. That doesn't bother me because I was never going back to it anyway, but If I had it right now, I wouldn't be here. I have tried to use the RUU exe in fastboot and the RUU zip in recovery from here. Neither will install, exe throws errors and the zip returns [bad]. I have also tried the [ROM] NegaLite-BluRom-JCFunk | 2.95 | Sprint/VM | Sense/Apex/Nova | 03/25/2014. This eventually installed, but will not boot even with installing boot.img separately. I followed all directions to the best of my ability, but by no means am I saying I did correctly, but I am pretty sure I did. So to recap - I have whats in the title, but no rom whatsoever installed that can be accessed. Any takers?
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Click to expand...
Click to collapse
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
oD33z said:
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
D33z
Click to expand...
Click to collapse
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Click to expand...
Click to collapse
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
oD33z said:
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
Click to expand...
Click to collapse
here's the thread
http://forum.xda-developers.com/showthread.php?t=2831444
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I am great with linux, but was under the assumption it needed to be burned to cd and that USB was not an option, please advise if not the case. I have read a ton and I remember reading about Unknownforce, but cant remember if thats the case or not.
Off topic: I learned from you that it has to be locked to go stock, but does it need to be unlocked to flash your rom or locked as well?
Unlocked for custom, locked for stock.
Here is unknownforce ultimate tool,
there was a live cd version made for windows users scared of linux.
I use tiny core linux for this, Ubuntu tries to mount all the partitions and you only have a 5 second window when they are writeable. I have used Ubuntu, at first, but preferred tinycore.
But first you are going to need to get stock.zip to install.
http://forum.xda-developers.com/showthread.php?t=1653777
I would do fastboot boot recovery.img
Then install negalite, so atless you can boot the phone
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
---------- Post added at 12:37 AM ---------- Previous post was at 12:24 AM ----------
here is 4ext recovery I would use this one first until you get used to things, best recovery for 3d.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
oD33z said:
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
Click to expand...
Click to collapse
did you fastboot boot?
There are several custom recoveries out there.
Here is thread for 4ext
http://forum.xda-developers.com/showthread.php?t=1408936
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
What I meant was, in your opinion, is the 4ext a better recovery than the unofficial TWRP?
During the install of Negalite at the point of -Setting Up Kernel Over-Clock Settings
under this it reads: assert failed: write_raw_image("/tmp/newboot.img","boot")
Is this a red flag of something not going right in any way?
After this I click Next>Recovery>Wipe Dalvik>Reboot and it boots into Fastboot. Whats happening at this point?
Since I am basically starting from scratch and the end goal is to have a kitkat rom and possibly S-OFF(if its a must to do so).
What all needs to be done as far as formatting, tweaks, or anything else to achieve the best performance, space, or anything you can think of?
Thats if you dont mind sharing. I appreciate your time and if I can be of service to you in any way, I will.
I am currently on the 4ext recovery with 1GB sd-ext 0 swap and formatted Ext4.
fastboot boot recovery.img
flashrom.zip from recovery
reboot, wipe dalvik, reboot
Negalite.zip installed with no errors whatsoever.
Thank You.
Beautiful smooth running rom btw.
Does all that above sound like I did the right things as for setting up and installing?
4ext is most stable, the unofficial has new features like f2fs and selinux, but 95% stable.
fastboot boot recovery.img is an old work around, also used to flash boot.img with fastboot. That is ok with roms that include a whole boot.img but roms like mine use a dynamic boot.img. Basically the installer makes the boot.img using your choices.
From what I know about Kitty kat I think you need to downgrade hboot or be s-off. Not sure I've stayed on ics for stability because I still use this phone. Also there is a new version of negalite on svn, just takes hours for me to upload a zip version.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Revision 7
Are you sure this is the latest?
oD33z said:
Revision 7
Are you sure this is the latest?
Click to expand...
Click to collapse
Lol, yes since I updated it a few weeks ago
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
I should have worded that different really, the revision numbers threw me, I honestly was just making sure I was in the right place. 48mb smaller, anything stripped?
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Click to expand...
Click to collapse
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
oD33z said:
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
Click to expand...
Click to collapse
Here. Try this
https://www.androidfilehost.com/?fid=23578570567720169
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
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 ?
My Evo has been completely trashed and I have no clue what to do.
I have hboot 1.19 s-on and I did the HTCdev unlock, and I rooted it and have the latest version TWRP (i think 2.3.something) with SuperSU installed. I tried to flash a ROM that was supposed to be compatible with with I had but i guess not. Everything was going great but I was stuck on the CM boot screen. After about 30 min of it sitting in that screen I figured something was wrong so i reset it and went back into TWRP. Someone told me to download MeanRom and flash that because its kernel and rom would fix everything. Here's where things get weird. I download MeanRom to my computer and mount my phone in TWRP to move the file over to the phone and when i went to factory reset before flashing it it kept saying unable to mount SD card and Internal Storage. I tried to do a restore my phone to an old back up and that wouldnt even work. So I wipe both caches and try to flash MeanRom anyway. i got a failed error and my phone shut off. Now my phone will only go into the Fastboot thing on the white screen and when i try to go into recovery, it just stays on the TWRP loading screen, not even letting me into the recovery program.
Is there anyway to fix this? My best buy insurance has expired because i missed 3 payments since I'm away at school and not working a whole bunch. So my whole smash it to pieces and get a new one solution is no longer an option.
I'm on a mac by the way so is there something I can enter into terminal to fix this? I don't care about losing any files or anything I'll do whatever I have to, to fix this.
Thanks in advance
- Josh
Read om4's guide don't panic...hboot 119 s-on you have to flash kernels separately.
Sent from my EVO using xda premium
I ran into the same problem. Word for word, really. I use a Mac, too. I went through HTCdev unlock, tried to flash a CM10 nightly and ran into a boot loop. No matter what I did, it was stuck. I couldn't restore to a nandroid backup because internal storage wouldn't mount. Couldn't do anything. All I had access to was bootloader and TWRP recovery.
I don't know the specifics of how this fixed it (I'm nothing close to a developer), but this is what I did to get out of it. You will need access to a Windows machine onto which you can download things.
1) If you still have access to fastboot, unroot your phone to stock. Completely stock.
2) Use DirtyRacun S-OFF (you'll need a Windows computer for this). Go through the whole process.
3) Re-root.
Nothing I tried fixed it until I started fresh. I couldn't tell you how it worked, but if you're desperate you really have nothing to lose but a little bit of time by doing the same thing I did.
Hope you get this figured out.
falconoble said:
I ran into the same problem. Word for word, really. I use a Mac, too. I went through HTCdev unlock, tried to flash a CM10 nightly and ran into a boot loop. No matter what I did, it was stuck. I couldn't restore to a nandroid backup because internal storage wouldn't mount. Couldn't do anything. All I had access to was bootloader and TWRP recovery.
I don't know the specifics of how this fixed it (I'm nothing close to a developer), but this is what I did to get out of it. You will need access to a Windows machine onto which you can download things.
1) If you still have access to fastboot, unroot your phone to stock. Completely stock.
2) Use DirtyRacun S-OFF (you'll need a Windows computer for this). Go through the whole process.
3) Re-root.
Nothing I tried fixed it until I started fresh. I couldn't tell you how it worked, but if you're desperate you really have nothing to lose but a little bit of time by doing the same thing I did.
Hope you get this figured out.
Click to expand...
Click to collapse
How would i unroot if I cant get into SuperSU since i cant boot up my phone? Do I need to do that first or can i just run the RUU without Going into SuperSU and hitting Unroot?
Also what do I need windows for? Getting S-OFF? Or unrooting?
Also thank you! I really hope this work!
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Shahal said:
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Click to expand...
Click to collapse
I'm sorry if this is a stupid question. But how do i re-lock it from fastboot?
U have to use the cmd window on your windows computer. I did it with mine before I ran dirty racun. It is a simple command but u have to be in the right directory ind the cmd line. Go through and look at the dirty racun guide and it tells u how to re-lock word for word I believe.
Sent from my EVO using xda app-developers app
Shahal said:
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Click to expand...
Click to collapse
Okay so I found a video on how to re-lock my phone in fastboot but when i type the command "fastboot oem lock"
it just says ' <waiting for device >
any suggestions on what to do? It's been stuck like this for about 5 min now.. in the video it took less than a second.
jklatt747 said:
Okay so I found a video on how to re-lock my phone in fastboot but when i type the command "fastboot oem lock"
it just says ' <waiting for device >
any suggestions on what to do? It's been stuck like this for about 5 min now.. in the video it took less than a second.
Click to expand...
Click to collapse
Turn on USB debug in devopleper options
Sent from a lens flare powered EVO LTE
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
Yeah i couldn't figure out how to do that. I would ask a question on how to do that and i just kept on getting the response of "google it" "look it up on youtube" or look in the forums. and I wasn't ever sure really where to find it because all my searches for it came up useless.
I just did the RUU on my phone and its finally back up and running! What a relief!!!
Now I'm going to try to get DirtyRacun s-off. How do I put a Custom Rom on my phone with S-off?
With s-off you just flash it in twrp..no extra steps
Sent from my EVO using xda premium
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
I only have windows 7 64bit. So this means i cannot go the dirtyracun route. Is there any other way to get S-OFF?
if not.. How do i fastboot flash the boot.IMG from the ROM manually?
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
I wish I'd ran into you when I had the same problem. I wasn't trying to make things more complicated for him, just telling him that when it happened to me, I went back to stock, went with S-OFF, and everything worked fine. At the very least I figured he probably would have just wanted his phone back.
falconoble said:
I wish I'd ran into you when I had the same problem. I wasn't trying to make things more complicated for him, just telling him that when it happened to me, I went back to stock, went with S-OFF, and everything worked fine. At the very least I figured he probably would have just wanted his phone back.
Click to expand...
Click to collapse
No. You helped me soooooo much! I was literally about to sell my phone for parts or something because everything went wrong that could go wrong and on top of that I couldn't find anything at all on how to fix it. I just did what you said and my phone is fixed! I want to go s-off now but dirtyracun doesn't support windows 7 with 64 bit, it only supports windows 7 with 32bit which I don't have access to. So i'm trying to find another way that is reliable to go S-OFF. It seems like S-OFF is the way to go and it makes everything easier.
If I cant find out how to go S-OFF with the windows 7 64 bit computer, then I guess i'll go S-on HTCdev unlock again and hopefully figure out how to manually flash the ROM or whatever it is that you do with S-ON.
jklatt747 said:
No. You helped me soooooo much! I was literally about to sell my phone for parts or something because everything went wrong that could go wrong and on top of that I couldn't find anything at all on how to fix it. I just did what you said and my phone is fixed! I want to go s-off now but dirtyracun doesn't support windows 7 with 64 bit, it only supports windows 7 with 32bit which I don't have access to. So i'm trying to find another way that is reliable to go S-OFF. It seems like S-OFF is the way to go and it makes everything easier.
If I cant find out how to go S-OFF with the windows 7 64 bit computer, then I guess i'll go S-on HTCdev unlock again and hopefully figure out how to manually flash the ROM or whatever it is that you do with S-ON.
Click to expand...
Click to collapse
Most sense roms come with a kernel installer for people that are S-ON and there have been reports of success using Win7 64bit and running DirtyRacun but.... if you run into problems they will not help you
bigdaddy619 said:
Most sense roms come with a kernel installer for people that are S-ON and there have been reports of success using Win7 64bit and running DirtyRacun but.... if you run into problems they will not help you
Click to expand...
Click to collapse
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
jklatt747 said:
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
Click to expand...
Click to collapse
It's included in the script just flash it like any other rom it takes a little longer to boot because it's writing the kenel so don't freak out
jklatt747 said:
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
Click to expand...
Click to collapse
There is an app in the market called Flash Image GUI to use it all you have to do is click on browse in the app search where ever you downloaded your Rom or kernel select it and it will extract and flash the boot.IMG for you. So if you are s on and wanna flash a aosp Rom you can first flash the kernel using the app then it gives you the option to boot directly in to recovery then install as usual wipe system ,data, both caches and flash your Rom that you extracted the kernel from. You can also just flash just a kernel if you want to OC.
Sent from my EVO using xda premium
bigdaddy619 said:
It's included in the script just flash it like any other rom it takes a little longer to boot because it's writing the kenel so don't freak out
Click to expand...
Click to collapse
dandan2980 said:
There is an app in the market called Flash Image GUI to use it all you have to do is click on browse in the app search where ever you downloaded your Rom or kernel select it and it will extract and flash the boot.IMG for you. So if you are s on and wanna flash a aosp Rom you can first flash the kernel using the app then it gives you the option to boot directly in to recovery then install as usual wipe system ,data, both caches and flash your Rom that you extracted the kernel from. You can also just flash just a kernel if you want to OC.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Okay so here's whats happens for me.
When i go bigdaddy's way: I put the MeanRom zip on my phone from my computer (MeanRom v64 or what ever the latest one is) I factory reset, wipe cache, wipe dalvic chache, and then go to install find the app and swipe to flash.. everything seems fine until i get an error and fail. It also says there is no MD5 file when i do this.
When I go dandan's way: I have the MeanRom zip on my phone (i've tried this with v64 *or whatever the latest one is* and v34) then i go into flash image GUI and go through finding it and everything. Then i get an error right above the Flash Image button saying "zip file must contain only one of the following: recovery.img, zimage, or a type of boot.img!" On my computer I unzipped the file and looked inside and all I see the boot.img and some folders but no recover or zimage so i dont know what it is talking about.
I really dont want to go through the processes of unrooting and relocking my phone again so i want to do this right. Any help from here on out would be greatly appreciated!
If someone could give me a step by step to follow or something for putting the Latest version of MeanRom on my phone that would be great!! I think i read somewhere that you have to put on the old version of MeanRom first. If that is so, could you also include how i would go about updating from the old version to the new one?
(If you're going to help me please make sure your method supports the HTC EVO 4G LTE on hBoot 1.19 Software v. 2.13.651.1 71ORD HTCdev Unlocked and Rooted with SuperSU and TWRP. (GooManager, and Flash Image GUI are installed to)
I dont know if this matters but it also says under Kernel Version:
3.0.8-01680-gb6402b4
[email protected] #1
SMP PREEMPT
Other info:
Baseband v: 1.12.11.0809
Android Version: 4.04
HTC Sense: 4.1
HTC SDK API level: 4.24
I know this post is really long and I probably put waaayyy more information then I actually needed to but I just want to be safe. It seems like everything I try for putting any Roms on my phone goes wrong with an error or failed message and I really want to do this.
I had followed this video ht tp://w ww.youtub e.com /watch?v=hQtUxEL8pd8 and did everything correctly. When I go to boot my phone up it shows the blue android boot animation then the green HTC animation then restarts.
Hboot 1.57
Somehow my recovery got deleted.
Clockworkmod recovery is installed.
I just don't know what to do
Is there a way I can just undo everything and go back to the stock rom?
Edit: Tried ViperROM and it's doing the exact same thing.
Make sure you are wiping everything except sdcard and then flash the rom. Maybe even try changing recoveries to 4ext.
Sent from my PG86100 using Tapatalk 2
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Jsparta26 said:
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Click to expand...
Click to collapse
I'm S-on, will it matter? And also I do mean 1.57. And one more thing. Does it matter if I boot up into a recovery using the command prompt? Also I'm not sure what kernel it is. I guess the one that's in the zip folder? Also sorry for slow responses I've been working days. Any chance you'll be on tomorrow around 7pm central?
Update: I reformatted everything and tried reinstalling Viperrom through CWM but no dice still boots up and resets. Got 4ext installed. Working from there.
Update: 4EXT is the best recovery I've ever seen and I'm never using CWM again.
Update: I installed VIperROM through 4ext and it's still restarting itself.
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Jsparta26 said:
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Click to expand...
Click to collapse
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I? Also i youtubed bootloop to see if it is really what's wrong and I came up with this video. ht tp ://www .y outube.co m/watch?v=OKXTD1-fqbc and my phones doing more than that. It's booting up all the way then once the screen and dock begins to load it restarts.
IAnb3rlin said:
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I?
Click to expand...
Click to collapse
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Jsparta26 said:
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Click to expand...
Click to collapse
How do I flash a kernel? I'm not really sure what one is, I just know it's really important.
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Jsparta26 said:
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Click to expand...
Click to collapse
I formatted everything using 4ext and installed a rom i also flashed the boot img just incase and it still restarted.
Here's the steps I took.
1. Format everything.
2. Download the.zip file and copy to SD card.
3. Load the recovery and enable smartflash.
4. Installed the rom.
5. Flashed the boot.img
6. Also tried without flashing the boot img.
And just to clarify. I'm installing ViperROM. And I only need the .zip file, correct?
I ended up using RUU to fix it and go back to the stock rom/ect, Then locked the bootloader unlocked it and flashed superuser and rooted it then got s-off using the wire trick. But after I rebooted it keeps taking me back to the jbear bootup logo and when I try to flash a recovery it doesn't load I just get the htc logo then jbear logo then it restarts. I followed this guide.htt p://w ww.yo utube.co m/ watch?v =tRj47iFQvbE I found here on the xda forums.
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Jsparta26 said:
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Click to expand...
Click to collapse
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
IAnb3rlin said:
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
Click to expand...
Click to collapse
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Jsparta26 said:
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Edit: just realized your using virgin mobile correct? I believe the reason your phone kept bootlooping with viper ROM was because of hboot. Try flashing a different hboot with the same method as the ruu and recovery.
Click to expand...
Click to collapse
I downloaded root checker and apparently I'm not root anymore. Yes I'm VM. I'm trying to rename the recovery and update it using the SD card now.
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
IAnb3rlin said:
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
Click to expand...
Click to collapse
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Jsparta26 said:
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Click to expand...
Click to collapse
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
IAnb3rlin said:
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
Click to expand...
Click to collapse
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Jsparta26 said:
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Click to expand...
Click to collapse
I just ended up unlocking the boot loader again and installing the recovery that way. Then saw this.. oh well lol. I really do appreciate the help. . I'm going to try to install viperrom again, and double backup this time! I'll let you know how it goes.
Hey guys i gota semi bricked EVO LTE on the 3.16 SW i was wondering if anyone can help me fix. I tried to root it and thats what caused this issue. I did the bootloader unlocked, loaded TWRP recovery, then installed SU, then it wouldn't turn on, would only flash to sprint screen.
I have tried to to a full wipe / factory - didn't work
i have tried to load the 3.15 RUU - does not work (it just shows loading the rom forever)
i have tried to load it through fastboot via Ulimited.IO (it just freezes during the loading of the SW)
what else can i try? I seems like everytime the phone tries to take a ROM it will just not respond.
thanks
OK your on the latest firmware I think 3.16 and if your s-on that means you have the new touch panel driver which limits what ROMs will work on your device.
You need to download a ROM with a s-on installer included or pull the boot IMG from the ROM and flash via fast boot because you can't flash kernels easily when your S-ON .You also will need a rom that's compatible with the latest fw. AFAIK most of the sense ROMs will be good to go, I really don't know which ones cause I'm s-off and don't have the tp driver problem.
If you need more info there's s thread stickied in Q&A called "don't panic" that will answer most of questions
Once your up and running you should go about getting S-Off.
SENT FROM MY LTEVO
corcgaigh said:
OK your on the latest firmware I think 3.16 and if your s-on that means you have the new touch panel driver which limits what ROMs will work on your device.
You need to download a ROM with a s-on installer included or pull the boot IMG from the ROM and flash via fast boot because you can't flash kernels easily when your S-ON .You also will need a rom that's compatible with the latest fw. AFAIK most of the sense ROMs will be good to go, I really don't know which ones cause I'm s-off and don't have the tp driver problem.
If you need more info there's s thread stickied in Q&A called "don't panic" that will answer most of questions
Once your up and running you should go about getting S-Off.
SENT FROM MY LTEVO
Click to expand...
Click to collapse
thanks for the info. So i need to get a rom with s-on installer and flash it via fastboot flash zip xxxxxx.zip? But i'm not even sure if i'm rooted. I did install the SU in there, it said okay, but now i cant access the recovery. only fastboot. would this damage the phone in anyways?
thanks
right now its showing
**tampered***
** relocked **
** security warning**
Jewel PVT SHIP S-ON RL
HBOOT - 2.09
RADIO - 1.12.11.1210
OpenDSP - V31.1.0.45.0815
emmc- Boot
oct 18 2012
I just tried to flash MeanBean v309 on it via fastboot and it didn't work? is it because the file is too big? I am pretty sure the bean mean is a S-on ROM
Looks like u need to unlock again. Use the same command as the last time
"Fast boot OEM unlock" or whatever it is. Flash twrp recovery thru fast boot. Once you have twrp installed flash a rooted ROM to gain root.
SENT FROM MY LTEVO
corcgaigh said:
Looks like u need to unlock again. Use the same command as the last time
"Fast boot OEM unlock" or whatever it is. Flash twrp recovery thru fast boot. Once you have twrp installed flash a rooted ROM to gain root.
SENT FROM MY LTEVO
Click to expand...
Click to collapse
took your advice, re-unlocked it and installed TWRP recovery on it, and now i get recovery, but i cant use it because the touch screen does not work so i'm in the process of trying to find a CMW recovery instead and try to install a newer rom.
truwrxtacy said:
took your advice, re-unlocked it and installed TWRP recovery on it, and now i get recovery, but i cant use it because the touch screen does not work so i'm in the process of trying to find a CMW recovery instead and try to install a newer rom.
Click to expand...
Click to collapse
Do not use CMW. It was abandoned a long time ago for our phones. Something about it screwing up partitions. Install a new version of TWRP. 2.4 or higher. And Venom rom has an s-on installer for sure. Other roms might have one but I'm not sure which ones. Stay away from CMW.
The s-on installer is just an installer added to the ROM zip so that you don't have to flash the boot.img seperately. Just get a working version of TWRP and flash Venom (or other s-on friendly rom). That should work.
tilltheend714 said:
Do not use CMW. It was abandoned a long time ago for our phones. Something about it screwing up partitions. Install a new version of TWRP. 2.4 or higher. And Venom rom has an s-on installer for sure. Other roms might have one but I'm not sure which ones. Stay away from CMW.
Click to expand...
Click to collapse
ahh okay thanks, i'll give it a shot and report back.
truwrxtacy said:
ahh okay thanks, i'll give it a shot and report back.
Click to expand...
Click to collapse
thanks guys so i got it working! i appreciate everyones help! I ended up loading a new TWRP recovery, and loading the new Meanbean and it works now.
I have one last question, does this mean i can only install roms compatible with 3.16 now? The only reason i went through all of this was because i wanted ICS on it. The new JB diag drivers dont work, and the only way i can make the diag drivers work is to downgrade to ICS. If i try to downgrade will i mess it up again?
thanks
truwrxtacy said:
thanks guys so i got it working! i appreciate everyones help! I ended up loading a new TWRP recovery, and loading the new Meanbean and it works now.
I have one last question, does this mean i can only install roms compatible with 3.16 now? The only reason i went through all of this was because i wanted ICS on it. The new JB diag drivers dont work, and the only way i can make the diag drivers work is to downgrade to ICS. If i try to downgrade will i mess it up again?
thanks
Click to expand...
Click to collapse
Yes, you are stuck on 3.16 roms. Anything below and your touchscreen won't work. I highly recommend going for s-off. Makes everything so much easier. The only other option is to use babyracun from unlimited.io then ruu to 3.15. But if you're doing that you might as well go for s-off.
tilltheend714 said:
Yes, you are stuck on 3.16 roms. Anything below and your touchscreen won't work. I highly recommend going for s-off. Makes everything so much easier. The only other option is to use babyracun from unlimited.io then ruu to 3.15. But if you're doing that you might as well go for s-off.
Click to expand...
Click to collapse
Agreed. I did babyracun and then Facepalm afterwards. Worked great on Windows 7 64bit of which isn't supported by the developers, of course
Delakit said:
Agreed. I did babyracun and then Facepalm afterwards. Worked great on Windows 7 64bit of which isn't supported by the developers, of course
Click to expand...
Click to collapse
Which is what this guy should do since he doesn't have ubuntu and probably doesn't want to use a live disc.
thanks alot guys, i was not aware of the babyracoon. I'll give that a shot.
thanks
i have a question about baby racoon, as it does not have a separate thing for it.
So do i download baby racoon and run all the adb commands, and then run face palm, then ruu?
or do i download baby racoon and run all the adb commands, and ruu then face palm?
sorry i'm a noob
truwrxtacy said:
thanks alot guys, i was not aware of the babyracoon. I'll give that a shot.
thanks
i have a question about baby racoon, as it does not have a separate thing for it.
So do i download baby racoon and run all the adb commands, and then run face palm, then ruu?
or do i download baby racoon and run all the adb commands, and ruu then face palm?
sorry i'm a noob
Click to expand...
Click to collapse
Do steps 6-9 on unlimited io. That will leave your phone at stock 3.15. Then go and find out what facepalm requires and continue with that.
Hi,
I have a Sprint CDMA HTC EVO 3D. I tried root and get S-OFF for it. Unfortunately I failed and now the phone fail to boot.
Below is what I did from which you might be able to diagnose it and give me suggestions.
(1) The original status of mu phone is:
Stock rom, I never root it before.
HBOOT-1.58.0000
Android Version: 4.03
HTC Sense version: 3.6
Software version: 2.95.651.6.710RD
(2) My root procedures:
I followed this post: http://forum.xda-developers.com/showthread.php?t=1813818
I successfully unlocked phone with HTCDev, successfully Flashed 4EXT recovery, and successfully installed Superuser-3.1.3-arm-signed.zip. I also booted into sytem, everything worked well.
However I failed in next step of JuopunutBear's Wire Trick (S-OFF). When I ran ControlBear.exe, it finally hanged there.
Current status of my phone:
Unfortunately I did not make a backup to my original ROM, so there is no way to revert back by restoring backup.
Now the phone is in unlocked status, I was able to boot to HBOOT and also enter 4Ext recovery, however I am not able to boot into Android. If I try to boot into Android, it always hang at black screen.
I am able to boot to fastboot (USB) mode, I tried to flash some stock ROM (listed at http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209), but I failed. For example, I ran a RUU of 2.89.exe, it detected my phone version is 2.95, and further update RUU failed.
Looks like my partition is ruined, but I might be wrong.
ANyone can help me to restore my phone to working status? At least I need the phone to be able to boo to Android.
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
lsdyna said:
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
Click to expand...
Click to collapse
EDIT:
Okay. I've got some questions.
1. You're stuck on some black screen as you said. It boots past the white HTC splash and then it's stuck on that black screen, right. Do you mean the juopunutbear "arrow screen" - juopunutbears boot.img?
2. I think if you had flashed the original boot img everything would have been fine.
3. The easiest way is to flash to stock, so lets try to figure out why it doesn't flash.
MrJyrks said:
Okay. So from what I understood, you are stuck on the black juopunutbear screen, right?
Click to expand...
Click to collapse
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
lsdyna said:
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
Click to expand...
Click to collapse
And you can boot to recovery, right?
EDIT:
One more thing. Which ruu were you trying to run
Edit2:
What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Edit3:
BTW, this was on the wire trick page... http://unlimited.io/jbtroubleshooting.htm - TROUBLESHOOTING There was everything you needed to know when you failed at something. Remember that page. You may need it the next time you try to do the wiretrick.
Q: Were you using a linux distro for the wire trick and did you use the appropriate files for wire trick since GB and ICS have separate tools?
If you want I may assist you in gaining s-off if we get this thing functional again.
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
MrJyrks said:
And you can boot to recovery, right?
EDIT: One more thing. Which ruu were you trying to run
Edit2: What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Click to expand...
Click to collapse
lsdyna said:
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
Click to expand...
Click to collapse
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Edit: This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Now I only want to revert my phone to stock, not considering root at present time.
I searched 2.95 ROM, unfortunately the highest version that I can find is 2.89. Does this mean I have no way to revert my phone to live? Thanks a lot.
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
lsdyna said:
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
Click to expand...
Click to collapse
If you have access to the recovery, most likely, yes.
Hello MrJyrks,
Thank you so much for the link! I am eager to try that. Before I do that I think I shall ask two questions to avoid further mess up the device:
Question #1: To install the deodexed rom, which is the correct way:
(1) Rename the ZIP file to PG86IMG.ZIP, put to root of sdcard, then boot, letting the Bootloader to do the update.
(2) In 4EXT recovery, enable smartflash, enable script asserts, then install the zip from the root of sdcard.
Question #2: You said I shall flash boot image, can you tell me how to do this? I mean, where shall I get the boot image file? Flash it with 4EXT? SHall I do it before or after install ROM zip file?
Thank you very much for your helps!!!
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I tried install the stock ROM from your link (using 4EXT with smartflash enabled and script asserts enabled.) . Amazing that installation completed successfully (indeed this is the first ROM zip that I was able to install successfully since I mess up the device). When I exit After that, it did some further update which I guess is the boot.img that you mentioned.
4EXT it said 'a pending update for your boot partition is detected' and I think it was doing the boot image flash that you mentioned, right?
Unfortunately when I boo the device, I still got black screen.
Now I am unlocked and also rooted (since I successfully installed superuser in 4EXT). DO you think I shall lock the devioce before installing the stock ROM? If so, one possible issue is that if I relock the device, I found 4EXT is not available. In that case, how shall I install the ROM zip file?
Thanks.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
Further update:
I flashed boot image by: fastboot flash boot boot.img which is included in the stock ROM zip file.
The flash went successfully. However, I am still not able to boot to Android. WHat I have is the device hang there, alternatively displaying logo with white background, and black screen.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
lsdyna said:
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
Click to expand...
Click to collapse
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
MrJyrks, thank you so much!!!
MrJyrks said:
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
Click to expand...
Click to collapse
Similar problem, can't return to stock
I have a problem similar to lsdyna's, and am hoping that even though this post is old, MrJyrks or someone might be able to help me.
I am unsuccessfully trying to return my phone to stock. First a bit of history.
I had 2.95.651.6.710RD s-on hboot 1.58 Android Version: 4.03 HTC Sense version: 3.6 on my phone, and wanted root. I didn't need s-off, just wanted to root so could do some tweaking (stop some apps from autostarting, stop some form getting network access, etc.) so loaded 4EXT Recovery Touch, and got root (fastboot oem get_identifier_token method), got superuser in there, and happily began tweaking. Famous last words... I didn't make a backup right away (learned my lesson!) and suddenly found a 'overtweaked' sluggish phone on my hands.
Thought best thing would be to lose the root & return to stock & start over, carefully, making backups.
So I used Fastboot (fastboot oem lock) to lock it (worked) and proceeded to try to load 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 into it [via my computer], but didn't realize until reading MrJyrks post that a lower RUU couldn't be used.
I now am relocked (phone does boot up, but can tell the system tweaks are still slogging it), lost the recovery, and wondering what to do... do I try putting recovery back in & using the Negalite 2.95 stock deodex ROM MrJyrks mentioned? If so, how do I use that zip file method verses the exe one I tried thru my computer?
Thanks for the help
You had issues with the RUU because your main version is higher than that contained in the RUU.
Unlock, flash recovery again. Boot into recovery and flash this zip: https://copy.com/wlVvwssXXNN00Pe
That will lower your main version. Relock the bootloader, put the phone into fastboot USB mode, then run the RUU while in fastboot USB mode.
Should be back to stock after that.