• 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

dustwun77 said:
Speaking of nandroid backups, I don't know where is the best place to put this question, does TWRP allow you to rename your backups? and if so, what format is acceptable?
Click to expand...

Yes.

Your backups will be under /sdcard/TWRP/BACKUPS/HT25FS409294 (if you chose to backup to the internal sd card - and if there's some variation in the HTxxxxx, don't worry).

As you can see, they will have names like: 2012-06-18--02-27-58

You can name them as you wish, use a dash instead of a space and no dots to be on the safe side. I named my first one original-original and I have another called orig-charmeleon from when I flashed that rom.
 
takirb said:
I was weary as well about using TWRP recovery, but it's worked ok for the little bit that i've used it so far. I did get an odd error trying to mount something when i restored a backup this evening, but it worked so i can't complain. I can shoot you the driver package i used when i rooted mine last week if it'll help, not sure if Regaw changed something between now and then. For his method, i was using a Win7 x86 PC.
Click to expand...

The restore error comes from a known bug trying to mount the sd card at the end of the restore.

As I recall, uncheck the option in the middle of the screen with no text to get rid of the nagging at the end. Either way, the error report is harmless on the final mount.
 
I wasn't sure if it had something to do with mounting the SD card in general, or if it was assuming I had my card partitioned like in the A2SD days of the original Evo and was giving an error. I tried sifting through the System log under TWRP but that would've taken forever with the standard text editor in ES File Explorer.

Thanks for clearing it up! My heart skipped a beat when i saw an error while attempting to restore :(
 
does anybody know if this is the reason my splash screen now has a do not distribute message from htc? or is that coming from someplace else?
 
jackgibbs said:
does anybody know if this is the reason my splash screen now has a do not distribute message from htc? or is that coming from someplace else?
Click to expand...

I don't know who spilled those beans or at what point we got that, but I'll bet you dollars to donuts that it's why we can flash anything from recovery. Just a guess, but anyway, so far as I know, that came along with this process.
 
jackgibbs said:
does anybody know if this is the reason my splash screen now has a do not distribute message from htc? or is that coming from someplace else?
Click to expand...

I didn't notice that until after I used this particular method and it authenticated through HTC Dev Unlock. I don't think it was there after the Linux/Mac/Windows root method (which doesn't contact HTC Dev Unlock site), just a *tampered* mark on the bootloader. Once i used Regaw's root method, I noticed the "Do Not Distribute" tag on the splashscreen, as well as "unlocked" on the bootloader.
 
Ok, this sounds plausible to me, from a trusted dev at Disclaimer on HTC Splash Screen - xda-developers

-viperboy- at xda-developers.com said:
I think this doesnt happen from unlocking the bootloader, I think its from flashing recovery. I think the bootloader checks to see if partitions are signed or unsigned when it boots. Because we don't have HTCs key to sign the recovery partition, I think the bootloader is seeing that a partition is missing a signature and then assuming its a development build. Most of the development builds contained unsigned partitions.
Click to expand...
 
Hey guys, about the driver issues. If you had any drivers previously installed, I'd use the Uninstall Program control panel feature, uninstall them and then install the drivers linked in my rooter thread. Still, I am developing a better way to check for installed drivers (other than looking for the ANDROIDUSB.sys file in your system32 folder) using Windows Management queries, but if you already got this working there would be no need to run it again once I come out with another update. Everything I update from here on will either be only internal code for the rooter to run better, or updating when they build a new version of TWRP.
I recommend TWRP, yes there was a few incidents on the OG Evo with a SEMI brick, and reverting back to S-ON somehow, but that has definitely since been cleared up in the newer builds.

Regarding the HTC development splash that comes up, yes it does pop up when you flash a recovery, but the actual reasoning behind it is the bootloader does a signature check of every partition on boot, and if it finds an unsigned partition (aka the custom recovery you just flashed) it puts that over the splash screen. Until we find a way to write to the partition where that code is located (right now we can read it for dayz ;) ) that'll have to stay.

Edit: And in case you all are wondering what **TAMPERED** means, it is the result of the checksum of the /system partition by the bootloader on boot. Since we added the Superuser.apk, su, and installed busybox in the root method, that changes the checksum (most likely md5 or sha1 used) of the partition as a whole, thus displaying that message.

EDIT2: Oh, and I saw the other day that I had **SECURITY WARNING** or something similar pop up after a relock. I believe that is because the bootloader is technically locked still, AND it senses an unsigned partition (the custom recovery). I haven't looked into this much, but that's my best educated guess.
 
regaw_leinad said:
Hey guys, about the driver issues. If you had any drivers previously installed, I'd use the Uninstall Program control panel feature, uninstall them and then install the drivers linked in my rooter thread. Still, I am developing a better way to check for installed drivers (other than looking for the ANDROIDUSB.sys file in your system32 folder) using Windows Management queries, but if you already got this working there would be no need to run it again once I come out with another update. Everything I update from here on will either be only internal code for the rooter to run better, or updating when they build a new version of TWRP.
I recommend TWRP, yes there was a few incidents on the OG Evo with a SEMI brick, and reverting back to S-ON somehow, but that has definitely since been cleared up in the newer builds.

Regarding the HTC development splash that comes up, yes it does pop up when you flash a recovery, but the actual reasoning behind it is the bootloader does a signature check of every partition on boot, and if it finds an unsigned partition (aka the custom recovery you just flashed) it puts that over the splash screen. Until we find a way to write to the partition where that code is located (right now we can read it for dayz ;) ) that'll have to stay.

Edit: And in case you all are wondering what **TAMPERED** means, it is the result of the checksum of the /system partition by the bootloader on boot. Since we added the Superuser.apk, su, and installed busybox in the root method, that changes the checksum (most likely md5 or sha1 used) of the partition as a whole, thus displaying that message.

EDIT2: Oh, and I saw the other day that I had **SECURITY WARNING** or something similar pop up after a relock. I believe that is because the bootloader is technically locked still, AND it senses an unsigned partition (the custom recovery). I haven't looked into this much, but that's my best educated guess.
Click to expand...

Seems like i have more drivers than i know what to do with for HTC. I did delete some. There is one, HTC usb bump, or something like that, from memory, don't know if I need it or not.

I'd really like to have a clean slate and start over with the drivers, but I am concerned I might unistall/delete the wrong thing and hose it up altogether... :p
 
EarlyMon said:
Yes.

Your backups will be under /sdcard/TWRP/BACKUPS/HT25FS409294 (if you chose to backup to the internal sd card - and if there's some variation in the HTxxxxx, don't worry).

As you can see, they will have names like: 2012-06-18--02-27-58

You can name them as you wish, use a dash instead of a space and no dots to be on the safe side. I named my first one original-original and I have another called orig-charmeleon from when I flashed that rom.
Click to expand...


I use periods in place of spaces with no issue thus far. My renamed nandroids look like this: ROMNAME-MM.DD.YY. Then maybe tweaks after that if their name isn't too long.
 
Lord Vader said:
I can't do a nandroid backup because I haven't flashed a recovery. Right now, I'm rooted, but only for files and apps. I haven't flashed a custom ROM. I'm giving serious thought to just leaving the stock ROM as is, freezing bloatware stuff, and enjoying my phone without experiencing the seemingly omnipresent bugs in non-stock ROMS.

I tried many a ROM on my EVO OG, and it never failed that sooner or later, every one had a bug or some kind of issue that caused weird things to happen--front facing camera always took an upside down picture; phone would freeze up requiring a battery pull & reboot; phone wouldn't answer calls properly--you name it. I'm hedging my bets that leaving the stock ROM on with root just for apps and stuff will be just fine for someone like me.

Because of this, I don't think I'd be able to do your above fix with a preceding nandroid. Not having the full understanding of exactly how to do that, it probably wouldn't be very wise of me to even try.
Click to expand...


Great post. I may be in the same boat as you, but some of these new ROMS seem awesome. It is tempting. But my biggest beef with rooting was how a lot of people acted like it was easy and the greatest thing ever, but then when you did it and had issues, there were all these niggling things you had to do to try and get things right.

That being said I ran the Tommy Tomato classic sense ROM forever on my OGEVO, and it was rather solid for me. It just took me a while to find the best option...I went through many ROMs..had bad battery life.resets..etc.

IMO a good ROM should run more stable, faster and lighter than stock, while doing every singe thing you can do stock plus more, or it is not worth it.
 
OstrichSaK said:
You guys don't have to run a custom ROM to have a recovery installed. In fact, I highly recommend doing that & making a backup of your stock ROM before flashing anything.
Click to expand...

Perhaps it would be a good idea to explain how that is done, because I'm sure there are those who don't know how to correctly do this.
 
Lord Vader said:
Perhaps it would be a good idea to explain how that is done, because I'm sure there are those who don't know how to correctly do this.
Click to expand...

Getting recovery installed is already explained in great detail already in other rooting threads.

Here's the AF guide you're looking for -

http://androidforums.com/faqs/450904-rooting-best-practices.html

And the specifics of how to run, what to press, on making a nandroid backup varies with each recovery, so that ought go into those threads as well. :) ;)
 
Personally, I found this thread @ XDA the most useful for flashing recovery, unlocking the bootloader & rooting all with one click. I wish I had found that thread first before I did some of those tasks individually because that one makes it easy to do all at once. When you're done, make a backup and you're all set.
 
You must log in or register to reply here.
Back
Top Bottom