Database Info

[GT-P6200][CWMRecovery][ROOT]ClockworkMod Recovery and Root

****** USE AT YOUR OWN RISK *******
This is NOT SUPPORTED SOFTWARE. This is purely for my amusement and entertainment. I'm making it available to download for those who might like to examine my work, but if you install it, you are on your own. I can't even test this myself. (I don't have a GT-P6200.)
Seriously - this has not been tested enough for me to be happy with it, and I'm unable to test it myself. Please read the thread for the GT-P6210 for instructions, known issues, warnings, etc.
If you do decide to install this anyway, please let me know how it works out for you. If no one is using it, I WILL NOT MAINTAIN IT AND WILL DROP IT.
If people do start using it, and the reports are that everything is working okay, then it'll get merged into what I'm already doing with the other two 7 plus models (meaning it'll get updated as needed when they do.)
Again, PLEASE READ the thread for the 6210 for everything you need to know: http://forum.xda-developers.com/showthread.php?t=1379532
..and here's a link for a CWM recovery.
Link: http://www.mediafire.com/download.php?do5jkna3dpas1tq
Take care
Gary

Hi! I'm a placeholder.

garyd9 said:
Hi! I'm a placeholder.
Click to expand...
Click to collapse
Hi, Placeholder. I'm a placeholder, too. Good meeting you here.

Pm'ed you. went straight in CWM, looks nice. able to make a full backup and md5. fails to restore in the middle of restoring /data
also getting UDIDs are inconsistent , fixing permission is supposed to take care of this.
and Im pretty much factory reset after reboot.
EDIT: appears as if Location cache map app by remy in market I had set to block wifi and cell caches. restoring a backup in CWM got permissions error, trestoring /data fails and Im left with pretty much a factory reset. went back to market and reinstalled suspicious app, installed and still says caches blocked removed app, rebooted, made back up and successful restore! woo hoo! Thank You Gary!
Note: should we make a note for 7+ CWM users beware blocked location caches, or re-write recovery to take care of this, and/or email the app dev?
anyways, pretty excited. Thanks so much Gary.

Anyone else want to help test the CWM Recovery for this tablet? (GT-P6200 only)
The current tester has had mixed results, but it _may_ have been the result of a third party app causing problems. I'd like to get someone else to test in addition to ensure there aren't any other issues.
In order to test, I need someone who has "adb" installed on their PC, is comfortable with linux commands, already knows how to use adb for commands such as "adb shell, adb push, and adb pull", doesn't mind using ODIN to restore their tablet to a factory state if it soft-bricks, and already knows how to use ODIN and CWM Recovery.
As a side-note; the third party app that MIGHT have been causing the problem is "Location Cache" by "remydemy." I don't use this app myself, but apparently it has some function to block the google/android location caches and it appears to do that by messing with the permissions on the files... which is somehow causing an error when the recovery tries to clean the /data directory in order to restore.
Thanks
Gary

link posted for testing.

thanks again gary loving it.

when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
So i just used root ecplorer to delete entire contents of folder. : )
is this not linked properly or CWM issue, or is this normal function?
thanks so much for your help.

chrisrotolo said:
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
Click to expand...
Click to collapse
I'll look into it. Please try this alternative to test that function: Boot your phone normally, and then reboot into recovery. Using the recovery menu, mount the /data partition. Then use 'adb shell' to shell into the device and manually look in the /data/dalvik-cache directory. Then "cd /" and from within recovery choose the advanced->wipe dalvik-cache. Then look in /data/dalvik-cache directory again to see if it did what it should have done.
It's possible, based on the ordering of your above description, that the dalvik cache rebuilt after you wiped it (during the reboot) but before you removed your bloatware.
Take care
Gary

thank you. Gary tried not to get Banned OK? we need you buddy. lol

chrisrotolo said:
thank you. Gary tried not to get Banned OK? we need you buddy. lol
Click to expand...
Click to collapse
Where you able to run those tests yet?
thanks
Gary

not as of yet, sometime today though.
---------- Post added at 03:13 PM ---------- Previous post was at 02:23 PM ----------
so yeah, you must be right. dalvik-cache was full with /data mounted. cd / then wiped dalvik from CWM, which finishes in a split second; a list (ls) shows no dalvik-cache folder after wiping, completly gone.
Answers my question.
One other issue I ran into, that you're may be aware of is somehow I disabled the power button in CWM, it said something about back button disabled. I think I had to hold power for 10 sec. to reset device.
Thanks.

chrisrotolo said:
...somehow I disabled the power button in CWM, it said something about back button disabled.
Click to expand...
Click to collapse
That one I'm not sure of and really can't help much with. No 'power' button means you can't select anything which would really be annoying.

it works great! instant root and cwm within 2 minutes! i highly recommend gary's method than the other one. i also don't seem to lose root access by clearing ram memory. SWEET.

Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?

lvsw said:
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
Click to expand...
Click to collapse
formatting the internal SDCard isn't going to happen with this version of CWM (that's designed for GB.) Honeycomb devices don't have a seperate /sdcard partition to format. Formatting the "internal sdcard" can be done from within the settings menu via a factory reset.
The other two items aren't broken - they simply don't exist in CWM recovery, and probably never will... Is having the pre-loaded samsgung sample video and music files repushed to your device over and over actually more important to you than the ability to do a nandroid backup? Do you even know what the CSC is that isn't being updated?
Have you bothered to seach around BEFORE installing this? Have you bothered to search around AFTER installing it to find out how to restore to factory?
I'm NOT going to answer your specific question on the basis that it's been answered already and I honestly feel that a user of XDA needs to have the ability to SEARCH before posting.
Take care
Gary

worked like a charm...backup and restore works perfectly...
thanks gary !!!

Hey Gary-
Question -
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
I could just flash a new recovery from ROM Manager, but I don't want to screw anything up.
Thanks!
Sent from my Galaxy Tab Plus using Tapatalk

jeffcavicchi said:
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
Click to expand...
Click to collapse
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary

garyd9 said:
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
Click to expand...
Click to collapse
Got it - sort of what I figured.
Am I wrong that Recovery still sees the external SD card as an internal SD card? I thought the last time I flashed a zip (boot animation) Recovery showed it as being on the internal card, even though it was actually on the external card. I could be wrong, though - and I don't have the device in front of me to check.
Not a big deal either way - thanks for the response, and your hard work!
*Edit*
Just realized I posted this in the wrong thread like an idiot - I have a P6210. guess that's what happens when you start posting things bc (before coffee).

My phone wont boot into Cmw recovery, Please help.

My phone is rooted (With Super One Click) and when tap the "boot into recovery" option in Rom Manager it just send me to the stock recovery (with Blue text and what not). I have flashed Rom Manager with my Sidekick 4g before I tried to boot into recover. Please, someone help me. The answer is probably right in my face, but my noobish eyes just cant see it. :crying:
Please don't bash me this is my first post. I made sure there wasnt any post like this before i started a new tread.

Don't use ROM Manager with Sidekick 4G as CWM doesn't work the same way. When you reboot you always go into Samsung recovery from where you gotta reinstall packages to 'fake flash' the CWM recovery. If it says permission denied, the recovery file wasn't pushed to /system properly. You gotta reinstall every single time .. till of course you install a custom ROM. I think most come with voodoo CWM which replaces stock recovery, allowing you to go into CWM directly when you go to Recovery.
Firstly you need root, which I'm assuming you already have. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using other similar apps that give you R/W (read and write) access. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery.
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
Edit: Looks like the links on Krylon's page aren't working .. if someone can give an alternative it would be great!

I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app

Those guided really helped me out I spent ages reading up different things so when I finally went and did it, I didn't face any problems!
Important notes:
1. Root, obviously I personally didn't use the latest edition of SuperOneClick (at the time) on the website, but the file the dev posted on his XDA Thread.
2. Don't use ROM Manager or any other 'one click' kind of recovery for this phone. You need to download a custom recovery file and update file (links above, thanks Krylon) and go into CWM Recovery through the official Samsung Recovery through reinstalling the custom update file. This is the only way to access Orange CWM. Most custom ROMs come with the Red Voodoo CWM which is permanent in the sense that when you go into recovery, you should go into CWM (Red), instead of having to go through Samsung.
3. Orange CWM (and some say Red CWM as well) has some mounting issues. Always remember to check your mounts such that System, Data (well just to be safe, all of the items in the list) always say UNMOUNT. Basically when its mounted, means CWM has access to the partition. It says UNMOUNT because it is MOUNTED. I know thats a bit confusing, but think of it like this - there is a light switch that says ON so when you press it, turns the lights on but then the writing changes to OFF because you need to push the switch to turn it off. Erm .. hope that helps?! Lol.
4. Basically if your partitions are showing up as MOUNT, means you need to MOUNT them. Otherwise whatever changes you did won't apply! Instead of getting confused like I did, just make sure the screen says UNMOUNT SYSTEM and so forth for the rest of the items on the list.
5. Before installing a custom ROM, I always wiped x 3, before and after. Means after checking mounts, wipe data / dalvik, etc. 3 times. So for me, after checking mounts I would go to wipe date - yes - done 1; wipe data - yes - done 2; wipe data - yes - done 3. Followed by wipe dalvik and whatever else you want to wipe. Then I'd check mounts again (they usually get unmounted after a wipe .. well for me they always have anyway) before installing the ROM. Oh, sometimes I installed the ROM twice. Then I'd check mounts, wipe x 3, check mounts again before finally rebooting and letting it stand still for around 20 minutes or so. I don't really know if there is a logic or if doing it so many times makes a difference but I know some other people have done this and (other than wasting time) it doesn't really do any harm (someone correct me if I'm wrong) so why the hell not? I think the basic reasoning behind double / triple wiping and installing is to make sure that the changes are properly written as sometimes the system still retains old data.
6. Some people have SD card partitioning issues apparent. I can't remember why everyone went around partitioning in the first place (it must have been for some important reason, completely slipped my mind right now .. I personally did it to link my apps / data to SD card and save internal memory / space) but I personally used Gparted to partition my card on a computer (rather than CWM on the phone as I've heard people have issues with this) and never had a problem.
But I think thats it. I know there is a lot of information but its really worth having a look at the guide and other posts on that thread as that and the ROM thread (I personally use GOV 3.2) really had me prepare for any possible issue beforehand so I started off in a position where I could avoid them.

WTF_IsA_Android said:
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
can someone update the sidekick 4g stuff everything is either dead or does not lead anywhere to download any of the required files, thanks.

TWRP backups

So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:

mark7807 said:
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
Click to expand...
Click to collapse
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.

exad said:
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
Click to expand...
Click to collapse
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.

mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.

mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
RC1 and backup system image, vendor image, data and boot.

robocuff said:
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
Click to expand...
Click to collapse
TheBurgh said:
RC1 and backup system image, vendor image, data and boot.
Click to expand...
Click to collapse
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!

mark7807 said:
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
Click to expand...
Click to collapse
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?

mark7807 said:
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
Click to expand...
Click to collapse
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.

TheBurgh said:
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
Click to expand...
Click to collapse
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??

mark7807 said:
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
Click to expand...
Click to collapse
Not that I am aware of. Mine is rooted and backups have been smooth sailing.

I recently attempted creating a nandroid backup via TWRP on my rooted Pixel and I'm consistently getting an error: 'cannot create [path]\backup file" message from TWRP. Is there a permission issue that I've overlooked here or does anyone have any thoughts as to why my rooted Pixel would be denying TWRP authority to create the backup?
Thanks

What version of twrp ?
I only use rc1, never seen this.

Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.

pstgh said:
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
Click to expand...
Click to collapse
When you boot into TWRP did it ask for your unlock PIN? If it doesn't/didn't, either keep rebooting into recovery or turn the phone off and go back into recovery until TWRP does ask for your encryption PIN. Sometimes TWRP doesn't ask, and without the PIN being entered, it can't write to the internal storage.
If you click "Install" in TWRP and see a bunch of gobbledygook it's because the internal storage is still encrypted so TWRP can't do anything with it.
You could probably use USB OTG through the USB-C connector, though, to do a backup to it, if you need to.

Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks

pstgh said:
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
Click to expand...
Click to collapse
I can't confirm since I've yet to do a successful backup but... Flashify Pro version looks like an option???
also
Anyone know when TWRP 3.1.0-0 will be out for Pixel? Looks like it addresses boot slots which off first glance seems like quite a fundamental feature no?

Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.

pstgh said:
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
Click to expand...
Click to collapse
Root Explorer does have support for Google Drive. In Root Explorer touch the plus sign in the lower right corner and in the menu that opens choose Google Drive tab.

Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.

pstgh said:
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
Click to expand...
Click to collapse
It sounds like you've got the right idea. Cut will move the files, copy will do just that. You choose one of the two and browse to the Google Drive tab, find the folder you want to use and then use the little clipboard thing to transfer the files to that folder. If that's what you're doing, the only thing I can think of right off the top of my head would be that you don't have enough space left on Google Drive for the size of the files you're trying to transfer. Try a picture or something and see if it takes that. If so, I'd suspect lack of Drive space is the reason it fails.

Urgent help require for recovering data

Hi there,
Its been a long time using the Note 3 since 2013. It had many issue but still carried on. But few days back when weak up in the morning saw the phone was off, though it was in charge full night. When turned it on it stuck in the Samsung glowing logo and nothing after that, it keep showing the same logo until it power is gone. Don’t know what happened that night, it was installing an update by itself or not.
Then google it and no steps helps, used odin and reflash with latest firmware from sammobile but that too didn’t help. I’ve lots of data in internal storage including sms and contacts and pictures. I’ve no issue to throwing off the phone but I cant lost all data in it, it will be a huge loss as just became a father and lots of pics on my new born baby, so you can understand the value.
Can anyone suggest how can I recover the data? Check the attachment for its current state. Thanks in advance.

Is your phone rooted?
Sent from my awesome Galaxy S8+

IamVaibhav said:
Is your phone rooted?
Sent from my awesome Galaxy S8+
Click to expand...
Click to collapse
No nothing at all, its complete stock, only official updates installed regularly.

soumen.sam said:
No nothing at all, its complete stock, only official updates installed regularly.
Click to expand...
Click to collapse
When you tried the official update from sammobile, did you add a PIT file in addition to the stock ROM?

chosenroyal said:
When you tried the official update from sammobile, did you add a PIT file in addition to the stock ROM?
Click to expand...
Click to collapse
I didnt have time to to learn all this. Just followed an instruction how to solve this and did, but no where I heard about PIT file, what is its purpose? all said to flash with just the .md5 file. Please advice. Thanks

soumen.sam said:
I didnt have time to to learn all this. Just followed an instruction how to solve this and did, but no where I heard about PIT file, what is its purpose? all said to flash with just the .md5 file. Please advice. Thanks
Click to expand...
Click to collapse
This is a bit long. I copied the explanation of PIT online.
PIT stands for Partition Information Table (PIT) and as the name suggests these are files which contain partition tables for your Samsung Galaxy Android phones. The PIT file contains all the relevant information for each required partition such as Partition Name, Block Size, Block Count, and other technical information. Every device has different PIT file associated with its stock firmware. Hence a correct PIT file is needed in order to properly flash the stock firmware on your device. Also, if there are two models of a device, say 32 GB and 64 GB, then both will have a different PIT file and you cannot use the PIT of the former with the later or vice-versa.
What does the PIT file do?
ROM (Read Only Memory) is similar to a hard disk on a PC where the information is kept permanently unless changed by the user. PIT file will re-partition the ROM of your device...
---------- Post added at 12:52 PM ---------- Previous post was at 12:49 PM ----------
So what's your phone's model number? Is it SM-N900? And does it have 32GB internal storage?

chosenroyal said:
This is a bit long. I copied the explanation of PIT online.
PIT stands for Partition Information Table (PIT) and as the name suggests these are files which contain partition tables for your Samsung Galaxy Android phones. The PIT file contains all the relevant information for each required partition such as Partition Name, Block Size, Block Count, and other technical information. Every device has different PIT file associated with its stock firmware. Hence a correct PIT file is needed in order to properly flash the stock firmware on your device. Also, if there are two models of a device, say 32 GB and 64 GB, then both will have a different PIT file and you cannot use the PIT of the former with the later or vice-versa.
What does the PIT file do?
ROM (Read Only Memory) is similar to a hard disk on a PC where the information is kept permanently unless changed by the user. PIT file will re-partition the ROM of your device...
---------- Post added at 12:52 PM ---------- Previous post was at 12:49 PM ----------
So what's your phone's model number? Is it SM-N900? And does it have 32GB internal storage?
Click to expand...
Click to collapse
Ok thanks, yes its SM-N900 32GB internal storage. All I want to fix it without formatting the internal storage. I even dont know after flashing it will clear then internal memory and reset or not. Even if I need the PIT file, then where can I get the stock PIT file? Thanks

soumen.sam said:
Hi there,
Its been a long time using the Note 3 since 2013. It had many issue but still carried on. But few days back when weak up in the morning saw the phone was off, though it was in charge full night. When turned it on it stuck in the Samsung glowing logo and nothing after that, it keep showing the same logo until it power is gone. Don’t know what happened that night, it was installing an update by itself or not.
Then google it and no steps helps, used odin and reflash with latest firmware from sammobile but that too didn’t help. I’ve lots of data in internal storage including sms and contacts and pictures. I’ve no issue to throwing off the phone but I cant lost all data in it, it will be a huge loss as just became a father and lots of pics on my new born baby, so you can understand the value.
Can anyone suggest how can I recover the data? Check the attachment for its current state. Thanks in advance.
Click to expand...
Click to collapse
Are you sure that you downloaded the right firmware for your country/career?

DontBrickYourPhone said:
Are you sure that you downloaded the right firmware for your country/career?
Click to expand...
Click to collapse
Checked all, country latest version exact model and all. Juts now trying reflash with the pit file.

If you want to cpy Data from your internal storage try tihis way
1 install official TWRP recovery
2 Reboot into recovery
3 connect your mobile to Pc annd then you can copy data from your internal storage
Hope it help you ?

you can try this method.
1.Root your phone and install twrp recovery.
2.mound and SDCard and reboot into recovery and from file manager in recovery copy all data from internal storage to SDCard by doing this your data will be safe .after that try to flash anr other rom like Resurrection Remix Or lineage to repair your phone.

Hi, if you flashed (completely) an update not compatible you lost your data, your contacts it`s recommendable to synchronise with Google if worst happen, if your data didn`t go away you can try to recover like others users recommended, first root device with this file https://download.chainfire.eu/353/CF-Root/CF-Auto-Root/CF-Auto-Root-ha3g-ha3gxx-smn900.zip, install official TWRP from Google Play and download from it correct version, go to recovery from same app and transfer to pc all that you can.
Sometime ago I tried to flash a rom with odin and result was the same, and issue was just for flashing without connection to internet, maybe help

Amh00200 said:
If you want to cpy Data from your internal storage try tihis way
1 install official TWRP recovery
2 Reboot into recovery
3 connect your mobile to Pc annd then you can copy data from your internal storage
Hope it help you
Click to expand...
Click to collapse
So after few days I got some time to work on it. I've already took the internal backup by TWRP like whats all etc. I did CWM Recovery and took the full backup and the format and reset. Now the phone turned on and restored the backup by CWM but again its in Boot loop. Now what to do? and yes I think its rooted now.
I only need contacts sms and action memo, thats all

raosahab said:
you can try this method.
1.Root your phone and install twrp recovery.
2.mound and SDCard and reboot into recovery and from file manager in recovery copy all data from internal storage to SDCard by doing this your data will be safe .after that try to flash anr other rom like Resurrection Remix Or lineage to repair your phone.
Click to expand...
Click to collapse
Yes I already took the backup and tried many repair fixing software but nothing helpped

SubwayChamp said:
Hi, if you flashed (completely) an update not compatible you lost your data, your contacts it`s recommendable to synchronise with Google if worst happen, if your data didn`t go away you can try to recover like others users recommended, first root device with this file https://download.chainfire.eu/353/CF-Root/CF-Auto-Root/CF-Auto-Root-ha3g-ha3gxx-smn900.zip, install official TWRP from Google Play and download from it correct version, go to recovery from same app and transfer to pc all that you can.
Sometime ago I tried to flash a rom with odin and result was the same, and issue was just for flashing without connection to internet, maybe help
Click to expand...
Click to collapse
I flashed with proper firmware and when it didnt help I tried CWM recovery and took the backup, while it was taking backup I saw it took all apps those I installed. So I'm sure it didnt format the data.

soumen.sam said:
I flashed with proper firmware and when it didnt help I tried CWM recovery and took the backup, while it was taking backup I saw it took all apps those I installed. So I'm sure it didnt format the data.
Click to expand...
Click to collapse
Well, we need to make things clear to try to solve this;
Assuming that you;
- Flashed correct firmware and for some reason process interrupt or apparently reached the end but device don´t boot (bad flashing)
- You took a backup from CWM nor TWRP (then you have a backup of system, data, boot, maybe recovery and probably cache. Then you can try the next:
- Put your backup ever in sdcard
- Flash some custom rom based on stock (zip format) with CWM (maybe necessary to do wipes to boot but probably you lost your data from device flashing before, but you have it in your backup)
- Now select an advanced restore, just restore data (if same native app of mms and notes are installed they took data again), reboot now and look, probably will be necessary restore also cache but let it just if needed)
- If for some reason don´t boot probably your partitions are corrupted but you can try first this. I hope help you and tell us how you go

SubwayChamp said:
Well, we need to make things clear to try to solve this;
Assuming that you;
- Flashed correct firmware and for some reason process interrupt or apparently reached the end but device don´t boot (bad flashing)
- You took a backup from CWM nor TWRP (then you have a backup of system, data, boot, maybe recovery and probably cache. Then you can try the next:
- Put your backup ever in sdcard
- Flash some custom rom based on stock (zip format) with CWM (maybe necessary to do wipes to boot but probably you lost your data from device flashing before, but you have it in your backup)
- Now select an advanced restore, just restore data (if same native app of mms and notes are installed they took data again), reboot now and look, probably will be necessary restore also cache but let it just if needed)
- If for some reason don´t boot probably your partitions are corrupted but you can try first this. I hope help you and tell us how you go
Click to expand...
Click to collapse
Thanks for your feedback. Yes I backup from CWM full system data and all and TWRP I took internal storage backup in PC.
I flashed with latest firmware from sammobile with Odin
I restore the backup in all way, full restore, only data and other one by one, but in all steps its unable to turn on again. I saw the internal memory data is intact but contact call log and sms r gone. I just waht these 3 things, snote is still there.
How do I know my phone is rooted? if I rood can I overwrite these data from the backup files? I installed two file manager but cant access the root. Please let me know. Thanks

soumen.sam said:
Thanks for your feedback. Yes I backup from CWM full system data and all and TWRP I took internal storage backup in PC.
I flashed with latest firmware from sammobile with Odin
I restore the backup in all way, full restore, only data and other one by one, but in all steps its unable to turn on again. I saw the internal memory data is intact but contact call log and sms r gone. I just waht these 3 things, snote is still there.
How do I know my phone is rooted? if I rood can I overwrite these data from the backup files? I installed two file manager but cant access the root. Please let me know. Thanks
Click to expand...
Click to collapse
If device don`t power on you need first of all flash correct firmware to repair partitions, you need to go step by step.
- Flash by odin, good level battery charged, access to internet, depending capacity of your pc don´t use many resources meanwhile flashing, if sucess reboot device completely now power off, put it in download mode
- Now, step 2 you need to root with this file, download it https://download.chainfire.eu/353/CF-Root/CF-Auto-Root/CF-Auto-Root-ha3g-ha3gxx-smn900.zip extract from zip and you have this file in .tar.md5, open odin, go to AP box, search file and flash it (download mode), this file will root device and will install TWRP (is needed to inject some scripts from supersu)
- how your backup is in CWM you need to go now to TWRP and flash CWM.img file via recovery.
- reboot in CWM and select advanced option to restore, just restore DATA, not other partitions, this overwrite your data app for your data backup, and without doing wipes try to boot. maybe system be unstable but you need now just recover some data, when you do that recommend a flash a custom rom or at least keeping root to take a backup with titanium periodically

Hi All, So with the rooted device I've managed to restore all data except call log, which I can ignore. But now the issue is, the system showing the software is not official and not supporting software upgrade and showing the system is custom. Now what to do, where can I get the exact firmware? thanks

sammobile or updato dot com or just search .

cannot use adb to solve continuous reboot - device offline

I have oneplus one came from chineese retailer already rooted and with adware. always meant to reflash with straight CM or with a version of AOSP, but ended up use adb (which I have for development, though I am NOT experienced in using adb, flashing rom or what ever only programming) to disable a number of apps and it seemed to be stable.
More recently I had a phone crash following the crash of an app that I think is the CM app launcher, something begining with t, trebuchet?, i dont recall. Since then the phone keeps rebooting and I cannot seems to use adb, the device is either not present or offline.
I can boot to cyanogen recovery which offers:
- reboot system now
- apply update
- apply from adb
- choose from internal storage
- wipe data/factory reset
- wipe cache partition
- wipe media
If I select apply from adb then the device is nolonger offline but in sideline mode, but I don't think this is what I want.
I never liked CM and I had always thought that I might try to flash with a version of AOSP if possible and I wondered if now was the time. I thought TWRP might be useful for this and the first step to installing this was:
C:\...\Downloads>adb reboot bootloader
but I get
error: closed
I briefly see the debugging notification before the phone reboots but in adb it is always not present or offline.
How do I get to the point of either solving my repeating reboot at least or preferably installing a version of AOSP that would be compatible with OnePlus One, preferably without destrying data. I think the data is in a different partition or something but I have forgotten the little I learnt about this a few years ago.
I would be so grateful of some help and learning, right now to all intents and purposes I have a nice looking brick.

hardya said:
I have oneplus one came from chineese retailer already rooted and with adware. always meant to reflash with straight CM or with a version of AOSP, but ended up use adb (which I have for development, though I am NOT experienced in using adb, flashing rom or what ever only programming) to disable a number of apps and it seemed to be stable.
More recently I had a phone crash following the crash of an app that I think is the CM app launcher, something begining with t, trebuchet?, i dont recall. Since then the phone keeps rebooting and I cannot seems to use adb, the device is either not present or offline.
I can boot to cyanogen recovery which offers:
- reboot system now
- apply update
- apply from adb
- choose from internal storage
- wipe data/factory reset
- wipe cache partition
- wipe media
If I select apply from adb then the device is nolonger offline but in sideline mode, but I don't think this is what I want.
I never liked CM and I had always thought that I might try to flash with a version of AOSP if possible and I wondered if now was the time. I thought TWRP might be useful for this and the first step to installing this was:
C:\...\Downloads>adb reboot bootloader
but I get
error: closed
I briefly see the debugging notification before the phone reboots but in adb it is always not present or offline.
How do I get to the point of either solving my repeating reboot at least or preferably installing a version of AOSP that would be compatible with OnePlus One, preferably without destrying data. I think the data is in a different partition or something but I have forgotten the little I learnt about this a few years ago.
I would be so grateful of some help and learning, right now to all intents and purposes I have a nice looking brick.
Click to expand...
Click to collapse
Did you try factory reset?

Thank you so much for your the suggestion, I appreciate it.
Not yet I haven't. I'm not familiar with the CM Recovery Software and the option is entitled "wipe data/factory reset". Do you happen to know if this means bother or either and if selecting this explains more and gives options before proceeding. Key is I want to avoid wiping data if possible because while most is sync'd offline some is recent and not or not for particular reasons.
If there's a choice then will "factory reset" leave personal data alone? Do you know, will the factory reset likely be to version/adaptation of CM put on by rooting retailer PLUS anoying/mal/ad/ware apps put on by rooting retailer.
If this is my only option then I will go ahead and do it and take the hit.
If following this, it is possible to install a stable Android 7.n.n AOSP only that will support the hardware and leave data intact (ONLY LEAVE DATA IF POSSIBLE) I would be very grateful for a clear and complete script to achieve this. I was a professional developer for 20 years, now semi-retired, so I know what I know and what I don't know in terms of foundational knowledge, taking care etc etc, but I am very inexperienced in flashing phones and using ADB except the fact the eclipse/android studio uses it.
I used a windows script to install fastboot if that is any help (though the script did show some errors it still said "All Done!" at the end. Tried to C&P the errors but failed). I can also try to install TWRP (or what ever) if that's any help.
Many thanks would really appreciate your help in my getting my OnePlus One working and stable again.
Andrew.

hardya said:
Thank you so much for your the suggestion, I appreciate it.
Not yet I haven't. I'm not familiar with the CM Recovery Software and the option is entitled "wipe data/factory reset". Do you happen to know if this means bother or either and if selecting this explains more and gives options before proceeding. Key is I want to avoid wiping data if possible because while most is sync'd offline some is recent and not or not for particular reasons.
If there's a choice then will "factory reset" leave personal data alone? Do you know, will the factory reset likely be to version/adaptation of CM put on by rooting retailer PLUS anoying/mal/ad/ware apps put on by rooting retailer.
If this is my only option then I will go ahead and do it and take the hit.
If following this, it is possible to install a stable Android 7.n.n AOSP only that will support the hardware and leave data intact (ONLY LEAVE DATA IF POSSIBLE) I would be very grateful for a clear and complete script to achieve this. I was a professional developer for 20 years, now semi-retired, so I know what I know and what I don't know in terms of foundational knowledge, taking care etc etc, but I am very inexperienced in flashing phones and using ADB except the fact the eclipse/android studio uses it.
I used a windows script to install fastboot if that is any help (though the script did show some errors it still said "All Done!" at the end. Tried to C&P the errors but failed). I can also try to install TWRP (or what ever) if that's any help.
Many thanks would really appreciate your help in my getting my OnePlus One working and stable again.
Andrew.
Click to expand...
Click to collapse
Okay,since you want to flash Aosp N,leave that factory reset thing.
https://forum.xda-developers.com/showthread.php?t=2788632
This thread should be enough atm.Everything has been explained,and it's just simple copy paste,so,even if you're unfamiliar with adb,you should be able to do just fine.
Just follow,install adb/fastboot drivers,unlock bootloader,and flash twrp.
Now,unlocking bootloader will format internal storage,which means everything....but,a simple adb command should be able to back everything up into your pc.
Ensure your adb/fastboot drivers are already installed,and using adb devices in cmd shows your connected device id,before below process!
adb backup -apk -shared -all -f C:\Users\NAME\backup.ab
Where "NAME" is the name of your Windows user name.
On the device, a new screen should appear. If you want to encrypt the backup, enter a password -- otherwise, tap Back up my data. The backup will begin, and you'll find the backup file in the folder declared in the backup command.
Depending on how much data your device holds, this process can take quite some time.
The restoration process is simple. Connect the device to be restored and (from the same location you issued the backup command) enter the command:
adb restore C:\Users\NAME\backup.ab
Where NAME is the name of the same Windows user from the backup process.
Again, depending on how much data is on the backup, the restore process can take some time.
Click to expand...
Click to collapse
When you're done doing all of this,just follow any rom's thread instructions to flash that rom.
Btw,you're on Cos13.1.x,yes?

So sorry for not replying to say thank you sooner, I have been busy with family issues.
Thank you so much for your response, I really appreciate it. I shall take a look at this soon and try to get regular android N on the phone soon. Thank you.

I'm just starting to read and work through this. Just to clarify, re my original post, is the fact that my phone is continually rebooting and that adb shows the device as offline a problem? Will I still be able to use adb to backup the phone contents? Do I need any special understanding to do that?

I finally came back to this and flashed a new rom carbon rom. I only noticed afterwards that there is very little support for this rom and I've had some issues.
If you think the issues are in some way generic and you have come accross them before you may have some ideas:
- there is no built in task manager and third party ones do not seem to cover the apps I am interested in. Any ideas why there is no built in task manager anymore like there used to be and how one might be able to turn it back on?
- the camera does not work and the open camera I installed instead has some image faults (or misunderstood feature). Big line down the middle of the image.
Any ideas.