Related
Nandroid is just a script. Rooting is another topic. This is to allow you to backup your data before you root. It's simple, fast and easy.
Download http://www.multiupload.com/K4BZ22SIT5
Clear the data for Google apps, and system components such as Browser, to prevent force closes during restore.
If you skip this step, at the end of the guide clear dalvik, fix permissions, and clear the data for the items that keep closing.
adb push psneuter /data/local/psneuter
adb shell chmod 777 /data/local/psneuter
adb shell /data/local/psneuter
adb shell dd if=/dev/block/mmcblk0p26 of=/sdcard/data.img
Your data is now backed up. Sdcard apps will still be on your sdcard, and cache and dalvik need to be cleared anyway. System apps will be replaced and the settings for them is already included in data. In short, you only really need data.
Root your device. After you have rooted, updated, and are on the stock rooted build (before a custom rom for best compatibility), restore your data.
adb shell dd if=/sdcard/data.img of=/dev/block/mmcblk0p26
Now do a titanium backup if you plan to install a ROM that wipes data, install whatever ROM you planned, and restore titanium (if needed).
Sent from my ADR6400L using Tapatalk
Thanks. I'm always amazed at the ideas you come up with. Getting ready to try out ubuntu on the bolt.
Sent from my ADR6400L using XDA App
Thanks, I have been hoping for something like this.
You are basically doing a temp root, right? Genius. Would it be possible to then push/install a backup program (mybackup pro, Titanium, etc) and run it? I guess you would also need to get superuser in first.
tsachi said:
You are basically doing a temp root, right? Genius. Would it be possible to then push/install a backup program (mybackup pro, Titanium, etc) and run it? I guess you would also need to get superuser in first.
Click to expand...
Click to collapse
It is possible, but in actually attempting to install Titanium during the process, I spent 15 minutes doing the temp root and this backup, 4 hours playing with su binaries and superuser apps without getting any combination to play nice, 10 minutes rooting and 20 minutes restoring this backup. It is all about efficiency...
so if I'm reading this right, this will allow restoring of data for games? That's the only thing keeping my wife from rooting.
Yes. You can re install the apps, then restore data files manually after root.
My wife is the same, won't root of I can't restore things after
nrfitchett4 said:
so if I'm reading this right, this will allow restoring of data for games? That's the only thing keeping my wife from rooting.
Click to expand...
Click to collapse
Sent from a gingerbread thunderbolt
True
twistedumbrella said:
It is possible, but in actually attempting to install Titanium during the process, I spent 15 minutes doing the temp root and this backup, 4 hours playing with su binaries and superuser apps without getting any combination to play nice, 10 minutes rooting and 20 minutes restoring this backup. It is all about efficiency...
Click to expand...
Click to collapse
Sent from a gingerbread thunderbolt
tsachi said:
Yes. You can re install the apps, then restore data files manually after root.
My wife is the same, won't root of I can't restore things after
Sent from a gingerbread thunderbolt
Click to expand...
Click to collapse
ok, so do the backup, root, reinstall her games, etc (nothing system), then use adb to restore data.
Makes complete sense as long as I don't think about it too hard...
nrfitchett4 said:
so if I'm reading this right, this will allow restoring of data for games? That's the only thing keeping my wife from rooting.
Click to expand...
Click to collapse
Same with my friend, until he lost signal while I was at 3 bars and he got sick of the battery life
nrfitchett4 said:
ok, so do the backup, root, reinstall her games, etc (nothing system), then use adb to restore data.
Makes complete sense as long as I don't think about it too hard...
Click to expand...
Click to collapse
Don't reinstall anything. Just clear out data for generic system apps (because his browser and gapps force closed until we did) backup, root, restore. The games are in the backup.
And yes, the ScriptFusion AutoBot already has this capability built in. When it detects you don't have root, it will perform the backup, and when you return after rooting it will restore it. It is actually about two steps away from being able to root a phone. Should be capable later this week.
Sent from my ADR6400L using Tapatalk
Almost done building an app to walk you through the entire root with backup process.
Sent from my ADR6400L using Tapatalk
From a similar thread quoted by jcase:
I advise against using this backup method, taking a DD of /data while its r/w can lead to corruption.
A better idea would be to push su (aka a temp root) into your path and use something like titanium backup to backup you data.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1174487
yareally said:
From a similar thread quoted by jcase:
http://forum.xda-developers.com/showthread.php?t=1174487
Click to expand...
Click to collapse
Yeah, thanks. That is there for people who don't think to walk away during the process and not cause data to be changed until it finishes, which is the real risk. As stated, this was tested. You are more than welcome to add additional findings, but EVERYTHING can risk corruption. You are playing with the bootloader, which could cause a brick... Did you root anyway? There ya go...
As for the app, that actually does a temp root with su included, which is actually a whitelist temp root (psneuter already gave you a temp root) and offers the chance to perform a backup before proceeding, either with dd or titanium.
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
Yeah, thanks. That is there for people who don't think to walk away during the process and not cause data to be changed until it finishes, which is the real risk. As stated, this was tested. You are more than welcome to add additional findings, but EVERYTHING can risk corruption. You are playing with the bootloader, which could cause a brick... Did you root anyway? There ya go...
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Yeah, I don't see the problem in doing what you were trying either, just wanted to bring it up . I would probably back it up outside of the booted OS area though just to be safe, like in recovery where can access adb still. Not sure if you can in hboot offhand though.
yareally said:
Yeah, I don't see the problem in doing what you were trying either, just wanted to bring it up . I would probably back it up outside of the booted OS area though just to be safe, like in recovery where can access adb still. Not sure if you can in hboot offhand though.
Click to expand...
Click to collapse
You would need root to root in recovery, which is a slight problem.
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
You would need root to root in recovery, which is a slight problem.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
That's why I mentioned hboot (the bootloader) as well, which you wouldnt need to, though I am not sure if adb detects the device in hboot. Not at a computer, so I can't try at the moment. Please don't half read what I write. I would like to try to help out if possible.
yareally said:
That's why I mentioned hboot (the bootloader) as well, which you wouldnt need to, though I am not sure if adb detects the device in hboot. Not at a computer, so I can't try at the moment. Please don't half read what I write. I would like to try to help out if possible.
Click to expand...
Click to collapse
Wow, lol. Well I don't quite understand what you mean "which you wouldn't need to". I read the full comment, but tried to bypass the parts that showed complete lack of understanding as to why rooting is done the way it is, but since you called me out on it... The device detects usb in fastboot, but cannot flash a radio there due to s-on. It detects in recovery due to modifications to the image that require the capability to flash modified images. The temp root works like my script, in that it tricks the system into believing it is unlocked, while other things are done to allow it to be truly unlocked, at which time a replacement image is loaded. Help me help you by at least researching the process before trying to alter it. Thanks.
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
Wow, lol. Well I don't quite understand what you mean "which you wouldn't need to". I read the full comment, but tried to bypass the parts that showed complete lack of understanding as to why rooting is done the way it is, but since you called me out on it... The device detects usb in fastboot, but cannot flash a radio there due to s-on. It detects in recovery due to modifications to the image that require the capability to flash modified images. The temp root works like my script, in that it tricks the system into believing it is unlocked, while other things are done to allow it to be truly unlocked, at which time a replacement image is loaded. Help me help you by at least researching the process before trying to alter it. Thanks.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Eh, call me out, i dont care, it's just the internet and it's not the first or the last time I will be incorrect.
You are right though after trying in the bootloader myself. I only meant to do the datadump part, nothing else outside the os area.
yareally said:
Eh, call me out, i dont care, it's just the internet and it's not the first or the last time I will be incorrect.
You are right though after trying in the bootloader myself. I only meant to do the datadump part, nothing else outside the os area.
Click to expand...
Click to collapse
twistedumbrella said:
I read the full comment, but tried to bypass the parts that showed complete lack of understanding as to why rooting is done the way it is, but since you called me out on it...
Click to expand...
Click to collapse
yareally said:
Please don't half read what I write.
Click to expand...
Click to collapse
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
Almost done building an app to walk you through the entire root with backup process.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
How is this coming along?
Hello, I have had my nexus 7 for about 2 days and have set everything up how I want it. From what I've read you can't root without erasing everything. If this is the case are there any apps that will back up my applications + app settings?
Thanks
dizzdiamonds said:
Hello, I have had my nexus 7 for about 2 days and have set everything up how I want it. From what I've read you can't root without erasing everything. If this is the case are there any apps that will back up my applications + app settings?
Thanks
Click to expand...
Click to collapse
titanium backup ftw
funkyboy1281 said:
titanium backup ftw
Click to expand...
Click to collapse
Thanks, I was under the assumption that TB only works on rooted devices. I will give it a shot anyways.
tb only does work on rooted devices.. u should of rooted it right out of box so u wouldnt have to erase anything
dizzdiamonds said:
Thanks, I was under the assumption that TB only works on rooted devices. I will give it a shot anyways.
Click to expand...
Click to collapse
probably would've helped if I actually read the question word for word...oops
dizzdiamonds said:
If this is the case are there any apps that will back up my applications + app settings?
Click to expand...
Click to collapse
You can backup most of your device with 'adb backup' before you do the unlock and then 'adb restore' it afterwards. It seems to miss certain things, like paid apps (or it did for me), so if those apps have options to dump config backups to /sdcard that would help in case you have to restore them.
movieaddict said:
tb only does work on rooted devices.. u should of rooted it right out of box so u wouldnt have to erase anything
Click to expand...
Click to collapse
Doh! I've made the same mistake as wel!
Harry GT-S5830 said:
ADB Backup & ADB Restore
Click to expand...
Click to collapse
Nvm, already posted.
It's not rooting that causes you the wipe, it's unlocking.
However no one has made a way to root without unlocking first.
So if someone figures out how to just root, it would be fine.
Cryingmoose said:
It's not rooting that causes you the wipe, it's unlocking.
However no one has made a way to root without unlocking first.
So if someone figures out how to just root, it would be fine.
Click to expand...
Click to collapse
So, I rooted my Nexus 7 a while back (using the Nexus Root Toolkit), then when Google pushed out the JB 4.1.2 Update, the root access vanished, should just clicking the root button re-root it without wiping everything?
hydroxyde said:
You can backup most of your device with 'adb backup' before you do the unlock and then 'adb restore' it afterwards. It seems to miss certain things, like paid apps (or it did for me), so if those apps have options to dump config backups to /sdcard that would help in case you have to restore them.
Click to expand...
Click to collapse
1. adb backup
2. unlock
3. adb restore
Or do I need to root as well and restore at last?
mgutt said:
1. adb backup
2. unlock
3. adb restore
Or do I need to root as well and restore at last?
Click to expand...
Click to collapse
Anybody answering?
I also have a Nexus 7 well setup and would like to understand how to root it without scratching data on it...
if eventually this could work, it would be great. SO, adb backup and then adb restore after unlocking?:crying:
1. adb backup
2. unlock
3. adb restore
Or do I need to root as well and restore at last?
Click to expand...
Click to collapse
It doesn't matter.
Unlocking is what erases the data, what you do afterwards doesn't make any difference.
But since you're already hooking up N7 to PC and booting it in all these weird modes, you might as well finish what you start.
I also have a Nexus 7 well setup and would like to understand how to root it without scratching data on it...
if eventually this could work, it would be great. SO, adb backup and then adb restore after unlocking?
Click to expand...
Click to collapse
You can't unlock the bootloader without erasing data.
You can use adb backup, but I just manually backed up what I needed (launcher settings, apps are downloaded automatically from play store, 'sd card' stuff, you don't really need anything else.) Besides, you're gonna be playing with all the settings all the time anyway for next couple of weeks , it doesn't really matter if they get erased.
Ramstein said:
Anybody answering?
I also have a Nexus 7 well setup and would like to understand how to root it without scratching data on it...
if eventually this could work, it would be great. SO, adb backup and then adb restore after unlocking?:crying:
Click to expand...
Click to collapse
I did that and it worked. I wanted the savegame of Final Fantasy III that is located in data/data/... after restoring the data the Nexus was still unlocked.
How I can restore tablet to default setting, I need to remove password.
Are you rooted with CWM?
Sent from my SGH-I777 using xda app-developers app
If your current ROM does not have root or CWM (for example, if you're still on stock Honeycomb), then about the only other way to do it might be through ADB commands to wipe (factory reset) the tablet -- but that will only work if you already had USB Debugging turned on in the settings.
ROM is not rooted. How I can do ADB commands? If it not help, I need to Flash ROM?
michahal said:
ROM is not rooted. How I can do ADB commands? If it not help, I need to Flash ROM?
Click to expand...
Click to collapse
Well, this gets kind of involved, and I've never actually done this myself, so I don't want to give you bad instructions.
ADB commands are commands that you can run from your Windows PC while the tablet is connected via the USB cord. As I said, however, the first requirement is that you have already enabled USB Debugging in the tablet's settings. If you're not sure, then it is probably not enabled, since the default is off. If that's the case, there is no point in going any further on the ADB commands, and resetting the tablet to the factory image might be the only option. If you are still on the stock Lenovo Honeycomb image, you can restore it by following the instructions on this thread in the Lenovo forums: http://forums.lenovo.com/t5/IdeaPad...1-Stock-Rom-120109-Bootloader-Fix/td-p/713621
Doing so will wipe all your data and applications. It should be just exactly like you got it from Lenovo, although Google Play will remember the apps that you had previously installed, so you can reinstall them.
So I was playing Family Fued last night on my phone and pressed the home button. After doing so, my phone screen turned black and became unresponsive so I held the power button and rebooted. Upon booting the phone got stuck on the boot animation.
So I tried dirty flashing my ROM, gapps, and kernel. The phone booted then got stuck on the Starting Apps toast with a continuous progress wheel. I tried a combination of wiping caches and dirty flashing to no avail. I was running francos kernel with -75 UV, but flashed a kernel without UV to be sure. I'm still unable to get past the starting apps toast when I restore to the backup I made.
I just want to get it to boot so I can retrieve some important text messages. Any help is appreciated. Thanks in advance.
Sent from my Nexus 4 using xda premium
If you're getting as far as the starting apps dialog, you should be able to get a logcat of the boot process, which will go a long way in diagnosing the problem, and if it is recoverable.
I'm thinking either a framework file got corrupted, or even more likely, your data partition is corrupted and upon bootup, dalvik can't write to /data/dalvik-cache while attempting to "optimize" apps, and it therefore hangs.
This is all just conjecture of course, and I could be completely wrong, but a log will surely help.
JsChiSurf said:
If you're getting as far as the starting apps dialog, you should be able to get a logcat of the boot process, which will go a long way in diagnosing the problem, and if it is recoverable.
I'm thinking either a framework file got corrupted, or even more likely, your data partition is corrupted and upon bootup, dalvik can't write to /data/dalvik-cache while attempting to "optimize" apps, and it therefore hangs.
This is all just conjecture of course, and I could be completely wrong, but a log will surely help.
Click to expand...
Click to collapse
How would I pull the log cat? Also, is there a way I could salvage corrupted data?
Sent from my Nexus 4 using xda premium
nbeebe24 said:
How would I pull the log cat? Also, is there a way I could salvage corrupted data?
Click to expand...
Click to collapse
You need to stream the output of logcat via (assuming windows) your command prompt console using adb:
adb logcat > log.txt
Then upload the log.txt file for review. That's the best place to start and see what it says.
JsChiSurf said:
You need to stream the output of logcat via (assuming windows) your command prompt console using adb:
adb logcat > log.txt
Then upload the log.txt file for review. That's the best place to start and see what it says.
Click to expand...
Click to collapse
Okay I'll pull the log when I get home. Are you able to read those?
Sent from my Nexus 4 using xda premium
I've read a logcat or two in my day
Sent from my Nexus 4 using xda app-developers app
JsChiSurf said:
I've read a logcat or two in my day
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do I have to wait until the cursor in the command prompt stops blinking to give you the log?
nbeebe24 said:
So I was playing Family Fued last night on my phone and pressed the home button. After doing so, my phone screen turned black and became unresponsive so I held the power button and rebooted. Upon booting the phone got stuck on the boot animation.
So I tried dirty flashing my ROM, gapps, and kernel. The phone booted then got stuck on the Starting Apps toast with a continuous progress wheel. I tried a combination of wiping caches and dirty flashing to no avail. I was running francos kernel with -75 UV, but flashed a kernel without UV to be sure. I'm still unable to get past the starting apps toast when I restore to the backup I made.
I just want to get it to boot so I can retrieve some important text messages. Any help is appreciated. Thanks in advance.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
The last time I was stuck in Starting APps, I did a factory data reset in Recovery Mode, and it worked.
Here's what I got so far http://pastebin.com/pf3b5gc8
opticaldh said:
The last time I was stuck in Starting APps, I did a factory data reset in Recovery Mode, and it worked.
Click to expand...
Click to collapse
That defeats the purpose of trying to recover my text messages. It boots fine from other back ups and fresh installs but not from the particular backup I started a thread about.
Sent from my Nexus 4 using xda premium
Titanium backup pro allows you to restore text message from android backups.
Not sure if the free version does it but I did find two other apps that are free that you can try.
1)app extractor (found on google play)
2) nand manager http://forum.xda-developers.com/showthread.php?p=35367320#post35367320
Sent from my Nexus 4 using xda app-developers app
Titanium or any other app, at this point, won't do any good at this point since the phone won't boot up all the way
The logs definitely show things look pretty FUBAR'ed. Though not optimistic, the first thing I'd try is to reboot to recovery and click 'fix permissions' via the 'Advanced' tab (assuming TWRP), and see if that does anything.
If that doesn't help any, and you don't care about trying to continue down the path of getting the ROM to boot, and all you do care about (mostly) is saving your text messages, assuming they are still there, what I would do is, from recovery, adb pull the data folder where the mms/sms/call log database is stored, do a full wipe, install a fresh rom, and then after first boot, reboot back to recovery and restore the data you pulled (this is all titanium is doing anyway).
You could even make a nandroid of your current bad setup if the above didn't work for some reason.
To get the current data for mms/sms/calls, first, reboot to recovery:
Code:
adb reboot recovery
Via your command prompt, make a directory in the same folder from where you are running adb, and then change into it, as follows:
Code:
mkdir com.android.providers.telephony
cd com.android.providers.telephony
Then, while still in recovery mode, pull your data:
Code:
adb pull /data/data/com.android.providers.telephony .
After you've successfully pulled your data, wipe the phone completely, install your new ROM, gapps, etc, and let it boot up completely, then reboot back to recovery again. Once back up in recovery, push the data back to the phone.
(make sure you are still inside the 'com.android.providers.telephony' directory you created via your command prompt)
Code:
adb push . /data/data/com.android.providers.telephony
That should restore you previous database, cache, etc.
Reboot the phone and cross your fingers
That's what I was essentially suggesting, but I didn't know how to manually do it.
From his current ROM that works he could use tb or the other two apps to restore just his SMS from his nandroid backup
Sent from my Nexus 4 using xda app-developers app
marsdta said:
That's what I was essentially suggesting, but I didn't know how to manually do it.
From his current ROM that works he could use tb or the other two apps to restore just his SMS from his nandroid backup
Click to expand...
Click to collapse
Problem is, he doesn't have a current ROM that works.
But, he could first wipe and install a fresh ROM all together, and then install Titanium, and use it to restore the above referenced data from a Nandroid.
Though, he'd FIRST have to/want to Nandroid the current bad ROM in order to make sure the nandroid has the most current data, else any new text messages would be lost since the previous nanadroid.
After doing all of that, it'd be much simpler/quicker to just follow the instructions provided above
All of this, of course, is based on bailing on the current ROM, but for the sake of challenge, I'd love to try and get it going as well, based on making changes and following the impact via logcat.
Well I feel dumb. I mixed up a couple threads that were talking about the same thing. Only in the other they did have a nandroid.
I should not be responding when I'm half asleep.
Edit - maybe I didn't mix up but its now I've only been up maybe for a bit. Had to drive brother to school. But reread his op and this caught my eye " I'm still unable to get past the starting apps toast when I restore to the backup I made."
So he does have a current nandroid of the bad ROM?
Sent from my Nexus 4 using xda app-developers app
marsdta said:
Well I feel dumb. I mixed up a couple threads that were talking about the same thing. Only in the other they did have a nandroid.
I should not be responding when I'm half asleep.
Click to expand...
Click to collapse
No worries, the concept / principle is still sound We're all here to help!
JsChiSurf said:
No worries, the concept / principle is still sound We're all here to help!
Click to expand...
Click to collapse
Now I'm getting "Error while restoring /system" when I try to restore my derped backup
nbeebe24 said:
Now I'm getting "Error while restoring /system" when I try to restore my derped backup
Click to expand...
Click to collapse
Why are you trying to restore your derped backup? Did you already wipe and update to a fresh ROM?
JsChiSurf said:
Why are you trying to restore your derped backup? Did you already wipe and update to a fresh ROM?
Click to expand...
Click to collapse
Yes, I'm already running a fresh install. I'm a little confused by your instructions above. Which setup am I pulling the telephony data from? The bad nandroid?
Sent from my Nexus 4 using xda premium
nbeebe24 said:
Yes, I'm already running a fresh install. I'm a little confused by your instructions above. Which setup am I pulling the telephony data from? The bad nandroid?
Click to expand...
Click to collapse
Last I read, you never got past the starting apps dialog, so all of my instructions are based on the fact that that's where you're at.
If you've already make a nandroid of the bad version and are up and running on a new ROM, this process changes.
In this case, what I would do is pull the the data partition nandroid file (in your TWRP/BACKUPS folder), "data.ext4.win", off of your sdcard, add the ".tar" extension (this is all these files are):
data.ext4.win.tar
Then open the above file with WinRAR, navigate to the same /data/data/com.android.providers.telephony/ folder referenced in my previous instructions and pull the content out of the .tar.
Then, go into recovery and use adb to push the contents of the "/data/data/com.android.providers.telephony" that you extracted from the .tar file and push back to your phone.
Or, if you use titanium, as mentioned above, you could try and extract it right out of the nandroid file directly while the new ROM is running.
Finally, i have solved it !!! A couple of days ago, i forgot my pattern and clicked on forgot pattern, but i didn't get a prompt to turn on wifi. So basically, i was stuck, unless i wanted to do a factory reset and lose all of my data. Here's my unique solution to this problem, :
First of all, you need to be rooted and to have usb debugging ON. Otherwise, it won't work.
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Here's what i did:
First, i booted the modified boot image and by using either adb or the toolkit, i pulled /data/data and /data/app to my pc.
Second, I made a full wipe and set up my N7 as usual. At this point, you need a good root file explorer in order to get to the /data folder. I installed colornote (from the app backup i made, because i wan't sure that there was a new version and,if there was, it could be a possible failure, because i wasn't sure how it would behave with the last version's data) and rebooted (in order for colornote to get into the dalvik cache).
Third, i opened up colornote's folder in /data/data and just replaced the databases folder with the one from my backup and i went to /data/dalvik-cache and deleted the corresponding color note dalvik file. Afterwards, i just rebooted and voila, all my stuff that i had written in color note was staring at me.
Now, i want to mention that i've only tried this with colornote (as it was my foremost priority to get to the essays that were stored there) and i've tried this on only 4.1.2. I can't guarantee that it will work on other apps or that you won't get damage to your precious Nexus 7, so please, proceed with caution, and don't blame me if something unexpected comes up. Good luck !!!
P.S. If you get more than one device or emulator, it's because you have bluestacks, disable or uninstall it, and you're good to go !!!
Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
iAndroidOS said:
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Click to expand...
Click to collapse
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck
If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium
NIMBAH said:
If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I tried that and it didn't work
bftb0 said:
Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck
Click to expand...
Click to collapse
Thank you for reminding me, it is imperative to restore the permissions
iAndroidOS said:
I tried that and it didn't work
Click to expand...
Click to collapse
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium
NIMBAH said:
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I dunno, i went into adb and used the adb shell rm /data/system/gesture.key
command and as soon as it finished, i unplugged my N7 and rebooted it, and the login prompt was still there.