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?
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
Like the title says.
I'm in recovery, I wiped it all (unfortunately even the ROM as zip I put on it) and now I don't have no ROM on it and no zip to flash a ROM.
Thought this was no problem, knowing from smartphone recoveries to mount sdcard and copying the file on it. But Nexus 7, well, has no sdcard.
What can I do?
As it is now, I don't have nothing on it and rebooting it wouldn't lead to anything useful.
I need help.
What can I do?
Thanks in advance.
l33ch0r said:
Like the title says.
I'm in recovery, I wiped it all (unfortunately even the ROM as zip I put on it) and now I don't have no ROM on it and no zip to flash a ROM.
Thought this was no problem, knowing from smartphone recoveries to mount sdcard and copying the file on it. But Nexus 7, well, has no sdcard.
What can I do?
As it is now, I don't have nothing on it and rebooting it wouldn't lead to anything useful.
I need help.
What can I do?
Thanks in advance.
Click to expand...
Click to collapse
If you have Android SDK installed, you can use adb push to push the zip file to your internal storage. Put the ROM zip file in your Android SDK - Platform Tools folder on your computer, reboot the N7 into Recovery (connected to computer of course!), open Command Prompt window and change directories to where ever you keep your Android SDK (for me, it's: cd sdk/platform-tools). Then type:
Code:
adb push <name of ROM zip file> /sdcard
Wait, and after about 20 - 60 seconds it'll complete, then you can flash the ROM. It'll be on the root of your internal sdcard (/sdcard).
Sounds difficult for a bloody rookie like me - is there really no easier way? Like transfering via recovery by just telling recovery to mound internal-sd so that it'll pop up on my pc? (know that from CWM and 4Ext on my smartphone)
Or could you explain the steps so that even the bloodiest rookie of them all could understand it properly :-/
aaaw **** -.-
by the way, device is still in recovery
l33ch0r said:
Sounds difficult for a bloody rookie like me - is there really no easier way? Like transfering via recovery by just telling recovery to mound internal-sd so that it'll pop up on my pc? (know that from CWM and 4Ext on my smartphone)
Click to expand...
Click to collapse
Maybe, I don't know. Have you tried it? What recovery are you using? I use TWRP.
RMarkwald said:
Maybe, I don't know. Have you tried it? What recovery are you using? I use TWRP.
Click to expand...
Click to collapse
TWRP as well. Just unlocked, rooted and flashed recovery and now I wanted to have a custom rom.
I tried to mount data and what else there was in "advanced" - my PC doesn't show me anything
Edit: not in advanced, it's the point "mount"
Restock and reroot.You can use Wugfresh toolkit for this. You just install the toolkit and if you can boot in bootloader mode you're saved. That's what I did and it solved my problem.
Sent from my Nexus 7 using xda premium
l33ch0r said:
TWRP as well. Just unlocked, rooted and flashed recovery and now I wanted to have a custom rom.
I tried to mount data and what else there was in "advanced" - my PC doesn't show me anything
Edit: not in advanced, it's the point "mount"
Click to expand...
Click to collapse
How'd you root/unlock, toolkit of some type?
Using the adb command mentioned is the only way that I know of to push a file to your N7. It's not as difficult to do as it sounds.
RMarkwald said:
How'd you root/unlock, toolkit of some type?
Using the adb command mentioned is the only way that I know of to push a file to your N7. It's not as difficult to do as it sounds.
Click to expand...
Click to collapse
Toolkit by WugFresh - I may try to get into bootloader and get back to stock - hopefully it works...
l33ch0r said:
Toolkit by WugFresh - I may try to get into bootloader and get back to stock - hopefully it works...
Click to expand...
Click to collapse
Yeah that would work, as long as you don't re-lock via fastboot. That's what probably wiped out your sdcard, was the fastboot unlock of your device, as it wipes your sdcard.
andymihail said:
Restock and reroot.You can use Wugfresh toolkit for this. You just install the toolkit and if you can boot in bootloader mode you're saved. That's what I did and it solved my problem.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Is it important which current status I choose?
There are 2 to be chosen: Soft-Bricked/Bootloop and Device is on/Normal
If "Device is on" means, that it's turned on, then this'll be my choice, right?
Totally shocked right now
This ain't even my device :-/
RMarkwald said:
Yeah that would work, as long as you don't re-lock via fastboot. That's what probably wiped out your sdcard, was the fastboot unlock of your device, as it wipes your sdcard.
Click to expand...
Click to collapse
No, wiping of my /sdcard was all my fault. I guess I have to take all credit for that
Well downloading the Stock with the toolkit takes quite some time...
foolish me -.-
Thanks for your help so far.
I'll definetely report whether it worked or not
I've never used any of the toolkits out there, I've done it using adb/fastboot commands in a Command Prompt window.
l33ch0r said:
Is it important which current status I choose?
There are 2 to be chosen: Soft-Bricked/Bootloop and Device is on/Normal
If "Device is on" means, that it's turned on, then this'll be my choice, right?
Totally shocked right now
This ain't even my device :-/
Click to expand...
Click to collapse
I can't remember my choice, was a few months ago.
Don't think you can go wrong with either.
I would try device is on.
Sent from my Nexus 7 using xda premium
RMarkwald said:
I've never used any of the toolkits out there, I've done it using adb/fastboot commands in a Command Prompt window.
Click to expand...
Click to collapse
I would've used your solution immediately but I'm just too unfamiliar with this method
Toolkits are probably the easiest way - and it was pretty easy - who could expect me to wipe the zip, I just moved to the storage before flashing it?...
Why does this file has to be hosted on goo.im?
Goo.im gives me roundabout 120kb/s...
It took a while for me also, but in the end everything worked well.
Sent from my GT-I9100 using xda premium
andymihail said:
It took a while for me also, but in the end everything worked well.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I desperately hope to have the same luck...will the bootloader still be unlocked after that procedure? I understand that root definetely is gone, but that shouldn't be a problem at all.
l33ch0r said:
I desperately hope to have the same luck...will the bootloader still be unlocked after that procedure? I understand that root definetely is gone, but that shouldn't be a problem at all.
Click to expand...
Click to collapse
It will remain unlocked until/unless you run the fastboot command: fastboot oem lock
If you don't run this, it will remain unlocked.
Whoaaaa I could scream!
Now that I downloaded the right one and try to flash it through the toolkit, it tells me, that there's no adb to be found. He doesn't recognize the device in bootloader.
What should I do?
OH THANK GOD! Tried it via recovery, he found it and restarted into bootloader
First of all: thank you so much guys - I was really shocked, but it all worked out
One more question before I make the same mistake again. Where should I put the zip which I wanna flash? When I have it connected to the pc, it shows me a portable device where the folders of the internal storage are (like Alarms, Android, DCIM, Download etc pp) - that's where I put the ZIP before.
Shall I keep it there?
And another question: what should I wipe in order to get it done properly?
Edit: Figured it out - got me CWM, much more familiar with that one
but thanks again for all your help guys
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.
So I managed to break the digitiser on my Nexus 4 last weekend. I have most things off it anyway but there are a couple of apps I need to run to get the data I need. I would like to be able to use android screencast to run the couple of apps or use it to set up my bluetooth mouse so I can use that as the screen itself still views fine. However, I need to enable USB Debugging in regular operation.
My phone is rooted, has CWM as the recovery and I have the ADB platform tools downloaded to my mac. This for a Nexus 7 is the closest I have come to an answer of how to do it. However, I can't find these files so I guess they are somewhere else to change these settings?
Any help would be much appreciated, thanks!
If you have cwm, not into recovery and use adb to pull files you want off your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you have cwm, not into recovery and use adb to pull files you want off your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I can't seem to find build.prop to be able to edit it. I can find default.prop but when I do adb pull /system/build.prop it doesn't work just says 'does not exist'.
mike_dangerous said:
I can't seem to find build.prop to be able to edit it. I can find default.prop but when I do adb pull /system/build.prop it doesn't work just says 'does not exist'.
Click to expand...
Click to collapse
In your recovery, I use twrp, mount system. It should work then.
Sent from my Nexus 5 using XDA Free mobile app
Works! Brilliant thanks! Hopefully the rest of this works!
So I have managed to Brick my phone into a boot loop of the cyanogenmod startup symbol. What can I do now?
Can someone confirm what the file permissions should be for settings.db and build.prop?
mike_dangerous said:
So I have managed to Brick my phone into a boot loop of the cyanogenmod startup symbol. What can I do now?
Can someone confirm what the file permissions should be for settings.db and build.prop?
Click to expand...
Click to collapse
Permissions should be rw-r-r. There's always the factory image to flash. You're not bricked!
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Permissions should be rw-r-r. There's always the factory image to flash. You're not bricked!
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
OK so I'm stuck how do I flash a factory image then? And I can't wipe my data or else the exercise is moot. Is there a way I can flash an image with the USB Debugging I require enabled? That would make my life much much simpler!
mike_dangerous said:
OK so I'm stuck how do I flash a factory image then? And I can't wipe my data or else the exercise is moot. Is there a way I can flash an image with the USB Debugging I require enabled? That would make my life much much simpler!
Click to expand...
Click to collapse
This going to get some what experimental but it won't wipe your date. I assume your bootloader is unlocked Just flashing the factory image will wipe your data but.... Download the factory image and extract it using winrar or 7-zip. Inside is a zip file, extract that too. You should find a system.img file in there. Flash that in fastboot
fastboot flash system system.img
Hopefully that'll get you past the boot loop
Edit, I'd forgotten that I made this. It'll get you up and running too. http://forum.xda-developers.com/showthread.php?p=533289
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
This going to get some what experimental but it won't wipe your date. I assume your bootloader is unlocked Just flashing the factory image will wipe your data but.... Download the factory image and extract it using winrar or 7-zip. Inside is a zip file, extract that too. You should find a system.img file in there. Flash that in fastboot
fastboot flash system system.img
Hopefully that'll get you past the boot loop
Edit, I'd forgotten that I made this. It'll get you up and running too. http://forum.xda-developers.com/showthread.php?p=533289
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Your link doesnt seem to work?
mike_dangerous said:
Your link doesnt seem to work?
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks a lot, I have now successfully unbricked my phone, enabled usb debugging and through a series of key strokes turned on bluetooth and connected my mouse. However, somewhere in the process I appear to have lost all my app data which was the points of trying to get in there in the first place. What could have done this? All my data e.g. photos is there but my SMS are gone!
mike_dangerous said:
Thanks a lot, I have now successfully unbricked my phone, enabled usb debugging and through a series of key strokes turned on bluetooth and connected my mouse. However, somewhere in the process I appear to have lost all my app data which was the points of trying to get in there in the first place. What could have done this? All my data e.g. photos is there but my SMS are gone!
Click to expand...
Click to collapse
You most likely wiped the data partition while trying to fix the bootloop.
Would the data partition not be where everything else is stored?
Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Is this image modified so that USB debugging is ENabled?
Background: I'm in the same situation as OP. Broken screen/digitizer, USB debugging is DISabled, unlocked, rooted, CWM recovery. I need to ENable USB debugging, otherwise I just keep getting told "error: device offline".
theman5511 said:
Is this image modified so that USB debugging is ENabled?
Background: I'm in the same situation as OP. Broken screen/digitizer, USB debugging is DISabled, unlocked, rooted, CWM recovery. I need to ENable USB debugging, otherwise I just keep getting told "error: device offline".
Click to expand...
Click to collapse
If you boot into recovery and then type adb devices is it still offline? It shouldn't be. You can recovery data while in recovery if that's what you're trying to do
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
Yes, when I attempt to run adb while in recovery I still get told that the device is offline.
Not sure what the best solution is. I was thinking about trying to flash a modified factory image that is already set up to have USB Debugging Enabled because I can probably flash that without wiping data. However, I don't know if such images exist or, if necessary, how to make my own.
Clearly the OP got around it but I can't seem to be able to and I'm not sure what to do.
theman5511 said:
Yes, when I attempt to run adb while in recovery I still get told that the device is offline.
Not sure what the best solution is. I was thinking about trying to flash a modified factory image that is already set up to have USB Debugging Enabled because I can probably flash that without wiping data. However, I don't know if such images exist or, if necessary, how to make my own.
Clearly the OP got around it but I can't seem to be able to and I'm not sure what to do.
Click to expand...
Click to collapse
I would start by flashing a twrp recovery in your current cwm recovery. I.know you don't need usb debugging checked in trwp.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would start by flashing a twrp recovery in your current cwm recovery. I.know you don't need usb debugging checked in trwp.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well I'll start there and keep you posted. Thanks!
I was able to get TWRP running as my recovery. When I run adb, my device appears as "recovery", however, I'm not able to access the "build.prop" file to edit it so I can ENable USB Debugging. I think this is because I'm not able to remount "system" as read/write. Not sure what my issue is, but when I run adb root, it claims to be already in root, however when I run su in adb shell, it claims it can't find su. Any ideas?