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

Root [Revised] Rooting Gingerbread 2.3.5 Dummies Guide

kracked dude said:
Final update
I have her keep entering in her email and password until it finally worked. Dunno why the other times it want working.
But for future reference, I'm wondering if the following procedure will work. Go to recovery make nandroid backup and restoring the backup. Will that work?
Click to expand...
yes it should, it would theoretically anyway revert everything rom related, including the lock counter back to before it was locked up.
 
Mikestony said:
In other words, if she gets locked up again and the gmail thing fails...boot into recovery, make a backup, then restore that backup? I don't know, but I would think you'd be in the same boat again.
However, restoring an earlier backup would work, albeit everything added since the restore point would be gone. :)
That's my thinking anyways ;)
Click to expand...







new optimus said:
yes it should, it would theoretically anyway revert everything rom related, including the lock counter back to before it was locked up.
Click to expand...

Thanks, so it wouldn't have worked anyways. I should have her install titanium for times like this.
So what would work?
 
kracked dude said:
Thanks, so it wouldn't have worked anyways. I should have her install titanium for times like this.
So what would work?
Click to expand...
your thinking is sound, just have her do a back up once a month, deleting the previous back up. That way she does not lose anything or very little. Thats good advice regardless of possible password problems. Also keep a copy of that back up on computer.
 
Hey guys!
My sisters phone (mikg, a2sd,etc) has been giving her problems, specifically the charging port no longer works (while I'm not here for that issue, if you know of a fix for that....) so she ordered extra batteries and an external charger. In the meantime, she switched back to her old phone taking her SD card with her. Now she tried to switch back to the evo, but on startup she gets a blank screen saver screen.
What can we do for her?
 
Can I assume she put the sd card back into the Evo also?
Perhaps boot into recovery, wipe cache, dalvik cache, then reboot.

About the charging port, did she try different chargers or cords? Will it charge via the computer usb port at all?
 
kracked dude said:
Hey guys!
My sisters phone (mikg, a2sd,etc) has been giving her problems, specifically the charging port no longer works (while I'm not here for that issue, if you know of a fix for that....) so she ordered extra batteries and an external charger. In the meantime, she switched back to her old phone taking her SD card with her. Now she tried to switch back to the evo, but on startup she gets a blank screen saver screen.
What can we do for her?
Click to expand...
MikG uses the ext partition on the SD card for several files, including the lockscreen. If the SD card wasn't put back into the device, there will be only wallpaper and no way to unlock the device.
 
Mikestony said:
Can I assume she put the sd card back into the Evo also?
Perhaps boot into recovery, wipe cache, dalvik cache, then reboot.

About the charging port, did she try different chargers or cords? Will it charge via the computer usb port at all?
Click to expand...

Yes you can assume that, it's the first question in asked her.
That's a good suggestion, I'll have her try that.
Different chargers and cords didn't help, she says that it needs to be held in a exact spot for it to work, also she gets the your battery is not compatible notification and that's with the original battery
 
kracked dude said:
Yes you can assume that, it's the first question in asked her.
That's a good suggestion, I'll have her try that.
Different chargers and cords didn't help, she says that it needs to be held in a exact spot for it to work, also she gets the your battery is not compatible notification and that's with the original battery
Click to expand...
Did the card get formatted or the ext partition wiped? If so, the problem will persist. Otherwise, there's no reason the lockscreen shouldn't show up, as long as the files are all still there.

It's possible the card/partition got reformatted simply by virtue of putting it into the old device. The ROM might need to be reflashed, in which case it's possible her data would be lost.
 
CapThrowback said:
Did the card get formatted or the ext partition wiped? If so, the problem will persist. Otherwise, there's no reason the lockscreen shouldn't show up, as long as the files are all still there.

It's possible the card/partition got reformatted simply by virtue of putting it into the old device. The ROM might need to be reflashed, in which case it's possible her data would be lost.
Click to expand...

She says she didn't format it. But as you said, maybe it happened by itself. Is there a way to check if the partition and files in there are still there?
 
kracked dude said:
She says she didn't format it. But as you said, maybe it happened by itself. Is there a way to check if the partition and files in there are still there?
Click to expand...
If you're using TWRP recovery there is. Otherwise the only other way to view the SD card contents is to connect it to a PC running a Linux distro. Those will mount ext partitions automatically.

I think someone did make a version of the MikG zip that doesn't wipe /data, but I can't recall where that was posted. Maybe when I get home I can look into it further. It might also be possible to flash the MikG update version to get it working again, since that one won't wipe data.
 
CapThrowback said:
If you're using TWRP recovery there is. Otherwise the only other way to view the SD card contents is to connect it to a PC running a Linux distro. Those will mount ext partitions automatically.

I think someone did make a version of the MikG zip that doesn't wipe /data, but I can't recall where that was posted. Maybe when I get home I can look into it further. It might also be possible to flash the MikG update version to get it working again, since that one won't wipe data.
Click to expand...

Pretty sure she's using amon ra recovery (recommended in the guide IIRC). No Linux computer is a available either.
Please keep me updated about the non wiping version, thanks
 
ocnbrze said:
that is up to you.....LOL

personally i love aosp roms.....so yeah i would be, but it is not for everyone;)
Click to expand...
Lol I know it's up to me just that I've never had a non stock or sense based rom before, so I'm a little hesitant but I'm sure I will probably love it based on all the love AOSP roms get around these parts.
 
I'm sorry for bad manners. I'm not sure where to jump in this conversation but this has had me stuck for a few days. My evo 4g had all the newest ota's before i picked it up from a friend. I've done all the backups for apps and data. I used this forum as far as a step by step process for rooting...after reading so many rooting procedures it seemed to be to the point. Ok I used the Htcdev method described, as it seemed to be fairly easily. Ok unlocked the bootloader no problem, installed amon ra recovery no problem, made a nandroid put a copy of it on the pc, which leads me to my problem.
Mostly indecision...I know how to flash the superuser zip, i understand that, but for one the link you used in your instructions is a dead link. Two, I've tracked down the zip I think, hosted by androidsu.com. Which I think I found Captiain_Throwback reference on the themikmik.com forum. When the instructions for rooting my evo were written in 1/24/2012 on this forum and the subfolder on androidsu.com was added on 3/24/2012 lists the zips you can download...it has multiple versions. So I was thinking about using the Superuser-3.0.7.efghi.signed.zip that you called for in the rooting instructions...even though its an older zip as compared to the version numbers.
I guess my question is should I use this zip or should i use a newer zip? As I read the changelog and faq's about this dev's work, it seems as if theres so many issues with the su binary and not getting it updated and bugs here and there. Would it be in my best interests to use a newer version of this zip? Or should I stick with the one that the instructions said to use, even though its from a couple years ago? Is there a better su zip out there, that I've just missed while researching? Or should I skip this step and flash a rom, it seems the more I read about them they have this zip embedded in the code? I could be wrong about that. Plus I read so many bad reviews on p.store about this app and how so many ppl can't update the app/binary. So many questions...my apologies. I'm a newb when it comes to this root info...thanks again to all the ppl that make this a cool forum.
 
Welcome goop!
Good to hear that you got as far as you did!!

I see also that the link for the su zip is broken. I'll have to get in touch with ocnbrze to fix that. ;)

That site you list:
Superuser seems to be posted by ChainsDD who is well respected and on the older versions page:
Superuser downloads | /superuser
I do see the file for Superuser-3.0.7.efghi.signed.zip.

I would use that one if you desire to stay on stock rooted, however, I personally would try a different rom;) Such as MikG! It's close to stock and performs way better and has alot more tweaks to it:)---it also has the su baked into it, so no need to flash the su.zip separately.

Any other questions, feel free to post!!
 
Ok thanks again for the reply...so you think I should proceed with the 3.0.7 not the 3.1...now if i does this step...but i later decide i want to try out this new mikg rom you guys are raving about am i gonna have issues with the signature because i would be using an older apk/binary and when i load up this newer rom i assume he probably used the newer version of su...I'm fairly computer literate i have a degree with programming/networking...i'm interested in diving in this stuff balls deep but i just trying to get my toes wet first
 
You must log in or register to reply here.
Back
Top Bottom