Related
I have the Evo, release day model, I believe that's the one without the Epson screen, and I'm rooted running 2.2 official release clockwork. Is it possible for me to remove the FPS cap on the screen without flashing another Rom? If so, can somebody also supply the downloads and instructions for it? Or just a link to another post. Please and thank you.
You can flash a custom kernel, otherwise your stuck with the cap. Sorry, can't post a link, I'm out and about posting from my phone. Go to the evo wiki for kernel choices. And don't forget to do a nandroid backup before you give it a go.
Sent from my PC36100 using Tapatalk
Search the Development section.
I tried making a NAND backup using Rom manager but it just reboot me into hboot and when I reboot back to normal and open up the app again it says failed. Can't remember if I already mentioned this but 2.2 rooted via unrevoked3 to unrevoked forever to stock 2.2 clockwork
Why dont you go through hboot then? Phone off power + volume button down till you get hboot up. Wait till scans. Go to recover and then nand backup. Can go back to Rom manager and change the name.
Sent from my PC36100 using XDA App
When I go into hboot and then recovery it doesn't give me any option for NAND. It just tells me I'm in fastboot and gives me the options of bootloader, reboot bootloader, reboot, and shut down I think. I'll have to check that again but I'm pretty sure that's what the options were. I'm sorry if I'm not to well informed about this.
I loaded a backup of CM7 and when it rebooted it went into a bootloop and I cant get into recovery. I've tried everything even flashing CWM again and also the stock ROM image. Still bootloop!
Please help
You didnt brick it, if you bricked it, it wouldnt start. You should still be able to get into recovery, by holding the power button and volume at the same time, and getting into Hboot, then go to recovery. Im also guessing it happened because you didnt whipe cache or data before you did this. First time i ever installed a new rom i got a bootloop,
Thank you for responding. I cant get into recovery it starts bootlooping once I select recovery. I tried loading the PB image of CWM and I also tried flashing the stock RUU. Cant get past HBOOT or initial bootloop. I CAN get into fastboot ADB though. Tried flashing a backup system.img, boot.img, data.img but boot.img said error
Your welcome, im not perfect at all this so excuse me a bit lol. So your saying when you select recovery, it boots up normally to the splash screen, or am i wrong? If your able to flash things them im pretty sure your able to get into recovery. Maybe also try another version of CM7? Transferring it to your phone.
No I select recovery in HBOOT and it goes straight to the white HTC INCREDIBLE screen and begins the bootloop process. I've pushed the CWM 3.0.0.8 in a pb13img file and still wont go into recovery. I cant get the phone past HBOOT
Thats really really weird that it wont go into recovery and it starts the boot. Hopefully someone can come with some extra assistance. It isnt bricked tho, i know that. So did you try formating data and cache then before doing anything either?
No I was busy and messed up. applied a backup without wiping data/cache. Came back to a powered off phone. Tried turning it on and it was bootlooping. I cant do anything now. Even if I can get S-ON i'll just get a replacement
There's a data wipe option in hboot, have you tried that?
Sent from my ADR6300 using XDA App
Goto Doug piston's web site and follow the go back to stock. You should be able to put the stock RUU on the root of your sd card named pb31img (not sure the exact file name but it is on dougs site). When you load in HBOOT, it should recognize the file and install. If I am not mistaken, this will unroot your phone as well.
http://dougpiston.com/?page_id=108
Pb31img file is there.
I tried the stock rom PB31IMG.zip and it continues to bootloop. If I cant get it fixed I want to at least get S-On
Probably aren't gonna be able to get S-ON cause that needs to be done in recovery..
Sent from my ADR6300 using XDA App
There is also the unrevoked forever s-on tool which you flash through recovery
Sent from my DROIDX using XDA App
Yeah cant get to recovery so I'm boned.
I got VZW to send me a replacement and also got Asurion to get my an Inc2. Not sure which to send back. Free replacement with a gamble getting caught S-On, or $99 free upgrade to Inc2
what radio were you running
try flashing alternate recovery?
i also seem to remember there being a way to root through adb isnt there a way to unroot like that too?
I tried amon ra and a another one no difference. I also tried everything I could adb wise to flash different systems and erase everything. Im running the new GB radio
I may be wrong but I don't think you can apply the RUU with that radio installed. Go back to the stock radio and I think you may be able to flash ythe RUU successfully.
Sent from my ADR6300 using XDA App
CSamson said:
I may be wrong but I don't think you can apply the RUU with that radio installed. Go back to the stock radio and I think you may be able to flash ythe RUU successfully.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I got excited thinking there was a way to unbrick because of a step I missed. So I went to make sure the radio was right. I HAD the GB Leak 2.15.10.05.06
Right now in HBoot it shows 2.15.00.07.28
I know its not considered a brick because it still turns on but there is NOTHING I can do to get it out of bootloop or past HBoot
hmm new GB radio this has been happening with thunderbolt users to.....but in greater numbers.....I'd advise against using the GB leaked radio...
Your backup. Rec2.x. and now. 3.x?
Sent from my Optimized Inc using XDA App
Hey Everyone,
Last week I I flashed the awesomeness that is Nils 3.0 v2.2. After that my Dinc began to randomly reboot and 5x vibrate hell. This would happen if i did anything CPU taxing i.e. Website with lots of media, extensive camera use, or using IP Camera software during an investigation.
I followed the instructions in the post to the T.
Today I was sad to try and flash the OTA leaked + and no issues today at all. I love the Nils rom and would like to know if there is something I can do to fix that issue.
Thank You
just to confrim s-off rooted with cwm 3.0.0.8 or 3.0.0.7 for amoled or cwm 5.0.2 also make sure your on hboot .92 issues similar to yours have been said by people who had the .77 hboot...
if you dont have a clue what im talking about what color is the recovery
I would probably run the new ruu as long as you have s-off then flash
one of the following 3 recoverys clockwork mod
3.0.0.7 if you have an amoled inc
3.0.0.8 if you have a slcd
or use 5.0.2 i have had no issues with it...
orange is 3.0.0.8
blue is 5.0.x.x
once you have the right recovery
then get nils 3.0 2.3 rom you should put this on the sd card after you format the sd card in fat32 then
boot back into recovery then go into
advanced format davlik
go to mounts and storage
format the following
/data
/datadata
/boot
/system
/cache
your phone should have absolutely nothing but recovery and what ever is in the emmc by default at this point.
then select install from zip pick what should be the only thing on the sd card at this point nils 2.3 3.0 rom wait till it finishes then reboot it should take roughly 5-8 minutes to boot be patient it is rebuilding the davlik it should eventually turn off the screen if you hit the power button it should come up on the lock screen un lock it and then go through the setup and your phone should be ready and stable...
Thanks I will do that. I am on h. 92 with cwm 5.x. So flash ruu factory stock? Or can I just follow the steps to format?
Sent from my ADR6300 using xda premium
Shadowbirdy said:
Hey Everyone,
Last week I I flashed the awesomeness that is Nils 3.0 v2.2. After that my Dinc began to randomly reboot and 5x vibrate hell. This would happen if i did anything CPU taxing i.e. Website with lots of media, extensive camera use, or using IP Camera software during an investigation.
I followed the instructions in the post to the T.
Today I was sad to try and flash the OTA leaked + and no issues today at all. I love the Nils rom and would like to know if there is something I can do to fix that issue.
Thank You
Click to expand...
Click to collapse
Fix here........
Shadowbirdy said:
Thanks I will do that. I am on h. 92 with cwm 5.x. So flash ruu factory stock? Or can I just follow the steps to format?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
depends are you also having issues with it not seeing the sd card and the usb not being detected if so the other guy posted a fix for those issues if you are just stuck in the stock rom like i think you said you had to install...
then no you should be able to just skip that and do the formatting options if it still does it after the formatting
use the ruu exe that recently got published in this thread would not be a bad thing to do first as it should blow every little thing away except for the s-off from there if i remember right you will need to reflash the recovery to the phone... grab it off http://dougpiston.com/?page_id=85 flash it in hboot after the ruu then format and then install nils 2.3 version that just came out weds
i have an htc evo 4g phone that has the android 2.3.5 running and i have it rooted and it is running a recovery mode of Amon ra. i have been trying the past like 4 hours to put a Rom on my phone. i download the rom of my pc and than plug my phone to the pc and after the download is finished i drag the download over and it loads on the sd card. than i turn the phone off and go to recovery then i clear everything using superwipe program and than i would flash the rom. the rom would download and say it has downloaded to the sd card. Then i reboot the phone and it just comes to the HTC EVO 4G white screen and doesnt do anything after that. i waited for like 25 min. and nothing it just stays at that screen. ANY ideas on fixing this or what to do. I really appreciate it.
Jdog0204 said:
i have an htc evo 4g phone that has the android 2.3.5 running and i have it rooted and it is running a recovery mode of Amon ra. i have been trying the past like 4 hours to put a Rom on my phone. i download the rom of my pc and than plug my phone to the pc and after the download is finished i drag the download over and it loads on the sd card. than i turn the phone off and go to recovery then i clear everything using superwipe program and than i would flash the rom. the rom would download and say it has downloaded to the sd card. Then i reboot the phone and it just comes to the HTC EVO 4G white screen and doesnt do anything after that. i waited for like 25 min. and nothing it just stays at that screen. ANY ideas on fixing this or what to do. I really appreciate it.
Click to expand...
Click to collapse
What rom? Are you flashing any additional mods or kernels? Have you tried manually wiping everything except sdcard 3 times?
Sent from my PC36100 using XDA
yeah .manually wipe everything like he said a few times. Then make sure your kernel is compatible with he from u are flashing u may need to dowlnload a kernel and flash it right after u flash your new from. I'm curious to what from u are flashing from and the kernel. And what from are u trying to install now
Sent from my PC36100 using XDA
I mean ROM
Sent from my PC36100 using XDA
Correction. Wipe everything except SD card
OG EVO 4G
AOKP BUIKD 28
Tiamet 4.1
Rom manager is better IMO. Just use Rom manager, it never gave me any problems. Power off. Press volume down+power at same time, wait for HTC logo. It should take you to the white screen that shows you soff or son . Click recovery, wipe boot-data-cache-system. Click on advanced, clear dalvik and battery stats, reboot recovery and install your Rom. That's exactly what I do and it works everytime. I'm a noob myself don't go brick your phone.
My hboot is 2.18
supersonic evt3 ship s- on
i have tried rom manager and it didnt load any either. i have tried putting team nocturnal and miui roms and stuff for my htc evo 4g. but i dont know if my version accepts it. It wont load any of them.
dave198803 said:
Rom manager is better IMO. Just use Rom manager, it never gave me any problems. Power off. Press volume down+power at same time, wait for HTC logo. It should take you to the white screen that shows you soff or son . Click recovery, wipe boot-data-cache-system. Click on advanced, clear dalvik and battery stats, reboot recovery and install your Rom. That's exactly what I do and it works everytime. I'm a noob myself don't go brick your phone.
Click to expand...
Click to collapse
ROM Manager is NOT better, it's way worse than doing it through recovery. Many people have problems and have even bricked devices due to Rom Manager. Just don't use it.
i just tried putting a prime xl rom for my phone and cleared eveything 3 times and stuff and it stills just goes to the white HTC EVo 4g screen. just no loading of the roms. thanks for all your answer and help guys. still am confused.
Yeah do it from recovery. Not rom manager. Never heard of that rom. Gonna try it on my phone tonight and check it out. Again did u see if the kernels u are using are compatible. That was my problem a few times when flashing sure is the link for the rom u are trying to install.
Sent from my PC36100 using XDA
If you restore from your nandroid backup, does it boot up?
Like others have stated, your checklist prior to flashing anything should be 1. Make sure you have more than 30-40 % battery charge, Download Rom, Kernel, and if your ROM is AOSP, gapps, place on SD, reboot into recovery, I have always used AmonRa 2.3, Nandroid first...... wipe ALL (x3), flash ROM, flash gapps if AOSP, flash kernel compatible w your build (2.3.), Reboot.....be patient while first boot takes a little longer than normal. Hope this helps
BeInGarvey
Jdog0204 said:
My hboot is 2.18
supersonic evt3 ship s- on
i have tried rom manager and it didnt load any either. i have tried putting team nocturnal and miui roms and stuff for my htc evo 4g. but i dont know if my version accepts it. It wont load any of them.
Click to expand...
Click to collapse
you should run revolutionary.io go to google and usr that tool. i think you need s-off to do what you wanna do man?
Jdog0204 said:
My hboot is 2.18
supersonic evt3 ship s- on
i have tried rom manager and it didnt load any either. i have tried putting team nocturnal and miui roms and stuff for my htc evo 4g. but i dont know if my version accepts it. It wont load any of them.
Click to expand...
Click to collapse
Wait are you s-on unlocked or just straight s-on in the bootloader?
Sent from my PC36100 using XDA
My s is on and it says on the top unlocked. I don't know exactly what that means.
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