Related
Okay, I am getting ready to root my phone tonight...
As far as all that - I think I got all that covered.
As far as flashing a recovery - I want to use amon-ra's - RA-evo-v1.8.0 found here - http://forum.xda-developers.com/showthread.php?t=705026
In that post it gives two differant ways to flash the recovery:
via fastboot
Code:
Copy recovery-RA-evo-v1.8.0.img to a location where fastboot can find it.
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)
via terminal app or adb => Make sure your rom contains flash_image!!
Code:
Copy recovery-RA-evo-v1.8.0.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img(press enter)
reboot recovery(press enter)
My questions are:
first of all - what is "Fastboot"?? I mean is it an application that I can download and install it this way?
second of all - what is a "terminal app"
&
third - what is "adb"?
I keep hearing the term "shell", is a "shell" the same as windows command prompt? Or is that "adb"?
I know these are probably stupid questions for most, but I like to have every thing ready to go before I tackle projects...
Any guidance would be greatly appriciated!!
J
Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.
terrel_b said:
Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.
Click to expand...
Click to collapse
Great, thanks for the response! That helps alot - I searched around a little while waiting for a reply and still didnt clear any thing up. I have already DL'd ROM Manager and I will just use that... I just like to have as much info as I can...
Thank you!
J
How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically
fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask
ifly4vamerica said:
How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically
Click to expand...
Click to collapse
Im using unrevoked... I am still running hboot 0.97.0000... thanks for the input, I appriciate it!!
J
roscoenr said:
fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask
Click to expand...
Click to collapse
Very helpful info - thanks!! I have already DL'd ROM Manger Pro...
Okay - another question, can i place the amon-ra recovery on the SD card BEFORE i root the phone or should I do that AFTER I root the phone? Just curious, I dont even know if it matters one way or the other... Just want to be sure before I do it...
Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...
JayStation3 said:
Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...
Click to expand...
Click to collapse
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.
alekosy said:
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.
Click to expand...
Click to collapse
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...
JayStation3 said:
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...
Click to expand...
Click to collapse
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
Everything is there, pretty much solid on the information. I hope it works out for you, if not don't RUSH and take your sweet old time browsing the forums for help. GL
Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell
alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
cool, I will read them and figure it all out... thanks for the info... i flashed amon ra last night, did a back up w/ TB... did a NAND back up through the recovery of the phone... Im just a little confused on the differant recoveries...
Jbcarrera said:
Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell
Click to expand...
Click to collapse
I thought I did reboot at least once, when I was preforming the NAND back up - but Im rebooting now and I will test it out again...
I do not have great 4G signal here at my house, so that may be it as well... I will mess with it and see whats up through out the day and let you know tonight...
I have noticed that my touch screen doesnt seem as responsive as it was and the phone in general is kind of glichy...
Ok, my 4G is still working... I must not have had a strong enuf signal at my house for it to kick in... No I'm having problems getting tether to work... I started a new thread on that one though...
Sent from the MATRIX... while plugged into my EVO... using the XDA app... from a galaxy far-far away.......
Accidentally broke my G2's screen [blank & unresponsive].
I'm getting a replacement from T-Mo ...but need to extract a some data from the phone's memory.
I've tried connecting it to my computer but I can't access anything unless I put in the Unlock Pattern on my phone (which I obviously can't)
Any suggestion on what I can do?
****Update*****
Screen went out but touch screen functionality remains [Screen Defect?].
I've been able to use ScreenCast to see my screen on my pc & use it to some degree.
Temp. rooted my 'broken' phone with Visionary, ran Titanium Backup ... now trying to do Clockworks Recovery.
...need some help with operating Clockworks w/ a Broken Screen..
More info on second page
If you install adb via the Android SDK, you should be able to extract everything you want.
http://developer.android.com/sdk/index.html
EDIT:
install adb
use adb pull to get what ever data you are looking for, probably something in /data/data/ ??
you can use adb shell to poke around on your phone
I think you might have to be rooted. I don't have an unrooted phone to test this on.
gee one said:
If you install adb via the Android SDK, you should be able to extract everything you want.
http://developer.android.com/sdk/index.html
EDIT:
install adb
use adb pull to get what ever data you are looking for, probably something in /data/data/ ??
you can use adb shell to poke around on your phone
I think you might have to be rooted. I don't have an unrooted phone to test this on.
Click to expand...
Click to collapse
I've had the SDK but I can't access my phone files because they are inaccessible from my PC + my phone doesn't have USB Debugging / ADB enabled by default...
I tried running ScreenCast to try and emulate my screen on my PC (something I've done before) but it wouldn't work because, as before, the phone to be detected as an ADB device
Other suggestions?
If nothing else what's a quick way to wipe all data to factory defaults (without relying on a screen )
SmartHat said:
I've had the SDK but I can't access my phone files because they are inaccessible from my PC + my phone doesn't have USB Debugging / ADB enabled by default...
I tried running ScreenCast to try and emulate my screen on my PC (something I've done before) but it wouldn't work because, as before, the phone to be detected as an ADB device
Other suggestions?
If nothing else what's a quick way to wipe all data to factory defaults (without relying on a screen )
Click to expand...
Click to collapse
If you have Clockwork recovery, you can boot into recovery mode and use adb.
shutdown
unplug the USB and shutdown- press and hold the power button for 2 seconds, scroll down on the trackpad several times and then press the trackpad button twice. it should shut down, or else pull the battery.
reboot into recovery
hold volume "down" and press the power button for a second and release. Wait 5 seconds and then press volume "down" once and press the power button. If all goes well, the phone should vibrate briefly. Wait a few seconds and then try adb.
Get a Ubuntu livedisk, boot from it and plug the phone in. You can see the phone's contents as well as sdcard. That would be the easiest. But if you can't do that and you have the latest clockwork mod, you will still need to mount stuff from recovery before you can access it. These instructions are relevant to the latest version (2.5+).
Once in recovery per gee one's instructions the menu is as follows:
Main Menu
- reboot system now <<- cursor
- apply sdcard:update.zip
- wipe data/factory reset
- wipe cache partition
- install zip from sdcard
- backup and restore
- mounts and storage
- advanced
By default "reboot system now" is select where it says cursor. Volume up/down to go up/down and trackpad to confirm. Power is to go back. The trackpad will also navigate for you, but it's hard to control so avoid using it for movement at all costs. It is also very sensitive to double clicks, try and make your click as quick and clean as possible.
Press Volume down 6 times and you will land on mounts and storage, then press trackpad (very quickly so as not to make it register a double click).
That menu is as follows:
Mounts and Storage
- mount /system <<-cursor
- mount /data
- unmount /cache
- mount /sdcard
- mount /sd-ext
- format boot
- format system
- format data
- format cache
- format sdcard
- format sd-ext
- mount USB storage
Your cursor starts on mount /system. Press trackpad once will mount system, pressing it again will unmount. Volume down will take you to data, and so forth. Then you can access those directories from adb, and do adb pull as others have suggested. Pressing it again will unmount it, and should be done. Keep in mind it will only unmount if you close all windows that point to that directory and leave the directory in adb shell (you can leave the directory by typing "cd /" to do that). If you stay in the directory or something is pointing to it, it will cause an error.
If you're unsuccessful, you can try doing a backup from clockwork.
From the main menu, press volume down 5 times and press trackpad.
The menu that appears is as follows:
- Backup <<-cursor
- Restore
- Advanced Restore
Simply click the trackpad again and it will perform a backup.
It will save the backup of the phone to the sdcard at /clockworkmod/backup/2010-12-8.x.x.x/
After that I'm not entirely sure how to extract it, hopefully someone else can help.
But simply put, get a live CD of linux and you go to Mounts and Storage and then to mount USB storage, you should have access.
Pic Please
How about "mount /system" or "mount /data" from the adb shell? This should be enough to poke around to extract files.
gee one said:
How about "mount /system" or "mount /data" from the adb shell? This should be enough to poke around to extract files.
Click to expand...
Click to collapse
*facepalm*
or that. if you go into adb shell, you can mount whatever directory and cp it to the sdcard. you can use 'umount' to unmount.
adb push/pull will not work when in adb shell, but you can easily copy it over to your sdcard with the cp command.
funkeee said:
*facepalm*
or that. if you go into adb shell, you can mount whatever directory and cp it to the sdcard. you can use 'umount' to unmount.
adb push/pull will not work when in adb shell, but you can easily copy it over to your sdcard with the cp command.
Click to expand...
Click to collapse
I just tried finding my G2 using an ubuntu 10.10 installation- it wouldn't find my phone unless I enabled USB mode, and then it would only find the sdcard. I'm still pretty new to ubuntu, so I might be missing something. It's like a brown version of my Mac!
adb push/pull will work from the terminal command line on your computer, not the shell.
Had some obligations I had to take care of but ... thank you for all the suggestions, I'll be trying them all to see which one I can get going!
I just got my replacement today & the first thing I noticed was the Z-Hinge issue.
Its looser than my original 'broken' phone right out of the box, even though the original has been thoroughly used for about 2 months...
so I gotta go thru Another replacement process ...
I suppose I'm going to keep getting replacements that people sent back for the Z-Hinge issue
gee one said:
If you have Clockwork recovery, you can boot into recovery mode and use adb.
Click to expand...
Click to collapse
^ I don't have any recovery programs on my device (unfortunately).
--
@ funkeee: I'll def. try this, seems promising.
ddgarcia05 said:
Pic Please
Click to expand...
Click to collapse
^ of?
gee one said:
How about "mount /system" or "mount /data" from the adb shell? This should be enough to poke around to extract files.
Click to expand...
Click to collapse
^ how would I go about and do that?
and as I mentioned before my device is simply set up for mass storage mode & I'm certain I need to get past the Unlock screen to access anything (but I obviously cant)
What kind of data are you trying to extract? It might seem obvious, but I think I should ask for the sake of completeness- is the data actually in the phone or on the memory card?
gee one said:
What kind of data are you trying to extract? It might seem obvious, but I think I should ask for the sake of completeness- is the data actually in the phone or on the memory card?
Click to expand...
Click to collapse
Well I can get the data from the memory card via my replacement G2 or an Sd adapter...but its mainly messages and some miscellaneous content / apps I had saved on the phone itself & the settings; its not a Big deal, but its something I'd like to port over.
If I didn't have a lock on it I could've managed my way through the menus using hard keys w/ my replacement as a guide but I have no way of doing it.
I wish there was an easy way to make a backup... still haven't got time to try the methods mentioned before, but I'm going to try and give it a go tonite.
Do you have a stock, unrooted phone? If you installed hboot-eng.img then there might be a chance.
gee one said:
Do you have a stock, unrooted phone? If you installed hboot-eng.img then there might be a chance.
Click to expand...
Click to collapse
yup, stock & unrooted... any hope?
SmartHat said:
yup, stock & unrooted... any hope?
Click to expand...
Click to collapse
I'm out of ideas, for whatever that is worth.
Thank you very much for the input, everyone.
I managed to get my phone into USB Debug mode & I've been able to open up a lot of options... (since I can finally use ADB).
So, Now I'm using my previously installed Android ScreenCast to see my previously Dead Phones Screen! -- Gotta love Android!
-- Now, can anyone suggest the best method for me to a image of my device, so I can flash it onto my replacement?
A Nandroid backup would be perfect, but you don't have root.
adb pull /data/app /somewhere/on/your/pc/app
will back up non-system apps, but not the settings or data
adb pull /data/data /somewhere/different/data
will grab your settings and data, but there is mix of other stuff in there as well that doesn't restore so well because it also contains other data. I think someone who is well versed in sqlite might be able to put it all back together.
Are there any data that you are looking for specifically? SMS? Browser bookmarks? etc?
gee one said:
A Nandroid backup would be perfect, but you don't have root.
adb pull /data/app /somewhere/on/your/pc/app
will back up non-system apps, but not the settings or data
adb pull /data/data /somewhere/different/data
will grab your settings and data, but there is mix of other stuff in there as well that doesn't restore so well because it also contains other data. I think someone who is well versed in sqlite might be able to put it all back together.
Are there any data that you are looking for specifically? SMS? Browser bookmarks? etc?
Click to expand...
Click to collapse
well I just temp rooted my 'broken' g2 ... ran titanium backup; Flashed clockworks recovery & now am backing up again(just to have all my bases covered)
When I went in to 'backup current ROM' in the Clockworks app, phone turned off and my Screen Cast disconnected... So I have no means of checking if I need to do anything else before my Rom's backed up
*ed-*
...but then again, since I have Visionary Temp root, wouldn't Clockworks loose its super user privileges when it restarted?
Answered my own question.
So it looks like nothing else will be possible unless I permaroot, which would void my warranty, meaning I won't be able to send it back in to T-mo
You can check the clockworkmod folder on your sd card to see if the backup completed. There should be 4 or 5 .img files if it ran.
Sent from my CyanogenMod Vision
I recently flashed a new rom and got stuck in a bootloop. I use teamwin recovery. I'm planning on following the guide by efrant http://forum.xda-developers.com/showthread.php?t=1626895 but I want to copy all of my data to my computer. I can use adb commands and my phone shows up under adb devices. I tried searching for adb commands to copy files to computer but everything I found seems to be how to copy files to the phone.
I looked at another thread about using adb to backup but it appears that I need to have my phone on and running normally. http://forum.xda-developers.com/showthread.php?t=1420351
I used the command "adb pull /sdcard/clockworkmod" to try to recover my nandroid backups but I want to be able to pull everything off of my phone
I tried using the command "adb pull system" but it doesn't pull anything. Is their a way to pull everything from my phone and put it on my computer so I can eventually copy it back?
Thanks a bunch.
What exactly do you mean by all of your data / everything? Most of your data is stored on your sdcard anyway. There's not much you'd lose.
adb pull /sdcard/ ~/Desktop/ [as an example].
If you wanted ALL of your data, i.e. factory image backup, you should've done that before flashing a new rom.
You cannot pull /system as its protected and would need insecure adbd for that to work. You could try to dd entire partition blocks, but i don't see the point. Just flash a factory image.
P.S. If you're in a bootloop, you can use adb in your recovery.
How do I find where the backup goes? I did "adb pull /sdcard/"
I did have a nandroid backup but I want to make sure I get all of my files and music off just in case
you have to tell adb where you want the files to go. you only gave it one parameter.
http://developer.android.com/tools/help/adb.html
go read syntax.
Zepius said:
you have to tell adb where you want the files to go. you only gave it one parameter.[/url]
go read syntax.
Click to expand...
Click to collapse
So I want to make sure I read this right, if I type in "adb pull /sdcard/ G:\backup" then it should copy everything from my sdcard folder into my backup folder on G: right?
yes.
Zepius said:
yes.
Click to expand...
Click to collapse
Awesome, thanks for your help.
Okay so my father was about to flash to my rom. We Wiped data, cache, delvik, and installed rom. Said it worked and rebooted the phone. Phone tossed us into the CWM again and we tried flashing again and it gives us error #7. Soooo, We did NOT make a backup and every time we try to reflash the rom it gives us error 7. We can't get the Phone to be detected by the computer so we can at least grab his data. The thing here is we can't afford to lose the data on the phone (I know, should have made a backup). Any advice on how to proceed would help significantly. I've never seen this kind of issue in my years of rooting android phones. It just sits at the Google screen and doesn't go anywhere.
Phone is Verizon Galaxy nexus running (was) MIUI
Update: Tried flashing back his previous rom (MIUI) and I'm getting the error 7 again. Even though that past rom worked perfectly. This is all very frustrating.
What data do you want to keep? Internal storage won't be wiped when flashing ROMs, and as for app data, contacts, SMS, etc, as long as you can enter CWM, you can pull them out of the phone with "adb pull".
Sent from Samsung Galaxy Nexus @ CM11
AndyYan said:
What data do you want to keep? Internal storage won't be wiped when flashing ROMs, and as for app data, contacts, SMS, etc, as long as you can enter CWM, you can pull them out of the phone with "adb pull".
Sent from Samsung Galaxy Nexus @ CM11
Click to expand...
Click to collapse
Well the problem is I don't have the Nexus adb installed onto the PC, so I can't connect to the nexus through USB. Can I install adb and everything without being in the rom? also I'm trying to get the Titanium backup folder and the photos.
If you can get into recovery, that means you can use adb. Just install the driver (if you are on Windows) and adb should work.
tonychau77 said:
If you can get into recovery, that means you can use adb. Just install the driver (if you are on Windows) and adb should work.
Click to expand...
Click to collapse
What's the command for pulling pictures and Titanium backup?
Hitmanthe3rd said:
What's the command for pulling pictures and Titanium backup?
Click to expand...
Click to collapse
adb pull [remote file] [local file]
You can pull the whole folder from your phone. The folder of Titanium Backup should be /sdcard/TitaniumBackup or something similar. For photos it is in /sdcard/DCIM
tonychau77 said:
adb pull [remote file] [local file]
You can pull the whole folder from your phone. The folder of Titanium Backup should be /sdcard/TitaniumBackup or something similar. For photos it is in /sdcard/DCIM
Click to expand...
Click to collapse
I tried to install ADB for Nexus and it failed and I ran into many roadblocks. Can you link me a W8 64bit guide I can follow?
Hitmanthe3rd said:
I tried to install ADB for Nexus and it failed and I ran into many roadblocks. Can you link me a W8 64bit guide I can follow?
Click to expand...
Click to collapse
I don't know much about those drivers because I use Ubuntu (just for my phone). But you can refer to this thread.
http://forum.xda-developers.com/showthread.php?t=1583801
tonychau77 said:
I don't know much about those drivers because I use Ubuntu (just for my phone). But you can refer to this thread.
http://forum.xda-developers.com/showthread.php?t=1583801
Click to expand...
Click to collapse
I got ADB installed but cannot get the pull command to work. It's adb /pull and it's in a 0 folder and then Titanium backup and in the Tina user folder . What would be the command?
Hitmanthe3rd said:
I got ADB installed but cannot get the pull command to work. It's adb /pull and it's in a 0 folder and then Titanium backup and in the Tina user folder . What would be the command?
Click to expand...
Click to collapse
"adb pull /storage/emulated/0/YOUR-DIRECTORY/YOUR-FILE C:\" or something like that.
Sent from Google Nexus 4 @ CM11
Hey folks,
Last night I was editing a file located under "data/system/users/0/settings_ssaid.xml" and upon rebooting my phone, it's been stuck in a boot loop. I have an original copy saved in a different folder, but unable to access anything to replace it.
Is there any specific fastboot command I can run to swap the files (adb push, pull etc)? Only boot slot A is giving me an issue, and I was reading flashing system.img would be able to help, but I don't wanna do anything I'm unsure will wipe any of my data where I'd have to start over unless I've recovered some of that data first.
If I do have to flash any stock images, pls post the instructions for clarity.
Thanks in advance.
Assuming adb can actually access your device, while it's stuck in a boot loop (test this by running 'adb devices' and see if you receive a response)
You can run the following command to list all the files in your specific folder.
adb shell ls FILEPATH
Every file in your specific folder will be listed. You can then do the following to pull/push your file
adb pull FILEPATH
adb push FILENAME FILEPATH
Of course you need to place the file that you want to push in your ADB folder.
Mind though, that simply replacing your edited file with the backup might not solve your bootloop.
You can always look up available commands here
adb shell ls - Android ADB Shell Commands Manual
Morgrain said:
Assuming adb can actually access your device, while it's stuck in a boot loop (test this by running 'adb devices' and see if you receive a response)
Click to expand...
Click to collapse
Yes, I can access adb and my device while it's booting up, but once it reboots I lose connection. Unless I can interrupt the process I'd have to be very quick in my typing to copy files lol.
Even with the few seconds I have to type some commands to access the directory of the file I edited, I do get a permission denied error.
Would swapping to Slot B during boot allow me into the system, or even flashing the system.img file?
RetroTech07 said:
Yes, I can access adb and my device while it's booting up, but once it reboots I lose connection. Unless I can interrupt the process I'd have to be very quick in my typing to copy files lol.
Even with the few seconds I have to type some commands to access the directory of the file I edited, I do get a permission denied error.
Would swapping to Slot B during boot allow me into the system, or even flashing the system.img file?
Click to expand...
Click to collapse
No because your file is on /data.
The issue is that you can't push your file to /scard since (I guess) you can't even get beyond to the point where /sdcard is mounted.
So copying it from /sdcard will likely be too late in the boot process.
Pushing directly into /data does not work either as you would have to be root. In the old days you could run and in root mode but I'm not sure that is still possible.
Factory reset will work.
On devices with separate recovery partition it would be possible to change recovery to allow adb access to /data so then push old file via recovery... But I would not know how to do that on Pixel as recovery is s part of the boot partition.
So effectively, it's likely you're only solution is to do a full firmware flash along with wipe.
I would first try a full flash removing the -w to avoid the wipe. It may work.
TonikJDK said:
I would first try a full flash adding the -w to avoid the wipe. It may work.
Click to expand...
Click to collapse
Probably a typo, but I think you meant you need to "remove" the -w to avoid a wipe.
Lughnasadh said:
Probably a typo, but I think you meant you need to "remove" the -w to avoid a wipe.
Click to expand...
Click to collapse
Thank you! My post is fixed.
TonikJDK said:
I would first try a full flash removing the -w to avoid the wipe. It may work.
Click to expand...
Click to collapse
Ok, I'm rooted so to be sure I don't mess anything up, lol can you list the steps just as a precaution?
Obviously I'd be in fastboot / recovery mode, then perform a flash-all but remove the -w so as to not erase my data?
Once the system boots, all of my texts and setup should remain as is, or do I have to go and recover it?
Would I be able to install the OS again on the inactive slot to recover data, or does that not work that way?
RetroTech07 said:
Would I be able to install the OS again on the inactive slot to recover data, or does that not work that way?
Click to expand...
Click to collapse
Nope ... there is only 1 data partition, so even when you flash the OS to the inactive slot, it would still use the same data partition. Moreover, it is then likely to upgrade/convert some files on /data which might result in not being able to go to the previous version in the old slot.
RetroTech07 said:
Ok, I'm rooted so to be sure I don't mess anything up, lol can you list the steps just as a precaution?
Click to expand...
Click to collapse
See https://forum.xda-developers.com/t/...thout-wiping-data-and-retaining-root.4356065/
so, unfortunately doing a full flash without wiping data didn't work. I'm almost inclined to believe that if TWRP was available for the P6/P, that I could go and push the file I had saved back into the directory of where it was and save myself from this mess.
I'm kicking myself because I'm usually backing up my data before I modify any system files, but this one time I hadn't done so and I had Google's backup turned off at the time, so I'm gonna have to lose some text messages over the last few days with some folks I enjoy speaking to. I do have some saved from late last week, but nothing from the weekend up until now.
As you said you can access ADB while booting, why not push/remove/replace the file while booting, even if this takes multiple boots to perform all commands, it should work assuming you can also use SU, if you can't, none of the below will work.
Code:
adb push <backup file location> /sdcard
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /sdcard/settings_ssaid.xml /data/system/users/0/
chmod 600 data/system/users/0/settings_ssaid.xml
I don't know why it's affecting your boot though, there's a .fallback file that the system should fall back to when the system notes that this file is corrupt.
If the above doesn't work, and you could try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /data/system/users/0/settings_ssaid.xml.fallback /data/system/users/0/settings_ssaid.xml
If that doesn't work, try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
And reboot, but again, I don't know why you're bootlooping from this, that file shouldn't be integral to booting.
Also, if you need to back up your data, why not just boot to boot_b, if it's not causing you issues? You really shouldn't have to reset your device to fix one problem - you could do a /data & /sdcard pull while booted to boot_b, or just run something like Titanium & SMS backup/restore.
DanielF50 said:
As you said you can access ADB while booting, why not push/remove/replace the file while booting, even if this takes multiple boots to perform all commands, it should work assuming you can also use SU, if you can't, none of the below will work.
Code:
adb push <backup file location> /sdcard
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /sdcard/settings_ssaid.xml /data/system/users/0/
chmod 600 data/system/users/0/settings_ssaid.xml
I don't know why it's affecting your boot though, there's a .fallback file that the system should fall back to when the system notes that this file is corrupt.
If the above doesn't work, and you could try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /data/system/users/0/settings_ssaid.xml.fallback /data/system/users/0/settings_ssaid.xml
If that doesn't work, try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
And reboot, but again, I don't know why you're bootlooping from this, that file shouldn't be integral to booting.
Also, if you need to back up your data, why not just boot to boot_b, if it's not causing you issues? You really shouldn't have to reset your device to fix one problem - you could do a /data & /sdcard pull while booted to boot_b, or just run something like Titanium & SMS backup/restore.
Click to expand...
Click to collapse
I appreciate the help but I can't go back as I've already wiped everything minutes before you sent this. If I had the above commands sooner I would have loved to try, although I'm not really sure why this became an issue in the first place. I tried booting to slot B, using both patched and normal boot images but it wasn't working, unless I did something wrong.
All I remember is installing an app to edit UDID for individual apps that I've used in the past, but because it wasn't identifying root properly, to which I'm assuming is an Android 12 issue, I decided to follow instructions for manually editing such IDs in the file I edited in my OP.
After I rebooted, I remember the main system about to start and seeing the Google boot logo with a percentage # go all the way up to 90%, then that's where the boot loop started. My guess at this point is either the app or the file I edited caused an issue, because I did nothing else up until that point. What's odd, is that after I formatted the whole system and rebooted, I saw the same percentage appear on screen after installing the same app to see if that was the issue, but it booted fully just fine.
I was going to just keep fighting this and keep the phone the way it was until I could maybe fix everything, but figured there's nothing I could do at this point since trying a flash of everything failed. I was up until 5am last night and it's almost 4 am with me trying to fix this. I feel defeated and upset because I don't believe I had to wipe this in the first place, and could have likely saved all of my data. I didn't have Google's backup option turned on and hadn't backed up my text messages because I was dumb. I'm more upset with myself than the phone honestly.
RetroTech07 said:
I appreciate the help but I can't go back as I've already wiped everything minutes before you sent this. If I had the above commands sooner I would have loved to try, although I'm not really sure why this became an issue in the first place. I tried booting to slot B, using both patched and normal boot images but it wasn't working, unless I did something wrong.
All I remember is installing an app to edit UDID for individual apps that I've used in the past, but because it wasn't identifying root properly, to which I'm assuming is an Android 12 issue, I decided to follow instructions for manually editing such IDs in the file I edited in my OP.
After I rebooted, I remember the main system about to start and seeing the Google boot logo with a percentage # go all the way up to 90%, then that's where the boot loop started. My guess at this point is either the app or the file I edited caused an issue, because I did nothing else up until that point. What's odd, is that after I formatted the whole system and rebooted, I saw the same percentage appear on screen after installing the same app to see if that was the issue, but it booted fully just fine.
I was going to just keep fighting this and keep the phone the way it was until I could maybe fix everything, but figured there's nothing I could do at this point since trying a flash of everything failed. I was up until 5am last night and it's almost 4 am with me trying to fix this. I feel defeated and upset because I don't believe I had to wipe this in the first place, and could have likely saved all of my data. I didn't have Google's backup option turned on and hadn't backed up my text messages because I was dumb. I'm more upset with myself than the phone honestly.
Click to expand...
Click to collapse
Ah damn, I was too late!
The 90% thing sounds like the November Google Play services updated - mine updated yesterday and I got the same thing when I rebooted, maybe something between the two got corrupt.
Yeah, I get that, I've had more than my fair share of self inflicted (and not so self inflicted) problems that have lost me data but you live and you learn I suppose