Related
In recovery mode, does wipe battery stats display an output? When I select it, it just puts me back to the previous screen with no output of a success or anything.
Is this normal?
Thanks!
Mine does this too. Ive always wondered about it. Lets hope we can get an answer from a dev.
Green cwm is broken in some areas. either get red clockwork or wipe data /cache and reflash your rom at 100% battery.
Sent from my SCH-I500 using XDA App
I have the red cwm that jt just released and I dont get any output when wiping the battery neither.
How did you get the red CWM, might i ask?
http://forum.xda-developers.com/showthread.php?t=942021
This is only if you are using group roms. I believe green still works for all the eclair stuff.
Sent from my SCH-I500 using XDA App
Any info on the original query?
I have flashed the "new_cwm" several times on my phone. Deleted the old update.zip before I did so.
Even after multiple flashings, when I boot into recovery all I get is the older green text screen.
Am I missing anything?
Anyone learn anything new?
This is still an issue. Anyone have resolution?
Sent from my SCH-I500 using XDA App
I have the same problem. Anyone?
Superclean 2.2 Froyo - Voodoo - Minimalist v1
Mine has never displayed any output, but it's always worked correctly. I don't think it is something to worry about unless it's causing problems.
Sent from my SCH-I500 using Tapatalk
If it makes you feel better, you can follow these steps to do it manually:
1. Charge to 100%
2. Power off phone and continue charging until you get the 100% message
3. Boot up and use a root file explorer to navigate to Data>System and delete "battery stats.bin"
4. Reboot, drain battery to 5-10%
5. Charge to full again
Kevin Gossett said:
If it makes you feel better, you can follow these steps to do it manually:
1. Charge to 100%
2. Power off phone and continue charging until you get the 100% message
3. Boot up and use a root file explorer to navigate to Data>System and delete "battery stats.bin"
4. Reboot, drain battery to 5-10%
5. Charge to full again
Click to expand...
Click to collapse
+1 this is an easy way to do it.
This is actually relevant to more than just the Thunderbolt. It fixes Superuser problems with numerous newer Sense releases.
http://forum.xda-developers.com/showthread.php?t=886999
My su binary is already being provided via the root thread but the matching Superuser is not. Without the matching patched Superuser, you'll see FCs when apps request root if the Superuser app itself is open.
Just apply the update zip from the aforementioned thread to fix it. ROM builders should use my patched version as well.
Please update to this, I will be fixing the tutorial as soon as I can, and noting it here.
Rafi, good to see you on the bolt. Looks like we will get a virtuous Rom too. Ran your Rom on the inc till I got run over by the desire z, hd craze.
Sent from my Thunderbolt!
Hmm, not sure if I should do this. I ran fix permissions in Rom Manager and it seemed to take care of all the problems. Everything's been working fine since then. What do you guys suggest?
i see no reason to mess with it if your set up is currently working
jacobk said:
i see no reason to mess with it if your set up is currently working
Click to expand...
Click to collapse
I agree - however, in my case, nothing was solving the FC's - so I put in this SU and all is right with the world.
I think it's worth trying if all other permissions methods are failing - it certainly "feels" more stable.
This fixes su issues while the superuser app is open.
Flash it.
Thank you rmk & jcase
even aftere re rooting fix my su issue i ran this and i feel su runs wayyyyy smoother now for apps that need su.
jacobk said:
i see no reason to mess with it if your set up is currently working
Click to expand...
Click to collapse
There is simply no way any newer Sense ROM works correctly without this patched version. You *will* ultimately encounter issues.
Don't believe me, try this. Open up the Superuser app itself, connect via adb shell, su system, su root. Observe hang. This is just an example, there are numerous other ways to have the issue occur.
RafficaX said:
even aftere re rooting fix my su issue i ran this and i feel su runs wayyyyy smoother now for apps that need su.
Click to expand...
Click to collapse
Good. maybe you can apologize now in the debloat rom thread instead of trying to smear my name.
can you just post it in here...i dont like guessing games...i see 2 links to pull requests on github...i dont know wtf that means. some of us dont speak computer 120% fluently..
MYxdaUSERNAME said:
can you just post it in here...i dont like guessing games...i see 2 links to pull requests on github...i dont know wtf that means. some of us dont speak computer 120% fluently..
Click to expand...
Click to collapse
Haha scroll down the page!! There's a flashable zip
sent from my Thunderbolt
for christ's sake...big blue letters. i thought that was the top of his sig..but he lost me at github.
good to go...i do remember a few force closes that never amounted to anything serious last night...
doodoostains said:
Hmm, not sure if I should do this. I ran fix permissions in Rom Manager and it seemed to take care of all the problems. Everything's been working fine since then. What do you guys suggest?
Click to expand...
Click to collapse
This was working for me until I rebooted. Once I did, everything was back to how it was.
I just applied the patch, restarted. VOILA! SU is working again. Thanks rmk40!
Superuser is acting up after working fine earlier. How can i boot into clockwork without rom manager anyone? thanks
frodsteamin2 said:
Superuser is acting up after working fine earlier. How can i boot into clockwork without rom manager anyone? thanks
Click to expand...
Click to collapse
Turn off phone. Hold volume down when booting up.
Sent from my ADR6400L using XDA App
Was able to get into CWR after a reboot, flashed. Thank you!
Edit * this fixed all my issues. . Thanks again
evilmunkeh said:
Turn off phone. Hold volume down when booting up.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Thank you for the response, my newbness was the problem as there was a file on sd card that keep trying to install when trying what you mentioned above.
Still getting FC's in SU after flashing... Did I miss something?
Never mind, fixed after running a program that required root.
Thanks!
Sent from my ADR6400L using XDA App
I was waiting to root my continuum until I got the new upgrade, which I expected months ago. Anyway I got the upgrade (froyo 2.2) and everything works great. I would like to root the phone, so I can tether it to my laptop.
I have seen older videos for other phones, but I was not sure they would work for the continuum, or if there is a newer easier way, as I am not tech savvy. I just want to work on my laptop as I run my kids to their after school activities.
Finally, which app works best for turning the phone into a hotspot.
Thanks in advance
The easiest way is to find superoneclick 2.3.3 That roots, nothing else.
The slightly more complicated way, is to flash a rooted version in Odin. And there are tutorials all over. You can also swing into IRC, and we can get ya going.
webchat.freenode.net
#samsung-continuum
Or....manual root
Sent from my SCH-I400 using Tapatalk
rooting problem
I was originally having problems tethering, but I figured it out. Too bad there is not an option for deleting posts, but I am excited that I can now tether.
abby_nitewolf said:
Or....manual root
Sent from my SCH-I400 using Tapatalk
Click to expand...
Click to collapse
How is that done? I've dabled with Linux on my PC so I'm familiar enough to be dangerous, but this question has been bugging me for a while now.
LGartrell said:
How is that done? I've dabled with Linux on my PC so I'm familiar enough to be dangerous, but this question has been bugging me for a while now.
Click to expand...
Click to collapse
adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
adb kill-server
adb devices
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adbreboot
There you go, you need a few files:
psneuter
su
busybox
Superuser.apk
Adb
But its easier and faster with SuperOneClick,
Sent from my SCH-I400 using Tapatalk
The kernel I included with the CWM recovery file will install the su binary for you. Get busybox and then install Superuser from the market and you'll be rooted.
Sent from my Galaxy Nexus
imnuts said:
The kernel I included with the CWM recovery file will install the such binary for you. Get busybox and then install Superuser from the market and you'll be rooted.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks. I've been playing with my Continuum now for several months with everyone's mods. Love the work you're all doing!
Question about installing ClockworkMod Recovery on Continuum.
Hi,
I am trying to figure out which version of CWM recovery is the appropriate, and most recent one for the continuum.
Can anyone point me to the correct file for the Samsung Continuum SCH-i-400.
Also, after I root the phone, how do I install CWM. Should I use a ROM manager, or do it manually?
Someone please help.
Thank you!!
You should try reading through the forums. I believe there is a thread that will have all necessary files.
Sent from my SCH-I400 using XDA
I used imnuts froyo rom.flashed with no problem.its not 100% stable,but it got the job done.
Sent from my SCH-I400 using Xparent ICS Blue Tapatalk 2
I figured I'd post in this thread instead of making a new one since it seems to be a similar issue. I rooted my phone ages ago right when I got it using the super one click program. Everything was working fine as far as I could tell, until I had a app on my phone tell me that it wasn't in fact rooted. I assume it was because my phone updated to 2.2.2 by it self one evening causing me to lose root. I checked with a few other apps that used to work fine (Titatium Back being one of them) which also told me my phone wasn't rooted.
I downloaded the newest version of SuperOneClick (2.3.3) and tried to re-root my phone. The program said my phone was already rooted and asked if I wanted to continue. I clicked no and then tried the 'Unroot' option. The program hung up and stopped responding so I did a factory reset and tried again. When I tried to root it again the program still said my phone was rooted and Superuser was still in my app list with no option to uninstall. I went to the market to try and uninstall that way but there wasn't an option either. I tried the un-root option again and SOC still would ended up not responding at a certain point (Installing BusyBox Step 2).
I pulled my battery and just tried to root again, it gets to the point of installing Superuser and freezes. I tried downloading an uninstall root app which didn't even show superuser. I also downloaded root explorer and tried to delete the superuser.apk from the system/apps folder and it failed to DL.
I am at a loss for what to do and would really appreciate any help in getting my phone rooted. I am in USB debugging and never installed any ROMS or anything previously. If there is any other information that would help troubleshooting this please let me know.
Vsoup25 said:
I figured I'd post in this thread instead of making a new one since it seems to be a similar issue. I rooted my phone ages ago right when I got it using the super one click program. Everything was working fine as far as I could tell, until I had a app on my phone tell me that it wasn't in fact rooted. I assume it was because my phone updated to 2.2.2 by it self one evening causing me to lose root. I checked with a few other apps that used to work fine (Titatium Back being one of them) which also told me my phone wasn't rooted.
I downloaded the newest version of SuperOneClick (2.3.3) and tried to re-root my phone. The program said my phone was already rooted and asked if I wanted to continue. I clicked no and then tried the 'Unroot' option. The program hung up and stopped responding so I did a factory reset and tried again. When I tried to root it again the program still said my phone was rooted and Superuser was still in my app list with no option to uninstall. I went to the market to try and uninstall that way but there wasn't an option either. I tried the un-root option again and SOC still would ended up not responding at a certain point (Installing BusyBox Step 2).
I pulled my battery and just tried to root again, it gets to the point of installing Superuser and freezes. I tried downloading an uninstall root app which didn't even show superuser. I also downloaded root explorer and tried to delete the superuser.apk from the system/apps folder and it failed to DL.
I am at a loss for what to do and would really appreciate any help in getting my phone rooted. I am in USB debugging and never installed any ROMS or anything previously. If there is any other information that would help troubleshooting this please let me know.
Click to expand...
Click to collapse
Here's the problem. SOC see's the superuser.apk in your app drawer, so it thinks you are still rooted. You aren't because you no longer have the su.bin (which is the reason none of the apps you have - including the 'unroot' app will work.). The fix for this is easy. When SOC says 'you are already rooted, would you like to root again', or whatever that message is, click yes. The worst thing that will happen is it will overwrite existing files with the same one (Have you ever opened a word document, and when you close it, it asks if you want to save, even though you haven't made any changes? Same thing). In this case, the files you need (su.bin and busybox) AREN'T there. So you don't even overwrite anything.
For the most part, rooting this phone is a pretty failsafe, and innocuous process. You can do it over and over again, and you won't hurt the phone in the slightest.
Txwolf1980 said:
Here's the problem. SOC see's the superuser.apk in your app drawer, so it thinks you are still rooted. You aren't because you no longer have the su.bin (which is the reason none of the apps you have - including the 'unroot' app will work.). The fix for this is easy. When SOC says 'you are already rooted, would you like to root again', or whatever that message is, click yes. The worst thing that will happen is it will overwrite existing files with the same one (Have you ever opened a word document, and when you close it, it asks if you want to save, even though you haven't made any changes? Same thing). In this case, the files you need (su.bin and busybox) AREN'T there. So you don't even overwrite anything.
For the most part, rooting this phone is a pretty failsafe, and innocuous process. You can do it over and over again, and you won't hurt the phone in the slightest.
Click to expand...
Click to collapse
Are there any other programs to use than SOC? When the dialog window pops up saying my phone is rooted I click yes, it goes through the process until it tries to install SuperUser. Once it get to that point it just freezes and is flagged as not responding by windows. Is there anything I should double check settings wise on my phone other than USB Debugging that could be causing the problem?
Vsoup25 said:
Are there any other programs to use than SOC? When the dialog window pops up saying my phone is rooted I click yes, it goes through the process until it tries to install SuperUser. Once it get to that point it just freezes and is flagged as not responding by windows. Is there anything I should double check settings wise on my phone other than USB Debugging that could be causing the problem?
Click to expand...
Click to collapse
As far as straight rooting programs, soc is the only one I know of that works. You said a factory reset didn't remove superuser from your app drawer? It should have. I spills try a factory reset in recovery, as opposed to the privacy section of settings.
The other option is to flash a pre rooted rom. A little more dangerous, if you don't know what you are doing, but gaurunteed to work. I have a territorial in this section that seems to with for everyone that's tried it. Our, if you want I can meet you in irc tomorrow evening, and we can look at it.
Sent from my SCH-I400 using Tapatalk 2
Txwolf1980 said:
As far as straight rooting programs, soc is the only one I know of that works. You said a factory reset didn't remove superuser from your app drawer? It should have. I spills try a factory reset in recovery, as opposed to the privacy section of settings.
The other option is to flash a pre rooted rom. A little more dangerous, if you don't know what you are doing, but gaurunteed to work. I have a territorial in this section that seems to with for everyone that's tried it. Our, if you want I can meet you in irc tomorrow evening, and we can look at it.
Sent from my SCH-I400 using Tapatalk 2
Click to expand...
Click to collapse
That's why I'm getting frustrated, after two factory resets through the privacy menu superuser is still in my app drawer. I think because it's flagged as a system file it isn't really touched when the phone restores it self. Are there any programs that would give me root folder access through my PC?
I really don't know much about doing anything with these phones, so I'd be a bit apprehensive about flashing new ROMs or anything that could brick my phone if I mess up. How can I reset it through the recovery menu? That at least sounds like something has a low chance of causing any irreparable damage.
I'm not sure if I think I'll be around later this evening, I'm on the east coast and don't think I'll be available until after 9pm.
Vsoup25 said:
That's why I'm getting frustrated, after two factory resets through the privacy menu superuser is still in my app drawer. I think because it's flagged as a system file it isn't really touched when the phone restores it self. Are there any programs that would give me root folder access through my PC?
I really don't know much about doing anything with these phones, so I'd be a bit apprehensive about flashing new ROMs or anything that could brick my phone if I mess up. How can I reset it through the recovery menu? That at least sounds like something has a low chance of causing any irreparable damage.
I'm not sure if I think I'll be around later this evening, I'm on the east coast and don't think I'll be available until after 9pm.
Click to expand...
Click to collapse
To reset in recovery, power down completely. Then hold the vol up, vol down, and power at the same time, until samsung logo comes up. It will color you into stock recovery (3e)
Using volume down to scroll, and camera button to select, choose wipe data/factory reset.
Next, scroll to yes, and select. Not sure if that will work to get rid of super user, but it's worth a shot.
If that direct with, let new knits, and I'll walk you through flashing a custom recovery, then a deodexed rom, if you'd like.
Sent from my SCH-I400 using Tapatalk 2
Txwolf1980 said:
To reset in recovery, power down completely. Then hold the vol up, vol down, and power at the same time, until samsung logo comes up. It will color you into stock recovery (3e)
Using volume down to scroll, and camera button to select, choose wipe data/factory reset.
Next, scroll to yes, and select. Not sure if that will work to get rid of super user, but it's worth a shot.
If that direct with, let new knits, and I'll walk you through flashing a custom recovery, then a deodexed rom, if you'd like.
Sent from my SCH-I400 using Tapatalk 2
Click to expand...
Click to collapse
I tried the wipe from the recovery menu to no luck, superuser is still in my app drawer. I'll probably have time tomorrow afternoon to jump on IRC. I really appreciate all your help so far, thank you.
Vsoup25 said:
I tried the wipe from the recovery menu to no luck, superuser is still in my app drawer. I'll probably have time tomorrow afternoon to jump on IRC. I really appreciate all your help so far, thank you.
Click to expand...
Click to collapse
I'll be around. Just pm me, when you know what time you will be on
Sent from my SCH-I400 using Tapatalk 2
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.