Related
help my g2 is stuck at the htc screen. i perm rooted it with s off and tried to overclock it. i went into clockwork mod recovery and installed the zip files g2 fast? now when i turn it on it goesd to htc screen and then it reboots at htc screen and reeats.
so you flashed a kernel? Was that kernel compatible with whatever rom you are using? Did you take a nandroid backup before hand?
no i didnt backup, i thought i did but apparently i didint.
He's right, that kernel is not compatible with the stock ROM. The best thing to do now is to take out the sd card and put it in a card reader. You just need to download a custom ROM to it so you can flash it. I think if you try to do a factory reset your phone will lose root, but I could be wrong. If you want to return to a stock ROM, search the forums. There are stock ROMs that have been "rooted" so to say. This may have been a blessing in disguise because custom ROMs blow away stock!
ok and how would i do this? i did a factory reset and everything. i think its rooted cause it has the clockwork mod recovery. should i try returning it?
dethformybodom said:
ok and how would i do this? i did a factory reset and everything. i think its rooted cause it has the clockwork mod recovery. should i try returning it?
Click to expand...
Click to collapse
Do you know how to take out the sd card? Also, do you have a card reader on your computer?
yes and i dont have a card reader but i can mount the sd card to the computer.
You don't even have to do that. All you have to do is boot into recovery. Mount the SD card and copy over a kernel that is compatible with the stock rom. Then flash the new kernel and you're all set. I'm sure the stock kernel is floating around here some where.
Gunlance said:
You don't even have to do that. All you have to do is boot into recovery. Mount the SD card and copy over a kernel that is compatible with the stock rom. Then flash the new kernel and you're all set. I'm sure the stock kernel is floating around here some where.
Click to expand...
Click to collapse
That's great!...didn't know you could access the sd card like that. He's right too. All you need to do is flash a kernel that is compatible with the stock ROM.
I think this one will allow you to overclock: http://forum.xda-developers.com/showthread.php?t=834565
okay, i already tried to find the stock kernel but i couldnt find it. even so i wouldnt know how to flash it.
dethformybodom said:
okay, i already tried to find the stock kernel but i couldnt find it. even so i wouldnt know how to flash it.
Click to expand...
Click to collapse
You do it the same way you did the g2 fast kernel.
install the zip? where do i find the stock rom or whatever?
Well you're going to have to use the search button for that one. Check the G2 sticky thread. You need either a stock kernel or stock rom compatible kernel. You could also skip this whole endeavor and just flash the latest CM7 rom from recovery. If you do flash a new rom then it is highly recommended to do a data wipe meaning anything you had done on the phone will be cleared.
found this http://forum.xda-developers.com/showthread.php?t=836042
im installing it at the moment i type. we'll see what happens.
it worked! thanks alot guys. i just wish i didnt do the factory reset. also would the phone still be rooted?
Yes, and if/when you decide to flash a custom rom, find out if it has an oc kernel included. CM roms are using pershoots 1.5Ghz UV kernels currently. If you want to use G2fast, you will need to flash that kernel after the rom, and slowly clock up to see how far you can run stable. I advise paying for SetCPU to monitor your OC as well.
HTC Vision 1.8 OC, CM7 RC1==HAPPY!!
So I rooted using unrEVOked a while ago, have flashed multiple ROMs, currently with CM7, but now I just want to take it back to the stock sense ROM. When I flash the ROM it brings up an error message and defaults back to CM7. This happens anytime I try to flash any new ROM now. Have tried flashing from Recovery and from ROM Manager. What am I doing wrong, am I missing something?
Edit: Now will only revert to CM 6.1.2 which was the first ROM flashed.
Is signature verification on?
Where did you get the"stock sense"rom?
Why not use a pc36img.zip?
What recovery are you using?
What is the error message?
Sent from my hand with XDA Premium installed
Are you still rooted? Boot into the bootloader (power off your device then simultaneously press the down volume button and the power button) and at the upper right corner when the bootloader screen appears you should see either S-ON or S-OFF. Hopefully, it displays S-OFF. If not, you are no longer rooted. If it does display S-OFF, I recommend that you flash the latest version of amon RA. Afterwards, reboot into recovery, select the wipe menu and then wipe EVERYTHING in it EXCEPT the SD card itself. When you're done, flash the rom you want to flash.
posting & replying via the XDA Premium app
dont know if it will help you but a friend of mine had a similar problem,and he thought it was a problem with the whole asop vs sense rom, what he did was flash another asop rom, he flashed miui rom and then he let it run for a few hours and then flashed sprint lovers rom which is pretty close to stock and it worked
Thanks everyone. Got it figured out. Not sure what the issue was but got Sprint Lovers flashed and running.
Just finished rooting my phone now I want to know how to get gingerbread on it tried
Doing a couple of roms but none work any advices???
What roms did you try and why didn't they work? It will help if you give us some more details.
And welcome to the forums.
Sent from my T-Mobile G2
Search the market for Rom Manager. Please make sure your phone is fully rooted, (S-Off).
I hope this helps you bub.
kboogi said:
Please make sure your phone is fully rooted, (S-Off).
Click to expand...
Click to collapse
Yeah, you need to be rooted AND S-Off. If you don't know, you can verify S-Off by powering down, then holding the volume down button while pressing the power button. When the screen comes up, there will be some text, and one of the lines at the top will say S-Off or S-On.
Go to market and download ROM Manager to get ClockworkMOD recovery flashed on your phone. Go to the dev section and choose a GB ROM, I suggest RMK's Virtuous G-Lite 1.0.2 as it is overclockable via SetCPU to 1.5GHz and is AOSP GB.
As posted above, make sure you have root and S-OFF as this will ensure that you are set for flashing roms.
To flash is simple, not sure if you have flashed before so I will post this anyways.
Download the rom you want to try and place in the root of your sd card. Once you have CWM flashed, use ROM Manager to boot into recovery. Go to backup/restore and perform a backup of your current setup. Then go to wipe and wipe data, cache and battery stats. After, head to flash zip from sd and select the rom zip, let it do its thing and you should be in business! First boot is always longest and should always perform a cold boot after a flash to settle things down before you use it.
Have fun!
Sent from my T-Mobile G2 using XDA App
How to Dual Boot Multiple ROMs on Your Android Phone
Whether you want to test out a new ROM for daily use or just keep an eye on one that's being developed, you can run multiple ROMs on your rooted Android phone with BootManager, and pick which one to use when you start it up.
Having multiple ROMs to choose from is great, but flashing and re-flashing new ROMs just to try them out is annoying. If you want to try one out but don't want to fully flash it over your current ROM, BootManager will let you flash it (and up to three others) to your SD card, so you can try multiple ROMs at once. The ROMs you run from your SD card won't be quite as fast, and not every ROM out there will work, but it should give you a chance to try out most other ROMs without fully flashing them.
Right now the app is officially supported on the original Motorola Droid, Droid Incredible, HTC Thunderbolt, HTC Vision, HTC EVO 4G, HTC Inspire 4G, HTC Desire, and the HTC Desire HD. It may work on other phones, though, they just aren't officially supported yet.
Note: This tutorial contains some pretty advanced stuff, and i don't recommend it if you're unfamiliar with rooting and flashing ROMs. If you're just starting out, check out how to root your Android phone and how to flash Android ROMs before moving onto something like this.
Step One: Flash a Second ROM
Before you do anything, make a nandroid backup of your current ROM with ROM Manager or through your recovery module. If anything goes wrong, you can always restore from this backup to get things back to the way they were.
To set up BootManager, just download and install it from the Market, and start it up. You'll also want to grab a ROM of your choice and save the zip file on your SD card.
When you first start up BootManager, it'll prompt you to back up your boot.img, which you should do before installing any ROMs. Once you've done that, head to "Install ROMs". Pick the zip file from your SD card containing the ROM you want to flash, and check all three boxes: Wipe System, Wipe Data, and Wipe Cache. Let it do its thing (which will take awhile). When you're done, it will give you the option of booting into your new ROM. Hit Done; we aren't ready to boot into it just yet.
Step Two: Install Google Apps and Other ROM Add-Ons
Most ROMs don't come with Google's copyrighted apps, like Gmail, the Market, and others. This is a problem, since when you boot into your new ROM you need BootManager to function if you ever want to boot out of it, and it won't work unless you're signed into the Android Market. Luckily, there's an easy fix (note: if you know your ROM comes with Google Apps installed, you can skip this step).
Download the Google Apps zip file for the ROM you just installed and go back to BootManager. Hit Install ROMs. This time, pick Google Apps' zip file, and use the same slot that you used in step one. Leave all three "wipe" boxes unchecked this time. When it's done, booting into that slot will take you to the original ROM, but with the Google apps installed.
If you want to install a theme or other zip-based mod in the future, you can do that using this method too. Just remember: if you're flashing a new ROM, check all three "wipe" boxes, but if you're just installing an add-on to a ROM, don't check any of them.
Step Three: Switch Between ROMs
To boot into one of your other ROMs, just head into BootManager and choose "Boot Installed ROM". It'll show you a list of ROMs you have installed on your device, and after choosing one of them it will reboot into that ROM. BootManager will come installed on each of your other ROMs as well, and as long as you're signed into the Android Market on that ROM, you can boot into it from there as well and switch back to your main ROM.
That's it! You can flash up to five ROMs at a time, so you'll never be bored by one measly operating system. Hit the link to download BootManager.
BootManager is a $2.99 download for Android 2.1 and up. See the Market page below for officially supported devices.
https://play.google.com/store/apps/details?id=com.drx2.bootmanager&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5kcngyLmJvb3RtYW5hZ2VyIl0. (Theres a lite and pro version )
Found this app in the sensation forums and found it was officially supported on DZ
great job!! studying...
Great post. THNX
Sent from my SK17i using xda app-developers app
sweet deal, think i'll try this out. any major bugs, in your experience?
That's neat, any chance of conflicts when it comes to data on swap/sd-ext/sdcard ?
Isn't this post supposed to be located in "G2 and Desire Z Themes and Apps"?
You are actually just recommending an app and providing information that is already available on http://www.init2winitapps.com/
Sent from my HTC Vision using xda app-developers app
Cool stuff! Thanks for sharing! Wonder if this is the step to go for booting other Mobile Linux Distros like MeeGo!
When will be available this app with support for sony phones?
Sent from my SK17i using xda app-developers app
I've already test on my desire z and this don't work, when i want to reboot on my seconde rom my phone freeze on the boot image (just before the boot animation) I don't know if i'm not wait enough time but I wait 8 minutes !! and i've juste the boot splash !! I had to go by the bootloaderand after by the recovery for restored my phone
But Thanks a lot It's a very good idee to make a tuto
Does anyone have any ICS roms working with this?
i highly doubt most ROMs would work with this, especially ICS roms... it's just too good to be true, and the app needs a lot of refinement.
Yeah I downloaded the light version and the only ROM I could get working was the JoyOS port. I tried Andromadus Mimicry, MIUIv4, G2Slim, and some others I don't remember and they didn't work.
Sent from my HTC Vision using xda app-developers app
raydar670 said:
Yeah I downloaded the light version and the only ROM I could get working was the JoyOS port. I tried Andromadus Mimicry, MIUIv4, G2Slim, and some others I don't remember and they didn't work.
Click to expand...
Click to collapse
I've used this app off-and-on for months. Couple things to note. It won't work on G2/DZ unless you set the large boot setting. Also, some ROMs just don't seem to like it. Most ROMs can be made to work by installing normally, doing a nandroid then installing the nandroid to the boot manager pseudo-partition. Even that way, I've had some ROMs that wouldn't boot.
I definitely used it for ICS (Andromadus and CM9/unnoffical, I think) before I committed to DD with ICS.
GinoAMelone said:
I've used this app off-and-on for months. Couple things to note. It won't work on G2/DZ unless you set the large boot setting. Also, some ROMs just don't seem to like it. Most ROMs can be made to work by installing normally, doing a nandroid then installing the nandroid to the boot manager pseudo-partition. Even that way, I've had some ROMs that wouldn't boot.
I definitely used it for ICS (Andromadus and CM9/unnoffical, I think) before I committed to DD with ICS.
Click to expand...
Click to collapse
I have tried the large boot setting for all those ROMs but not the nandroid yet, maybe I'll try that later.
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