• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Regaw Mod One Click Root

I am so bass ackwards, it sounds like. I took literally hours to get rooted. Waiting for device. Back and forth. Trying the one click and HTC unlock. Getting no where. And then, presto! It worked.
I did the Lazy Panda once, and I was good to go! Weird.
So since then, I have removed the red writing twice, upgraded my hboot, (right? )And now installed a Rom based upon the ota and installed the radios and firmware from the same.
What is next? New kernels?
 
Now I have an update message in my notification bar to update my OS from Sprint. Anyone know how to make this go away since updating will un-root and make re-rooting much more difficult? Not sure if this is the correct place for this post but it's not incredibly busy so I'm sure nobody will mind a question that's related and that others might have as well.
 
Now I have an update message in my notification bar to update my OS from Sprint. Anyone know how to make this go away since updating will un-root and make re-rooting much more difficult? Not sure if this is the correct place for this post but it's not incredibly busy so I'm sure nobody will mind a question that's related and that others might have as well.

Are you sure its not just the sprint app asking for an update?


If it is truely an ota update, just go to settings>system updates>HTC software updates> and uncheck the box to check for an update

You can also just flash the updated rom
 
As I mentioned elsewhere -

regaw_leinad at XDA said:
Also, we can block OTAs from installing by running
Code:
mv /system/etc/security/otacerts.zip  /system/etc/security/otacerts.zip.bak
That's how I did it back on the HeroC

Can also be done with EStrongs File Explorer.

Give Root Explorer privilege and mount /system r/w for writing. Long press file name, rename to add the .bak extension.
 
Are you sure its not just the sprint app asking for an update?


If it is truely an ota update, just go to settings>system updates>HTC software updates> and uncheck the box to check for an update

You can also just flash the updated rom

Yes, I'm sure.

None of what you suggested works. Unchecking the box does nothing because the update is still there even after a reboot and a reset.

As for updating the ROM, why would anyone want to do that? They would lose root and depending on what security changes the new ROM includes it may not be as easy as simply rooting again. Just blindly suggesting people do things could be dangerous for someone who doesn't understand root very well and is looking for help. If you don't know the answer maybe you shouldn't suggest solutions. I appreciate you trying to help but sometimes the help could be worse than the problem if you don't know what you're suggesting.

As I mentioned elsewhere -



Can also be done with EStrongs File Explorer.

Give Root Explorer privilege and mount /system r/w for writing. Long press file name, rename to add the .bak extension.

I didn't see that but will do it using the EStrongs method. Thanks!

Edit: it didn't work. I gave EStrong privilege and then mounted it and renamed. I then rebooted and the annoying message is still in the notification bar.
 
Go to recovery, clear cache and Dalvik, if it comes back then it's very likely that that's the PRL update they've been pushing. I got that this weekend.

And check your sd card partitions for any file named update.zip - and erase.

You can mount each sd card as usb storage from TWRP 2.2.0 and use your pc to search.
 
You can also just flash the updated rom

As for updating the ROM, why would anyone want to do that? They would lose root and depending on what security changes the new ROM includes it may not be as easy as simply rooting again. Just blindly suggesting people do things could be dangerous for someone who doesn't understand root very well and is looking for help. If you don't know the answer maybe you shouldn't suggest solutions. I appreciate you trying to help but sometimes the help could be worse than the problem if you don't know what you're suggesting.

I think you misunderstood what Rx was saying. Flashing the updated, rooted stock ROM found here at XDA is just like flashing any other ROM. When you flash that in conjunction with the radio linked in the OP of that thread, you get 99% of the updates that were pushed in the OTA. What you don't get is the updated hboot, which you don't want anyway.
You do NOT lose root by flashing it, you do NOT have to re-root or anything else.

Now, taking the OTA is wildly different than flashing the updated ROM. In that case, you definitely do lose root and the ability to s-off (for now).

Rx: apologies if I speak out of line or put words in your mouth.
 
Go to recovery, clear cache and Dalvik, if it comes back then it's very likely that that's the PRL update they've been pushing. I got that this weekend.

And check your sd card partitions for any file named update.zip - and erase.

You can mount each sd card as usb storage from TWRP 2.2.0 and use your pc to search.

Nope, not a prl it's 1.22.651.3 and I may do the updated ROM posted but there are a few people complaining of other issues being created and I'm not using Google Wallet yet so I may just skip for now. I wasn't able to find any other update.zip files so I'll clear the cache & dalvik and see what happens. I also need to update my TWRP so this is probably as good of a time as any I suppose.
 
I think you misunderstood what Rx was saying. Flashing the updated, rooted stock ROM found here at XDA is just like flashing any other ROM. When you flash that in conjunction with the radio linked in the OP of that thread, you get 99% of the updates that were pushed in the OTA. What you don't get is the updated hboot, which you don't want anyway.
You do NOT lose root by flashing it, you do NOT have to re-root or anything else.

Now, taking the OTA is wildly different than flashing the updated ROM. In that case, you definitely do lose root and the ability to s-off (for now).

Rx: apologies if I speak out of line or put words in your mouth.

That was exactly what I suggested. Flashing an updated Rom =\= taking the ota

You should never take an OTA while rooted. I'm on record all over this forum as well as xda saying that.
 
That was exactly what I suggested. Flashing an updated Rom =\= taking the ota

I apologize for my snarky reply then because I misread what you were suggesting. I took it to read you were suggesting I just accept the OTA when you said to update the ROM. I didn't read what you said as locate the updated ROM and manually install. Heck, I wasn't even aware it was available yet until post #113 that linked to the updated ROM.
 
OK, I am beating my head against the desk right now. This definitely isn't my first rodeo but after 3 hours of trying last night I still can't get this to work, once it reboots to recovery it sits there saying phone not connected. I have tried uninstalling and loading drivers all the different ways possible but nothing seems to work, anybody have an idea what is going on here?

On edit: I can't even get Sync to recognize the phone.
 
I apologize for my snarky reply then because I misread what you were suggesting. I took it to read you were suggesting I just accept the OTA when you said to update the ROM. I didn't read what you said as locate the updated ROM and manually install. Heck, I wasn't even aware it was available yet until post #113 that linked to the updated ROM.

No problem. The rooted flashable Roms are usually out the same day as the ota comes out.
 
OK, I am beating my head against the desk right now. This definitely isn't my first rodeo but after 3 hours of trying last night I still can't get this to work, once it reboots to recovery it sits there saying phone not connected. I have tried uninstalling and loading drivers all the different ways possible but nothing seems to work, anybody have an idea what is going on here?

On edit: I can't even get Sync to recognize the phone.
I'm not exactly sure of which point you are in the process, but did you check USB debugging back on after it booted and wiped the phone?
 
OK, I am beating my head against the desk right now. This definitely isn't my first rodeo but after 3 hours of trying last night I still can't get this to work, once it reboots to recovery it sits there saying phone not connected. I have tried uninstalling and loading drivers all the different ways possible but nothing seems to work, anybody have an idea what is going on here?

On edit: I can't even get Sync to recognize the phone.


Ok, did you put HTC Sync back to see what the deal was, or was it there all along?

HTC Sync and the old drivers I used for my 3D revolutionary worked fine for this on WinXP for me - but I lucked out on that combo.

If Sync was there all along, get rid of it.

If you're on Win 64-bit, then I think OstrichSak may help, he had USB driver issues holding him up and I think he used that rev of Windows.
 
Ok, did you put HTC Sync back to see what the deal was, or was it there all along?

HTC Sync and the old drivers I used for my 3D revolutionary worked fine for this on WinXP for me - but I lucked out on that combo.

If Sync was there all along, get rid of it.

If you're on Win 64-bit, then I think OstrichSak may help, he had USB driver issues holding him up and I think he used that rev of Windows.

Yeah, make sure you use the proper drivers for your PC's operating system via the Regaw post. Verify via the Device Manager that your device is communicating with your PC. I suggest using ONLY the drivers in Regaw's post because I thought I had the proper drivers too. It wasn't until I installed the drivers from Regaw's post that I had success. Also, make sure your device isn't in charge mode.
 
I'm not exactly sure of which point you are in the process, but did you check USB debugging back on after it booted and wiped the phone?

Yes, it was checked.

Ok, did you put HTC Sync back to see what the deal was, or was it there all along?

HTC Sync and the old drivers I used for my 3D revolutionary worked fine for this on WinXP for me - but I lucked out on that combo.

If Sync was there all along, get rid of it.

If you're on Win 64-bit, then I think OstrichSak may help, he had USB driver issues holding him up and I think he used that rev of Windows.

Thanks for the quick response EM, I just figured out the problem, it was either a faulty cable or it won't work through USB 3.0, can't say for sure which. I grabbed a cable I knew worked and plugged in to a USB 2.0 port and it worked flawlessly.

Don't you love it when it is stupid little things like that which kept you up till 3am?;):D
 
Yes, it was checked.



Thanks for the quick response EM, I just figured out the problem, it was either a faulty cable or it won't work through USB 3.0, can't say for sure which. I grabbed a cable I knew worked and plugged in to a USB 2.0 port and it worked flawlessly.

Don't you love it when it is stupid little things like that which kept you up till 3am?;):D

I was just on my way over to post because it hit me to check the cable, lol. :D

And yep, when Granite1 went for the s-off method, USB 3 bit him in the rear as well.

I think we need to get a USB 3 warning out there... hmmmmmm.
 
Yes, it was checked.



Thanks for the quick response EM, I just figured out the problem, it was either a faulty cable or it won't work through USB 3.0, can't say for sure which. I grabbed a cable I knew worked and plugged in to a USB 2.0 port and it worked flawlessly.

Don't you love it when it is stupid little things like that which kept you up till 3am?;):D
Heh, I had cable issues when doing the LazyPanda s-off :p Glad you got it figured out and rooted though!
 
Back
Top Bottom