Related
Well, I should have listened to myself. I was going to stick with the stock gtab because of the dangers of modding a new ROM. I even started a thread about keeping my tablet stock.
But stock is so messed up and so hard to work with I decided to go ahead and mod Roebeet's 1.01a version.
It installed the first time. Then I reset the data from the Security Menu. Seemed to be running, but the Tnt side didn't work. Worked from the new Launcher menu and I thought I was home free.
Then it went off and automatically came back on, then the VS birds, the GTab, then birds, then tab.....off button no longer turns off....tried redoing the ROm again....no change....tried again....no change.
Loaded CWM 08 satisfactorily. Tried cleaning the data as suggested in threads. No change. I put 2.20 on another sd card. edited it for SDCARD2. Now I can't get CWM to see the external card to load it.
It did load CWM from SDCARD2!
I'm sure there's something I don't know or have done wrong, but I'm stalemated for the time being. Can't shut the machine off, so just have it idling on AC power.
Can anyone tell me how to get CWM to load from the SDCARD2 so I can see if TnT 2.20 or something else well work?
I'd appreciate suggestions. I knew I should have stuck with stock -- but didn't listen to myself. My bad!
Rev
Follow this guide word for word
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
it will take you back to stock and you can start again.
Im pretty sure you just need to repartition the sdcard. Its under advanced in cwm.
butchconner said:
Well, I should have listened to myself. I was going to stick with the stock gtab because of the dangers of modding a new ROM. I even started a thread about keeping my tablet stock.
But stock is so messed up and so hard to work with I decided to go ahead and mod Roebeet's 1.01a version.
It installed the first time. Then I reset the data from the Security Menu. Seemed to be running, but the Tnt side didn't work. Worked from the new Launcher menu and I thought I was home free.
Then it went off and automatically came back on, then the VS birds, the GTab, then birds, then tab.....off button no longer turns off....tried redoing the ROm again....no change....tried again....no change.
Loaded CWM 08 satisfactorily. Tried cleaning the data as suggested in threads. No change. I put 2.20 on another sd card. edited it for SDCARD2. Now I can't get CWM to see the external card to load it.
It did load CWM from SDCARD2!
I'm sure there's something I don't know or have done wrong, but I'm stalemated for the time being. Can't shut the machine off, so just have it idling on AC power.
Can anyone tell me how to get CWM to load from the SDCARD2 so I can see if TnT 2.20 or something else well work?
I'd appreciate suggestions. I knew I should have stuck with stock -- but didn't listen to myself. My bad!
Rev
Click to expand...
Click to collapse
CWM .12 (the newest one) actually reads from the microSD. But (and this is a big BUT) it has issues with non-padded boot.img files, which is what TnT Lite, and TnT stock based 1.01a1, and stock itself, use. So it's a double edged sword. I still use .08 because of this issue.
I would also recommend the SD card re-partition. You have cwm already so you are halfway there. Worst case it's nvflash time - I have a post on that process, as well.
Fate Zero,
Thanks for the quick reply. I had that post laying on the desk before I even started. It wouldn't work because the G-Tablet would not read or access SCCARD2 as I mentioned in the first post.
Rev
GideonX,
It wasn't that simple, but your suggestion was part of the solution!!! Thanks!!!
Rev
P. S. -- See answer to Roebeet for more info.
Roebeet,
I am back up on TnT 2.20 and your suggestion was a part of what I did.
I really believe something messed up the SDCARD2 operation. After I loaded CWM that way, I couldn't get it to work anymore and so the re-installs keep just trying to load the faulty 1.01a setup.
But here's what I did.
I found the USB option on the Mounts and Storage menu in CWM. I plugged in the cable to mini-USB and my PC. I mounted/turned on the USB and the drive popped up in Explorer on the PC. I could see the old "Update.zip" file and "Recovery" folder on the SDCARD (the ones for 1.01a) and so I erased them. I then copied in the TnT 2.20 files and shut down the links and went back to the G-Tablet and CWM. Still wouldn't work.
So I went to the Advanced menu and re-partitioned the SDCARD -- 2048 and 256 as everyone suggested. Then I just went down the menu in CWM and formatted all the system/cache/sdcard/etc. folders. Then I went by to the USB-PC connection and loaded the ROM files into the newly created and formatted SDCARD folder. Went to the other menu item and told it to apply the zip file -- which it immediately did setting up TnT 2.20.
That rebooted and I went through most of the basic setup, got wireless working, web, etc.
Only problem is I need to get Root Explorer installed to do the Market Fix, and when I went to ES Explorer to go to downloads and install it, it didn't find it in the market. So I will have to figure out a way to install or use something that will let me install the Root Explorer apk I have in the "Downloads" directory on the SDCARD.
I will try to re-think this account and re-write it more accurately when I'm not so bleary-eyed and thick-headed. I have not seen a G-Tablet account of someone rebuilding using the kind of "side-loaded" method I scrabbled together.
Suggestions on how to get to the downloads directory to install apps?
Rev
From CWM,
butchconner said:
Roebeet,
I am back up on TnT 2.20 and your suggestion was a part of what I did.
I really believe something messed up the SDCARD2 operation. After I loaded CWM that way, I couldn't get it to work anymore and so the re-installs keep just trying to load the faulty 1.01a setup.
But here's what I did.
I found the USB option on the Mounts and Storage menu in CWM. I plugged in the cable to mini-USB and my PC. I mounted/turned on the USB and the drive popped up in Explorer on the PC. I could see the old "Update.zip" file and "Recovery" folder on the SDCARD (the ones for 1.01a) and so I erased them. I then copied in the TnT 2.20 files and shut down the links and went back to the G-Tablet and CWM. Still wouldn't work.
So I went to the Advanced menu and re-partitioned the SDCARD -- 2048 and 256 as everyone suggested. Then I just went down the menu in CWM and formatted all the system/cache/sdcard/etc. folders. Then I went by to the USB-PC connection and loaded the ROM files into the newly created and formatted SDCARD folder. Went to the other menu item and told it to apply the zip file -- which it immediately did setting up TnT 2.20.
That rebooted and I went through most of the basic setup, got wireless working, web, etc.
Only problem is I need to get Root Explorer installed to do the Market Fix, and when I went to ES Explorer to go to downloads and install it, it didn't find it in the market. So I will have to figure out a way to install or use something that will let me install the Root Explorer apk I have in the "Downloads" directory on the SDCARD.
I will try to re-think this account and re-write it more accurately when I'm not so bleary-eyed and thick-headed. I have not seen a G-Tablet account of someone rebuilding using the kind of "side-loaded" method I scrabbled together.
Suggestions on how to get to the downloads directory to install apps?
Rev
From CWM,
Click to expand...
Click to collapse
Bleary eyed as well (time for sleep) -- I personally use Titanium Backup for the (primary) Market fix. Has worked every time and I've done it a alot, as you might expect. I'm not sure why the file manager won't let you run an apk from the downloads section, but I believe you can download (and run) the TB apk right off their web site.
I'm guessing from the root explorer comment that you are trying the additional Market fix, for even more apps? Maybe you can get it working enough with the primary fix, to get root explorer? I see it in my own Marketplace, although it's not a free app.
Sounds like you are getting there. I replied back to your PM but I guess I saw it a little late
I was hoping you wouldn't run into a bunch of issues when I wrote you back. You will get it. I think you are almost there.. And I have been in the same boat myself a bunch of times. Nothing like thinking you just wrecked your new toy....
You can use the microsd to load the Vanilla with ClockworksMod, but you are still in a boot loop. So, like others stated format the internal SD. Then use your USB mount option to copy over the stock rom and flash. This will get you back up and running.
Reboot, install TNT lite using Clockwork, reboot, skip Google sign in. Install Titanium and clear that google process. Create a Google Account and reboot.
Market should work after that.
butchconner said:
Roebeet,
I am back up on TnT 2.20 and your suggestion was a part of what I did.
I really believe something messed up the SDCARD2 operation. After I loaded CWM that way, I couldn't get it to work anymore and so the re-installs keep just trying to load the faulty 1.01a setup.
But here's what I did.
I found the USB option on the Mounts and Storage menu in CWM. I plugged in the cable to mini-USB and my PC. I mounted/turned on the USB and the drive popped up in Explorer on the PC. I could see the old "Update.zip" file and "Recovery" folder on the SDCARD (the ones for 1.01a) and so I erased them. I then copied in the TnT 2.20 files and shut down the links and went back to the G-Tablet and CWM. Still wouldn't work.
So I went to the Advanced menu and re-partitioned the SDCARD -- 2048 and 256 as everyone suggested. Then I just went down the menu in CWM and formatted all the system/cache/sdcard/etc. folders. Then I went by to the USB-PC connection and loaded the ROM files into the newly created and formatted SDCARD folder. Went to the other menu item and told it to apply the zip file -- which it immediately did setting up TnT 2.20.
That rebooted and I went through most of the basic setup, got wireless working, web, etc.
Only problem is I need to get Root Explorer installed to do the Market Fix, and when I went to ES Explorer to go to downloads and install it, it didn't find it in the market. So I will have to figure out a way to install or use something that will let me install the Root Explorer apk I have in the "Downloads" directory on the SDCARD.
I will try to re-think this account and re-write it more accurately when I'm not so bleary-eyed and thick-headed. I have not seen a G-Tablet account of someone rebuilding using the kind of "side-loaded" method I scrabbled together.
Suggestions on how to get to the downloads directory to install apps?
Rev
From CWM,
Click to expand...
Click to collapse
FateZero said:
Follow this guide word for word
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
it will take you back to stock and you can start again.
Click to expand...
Click to collapse
Worked flawlessly for me. Thanks!
All,
Thanks to those who replied for help, moral support, suggestions, and whatever.
I have been up on 2.2.0 ever since the malfunction that started all this and now have added my desired software, etc.
Bottom line is that with this experience I now think I know enough to hold things together and do whatever testing I want to do. I hate to have learned it the hard way. And I wish I had known enough about CWM to load it first and preserve the stock hardware on it.
I will say that IMHO the G-Tablet rocks. Yes, the screen is substandard, but I usually hold it in front of me or set it up on a stand anyhow. And straight on it's not bad. I will keep following watching for a screen mod.
Again, thanks all.
Rev
I just recently received the new Spring Nexus S 4G...Model GRJ22 with Android 2.3.4 installed. I'm looking for the proper way to root this device and came across this article: http://www.redmondpie.com/how-to-root-nexus-s-4g-tutorial/
I'm currently on Step 2 and wondering if a mounted SD Card is necessary in order to root the device? On my last phone, the Motorola Atrix, I was able to root without having an SD Card and install all my apps to the phone. Does the Nexus S not have enough room to do this and if I do install SuperUser directly onto the device, would I be able to recover/reset to factory in the future?
My second question is this. At the end of this guide it says "You now have permanent root"...
If I ever wanted to restore/reset this back to factory settings is it possible? (this is a business phone, provided by my company, not a personal purchase). I will eventually have to return this device. Do I need an SD card in order to reset this to factory?
Thirdly (for those that may know)...I'm trying to reset my Atrix back to factory settings. I've flashed back to factory, and even went and did a hard reset on my phone. It's wiped all my apps clean and took me back through the initial setup. However, if I go to file manager...I still see all the folders that were created when I had my phone rooted. Program folders, temp files, photos I took...why are all these files/folders still here? It seems to have unrooted, but how do I wipe the phone back to COMPLETE factory form?
Answer to question 2:
You can reset this to factory setting pretty easily,
You need a 'Stock GRJ22 4G Nandroid' [keep it safe somewhere]
Then when in 'clockworkmod' click 'backup and restore' > 'restore' > 'StockGRJ22Nandroid.zip'
Then all will be back to STOCK after this operation is complete [ie. No Root,No Clockworkmod, No Modded Rom]
The only thing left to do is go into 'cmdprompt' [win7] and navigate to your Android-SDK ie. 'cd C:\android-sdk\tools' then type in 'fastboot oem lock'
Answer to question 3:
Even though you clicked 'Factory reset/wipe' it will always keep the files on your '/sdcard' directory, its pretty good really because i store all my 'cyanogen roms',spare apk's and a backup or two.
I do not know the answer to question 1 but i would assume that you didnt need an external /sd as i have a nexus s [3g model] and it has 16GB built in, meaning all was possible without needing one.
Hope this help you on your rooting journey, i know it can be tough to get your head around but it will sink in eventually, even the most skilled face daunting tasks
Great! Thank you so much!
Could you possibly link me to that StockGRJ22Nandroid.zip file?
Does anybody else have any words of advice? I'd really appreciate it!
Also is there anyway to erase those extra files left on my Atrix? A program...or possibly a forum that lists the default files/folders I need to KEEP so I can delete the other files?
In my opinion the article you are referring to is poorly written and incomplete. You'll be better off using this guide:
http://forum.xda-developers.com/showthread.php?t=1078213
You need to have Android SDK and proper phone drivers installed on your PC.
In the development section they have threads related to questions you have.
Sent from my Nexus S 4G using XDA Premium App
Hello !
I am feeling really down today after been trying to get my phone working again.
There is a huge problem currently, I am really annoyed that it doesn't work at all.
First thing, my phone won't start after update it just boot loops and never seem to end it.
First thing I noticed /boot, /cache /system and most things are gone, I can load up recovery but nothing more. I have no idea what happened but the whole image folder was wiped and I had to myself put in the CWM recovery.
I can't do an upgrade "again" as it will be stuck @ the unpacking part without starting it at all.
I been trying with 2.3 V2 and with B133(My stock rom I got).
If anyone has a solution that can solve this problem please help out if you could. Also if you are about to tell me get this and that, please most cases I haven't seen any of the Firmware roms in @modaco wiki links work. Means I can't download them, so if you happen to have spare copy please upload it and link it to me. I have been googling and looking through this section twice, nothing really worked out.
Thanks in advance !
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
dancer_69 said:
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
Click to expand...
Click to collapse
Hello, thanks for the reply.
I have no idea about this .cust_backup partition and how I am supposedly to access it via windows. Also the thing you said about fixing partition within Windows, the check disk thing. I am not sure about that part either as I can load CWM and it can read the partitions but they are empty. Also there is nothing in this forums that contains original things, only way for me to fix this if someone have extra copy and can guide me on how and where to place the all needed files. I am pretty sure it's only things that are missing and I can't get a grip out of this.
So to sum up what my problem is.
I did an upgrade from 2.2 to 2.3 with official firmware, it worked out normally but after a reboot my phone became stuck in an endless loop, I can't do anything and it will not I repeat it will not allow me to "re flash" any firmware I tried so far, the 2.3 V2 and B133.
I am begging someone in this forum section, please if you have the knowledge about this problem care to help?
I can't get a refund out the phone warrenty is off and I do not have that much spare money.
Thanks in advance !
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Blefish said:
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Click to expand...
Click to collapse
The most common things I have already done, but do enlighten me what this "custom" parition is. Because in windows I do not see such partition I see a removable partition which I have now added a folder called image with these containing files.
http://forum.xda-developers.com/showthread.php?t=1370960
EDIT ** Also regarding to first person who said about Windows partition manager. The thing is I see a lot of partitions and there is no labeling for them, might be because they are ext2/3 or even something else? In anycase I can't do so much I just find it really odd I have many duplicates and I am guessing that must be errors... Because I am seeing the main recovery partition which has no label too... its at 240 MB where 135MB is used. Lastly there is my internal SD card empty and healthy still I can't reach it within Windows if I do not mount it...And can't now without going into the android OS. I Have loads of free space "partitions I don't understand why they are there".
**
Thanks for helping out, it feels not good to have a half dead phone, it's still not solved :'-(
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
dancer_69 said:
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
Click to expand...
Click to collapse
I have placed all things that I got from here.
http://forum.xda-developers.com/showthread.php?t=1370960
And I can't run the upgrade firmware, it gets stuck at first stage which is to unpack the the update.app thing.
It just stays like that not blinking and frozen.
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
dancer_69 said:
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
Click to expand...
Click to collapse
You are not understanding me :-(, I have wiped already millions of times in millions of different ways just to get it work. And no, I don't have the device connrected when I upgrade, it won't work properly then, I have tried to wait for the progress bar to "start" move it won't happen the battery will die, and nothing happened.
I can't go in with normal Recovery mode, can only go in with CWM, the normal recovery mode is really small, I mean only 3mb, while the froyo version is 5mb. Now I am asking if you have the time to upload the image files from 2.3 V2, the ones in forums are for V1. Which I don't know might conflict.
Thanks again for trying to help me out, this is really frustrating to get it to work.
**EDIT**
I worked it out !
I think I understood what you meant, I did as you told I started first with pluggin in the charger forced it to upgrade and now it's upgrading, thank you so much dancer_69. I was going to go tomorrow to buy a new 2nd hand smartphone. But now I can save my money for other things !
**EDIT of EDIT **
I seem to have downgraded to B133, I will try now with B158 2.3 V2 again and hopefully it will work now.
Yes, wasn't clear because I don' t remember what I've done and solve it. But I think that I did it like you discribed too.
Anyway I'm glad that was helpful(kind of)..
And don' t give up so soon with smartphone' s bricks, I've faced brick kind of problems many times and if the device it' s not completely dead, there is something you can do. Maybe need more search or many tries(sometimes the same things) but at the end(and of course If there isn't a hardware problem) device can unbrick.
I am sick of MTP USB connection and I want to know if there's any way to use normal mass storage.
Today I tried to copy nandroid backups to my PC and I can't.. It just won't copy my files. (Windows 7)
adb pull will recursively grab the contents of a remote folder if you use a trailing /
e.g.
C:\foo> cd MyBackups
C:\foo\MyBackups> adb pull /sdcard/TWRP/BACKUPS/device-serial-num/
You may need to move your CWM/TWRP backups out of /data/media and into /data/media/0 if you are using lightly-rooted stock (as ro.secure = 1 and therefore the adb shell does not get root privs)
Other alternatives are mounting a drive or USB stick via OTG and shuttling files.
I use Win 7 Pro x64, and it is my impression that MTP seemed to behave better after I completely uninstalled the Google & XDA Universal Naked USB drivers, and used only the Asus N7 USB driver for everything (with a .inf file hack). TBH, though, I don't know why that would be the case though, as a generic MS driver handles the MTP connection. Perhaps 4.2.2 fixed something, I dunno - MTP seems to work OK for me now.
good luck
Thank you, that helped.
I also have related question for you, I had stock rom and now I am using PA ROM. Everything what saved after flashing PA is on storage/sdcard0 but there is also folder storage/sdcard0/0 where all stock rom data are... why? and can i merge them?
(also apps access only sdcard0, so for example Gallery doesn't see pics from sdcard0/0)
Tomaco said:
Thank you, that helped.
I also have related question for you, I had stock rom and now I am using PA ROM. Everything what saved after flashing PA is on storage/sdcard0 but there is also folder storage/sdcard0/0 where all stock rom data are... why? and can i merge them?
(also apps access only sdcard0, so for example Gallery doesn't see pics from sdcard0/0)
Click to expand...
Click to collapse
(TL;DR I don't know)
I've seen similar reports before, but I haven't experienced it myself, nor have I followed the issue. Do some more searching on this forum, I guess. I don't know if it's custom recoveries that have been causing that behavior, or if it has something to do with the ROMs being flashed, or whether it is a 4.1.x/4.2.x multi-user conversion issue. There probably should be some traffic in the custom recovery threads about it.
I've been using TWRP and sticking with lightly-rooted stock and haven't observed such behavior. About the closest thing that I experienced was that initially TWRP put its stuff at /data/media/TWRP, but after I manually moved it to /data/media/0/TWRP, it seemed happy enough with that (and started putting new Nandroid backups into the moved folder location). That makes it easy enough to get backup copies off the tablet using MTP, even though it is irritating that timestamps don't get preserved doing things either of these ways.
good luck
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Diet6 said:
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Click to expand...
Click to collapse
Do you still need help? What about mtp mounting? You can pull * for a whole folder
Why not adb sideload a new rom?
I don't think I can MTP mount a Nexus 10, at least not in recovery mode. What I ended up doing was buying a OTG usb drive and making a backup to that. Problem was it split the tar over 4 files, which corrupted them (or at least made them not work with 7zip or tartool) fortunately I was able to get them to work with cygwin enough to get the files I wanted. I didn't want to sideload a new rom until I had backed up certain application data just in case it removed it.
All in all, had to buy a OTG usb drive (I would have just bought a cable but all the stores around here had was this "Dane 16gb OTG drive". So 20 bucks later I had the files I needed. Still annoyed that you can't do a ADB backup from fastboot or recovery mode, it seems like those would be the best places because no system files are in use, but who knows maybe the developers know something I don't.
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
TWRP recovery mode can only backup to OTG (if your device supports it, Nexus 10 does), but if the backup is larger than 2gb it will split the file and you will need some form of linux to extract it.
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Well you can easily flash latest rwrp that does well on my Linux mount internal storage but another solution is just flashing a rom with abd sideload and the'the back up from pc the content
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Or that will just un brick your tablet
Diet6 said:
Still annoyed that you can't do a ADB backup from fastboot or recovery mode
Click to expand...
Click to collapse
adb doesn't work in fastboot mode, only recovery or Android itself.
Diet6 said:
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
Click to expand...
Click to collapse
Maybe because /data (not talking about /data/media) wasn't mounted?
Diet6 said:
TWRP recovery mode can only backup to OTG
Click to expand...
Click to collapse
Huh?
Diet6 said:
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Click to expand...
Click to collapse
That's NTFS' problem, not TWRP's.
beekay201 said:
1. adb doesn't work in fastboot mode, only recovery or Android itself.
2. Maybe because /data (not talking about /data/media) wasn't mounted?
3. Huh?
4. That's NTFS' problem, not TWRP's.
Click to expand...
Click to collapse
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Diet6 said:
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Click to expand...
Click to collapse
I'd just 'tar' what I wanted on the device and then pull that with adb.
Yeah, I just had no idea what I wanted. I'm not 100% familiar with how the system stores application data, I figured if I copy everything than anything I "miss" after I formated it I'll be able to just research where it was and dig in the backup and pull it out.
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Khaon said:
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
Yes, sorry for the slow reply. I've completed my update, just wanted to follow up on everything I did incase the information is useful for anyone else new to this like I am.