Related
So I had some "help" from a well meaning visiting nephew who was playing with my phone and noticed that I had an update available and decided that I should really have the latest software on my phone...so now I am on 2.17 with hboot 1.5, locked bootloader and all with no custom recovery BUT I am still s-off. I have a NAND backup that is not to old that I did with CWM, but how do I get to that to install it?
I have been looking for several hours and cant seem to find a solution...maybe I'm just searching under the wrong keywords...nevertheless HELP!!!!!!!
I am in the process of downloading a 1.13 stock ruu. Will that work or is there a quicker way to get this done?
I would prefer to avoid HTC unlock if I can, and my understanding is that with s-off, I should be able to.
Thanks for helping bail my ass out guys and girls!
(I thought about it, but no, I didnt beat the kid...his intentions were good...at least they better have been...)
Have you tried flashing a cwm recovery? I think I read someone had the same problem.seens your s-off you should still be able to flash a recovery, and after that's done then you can be able to wipe and flash anything you want, and you well even be able to downgrade your hboot.
Nope, it wont let me flash a recovery through fastboot...access denied (phone shows locked). I cant install it with "flash image gui" because i dont have root.
I know it should be an easy fix because I have the all important s-off...I just cant find how to do it.
taminrob said:
So I had some "help" from a well meaning visiting nephew who was playing with my phone and noticed that I had an update available and decided that I should really have the latest software on my phone...so now I am on 2.17 with hboot 1.5, locked bootloader and all with no custom recovery BUT I am still s-off. I have a NAND backup that is not to old that I did with CWM, but how do I get to that to install it?
I have been looking for several hours and cant seem to find a solution...maybe I'm just searching under the wrong keywords...nevertheless HELP!!!!!!!
I am in the process of downloading a 1.13 stock ruu. Will that work or is there a quicker way to get this done?
I would prefer to avoid HTC unlock if I can, and my understanding is that with s-off, I should be able to.
Thanks for helping bail my ass out guys and girls!
(I thought about it, but no, I didnt beat the kid...his intentions were good...at least they better have been...)
Click to expand...
Click to collapse
S-Off just means that the security is off, and you're able to write onto the boot partition of the phone when flashing a ROM, in one shot. If your Hboot = 1.50, you may have to unlock your bootloader via HTCDEV method, your phone gets wiped. Try HTC SuperTool, maybe it will work, since you're S-Off.
http://forum.xda-developers.com/showthread.php?p=21538250
Follow my post and the links in there should get you back to 1.4
Sent from my HTC Evo 3D using Tapatalk
Thank you, that got me back in where I needed to be! Was able to load CWM again and restored from my back up...now all I need to do is make since of all the conflicting instructions to do this update so the icon goes away...found some that are fairly clear, but the links are broken now that the upload sites are blacklisted.
Either way, just glad to have my hboot back where it belongs.
Hi! Running into some trouble. I would have posted this in the development area but I am not allowed to until I have 10 posts. I went through the process of unlocking then rooting using amon ra, but thats the last thing I did right. I was in recovery and made the mistake of thinking I could restore an old nandriod, which happened to be from my bionic. Well now I am stuck at the HTC white screen and cannot get anywhere. I downloaded the all on one kit and successfully booted into recovery using it, but even after doing a full wipe I cannot get anywhere. I am new to HTC and with a moto device I would have just sbf'd back but I dont know what to do at this point. Any and all help would be appreciated, thanks!
What did you try to restore and dis you install re install the kernel for it
sent from ics land
I tried to restore a nandroid backup which is what I am guess caused the issue. I am new to HTC and its process, so I am unaware what you are asking by kernal. I unlocked the phone and installed amon ra 3.14 and that was it. Once it was installed I went into recovery and tried the backup, which I am now regretting. Sorry, completely new to this process, thank you very much for your patients
Just download a new ROM in the development thread.
Okay, thought that may fix so I have been downloading one, just hasnt finished yet. Once completed, do I just move it to my SD card, pop it into my phone, boot into recovery and load the zip? Never done it before, just want to fact check.
Is it an ICS or GB ROM?
It is one of the ICS roms....sigh, lol, guess that complicates things. Well, since I have already gone this far, should I go ahead and just relock, load new leaked RUU then unlock and load ICS rom OR forget that, download a GB rom and just flash it?
No you're good with downloading an ICS ROM. Did you also download the PH98IMG that goes with it?
I downloaded earlier when trying to root with Amon Ra and and got a message that it was out of date, so I thought it PH98IMG was Amon Ra from what I read in the forums and downloaded the new 3.14 and loaded that. Was I mistaken? If so, what is PH98IMG? There is a wealth of knowledge on this site, just really hard to piece it all together, lol, thank you again for your patience.
I was confused at first on what it was, too. I may not be 100% on this but it's essentially the kernel for the ROM. Since we don't have s-off we have to manually flash kernels in HBOOT instead of just flashing them in recovery.
What you wanna do is rename whatever the kernel is to just PH98IMG(it usually has it already in the name). Delete whatever comes after it. So it will say PH98IMG.zip afterwards. Then what you'll wanna do is put it in the root of your sd card. That means don't place it in any folder.
Flash the ROM first in recovery then go into HBOOT and it will read the PH98IMG.zip and prompt whether you want to update or not. Hit volume UP to update and then reboot and you should be good.
Also, make sure you delete the PH98IMG.zip from your SD card before going back into HBOOT again because it will keep asking you if you want to update it. This will prevent you from getting into Recovery from the Bootloader and if you ever get stuck in a bootloop, like you just did. The only way to get back into recovery would be to remove SD card and connect it to another phone or Computer and delete it that way.
Woah, excellent, just want I needed, some simple breakdown of everything. Once last favor, I searched for the PH98IMG(cant remember where i got it earlier) and there are alot of items named the same thing. Can you point me in the right direction of the one I need?
Which ROM are you trying to flash?
CleanRom 4.0
Well, actually you will need to relock and download the RUU if you want to use that ROM.
ok, downloading the RUU now and have the Rom downloading as well, once they are finished I would relock, load the RUU, unlock then load the new Rom right?
Yes that is it. While running the RUU follow the directions from Scott to the T. He has them posted in the first post, or at least a link to his directions.
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
So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
Help... I have rooted my droid x2 in the past a couple of times, but this Rezound is something different and for some reason I just cannot get it. I really need some assistance. I have been reading all over androidcentral and xda-developers all day and night but It's just overwhelming or something has to go wrong. I tried Hasoon's kit, my device wasn't recognized... then I tried HTCdev website... that was successful, but then I locked it after unlocking it, and I figured out that I probably need it unlocked so I can flash a rom... It would just be easier if someone could chat with me on Skype or something and I'd really appreciate if someone could get me going again and maybe chat with me and give me step by step help. My username is mikeonabike11.
Thanks again,
Confused.
gs3noob said:
Help... I have rooted my droid x2 in the past a couple of times, but this Rezound is something different and for some reason I just cannot get it. I really need some assistance. I have been reading all over androidcentral and xda-developers all day and night but It's just overwhelming or something has to go wrong. I tried Hasoon's kit, my device wasn't recognized... then I tried HTCdev website... that was successful, but then I locked it after unlocking it, and I figured out that I probably need it unlocked so I can flash a rom... It would just be easier if someone could chat with me on Skype or something and I'd really appreciate if someone could get me going again and maybe chat with me and give me step by step help. My username is mikeonabike11.
Thanks again,
Confused.
Click to expand...
Click to collapse
unlock it again. then install amon ra. and then flash a rom. really easy. its over complicated when you read a bunch of forums and try to figure it out yourself
cslingerland said:
unlock it again. then install amon ra. and then flash a rom. really easy. its over complicated when you read a bunch of forums and try to figure it out yourself
Click to expand...
Click to collapse
alright. i got it unlocked. i cant figure out the amon ra part...
gs3noob said:
alright. i got it unlocked. i cant figure out the amon ra part...
Click to expand...
Click to collapse
1) Grab the PH98IMG.zip from the Amon-Ra thread
2) Stick it on the root of your sdcard
3) Reboot into bootloader
4) Press power - the bootloader will scan for an update package, you should then be prompted to hit volume up to install it. If nothing is found, you didn't place the PH98IMG.zip in the right place.
5) Hit volume up to install
6) Reboot when asked
7) Remove the PH98IMG.zip asap.
You can now reboot back into the bootloader then pick recovery from the menu to get into Amon-Ra. Make sure you back up your existing rom before wiping and installing a new one.
One thing you need to know is that a PH98IMG file can be many things. It is only the name of a file that your phone looks for to use when booted into hboot. So it can be a kernel, an entire RUU (OS), a custom recovery or ROM... basically anything. It just means that item was packed into a PH98IMG file in order to run automatically off your SD card when the phone boots. So you need to know what the PH98IMG file is that you are using or you might flash something you don't want that can possibly cause your phone to not work properly.
You'd be doing yourself a favor by learning to use fastboot for things first so you understand the process more before using the "automated" way of doing everything using a PH98IMG file.
Also, as soon as you have Amon Ra installed and have rooted the phone, make a nandroid of your phone at stock and save that in case you need it if something goes wrong flashing the ROM, as mjones mentioned above. It's much easier to restore the nandroid than getting the RUU to get back to stock.
Another thing to think about is whether or not you want to go s-off or not. It unlocks the security of the phone making it both easier to flash ROMs by letting the kernel flash immediately afterwards by itself and also easier to brick the phone by doing something by mistake. You don't have to s-off, you'll just have to manually flash the kernel after flashing a ROM if you don't. If you don't flash ROMs often you might want to read up about it more before you s-off. I rarely change ROMs and I'm still s-on and it doesn't affect me negatively at all.
Also, there's a "Help" thread in the General section, I think it's a sticky, and some guys have posted their gtalks so that people can hit them up for help. Maybe one of those guys can walk you through it. I would be willing to do it but I'm not as experienced as they are and haven't rooted/flashed anything for a year now.
cslingerland is helping me with mine thanks for the help!
feralicious said:
One thing you need to know is that a PH98IMG file can be many things. It is only the name of a file that your phone looks for to use when booted into hboot. So it can be a kernel, an entire RUU (OS), a custom recovery or ROM... basically anything. It just means that item was packed into a PH98IMG file in order to run automatically off your SD card when the phone boots. So you need to know what the PH98IMG file is that you are using or you might flash something you don't want that can possibly cause your phone to not work properly.
You'd be doing yourself a favor by learning to use fastboot for things first so you understand the process more before using the "automated" way of doing everything using a PH98IMG file.
Also, as soon as you have Amon Ra installed and have rooted the phone, make a nandroid of your phone at stock and save that in case you need it if something goes wrong flashing the ROM, as mjones mentioned above. It's much easier to restore the nandroid than getting the RUU to get back to stock.
Another thing to think about is whether or not you want to go s-off or not. It unlocks the security of the phone making it both easier to flash ROMs by letting the kernel flash immediately afterwards by itself and also easier to brick the phone by doing something by mistake. You don't have to s-off, you'll just have to manually flash the kernel after flashing a ROM if you don't. If you don't flash ROMs often you might want to read up about it more before you s-off. I rarely change ROMs and I'm still s-on and it doesn't affect me negatively at all.
Also, there's a "Help" thread in the General section, I think it's a sticky, and some guys have posted their gtalks so that people can hit them up for help. Maybe one of those guys can walk you through it. I would be willing to do it but I'm not as experienced as they are and haven't rooted/flashed anything for a year now.
Click to expand...
Click to collapse