Related
I'm struggling with all the terminology and methods with flashing. Basically I just wanted root, so I read several different guides and got a rooted status and managed to install the Amon Ra recovery. However my bootloader (also called HBOOT - is that correct?) shows tampered / unlocked now. Basically, I want to flash back to the most current build and try again.
Would the link on the Android Police forums to download RUU 4.03.605.2 be latest Verizon build as if it were fresh out of the box?
I checked on the wiki, but didn't see anything for the Rezound there.
Also, to use this utility, I relock my bootloader using HTCDev and then move this zipped file to my sd card and reboot to the bootloader either using adb or the power + volume down, correct? It will see the zip file and begin flashing or do I run an executable from my PC with the phone connected? I'm not S-Off because I figured that is way above my head at this point.
I appreciate any help anyone can offer.
The tampered just means you have a custom recovery like Amon Ra installed.
Sent from my ADR6425LVW using xda app-developers app
oatlord said:
I'm struggling with all the terminology and methods with flashing. Basically I just wanted root, so I read several different guides and got a rooted status and managed to install the Amon Ra recovery. However my bootloader (also called HBOOT - is that correct?) shows tampered / unlocked now. Basically, I want to flash back to the most current build and try again.
Would the link on the Android Police forums to download RUU 4.03.605.2 be latest Verizon build as if it were fresh out of the box?
I checked on the wiki, but didn't see anything for the Rezound there.
Also, to use this utility, I relock my bootloader using HTCDev and then move this zipped file to my sd card and reboot to the bootloader either using adb or the power + volume down, correct? It will see the zip file and begin flashing or do I run an executable from my PC with the phone connected? I'm not S-Off because I figured that is way above my head at this point.
I appreciate any help anyone can offer.
Click to expand...
Click to collapse
4.03.605..2 is the latest vzw build.
jbh00jh said:
4.03.605..2 is the latest vzw build.
Click to expand...
Click to collapse
If I want to load that RUU, do I have to relock my bootloader? Will I be able to load the file from the Android Police forum without being S-OFF since I've rooted and loaded a recovery?
oatlord said:
If I want to load that RUU, do I have to relock my bootloader? Will I be able to load the file from the Android Police forum without being S-OFF since I've rooted and loaded a recovery?
Click to expand...
Click to collapse
Having S-OFF negates the need to relock your bootloader.
You should be able to flash the "RUU" zip file with your phone in its current condition.
If you do some research in this section in the S-OFF threads, you'll get some good info about not re locking after s-off.
Re-locking is only necessary if you don't have s-off.
Sent from my ADR6425LVW using Tapatalk 2
to reinstall the RUU, first make sure you have fastboot on your PC and your phone is in the fastboot menu of the bootloader and connected to your PC. It should say "fastboot USB". (If you don't have the HTC drivers installed, download HTC Sync 3.0 and that should install it. I haven't gotten it to work on Windows 8 so if you use Windows 8 use these drivers)
Open a command prompt, change the directory to where your fastboot.exe is (example: cd c:\fastboot_directory). Type in 'fastboot oem lock'. Your phone will restart, then boot up. Turn it off, reboot to the bootloader and make sure it says *RELOCKED* on the top. Then, go back to fastboot and in your cmd window, type in 'fastboot oem rebootRUU'. Your phone will reboot and show a black screen with a grey HTC logo. Copy the RUU (doesn't matter if it's named PH98IMG.zip or something else) into the same folder as fastboot.exe and type in 'fastboot flash zip ruu_zip_name.zip' (obviously replacing ruu_zip_name.zip with the zip's actual name). The terminal will start sending the zip and details will be displayed on your computer screen. Your phone will also have a progress bar. Once the terminal on your computer says it's finished, you can reboot your phone.
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Yes, you can use the above method fine. However, going S-Off is very easy. It seems like a daunting task, but if you read the directions thoroughly it is very easy. I used the .5 version of Juopunutbear and it worked without a hitch. You are already unlocked and rooted, so if you S-Off, you won't have to do it all over again. From there you can flash the RUU, flash a FLASHABLE version of AR 3.15, then reflash any rom that you want. You will only get the benefit from global with roms that are built aroung the .2 base, but you will get updated radios. I haven't honestly noticed much of a difference with the new radios though.
layneja said:
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Click to expand...
Click to collapse
Flash stock recovery here's a link http://www.mediafire.com/?wb21d2gdurui2c6 then lock bootloader. (Fastboot OEM lock)
After locking bootloader(cuz your s-on) rename the ruu you downloaded from android police To PH98IMG put on your sd return sd phone boot into bootloader run update, if it stops and powers off mid update remove battery and start it again, It flashed the hboot first then you gotta go back In And finish the update.
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
---------- Post added at 11:41 AM ---------- Previous post was at 10:59 AM ----------
layneja said:
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Click to expand...
Click to collapse
Also to avoid any problems do a factory reset in hboot after update is installed. Being that we're s-on when we re-unlock it does it for us but I've heard some people are having problems after the ruu if they didn't FDR while on stock recovery.. just a heads up
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
famouscollin said:
Flash stock recovery here's a link (removed cause I'm too new) then lock bootloader. (Fastboot OEM lock)
After locking bootloader(cuz your s-on) rename the ruu you downloaded from android police To PH98IMG put on your sd return sd phone boot into bootloader run update, if it stops and powers off mid update remove battery and start it again, It flashed the hboot first then you gotta go back In And finish the update.
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
---------- Post added at 11:41 AM ---------- Previous post was at 10:59 AM ----------
Also to avoid any problems do a factory reset in hboot after update is installed. Being that we're s-on when we re-unlock it does it for us but I've heard some people are having problems after the ruu if they didn't FDR while on stock recovery.. just a heads up
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
Click to expand...
Click to collapse
Just to clarify: when you reboot using "adb reboot" or power + volume down, are you booting into the bootloader or hboot? I've read the guides but still a little confused there.
Also, what does the stock recovery do versus something like Amon Ra? Does the stock recovery allow for creating backups and what-not? Sorry to be a total noob here. I can bake cookies or something for you all for your help, hehe.
WookieFan said:
Having S-OFF negates the need to relock your bootloader.
You should be able to flash the "RUU" zip file with your phone in its current condition.
If you do some research in this section in the S-OFF threads, you'll get some good info about not re locking after s-off.
Re-locking is only necessary if you don't have s-off.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
if you're s-off you shouldn't have to unlock.
---------- Post added at 07:17 PM ---------- Previous post was at 07:11 PM ----------
oatlord said:
Just to clarify: when you reboot using "adb reboot" or power + volume down, are you booting into the bootloader or hboot? I've read the guides but still a little confused there.
Also, what does the stock recovery do versus something like Amon Ra? Does the stock recovery allow for creating backups and what-not? Sorry to be a total noob here. I can bake cookies or something for you all for your help, hehe.
Click to expand...
Click to collapse
The bootloader is the hboot. You power on holding vol down to get there.
The stock recovery does not allow you to create backups, or do much at all I'm pretty sure. That is why we have custom ones.
If i helped throw me a thanks
iamwalterwhite said:
Yes, you can use the above method fine. However, going S-Off is very easy. It seems like a daunting task, but if you read the directions thoroughly it is very easy. I used the .5 version of Juopunutbear and it worked without a hitch. You are already unlocked and rooted, so if you S-Off, you won't have to do it all over again. From there you can flash the RUU, flash a FLASHABLE version of AR 3.15, then reflash any rom that you want. You will only get the benefit from global with roms that are built aroung the .2 base, but you will get updated radios. I haven't honestly noticed much of a difference with the new radios though.
Click to expand...
Click to collapse
Do you mean flash the RUU in the bootloader and then the recovery also in bootloader? i only ask cause im at school and i forgot my microsd adapter so i cant rename the zips so that I can flash both of them from there, but if i can do it from recovery then im set
xxtsxx said:
Do you mean flash the RUU in the bootloader and then the recovery also in bootloader? i only ask cause im at school and i forgot my microsd adapter so i cant rename the zips so that I can flash both of them from there, but if i can do it from recovery then im set
Click to expand...
Click to collapse
Sorry that you never got an answer to this. Yes, you should flash both recovery (stock) and the RUU as PH98IMG zip files. Wait to start this process until you have a pc/sd card reader available. Trying this without those basic tools is going to make this a frustrating process for you.
Sent from my ADR6425LVW using Tapatalk 2
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.
Hey everyone,
So I have successfully HTC Unlocked my Rezound bootloader, installed Amon Ra, and then installed and booted the CM9 unofficial. Problem was that CM9 wasn't quite as cooperative as I'd hoped - it is unofficial, after all, and so I decided to abandon that in favor of Nils' Business ROM. Here's where I ran into issues.
I have tried everything in every order I can find online and think of, including Nils' writeup. So, for the life of me, I cannot get the leaked ICS RUU to boot (4.03.605.2 as listed in his instructions on XDA). Install runs fine every time I do it from the relocked (I checked) stock HBOOT, all steps included. Every time it reboots (and I've tried forcing it back into hboot to do the install a second time) it just goes to the white HTC screen and starts boot looping. Tried it a million ways, no go. Also worth noting - the stock recovery doesn't install properly, either. Some'fin is hinky, here.
So I've tried just "assuming" it went fine anyhow and then proceeding with the install for Nils' ROM and same deal, no go, although with one difference. With Nils' ROM, it does display the boot splash screen "Nils Business ROM" or what have you about 1 out of every 4 "boots" in the loop cycle, and then reboots again.
I think I am going to perform S-OFF tomorrow if I have the time, and then try it again using the S-OFF instructions, but I would sincerely appreciate any help from you all. Honestly, I'm at near wit's end with this device, and I don't want to be, I enjoy this chase too much, but I *really* want the reward at the end of it, lol.
Any help is deeply appreciated.
- Katie
Re: [Q]
I'm guessing because of the corrupted recovery, you have a bad download of the RUU. Try re downloading and check the md5 hash for a match. The ruu should reboot itself after the first pass and end up in bootloader again for the second pass.... If not then after the first pass just hold down power + vol down to get back to bootloader.
Hope this helps
Sent from my ADR6425LVW using xda app-developers app
Make sure that you have a booting ROM before you s-off. You will cause yourself all kinds of heartache if you don't.
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Snuzzo said:
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Click to expand...
Click to collapse
Hey, thanks. Yeah, the RUU does check out just fine against an MD5SUM.
nm.... just read your original post again and you say you did relock the phone. I was hoping it was something simple like that that was overlooked.
Carry on...
feralicious said:
Nothing to see here, folks, move along.
Click to expand...
Click to collapse
Right now, I cannot S-OFF because it requires a working stock image, and I'll be lucky to get anything more than CM9 unofficial working here.
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
feralicious said:
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
Click to expand...
Click to collapse
Well that's the trick. CM9 didn't work well enough to even be worth backing up. I'm trying to reinstall it again now just to see if I get there - and it looks like I will. Once I'm back up with that, I'm not sure where to go from there. The phone barely worked under CM9. Really hoping to get Nils' ROM on there, since it gives all the nice features of a stock device without the bloatware. Even if I never get S-OFF, I'll be perfectly happy with just Nils' software.
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
feralicious said:
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
Click to expand...
Click to collapse
I did try wiping everything first. No luck. I will try the CleanWipe tomorrow, because right now, whatever my issues are, I'm being prevented from solving them since I can't S-OFF and I can't even seem to get a working ROM to make the phone worth having! Ugh.
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Thank you, your magnanimity! Seriously, lol, you're gracing my thread just by being here. :victory:
feralicious said:
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Click to expand...
Click to collapse
Thanks for the clicky, Feralicious. Same results, unfortunately. I'm going to try doing the RUU flash of Nils' ROM instead. Do you guys know where I can get the ICS firmware by itself? I cannot be sure that it's actually flashed right, unfortunately.
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
I'll do that stuff and let you know. Thank you!
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
ncc74656m said:
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
Click to expand...
Click to collapse
My DNA said something about failing when I locked it. But it locked just fine.
Since it is failing.
fastboot oem rebootRUU
fastboot oem lock ----if unlocked
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Should work Maybe
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
Click to expand...
Click to collapse
Ok, so, this part including a factory reset got me to "HTC Quietly Brilliant" screen, but then it bootloops again. Tried factory resetting again to no avail. Trying the second part.
Flyhalf205 said:
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Click to expand...
Click to collapse
Same thing as before unfortunately. :/ Performed a factory reset afterwards to be safe - no go. Everything shows OK though in both this and the above install. *shrug*
Flyhalf205 said:
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
ncc74656m said:
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
Click to expand...
Click to collapse
I really wouldn't see why you would need a Sense rom to get s-off. I would imagine it would just need su and busybox installed. But nandroid then try a sense rom again. Make sure you flash the boot.img through fastboot
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.
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