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 ?
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
I had much the same problem with my cdma, hboot 1.5, S-On shooter. When I was S-On none of the ICS roms would work. The all bootlooped on me. If you follow the rooting method found here on xda, it will get you back to a stock Rooted GB Rom.
go into hboot -> fastboot USB-> run command dos -> fastboot cwm-4.0.1.4-shooter.IMG -> flash the 2.17 firmware-> enjoy.
I had to S-off with Juopunutbear, then re-run that root/flash to get past the bootloops.
Sent from my Shooter using xda app-developers app
Unfortunately I have tried that and it still is not working.
My only suggestion would be to try it a few times, other then that, its above my head.
Sent from my shooter using xda app-developers app
rookiemistake said:
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
Click to expand...
Click to collapse
Have you tried one of the ruu exe files that you run from your computer? If you are trying to go stock, you should be able to relock the bootloader and run the ruu and that's it.
Sent from my ICS 3VO with Tapatalk 2
First of all I want to thank everyone that has been attempting to assist me with my problem. I have tried to relock since I am on htcdev unlock and then run an ruu force via my computer. I get an installation aborted error when trying to flash pg86img via recovery. I don't know what else to say.
You can't flash a bootloader zip from recovery. You have to flash it from hboot. Also make sure the zip is named correctly "PG86IMG.zip" without the quotes. Also make sure the zip is on the root of your sd as in not in any folders. Once you've named the zip correctly and placed it correctly then power off the phone. Hold down the volume down button and tap the power button. You should boot into the bootloader wait until the phone recognizes the zip and follow the on screen instructions. Hopefully this helps.
#Root-Hack_Mod*Always\=LTE
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
rookiemistake said:
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
Click to expand...
Click to collapse
To get the ota release (if it ever comes ) I do believe you will need to be locked and running the existing gingerbread rom. While I am not positive, I think the system uses the props file to determine if an update is applicable, and it will likely not recognize the teamgenesis rom version as being upgradeable.
Now I will likely get flames for saying this, but if you want to put the meanrom v2.4 of ICS on the phone, it can be done with s-on, you just need to follow the correct process. I ran that rom for a while, and it is very stock like, stable, and has a few enhancements that you will not find on a non-rooted stock rom. I never found anything wrong or not working with that rom.
To get it to load, first I downloaded flashimagegui from market, put the meanrom zip file on the sd card and made sure I had a recovery that I could get into. I am using TWRP v2.1.1, lots of folks talk about others like ext4, and I am only going to say use whichever you like, after all it is your phone.
Then with the phone unlocked via the htc method, I started the flashimage app, and browsed to the meanrom file. It extracted the kernel and flashed it. Once that was done, with clear cache buttons selected, rebooted to recovery, and used the install menu selection of TWRP to again flash the same rom file. Once it flashed the file, selected clear cache and dalvik just to be safe, selected reboot system, and it worked great.
Have a great weekend.
So, apparently I am still doing something wrong. I have put the pg86img on the root, relocked to the bootloader, and let it run it's course. However, it will get through with reading it and stops and does not finish anything with loading the system information. I have also tried to run the ruu via usb connection. I keep running into a c++ issue saying runtime error. I have wiped everything and thankfully I did make a backup of the rom and other information that I was runing so I can currently fall back on that.
I am on hboot 1.5, 2.17, and teamgenesis ICS rom for evo 3d.
Apparently there have been rumors that Sprint has finally released the ICS OTA, not that it really matters anymore, but I have run into a few interesting glitches, such as WIFI not staying connected while asleep or disconnecting.
If I have to I am willing to pay to do a netmeeing with someone in order to be able to fix this.
Sorry if it sounds like I am getting frustrated, but I have tried every walkthrough that I have found and have not had any luck with any of them.
Please help.
I forgot to say I am s-on
Let me start off by saying that I'm a complete idiot and wasn't being very careful.
I have several problems with my Rezound right now and I'll try to be clear and concise. My internal SD card won't mount in the recovery menu, nor HBOOT, therefore I cannot flash PH98img.zip in HBOOT. My external SD will mount, but I'm not sure if the PH98img.zip will work from the external SD because it doesn't show up in HBOOT. My HBOOT reads as follows:
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.10.00000
eMMC-boot
OCT 5 2011,21:18:48
And also, here's a weird thing: My phone will show up in adb devices only when the phone is off or when I'm in the Recovery menu. My phone won't appear in adb devices when I'm in HBOOT menu. I'm running ClockworkMod Recovery v6.0.2.3.
I have tried using a few different ROMs to no avail. I think my main problem as of now is that I cannot access my internal SD card. Before I install a ROM I wipe everything I can think to wipe, cache, dalvik cache, factory reset. Some of the ROMs have the Aroma installer where it asks if I want to wipe on those and I say yes every time. I cannot start my phone because I'm stuck on HTC white screen whenever I try to boot the phone. I've tried using the Old_Firmware_Patch.zip and the GB Firmware Patch.zip. I have had no luck so far. Again, I'm sorry that I'm not exactly sure what I'm doing and I need a bit of help. Thank you and I appreciate any help that you can give.
Additional Information
Prior to this complete failure in my phone I was using an early leak of ICS, one of Newts ROMs. His ROM didn't support 4G and had trouble with a few other things including stock wifi settings. Every time I tried to go to wifi settings the "com.settings.htc" or some such process would crash. So I wanted to update to a newer ICS ROM that hopefully supported 4G and didn't have problems with wifi settings. I thought it would be as simple as loading a ROM onto the external SD and loading it from recovery, but it wasn't that easy. Because I'm S-ON I apparently missed a few steps and forgot that I have to flash PH98img.zip. But now that I cannot access my internal SD card, I cannot flash PH98img.zip as far as I know.
First thing you want to do is get off of Clockwork Mod recovery. It doesn't play well with the Rezound. Go grab Amon Ra and flash v3.16.
Secondly, you can flash a PH98IMG file off the external sd, providing you can read it of course.
I think you are still on GB firmware based on your hboot, not completely sure about that. But it's def an old hboot.
So actually, I would run the RUU and update all your firmware, don't bother flashing Amon Ra first, do that after the RUU. Find it here:
http://androidfiles.org/ruu/?dir=Vigor
Top one, 3.14.605.12. Then after you run that, you can check for and accept the latest OTA that came out a couple weeks ago and then you'll be up to date with the official updates.
You'll need to relock the phone before running the RUU
fastboot oem lock
And save everything you need from the phone first since this will wipe everything and get you back to factory stock.
Then to run the RUU attach the phone to your pc and double click on the exe RUU file. It will do it's thing. Or you can use the following commands in fastboot to get it going:
fastboot oem rebootRUU
fastboot flash zip NameOfZip.zip
Make sure you let it go all the way through. I ran the global RUU and the screen went black for a while then it goes back to finishing up, so if that happens just let it keep going. I think you end up in bootloader when it's done, and it'll ask you if you want to reboot. You should go ahead and boot up and make sure it's working okay.
After you run the RUU you will need to unlock again. Then flash Amon Ra, flash superSU for root (though I think you can just get root via Amon Ra again now) and make a nandroid of stock so you can always go back to this when you run into trouble, then flash a custom ROM if you choose.
That should sort everything out since like I said, it'll be a clean start and you'll get everything updated.
Oh, and the PH98IMG.zip file you have to flash because of being s-on is the kernel for the ROM you are flashing. So know that each PH98IMG.zip file is not the same as the other, the ROM makes the one you need using the kernel that is specifically for that ROM. So you'll either need to pull it out of the ROM and flash via fastboot, download the separate PH98IMG file if there is one in the ROM's thread, or the ROM may make one during the flash and leave the PH98IMG file on your SD card in which case you go to bootloader and accept the update, which will be the kernel.
If you don't flash the kernel then the phone won't boot, it'll just get stuck.
One last thing, I would grab CleanWipe from the Dev section and use that for wiping whenever you change ROMs. It'll really get the job done.
Back to stock now
You, feralicious, are a beautiful person for replying so detailed lol. I got my phone to start up gladly. I just now read your post. Earlier I got it working by following a thread which basically said exactly what you said: relock using fastboot oem lock and then do the lastest RUU. It was a thing of beauty. I as so lost prior to that.
It's good to know that each PH98IMG.zip is different per rom. I had no idea. I'm going to stay stock for a while. It's just nice to finally see that 4g up on the top of my phone after having dealt with 3g only for like 6 months. I'll definitely come back to this site if I have an trouble while attempting to re-root the phone. Thanks so much for your excellent reply.
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
simonsgray said:
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
Click to expand...
Click to collapse
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Thanks man. sig is a little out of date, i havent' needed xda as much since jumping to nexus. TWRP and i didn't do the s-off stuff. it says it needs a stock rom and i just havea spinning cyanogen mod. i will try install the 4ext and see if that changes the results.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
simonsgray said:
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
Click to expand...
Click to collapse
If you want to flash back to the stock ICS image you need to first relock your bootloader. When you relock it will say relocked when in hboot. The procedure is to place the image in the root of your external SD card and select from hboot. It should recognize and flash back to stock, however everything other than your external SD gets wiped in the process. So you need to make sure you have a good recent backup. Also, you remember when you first HTC dev unlocked they sent you an image to push to unlock? Well, I hope you saved it, because you'll need it again to re-unlock the bootloader after flashing the firmware image, but before attaining s-off.
However, if you were already on your carrier's latest ICS firmware before you started flashing different ROMs, you probably already have their latest radio. If you install the latest 4ext and enable smart flash, you'll probably succeed in installing any of the source built ROMs (ASOP, CM, PACman, evervolv) without s-off, because ROMs built from the source don't have the CID flag in their binaries.
If you still decide to go back and attain s-off the procedure is as follows: 1) relock your bootloader 2) flash the latest stock firmware for the carrier that sold your device. 3) Unlock your bootloader again using the image and commands you previously did to HTC dev unlock the first time, 4) get s-off using the wire-trick 5) flash the hacked hboot (and another radio if you desire, but not required for most ROMs) 6) super CID to remove all carrier locked file / partition limitations and protections 7) Flash your preferred recovery. Because you're now s-off you can use TWRP, CWM, or 4ext since the protected partitions are no longer an issue. 8) Flash any ROM you want provided it's based on ICS or later (below won't work because the radio is incompatible).
Edit: One other thing to note before starting any of this make sure your battery is fully charged. Also, the first time you boot after installing CM or any ASOP based ROM it can take quite some time to go through the process before you get to the login screen. For me it usually takes a little under 10 mins. It may at first appear to be a little sluggish until the rom settles, usually about 10-15 mins.
I hope this helps
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