Related
Back from Moto-land with Rezound. I've flashed several ROMS and one I would like to flash now says that I must firs be on the leaked 3.11.605.22 firmware.
I thought that when I flashed a rom and it rebooted into bootloader to install the PH98IMG.zip file, that it was installing the necessary firmware. I'm confused.
How do I get to the necessary Leaked firmware. I've searched and googled, but everything I find, indicates that I cannot install the leak, because I have already used the HTC unlock tool. Again, confused
I appreciate your help!
ruu isn't a Tom that loads the kernel afterwards. the leak is flashed all at once which appears to be how kernels are flashed. flashing the leak requires the lock then it flashes everything together but remember it wipes all data with exception of external sd
Followup Q1: So is it possible to get to the RUU 3.11.605.22 firmware, WITHOUT re-locking and flashing the leak? (not concerned at all about full wipe, do it with each rom)
Q2: If I do have to re-lock and then flash the leak, do I first have to return to a 100% stock state (ie, restore all the bloat-ware and such)? (if you've ever had a Bionic you know what I'm talking about)
http://forum.xda-developers.com/showthread.php?p=23700622
Sent from my ADR6425LVW using Tapatalk
nukeboyt said:
Followup Q1: So is it possible to get to the RUU 3.11.605.22 firmware, WITHOUT re-locking and flashing the leak? (not concerned at all about full wipe, do it with each rom)
Q2: If I do have to re-lock and then flash the leak, do I first have to return to a 100% stock state (ie, restore all the bloat-ware and such)? (if you've ever had a Bionic you know what I'm talking about)
Click to expand...
Click to collapse
Originally Posted by JoelZ9614 View Post
Here are the instructions...
Download...
rename the zip to PH98IMG.zip
put on your sdcard
reboot to bootloader
fastboot oem lock
reboot to bootloader again
flash.
reboot to bootloader
[if it says security warning and tampered at the top flash again..after continue to next step]
fastboot flash unlocktoken Unlock_code.bin [of course only if u have ur original Unlock_code.bin if not do the whole htc thing again]
reboot......
A little confused. Android Police says you have to be fully stock with a locked bootloader to install 605.22. According to this, I don't have to be stock, I just have to relock it, and be aware that the full RUU install with radios will wipe my entire phone except external SD? (I wouldn't ask this except that it directly contradicts the AP post.)
And do we have the ability to re-root the resulting ICS installation?
And there's no other way to apply just the radios and the pre-rooted (Non-RUU?) version?
Does the pre-rooted version also do a full wipe?
cpurick said:
A little confused. Android Police says you have to be fully stock with a locked bootloader to install 605.22. According to this, I don't have to be stock, I just have to relock it, and be aware that the full RUU install with radios will wipe my entire phone except external SD? (I wouldn't ask this except that it directly contradicts the AP post.)
And do we have the ability to re-root the resulting ICS installation?
And there's no other way to apply just the radios and the pre-rooted (Non-RUU?) version?
Does the pre-rooted version also do a full wipe?
Click to expand...
Click to collapse
So far no other way to get the new radios , sounds like the only reason the OTA leak worked was the way it was packaged. This new leak isn't packaged the same way so you would have to relock and run the RUU to get the new radios.
Personally, all I did was reflash stock recovery before hand, but I had to run it a few times to get it to work fully and at one point I just relocked with amon recovery installed and ran it and it worked just fine. It wipes recovery as part of the installation and installs the updated stock recovery.
andybones said:
Originally Posted by JoelZ9614 View Post
Here are the instructions...
Download...
rename the zip to PH98IMG.zip
put on your sdcard
reboot to bootloader
fastboot oem lock
reboot to bootloader again
flash.
reboot to bootloader
[if it says security warning and tampered at the top flash again..after continue to next step]
fastboot flash unlocktoken Unlock_code.bin [of course only if u have ur original Unlock_code.bin if not do the whole htc thing again]
reboot......
Click to expand...
Click to collapse
Sorry for the questions, but when I do all of this, will I still have the Amon Ra recovery, or does this return to the stock recovery (which I assume it does)?
When the PH file is flashed in recovery it will overwrite whatever recovery you had flashed previously and leave you with stock everything...including recovery.
Sent from my ADR6425LVW
I was able to upgrade to the new ROM and then re-unlock my phone. But when I put Amon Ra in SD folder as PH98IMG.zip and reboot to the loader, I am never prompted to install it. Furthermore, attempts to get into recovery result in a green circular icon followed by a red triangle with exclamation point.
I tried all sorts of resets and reboots. Right now I have a green recovery option, but no working recovery. The top line says "UNLOCKED".
I've tried Amon Ra 3.13 and 3.14.
Download this file.
Place it in the same folder that you setup for the HTCdev unlock.
Rename it to "recovery."
Go to the command prompt and type in this command: cd c:\nameoffolder (mine is c:\Android for example)
Boot into Hboot
Select Fastboot
Connect to PC
Then type this exactly : fastboot flash recovery recovery.img
That should get you loaded with Amon Ra.
http://forum.xda-developers.com/showthread.php?p=19205213
Installation instructions are in the OP.
What you see now when you select recovery in hboot is what is considered stock recovery
Sent from my ADR6425LVW using Tapatalk
EmerikL said:
Download this file.
Place it in the same folder that you setup for the HTCdev unlock.
Rename it to "recovery."
Go to the command prompt and type in this command: cd c:\nameoffolder (mine is c:\Android for example)
Boot into Hboot
Select Fastboot
Connect to PC
Then type this exactly : fastboot flash recovery recovery.img
That should get you loaded with Amon Ra.
Click to expand...
Click to collapse
Thank you. I had already figured it out, and this is exactly what the problem was. Last time I flashed with a PH98IMG version of recovery, but this latest version that I have is for Fastboot. Thanks!
Never thought it would be such a relief to see the "TAMPERED" warning, lol.
All is good!
ZIP to fix mainver problems
http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4
i am goin through a really big problem! i was trying to permanently root my phone! but during the revolutionary step it says hboot 1.40.0000 or 1.30.0000 it says 1.40.0000 and it also says it is not supported yet! please help me!
Hi,
you dont need S-OFF for evrything. If you cannot S-OFF,
still you can flash roms, and do most of the things without a problem,
Only thing is you cannot just install custom roms using the recovery menu.
You need to download and installed Android Framework tools and fastboot in your PC to fire ADB Dos commands to your phone via USB to flash the updates.
Let me know.
theRocker_007 said:
Hi,
you dont need S-OFF for evrything. If you cannot S-OFF,
still you can flash roms, and do most of the things without a problem,
Only thing is you cannot just install custom roms using the recovery menu.
You need to download and installed Android Framework tools and fastboot in your PC to fire ADB Dos commands to your phone via USB to flash the updates.
Let me know.
Click to expand...
Click to collapse
You can flash ROMs through recovery on S-on too and it will work fine as long as the new ROM contains the same kernel as your current kernel. And if it contains another kernel use flash Image GUI app or fastboot command to flash tha kernel.
Provided your bootoader is unlocked via www.htcdev.com
mnomaanw said:
You can flash ROMs through recovery on S-on too and it will work fine as long as the new ROM contains the same kernel as your current kernel. And if it contains another kernel use flash Image GUI app or fastboot command to flash tha kernel.
Provided your bootoader is unlocked via www.htcdev.com
Click to expand...
Click to collapse
Most of the time, ROMs does not have the same kernal,
So most of the users who are s-on and new to flashing get stuck on boot loops. Other thing is flash image gui app is a paid application
So best way is to use fastboot commands to flash the kernal after installing the ROM zip file
Cheers..
You could update to hboot 1.50, use the HTCDev unlock and use the Wiretrick to get s-off
Hi!
I've updated to honeycomb 3.2.1 and everything worked fine. Then I decided to unlock bootloader using HTCDev site and root it.
Everything went ok and flyer was working until I decided to flash custom ROM (Cool 3D Honey and later LeeDroid).
After following the install guide device is stuck in a boot loop. It's booting to the "desktop" screen and then reboots over and over again.
Same happened with LeeDroid rom.
How can I get it working again? No matter which rom - just to make it work.
I can only boot into fastboot/recovery now.
hboot 1.11
S-ON
rooted
Please help
You need to flash the boot.img using fastboot. This needs to be done everytime you flash a custom ROM. Otherwise, you have no kernel (or kernel is mismatched for the ROM you are on). This is one of the downsides to having S-On versus S-Off (and with you hboot version, there is no S-on, as you likely already know).
To flash boot.img using fastboot:
- On your computer, use a zip program (Winzip, WinRAR, etc.) to open the ROM zip.
- Extract boot.img, and put it in the same folder that you have fastboot.exe (which you should alreay have if you are bootloader unlocked).
- Connect the Flyer to your computer via USB, put phone into fastboot mode
- Open command prompt on computer
- Change directory in command prompt to the folder where you have fastboot.exe
- Use following command to flash boot.img:
fastboot flash boot boot.img
- Reboot phone after flash is complete, and it should boot properly
Also, make sure you are trying to flash on HC, ICS, or JB based ROMs. GB based custom ROMs require GB hboot. Since you are only bootloader unlocked (not S-Off) I don't believe you can downgrade hboot (at least not easily). So I think you are stuck on HC, ICS, and JB ROMs (no GB ones).
redpoint73 said:
You need to flash the boot.img using fastboot. This needs to be done everytime you flash a custom ROM. Otherwise, you have no kernel (or kernel is mismatched for the ROM you are on). This is one of the downsides to having S-On versus S-Off (and with you hboot version, there is no S-on, as you likely already know).
Click to expand...
Click to collapse
Thanks for your effort.
I've followed the procedure you described above but still no luck for Cool 3D honey or LeeDroid (HC) ROMS. However, I was able to flash Virtuous ROM yesterday and Flyer is working. Only bug I noticed for now is that I can only power it down through fastboot > powerdown because standard/software power down option is not working (probably ROM bug or something).
BTW, should I follow this guide to downgrade to GB? Can I expect this to work?
http://forum.xda-developers.com/showthread.php?t=1428104
redpoint73 said:
You need to flash the boot.img using fastboot. This needs to be done everytime you flash a custom ROM. Otherwise, you have no kernel (or kernel is mismatched for the ROM you are on). This is one of the downsides to having S-On versus S-Off (and with you hboot version, there is no S-on, as you likely already know).
To flash boot.img using fastboot:
- On your computer, use a zip program (Winzip, WinRAR, etc.) to open the ROM zip.
- Extract boot.img, and put it in the same folder that you have fastboot.exe (which you should alreay have if you are bootloader unlocked).
- Connect the Flyer to your computer via USB, put phone into fastboot mode
- Open command prompt on computer
- Change directory in command prompt to the folder where you have fastboot.exe
- Use following command to flash boot.img:
fastboot flash boot boot.img
- Reboot phone after flash is complete, and it should boot properly
Also, make sure you are trying to flash on HC, ICS, or JB based ROMs. GB based custom ROMs require GB hboot. Since you are only bootloader unlocked (not S-Off) I don't believe you can downgrade hboot (at least not easily). So I think you are stuck on HC, ICS, and JB ROMs (no GB ones).
Click to expand...
Click to collapse
thank you very much
shinichiwtbe said:
Thanks for your effort.
BTW, should I follow this guide to downgrade to GB? Can I expect this to work?
http://forum.xda-developers.com/showthread.php?t=1428104
Click to expand...
Click to collapse
I think this is what you want: http://forum.xda-developers.com/showthread.php?t=2070140
The linked RUU thread in the guide is obsolete (dead/deleted download links). But the method seems to be valid, if you can find the RUU for your version.
i have same scenario with the you dude
HC
s-on
1.11 hboot
i want to flash this Cool3dhoney, but the thread said that i must have proper radios and hboot, dunno what's the proper radio and hboot
RadarZgin said:
i have same scenario with the you dude
HC
s-on
1.11 hboot
i want to flash this Cool3dhoney, but the thread said that i must have proper radios and hboot, dunno what's the proper radio and hboot
Click to expand...
Click to collapse
Honeycomb ROM requires a HC hboot. So if you are already on HC, you are already on one of the correct hboot versions. I don't think that radio will make much difference, and the one you are on is probably fine..
Since you are S-on, you must manually extract boot.img and flash from fastboot as I instructed in post #2 above. That is probably the reason why you can't boot. The kernel will not flash in recovery with S-on. So your kernel is currently mismatched with the ROM.
redpoint73 said:
Honeycomb ROM requires a HC hboot. So if you are already on HC, you are already on one of the correct hboot versions. I don't think that radio will make much difference, and the one you are on is probably fine..
Since you are S-on, you must manually extract boot.img and flash from fastboot as I instructed in post #2 above. That is probably the reason why you can't boot. The kernel will not flash in recovery with S-on. So your kernel is currently mismatched with the ROM.
Click to expand...
Click to collapse
thank you sir for the reply, i already studied everything, flashing and flashing boot.img manually, thanks! now ill flash this rom
Okay so i bought my rezound recently then I unlocked it Rooted it and tried installing a rom Im on S on with the unlocked bootloader
im using the amon ra recovery
i wipe then i install the rom and then i reboot the phone but it always gets stuck on the bootanimation
can someone give me the detailed steps to install this rom please
http://themikmik.com/showthread.php...nse-4-5-ICS-4-0-4-(9-29-12)-Stable-and-smooth
thank you
Sounds like you need to flash the kernel. When s-on you need to flash the kernel separately after flashing the ROM.
Some ROMs make the PH98IMG of the kernel for you and if so it will be on the root of your external card. If you boot into bootloader it should ask you if you want to take the update, say yes, that's the kernel. You should be able to boot after that.
If there's no PH98IMG left for you, pull the boot.img from the ROM and flash in fastboot.
fastboot flash boot boot.img
If it's not the kernel issue then post back.
Followed your link to the ROM. Looks like you can just download the kernel from the thread. From the install directions:
**Installation of boot.img**
-download boot.img
-copy to pc to your fastboot directory
-cd to the directory
-type these commands
-"fastboot flash boot boot.img"
That is for if you are s-on, which you are. I'm sure this will get you going.
Yes !! it worked thank you alot :laugh:
just one more question do i have to do the same thing every time i install a new rom?
Yes. Since you are s-on you must flash the kernel that goes with the ROM after you flash the ROM.
If you s-off you won't have to but it makes it easier to brick the phone. I've also read where some people have lost the use of their usb ports trying to s-off. I'm s-on and it doesn't bother me to flash the kernel separately. The ROM I'm using puts it on the sd card and puts the phone in hboot so all I have to do is accept the update. Easy peasy.
I have experience with HTC EVO phones, but the Rezound is new to me. it's root and s-off are different, and I've gotten myself stuck.
Before I make things worse, I want to ask for some help. I tried flashing the newest CM ROM, while s-on, and now can't get past the HTC boot screen. I can get into the bootloader, and into recovery, but I'm not sure what to flash to get the phone bootable again. I can't mount the USB from TWRP (well I can, but can't see the SD card in either windows on Linux), so I have to take the card, but it into another phone to copy files to it, then put it back into this phone.
So, here is where I am now, how should I proceed?
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
eMMC-boot
TWRP recovery works fine, but I'm not sure what to install from here to fix me up. I have 3 RUU files, (1.02.605.6, 2.01.605.11 and 3.14.605.12 ICS) but can't get the USB connection to work so I need to flash from recovery. I could try connecting to a windows 7 machine (I'm running windows 8 and Ubuntu 13.10)
My goal is to get back to something stock, so I can s-off, so I can install a recent ICS build and use a Verizon phone with the Telcel GSM network in Mexico.
All help is much appreciated!!
JustinChase said:
I have experience with HTC EVO phones, but the Rezound is new to me. it's root and s-off are different, and I've gotten myself stuck.
Before I make things worse, I want to ask for some help. I tried flashing the newest CM ROM, while s-on, and now can't get past the HTC boot screen. I can get into the bootloader, and into recovery, but I'm not sure what to flash to get the phone bootable again. I can't mount the USB from TWRP (well I can, but can't see the SD card in either windows on Linux), so I have to take the card, but it into another phone to copy files to it, then put it back into this phone.
So, here is where I am now, how should I proceed?
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
eMMC-boot
TWRP recovery works fine, but I'm not sure what to install from here to fix me up. I have 3 RUU files, (1.02.605.6, 2.01.605.11 and 3.14.605.12 ICS) but can't get the USB connection to work so I need to flash from recovery. I could try connecting to a windows 7 machine (I'm running windows 8 and Ubuntu 13.10)
My goal is to get back to something stock, so I can s-off, so I can install a recent ICS build and use a Verizon phone with the Telcel GSM network in Mexico.
All help is much appreciated!!
Click to expand...
Click to collapse
the reason you are stuck is because you have to fastboot flash the boot.img exctracted from that rom via fastboot usb in the bootloader...you must also have an unlocked bootloader to do this....if you need further instructions ill be glad to help.....as for the RUU's you need to be s-off and have a relocked bootloader for them to work or you can brick the device
REV3NT3CH said:
the reason you are stuck is because you have to fastboot flash the boot.img exctracted from that rom via fastboot usb in the bootloader...you must also have an unlocked bootloader to do this....if you need further instructions ill be glad to help.....as for the RUU's you need to be s-off and have a relocked bootloader for them to work or you can brick the device
Click to expand...
Click to collapse
Thanks. Considering my goal for now is to get back to a stock ROM so I can get s-off, would it be better to rename an RUU to PH98IMG.zip, then relock my bootloader, then flash the PH98IMG from the bootloader, to get me to a stock/updated/known ROM all in one shot, or do I have to figure out how to flash the boot.img file from the CM ROM, then flash the RUU after that's done. Either way, I need to relock the bootloader to flash or install an RUU, correct?
My Windows 8 computer just seems to have given up on reading/identifying the phone while the phone is in recovery, and I've spent too many hours trying to fix that stupid problem, that I'm almost ready to dump windows 8, and install 7 on this new laptop. I have another w7 laptop in the house that I could use, but if there's a simple HTC drivers for windows 8 fix that actually works, I'd probably rather keep windows 8 and do it all with this machine.
thanks again.
JustinChase said:
Thanks. Considering my goal for now is to get back to a stock ROM so I can get s-off, would it be better to rename an RUU to PH98IMG.zip, then relock my bootloader, then flash the PH98IMG from the bootloader, to get me to a stock/updated/known ROM all in one shot, or do I have to figure out how to flash the boot.img file from the CM ROM, then flash the RUU after that's done. Either way, I need to relock the bootloader to flash or install an RUU, correct?
My Windows 8 computer just seems to have given up on reading/identifying the phone while the phone is in recovery, and I've spent too many hours trying to fix that stupid problem, that I'm almost ready to dump windows 8, and install 7 on this new laptop. I have another w7 laptop in the house that I could use, but if there's a simple HTC drivers for windows 8 fix that actually works, I'd probably rather keep windows 8 and do it all with this machine.
thanks again.
Click to expand...
Click to collapse
ruu is an exe file... ota is a .zip.....your best option to do s-off is install amon ra recovery and install a stock based rom found in Rezound Android Developement....if you follow my s-off guide here in the Rezound [email protected] youll find links to everything you will need.....windows 8 requires special drivers for anything to work....i suggest downgrading to windows 7 if you can as 8 has way too many compatibility issues with anything that requires legacy stuff
REV3NT3CH said:
ruu is an exe file... ota is a .zip.....your best option to do s-off is install amon ra recovery and install a stock based rom found in Rezound Android Developement....if you follow my s-off guide here in the Rezound [email protected] youll find links to everything you will need.....windows 8 requires special drivers for anything to work....i suggest downgrading to windows 7 if you can as 8 has way too many compatibility issues with anything that requires legacy stuff
Click to expand...
Click to collapse
Yeah, I saw someone suggest to rename the RUU.exe file to PH98IMG.zip file to flash it with the bootloader. it this would work, it seems the easiest thing to do from here, but you suggest that it might brick the phone, so I'm not ready to try that yet.
Yes, I was trying to follow your "how to" guide, and you say to flash a stock ROM, and point to one as an example (Global OTA RED-1.0) ROM, but that ROM points to another thread on how to flash ROM with s-on, and it's not particularly clear what one should do, so I'm not sure how to proceed from here, exactly. Here are the steps that are unclear to me...
-adb reboot bootloader
-fastboot erase cache
-fastboot oem lock
-fastboot oem rebootRUU (is this the exact text to type, or do they mean -fastboot oem Global_OTA_RED-v1.0.zip or do they mean -fastboot oem RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe or something else entirely?)
-fastboot flash zip firmware.zip (where am I getting "firmware.zip or is this another example of me needing to replace firmware.zip with something else, and if so, what?)
(it will fail for with pre-update flush again immediately error). So do it again -->
-fastboot flash zip firmware.zip
(it will finish)
when its done:
-fastboot reboot-bootloader
-fastboot flash unlocktoken Unlock_code.bin
-pull the battery and replace.
Once this is done, I think I could then proceed to the s-off process.
[Stupid windows 8 drivers - I will have to install Windows 7 on another partition now ]
JustinChase said:
Yeah, I saw someone suggest to rename the RUU.exe file to PH98IMG.zip file to flash it with the bootloader. it this would work, it seems the easiest thing to do from here, but you suggest that it might brick the phone, so I'm not ready to try that yet.
Yes, I was trying to follow your "how to" guide, and you say to flash a stock ROM, and point to one as an example (Global OTA RED-1.0) ROM, but that ROM points to another thread on how to flash ROM with s-on, and it's not particularly clear what one should do, so I'm not sure how to proceed from here, exactly. Here are the steps that are unclear to me...
-adb reboot bootloader
-fastboot erase cache
-fastboot oem lock
-fastboot oem rebootRUU (is this the exact text to type, or do they mean -fastboot oem Global_OTA_RED-v1.0.zip or do they mean -fastboot oem RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe or something else entirely?)
-fastboot flash zip firmware.zip (where am I getting "firmware.zip or is this another example of me needing to replace firmware.zip with something else, and if so, what?)
(it will fail for with pre-update flush again immediately error). So do it again -->
-fastboot flash zip firmware.zip
(it will finish)
when its done:
-fastboot reboot-bootloader
-fastboot flash unlocktoken Unlock_code.bin
-pull the battery and replace.
Once this is done, I think I could then proceed to the s-off process.
[Stupid windows 8 drivers - I will have to install Windows 7 on another partition now ]
Click to expand...
Click to collapse
no an ruu.exe you run in windows and is a program....a ph98img is an ota update file or something custom made like a recovery and when flashing a rom you have to extract that particular rom with lets say 7 zip...pull the boot.img file out of it and place it in the fastboot folder on your pc.. boot into bootloader on the phone and select the fastboot option then plug it into pc....once the phone says fastboot usb in command prompt direct it using cd C:\yourfastbootdirectory then once you are in fastboot folder in command prompt typt fastboot flash boot boot.img....you only do this after flashing a rom in custom recovery
Edit: btw this is your only option to have a usable rom while s-on including getting to a stock rom again....running the ruu.exe while s-on will brick you....a ph98img.zip with a version of android older than what you are on will brick also or give you a main version is older error
REV3NT3CH said:
no an ruu.exe you run in windows and is a program....a ph98img is an ota update file or something custom made like a recovery and when flashing a rom you have to extract that particular rom with lets say 7 zip...pull the boot.img file out of it and place it in the fastboot folder on your pc.. boot into bootloader on the phone and select the fastboot option then plug it into pc....once the phone says fastboot usb in command prompt direct it using cd C:\yourfastbootdirectory then once you are in fastboot folder in command prompt typt fastboot flash boot boot.img...you only do this after flashing a rom in custom recovery
Edit: btw this is your only option to have a usable rom while s-on including getting to a stock rom again....running the ruu.exe while s-on will brick you....a ph98img.zip with a version of android older than what you are on will brick also or give you a main version is older error
Click to expand...
Click to collapse
Thanks again. I thought it was weird to rename an RUU to the img file, which is why I asked before proceeding. So, since I flashed the CM ROM, I need to pull the boot.img from that same ROM, put it in the android SDK folder on my machine (which is now running Windows 7), then run the fasboot flash boot boot.img and then I should have a functioning phone again.
Then, do the s-off procedure, then I can flash the newest RUU to get everything updated/current, then I can run any ICS ROM from that point.
Sound about right?
Oh, I had to wipe the machine to install windows 7, so I no longer have Ubuntu installed for dual boot. The unlimited site says it only works with Ubuntu 32-bit, and doesn't work with Live USB. I don't want to install 32 bit Ubuntu (rather install 64 bit). What is the best method for s-off, considering these limitations?
thanks again for all your help!!
JustinChase said:
Thanks again. I thought it was weird to rename an RUU to the img file, which is why I asked before proceeding. So, since I flashed the CM ROM, I need to pull the boot.img from that same ROM, put it in the android SDK folder on my machine (which is now running Windows 7), then run the fasboot flash boot boot.img and then I should have a functioning phone again.
Then, do the s-off procedure, then I can flash the newest RUU to get everything updated/current, then I can run any ICS ROM from that point.
Sound about right?
Oh, I had to wipe the machine to install windows 7, so I no longer have Ubuntu installed for dual boot. The unlimited site says it only works with Ubuntu 32-bit, and doesn't work with Live USB. I don't want to install 32 bit Ubuntu (rather install 64 bit). What is the best method for s-off, considering these limitations?
thanks again for all your help!!
Click to expand...
Click to collapse
ive done it on ubuntu 12.04 64 bit....those on higher versions have had to instal the 32bit libs on 64bit which in the comments in my s-off guide a guy posted on how to do just that
REV3NT3CH said:
ive done it on ubuntu 12.04 64 bit....those on higher versions have had to instal the 32bit libs on 64bit which in the comments in my s-off guide a guy posted on how to do just that
Click to expand...
Click to collapse
Worked great!!! I'm now s-off.
Now I just need to figure out how to get updated to the most recent radios and firmware, then pick a new ROM.
Thanks for all your help!
JustinChase said:
Worked great!!! I'm now s-off.
Now I just need to figure out how to get updated to the most recent radios and firmware, then pick a new ROM.
Thanks for all your help!
Click to expand...
Click to collapse
in my downgrade/upgrade guide the ph98img ota's are the updates to most recent hboot and radios...