Related
So I now have Clockwork Recovery 3.x and running cm7. I tried straight flashing the latest T-Mobile ROM (1.22?).
It fails right away. I am not really wanting to unroot or turn S-ON. Is it failing because I am using cwr 3.x and need to flash the 2.x recovery? I thought I read somewhere that to flash a Froyo rom 2.x is needed, and 3.x is only for the GB roms...
Also, if and when I do successfully flash the stock rom, will this remove root/s-ff or the other unlocks gfree performed? And the linked thread for flashing the OTA rom instructs to rename to update.zip... is that only for the non-rooted folks?
And lastly, since the clockwork recovery 2.x has been out there for a while, thread info is quite old. Can i simply reflash the 2.x recovery using ROM Manager?
Thanks in advance.
The 1.22 is just an update zip it is not a complete PC10IMG stock rom that is why it is failing, make sure you have s-off via gfree before flashing a stock PC10IMG other wise it will turn your s-on, there is only a 1.19 complete PC10IMG rom out right now, this is pre OTA.
Yes you should be able to use rom manager to reflash older CWM recovery
Sent from my HTC Vision
fermunky said:
So I now have Clockwork Recovery 3.x and running cm7. I tried straight flashing the latest T-Mobile ROM (1.22?).
It fails right away. I am not really wanting to unroot or turn S-ON. Is it failing because I am using cwr 3.x and need to flash the 2.x recovery? I thought I read somewhere that to flash a Froyo rom 2.x is needed, and 3.x is only for the GB roms...
Also, if and when I do successfully flash the stock rom, will this remove root/s-ff or the other unlocks gfree performed? And the linked thread for flashing the OTA rom instructs to rename to update.zip... is that only for the non-rooted folks?
And lastly, since the clockwork recovery 2.x has been out there for a while, thread info is quite old. Can i simply reflash the 2.x recovery using ROM Manager?
Thanks in advance.
Click to expand...
Click to collapse
Ill try to help a fellow tampa area guy out
the stock rom your trying to flash isnt going to work with CWM 3.XX your need to replace it with 2.XX. flashing a stock rom will not remove root or s-off.
when i go back and forth using CWM from 3.xx to 2.xx i follow these directions... there super easy... and i have never had a problem with it.
1. Install clockworkmod from market.
2. Flash Clockworkmod recovery from Rom Manager.
3. Navigate to clockworkmod/download/koush.tandtgaming.com/recoveries (or where ever your recovery was downloaded to. This can be done in File Manager, Astro, or Androzip.
4. Mine was "recovery-clockwork-2.5.1.3-vision.img". Rename it to "recovery-clockwork-2.5.1.3-visionXXX.img" or something obviously different.
5. Download clockworkmod 3.0 from hereish:
http://forum.xda-developers.com/showthread.php?t=893933
6. Move your recovery.img to clockworkmod/download/koush.tandtgaming.com/recoveries and name it recovery-clockwork-2.5.1.3-vision.img
7. Go into ROM Manager and Flash Clockworkmod recovery, it will say its still 2.5.1.3 when your done. Reboot into recovery and you'll be welcomed by a new orange 3.0
Click to expand...
Click to collapse
of course you can just reverse these directions to go back to 2.xx...
you shouldnt have to change the stock rom name to "update.zip" just flash the zip like you would any other rom through CWM...
Thanks WarBird! I think I'll just flash the recovery images using flash_image. Can you confirm what joemn said though? If I want to flash the stock ROM, do I need both the PC whatever and the ota?
Also
make sure you have s-off via gfree before flashing a stock PC10IMG other wise it will turn your s-on
Click to expand...
Click to collapse
This doesn't make sense. Based on this, you're saying that if I have s-on, flashing pc10img will... turn s-on...?
fermunky said:
Thanks WarBird! I think I'll just flash the recovery images using flash_image. Can you confirm what joemn said though? If I want to flash the stock ROM, do I need both the PC whatever and the ota?
Also
This doesn't make sense. Based on this, you're saying that if I have s-on, flashing pc10img will... turn s-on...?
Click to expand...
Click to collapse
You are misunderstanding me, what I am saying is if you rooted via the old method and don't have radio s-off via gfree flashing a stock PC10IMG will turn your s back on, and what I told you about the 1.22 update zip is correct.
Sent from my HTC Vision
Ah I see. Since I was late to the G2 game, I did use gfree to get s-off as mentioned in my op. Thanks!
Hi,
I have a rooted/s-off htc desire. And i'm just experimenting with it. I'm trying to just get the rom (so no radio, hboot and recovery) out of a ruu rom.zip. So i can flash it with RA-Desire recovery.
I don't care about the fact that there are already nice custom roms out there (normaly i use gingervillain). I just want to try this to experiment with the stock rom,
Eh? Might nit be understanding this correctly but here goes. The hboot, recovery and radio are not in a rom, any rom for that matter. They are all seperate. That is why you flash them. If your just wanting AMONRA recovery, just flash it in recovery. And please don't mess with the hboot. If you **** that up then you brick your phone
Sent from my HTC Desire
A stock PB99IMG.zip has all the above in it so assuming the OP is wanting to take them out of a stock ROM and flash the rest. Doubt this would work as the ZIP file isn't designed to run in the same way as a custom ROM update-script
Eddy understands what I want. I think it is possible. I red the following on de alpharev website.
Will my phone stay S-OFF forever?
Yes and no. As soon as you decide to flash a stock RUU that has a HBOOT update in it, this hacked HBOOT will be overwritten.
You do have the option to remove the HBOOT update from the rom.zip inside the RUU. Since your phone no longer checks signatures, you could easily do that.
Click to expand...
Click to collapse
Yeah that would suggest that you could flash the ZIP with the files removed - the issue is that the ROM.zip (PB99IMG) isn't a ZIP file in the true sense so you'd need 7-Zip to extract the files and then re-zip them without the HBOOT, radio, etc
I'd assume you'd flash it as you would a normal PB99IMG file and not like a custom ROM but I don't know
Actually my idea was to just flash it from recovery (if possible).
It wouldn't work as you don't flash .IMG files in recovery
ok, thanx. But how do they do it with that stock rooted roms?
if i flash a new hboot like cm7 what are the requirements before doing that?..i actually am on rcmix 1.2 bravo hboot and i want cm7 version..
S-off
orsidoc said:
if i flash a new hboot like cm7 what are the requirements before doing that?..i actually am on rcmix 1.2 bravo hboot and i want cm7 version..
Click to expand...
Click to collapse
Sent from my HTC Desire using XDA App
i am s-off..but i have to download the cm7 version of the rom or not before flashing the img?
go to alpharev.nl and download the hboot file you need (remember to check md5)
then 2 methods: either put PB99IMG(something like that) file on root of sdcard and boot phone into bootloader, it will find the file and ask you to confirm it
or flash .img file through fastboot
then flash ROM designed to run on diffrent hboot
just downloaded the rom then used android flasher it went smooth...
Hello,
sry for this noob question but I have searched this problem on the forum and it seems like that nobody else is having ´the same problem.
Since I've rooted I have been wanting to flash a custom rom on my phone. For my particular ROM the developer suggests to flash the latest Radio. I've tried to install it through the recovery ("install zip from sdcard") but my recovery just won't install it.
rooted using revolutionary. Of course s-offed. My Phone is the PVT4 SLCD with erase size of 20000
My Recovery is ClockWorkMod 5.0.2.0 (That from rom manager)
Thanks
CCuber
CCuber said:
Hello,
sry for this noob question but I have searched this problem on the forum and it seems like that nobody else is having ´the same problem.
Since I've rooted I have been wanting to flash a custom rom on my phone. For my particular ROM the developer suggests to flash the latest Radio. I've tried to install it through the recovery ("install zip from sdcard") but my recovery just won't install it.
rooted using revolutionary. Of course s-offed. My Phone is the PVT4 SLCD with erase size of 20000
My Recovery is ClockWorkMod 5.0.2.0 (That from rom manager)
Thanks
CCuber
Click to expand...
Click to collapse
You wrote everything except the most important part - bootloader information.
But I reckon what you'll write so probably the /cache is to small to flash radio using a .zip leaving you only with fastboot flash method.
Hi, I don't know which hboot you are using. But I think you have got one with small cache partition (5M size). If it's true, you should flash radio by fastboot.
Actually I have the stock hboot. I think the recovery is the problem. So CWM says the installation aborted. Amend scripting is no longer supported. I should switch to edify scripting. How can I do that?
for what its worth, my advice if you have a recent radio (one where second string of numbers starts with _5) then leave it and try it with the rom. If you do need to change it I'd recommend learning to use fastboot to flash as it takes other software layers out the equation.
Also, get rid of Rom Manager - you don't need it and it causes problems with Desire - and since you're s-off install 4Ext Recovery.
CCuber said:
Actually I have the stock hboot. I think the recovery is the problem. So CWM says the installation aborted. Amend scripting is no longer supported. I should switch to edify scripting. How can I do that?
Click to expand...
Click to collapse
I had the same problem with stock hboot. I only have a Mac and Ubuntu machines, and I haven't found an easy step by step tutorial to use fastboot (only for Windows) so I'd rather do it with just the phone itself. So is it still possible to flash radio without using a computer?
On the other hand I used to have the latest radio before unrooting my phone for warranty reasons, and I can't see any difference in performance...
Here is a German Tutorial (sorry for that):
http://www.brutzelstube.de/2012/edify-scriptfehler-flashen-eines-radio-images-mittels-adb/
I had the same issue, did it with this tutorial and it worked good for me!
Short translation:
#1: Boot in the Fastboot menu (start with power+ volume down then fastboot)
#2: Install ADB http://www.brutzelstube.de/wp-content/uploads/2010/12/adb-tools.zip
#2: Extract the "radio.img" from the Radio .zip file and copy it to the ADB folder
#3: Connect your mobilphone with the Computer, wait a few seconds then navigate with cmd to the ADB folder and put the following line in: "fastboot flash radio radio.img"
#4: restart your phone
It worked for me!!!
Easier way would be Android Flasher:
http://forum.xda-developers.com/showthread.php?t=794638
For an english guide for ADB / Fastboot check my sig.
I just flashed the latest radio from recovery. I know this is not the safest way to do it. In rom manager I flashed the Clockworkmod 2.5.0.7 version. And then from recovery I just installed the latest radio. Worked for me.
anzianzi said:
I just flashed the latest radio from recovery. I know this is not the safest way to do it. In rom manager I flashed the Clockworkmod 2.5.0.7 version. And then from recovery I just installed the latest radio. Worked for me.
Click to expand...
Click to collapse
Addition: One can only use recovery to flash Radio, if the Hboot has at least 35 MB space for /cache-partition.
Sent from my HTC Desire using XDA
anzianzi said:
I just flashed the latest radio from recovery. I know this is not the safest way to do it. In rom manager I flashed the Clockworkmod 2.5.0.7 version. And then from recovery I just installed the latest radio. Worked for me.
Click to expand...
Click to collapse
Can you or any one else provide me the link to download Clockworkmod 2.5.X.X. I cant find it anywhere.
I have 32.49.00.32U_5.11.05.27 baseband version and Stock hboot.
Do i need to upgrade it to install sense 3.5 roms? Are there any risk in flashing radio? As every sense 3.5 rom freezes occasionally on my desire.
Thanks
any 3.5 sense rom is too heavy for desire, you can speed it up if you use cm7r2 hboot... flashing radio is risky operation if radio flash will fail it is not recoverable in most cases, htc will replace motherboard if you can provide proper reason under warranty... you don't need to update radio to flash rom but battery life can be affected by radio...
to flash radio without ruu you must be s-off
Usama Ahmed said:
Can you or any one else provide me the link to download Clockworkmod 2.5.X.X. I cant find it anywhere.
I have 32.49.00.32U_5.11.05.27 baseband version and Stock hboot.
Do i need to upgrade it to install sense 3.5 roms? Are there any risk in flashing radio? As every sense 3.5 rom freezes occasionally on my desire.
Thanks
Click to expand...
Click to collapse
You can flash older versions of clockworkmod recoveries in rom manager, just search from market/play store. That's what I did.
rom manager is not recommended, rather to flash it manually via fastboot but you must be s-off
why do you want old version of cwm?...
see bortak's guide om top of q&a section
kotag82 said:
rom manager is not recommended, rather to flash it manually via fastboot but you must be s-off
why do you want old version of cwm?...
see bortak's guide om top of q&a section
Click to expand...
Click to collapse
I want old version of cwm so i can flash radio. Because i cant flash radio on latest cwm or 4ext recovery.
I just wanted to ask will latest radio solve my problem of sense 3.5 rom freezing randomly?
Usama Ahmed said:
I want old version of cwm so i can flash radio. Because i cant flash radio on latest cwm or 4ext recovery.
I just wanted to ask will latest radio solve my problem of sense 3.5 rom freezing randomly?
Click to expand...
Click to collapse
No changing radio gives no guarantee that your freezes are gone. For instance your sd card could be the problem with freezing software ( sd card to slow )
sent from the Netherlands....
MarcelHofs said:
No changing radio gives no guarantee that your freezes are gone. For instance your sd card could be the problem with freezing software ( sd card to slow )
sent from the Netherlands....
Click to expand...
Click to collapse
I have Kingston 16gb class 4 card. Is it slow?
Other information PVT4, S-off, hboot 0.93, Stock hboot.
Usama Ahmed said:
I have Kingston 16gb class 4 card. Is it slow?
Other information PVT4, S-off, hboot 0.93, Stock hboot.
Click to expand...
Click to collapse
Class 6 HS cards are faster, could be the problem. I had freezes with a 8 gig class 4 card. I bought another card and my freezes are gone. I am NOT saying that a faster card is the solution but it might help. Try testing it with a friends card that's faster
sent from the Netherlands....
MarcelHofs said:
Class 6 HS cards are faster, could be the problem. I had freezes with a 8 gig class 4 card. I bought another card and my freezes are gone. I am NOT saying that a faster card is the solution but it might help. Try testing it with a friends card that's faster
sent from the Netherlands....
Click to expand...
Click to collapse
Ok bro i will see what i can do. Thanks for your help.
I've been using the HTC Desire HD for a long time, and I was wondering if things I've learnt with that phone are still relevant.
With the DHD, if the phone was S-ON (but with an unlocked bootloader and a custom recovery), whenever flashing a new ROM it was necessary to extract the boot.img file from the zip and flash it manually by using: fastboot flash boot boot.img.
That was because a custom recovery couldn't flash a custom kernel while the device was S-ON.
Is that also the case with an M8 device that stays S-ON?
Or is a custom recovery now able to write any custom kernel regardless of being S-ON/S-OFF?
Thanks!
Indeed
s-on = Flash kernel via fastboot
s-off = kernel is flashed via rom/recovery
Thank you for the quick reply!
quick question..if what you say is true..if s on flash kernal in fastboot..if s off just flash normally threw recovery...why in captins thread with his GPE rom..says s off users must flash boot.img in fastboot?...i was about to try his rom ,before i got to that part..i am s off and ive never had to flash a boot.img threw fastboot before flashing the rom....next question..do i need to unpack the rom zip ,extract the boot.img flash it in fastboot..then repack the zip and flash again in recovery?ive never had to do this..i thought i would see a boot.img zip as a seperate download wouldve been lot easier...ive never unpacked a zip to extract a boot.img before...so i had to back out for now..can someone plz give me step by step directions how to flash captins GPE rom..really appreciate it..and i know im in the correct section to ask such a newbie question..thanks in advance
is this still true with modern Marshmallow/Nougat ROMs (and their associated firmware updates)? the device is unlocked and S-ON?
example: I just flashed ViperROM v6.1 on Tmobile M8 with v6.2 firmware and separate flash of boot.img NOT required.
In fact, I validated theory by doing the traditional procedure and result as phone that did not boot.
traditional procedure: flash ROM via TWRP and reboot direct into bootloader and fastboot. then finalize by manual flash of boot.img via fastboot. boot.img pulled from root directory of ROM zip.
any insight would be appreciated. -GA
Mr Hofs said:
Indeed
s-on = Flash kernel via fastboot
s-off = kernel is flashed via rom/recovery
Click to expand...
Click to collapse
gads1 said:
is this still true with modern Marshmallow/Nougat ROMs (and their associated firmware updates)? the device is unlocked and S-ON?
example: I just flashed ViperROM v6.1 on Tmobile M8 with v6.2 firmware and separate flash of boot.img NOT required.
In fact, I validated theory by doing the traditional procedure and result as phone that did not boot.
traditional procedure: flash ROM via TWRP and reboot direct into bootloader and fastboot. then finalize by manual flash of boot.img via fastboot. boot.img pulled from root directory of ROM zip.
Click to expand...
Click to collapse
No need to flash boot.img separately using fastboot (with s-on).
But it shouldn't hurt anything, either. It's just a redundant step, as you are just flashing the same boot.img that TWRP is already installing.
Try it again, without flashing boot.img separately. But I have a feeling something else is causing no boot. Make sure you are using current TWRP (version 3.1) with default TWRP wipe (cache, dalvik and data), or try another ROM.