yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Rammv:
Hey what are you doing in here ! You have a rom to finish no time playing around in other sites!!!!!!!! Get back to work ! LOL!!!!!!!!!
[EVO 4G Android Development] smelkus:
Seriously, there is no need to share this kind of post in a thread. I don't want to be a jerk, but it is just not necessary. See my previous post and work at it. I'd like to see feedback and valid criticism. You know where I post stuff. Work at it until you download it. Hundreds have already got that far. Thanks.
[EVO 4G Android Development] bennyboy78:
smelkus, loving the new wipe options. especially superwipe

great job dude!
[EVO 4G Android Development] oodork123:
First download for ics theme lol. It's great love the cache/delvik cache mod wipe.
[EVO 4G Android Development] robo4130:
Man I seriously love the new x3 wioe options....keep up the awesome work
[EVO 4G Android Development] ShagNasty2:
Im in. I love drellisdee's version, your version makes it even better.
[EVO 4G Android Development] drlzanej:
Well,,,**** man, for the first time in my life im speechless,,,,This is absolutely incredible, i love it . Thanks man,,,Later:cool:
[EVO 4G Android Development] ShagNasty2:
SD

I love the recovery. Something i would like to see that i havnt seen in any recovery ive used is maybe listing the format entire sd card option (maybe would save an oops) in a Seperate category under wipe (maybe something like "sd tools")and include sd partitioning in the same, but leave the less destructive sd wipes where they are.
[EVO 4G Android Development] smelkus:
If you've moved up to v4.2, the sd card wipe is in its own category now and I moved it. That was done based on another users feedback from TCD. So, one would have to click down 12 times or up 4 to get to it. It says:

***Entire SD Card!!*** and if you click it the confirm message says :

"Wipe ENTIRE SD Card!!

This is Irreversible!!"

Who would agree someone who got that far and hit confirm would deserve a full SD wipe? It would be a good lesson for that person in my mind in all seriousness. Sometimes it takes a few bonehead mistakes to get people to start reading about what they're doing instead of just clicking away.

That said the SD wipe is just like the other wipes calling erase_root. The sd partitioning menu uses the sdparted script along with other binaries. Different actions. (Plus, I don't want to work in the wipe menu any more ;) )

I'd love to have a flash menu where you could queue up everything you want to flash in a specific order and autoreboot on complete. Probably out of my capability at this point. BTW, I'm pretty sure you only have to go back twice if you went into the flash menu and didn't flash anything. If you successfully flash something, you should only have to go back once to the reboot option if I remember right.
[EVO 4G Android Development] ShagNasty2:
SWEEEEEEEET I will definitely update. You rock man.

---------- Post added at 05:28 PM ---------- Previous post was at 04:55 PM ----------

I am sorry that you feel if people dont get it the first time they need to read more clearly:confused:. With that said..... My only point was that a great majority of flashers are new and may not understand what they are reading.

But i still think this recovery is the best to date.:D
[EVO 4G Android Development] smelkus:
That's exactly my point. When I first got into Linux I read this article. What I'm talking about is Problem #4 from that article (particularly the fifth paragraph).

Presumably, in the case of this sd wipe topic, we would have a user who...

1) wanted to root their phone (that's huge)

2) rooted their phone

3) Understood what a recovery was

4) Found this recovery

5) INSTALLED this recovery

6) Went to the WIPE menu

7) and faced a decision

If they made it through all of those steps and looked at an option with six asterisks, ALL CAPS, exclamation points and confirmation dialogues and STILL clicked GO, they're going to get what's coming to them. That option has to be put somewhere and it comes with its risks.

Hopefully, the person who DID wipe their SD card would say, "What the hell happened?" and then spend some time learning more about this recovery or about their SD card or anything really.

I'm not wishing for someone to wipe their SD card. But anyone who made it through steps 1 and 2 above should consider learning more even if it's only one little thing a week. Read an update-script from a flashable zip, read some source code, etc. Probably won't make any sense at first, but it doesn't to anybody at first either.

Hope that explains my thoughts better.
[EVO 4G Android Development] ShagNasty2:
Point taken. And very informitave i might add. Please take no offense to my post, this "is" my new recovery. I just tried some newbie mistakes and found it very easy to wipe the sd thats all. Of coarse i keep a back-up:D
[EVO 4G Android Development] sharkytm:
Yet again, this recovery is awesome. The haptic button use and the auto-reboot is a huge time saver. Thanks!
[EVO 4G Android Development] polar2792:
juss flashed the ics style using the PC36IMG.zip n it worked perfect, looks extremely useful good job smelkus
[EVO 4G Android Development] drewmonge:
Just wanna say, this recovery rocks hard. Hands down, best recovery I've ever used on my Evo. Thank you, Smelkus!
[EVO 4G Android Development] Rxpert:
I'm going to recommend this to everyone
[EVO 4G Android Development] smelkus:
Thanks again for all the great feedback. Over 1,100 downloads for all themes and versions. That's awesome!
[EVO 4G Android Development] MizzouBrent:
Need to update to 4.2 but really loving this. Has caused me zero problems and the added functionality is great
[EVO 4G Android Development] fitz420:
Between this and decks reloaded its great to see all this trying to make something already perfect even better. Soooooooo glad I didn't jump to a 3d when everyone else did.
[EVO 4G Android Development] rjd728:
4.2 Rocks!

Kudos to the Dev's once again! :D
[EVO 4G Android Development] Digitalkarma:
Smelkus, you're recovery is tha f***ken s#%t!! In expletives cuz that's how awesome it is! Thanks for bringing it to us :)
[EVO 4G Android Development] carp532:
Alright everybody with 1,100 downloads let's knock the his thanks meter out of the park......:D
[EVO 4G Android Development] ropodope:
just added 12 thanks to the smelkus meter.

ropodope

Change, nothin' stays the same. Unchained, and ya hit the ground runnin'.
[EVO 4G Android Development] atapia984:
Never understood that. Why not give Thanks? It is the least one can do. Shame.

Sent from my PC36100
[EVO 4G Android Development] smelkus:
I was just in 4.2, wiped Caches, and did a backup of B, D & S on the Team Dirt CM9 port. After autoreboot, the phone got past the splash screen and then turned off. Power button didn't respond, pulled battery, pressed power, booted fine.

With as much development going on right now and the pure beating my phone has taken over the last month, it's tough to say what happened there. Let me know if it happens to anyone else. I think it might have happened another time to me, but not sure.

So, I have a feature request: move recovery.log to sd automatically before autoreboot.

Get on that me!
[EVO 4G Android Development] CRIME INC.:
Happened to me earlier today, same exact series of events.
[EVO 4G Android Development] youngchris29:
That's weird, I literally just experienced the same exact thing.
[EVO 4G Android Development] smelkus:
Well, I can say this... the recovery made the backup and rebooted like it was supposed to. I just went in wiped existing and restored that backup with autoreboot without a hitch.

If that happens to others, please mention your ROM and kernel for the heck of it. I don't know what it is.

Also, I'd appreciate seeing some recovery logs from folks if anyone has time. When you're not planning on autorebooting, when you're done doing your tasks go to the Other menu on the main screen and move recovery.log to sd. When you boot up, that file will be on the root of your sd card. PM it to me or pastebin or whatever. Would just like to see some other phones reports.

Right now I know adding autoreboot the way I did caused I: Set boot command "" to appear multiple times in the recovery logs. That log comes from bootloader.c, but I'm not clear why it appears yet. Doesn't seem to cause any performance problem. If there's any developers out there who could help, I would love some help. :)

My Github
[EVO 4G Android Development] fitz420:
I have been using 4.1 since u dropped it and have been flashing like crazy and HAVE NOT had this happen. Just figured I'd chime in in case its only 4.2 related.
[EVO 4G Android Development] polar2792:
yo smelkus flashed a ROM wiped sd ext first then a superwipe worked perfect flawless, way better than stock amon ra adding thanks to ur meter now

EDIT: i didnt autoreboot but if u want the log ill shoot it ur way, let me know
[EVO 4G Android Development] ngh55:
Which one is the PINK from the themed recoveries?
[EVO 4G Android Development] ropodope:
the aokp themed recovery.

ropodope

Change, nothin' stays the same. Unchained, and ya hit the ground runnin'.
[EVO 4G Android Development] oodork123:
Download it a few days ago, loving it. Relearning how to wipe again but I'm human and I can do it.

that dude drives a A-Team van. yeah that's right, I'm working on it. Z.R.T.
[EVO 4G Android Development] Hockeytown1970:
I used the bootloader method and it is now stuck on parsing...[PC36IMG.ZIP] can't go into recovery. What am I doing wrong?
[EVO 4G Android Development] spyder3:
Whats up with the backup file name?

ex. Amon RA - BDARS-20120421-1857 (DATE-TIME)

Smelkus - BDARSW-19800106-0002 (?-?)

I'm not pooping on it, just trying to figure it out to make sense of what the numbers signify.
[EVO 4G Android Development] smelkus:
1) Did you download one of the files that already contained 'PC36IMG' in the file name and its extension was .zip? (i.e. PC36IMG_ra-supersonic-4.2-smelkus-ics.zip)

2) When you renamed the file, did you delete "_ra-supersonic-4.2-smelkus-ics" from the file name so its new name was PC36IMG.zip and move it to the root of your sdcard?

3) When you booted to bootloader by holding volume down and power, did you wait for it to scan and when it detected this file, did you press volume up to accept update?

4) When it completed, did you you press volume up to reboot?

The answer should be 'Yes' to all four questions to install correctly. If you answered 'No' to any of the above, that's where you went wrong.

Hope that helps.
[EVO 4G Android Development] smelkus:
Hmmm... none of mine appear like that and I have made A LOT under my version. Mine all still show like Amon Ra - BDS-20120522-0819 (Boot,data,system-May 22, 2012 at 8:19am).

Could you go make another backup and before leaving that recovery session, go the Other menu and move recovery.log to sd and PM it to me (don't paste in the thread it'll be too long)?

I didn't muck with any of that code, so I'd be interested to see what the log says. Also, don't worry about pooping on it. I'd rather people be honest and tell me what they think.
[EVO 4G Android Development] Hockeytown1970:
I am on 4 Kornerz with underworld kernel, does it matter which version I use?
[EVO 4G Android Development] CRIME INC.:
No
[EVO 4G Android Development] spyder3:
Sure thing, backing up as I type.

One thing I noticed is that you don't select recovery, android secure, or wimax...I read a tutorial somewhere saying to select those...is it unnecessary?
[EVO 4G Android Development] smelkus:
Boot, data, system is the minimum for a ROM. That's all I ever backup and restore going from ROM to ROM. I use a2sd so all of my apps are on my sd-ext partition. I keep a separate backup of sd-ext once a month or so and use that on occasion.

I don't live in a 4G area, so I have one backup of that from a few months back. Never use it. A 4G person may know more about that backup. You might want to backup .android_secure if you're using an Apps2SD type of app versus DTa2sd. Those apps get moved to your /sdcard/.android_secure folder.

Don't see much need to backup and restore recovery. I'd be interested in any others thoughts about it.
[EVO 4G Android Development] smccue:
Are my Amon_RA nandriod backups compatible with this recovery?
[EVO 4G Android Development] slickrick54:
!!!Awesome Recovery!!! Thanks love the new options.
[EVO 4G Android Development] anthony_s:
Yessir
[EVO 4G Android Development] ItsLasher:
Has anyone used the Nandroid feature yet? The last (newest) version of RA's I had nothing but issues with it.
[EVO 4G Android Development] smccue:
Thanks, time to make the change.
[EVO 4G Android Development] ropodope:
no nandroid problems at all.

ropodope

Change, nothin' stays the same. Unchained, and ya hit the ground runnin'.
[EVO 4G Android Development] ItsLasher:
+1 Thanks a lot. RA was starting to piss me off with only restoring 3\4 max.
[EVO 4G Android Development] ben.nesheim:
i have had a bad time with nandroids as of yet i tried restoring some aosp gingerbread and it bored it up real bad and reboots just seemed to make it worse. i dont know if its really recovery related i jusk to titanium back up and flashing
[EVO 4G Android Development] bluezr1:
I have this downloaded and sitting on my sdcard. Unfortunately I haven't got a change to try it yet, hopefully tomorrow after jmztaylor drops a nightly (I can't wait to test this out.) :)

I downloaded 4.1 seeings that a few people were reporting a few hiccups with 4.2. That is unless someone can confirm that 4.2 is safe to use?

Thanks smelkus,
[EVO 4G Android Development] smelkus:
At this point, I don't think there's any hiccups with 4.2 compared to 4.1. If anything they both have the same problem, which right now is either non-existent or strangely random.

I mentioned having a backup with autoreboot essentially turn off the phone after the reboot and splash screen. Well it rebooted and it made a backup, so it did what it should and in that case I didn't use any code new to 4.2. The caches wipe is the same as in 4.1.

I did the same exact steps I did before with the same ROM and kernel four times today and never had a repeat. All went perfectly.

In any case, all that happened was the phone turned off. Pulled the battery and pressed power and it booted fine. So, while inconvenient, it didn't seem to be "bad."

When I was learning how to build this recovery, I was warned autoreboot was experimental and untested. I personally don't care. I just want autoreboot!! So "safe" would probably be v3.11 or v2.3. But what fun is that?? Our phone is "end of life." Let's get what we can out of it, right? ;)
[EVO 4G Android Development] bluezr1:
Thanks for the response. I'll be checking it out tomorrow.

I hope I didn't offend you by asking, I just wanted to make sure. I still have a little over four months left until I'm ready for a new one. :(

Oh yah, I agree with you on getting what we can out of it. :D

Thanks again bud,
[EVO 4G Android Development] spyder3:
What's all this talk about "end of life"...pssh

My phone is running better than ever now, and after jumping carriers I plan on running this thing until the wheels fall off!
[EVO 4G Android Development] smelkus:
No offense taken. You should ask something like that in this thread.
[EVO 4G Android Development] Captain_Throwback:
It's this exact reason that I'm switching between using this recovery, and TWRP 2.1.2 :eek: (yup, you read that right).

Great job on this. I had moved back to 2.3 after having some issues with 3.11, but I haven't had any issues with this one so far (or TWRP, for that matter :confused:).
[EVO 4G Android Development] spyder3:
Is there a way to add "Convert EXT 4 to EXT 3"?

It's a pain in the ass re-partitioning a card just to move back one step.
[EVO 4G Android Development] smelkus:
Thanks! Great to hear from you. I know you had a lot of these requests on the 3.11 thread. I was right there with you.

Nope.

WARNING: Once you run this command, the filesystem will no longer be mountable using the ext3 filesystem!
[EVO 4G Android Development] spyder3:
What does that mean exactly? If I upgrade, then I also need to run those command lines in terminal? Is that true when loading a new kernel as well?
[EVO 4G Android Development] smelkus:
No, you don't have to worry about it. Those are the commands recovery runs when you click on "SD:Ext3 to Ext4" (See lines 37-38 here)

So, if you already did that, you have yourself an ext4 partition. If you want ext3 again, you'll have to reformat.
[EVO 4G Android Development] MizzouBrent:
What benefit is there to EXT4? I have always kept mine at EXT3. Loving your recovery by the way. Zero issues and love all the options.
[EVO 4G Android Development] CRIME INC.:
Smelkus, in ur opinion is it worth it to move to an ext4 partition. Forgive my noob question but what are the benefits?

Sorry to ask this on ur recovery thread, but since u were already discussing ext4, I thought I'd ask.
[EVO 4G Android Development] Captain_Throwback:
Since we're talking about ext4 partitions . . .

Is there any way to have both an ext3 and and ext4 partition? I recently reformatted and repartitioned my SD card with both, but I'm not sure what's going to happen if I try to use either (or both?) with a ROM.
[EVO 4G Android Development] fitz420:
I used to use ext4 but honestly don't notice any difference. Also, sense roms, as far as I know, don't support ext4 so if u flash a bunch of stuff you'll have to reformat for going back to sense, as u can't downgrade ext4 to ext3
[EVO 4G Android Development] ropodope:
Ext4 is faster, just as stable. It just is. Most roms worth their weight support it now. And since I could care less about a sense rom, then for ME no worries here. If you are happy with ext3 then stay there.

ropodope

Change, nothin' stays the same. Unchained, and ya hit the ground runnin'.
[EVO 4G Android Development] spyder3:
We are all kinds of effing up Smelkus' thread here! lol

Sorry about getting that ball rolling bro...BUT, since we're talking about it...:D
[EVO 4G Android Development] smelkus:
I don't mind at all. It's something the recovery does, so why not discuss it here? Rather than re-state...

"EXT4 is more scalable, more efficient through the use of Extents, supports larger disk capacities, can handle twice the number of sub-directories, is capable of handling online defragmentation, and there is improved reliability via journal checksums. "

-- Phoronix Benchmark

So... faster. And/or... newer. That usually does it for me.

But, you gotta make sure your ROM and kernel combo support it and some nandroids made prior to the conversion won't work any longer. So you gotta weigh that out and make a choice.
[EVO 4G Android Development] spyder3:
Well in that case, I just upgraded to ext4 and got stuck on the splash screen. First, I tried wiping everything and flashing a new rom...no dice. Finally I did a Factory reset, then repaired the ext, and reflashed the rom. It's good to go now.

I'll be rocking this TD CM9 until that reloaded update is ready.
[EVO 4G Android Development] smelkus:
Not sure I follow. Do you mean you have one ext3, one ext4 and a FAT? Once you add ext4 extents to a partition there's no going back. I'm pretty sure you can mount ext3 as ext2 without the journaling though. If you decide to boot it up, run the command "mount" in terminal emulator and see what it returns.
[EVO 4G Android Development] smelkus:
I'm probably going to confuse a lot of people, but I'm going out of town this weekend and wanted to post this.

v4.2.1 is only for the mason theme right now. Just updated the graphics to that new logo.

I also added the inital dalvik wipe back in on the Superwipe option because I forgot it on v4.2 for all themes. I have to build the whole recovery each time to change the font color and that's a PIA for such a minor update.

So, if you want the new theme. It's up with one very small fix (how many wipes can we have folks?). The other themes will get that fix when I get more done.
[EVO 4G Android Development] Captain_Throwback:
That is exactly what I mean. I'll have to flash a ROM and see what that command returns. I get the feeling it'll only mount whichever partition is first.
[EVO 4G Android Development] suprano:
I tried it out and I love it!! Great work man. :D

MIUIeD UP!
[EVO 4G Android Development] amiblindyet:
Amazing MOD! All in one! One and done I always say.. I said that once.

I can't understand why this wasn't done sooner. Great work!
[EVO 4G Android Development] dsEVOlve:
Thought I better ask before taking the plunge (at the risk of sounding stupid). This is backward compatible with my old AmonRa nandroids, right?
[EVO 4G Android Development] CRIME INC.:
Yes
[EVO 4G Android Development] smelkus:
So much for adding that to the OP under Important Notes #3. ;) It's all good.
[EVO 4G Android Development] pmacevad:
Is there a way to revert ext4 to ext3 or do u need to re partition? Thanks.

Sent from my ever-changing Evo.
[EVO 4G Android Development] smelkus:
Go two pages back
[EVO 4G Android Development] Brian Rubin:
Been using this a couple days now, love it. Thanks to everyone involved for their hard work. :-)
[EVO 4G Android Development] HearMeWhisper:
I tried restoring a nandroid backup and it wouldn't take. Any ideas?
[EVO 4G Android Development] ropodope:
yeah if your nandroid was ext 3 and converted to ext 4, some of your nandroids won't restore.

ropodope

It's a showdown in the no man's land, for the cowboy of the modern day.
[EVO 4G Android Development] smelkus:
Did you get an error? The recovery log would explain what happened. You have to move that to the SD card during the same recovery session. If there was an MD5 mismatch, it was saving you from mucking up your phone with a bad backup. Need more info...
[EVO 4G Android Development] slam11100:
+ 1
[EVO 4G Android Development] dr_chunk:
Love the options on this recovery, wiping is simple and thorough. Thanks for the great work!
[EVO 4G Android Development] ropodope:
no more wipe scripts, you'll never find a better one for the evOG. Selective backup/restore, autoreboot back/restore. Full capacitive, touch screen scrolling...this ones for the ages.

ropodope

It's a showdown in the no man's land, for the cowboy of the modern day.
[EVO 4G Android Development] sha4000:
Well now I know why my nandroids would not restore earlier. I went from 3 to 4 after reformatting my sd card. Yes I did back it up first:cool: but when I put the nandroid folder back it had a question mark by it in recovery. I ended up reflashing cm9 and reloaded again and restoring all my apps from the play store and then nandroid both roms. Now I'm good:eek:
[EVO 4G Android Development] smelkus:
v4.3 is up.

I added a feature in the Other menu where you can get the current ROM version. The idea being if you forget to rename a backup and don't want to restore and boot to find out what it is, you can use this feature to find out right after restoring it-- no need to boot up (don't use autoreboot if you're going to try this feature as you won't have a chance to run it).

It works by reading the build.prop line by line (so it can be slow at first) and returning what the ROM developer put after modversion= or romversion=. I've tested it on Reloaded, deck-gb, deck-ics, tommy classic, mikg, evervolv, and cm7.2 and it works well.

The limitation is the inconsistency in the build.prop across ROMs. Some ROMs conveniently include the ROM name and version in the same line. So with 1.3d for instance, you get Current ROM: gingerbread-evo-deck-1.3d

On MikG 3.1, you just get Current ROM: MikRoms. On Deck ICS, you get Current ROM: PROJECT_D, etc. So, it not exactly the most amazing feature ever, but can be useful if you're backing up ROMs that list the name and version consistenly and forget to rename them. You can run it first thing upon booting recovery, after a flash or after a restore.

If the ROM doesn't list its name commonly then it will say Current ROM: ~. You can PM the build.prop of your ROM to me if that happens and I may be able to either change my code or tell you it ain't gunna happen.

Also, added that initial dalvik wipe to ICS and AOKP themes from v4.2.1.