Hi there,
I am stuck in a unique situation where my Android phone is acting strangely. It appears that all apps lost internet and/or SD card storage permissions. From the phone no app can read/write/access storage or internet. I can still use adb to look at the SD card (both internal and external) on the phone, I can install a package using adb, I can pull files using adb, but I can't write or delete any files using adb.
I wonder if there is a way to regain those permissions by using adb? Sending some package and execute some commands to force Android to reload the platform.xml? Does it have anything to do with KNOX on the device somehow getting into the way? When I put the phone in Download Mode I still see KNOX not being tripped (0x0).
The Android version is 4.4.2.
P.S. Forgive me if this post seems to be out of place. I was posting similar questions in the specific phone forum but I got little success there. So I decided to post the question here in the generic Android area, hopefully it is the right place where there are many more developers who have experience with Android in general can help.
Thanks
Related
Greetings,
I have two Vibrants - one I bought from TMobile (and running stock everything), and one I later bought on eBay (running Froyo thanks to TeamWhiskey). I bought the second phone so that I could mess around with flashing ROMs and be able to brick a phone without it mattering. Hah.
Last night, for no reason I can discern, my stock TMobile Vibrant phone spontaneously soft bricked itself. My eBay test phone is fine.
I don't hugely care WHY the Tmobile phone bricked itself, but what I do care about are the pictures that are on the internal storage area.
I used Odin last night to flash in T959UVJI6.tar (but I did NOT use the 512.pit file). One of the posts I read said that doing so should fix a soft brick, without messing up the internal user storage area where pictures are located. No change - when I power on the Tmobile phone it hangs at the Galaxy S logo and then goes black.
Does anyone have any suggestions of how to access the internal storage area of a soft bricked Vibrant? And/or, can someone explain or point me at an explanation of what impact using a PIT file (vs not) and checking the "reformat" box in Odin (vs not) will have on the internal storage area? I don't care about overwriting the apps - I am just hoping there is some way to pull off the pictures or unbrick the phone WITHOUT deleting them.
Many thanks!
Wrong section..probably going to get flamed. Odin again with the pit file and you still wont lose pics and stuff. But next time...Q and A section...not being a ****, but that's where you ask all your questions.
sent from the other side of my galaxy.
jmercil said:
Wrong section..probably going to get flamed. Odin again with the pit file and you still wont lose pics and stuff. But next time...Q and A section...not being a ****, but that's where you ask all your questions.
sent from the other side of my galaxy.
Click to expand...
Click to collapse
Thanks for the reply. Is there some way I can move my post to the Q&A section? Or is that something only a Mod can do?
Also, do I check the reformat box or leave it unchecked?
Thanks again.
noise said:
Thanks for the reply. Is there some way I can move my post to the Q&A section? Or is that something only a Mod can do?
Also, do I check the reformat box or leave it unchecked?
Thanks again.
Click to expand...
Click to collapse
No need to reformat.
That's only for special occasions, really. And yeah, as far as I've seen, only mods can move posts.
yeah i would also like to know to that. the other day i deleted the 3d gallery app apk odex files because it was annoying the hell out of me with it's referenced folders - i tried clearing the default folder and but it was still showing random pictures from the shutdown folder and where ever else - so what did i do? i backed up the apk and odex file then deleted them from the system folder. rebooted w/o any issues - then i tried installing the apk... nothing - kept giving me a failed app install notification. i tried this 3-4 times then gave up. at this point i restored the apk/odex file to the system folder and rebooted the phone - nothing... gets past the galaxy s animation screen then screen goes black... nothing....
tried multiple reboot and keeps getting to the same black screen of doom - the other odd thing is windows do recognize it after it gets past the galaxy s boot screen and into the blank screen when i check in the device manager
ADB pull /sdcard/"whatever u have on ur phone"
Learn ADB
Reading is Fundemental
I'd also like to know if there are anyways to access the internal memory of a soft bricked phone. I know I can use ODIN, but I could fix the problem right now sans computer or USB if Clockwork recovery could access my sd card; I flashed a new kernal on stock JI6 and apparently needed to to flash a backsupport.zip first.
So, I don't have a cable with me, so can't use ODIN, clockwork recovery doesn't restore kernals and doesn't access the SD so... I'm screwed until I get home (not a huge deal). Alternatively, I could also not get clockwork to USB mount so I don't think that works either.
boimarc89 said:
ADB pull /sdcard/"whatever u have on ur phone"
Learn ADB
Reading is Fundemental
Click to expand...
Click to collapse
lol thanks man. but i also tried that. adb can't recognize it - and i found out it's the hard lock t-mobile version where doing the three button power up does not get you into the recover screen. unless i read that wrong? lol
Update: I used Odin again, this time with both the TAR and the PIT file. Same result as last time. Odin appears to have completed copying everything over successfully, but upon reboot, I still get the soft-brick Galaxy S that doesn't go away.
I didn't try ADB earlier because all the posts/various docs I read thus far seemed to imply that ADB needed a normally functioning phone - not one that got stuck at the Galaxy S logo. I was wrong.
Here's what I did, hope it helps someone else. [Commands below assume you're using windows, and want to copy the entire contents of the internal SD memory (called "/sdcard") on your PC that you created (e.g., "c:\sdcard"]
1. Install ADB
2. Plug in soft-bricked phone and power on
3. Run command prompt and navigate to the directory where adb.exe is located. In my case, it was C:\Program Files (x86)\Android\android-sdk-windows\platform-tools.
4. From the command prompt:
adb pull /sdcard c:/sdcard
NOTE: the c:/ slash should be as shown - not c:\ as you would normally type under Windows.
392 seconds later, I had all 8G of photos on my PC.
I still don't know why the stupid phone won't boot properly, but now I don't care and can blast everything away. Thanks to everyone who contributed. Next time I'll be sure to post in Q&A instead.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
spencerj2001 said:
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
Click to expand...
Click to collapse
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
no adb does not see my device but i can access the internal sd card
Swiftks said:
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
Click to expand...
Click to collapse
spencerj2001 said:
no adb does not see my device but i can access the internal sd card
Click to expand...
Click to collapse
If you can access the internal card, its weird that adb can't see your device... oh well... try reverting to a earlier/different firmware via a blob. See thread in dev section.
Sent from my CM7 Atrix 4G
i did exactly the same mistake: i uninstalled some system apps (the asus preinstalled apps, with titanium) without unlocking the bootloader, and after a wipe from the stock recovery i'm not able to go beyond setup configuration, it always stops. but i can see and use internal and external memory from my computer. did you find a solution?
Hi, Because of the issue I described below. I need to have a custom recovery to have acces to the internal memory from the recovery menu.
Currently my phone is not rooted. If I understand all correct I need to flash a recovery like Philz.
Will this affect the data which is now stored on my phone? This since that's my main goal, regain access to that data and copy it. If flashing my phone would erase this, there is no need for me to flash it at all.
All i need is access to the internal SD memory.
Thanks for any replies
Originally Posted by chris74! View Post
Hi,
I have a samsung galaxy s3 GT-i9300.
Since this morning it's in some sort of bootloop. It boots, shows the lockscreen for about 15 seconds then powers down to automaticly boot again.
I have a replacement phone, so would like to transfer some data from the internal SD memory to an external SD card. Problem is... the phone is not powered on long enough to do this!
I tried to clear the cache, also booted in safe mode (also shuts down in safe mode).
My only concern is to get some data from the internal SD memory. Any suggestions for a workaround?
I've so far followed these instructions:
Pre requisite is having adb "installed" on your windows PC. Download THIS file and follow the instructions in the readme.
You need to observe the following. For android 4.1.x and earlier, /data/media for android 4.2.x and newer, /data/media/0 - I will assume 4.2.2 for this guide,.
1) Boot into recovery, connect usb and go to "mounts and storage". Toggle the "mount data" options to mount these partitions. Tip, when mounted, the option then becomes "unmount data"
2) Open "cmd" in Windows and type the below code, which will copy all your data to a folder called sdcard on your windows desktop
Code: adb pull /data/media/0/ c:\users\rootsu\desktop\sdcard
Also note, this assumes you have windows vista or newer. Also, it assumes your windows username is rootsu.
That's it, simple.
Click to expand...
Click to collapse
No it won't affect data
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Errors while downloading from internal memory
Hi,
I'm trying to get access to the internal memory of my Sansung Galaxy S4 GT-i9300. This since the phone seems to be in some sort of bootloop. Before going back to factory setting i want to secure all data which is stored on the phone. Mainly my whatsapp history.
I have rooted my phone and installed Philz as custom recovery. I have downloaded the latest drivers for my phone and installed adb on my win7-64 client (dutch installation).
Now in a shell I run:
pull adb /data/media c:\gebruikers\me\ff
I get the following error:
cannot create directory c:]gebruikers\me\ff\Samsung/Music/etc... : No such file or directory
Can anyone help me to point out what I'm doing wrong here?
chris74! said:
Hi,
I'm trying to get access to the internal memory of my Sansung Galaxy S4 GT-i9300. This since the phone seems to be in some sort of bootloop. Before going back to factory setting i want to secure all data which is stored on the phone. Mainly my whatsapp history.
I have rooted my phone and installed Philz as custom recovery. I have downloaded the latest drivers for my phone and installed adb on my win7-64 client (dutch installation).
Now in a shell I run:
pull adb /data/media c:\gebruikers\me\ff
I get the following error:
cannot create directory c:]gebruikers\me\ff\Samsung/Music/etc... : No such file or directory
Can anyone help me to point out what I'm doing wrong here?
Click to expand...
Click to collapse
Can I have a screenshot of the error please?
Also, have you read:
General > Sticky roll-up thread > S3 storage (data recovery)?
I have laid out the adb commands fully here.
Please can you use proper thread titles?
HI,
Since I'm a new user i cannot post links yet, so i've put a screenshot here postimg.org/image/ngflqe3yt
I did read: General > Sticky roll-up thread > S3 storage (data recovery)?
I was a great help and pushed me approx. 90% on my way. Now i'm stuck on the last part.
thanks again!
Does the folder "ff" exist?
the directory ff is existing. However the subfolder Samsung was not. So i now created this and ran the same command again. And... it's copying all data from my mobile!!!
Now i can go back to factory settings or try a custom ROM since i'm not that happy with touchwizz.
Just awesum! I thank you for this forum and the help provided.
chris74! said:
the directory ff is existing. However the subfolder Samsung was not. So i now created this and ran the same command again. And... it's copying all data from my mobile!!!
Now i can go back to factory settings or try a custom ROM since i'm not that happy with touchwizz.
Just awesum! I thank you for this forum and the help provided.
Click to expand...
Click to collapse
Oh ok. Thats good. Its odd you had to create samsung though but never mind. The weird thing was how after samsung, the \ turned to /
The Samsung folder justy contains some sample music & video.
I could have seen this myself, guess it just got a bit late yesturday.
Anyway, great help. I will now see if i can bring my S3 back to live or turn it in for repair.
I would like to be able to download apps directly to my SD card. I found some instructions online on how to set this up without "rooting". If you are familiar with the process I would appreciate some help. I got to the part where you are supposed to type the command "adb devices" but my phone does not come up. Why is this and what can I do? I would appreciate if you had a link to a troubleshooting page that already addressed this as well.
root it
it is the best way to move app to sd
u can use l2sd, a2sd
or u can edit your vold.fstab(system/etc)
If you have a Samsung it simply can't be done. I have a feeling it's the same with other manufacturers if they aren't already set up for "app to sd". Even rooting won't get it done with a Samsung. There are ROMs that give app to sd functions and there is flashable software that gets the job done. Still no root, no app2sd unless the manufacturer has included it in the firmware.
Hello and thanks for reading / helping if you can.
In brief, I have a Samsung Tab 2 GT-P3110 tablet which was running android 4.2.2. It's main use was as a controller for my sonos sound system which no longer supports my device. I thought I'd try and update it rather than simply chuck it into landfill for no good reason other than it was old like me! I know almost nothing about what I am doing, sorry!
So far I have I think 'rooted' the device using something called odin, and installed the clockwork recovery mod. I have also installed the Samsung drivers onto my PC and I have on my pc a zipped file which I believe will install a newer version of android (perhaps some guidance might be required for best file to go for). Unfortunately I am unable to see my tablet's sd card (or anything to do with the tablet) when connected to my pc via USB in order to copy it. Moreover I have copied the same file to a micro sd card but when I put this directly into the tablet and try and boot off the external card I get an access error and the card is not read.
I am out of ideas now and wonder if one of you clever people might be able to help me? I think I read somewhere about having to switch on USB debugging and USB sharing or the like BEFORE rooting. The instructions I used only mentioned the former and so that's all I did. Maybe I've locked myself out for good.
Thanks again, Pezos
Blimey, I really must have killed it! Surely someone out there can help me fix it?