Develop Bugs

Rooted, didn't do OTA update, Can I stop the nagging?

I figured I'd start a post for this since some people probably don't want to update after doing the root process, or maybe it would break root.
Is there a way to delete the OTA update off your phone and stop it from downloading it again and nagging you to update?

you could always root after updating since it obviously doesn't stop you from rooting

jonnybueno said:
you could always root after updating since it obviously doesn't stop you from rooting
Click to expand...
Click to collapse
I know, but I had a hell of a time getting done so I don't want to go though it again. It took a long time to get adb running in recovery, after that it was cake.

Think I found it, did its like the droid. Dunno if it will stop the updates yet, but still need to find the file it downloaded.
Went to
/system/etc/security/
renamed otacerts.zip to otacerts.bak
Anyone install the OTA update after doing root? Did it break it?
I would do it but, I already done this twice now and it was hard as hell to get shell in recovery
Damn whenever I reboot it goes back to .zip

TNS201 said:
Think I found it, did its like the droid. Dunno if it will stop the updates yet, but still need to find the file it downloaded.
Went to
/system/etc/security/
renamed otacerts.zip to otacerts.bak
Anyone install the OTA update after doing root? Did it break it?
I would do it but, I already done this twice now and it was hard as hell to get shell in recovery
Damn whenever I reboot it goes back to .zip
Click to expand...
Click to collapse
Unfortunately, even if it stuck, renaming otacerts.zip causes horrible battery life. It will continuously download the update, over, and over. It will download it, check the certs to see if its good. See its bad, go again, and again...
XC

xcsdm said:
Unfortunately, even if it stuck, renaming otacerts.zip causes horrible battery life. It will continuously download the update, over, and over. It will download it, check the certs to see if its good. See its bad, go again, and again...
XC
Click to expand...
Click to collapse
Yea well it doesnt stop it anyway, it already downloaded the file.
I wonder if theres any other way to stop it from nagging.

Much simpler to do the update and then reroot.
via my dinc...

krelvinaz said:
Much simpler to do the update and then reroot.
via my dinc...
Click to expand...
Click to collapse
Will it kill my root, I got superuser.apk installed already and that functions properly, will the OTA mess up anything?

don't know. I don't know anyone else that is doing what you are doing.
Re-rooting isn't that hard. I've done it 10-12 times before there was a way to make it stick. Just a little typing assuming you get access.
Chances are you may re-root again anyways as they come out with better packages to do it.

TNS201 said:
I figured I'd start a post for this since some people probably don't want to update after doing the root process, or maybe it would break root.
Is there a way to delete the OTA update off your phone and stop it from downloading it again and nagging you to update?
Click to expand...
Click to collapse
I'm not rooted yet so I can't say for certain, but you can almost certainly shut down auto-OTA check by editing the build.prop and or userinit.sh in /system. Those two files control most of the automation on your Droid! Good luck, and if I helped you, send me a 16gig SDcard so I can root too

i just deleted the otacerts.zip in /system/etc/security/ and now it says my system is up to day in about phone.

I can confirm that running the OTA after rooting will temporarily break root. You *will* have to redo the adb in recovery > payload before your root apps or superuser.apk will work again.
The good news is that you *can* simply redo it. No big deal once you are comfortable getting into adb in recovery.

crappypunk said:
i just deleted the otacerts.zip in /system/etc/security/ and now it says my system is up to day in about phone.
Click to expand...
Click to collapse
Still not sure why you went this way.
Unless you installed Superuser recently, you don't have that much "root" and will need to do it all over eventually again anyways.
It would be a lot simpler, if you did the OTA first, then re-root your phone using the newer instructions which give you a more rooted SAFER setup.
If you didn't do the newer Superuser, you now have a potentially vulnerable phone that an app can exploit because they can do su and not need approval first.

krelvinaz said:
Still not sure why you went this way.
Unless you installed Superuser recently, you don't have that much "root" and will need to do it all over eventually again anyways.
It would be a lot simpler, if you did the OTA first, then re-root your phone using the newer instructions which give you a more rooted SAFER setup.
If you didn't do the newer Superuser, you now have a potentially vulnerable phone that an app can exploit because they can do su and not need approval first.
Click to expand...
Click to collapse
I tried rooting my phone since the day root was achieved using a few different sd cards I have and failed every time. Last night I decided to downgrade and got my phone rooted on the first try. I'm no noob. I've established ADB on my HTC Vogue which is a WinMo phone running Android, I've rooted a My Touch 3G and a Hero but until I downgraded my phone I couldn't get root. At least not with my sd cards so for me running the OTA then rooting is just not an option. I will just deal with it until NAND write access is achieved.

krelvinaz said:
Still not sure why you went this way.
Unless you installed Superuser recently, you don't have that much "root" and will need to do it all over eventually again anyways.
It would be a lot simpler, if you did the OTA first, then re-root your phone using the newer instructions which give you a more rooted SAFER setup.
If you didn't do the newer Superuser, you now have a potentially vulnerable phone that an app can exploit because they can do su and not need approval first.
Click to expand...
Click to collapse
Some of us are not able to easily get into adb shell, often taking days of trying (hundreds of reboots). I was finally able to get in, and don't ever want to have to do it again. I have wifi tether working, and that is plenty for me until they come up with an easier way to get into adb shell in recovery. I am assuming this guy is in the same boat (as far as how hard it is to get into adb shell).

It won't matter soon. Wait until the Unrevoked custom recovery comes out in a few days and then you can find a nice custom rom that won't bug you.
-------------------------------------
Sent via the XDA Tapatalk App

I have pre order version and so far its been great. When the ota came to me I clicked install and it errored out...it has Not prompted me a single time since and everything has been perfect and I'm rooted...any thoughts on this?
-------------------------------------
Sent via the XDA Tapatalk App

askwhy said:
I can confirm that running the OTA after rooting will temporarily break root. You *will* have to redo the adb in recovery > payload before your root apps or superuser.apk will work again.
The good news is that you *can* simply redo it. No big deal once you are comfortable getting into adb in recovery.
Click to expand...
Click to collapse
Yeah if it were only true, but cannot get back into adb recovery unless i down grade, now what?

PDAnuby said:
Yeah if it were only true, but cannot get back into adb recovery unless i down grade, now what?
Click to expand...
Click to collapse
Doesn't matter now. You should be able to start flashing ROMs soon with the Recovery Reflash tool from Unrevoked http://unrevoked.com/recovery/
Those Unrevoked guys are really hooking us up

I too had an incredibly hard time getting into the shell... I finally down graded, was able to get in (I don't' think that got me in, as it all ended up in being timing that I just had to get).
anyways, i've now installed the unrevoked recovery tool and updated to the latest clockwork via rom manager.
Anyways... that nag screen is getting old, so which rom are people installing on their systems that's getting rid of the nag / is an updated one?
I do NOT want to have to go through the root process again, what a pain it was for me...

Unrevoked 1-click apk defeated in recent update?

My Evo is doing fine, but I was trying to help a friend root his yesterday and the Unrevoked 1-click apk didn't appear to be doing the trick. The only difference I can think of between our two phones is that I haven't downloaded the update that came this week. Has Sprint defeated this root method in the most recent patch?

Yes...they are up to UnrEVOked 3.

chazglenn3 said:
Yes...they are up to UnrEVOked 3.
Click to expand...
Click to collapse
Right, this method requires you to use a PC though, right? I'm wondering if its still possible to root it using the unrevoked on-phone application, or has this been defeated? And if so, was the defeat in the most recent patch?

bump. I'm afraid the answer given is still a bit unclear to me. Can someone please clarify?

Make sure you are going to 'unrevoked.com/m' if you want to use it on your phone and avoid having to use the pc method. I forgot the /m when I first tried it and got pretty confused as well.

ashbare said:
Make sure you are going to 'unrevoked.com/m' if you want to use it on your phone and avoid having to use the pc method. I forgot the /m when I first tried it and got pretty confused as well.
Click to expand...
Click to collapse
Yes, this is exactly what I did. The apk downloaded and installed, but didn't appear to gain root when I ran it. I ran it several times, but every time I attempted to run wifi tether, it would say that I wasn't root.

You can try downloading the Simple Root app from the development forum, Its only 4 clicks and its a legitimate full root. It does require the PC, but you seem to know how to use one of those as you got to this website.
Don't take shortcuts because your not sure what you're doing, learn

Mast3rpyr0 said:
You can try downloading the Simple Root app from the development forum, Its only 4 clicks and its a legitimate full root. It does require the PC, but you seem to know how to use one of those as you got to this website.
Don't take shortcuts because your not sure what you're doing, learn
Click to expand...
Click to collapse
Thank you for the reply. I'll probably end up Simple Root for myself, but this is for a somewhat elderly friend of mine. He only needs root for wifi tether, since he can't get broadband where he lives (3g is okay). I figured the apk root method would be suitable for him since he would know how to uninstall it if he needed to claim is warranty or something. I won't be around to support his phone for him.
Anyway, thanks again. I'm still learning myself and appreciate the advice.

Ahh ok, he can always hit the wipe button and it will go back to a state good enough for the average sprint rep.

I Installed unrevoked 3by usb because i got last version 147.651.1. Its anyway to unroot and get back to stock rom. I tried different ways and nothing for example i wiped data, hard reset . etc.
Right now i dont have wifi is unable and that why i would like get back to stock. Also i use the method with htc sync and the ruu 132.651.1 andgive me error 171 then reintall the ruu give me error 140 and boot to the main screen/
Please any solution to get back to stock .
thanks in advanced,

PSA: Rooting methods and recently discovered dangers

To senior Mytouch 4gers:
Let's just start recommending the root.sh/visionary method to beginners and people who haven't rooted yet. It might not be the rooting method that causes issues but so far it looks like it plays a role in it. only gfree rooters have had this issue so far, so let's stay on the safe side, huh? just link this thread: http://forum.xda-developers.com/showthread.php?t=834225 and we can notify people later on about whether or not they should use gfree, as it's easy to use even after the root.sh method.
UPDATE:
It turns out that the rooting method may have little to no effect on this issue. Please read the bottom past the "update" title
Most of my data here will be pulled from http://forum.xda-developers.com/showthread.php?t=1074922 and similar threads.
Many of you probably have already read about this, but it has been becoming more and more common for people to get errors in recovery saying that certain partitions cannot be mounted, usually data and/or cache. The issue is that they cannot be re-formatted in recovery because the recovery partition is messed up as well.
Some people escape this using PD15IMG, but about 50% hit another error - Fail-PU in hboot when trying to use this. The only recovery here is available if you have the engineering hboot (Which at this point i would highly recommend you flash). without it, the phone is effectively bricked (I know, i know, not really bricked if you can get to hboot, but it's to the point that there is no recovery and the phone is unusable.)
We have narrowed it down to this: these errors only happen to people who used the gfree method to root. one (convincing) theory was posted in the previously linked thread by xdviper:
xdviper said:
Alright well I've been reading logs from G2_Root channel from April 26th and so on, and it looks like the G2 has two different types of the emmc chip. Gfree powers off this chip and then initializes the chip again in order to get around the write protection. I remember before we had root access on the G2 (before I traded for a mytouch) I would lurk around the irc channel and read progress. I remember having to get the chip to power on in order to get around the write protection.
Now it looks like while the phone is being used, or booting up and or trying tto read or write from emmc the chip suddenly dies. This is what causes us to get force closes, freezes and not being able to get past the splash screen and also explains the recovery not being able to mount partitions.
We're going to need people to join in the G2 channel preferably ones who still have their defective phones to get some data off it.
Again, this is a very vague summary of what I've been able to read off the irc logs.
Why the G2? Because we're using the same gfree method to root our phones and with our phones dying it makes sense.
I think, they have already ruled out recovery and the Eng hboot to be culprit but this is just too early in the game to determine.
Here's a thread from the G2 side, if anyone still has this problem with their cache not being to mount please check out post #13.
I'll look.around more and see what I find from the G2 side.
http://forum.xda-developers.com/showthread.php?t=1039504
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
In addition to (Hopefully) discovering the issue, we believe we have something you can do to lower your chances of being afflicted by this issue. IF you use the gfree method, reflash recovery a couple times, and hopefully it will work correctly. If you are not in need of a sim unlock, carrier unlock, whatever gfree does, use the visionary method with root.sh. At this point there are no documented cases of these issues happening with users that used that method.
Root.sh method:
http://forum.xda-developers.com/showthread.php?t=834225
Thanks for reading, have fun and be safe!
Mod: I feel it would be beneficial if this thread was stickied.
UPDATE
It turns out that the rooting method may have little to no effect having this issue, in a quote from Guhl99:
guhl99 said:
Hi !
After analyzing this issue a lot and also discussing this with scotty2 on #G2ROOT yesterday I would like to say that we can see no way how gfree could be causing this issue that effects the G2/DZ/DHD/MT4G.
We see that it seems to effect people that used gfree to radio S-OFF and root the phone but this is very likely only an statistical effect as gfree is the most used rooting method now.
The only thing that we know fur sure (or at least with a very very high probability) is that only emmc chips with the name M4G2DE are effected. You can find the name of your emmc chip by using the following command (in a terminal or adb shell):
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
To be sure that you really are effected by the emmc issue (and not other partition corruption issues that show similar symptoms) you have to look at the kernel messages when booted to clockworkmod recovery. Do to this boot the phone into recovery and then (in and adb shell) issue the following command:
Code:
cat /proc/kmsg | grep mmc0
or
Code:
dmesg | grep mmc0
If you see output like (not necessarily in this order) :
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
then you are effected by this issue.
Basically the emmc chip does not initialize any more after the first attempt to access it in write mode.
Based on our current knowledge this is a hardware issue and can not be cured. We will keep investigating this issue and welcome everybody to discuss it on #G2ROOT.
Have fun - Guhl
Click to expand...
Click to collapse
I looks like M4G2DE is the bad one and SEMO4G is the good one. We don't have any cases of other ones, but please post yours if it is different. Keep in mind we still aren't 100% sure about this being the cause, but it's very probable, as a logcat on booting in to recovery shows this chip dying. Also be aware that this is a hardware issue, no software can fix this. you have the bad one or you don't.
Also, it would be nice if when you post you would list these things:
1. what method of rooting you used
2. which version of hboot do you have
3. which emmc chip serial do you have
4. have you encountered this issue before
Let's not throw away the idea that the rooting method still plays a big role in this issue! please post any information you have about the partition errors and FAIL-PU errors! All information is welcomed!

If we're still not sure why it's happening, then how do we know reflashing recovery a couple times will fix it? The cause is still unknown, right? Cuz I've gfree'd several Glaciers and haven't encountered this problem.

i personally do not trust auto-rooting. I did the visionary and root.sh way of rooting and have engineering bootloader and have not had a single issue.

Wow lucky I read this. I need to SIM unlock my phone. Should I wait till this issue has been figured out? I am afraid I might brick my MyTouch 4G. I am not with T-Mobile and also not in the US, bought the phone off ebay, so can't really call them to get unlock code. Do i have any other options?

dacquesta1 said:
i personally do not trust auto-rooting. I did the visionary and root.sh way of rooting and have engineering bootloader and have not had a single issue.
Click to expand...
Click to collapse
Same here. Root.sh all the way.
Here is the method I used. Very similar to grankin's linked to in the OP, but slightly more simple: http://forum.xda-developers.com/showthread.php?t=858021. Follow that and you'll be fine.

Good to know! I rooted via the root sh method and have been considering doing gfree, not now!
Sent from my MyTouch4G running RoyalGinger 2.0

dacquesta1 said:
i personally do not trust auto-rooting. I did the visionary and root.sh way of rooting and have engineering bootloader and have not had a single issue.
Click to expand...
Click to collapse
So thats a no on auto rooting. for me.

clem2595 said:
So thats a no on auto rooting. for me.
Click to expand...
Click to collapse
Unless you need SIM unlock I would highly recommend the root . sh method. Go to theunlockr.com there is a very simple video guide in the "how to's" section.
Sent from my MyTouch4G running RoyalGinger 2.0

Towle said:
Unless you need SIM unlock or are planning on flashing radios I would highly recommend the root . sh method. Go to theunlockr.com there is a very simple video guide in the "how to's" section.
Click to expand...
Click to collapse
I know that the root.sh method isn't "true" S-OFF and that the radio's security flag is still technically "on", but does that mean you aren't able to flash new radios after rooting that way?

I didn't use gfree, just root.sh, and I've flashed 4 radios no problem...
Sent from my HTC Vision using XDA App

No issue flashing radios here. Never a single issue flashing roms radios recoveries anything.
Sent from my HTC Panache using XDA Premium App

TeeJay3800 said:
I know that the root.sh method isn't "true" S-OFF and that the radio's security flag is still technically "on", but does that mean you aren't able to flash new radios after rooting that way?
Click to expand...
Click to collapse
I've flashed a couple radios and I rooted the visionary/root.sh method. If I'm not supposed to be able to, I guess I got lucky.
Sent from my HTC Glacier using XDA App

It's still not clear whether you're "supposed" to be able to flash radios or not, but it seems to be working for everyone that has rooted with root.sh. I'll just blame you guys if I brick my phone.

Sorry very bad wording on my part.
I guess I should have said radio s-off
Onefast said:
I didn't use gfree, just root.sh, and I've flashed 4 radios no problem...
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my MyTouch4G running RoyalGinger 2.0

rooting the visionary method gives radio s=off...mine has been like that since i rooted and i have flashed all four radios and countless ROMs

dacquesta1 said:
rooting the visionary method gives radio s=off...mine has been like that since i rooted and i have flashed all four radios and countless ROMs
Click to expand...
Click to collapse
Do I have the fastboot commands correct here?

I also used the unlocker how to and worked great. Uses visonary and root. sh
Reply via MT4G Royal Ginger 2.0 on the #1 android forum app- XDA

TeeJay3800 said:
Do I have the fastboot commands correct here?
Click to expand...
Click to collapse
truthfully i do not know. i don't use command lines to flash anything. i just put radio images on the root of my sd card and go into the bootloader and flash it there and i flash roms from recovery...never any issues.

I have gotten this error for the second time on the same device...the first time I recovered by flashing a 2.x.x.x CWM in EBL and the formating cache in the old recovery, reflashing CWM 3.0.2.4 in EBL and I was all set after restoring a NANDroid. BUt the second I got the error I have tired everything so far and nothing gets it to go away, I cant even flash the old CWM in EBL I get an error in adb

Hey to all of you that are saying we don't really know the solution, im aware of that. The reflashing of recovery is merely the most we can do at this point. it won't save you, but it's a theory that can't hurt to try.
Sent from my HTC Glacier using XDA App

Running into an issue regarding recovery.

I like to think I am rather educated in regards to how to root and all that. I just got my replacement Evo today and of course it is updated to 2.3.3. So I can't use unrevoked, but I was hoping to flash over to a older backup I made on 2.2 on my old phone.
Except, when I do the whole hold the volume down + power button and eventually choose recover, all that happens is a image of a phone and a exclamation point appears and it never leaves here.
I know in order for me to be able to use ClockwordMod I need to root the phone, which can't happen on 2.3
So what are my options? How do I flash over my old rom???? Even if it doesnt let me get back to 2.2 its still better than redownloading all my apps.

Rapture Veteran said:
I like to think I am rather educated in regards to how to root and all that. I just got my replacement Evo today and of course it is updated to 2.3.3. So I can't use unrevoked, but I was hoping to flash over to a older backup I made on 2.2 on my old phone.
Except, when I do the whole hold the volume down + power button and eventually choose recover, all that happens is a image of a phone and a exclamation point appears and it never leaves here.
I know in order for me to be able to use ClockwordMod I need to root the phone, which can't happen on 2.3
So what are my options? How do I flash over my old rom???? Even if it doesnt let me get back to 2.2 its still better than redownloading all my apps.
Click to expand...
Click to collapse
there is no root yet for the 2.3.3, their working on it. sorry

dased14 said:
there is no root yet for the 2.3.3, their working on it. sorry
Click to expand...
Click to collapse
so there is no way possible for me to recover without rooting?
I still have to do update the drivers on the phone (device manager, installing the unrevoked drivers...unless i need to be rooted for this as well)
so even then I still cant use the recovery option? whats the point of it? HTC doesnt want you rooting, hence 2.3 being stock on Evos, but yet they include the recovery option on their phones which you seemingly cant use...unless...you...root? im confused. Unconfuse me please

Rapture Veteran said:
so there is no way possible for me to recover without rooting?
I still have to do update the drivers on the phone (device manager, installing the unrevoked drivers...unless i need to be rooted for this as well)
so even then I still cant use the recovery option? whats the point of it? HTC doesnt want you rooting, hence 2.3 being stock on Evos, but yet they include the recovery option on their phones which you seemingly cant use...unless...you...root? im confused. Unconfuse me please
Click to expand...
Click to collapse
Rooting doesnt exactly let you use recovery.
The stock recovery from HTC is basically nothing.
When you do full root. It gives you the ability to install unsigned apps. That is what s-off means (security off). So the bootloader doesnt check to see what your installing is signed by HTC.
So therefore.
1. Root
2. Install custom recovery.
Now some automated root apps (unrevoked) do the whole process for you.
If you root by adb. You would be rooting and installing a custom recovery seperately, if you actually knew what the adb codes were and not just following a tutorial.
You can root and still have no recovery. Root doesnt mean custom recovery. They are two seperate things.
So even though the recovery option is there it is unuseable. Until you root. Then you can get a custom recovery...hope this helps
Sent from my PC36100

Rapture Veteran said:
so there is no way possible for me to recover without rooting?
I still have to do update the drivers on the phone (device manager, installing the unrevoked drivers...unless i need to be rooted for this as well)
so even then I still cant use the recovery option? whats the point of it? HTC doesnt want you rooting, hence 2.3 being stock on Evos, but yet they include the recovery option on their phones which you seemingly cant use...unless...you...root? im confused. Unconfuse me please
Click to expand...
Click to collapse
At this time no. I think its more of a way to get you to buy the next thing from them. If devs keep making the phone feel fresh and new, how long would you wait to upgrade(just my take on it). I believe recovery is there for their developers and carriers developers(to add their bloat) again just my take. Give the devs here sometime and i'm sure they'll find a way to get root back.
Brought to you by the little voices in my head

r.storm85 said:
Rooting doesnt exactly let you use recovery.
The stock recovery from HTC is basically nothing.
When you do full root. It gives you the ability to install unsigned apps. That is what s-off means (security off). So the bootloader doesnt check to see what your installing is signed by HTC.
So therefore.
1. Root
2. Install custom recovery.
Now some automated root apps (unrevoked) do the whole process for you.
If you root by adb. You would be rooting and installing a custom recovery seperately, if you actually knew what the adb codes were and not just following a tutorial.
You can root and still have no recovery. Root doesnt mean custom recovery. They are two seperate things.
So even though the recovery option is there it is unuseable. Until you root. Then you can get a custom recovery...hope this helps
Sent from my PC36100
Click to expand...
Click to collapse
well thats not what i wanted to hear. any clue as to how far off unrevoked is to finally cracking this 2.3?

dased14 said:
At this time no. I think its more of a way to get you to buy the next thing from them. If devs keep making the phone feel fresh and new, how long would you wait to upgrade(just my take on it). I believe recovery is there for their developers and carriers developers(to add their bloat) again just my take. Give the devs here sometime and i'm sure they'll find a way to get root back.
Brought to you by the little voices in my head
Click to expand...
Click to collapse
i truly hope so. ive been spoiled by CM7. I like to run juicedefender ultimate on CM7 during my work days where im not around a plug and ill be at over 85% on a 15 hour day. on stock HTC 2.3 with the same juicedefender settings running on the same 15 hour day, im down to 50% or lower sometimes. i can live without root for now. the biggest negative is I just cancelled the Sprint hotspot because of CM7.
can you even run the hotspot on stock sense if you aren't paying for it like you could on a root?

Rapture Veteran said:
i truly hope so. ive been spoiled by CM7. I like to run juicedefender ultimate on CM7 during my work days where im not around a plug and ill be at over 85% on a 15 hour day. on stock HTC 2.3 with the same juicedefender settings running on the same 15 hour day, im down to 50% or lower sometimes. i can live without root for now. the biggest negative is I just cancelled the Sprint hotspot because of CM7.
can you even run the hotspot on stock sense if you aren't paying for it like you could on a root?
Click to expand...
Click to collapse
No you have to be rooted to run either Sprint Hotspot or Wireless Tether.
No ota on root yet. But im sure they are working on it...
Sent from my PC36100

[Q] Running into problem following root guide

Hello. The guide I'm following is found at http://forum.xda-developers.com/showthread.php?t=2221039. I'm following it character for character short of where the thread has corrections to some errors.
My end goal is getting CM7.2 on this thing and having a rooted phone. My question is basically "What do I do when I'm experiencing the following?"
When I get to:
•fastboot flash zip firmware.zip under step 7 I end up with a FAILED (remote: 41 model id check fail)
Everything prior to this point is going exactly as it should as far as I can tell. There are no other errors of any kind. When I continue through the process after this failure I end up at:
•adb shell /tmp/gfree -f under step 8
This is where the second failure occurs which I imagine is due to the firmware issue. It ends up with a bunch of lines showing things happening and then comes to:
Attempting to power cycle eMMC... Failed.
Module failed to power cycle eMMC.
These are the only issues I'm having with this guide and can't seem to figure it out. Unfortunately I can't ask on that thread because I'm under the 10 post mark as I've tried to read instead of ask questions. At this point I'm just stuck though. As of now I'm trying to flash CM7.2 using CWM as the rooted stock rom is done in that guide. So far I'm having no luck though. I'm glad I'm using this as a test dummy before getting a newer phone and attempting anything on it. Any help that can be provided is greatly appreciated. I'd love to get this sorted out.

bhd1223 said:
•adb shell /tmp/gfree -f under step 8
This is where the second failure occurs which I imagine is due to the firmware issue. It ends up with a bunch of lines showing things happening and then comes to:
Attempting to power cycle eMMC... Failed.
Module failed to power cycle eMMC.
Click to expand...
Click to collapse
From what I have read gfree works for Android 2.2.1 and you do realize if you the hboot version is correct you can just unlock at htcdev.com and flash the rom. Thats what werked for me.

lamebmx said:
From what I have read gfree works for Android 2.2.1 and you do realize if you the hboot version is correct you can just unlock at htcdev.com and flash the rom. Thats what werked for me.
Click to expand...
Click to collapse
Thanks. Actually, just after I posted that I tried to load CM 7.2 in the same way that it directed to load the rooted stock ROM in the guide. This was after using the HTC Dev Unlock. Then I discovered I needed to have 4.0+ to stream video from an app I was using. The night after that I ended up going with an Unofficial CM 10.1 port for Ace devices and making it think it was an Inspire 4G again (http://forum.xda-developers.com/showthread.php?t=2093845).
A little wonky at random times, probably hardware related, but works really well and allows me access to things I wouldn't otherwise have. I was really concerned about running non-final release or "stable" labeled ROMs which has had me holding off on getting a newer phone. After running this build for a few days which is based off a nightly, I see no reason to worry. It seems a simple process to do all this stuff although I'm sure the actually programming is more difficult.
Basically, the only thing I'm left without is S-Off. From further reading I've done this doesn't even really matter anymore. I can load custom ROMs, I can gain su access, I can do anything I want to the phone as far as I can tell. I'm happy with it is unless there is some secret of awesomeness I'm unaware of that I've yet to tap.

bhd1223 said:
Basically, the only thing I'm left without is S-Off. From further reading I've done this doesn't even really matter anymore. I can load custom ROMs, I can gain su access, I can do anything I want to the phone as far as I can tell. I'm happy with it is unless there is some secret of awesomeness I'm unaware of that I've yet to tap.
Click to expand...
Click to collapse
I just got S-OFF with this guide:
http://forum.xda-developers.com/showthread.php?t=2367322
using the proper PD98IMG.zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2193681
FYI it downgrades you in the process and I have not got my phone to boot yet, but im 99% sure its cuz i have not done the upgraded RUU from the first thread (JB probably does not like GB radio etc) but unlocked and S-OFF leaves it where you should be able to fix it.

lamebmx said:
I just got S-OFF with this guide:
http://forum.xda-developers.com/showthread.php?t=2367322
using the proper PD98IMG.zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2193681
FYI it downgrades you in the process and I have not got my phone to boot yet, but im 99% sure its cuz i have not done the upgraded RUU from the first thread (JB probably does not like GB radio etc) but unlocked and S-OFF leaves it where you should be able to fix it.
Click to expand...
Click to collapse
Thanks lamebmx. I was having a boot issue as well when I first installed CM7.2. Then I learned that each ROM needs to have it's own boot image flashed to the boot partition. After that no issues. When I did 10.1 I used the boot image from that as well and haven't had any issue with booting. You may have done that already but it can't hurt to re-flash if you already did, or do it if you haven't.