Hi all,
I hope you can help as something very strange and unusual has happened to my Galaxy S3 LTE i9305 (on Orange in UK). Samsung technical support tell me they've not heard of the issue before as do the official repair shop. I have never installed any unusual software or tried to access the internals etc.
On Sat 26th Oct, in the evening, the phone was connected via USB to my laptop charging. There was no data transfer taking place, and the laptop was idle. The phone was not in use, nor was I nearby but randomly it showed the Samsung splash screen logo - it looked a little weird as it was pure black but with random speckles of coloured dots (which made it look like a Galaxy - I thought perhaps I hadn't noticed it before). I was unable to reset so took the battery out and replaced. It did the same thing and then on the second time of removing hte battery the screen became completely white with black marks generating a fuzzy effect - it's been like this ever since.
I get the white fuzzy screen if attempting to turn the phone on, or attempting to recovery mode, however if going to the install option (which I assume happens before Android boots), the screen is absolutely fine and proves not to be at fault. I should add the screen is cracked slightly, it has been since April and is not the cause of this random error.
Tech support tell me that they'll happily accept it back but ultimately, they will wipe the phone and send back as reconditioned. I've tried to connect via Kies, device not found - nor is it when connected to a computer - infact the computer tries to 'install device drivers'.
I'm sure everyone says this however I am an organiser of a large local festival in the UK and the phone has some very important detail storesd in the ColourNote app which I need to access - also the contacts appear not to have synced with GMail since May.... I'm desperate to access these files, for money too potentially, but cannot afford to go down the simple, wipe and reformat easy option. Can you help? Do you know any software that can access data from the internal memory card (note I've removed the external card which contained the photos) How about once the phone has been wiped, to try and see if anything can be recovered then.
Would really appreciate your support, this developer community is my last option and you're normally so awesome, as can't find any reference to the problem online.
Is your colour note app not synced ??
You can try RECUVA data recover.
You need to read the faqs and guides first .
Including the one that covers storage and recovery ..
Samsung reject warranty on phones that have damaged screen .
JJEgan said:
Is your colour note app not synced ??
You can try RECUVA data recover.
You need to read the faqs and guides first .
Including the one that covers storage and recovery ..
Samsung reject warranty on phones that have damaged screen .
Click to expand...
Click to collapse
Hi,
....no I had never set it up. So ironic that was on the to do list in the app.
I'll look into Recuva, is that for before or after I send it off. Is there much chance do you think?
Yes, sorry. I meant to say I also have phone insurance which covers the screen so will have it off to them first, and then onto Samsung - ie 2 places of data wiping!
Thanks for your reply though,
Kind of hoping I may just be able to fix the problem, even if only temporary, but realise it's unlikely
s_boddy said:
Kind of hoping I may just be able to fix the problem, even if only temporary, but realise it's unlikely
Click to expand...
Click to collapse
Hi mate,
You can try flashing just the system (and boot) images if you think it's a software issue.
That way your data partition will be intact.
Instructions:
Step 1) Download the Stock ROM you want to use
Step 2) Rename the file from .tar.md5 to just .tar
Step 3) Open the .tar with WinRAR or something similar
Step 4) Extract: system.img (and boot.img if you want the Kernel)
Step 5) Create ODIN file from .img files http://forum.xda-developers.com/showthread.php?t=1484304
Step 6) Flash the new ODIN file to restore your firmware to Stock!
On Windows you can use Cygwin to run these commands if you don't have access to Linux.
NOTE 1: That guide uses recovery.img as an example but you can replace that text with system.img on the first line.
NOTE 2: If you are adding more than one file (eg. system.img & boot.img) simply list them one after the other with a space between each file.
NOTE 3: Do not include data.img, it WILL wipe your data! Do not include cache.img, hidden.img, these MAY wipe your data!
Best of luck, I hope this helps you out :fingers-crossed:
Have a great day!
-Shaz
So, here’s how you can recover data from a Soft-Bricked Android smartphone:
1. Once you’ve installed a custom recovery on your device, open it using the specific method for your device. E.g for Samsung you can turn off the device completely, then turn it on by pressing and holding Volume Up + Home + Power Key and you will be able to access the recovery. These methods vary for different devices.
2. Once in CWM or TWRP Recovery you will find a number of options.
For CWM Recovery, select “Mounts & Storage > Yes”.
In Mounts and Storage menu you will find some more options, from the list select “Mount USB Storage or the option depending upon your choice.”.
Now connect your phone to your PC using the data cable.
As soon as you connect your phone to your PC, the USB Storage / Internal Storage will open up in folder view.
You can copy all of your files to your PC now.
3. For TWRP Recovery, Select “Mount > USB Storage”.
Connect your phone to your PC and it will open up the USB / Internal Storage.
3. Copy your desired files.
That’s all! You can easily recovery all of your data stored on the internal storage of your Android device.
Related
I have a Verizon Galaxy Tab 7 (SCH-I800) and I can not link up to it in ADB.
I have installed the Android Development Kit, Samsung drivers, and downloaded CM10.1.
I was able to contact the tablet in command prompt through heimdall and push clockworkmod recovery.
I'm following this guide:
http://rootzwiki.com/topic/33743-ext...rd-only-guide/
I've removed the internal memory card.
I've modified the update.sh file and rezipped everything.
I just need to know WHY adb cannot find my device. When I type "adb devices" in the command line NOTHING shows up. I've tried reinstalling the samsung driver, reinstalling the driver that came with heimdall, and updating the samsung driver via windows update.
By the way, this device would bootloop at the verizon loading screen, could not be updated, and could not load its original android OS, therefore I cannot turn on debugging or anything like that. Alls I can do is access the "PC connection" yellow screen and the CWM bootloader I pushed with Heimdall.
By "Internal" Memory ya meant "External" Memory right? as the Internal Memory is the 16GB Flash ROM.
In any case all pedantry aside. Did you remember to check the USB Debug Setting?
I think you can find this under the Wi-Fi Settings (On the Samsung Stock ROMs), IIRC it should be near the "Samsung Kies / Media Player / USB Storage" Settings. On CM10 Builds you'll find it in the "Developer Settings" near the bottom of the List.
Pretty sure you have to check this "Flag" before you can use ADB on your Device...
In that case consider yourself bricked!
In this case I'd recommend you find the Overcome Recovery Package: HERE
Install such Driver that you may need, then fire up Odin3 v1.7
Then set your Device into Download Mode (e.g. Hold Volume Rocker down + Power till you enter the Download Mode Screen)
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
Most People would just use the XXJPZ (GSM modem.bin), here but, since you have a CDMA Phablet, you'll have to find and pick the correct modem.bin File that is the best match for your CDMA Device. This is also likely why your now soft-bricked.
Hopefully after all this rigamarole you'll land up on a Stock, non-branded Samsung Gingerbread 2.3.3 ROM.
To which I would just download This, and that should give you Root.
Without all that tedious mucking about with ADB.
The internal chip has failed. I cannot boot the device whatsoever. I removed it as the link states. Therefore i cannot check off debug mode on the tablet. I will try your suggested method and report back
Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.
If you look at the link I posted, my tablet was doing the same exact thing as pictured in the link. Saying it could not mount any files or anything. No matter what I did, it would just get to the verizon loading screen and keep flashing "verizon".
I haven't tried the "overcome" method as it didn't really seem like it'd work.
I want to ADB my device to push the new ROM to it. I've already formatted the SDcard as suggested in the guide. Since clearly no one is clicking the link and reading the guide, I'll post it:
Summary:
- Open up the device and take internal SD Card out.
- Re-assemble the device.
- Partition the external SD Card (3 partitions, two small ext4 and one big FAT32)
- Modify ICS or later ROM's update.sh to use partition 3 as external SD Card.
- Flash modded ROM via CWM (and Google Apps optional).
- Enjoy
Taking it appart:
Don't panic!, if you can use a screwdriver and build with Legos you are qualified to do this!
iFixit does a wonderful job of showcasing how to open the device up that I rather link to them than try to out-do them.
Follow their guide until step 13 then refer back to this guide. http://www.ifixit.co...Teardown/4103/1
Posted Image
To actually remove the Internal SD Card (that is not soldered to the board but in-fact glued to it), I recommend you take an exacto knife (or other small blade or thin screwdriver) and slide it around the edges gently; once the edges are loose, take your screwdriver under the chip and just pop it up.
Posted Image
There will be adhesive residue on the board, I recommend using some gentle solvent to remove it (I used a cloth with a little paint thinner).
Put everything back together (just follow the iFixit guide on reverse) and feel proud that you are done with the hardware mod.
Partition your external SD Card
I used three partitions (all primary, not logical) , two 500 MB ext4 and a FAT32 with the rest of the space.
Linux users will probably not require much help on deciding what software to use, but for Windows users MiniTool Partition Wizard does a good enough job.
Do note that your device will perform according to your external SD Card, so it's not a bad idea to invest in a category 10 SD Card.
Modifing the ROM:
Download your ICS / JB ROM of choice, unzip it and open update.sh
Edit both line 31 and 35 to be as bellow
SD_PART='/dev/block/mmcblk0p3'Save and zip back.
Loading the Modded ROM to the SD:
Because we messed with the SD Cards, CWM will have a bit of trouble finding the external SD Card (until we flash our ROM).
Go ahead and connect your device to your computer and ADB the following command:
adb shell "echo /dev/block/mmcblk0p3 > /sys/devices/platform/usb_mass_storage/lun0/file"
That will allow you to access your SD Card from your PC, just copy your modded ROM to it.
Now, issude the following command:
adb shell mount /dev/block/mmcblk0p3 /sdcard
This will allow you to install the .zip file from CWM, go ahead and do that.
After checking partition types, your device will reboot and appear on a countdown to find the external SD Card, go ahead and reboot it manually before it does automatically (reboot to recovery with volume up).
Flash the .zip again, this time the installation will go successfully and you will have a working device.
Optionally, flash your desired Google Apps.
Now if we could get back to my original question, does anyone know why this device will not allow me to ADB it even when it's in download mode (a.k.a volume down/power button)
I actually got my tablet to boot up this morning for about 1 minute, then it shut off for no reason and did the "verizon" flash again when restarted.
priyana said:
Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.
Click to expand...
Click to collapse
Please correct my but, what other then the modem.bin File could brick such a CDMA Device?
AFAIK as long as he picks the correct CDMA modem.bin it should work alright?
In the case that I am in error, then how does One recover such a CDMA Device then?
I can easily recover this device if I can get the ADB commands to start working. I feel like no one is reading the instructions. If you look at the link where the instructions are, there is a screenshot of his device. All of that "unable to mount" etc is what was happening to my device, hence why I removed the failed chip.
If I could get my device to show up in ADB, I wouldn't be asking this question!
By the way, I'm on an HP DV6. I tried all this in windows 8 and got nothing, so I installed a backup hard drive and put windows 7 on (this is what I'm on now) to see if that'd make a difference. Still nothing. I also tried on my old Gateway desktop but in download mode my old PC (still USB 1.1 1GHz celeron 512mb ram) the PC has no clue what the tablet is.
So I finally got this thing to boot into 2.2. Now the touch screen is unresponsive and the battery goes to 0 as soon as it's unplugged. Going to take it apart in the morning and make sure everythings connected. Might try a new battery but if this thing doesn't show more promising results soon I'm going to just say screw it and get rid of it.
Edit: Touch screen works but is flipped. If I slide my finger side to side nothing happens. If I slide it up and down i can awkwardly unlock the device. I'm guessing reload the factory image?!
the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?
priyana said:
the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?
Click to expand...
Click to collapse
If you put it into download mode it shows right up in my device list, drivers for "samsung USB device" load up. I can contact the tablet through heimdall to load bootloaders, images, etc.
For some reason I got it working pretty good last night except the touch screen issue. I reloaded the stock rom again and am playing with the SD card partitions since that's how I got it to boot up the last 2 times. I dont even care if I can load Jellybean on, I just want a working tablet.
By the way, this is SOLVED.
It will now boot up using a Stock ROM plus the zImage + recovery from clockworkmod
My touch screen is flipped (so I have to slide up and down to get it to swipe side to side) but at least it's on now. Made a new thread to address the flipped touch screen issue!!
Hi,
Like many, I got the same problem after installing new ROM (Runymede KitKat 4.4), but even after reading many threads and advises in other sites, my phone is still bricked. Any help will be highly appreciated.
Details:
Loaded the ROM, was working, but no internal SD.
I was stupid enough to perform a factory default, then, being even more stupid (amazing, no?), deleted the ROM somehow.
Now I'm left with a brick which only accepts recovery mode, nothing else.
Phone is connected to a PC, with working cable (verified), but not recognized by PC.
When I enter the recovery, in FASTBOOT mode.
Same screen gives me the following:
******IR-KEY***
RUNNYMEDE PVT SHIP S-OFF (yes, I'm sure it's off)
HBOOT-6.25.444
RADIO-3831.16.00.16_M
eMMC-boot
Oct 20 2011.00:20:33
Now, I managed to go to recovery, and browse there in file manager.
Went to system/etc/ in order to check vold.fstab, but it's not there.
Went to SDcard directory - no ROM zip file is there (of course. I deleted it...).
Bottom line - 1 Sensation XL stuck on boot, no ROM or installed system, no recognition by PC = nice paper weight.
The recovery I'm getting is TWRP (not CWM) and as I wrote, it's on S-off.
It's quite clear to me that first step is to somehow load a ROM.zip file to the device, but as I wrote - it's not recognized by PC (Yes, I did try to do USB mount via TWRP. No, it did not help. nothing recognized, even after replacing USB port and even on a different computer).
Tried few "magic tools" that meant to save HTC XL found in the web, no help. Youtube search brought me few guides, but all start at working device with working ROM installed, while mine has nothing.
Next (last?) was to try and transfer the zip file via ADB sideload, and here I got stuck:
Downloaded different kinds of ADB packages I found, but I don't understand how to use them. I'm not using LINUX/UNIX or any similar based OS, but MS WIN7. I assume that it needs to be done via CMD window, but couldn't find
a proper guide of how to try and transfer the file to the device. all guides seem to assume that I know what I'm doing, while (as result proves) I have no clue.
I'l be really thankful if someone can publish a dummy-proof, step-by-step guide for using ADB sideload method to identify the device, then transfer a new ROM to it.
Any other suggestions would be welcomed as well, unless it's something like "hold firmly, move your hand back and throw the piece of sh&$t on the nearest brick wall" or "paint in light Blue, drive to nearest beach and throw as far as you can".
Thank you for lasting the long post, and even more if you can suggest a solution.
dnt wrry
shemer_t said:
Hi,
Like many, I got the same problem after installing new ROM (Runymede KitKat 4.4), but even after reading many threads and advises in other sites, my phone is still bricked. Any help will be highly appreciated.
Details:
Loaded the ROM, was working, but no internal SD.
I was stupid enough to perform a factory default, then, being even more stupid (amazing, no?), deleted the ROM somehow.
Now I'm left with a brick which only accepts recovery mode, nothing else.
Phone is connected to a PC, with working cable (verified), but not recognized by PC.
When I enter the recovery, in FASTBOOT mode.
Same screen gives me the following:
******IR-KEY***
RUNNYMEDE PVT SHIP S-OFF (yes, I'm sure it's off)
HBOOT-6.25.444
RADIO-3831.16.00.16_M
eMMC-boot
Oct 20 2011.00:20:33
Now, I managed to go to recovery, and browse there in file manager.
Went to system/etc/ in order to check vold.fstab, but it's not there.
Went to SDcard directory - no ROM zip file is there (of course. I deleted it...).
Bottom line - 1 Sensation XL stuck on boot, no ROM or installed system, no recognition by PC = nice paper weight.
The recovery I'm getting is TWRP (not CWM) and as I wrote, it's on S-off.
It's quite clear to me that first step is to somehow load a ROM.zip file to the device, but as I wrote - it's not recognized by PC (Yes, I did try to do USB mount via TWRP. No, it did not help. nothing recognized, even after replacing USB port and even on a different computer).
Tried few "magic tools" that meant to save HTC XL found in the web, no help. Youtube search brought me few guides, but all start at working device with working ROM installed, while mine has nothing.
Next (last?) was to try and transfer the zip file via ADB sideload, and here I got stuck:
Downloaded different kinds of ADB packages I found, but I don't understand how to use them. I'm not using LINUX/UNIX or any similar based OS, but MS WIN7. I assume that it needs to be done via CMD window, but couldn't find
a proper guide of how to try and transfer the file to the device. all guides seem to assume that I know what I'm doing, while (as result proves) I have no clue.
I'l be really thankful if someone can publish a dummy-proof, step-by-step guide for using ADB sideload method to identify the device, then transfer a new ROM to it.
Any other suggestions would be welcomed as well, unless it's something like "hold firmly, move your hand back and throw the piece of sh&$t on the nearest brick wall" or "paint in light Blue, drive to nearest beach and throw as far as you can".
Thank you for lasting the long post, and even more if you can suggest a solution.
Click to expand...
Click to collapse
here i will help you...
first of all jst go to recovery, as you said it is twrp, then select mount option and again select mount storage and your pc will open up dialogue box which will be your sdcard...
if this FAILS....then go to wipe option, select advanced wipe and jst tick on sdcard option and click on repair drive......you will see sdcard details...
try it..
if you get any details of sdcard then reply me...
Hi.
Thanks for the reply.
I forgot to mention, did try the "mount" option, including wipe every option (separately and combined).
Still no sign from PC.
Micro USB port is good, I get charging of battery and PC responds when phone is connected, but looks like driver is corrupted or missing.
I'm pretty sure my only option is ADB sideload. Once I get the zip file on the phone, looks like I can proceed from there...
download htc driver
shemer_t said:
Hi.
Thanks for the reply.
I forgot to mention, did try the "mount" option, including wipe every option (separately and combined).
Still no sign from PC.
Micro USB port is good, I get charging of battery and PC responds when phone is connected, but looks like driver is corrupted or missing.
I'm pretty sure my only option is ADB sideload. Once I get the zip file on the phone, looks like I can proceed from there...
Click to expand...
Click to collapse
then you only need to download new htc driver and use windows xp if win7 fails...
other option is go to device and printers in win7, > right click on your android device device icon > troubleshoot it.... i think everything will be fine...
and if this will help then you are able to mount usb storage from mobile twrp recovery...
nirmalviper said:
then you only need to download new htc driver and use windows xp if win7 fails...
other option is go to device and printers in win7, > right click on your android device device icon > troubleshoot it.... i think everything will be fine...
and if this will help then you are able to mount usb storage from mobile twrp recovery...
Click to expand...
Click to collapse
Hi,
HTC driver (included in HTC sync) downloaded, no change.
Unfortunately, WIN XP is not really available...
The Android device is not there, that's exactly the problem.
Hi,
An update regarding this HTC.
I put it in my friend's lab, he found that the USB port connection was loose, so after some welding it's working, and phone is identified by the computer.
Managed to send it a ROM zip file, then flashed the ROM, phone is functioning, but...
Problem now is that the phone's internal memory (what HTC define as "SD card", although it's the internal flash memory) is still not found by the phone - e.g. impossible to take photos, get any files with whatsapp or any other storage related actions.
I did try to install another ROM, same result.
I think problem is derived from the fastboot version, which is (still):
******IR-KEY***
RUNNYMEDE PVT SHIP S-OFF
HBOOT-6.25.444
RADIO-3831.16.00.16_M
eMMC-boot
Oct 20 2011.00:20:33
Every former thread I saw in XDA or other site, related to 1.25.0 or 1.28.0 (ICS or JB), not this HBOOT.
Note that phone is in S-OFF, but memory is not yet found.
TWRP is installed, of course (so phone is already rooted).
IMHO, what I should do is replace the HBOOT version, but I have no clue of how to do so.
Found some old threads about this issue, but either the download links are broken, or the "tool" package in the link is disabled by Chrome browser due to trojan warning.
Would much appreciate if any of you can assist with clear step-by-step guide of what should be done in order to "save" the SD memory of the phone, as I could not find any proper guide even after spending much time searching.
Thanks in advance
Shemer.
As title says. Also when I connect to USB into my windows computer the N6
icon appears, when I click on it its blank, no files! I tried to copy my pics and it
says devise cannot accept!
Seems my storage partition is somehow lost. I tried to reflash 2x, same result.
Can anyone guide me on what to do.
CC
cc999 said:
As title says. Also when I connect to USB into my windows computer the N6
icon appears, when I click on it its blank, no files! I tried to copy my pics and it
says devise cannot accept!
Seems my storage partition is somehow lost. I tried to reflash 2x, same result.
Can anyone guide me on what to do.
CC
Click to expand...
Click to collapse
Try doing a factory reset from within Android, I hope this helps.
http://forum.xda-developers.com/nexus-6/help/64gb-stuck-23gb-t2970279
Read down a few posts. It worked for me on 5.1.1.
I also have the same problem but with the 32gb version.
I started with a locked unrooted 5.1.1 Nexus 6.
I followed the instructions from Google's file image site.
I unlocked the boot loader.
Then ran the flash all script that failed, so I manually flashed the phone.
Phone rebooted and started up fine.
I attempted to re-lock the boot loader but it failed.
When connected to a windows system the phone shows up on auto play but file explorer shows No files or folders.
Tried a factory wipe still nothing.
worked
knightsh said:
http://forum.xda-developers.com/nexus-6/help/64gb-stuck-23gb-t2970279
Read down a few posts. It worked for me on 5.1.1.
Click to expand...
Click to collapse
That worked! TY
Now my last problem, when I enable USB debugging, plug into computer accept the computer
on the N6 and then I goto transfer my music files etc like I have done a million times before,
The icon appears on the computer when I double click its empty and I cannot
write to it! Any suggestions?
CC
This happened to me. I performed the advice recommended above and this fixed it for me
Edit: Ha. You just beat me.
copy
danieljw said:
This happened to me. I performed the advice recommended above and this fixed it for me
Edit: Ha. You just beat me.
Click to expand...
Click to collapse
Can you copy files to device with usb?
CC
cc999 said:
Can you copy files to device with usb?
CC
Click to expand...
Click to collapse
Yes. The phone defaults to charge-only mode via USB, which prohibits file transfer; this is why the device folder was empty in Windows. Switch to MTP mode via the notification shade and it will appear as it normally does.
In addition, in Developer options, you can configure the default USB mode, so as to prevent this from happening in the future.
or, just move into the 21st century, and use a program like wifi explorer pro, and never have to connect with a usb cable to transfer anything ever again..
wase4711 said:
or, just move into the 21st century, and use a program like wifi explorer pro, and never have to connect with a usb cable to transfer anything ever again..
Click to expand...
Click to collapse
Agreed that apps like this are very convenient. Sometimes still prefer hardwiring for transferring 20-30 GB worth of stuff, even though MTP is a total drag.
danieljw said:
Yes. The phone defaults to charge-only mode via USB, which prohibits file transfer; this is why the device folder was empty in Windows. Switch to MTP mode via the notification shade and it will appear as it normally does.
In addition, in Developer options, you can configure the default USB mode, so as to prevent this from happening in the future.
Click to expand...
Click to collapse
This fixed my Issue. It was set to MTP but I switched it to Charge only then back to MTP and it works now.
Thank you.
with a fast wifi connection, its not really much slower to transfer big stuff as well; although, how often are you transferring 20-30 gigs of stuff???
I think I have used the cable to transfer maybe 3 or 4 times since I got this phone..wireless charging, no cables to transfer files, its time to embrace 2015!
TWRP Resize partition function
Addressing just the problem posed in the title of this thread, if you have TWRP installed, or if you choose to install it after you discover this problem, then you have an option that will preserve your data: use the new "resize partition" function within recovery.
Boot to TWRP (version 2.8.7.1 or higher)
Choose "Wipe" button (do not slide yet!!) then "Advanced Wipe" button.
Select the Data partition, then "Repair or Change File System" button.
Choose the Resize button.
Now you can slide to confirm, and it will expand the partition to it's full potential, without disturbing the data.
danieljw said:
Yes. The phone defaults to charge-only mode via USB, which prohibits file transfer; this is why the device folder was empty in Windows. Switch to MTP mode via the notification shade and it will appear as it normally does.
In addition, in Developer options, you can configure the default USB mode, so as to prevent this from happening in the future.
Click to expand...
Click to collapse
Sorry for OT:
Definitely doesn't work on a rooted Nexus 5. It always jumps back to charge only. Does this work 100% on Nexus 6 devices?
File transfer also doesn't work properly for me (and at least one other person in the NExus 5 Troubleshooting subforums), if you want to move a folder onto the SD card which has a system file and / or subfolders in it, it will most likely fail. There are also a lot of folders not showing in Windows Explorer, so if i.e. I want to move Titanium Backup files to the SD card I just can't place a folder and name it "Titanium Backup" because it won't get recognized. I have to create a dummy folder, place the backup files in there and then move them manually with ES File Explorer to the now visibile real TB folder.
That bothered me so much I did a rollback to Lollipop, hopefully those things get fixed by Google or with an Xposed module (if this is working somewhen).
My apologies for posting a question on what is most likely the wrong forum - but after 15-minutes of searching, I could not find the right forum for a new Galaxy Tab Active 2 question.
This is a question more related to software and may be more generic ?
My wife is the owner of a new Galaxy Tab Active 2 , and she is struggling to have her many Android applications installed not on the 16-GByte internal memory, but instead on a 128 GB microSD card she has in the Tablet. She has found various guides, but they either are not applicable to Active2 (as their menu options don't exist on Active 2) or they simply only work for some apps but not the necessary/important to her applications that she wants to transfer to the microSD card. In particular she would like the application "Line" ( https://play.google.com/store/apps/details?id=jp.naver.line.android&hl=en ) and also "WhatsAPP' (https://play.google.com/store/apps/details?id=com.whatsapp&hl=en) configured such that all their data goes on the microSD card. Unfortunately (especially for Line) she has not been able to do such.
Can anyone point me to the correct forum area ?
Again - my apologies for likely posting in the wrong area.
I own tab active 2 sm-390 too. 16gb is really not enough. We can only wait some professional to root the machine. Once root, we can try 'adaptive storage' or other app like 'App2SD' to save internal storage.
Just want to update you that I solve the storage problem.
1) You need to download the firmwire , extract the 'boot.img' file. Then, copy the file to your tablet.
2) Then, you have to install Magisk Manager and run the manager to patch the 'Boot.img'. In setting, remember to set the output file to odin format.
3) Copy the patched file to computer. In computer, run odin to install the patched file to tablet.
4) The tablet will then be reset. Now, the tablet is already rooted.
5) Then, run Apps2SD, you can move all apps to SD.
I am now have around 50 apps installed.
Please a step by step
Awesome!
You are such a genius to give us this good news
Can you please provide us a step by step guide and also the links to the files so that we can follow.
Thank you so much
How are you getting root.
I have the galaxy tab active 2 / T395 and have tried all the stand alone apks out there that claim they can root any android device; 'KingRoot, KingoRoot, OneClickRoot, z4mod.z4root, Rootmaster and Framaroot'. But do absolutely nothing for the T395 active 2.
However I can confirm that 'mark.mccv' method of rooting DOES WORK for the T395.
I guess the days of using CF-Auto Root & TWRP are over for the newer Nougat 7.1.1
mark.mccv said:
Just want to update you that I solve the storage problem.
1) You need to download the firmwire , extract the 'boot.img' file. Then, copy the file to your tablet.
2) Then, you have to install Magisk Manager and run the manager to patch the 'Boot.img'. In setting, remember to set the output file to odin format.
3) Copy the patched file to computer. In computer, run odin to install the patched file to tablet.
4) The tablet will then be reset. Now, the tablet is already rooted.
5) Then, run Apps2SD, you can move all apps to SD.
I am now have around 50 apps installed.
Click to expand...
Click to collapse
You forgot to mention, when installing the 'patched_boot.img' you need to turn 'OFF' both the FRP & OEM locks. Otherwise, when trying to flash the 'patched_boot.img' through Odin on the PC.
The devices download screen shows 'custom binary boot file' blocked by the FRP & OEM locks......
For anyone stuck on this ROOT process , you turn off the FRP lock by just deleting your Google accounts from your devices settings page.
Remove, turn OFF the OEM lock , by going to 'settings' > 'developers tools' > 'oem unlock'
On flashing the patched_boot.img , you will see a verification screen page after reboot, which forces you to reset, reformat your device. So back up your files beforehand.
Once reset, your device is rooted, ready to install busybox , adaway etc.
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info.
Crap: posetd this is two threads, realized i was typeing in the wrong one, cut and pasted and still hit send. oops
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Also, If you are having any trouble, then you can take a look at this thread (more detailed): https://forum.xda-developers.com/galaxy-tab/help/how-to-root-samsung-galaxy-tab-active-2-t3775664
Last thing, you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)
Did App data remain after rooting
mark.mccv said:
Just want to update you that I solve the storage problem.
1) You need to download the firmwire , extract the 'boot.img' file. Then, copy the file to your tablet.
2) Then, you have to install Magisk Manager and run the manager to patch the 'Boot.img'. In setting, remember to set the output file to odin format.
3) Copy the patched file to computer. In computer, run odin to install the patched file to tablet.
4) The tablet will then be reset. Now, the tablet is already rooted.
5) Then, run Apps2SD, you can move all apps to SD.
I am now have around 50 apps installed.
Click to expand...
Click to collapse
Hi mark.mccv
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.
I just came across a little gem, my uncle Gave me his T397U that he used to use for work, but has since upgraded!!!! I was so stoked until I powered up to realize that’s its full on knox mdm and is running what I’m assuming is the OS from his job, accessing reg samsung os at all is only possible through safe mode at the present moment ...I apologize if I’m in the wrong area, I’m vey New and honestly not even navigating around the boards to efficiently just yet ! Hopefully someone will want to throw me a bone! Thank you all for the amazing plethora of information!!!!
Hello guys,
I hope someone can help me with this problem...
So the thing is - yesterday I finally got OneUI 3 and Android 11 update (yay?). But ofcourse as soon as the phone rebooted and optimised all the apps and came back to main screen it rebooted after a minute or so...everytime. As soon as I enter my pin and unlock the phone it reboots after a short period.
The same problem happened when I de-bloated the phone a while ago via ADB - but I then enabled back all the apps except facebook and some "safe to debloat apps" which were not even system apps and it has since worked for almost a year. But here we go again....
I even "re enabled/installed" all the apps I could list in ADB ( so basically all the apps on the phone) and then went to wipe cache - but still no go.
I am also wondering if there is a posibility to somehow mount storage just to copy some files to my computer (which are important, and my latest backup is around a month old) and then I'll gladly do a a factory reset - no problem.
Any help would be appreciated, thanks!
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
TacoDeMuerte said:
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
Click to expand...
Click to collapse
Hello, thanks for the reply and helping out.
But all the commands and stuff is kinda useless because the phone reboots sooner than in 30 seconds after getting to the main screen. When I boot to recovery the storage doesn't get mounted.......
And I would've had TWRP but the phone is still under warranty so that's a shame, because on my backup phone I have it (and so did on all the previous ones) and it would be great. But IIRC if I install TWRP now, the phone needs to be wiped.
FFS samsung, what is this....because I now read a couple threads and posts on social media people having exactly same problem, and some didn't do anything with ADB prior to update. shame...