Develop Bugs

Clockwork 3.x does not flash properly?, want to go back to 2.5.x? Look here!

I'm looking for CW 2.5.0.1(?) so I can flash radio and other files. It seems like 3.x "aborts" install with some files.
I have not been able to find the 2.5.x CW img for the Evo. Also, now that my phone is crippled (flashed a new ROM), how do I install the 2.5.x over the 3.x? ROM Manager does not give me the option to flash back to 2.5.x
Thanks for any quick help!
BTW, I'm not using RA because it doesn't seem to allow me to navigate the SD directory to chose files to flash. If there is something I'm missing, let me know.
Edit:
See post #7 below, it contains the file to get you back to 2.5.0.1!!

snovvman said:
I'm looking for CW 2.5.0.1(?) so I can flash radio and other files. It seems like 3.x "aborts" install with some files.
I have not been able to find the 2.5.x CW img for the Evo. Also, now that my phone is crippled (flashed a new ROM), how do I install the 2.5.x over the 3.x? ROM Manager does not give me the option to flash back to 2.5.x
I believe that the new clockwork is causing problems for a lot of people, myself included. I cant revert to an old clockwork like 2.5 either. I just had to flash RA 1.8 on my phone and my wife's Evo.
Click to expand...
Click to collapse

Rom manager has an option at the very bottom called "all clockwork recoveries"... Use that and select whatever build you want.
Sent from my pants. You figure out how I typed it.

Justin.G11 said:
Rom manager has an option at the very bottom called "all clockwork recoveries"... Use that and select whatever build you want.
Sent from my pants. You figure out how I typed it.
Click to expand...
Click to collapse
For some reason that method isn't working for a lot of people, myself included. The thing that is working is to flash RA 1.8
I tried several times to revert to an old clockwork and kept getting an error.

go here... http://www.clockworkmod.com/download/recoveries/
click the supersonic recovery you want... make sure its the .zip file.
put on ur SD card and flash. hope this helps

Justin.G11 said:
Rom manager has an option at the very bottom called "all clockwork recoveries"... Use that and select whatever build you want.
Sent from my pants. You figure out how I typed it.
Click to expand...
Click to collapse
cbond007 said:
For some reason that method isn't working for a lot of people, myself included. The thing that is working is to flash RA 1.8
I tried several times to revert to an old clockwork and kept getting an error.
Click to expand...
Click to collapse
Correct, the older versions in ROM Manager do not work for the Evo.
I ended up finding a pc36img.zip and flashed it. I am now back to 2.5.0.1. I don't use RA because I can't select files. It's a pain when I have a lot of files to flash.

Here is the Clockwork 2.5.0.1, packaged flashable.
Put it in the root of your SD, boot into bootloader, let it update, and life is good again...
Edit: Some additional info to save you some searching:
Make sure you flash using bootloader and NOT your current recovery. Power off, hold Vol Down, and Power On. Let it update the image, then reboot into recovery again. At that point, you should see 2.5.0.1.
ROM Manager does not properly downgrade. 2.5.1.4/3, I have been told, is not for Evo. You will need to flash manully as I described.

snovvman said:
It seems like 3.x "aborts" install with some files.
Click to expand...
Click to collapse
There's a more sinister problem with 3.0.0.1 (which appears to have now been retracted, as ROM Manager, after updating me to 3.0.0.1, is now showing "Latest Recovery: 3.0.0.0" at the time I write this).
It's only sheer chance that I had another unrelated problem, or I would have been screwed -- the Nandroid backup is broken in 3.0.0.1 (it completed the backup operation within about 2-3 seconds, clearly not having backed up everything!)
Edit: I checked in the backup directory, and the only files backed up by 3.0.0.1 were boot.img and recovery.img
Now that I reverted to 3.0.0.0, at least the backup takes a good long time and seems to be listing all the usual stuff, but I don't feel that I can trust 3.0 now.
I'm going back to what was working for me a couple of days ago (2.5.1.2) when I tried CyanogenMod (6.1.1) for the first time. ROM Manager and ClockworkMod Recovery handled it all so perfectly that I kicked it off with checkboxes enabled for the "back it up" and "wipe" options, got called away for about 1/2 hour, and when I returned, there was CM6 in all its beauty, even including the Google apps.
Is there an "official" place to report bugs for ClockworkMod Recovery? I noticed that the clockworkmod.com web site has gone poof (Google cache shows it intact on Dec 11th).
--tgi
HTC Supersonic / Sprint EVO 4G / Hardware 002
myn's Rooted Froyo 2.2 3.29.651.5 Radio 2.15.00.09.01 Kernel 2.6.32-ge2fb08e [email protected] #11

I'm sorry, but as an AR Recovery user, I see no reason to switch to Clockwork other than being able to browse folders other than the root of your memory card for ZIPs. AR seems much more stable and has had all of the features (except that one) that CW recently had added.

tgi007 said:
There's a more sinister problem with 3.0.0.1 (which appears to have now been retracted, as ROM Manager, after updating me to 3.0.0.1, is now showing "Latest Recovery: 3.0.0.0" at the time I write this).
[/COLOR]
Click to expand...
Click to collapse
When ROM Manager prompted me to update tonight, I got 3.0.0.2. I was able to complete a backup, including the WiMax partition. Going back to the advanced restore menu, I was given the option to backup WiMax and other partitions seperately.

Does flashing work properly now?

At this point I'm afraid to try.

Product F(RED) said:
Does flashing work properly now?
Click to expand...
Click to collapse
Flashing works just fine with 2.5.0.1.

snovvman said:
Flashing works just fine with 2.5.0.1.
Click to expand...
Click to collapse
+1
.......

snovvman said:
Here is the Clockwork 2.5.0.1, packaged flashable.
Put it in the root of your SD, boot into bootloader, let it update, and life is good again...
Click to expand...
Click to collapse
I have a Root folder I made in sd card and put the image file in folder in bootloader now its not reading it. what to do?
Edit: I figured it out and works perfect!! Thanks Button..

Product F(RED) said:
I'm sorry, but as an AR Recovery user, I see no reason to switch to Clockwork other than being able to browse folders other than the root of your memory card for ZIPs. AR seems much more stable and has had all of the features (except that one) that CW recently had added.
Click to expand...
Click to collapse
+1 on this I will have to admit other than folder search I see nothing better about CW over AR and AR has great wiping features and usb mode. But to each its own...

Product F(RED) said:
I'm sorry, but as an AR Recovery user, I see no reason to switch to Clockwork other than being able to browse folders other than the root of your memory card for ZIPs. AR seems much more stable and has had all of the features (except that one) that CW recently had added.
Click to expand...
Click to collapse
playya said:
+1 on this I will have to admit other than folder search I see nothing better about CW over AR and AR has great wiping features and usb mode. But to each its own...
Click to expand...
Click to collapse
Question for yoru guys: When you flash with RA (/AR), do you just rename the file and put it into the root of SD each time? Is there an easier way to flash with RA that I am not aware of?

snovvman said:
Here is the Clockwork 2.5.0.1, packaged flashable.
Put it in the root of your SD, boot into bootloader, let it update, and life is good again...
Click to expand...
Click to collapse
I tried this it says it runs the recovery but after I reboot and run rom manager it says clockworkmod 3.0.0.2. Am I missing a step?

snovvman said:
Question for yoru guys: When you flash with RA (/AR), do you just rename the file and put it into the root of SD each time? Is there an easier way to flash with RA that I am not aware of?
Click to expand...
Click to collapse
Not defending CW, but it does have USB Mode. It's just tucked away in the menu.
If I'm on my PC, I download and then just drag to the phone or I use Dropbox, then Astro to move it to the root. If I'm not, then I use Astro. I don't have to rename anything.

ARG! I flashed 2.5.0.1 and still non of my old backups work they all hang at the white htc boot screen. I am just booting into recovery and running restore should I be doing something first?

reboot into recovery question

So im following a way to put a rom onto my phone, let me post the steps and go from there
1. The first step is to download Modaco’s Custom ROM from here and save it on your desktop. done
2. Once done, download ROM Manager from Market on your phone. done
3. Once the ROM Manager is installed, launch app and flash ClockworkMod Recovery. done
4. Now after flashing ClockworkMod Recovery, connect your phone to the computer. done
5. Once your phone is connected, mount SD card and copy the earlier downloaded ROM file to SD card root. done
now this is where im having an issue.... i know where it says to reboot into recovery, but when i do this, i get a black screen with a pic of my phone and a red triangle with an exclamation mark on it.... what am i doing wrong?
6. After this launch ROM Manager again and tap on Reboot into Recovery.
7. Once you are in recovery, scroll down to Apply Zip from SD card and select.
8. Now wait for the installation to finish. The ROM size is 257 MB, so you can well imagine the time it will consume.
9. Once the installation is finished, reboot your phone.

This means ClockworkMod recovery Did not stick, sometimes it takes a couple of tries to get it to stick, so go back into Rom Manager and Press "Flash ClockworkMod recovery" Again, then reboot into recovery, if you still see the black screen with the trangle and ! (this is stock recovery) , just pull the battery and repeat the steps of Flashing CWM recovery again untill it sticks, It took mine three times before it would stick. Also you must make sure you have S-off and root.

well from all the reading i did, using the visionary+ would be enough of a root... granted my s-off isnt there, its still saying s-on.... and on another post made, i tried to follow the instructions, but i cant seem to change this...
suggestions on how?

The other day I gave you a link to a thread on how to properly get S-off and root on your phone, you choose not to use that link, instead you used Visionary, so I am going to assume that you do not have ABD set up on your home computer, so now here is another link to a new thread on how to get temp-root with Visionary, which is what you have now, then perm-root S-off with Gfree, follow the instructions in this new link from start to finish and you should have S-off when its all done. HERE IS THE LINK. I suggest you do a lot more reading before proceeding any further because it seems to me you really don't understand what you are doing and Mod'ing your phone and making a mistake can have the potential to BRICK your phone. Having root and S-off are two different things and you need S-off in order to flash custom Roms and recovery.
I still recommend getting S-off and root using the method HERE, its the safest way to root and get S-off, this is the link I gave you the other day to the XDA Wiki.

im using this link
http://forum.xda-developers.com/showthread.php?t=928160
and trying to follow it... but for some reason, when i do this step
$ su
# cp /sdcard/root_files/perm_root /data/local/perm_root
i get a msg that says cp:cannot create '/local/perm_root': no such file or directory
yet im following the steps exactly

Did you make sure to unzip the root_files.zip before placing all the files on the root of your sd card, do not just place the root_files.zip on your sd card it must be unzipped first.
Also make sure you put a space between perm_root and /data
I put a red * where the space needs to be.
From what you typed below it looks like you didn't.
kneedraggin101 said:
# cp /sdcard/root_files/perm_root /data/local/perm_root
Click to expand...
Click to collapse
This is what it should look like, without the red * of course,
Code:
# cp /sdcard/root_files/perm_root[COLOR="Magenta"]*[/COLOR] /data/local/perm_root

well i got everything to work there just before you posted this, and i proceeded to install this rom found here
hxxp://android.modaco.com/content/t-mobile-g2-g2-modaco-com/322825/with-sense-10-feb-r3-htc-vision-g2-z-modaco-custom-rom-with-online-kitchen/
followed the steps to make it work, got into recovery, let it install via the steps listed above
now the phone is restarting over and over again.... and it keeps going to the htc quietly brilliant logo, then has the modaco logo under it... but it keeps going over and over....
ideas?

You are in a boot loop, did you wipe data prior to flashing the new ROM? The rom you downloaded might be a corupt download, try to redownload it again and flash it again. Also, just curious why MODACO rom there are so many other better choices available, IMHO.
Sent from my HTC Vision using XDA App

well i just saw that it was one with a sense rom, so i thought i would try it out.... and this rom said no need to wipe data... thats part of why i chose it...
also how do i re download it and get it on my sd card? when i cant connect to the computer now
also what is a good solid sense rom, that i dont have to delete everything off my phone first, and ill gladly try that out... remember im new to this... so all the info you give me now is totally uncharted areas,
so lmk
Cheers

I would use Virtuous I think its the best sense rom out, you should always do a full data wipe when changing roms, when updating the same rom its not really needed, as far as getting it onto your sd card, I would just pull it out of the phone and put it into a card reader on my computer and then install the new files that way then place it back into your phone .
Sent from my HTC Vision using XDA App

ok and do you have a quick link i can trouble you for the virtuous rom?
and how do i back up whats on my phone now, i dont want to loose anything thats on there.....and since im stuck in this boot loop, im stuck for a way to back it up

Ok to make a back up from where you are stuck at, pull the battery then put it back in hold volume down then press power, this boots it into bootloader, use the volume button and scroll down to recovery and select it by pressing the power button, it should boot into CWM recovery, then press backup and restore, then select backup and it should back up your current rom, to do this in the future just use rom manager to make your back ups, here's the link to Virtuous http://forum.xda-developers.com/showthread.php?t=837042
Sent from my HTC Vision using XDA App

but wouldnt that copy my current rom thats stuck in a boot loop?

Sorry you are right , so it looks like there would be nothing for you to back up. Prior to flashing MODACO you should have made a copy of your stock rom w/root but its to late for that now, so theres nothing to do now but flash a new rom.
Remember when you flash a new rom it could take a few minutes to boot the first time so give it a few minutes.
Sent from my HTC Vision using XDA App

Making the nandroid backup wouldn't hurt though. If there is stuff you really need, you can transfer the backup to a computer and then extract the contents of the data and system images with an unyaffs tool. Then you can restore at least some things manually once you have your new ROM up and running (since you'll then have the APKs and their respective data directories).
Kind of a pain and may not work depending on what you want, but if there is stuff you really need, better to at least have the opportunity to recover than not.

so I installed the virtuous Rom and now I cant use the market... is there a fix for this?

kneedraggin101 said:
so I installed the virtuous Rom and now I cant use the market... is there a fix for this?
Click to expand...
Click to collapse
Try fixing permissions, boot into recovery, select advance, select fix permissions, reboot. If that doesnt help, use titanium to wipe the data from the market app and see if that helps.

how do I do the titanium backup part? I tried the recovery part, didn't work.....

[Q] stuck at white htc evo 4g screen - not flashed anything yet

hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.

Maybe its the busybox that you downloaded. You should hit up recovery and do a full wipe! The start up again. What rom are you running, most roms have busybox included so when you download it I've seen phones get the white screen of death. Grab a rom and reflash it. Since you put busybox that nandroid you made probably is no good. Reason I'm telling you all this is because has happened to me before. Good luck
Sent from my PC36100 using XDA Premium App

ravissimo said:
hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.
Click to expand...
Click to collapse
Well, I'm not sure what exactly went wrong for ya, but I might suspect it was something to do with some of the apps you downloaded prior to making your backup. The first thing to try, would be to boot to recovery, and wipe cache, and then go to 'advanced' and wipe dalvik cache. Then try to reboot. If that fails, then you're next option (without flashing a new ROM) is to do a data/factory reset. You will however lose all of your apps, settings, contacts, texts, etc. You unfortunately don't really have any other options, unless wiping cache's helps you out. If a factory reset doesn't allow you to boot, then you're most likely going to have to flash a new ROM. And also, I thought that Unrevoked flashed the latest clockwork recovery, which would be 3.0 or somehting like that, no?

Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?

ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
You don't need to download busy box, I would delete that app. If you flash a rooted rom it should already have busybox; if you just rooted your phone and want to download busybox on your current stock rom then it will be ok. I would wipe and flash a new rom just to be safe.
Sent from my PC36100 using XDA Premium App

ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
Well, I'm not exactly sure why you want to download busy box so badly. Any rom comes with busy box cooked in. I have only once installed busy box. The only time i remember having to do it, was Immediately after I rooted with Unrevoked, i went to use Titanium, and had some error. I hit the problems button and that updated busy box from there. Other than that, I've never messed with it.
And yes, most likely your nandroid backup is not going to be of any value to you. You could try restoring it if you'd like, but I predict it would be a waste of time. And I'm not sure that it matters that you didn't 'open' and click install on busy box. If you downloaded it from the market, wouldn't it just download and install itself automatically? I would just flash a rom, and be done with it. Roll with whatever version of busy box comes with the ROM you flash. As you said, you're only option is a factory reset now, and if you're going to do that, you certainly may as well flash a custom rom at the same time. You just need to download a rom, and put it on your sd card. You can mount the sd card as a disk drive to your computer from within recovery. I use amon ra, and its called USB MS TOGGLE. I'm not sure what it's called in clockwork, but the option is there. So put the rom on your sd card, perform a complete wipe, (i'd flash calkulin's format all.zip as well), flash a rom, reboot, and forget about anything with busy box. It will be installed on the rom already.

If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App

Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.

If you can get a logcat that should show what is causing it to bootloop. It's 'adb logcat > logcat.txt' to do it, run that and wait for it to loop 3 or 4 times before pushing Ctrl+C to stop it.

Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.

ravissimo said:
Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.
Click to expand...
Click to collapse
Right. But unfortunately now, your data seems to be lost. Did a factory reset help anything? If not, you got to wipe and reflash a rom.
Sent from my PC36100 using XDA App

ravissimo said:
Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.
Click to expand...
Click to collapse
I understand that. As I stated, I'm not sure what's causing your problem. As xhausx said, try getting a logcat
Sent from my PC36100 using XDA App

What method of rooting did you use? What recovery do you have right now? As hausx said you could do a logcat and he'll check it out!
Sent from my PC36100 using XDA Premium App

Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.

ravissimo said:
Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.
Click to expand...
Click to collapse
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.

xHausx said:
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.
Click to expand...
Click to collapse
OK, so I downloaded and extracted the auto-root tools only zip from your sig, and then ran OpenShell.bat and typed as you said "adb logcat > logcat.txt" with my phone plugged in. said "waiting for device" and then i turned on my phone and let it boot 4-5 times before ctrl+c and pulling the usb. all the logcat.txt says is...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
am i doing something wrong?
my apologies, i've only throughly read on how to root, i hadn't gotten into flashing or anything else yet. just been on xda site for a few days now reading all i could about rooting (which went fine, but now i'm screwed).

dirkyd3rk said:
If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
For the hell of it I did just that and it did bork it.... lmao

chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
Did it really? Lol It did it to me man I was pissed!

chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
man, for the life of me, i can't believe i didn't do a nandroid before i downloaded the app. for some reason i thought only downloading an app from the market, not flashing anything or whatever, would not screw up my phone.
anyway, since my data is lost, i wanted to try again. can i flash the unrevoked S-ON utility and then the latest Sprint RUU and then re-root? i read somewhere else that it won't remove my wimax/RSA keys or SD card, is that correct? is there a way to backup my RSA keys before I do anything else? should i do that, re-root, then nandroid, then mess with stuff? i basically wanted a stock Sprint EVO but one that's rooted so i can run root-based apps, that's what I want to get to.

Flash the Amon Ra recovery via the AR pc36img.zip file in hboot method, then reboot to recovery, do a full wipe/factory reset and try to boot to system.

[Q] Rooting Help

Hello
i m new to andriod
i have s-off my phone
Wildfire S (T-Mobile)
and i want to root it
but there are few question i want to know about
1-can i move unmoveable apps to sd card too?
2-if in case i brick it is there a easy way to unbrick it
thanks

information
RRRb50 said:
Hello
i m new to andriod
i have s-off my phone
Wildfire S (T-Mobile)
and i want to root it
but there are few question i want to know about
1-can i move unmoveable apps to sd card too?
2-if in case i brick it is there a easy way to unbrick it
thanks
Click to expand...
Click to collapse
if you use things like app2sd and link to sd yes you can put apps to sd. also you can get custom roms that have apps to sd already enabled.
and that depends on what kind of brick. if you get a soft brick, you can try to fix with a ruu, usually as long as you can get to the bootloader you are ok but if you get a hard brick your f***ed. you would need a jtag- used for modifying software on the chip- and they don't come cheap and are not much use without the knowledge of how to use it.
with that in mind though, hard bricks are usually quite hard to do. only times ive ever really heard of it happening is when people flash the wrong radio files or bootloader files. since you have s-off (i assume by xtc clip) be warned that your phone wont give you any warnings if something is wrong or will kill it, radio and bootloader wise.
but. if you are only rooting the odds of you bricking are low, allowing you follow guides properly ect. hope this helps you keep informed

thanks for the fast reply
well i have hacked my psp
like when installing custom firmware you should not press anything or remove the battery and connect anything with it
if you did it gets brick without that there are 5% chance it will brick
so mostly what are the reasons which cause andriod to brick
thanks a lot for helping though
and also can you send me the best rooting method too

the plan.
RRRb50 said:
thanks for the fast reply
well i have hacked my psp
like when installing custom firmware you should not press anything or remove the battery and connect anything with it
if you did it gets brick without that there are 5% chance it will brick
so mostly what are the reasons which cause andriod to brick
thanks a lot for helping though
and also can you send me the best rooting method too
Click to expand...
Click to collapse
well, most of the hard bricks come from flashing system stuff that is corrputed/for the wrong phone/ not built right. ect ect ect
with soft bricks it varys usually flashing stuff that then doesnt work is peoples most common mistake. alot of people think that theery brick there phone when they flash a new rom without deleting the caches ect and the get stuck in a boot loop.- a bootloop is where the phone gets stuck booting up an cannot get past it. easly recoverable
the best way to root for you is going to be by getting the clockworkmod recovery image, flashing it to your phone and then flashing the superuser script from the recovery.
so first download this http://forum.xda-developers.com/showthread.php?t=1213229 after youve downloaded this place it on the root (not int any folder) of your sd card.
then go to the bootloader (i assume you know how since you xtc clipped your device) and your phone should find the pg76img.zip then push the up button to flash it. that should be successful and the phone should reboot. after this go back to your bootloader, and scroll down (using the volume buttons) to recovery. select it and your phone should boot into clockworkmod recovery
now i suggest that you perform a nandroid backup. a nandroid backup is a complete copy of the system image, your rom/apps/contacts/txt messages, the lot. everything is copyied and saved as a backup, so if things go wrong you can always go back to it. i recommend you do a backup before you try anything, just so you can always roll back to it
so scroll down to backup and restore and select backup. make sure you have like 500mb of space on your sdcard just to be sure you have enough space.
after that you will want to go to here http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip and download that. same plan again, put it on the root of your sdcard and then go back to recovery.
this time select install zip from sdcard. (or something like that) then select CHOOSE zip. then choose the superuserzip you downloaded and select flash it. when this is done reboot the phone and wait for it to boot fully. when its done go into your list of installed apps and when you see the superuser app you will know your definatly rooted
discliamer as with everyone else here i take no responsibility if this kills your phone, slays a dragon, turns into a wizard or blows up into a neutron star lol but if you follow this guide you should be fine. pretty noob proof.

heavy_metal_man said:
well, most of the hard bricks come from flashing system stuff that is corrputed/for the wrong phone/ not built right. ect ect ect
with soft bricks it varys usually flashing stuff that then doesnt work is peoples most common mistake. alot of people think that theery brick there phone when they flash a new rom without deleting the caches ect and the get stuck in a boot loop.- a bootloop is where the phone gets stuck booting up an cannot get past it. easly recoverable
the best way to root for you is going to be by getting the clockworkmod recovery image, flashing it to your phone and then flashing the superuser script from the recovery.
so first download this http://forum.xda-developers.com/showthread.php?t=1213229 after youve downloaded this place it on the root (not int any folder) of your sd card.
then go to the bootloader (i assume you know how since you xtc clipped your device) and your phone should find the pg76img.zip then push the up button to flash it. that should be successful and the phone should reboot. after this go back to your bootloader, and scroll down (using the volume buttons) to recovery. select it and your phone should boot into clockworkmod recovery
now i suggest that you perform a nandroid backup. a nandroid backup is a complete copy of the system image, your rom/apps/contacts/txt messages, the lot. everything is copyied and saved as a backup, so if things go wrong you can always go back to it. i recommend you do a backup before you try anything, just so you can always roll back to it
so scroll down to backup and restore and select backup. make sure you have like 500mb of space on your sdcard just to be sure you have enough space.
after that you will want to go to here http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip and download that. same plan again, put it on the root of your sdcard and then go back to recovery.
this time select install zip from sdcard. (or something like that) then select CHOOSE zip. then choose the superuserzip you downloaded and select flash it. when this is done reboot the phone and wait for it to boot fully. when its done go into your list of installed apps and when you see the superuser app you will know your definatly rooted
discliamer as with everyone else here i take no responsibility if this kills your phone, slays a dragon, turns into a wizard or blows up into a neutron star lol but if you follow this guide you should be fine. pretty noob proof.
Click to expand...
Click to collapse
thnx alot
i will try this btw using the chrager is ok or not?

I used this rom when i rooted my Wildfire S using this root tool. It worked great! Try it. Hard-Bricks is pretty hard to get, and the chance is not so big.

Molleresa said:
I used this rom when i rooted my Wildfire S using this root tool. It worked great! Try it. Hard-Bricks is pretty hard to get, and the chance is not so big.
Click to expand...
Click to collapse
thnx i will see which seems easy
heavy_metal_man said:
well, most of the hard bricks come from flashing system stuff that is corrputed/for the wrong phone/ not built right. ect ect ect
with soft bricks it varys usually flashing stuff that then doesnt work is peoples most common mistake. alot of people think that theery brick there phone when they flash a new rom without deleting the caches ect and the get stuck in a boot loop.- a bootloop is where the phone gets stuck booting up an cannot get past it. easly recoverable
the best way to root for you is going to be by getting the clockworkmod recovery image, flashing it to your phone and then flashing the superuser script from the recovery.
so first download this http://forum.xda-developers.com/showthread.php?t=1213229 after youve downloaded this place it on the root (not int any folder) of your sd card.
then go to the bootloader (i assume you know how since you xtc clipped your device) and your phone should find the pg76img.zip then push the up button to flash it. that should be successful and the phone should reboot. after this go back to your bootloader, and scroll down (using the volume buttons) to recovery. select it and your phone should boot into clockworkmod recovery
now i suggest that you perform a nandroid backup. a nandroid backup is a complete copy of the system image, your rom/apps/contacts/txt messages, the lot. everything is copyied and saved as a backup, so if things go wrong you can always go back to it. i recommend you do a backup before you try anything, just so you can always roll back to it
so scroll down to backup and restore and select backup. make sure you have like 500mb of space on your sdcard just to be sure you have enough space.
after that you will want to go to here http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip and download that. same plan again, put it on the root of your sdcard and then go back to recovery.
this time select install zip from sdcard. (or something like that) then select CHOOSE zip. then choose the superuserzip you downloaded and select flash it. when this is done reboot the phone and wait for it to boot fully. when its done go into your list of installed apps and when you see the superuser app you will know your definatly rooted
discliamer as with everyone else here i take no responsibility if this kills your phone, slays a dragon, turns into a wizard or blows up into a neutron star lol but if you follow this guide you should be fine. pretty noob proof.
Click to expand...
Click to collapse
i just forgot one question
do i need to format the sd card or its ok without it?

It should be fine without formatting if its the one that came with the phone also what do you mean use the charger? A. Make sure the phone has full battery and b. If you mean for transferring the data to the sdcard then yes of course
Sent from my Wildfire using xda premium

You get it going pal?
Sent from my Wildfire using xda premium

heavy_metal_man said:
You get it going pal?
Sent from my Wildfire using xda premium
Click to expand...
Click to collapse
sorry
i was sleepy at that time
and i m going to collage now
i will try when i will come back

hey i tried to root and first time in the boot menu i was able to update it but it just keeps updating every time i go to bootmenu
and it dosnt go down so that i can select recovery please

Remove the SD card while you turn off the phone. Then go into recovery, insert the SD card while the phone is on.
Sent from my HTC Wildfire S A510e using XDA App

thanks a lot everyone i was able to root my phone and i can see the superuser app too
btw if i use a wrong app or not compatible custom rom or some other stuff will it cause my phone to brick

A hard brick is usually caused when you flash wrong bootloader or radio files.
A soft brick, usually caused by flashing wrong custom ROMs can be recovered easily.
Just read carefully before you do anything with your phone and you're good to go.

RRRb50 said:
thanks a lot everyone i was able to root my phone and i can see the superuser app too
btw if i use a wrong app or not compatible custom rom or some other stuff will it cause my phone to brick
Click to expand...
Click to collapse
good to hear mate. enjoy being rooted

heavy_metal_man said:
good to hear mate. enjoy being rooted
Click to expand...
Click to collapse
hey bro
can you send me a link to app which saves application data to sd card
like browser data etc

RRRb50 said:
hey bro
can you send me a link to app which saves application data to sd card
like browser data etc
Click to expand...
Click to collapse
i think alot of the app data is self contained tbh mate. do you mean so you can extract the data and use it on a different rom or like an app2sd type thing?

heavy_metal_man said:
i think alot of the app data is self contained tbh mate. do you mean so you can extract the data and use it on a different rom or like an app2sd type thing?
Click to expand...
Click to collapse
yeah app2sd
and btw which is xda app to post on forum

https://market.android.com/details?...mNvbS5xdW9vcmQudGFwYXRhbGt4ZGEuYWN0aXZpdHkiXQ.. that is the app, just sign in and your off. also http://www.appbrain.com/app/app-2-sd-(move-app-to-sd)/com.a0soft.gphone.app2sd try give this a bash. ive not used it so i dont know just what is needed to get it to go, you might need to formatt your sdcard but im sure the app will tell you.

ok thnx i will give it a try

HTC G2 White Screen with Andromadus ROM 1.1.2

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