Related
I was trying to flash defrost ROM but after the flash it just stucks at the HTC logo, I leaved it for about an half an hour but no difference. Then I restored my nandroid backup and it worked fine again. Then I tried flashing a few other Roms too, none of them work EXCEPT untouched and just-rooted sense ROMs. I tried both sense and non-sense based ROMs, same result. I've upgraded my radio once to which I think is the latest. I tried restoring an old nandroid backup which was native-htc 2.1 and flashing eclair there didn't help either. I ALWAYS did a full wipe before flashing.
It's an rooted amoled-desire.
What should I do?
Big thanks in advance, zlayaa
Sent from my HTC Desire using XDA App
try installing this rom its worked fine for me every time rom then radio then reboot.
http://forum.xda-developers.com/showthread.php?t=741661
What happens when a rom has finished installing (what does it say?) or does it not get that far?
Hello! Thanks for the tips, I first did a full wipe. Then I flashed DeLite through Recovery (Power + Rocker Down, then Recovery and Install from Zip in the black-green custom recovery screen). I got this output:
Installing: SCARD:FroyoDelite_1.1_Odexed.zip
Finding update package..
Opening update package..
Installing update..
Welcome to Froyo Delite 1.1!
Verifying current system..
Clearing /system..
Unpacking new files
Symlinks and permissions..
Installing busybox..
Patching boot image..
Install from sdcard complete
Click to expand...
Click to collapse
Then I flashed the radio file, got this output:
Installing SDCARD:Radio......
Finding update package..
Opening update package..
Installing update..
Extracting radio image..
Installation complete.
Reboot via menu to complete installation.
Install from sdcard complete.
Click to expand...
Click to collapse
After the flash I went back and hit restart, it completed the radio flashing and rebooted. Then it once again stuck at HTC logo for 20 minutes until I pulled the radio. I tried flashing OpenDesire with the latest Radio and the same result.
I am having the exact same problem. Have tried flashing many roms and radios while wiping before each flash and every one freezes at the white htc screen after reboot. Only thing that works is restoring my original nandroid backup. Any help would be appreciated!
bump
(how long time do you need to wait to be allowed to bump?)
try downloading rom manager from the market and try it that way, could be that your update.zip is screwed
I tried using the flash method in ROM Manager, no difference. I haven't renamed it to update.zip, I've always used flash zip file method in clockwork recovery. Does that make any difference?
Bump
Sent from my HTC Desire using XDA App
Hy all.
I'm experiencing the same kind of problem than yours, EXCEPT for ModacoCustomROMs : I successfully flashed MCR8 and then MCR9 ROM.
But, for any other Custom ROM, I get stuck in the HTC green logo screen, and never come to the animated boot screen, or, in some cases, I come to the animated boot screen, but enter in an infinite boot loop.
I discovered that I have two "bad blocks" in the /data partition, but do not know whether it could come from that (in recovery mode, I mount /data, and then, type the following command
Code:
adb shell dmesg|grep bad
and get the following message
Code:
[xxxxxxx]block 643 is bad
[xxxxxxx]block 727 is bad
I perhaps have also bad blocks in the boot partition, but do not know how to check ...
Hey! Thanks for the tip, I flashed the Modaco ROM and it worked fine! How do I check my system for the bad blocks?
I'm happy now though, I was mainly looking for a ROM which was de-odexed and had some simple mods. But it'd be interesting to know why this is happening!
EDIT: I missed that you described the commands, I'll try it and tell you the output
Sent from my HTC Desire using XDA App
I've now checked the phone with the command and I got no output, so I guess I don't have any bad blocks.
I've tried to flash MiUI but it failed too! I'd really like to get this to work so I'd appreciate all help, big as small; and because I'm fairly new to android so I'm not sure what info I should provide either, I understand that it can be very hard for you guys to debug this.
Thanks in advance. Zlayaa
Edit: I saw an option in ROM Manager, Fix permissions, and i tried it. After that I flashed miui and it worked!
Sent from my HTC Desire using XDA App
This might work for all of you
This is if you still want to run on Defrost.
WAIT, BEFORE YOU START, CREATE A GOLDCARD. IT IS VERY NECESSARY. THINGS WILL GO WRONG IF YOU DONT.
EDIT: YOU MUST BE ABLE TO BOOT GO TO THE BOOTLOADER MENU.
Firstly, download this file. http://dl.dropbox.com/u/13240777/Desire Downgrade.ZIP
Extract the files.
Run the win-down.bat file.
Follow on screen instructions.
After the process is completed, Head to the root of your SD card and check if there is a file named P99***IMG (FORGOT THE EXACT NAME BUT IT SHOULD BE SOMETHING LIKE THIS) there should be one.
Secondly, disconnect your phone and turn it off.
After that boot up your phone while pressing the volume down button and the power button.
The bootloader should be checking for files after awhile and once it found the file that is supposed to be in the root of your sd card, press the volume up button (NOT EXACTLY SURE, SHOULD BE THE ONE THAT SAYS YES AND CONTINUE)
It should be writing files to your phone. and replaces everything. E.G: HBOOT, RECOVERY,RADIO and such.
It should be writing files successfully and then it would ask you to reboot. Continue with the reboot and you should be having your Desire back to stock. Perfect.
PLEASE KEEP IN MIND THAT THERE ARE RISKS INVOLVED LIKE FAILURE OF WRITING TO THE HBOOT. PLEASE REMEMBER TO FOLLOW INSTRUCTIONS. MAINLY, DO NOT BLAME ME FOR ANYTHING THAT GOES WRONG.
FINALLY, YOU SHOULD BE READING EVERYTHING UP TO HERE AND THAT YOU MUST HAVE A GOLDCARD (A GOLD SD CARD)
Hope this helps you and please ask if you have further questions. PM me if the questions cannot be answered here. Good Luck
Big thanks! This seems to have fixed my problems!
I've tried and I've tried, and I've tried and I can't get the newest clockworkmod to flash so I can try to taste some gingerbread. I've looked a lot, and I've tried to use the "easy way" that's stickied at the top of this thread and I've tried to push through terminial as well but it tells me the image isn't found. So, please do not tell me to search and what not because more than half the time I do in fact search, considering I am an active member of this forum I know all about it. Idk if I'm naming the file right, or if I'm suppose to extract files from the zip or what not, but nothing seems to work. So help a brotha out, and tell me what YOU did to get it to flash with step by step, detailed if possible steps. I appreciate you taking the time to read, and possibly help. I know its annoying, but I would love you for ir
-PH.
Sent from my HTC Vision using XDA App
post the steps you took, perhaps someone can glean an operational error from that. my guess is you need to navigate to the proper directory or rename the file
I flashed it using terminal from phone and recovery on sd.
I have heard ppl getting issues with that image not found thing, some other files have to be copied to allow the flash_image command to work but cant remember where.
What might work,..... use rom manager to update your recovery if you havent used rom manager before. Then check where rom manager places the downloaded recovery. Then rename ur recovery v3 to the exact same name as the 2.5 and place in the relevent folder, then try to get rom manager to flash it, like tricking it.
This method was reported to work a while back.
Worth a bash?
If fail, drop me a pm, ill have a look for that flash_image binary stuff when i get home tonight pal.
Sent from my HTC Vision using XDA App
Have you tried this method?
http://forum.xda-developers.com/showthread.php?t=902493
The main plan I was trying to do was replace and trick rom manager into thinking it was the original but it is really 3.0. So I replace thr image and rename and flash clockwork and when I go into recovery and its a no go. Then when I try to flash it via terminal it says the image isn't found when I know it is on the root of my card. Do I need to unzip the file and take the imgage out and place it on the root of my sd card, or put the zip on my sdcard and try to flash it?(doing it via terminal). How do I need to rename the file? I've also read somewhere that I need to have the correct rom binary, is that correct? I'm running a virtuous sense rom right now. What does that mean?
Sent from my HTC Vision using XDA App
I was having similar problems with flash_image, and I managed to get 3.0.0.5 on there by:
1. Flashing back to stock and starting fresh (did this with a pc10img via bootloader)
2. Rooting via the gfree -f as on the wiki
3. Downloading CW Rom Manager from the market
4. flashing the 2.x recovery that comes with that
5. Use Rom manager to download and install Cyanogen 6.1.1 clearing data and cache
6. Use flash_image instructions linked above by raitchison to install CWR 3.0.0.5.
Probably the long way around, but helped me get a grasp of what all was going on with my phone, and gave me a clean slate to start with. Haven't upgraded to CM7 yet, but now I know I can when I'm ready.
I know it doesn't help you now, but...........
Just read a tweet from koush that he is going to be releasing the CWM Recovery 3.0.0.x officially very soon, he is just waiting on cyanogen to finish running some test with it, so for people having issues with flashing CWM recovery 3.0.0.x you should see some official support from koush real soon.
It actually does help because I can wait a little more for the convicence of flashing. Thank you sir.
Sent from my HTC Vision using XDA App
Have you been doing the method using advanced and "fastboot flash recovery.img"?
Sent from my T-Mobile G2 running Cyanogenmod.
ibemad1 said:
Have you been doing the method using advanced and "fastboot flash recovery.img"?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
That requires that you have the Engineering HBOOT
I got it to work just flashing the reovery through terminal. Turns out since I was using a sense before hand, and not stock of a cm 6.1.1 I didn't have the correct binary for the rom. So I flashed cm6.x.x and then flashed the newest cw3. Its all good.
Sent from my HTC Vision using XDA App
uhh.. all i had to do was change the name of the recovery.img (3.0.0) the exact same name as the one in ROM manager. reflash with rom manager and its done. Works everytime
there is also a "how to" on it. But if you know how to copy and paste when your SD card is mounted to computer its pretty simple
Spastic909 said:
uhh.. all i had to do was change the name of the recovery.img (3.0.0) the exact same name as the one in ROM manager. reflash with rom manager and its done. Works everytime
there is also a "how to" on it. But if you know how to copy and paste when your SD card is mounted to computer its pretty simple
Click to expand...
Click to collapse
+1, I don't even mount to my computer though. I do it all through Astro. Easy breezy.
that does work, but the only reason it wasnt working because i didnt have the correct rom binary because i was using virtuous sense.
CWM 3.0.0.5 is now supported by ROM Mnanger, so for all the people having problems flashing the new recovery, rom manager will do it for you.
Sent from my HTC Vision
Hi,
I have an htc desire with recovery RA_Desire 2.0 and radio 5.11.05.27.
I was trying to install the rom found in the post below.
http://forum.xda-developers.com/showthread.php?t=833310
I have the ext partitions, wipe everything i can wipe and then flash the zip file.
The flashing has no problems.
The rebooting has. In fact, it loops on the first white htc screen.
Did anybody encounter a similar problem?
More, i can't run the script attached in that post to unistall apps from the main rom.
Thanks a lot
Hi and welcome to xda,
I haven't been stuck in a boot loop myself, but from what I have heard you should either flash another rom, reflash the current or flash the stock rom, some people have reported that they had the problem if they had a swap partition on their sd card, that would be worth checking as well, hope this helps
Bootloops are a pain sometimes but they happen rarely or if you do something wrong. Just a simple flash and check that everything is setup fine (if your using something like A2SD) and flash. Should be ok by the time you reboot.
Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse
Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....
Shot you a PM.
Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse
Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk
motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse
Ive always been running CM roms since I got the phone nearly two years ago, but recently have been reading too many good things about ICS roms. My phone has been laggy as of late, and honestly after nearly 2 years, I wanna see and try something new. I've been reading some stuff about updating 4EXT or something like that. Can someone link me or explain in great details how i do this? What is it? And if I do that, will i still be able to run my old CM rom if i decide the ICS roms arent for me? I dont want to be unable to roll back.
Whats the best ICS roms out there right now?
Many thanks!
___________________
SOLVED AFTER A STEP BY STEP INSTALLATION WITH KB!! MANY THANKS
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
Ive always been running CM roms since I got the phone nearly two years ago, but recently have been reading too many good things about ICS roms. My phone has been laggy as of late, and honestly after nearly 2 years, I wanna see and try something new. I've been reading some stuff about updating 4EXT or something like that. Can someone link me or explain in great details how i do this? What is it? And if I do that, will i still be able to run my old CM rom if i decide the ICS roms arent for me? I dont want to be unable to roll back.
Whats the best ICS roms out there right now?
Many thanks!
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
Depends on your definition of best, personally I like EliteMod ICS (in my signature) but you may want to try out Andromadus Mimicry 1.3.0, it's pretty nice out of the box and has a graphical installer (aroma).
Just be aware that due to the fact that the Desire-Z/G2 does not have an official ICS release, that some things such as hardware drivers have their limits.
1) Camera drivers are not fully available, so the camera won't function as well as it would have on a GB rom.
2) No Wireless-N, also due to drivers, but Wifi-B/G are available.
and a number of other smaller issues which are mentioned varying on the roms, but the two above are the most common complaints, something to keep in mind before you start updating the thread about lack of it.
4EXT Recovery is just another recovery, like ClockworkMod is another recovery.
I personally prefer 4EXT Touch Recovery ( http://www.4ext.net/ has the app to install it ), but both ClockworkMod (what you may have now) and 4EXT can create backups, and restore your backups to the phone (just make sure you do a factory-reset/wipe cache, when you're flashing a brand new rom on, and when you wish to restore a backup.)
So i can flash ics roms with clock work mod and not use 4ext?
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
So i can flash ics roms with clock work mod and not use 4ext?
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
You can, they're both recoveries and will both apply a rom zip. I just find 4EXT to have quite a bit more features that pertain to ICS (i.e.: the ability to convert some of your partitions from the older ext3 filesystem to the ext4 filesystem which is better, but not all roms support it, most ICS roms do though), as well as the ability to do tar-based backups (compresses, smaller backup size), and the paid version of the app lets you configure a number of settings in 4EXT (much like the paid version of Rom Manager).
Just don't flash roms via the app, always do that from the actual recovery, or you risk causing problems.
Generally speaking: Reboot into recovery (you can do this from the power menu in CM7.2)
1) Perform a backup of your currently installed Rom to the SD card
2) (toggle USB storage and copy over the rom zip if you haven't already done so)
3) Perform a Factory Reset/Wipe and wipe cache
4) Goto Apply zip from SD Card and select the new ROM
5) Flash any additional zips you want on top, google apps, wifi calling, etc (note the thread for any specifics, for example Mimicry doesn't come with Google Apps so need to flash the ICS google apps if you want them, where as EliteMod includes a custom set of google apps already)
6) reboot and enjoy.
If you decide you don't like it, just repeat the above steps, just do a restore at #4 and reboot.
Both of the ones I mentioned (mimicry, elitemod) by no means require a swap partition or sd-ext partition, but you can partition the card via either clockworkmod or 4EXT, just skip the sd-ext2 option (since elitemod doesn't support a secondary one [and not much point either). And don't set a sd-ext size less than 1.5GB (no sense in making it smaller than your /data partition).
For both though, skipping an SD swap is advised, I only have SD swap on mine cuz no other rom I know of supports dataswap and I'd rather have my SD Card partitioned already to test out other roms than to re-do the SD Card each time (since you gota make sure to back up the content of the SD Card to the PC). 4EXT though will let you repartition the SD card without erasing the FAT32 partition, where as clockworkmod will always wipe the whole card before repartitioning (it's just easier to partition from scratch though).
Yeah the whole partition and swapping was the confusing part. But good to hear I don't have to do any of that. I did see the gapps zip included in the mimicry thread, but where can I find a wifi calling apk to install? Also +1 thanks to u for the detailed reply! Thanks!
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
Yeah the whole partition and swapping was the confusing part. But good to hear I don't have to do any of that. I did see the gapps zip included in the mimicry thread, but where can I find a wifi calling apk to install? Also +1 thanks to u for the detailed reply! Thanks!
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
In Mimicry the Aroma installer will actually let you pick that option during the graphical install. It's one of those roms that presents you with a nice installation menu after you select the zip to be applied. Just bear in mind though you need the 26.13.04.19 radio in order to use the T-Mobile Wifi calling app (and course be on T-Mobile). EDIT If you're one of those people who end up getting no WIFI at all after flashing the Wifi calling app from the aroma installer and have the 26.13.04.19 radio, in the first post of the mimicry thread there's a mention of a Wifi-Fix app you can install that might be able to fix that.
For EliteMod ICS, you would apply it by downloading the zip in my signature (for the wifi calling) and flashing that after flashing the rom. But again, needs the 26.13.04.19 radio, as the app won't work with an old radio (26.03.*)
The thread on applying the radio is also linked from my signature , if you're on a T-Mobile G2, you can just grab the first 26.13.04.19 zip file, rename it PC10IMG.zip just like the instructions say there, put it on the SD Card, reboot into the boot loader and apply the radio. Also if you're planning on flashing either mimicry or Elitemod immediately after flashing the new radio, both roms already Clean your EFS partition for you when you install them in recovery, so you don't have to run the EFS wipe zip (something you normally need to flash in recovery after changing a radio).
KB suggested EliteMOD to me a few days ago,...... Gota say it is running vnice at the moment, highly recommend it. w/ SD EXT, no swap.
I downloaded the zip file from the Andromadus thread, and proceeded to flash the ROM. It says the flash was successful, however upon rebooting, I would see the HTC screen but it would never make it to the boot animation. I would just get a black screen. I tried flashing through ClockWorldMod v5. I cleared all data and caches, and then flashed the ROM.. still not working?
mapheG2 said:
I downloaded the zip file from the Andromadus thread, and proceeded to flash the ROM. It says the flash was successful, however upon rebooting, I would see the HTC screen but it would never make it to the boot animation. I would just get a black screen. I tried flashing through ClockWorldMod v5. I cleared all data and caches, and then flashed the ROM.. still not working?
Click to expand...
Click to collapse
What's the exact details of your phone, i.e.: hboot information and radio version.
I flashed the radio from your signature. Hboot information: 0.82.0000
blkjack said I needed to do a superwipe. If that is the case, how would I perform one?
mapheG2 said:
I flashed the radio from your signature. Hboot information: 0.82.0000
blkjack said I needed to do a superwipe. If that is the case, how would I perform one?
Click to expand...
Click to collapse
hboot in my signature is a 0.84.2000 which is a desire-z engineering hboot.
0.82.000 would be an S-ON hboot which you wouldn't be able to change much at all. (which would be odd if you managed to get the 26.13.04.19 radio flashed, while S-On since it wouldn't normally allow you to).
May want to reboot into the boot loader mode and verify all your hboot information.
kbeezie said:
hboot in my signature is a 0.84.2000 which is a desire-z engineering hboot.
0.82.000 would be an S-ON hboot which you wouldn't be able to change much at all. (which would be odd if you managed to get the 26.13.04.19 radio flashed, while S-On since it wouldn't normally allow you to).
May want to reboot into the boot loader mode and verify all your hboot information.
Click to expand...
Click to collapse
I flashed a radio in the past. And it clearly says I have S-OFF on the top. I had the (26.03.02.26) radio before. And it did successfully flash the radio linked from your signature. HBoot says 0.82.0000. Where to go now?
EDIT: I found this link (http://forum.xda-developers.com/showthread.php?t=1044992) but dunno if this is outdated or not. If not, which of the three files do I want?
mapheG2 said:
I flashed a radio in the past. And it clearly says I have S-OFF on the top. I had the (26.03.02.26) radio before. And it did successfully flash the radio linked from your signature. HBoot says 0.82.0000. Where to go now?
EDIT: I found this link (http://forum.xda-developers.com/showthread.php?t=1044992) but dunno if this is outdated or not. If not, which of the three files do I want?
Click to expand...
Click to collapse
I think, the -=SuperWipeG2+=-.zip should be the right one, but as I'm not sure, I did a quick Google search for you and found this:
EdKeys said:
I recently flashed the new 4EXT Mod of ClockworkMod Recovery. The 4EXT Recovery is based off of Koush's CWM Recovery but offers additional power options, one of which is the ability to show the file system format your partitions are formatted in. To my surprise my system was formatted in the Ext 4 format and my data and cache partitions were formatted in Ext 3. The new 4EXT Recovery offers the option to convert the format without deleting any of the data. Your ROM will stay intact after the conversion. I selected that option and changed my data and cache partitions to ext 4 to match my system, rebooted, and notice quite an improvement in speed and smoothness in my current CM7 Nightly. After looking into it further I found out that the SuperwipeG2 that many of us have been flashing is formatting our partitions in the Ext 3 format. The reason only my system was formatted in ext 4 is because I used ClockworkMod Recovery the last time I did a full wipe to first flash the Superwipe, and then I immediately formatted system again with ClockworkMod Recovery. If you've used SuperwipeG2 to do a wipe, more than likely your system, data, and cache partitions are now Ext 3. You might want to check with your ROM developer to see if your ROM will run on the Ext 4 format. If its a CM7 based ROM, it will.
You can find more information about the Ext 4 format here.
Tsubus has since modified SuperwipeG2 so that it now formats the partitions into ext 4 when you flash it. I've used it and it also includes the EFS wipe. You can find it here. As I said, if there is no reason to wipe right now the new 4EXT Recovery can convert your partitions if you choose if they are in currently Ext 3. At the very least you can see what format they're currently in with 4EXT. I highly recommend it. You can always flash back to CWM Recovery if and when you choose. The partitions will remain Ext 4 once you choose to convert.
UPDATE: Several users have reported that checking partition information with Terminal Emulator is not reliable.
Click to expand...
Click to collapse
This one should definitely be the right one.
Besides that, the problem might also be a bad download, as your symptom fits a known issue in blk_jack's thread:
blk_jack said:
...
Q) After flashing I'm stuck at the HTC logo screen!
A) This is likely the result of a bad download. Check your downloaded md5sum hash against the one listed next to the download link above....
Click to expand...
Click to collapse
I thought it was a bad download too, so I downloaded from one of the mirrors. Still the same problem.
mapheG2 said:
I thought it was a bad download too, so I downloaded from one of the mirrors. Still the same problem.
Click to expand...
Click to collapse
So you did not check the MD5 hash?
Im a bit of a noob and all of this wasnt around when I was flashing CM roms ages ago. How do I do that? Would that fix my issue??
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
Im a bit of a noob and all of this wasnt around when I was flashing CM roms ages ago. How do I do that? Would that fix my issue??
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
An MD5 hash is something like a fingerprint of a file and it was definitely there when you first flashed CyanogenMod ROMs. The MD5 hash/sum is used to compare two files because it is possible that a downloaded file is slightly different from the original file due to mistakes that could have happened during transfer. So "checking the MD5 hash" means using a program to calculate that "fingerprint" of your downloaded file and comparing it with the "fingerprint" mentioned in blk_jack's thread. If the file you have downloaded is slightly different, its MD5 hash will be different from the MD5 hash that it should have and thus will be unusable and lead to a phone being stuck at HTC boot logo.
By the way, downloading a file from two different mirrors doesn't exclude the risk of getting a corrupt file.
I ran "md5 update.zip" from my Mac's desktop where the file is located. I was returned MD5 (update.zip) = 2a314e5f1361825c83a354aea38c6c4b .. which matches the md5sum of what was given. What next?
And I noticed you have the same H-Boot information that KB was talking about earlier, so I guess that can't be the problem either. Should I just try to Superwipe?
mapheG2 said:
Ok, so if it is a bad download, how do you remedy it? Because there are only so many options to download the ROM right. And what program are you referring to
Click to expand...
Click to collapse
There are actually lots of programs to calculate an MD5 hash. If you are on Linux it usally is as easy as typing md5sum <path to file> in a shell and reading the output. If you are on Windows, I'd recommend a Google search for "md5 generator" or something like this. Maybe even your recovery is able to calculate a file's MD5 hash - I'm using 4EXT and it definitely is, though I don't know if ClockwordMod is.
You can't remedy a bad download except trying to download it again, hoping that the file will be transferred right.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
mapheG2 said:
I ran "md5 update.zip" from my Mac's desktop where the file is located. I was returned MD5 (update.zip) = 2a314e5f1361825c83a354aea38c6c4b .. which matches the md5sum of what was given. What next?
And I noticed you have the same H-Boot information that KB was talking about earlier, so I guess that can't be the problem either. Should I just try to Superwipe?
Click to expand...
Click to collapse
Oh, sorry - didn't update the thread's page before submitting my reply.
Just try it, there should be nothing wrong with it.
Okay, I read that I should manually clear all the data and cache first and THEN run the superwipe, followed by installing the ROM right? And I will be downloaded from the thread I listed because I still have ext3 I guess and don't want to deal with a ext4 change right now.