Database Users

Boot Manager on Kindle?

Hey all,
So I've been trying to get Boot Manager working on the Kindle Fire. I've entered in all of the settings it has asked for, but the app stops when it tries to download some file.
I'm at work now, but I'll post the settings later tonight. I'm reasonably sure they are correct.
Has anyone had any luck, or is this just not possible? I'd love to dual-boot between ICS/Stock. Speed should even be better than what I'm used to with my OG Droid, since the 'SD card' on the KF is just the internal memory...
Alright, here are the settings. These are for on the CM9 ROM.
Device Name: blaze
SdcardBlock: /dev/block/mmcblk0p12
System Size: 528mb
Data Size: 1170mb
Cache Size: 100mb
Didn't know the cache size, but I figured it didn't matter much.
Finally, the program accepts all this and then complains about being unable to download files. Any idea why?
Edit2:
I went to init2winit's IRC channel, and I'm trying to help them get the settings to port it correctly. Will update here if anything comes of it...

podspi said:
Hey all,
So I've been trying to get Boot Manager working on the Kindle Fire. I've entered in all of the settings it has asked for, but the app stops when it tries to download some file.
I'm at work now, but I'll post the settings later tonight. I'm reasonably sure they are correct.
Has anyone had any luck, or is this just not possible? I'd love to dual-boot between ICS/Stock. Speed should even be better than what I'm used to with my OG Droid, since the 'SD card' on the KF is just the internal memory...
Alright, here are the settings. These are for on the CM9 ROM.
Device Name: blaze
SdcardBlock: /dev/block/mmcblk0p12
System Size: 528mb
Data Size: 1170mb
Cache Size: 100mb
Didn't know the cache size, but I figured it didn't matter much.
Finally, the program accepts all this and then complains about being unable to download files. Any idea why?
Edit2:
I went to init2winit's IRC channel, and I'm trying to help them get the settings to port it correctly. Will update here if anything comes of it...
Click to expand...
Click to collapse
I've been trying to get it to work 2. I got past the downloading part but using a older apk that was on there support forum but it still doesn't work right. Tryed CM7 and ICS and even tryed it on a stock+ rom none worked. Iv'e been useing the setting below. I can get roms to install in cm7 but won't even try to boot them so I switched to the clockwork recovery just in case that was the prob no go there and tryed to flash one of the update.zip s but it wont flash it errors out because it can't copy the boot.img file.
Device Name: omap4sdp
SdcardBlock: /dev/block/mmcblk0p12
System Size: 528mb
Data Size: 1170mb
Cache Size: 256mb
I also would love to get this to work, because I can't decide on a rom to use would love to keep a copy of one of the Stock+ roms for a the Amazon junk.

Just to clarify, you WERE able to install ROMs at some point? Link to APK perhaps?
Also, what error message do you get specifically when you try to flash the update.zip?

podspi said:
Just to clarify, you WERE able to install ROMs at some point? Link to APK perhaps?
Also, what error message do you get specifically when you try to flash the update.zip?
Click to expand...
Click to collapse
Yes was able to install ROMs in SD slots.
The APK is in the thread http://forum.init2winitapps.com/viewtopic.php?f=7&t=278 on there forum about not being able to dl files.
After you get it to download files it won't build the boot.img for the phone rom but you can copy the boot.img from your phone roms zip to the bootmanger/phonerom folder then run the phone rom setup and it works that way.
Then you can install a rom in a sd slot on ICS and stock it had probs doing that but on CM7 it says its succesful. But when you try to boot the rom it does nothing at all. So I tried flashing the update.zip from the SD rom slot and it errors out. I'll attach the log.txt form boot manager for you and a copy of the failed flash recovery.log and the .apk, the apk will only work if you have a paid for bootmanger since it connects to google for a check.

Thanks! I got up to the point you reached, but I haven't been able to boot the installed ROM.
I even tried manually flashing the boot.img via fastboot, but no go. Just a bootlock (and not a bootloop of the SD ROM).
Hrm... That is a bit disappointing but I don't know enough to be able to tell whether that means it isn't working at all, or whether there is some path that isn't correct somewhere...

[Q] Nook Color - Google Apps Pack won't install

Hello,
I have just installed CyanogenMod 7 for the Barnes & Noble Nook Color :: V7.0.3 using ClockworkMod Recovery.
After installing CyanogenMod 7, I install the Google Apps addon version: gapps-gb-20110307. The installation goes smoothly, and I receive the "Installation Complete!" message before I remove the MicroSD card and reboot.
Upon reboot from ClockworkMod Recovery, I receive an "Installation Failed" screen that tells me to power on and off the device. I do so, and successfully boot into CyanogenMod7.
I immediately proceed to the Homescreen, where the only items are "Messaging" "Contacts" "Clock" "Email" "Camera" and "Gallery". I have no prompt to set up my Google Account or Timezone. Also, I do not have Market, but I can connect to my WiFi network.
Thank you for your help, it is appreciated. I am obviously a noob, and my apologies for stepping on any toes!

Wow! Looking at some of the questions neighboring mine and their lack of responses, I tend to doubt that mine is going to get answered, even over the long run. I thought this forum had active users, at least that is what the Registration Video said...6 million active users was it???

First of all, deep breath. It may not get answered right away, but typically the questions get answered.
First off, any particular reason you are running 7.0.3? If I recall, this includes the old kernel that has terrible battery life. I would recommend going to 7.1 found here.
I don't know which gapps goes with 7.0.3, but I would double check to make sure it was the right one. I'd still recommend upgrading to 7.1 stable.

Also, I personally recommend doing ROM and GAPPS in two steps... I have eliminated some of the problems I have seen myself by using that method.
1. Install ROM... boot it up... let it settle in.
2. Reboot into CWM and install GAPPS... boot it up... do your thing
Also remember... 4 hours isn't a real long time to wait before posting a second post like you did... especially on a Sunday evening... This is a forum... not an immediate feedback application.

My apologies for my impatience. I did not mean to sound so callous, but after rereading my comment, I realize how abrupt it was.
Also, I remember the site introduction mentioning clicking on the thanks meter as a piece of site etiquette. How do I do that?

After following your advice, I am still having the same problem: not able to use the Android Marketplace as the item is not on my Homescreen, and the Google Apps are not installing.
I took biohazrd's advice, and I upgraded to 7.1 stable.
I also took DizzyDen's advice and installed CyanogenMod 7.1, reboot, let it settle, powered off, booted into Clockwork and installed the google apps pack (gapps-gb-20110828-signed), then rebooted again.
Still, I have no Android Marketplace.
As I stated in my previous post, I am a newbie, and I don't know what I am talking about, but off the top of my head, I have a feeling as if the google apps pack that I used (gapps-gb-20110828-signed) is not the right one. Could this hold any water?
Also, I don't know if it makes any difference, but I bought my Nook in December 2011 and it is a refurbished model. Because I purchased it in 2011, I updated the partitioning scheme using (repartition1GBdata-v1) and (reformatData-v1).
Thanks again, I appreciate the help!

Littlefatman said:
After following your advice, I am still having the same problem: not able to use the Android Marketplace as the item is not on my Homescreen, and the Google Apps are not installing.
I took biohazrd's advice, and I upgraded to 7.1 stable.
I also took DizzyDen's advice and installed CyanogenMod 7.1, reboot, let it settle, powered off, booted into Clockwork and installed the google apps pack (gapps-gb-20110828-signed), then rebooted again.
Still, I have no Android Marketplace.
As I stated in my previous post, I am a newbie, and I don't know what I am talking about, but off the top of my head, I have a feeling as if the google apps pack that I used (gapps-gb-20110828-signed) is not the right one. Could this hold any water?
Also, I don't know if it makes any difference, but I bought my Nook in December 2011 and it is a refurbished model. Because I purchased it in 2011, I updated the partitioning scheme using (repartition1GBdata-v1) and (reformatData-v1).
Thanks again, I appreciate the help!
Click to expand...
Click to collapse
If it isn't on the Homescreen, did you check by open App Drawer?

Thanks for the reply Votinh.
I did not find the Marketplace in the App Drawer. My app drawer currently contains:
Browser, Calculator, Calendar, Camera, Clock, Contacts, Dev Tools, Downloads, DSPManager, Email, File Manager, Gallery, Messaging, Music, Phone, ROM Manager, Search, Settings, Sound Recorder, Spare Parts, Superuser, Terminal Emulator, Theme, Chooser, Videos and Voice Dialer.
I was having a look around and figured out how to look at the Internal storage and found something called Market Apps Installer version 1.1. I click on it, but it offers few options to fiddle with and seemingly no way to access the Android Marketplace.
Again, thanks for your help, I truly do appreciate it!

If it doesn't work as expect, I guess you have to list step by step what you have done up to that point, that may help us pin point where and what you did wrong.
Also, pls clearly indicate where you run the ROM from.

Thanks again for your help, Votinh.
votinh said:
Also, pls clearly indicate where you run the ROM from.
Click to expand...
Click to collapse
I am not sure what you mean. Where can I possibly run the ROM from (what are the possible answers)? I would assume that I could run it only from the SD card. Sorry for being a newbie!
I will list step by step all of my actions and detail them in the response. Maybe, I will go through the whole installation process again and mark down everything that transpires.

Also, what do you think of my theory? That I am downloading and installing the wrong gapps pack?

Littlefatman said:
Also, what do you think of my theory? That I am downloading and installing the wrong gapps pack?
Click to expand...
Click to collapse
gapps-gb-201111028-signed.zip is still on the CM wiki as the latest version... did you verify MD5 checksum and ensure you didn't have a bad download?

Littlefatman said:
Thanks again for your help, Votinh.
I am not sure what you mean. Where can I possibly run the ROM from (what are the possible answers)? I would assume that I could run it only from the SD card. Sorry for being a newbie!
I will list step by step all of my actions and detail them in the response. Maybe, I will go through the whole installation process again and mark down everything that transpires.
Click to expand...
Click to collapse
In here, xda NC forum, you will frequently see the term "eMMC" and "uSD"
eMMC refers to the internal memory of the device, as currently where the B&N stock ROM resides while uSD is the external card where we can put the custom ROMs such CM7/9 in and run from there.
Depends on which method you choose to use, different procedures/instructions needed.
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
Littlefatman said:
Also, what do you think of my theory? That I am downloading and installing the wrong gapps pack?
Click to expand...
Click to collapse
As for your theory, I and we assume that you have installed CORRECTLY and if it isn't working as expect, then we need to know step-by-step how you did.
Everything is possible from bad zip to bad card.

My apologies for the delay in my reply. It has been a hectic week+end.
did you verify MD5 checksum and ensure you didn't have a bad download?
Click to expand...
Click to collapse
I am ashamed to say it, but I do not know how to verify a checksum to ensure the intergrity of a download. Although, I did download the gapps file twice, once each on different computers, copied it to the SD card and attempted to update. Is it possible that I could have gotten 2 bad downloads on 2 different PCs?

I have gone back and redone every bit of my CyanogenMod and Google apps installation on my Nook Color. I have taken notes on it and below is my step by step description of what I have done and observed. My apologies for the book, but I wanted to be as thorough as I could. Thanks for your help and I would appreciate and advice that can help me resolve this unfortunate situation.
1. Downloaded ClockworkModRecovery (2gb_clockwork-0.7.tar.gz) from http://code.google.com/p/monster-rootpack/downloads/detail?name=2gb_clockwork-0.7.tar.gz&can=2&q=
2. Downloaded CyanogenMod 7.1 (update-cm-7.1.0-encore-signed.zip) from here http://download.cyanogenmod.com/?type=stable&device=encore
3. Downloaded Google Apps (gapps-gb-20110828-signed) from here http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
4. Downloaded Win32DiskImager (win32diskimager-binary) from here https://launchpad.net/win32-image-writer/+download
5. Extracted Win32DiskImager files to a folder on desktop
6. Decompressed and Extracted ClockworkModRecovery to Desktop (this took longer than I expected, the extraction strangely taking 5 minutes)
7. Start up Win32 DiskImager and receive the following File Error message: An error occurred while accessing the device. This usually means something is currently accessing the device; please close all applications and try again. Error 1 Incorrect Function.
8. The File Error message displays itself 3 times. I click OK three times, and then the Win32 Application opens, and I continue with my process.
9. Use Win32 DiskImager to write ClockworkMod onto my MicroSD card. The MicroSD card is a 1 year old, 2GB Transcend MicroSD Card. I use an Kingmax MicroSD card adapter to plug the card into my Computer’s SD card slot.
10. Copy the CyanogenMod 7.1 file and the Gapps 20110828 file to the MicroSD card.
11. Eject the MicroSD card from the PC, insert it into my Nook, and power on.
12. Boot into ClockwordMod Recovery, I go to Mounts and Storage, click on Format System and confirm YES. Next, I format Data and Cache.
13. NOTE: Previously, I was receiving an "Error: can't format /data" error as my newer Nook Color had a different partitioning scheme. I used ‘reformatData-v1’ and ‘repartition1GBdata-v1’ to remedy this when I first attempted to install CyanogenMod. It seems to have gone off without a hitch.
14. I then go to ‘install zip from sdcard’ , the choose ‘choose zip from SD card’ and select the Cyanogenmod 7.1 zip. It opens and installs.
15. After the install completes, I remove the SD card and reboot the Nook.
16. Upon reeboot, I get a Cyanogen loading screen for a few seconds, followed by an error screen that says Install Failed with a large red and white exclamation mark over a Nook clip art.
17. The Nook powers off after a few seconds. I then power on again and sucesssfully boot into Cyanogenmod. I do not have the Marketplace app at this point.
18. I power off, replace the SD card, and boot into Clockworkmod.
19. I choose ‘install zip from sdcard’ and then ‘choose zip from SDcard’ and the gapps zip. I confirm YES and install the gapps zip.
20. I remove the SD card and reboot the system. I receive the exact same ‘Install Failed’ error screen with the red and white exclamation mark over a nook clip art.
21. After a few seconds the nook powers off after the error screen. I power on again and boot into CyanogenMod.
22. There is no Marketplace app on the homescreen or in the App Drawer, leaving me with the same initial problem
Thank you for everything!

I don't think Market will show until you have registered with google. There is a setup wizard or one time provisioning process to go through. That may be the thing that is failing when you first boot. Not sure how to get you back on track.
Sent from my NookColor using Tapatalk

Re: Google Apps Not Installing
Hi,
After you install CM 7.1, Google Apps, and reboot (hard power off and cold boot - the first boot will fail), look for the Google Talk app in your App Drawer and log in to it with your Google credentials. That should spawn the installation of the rest of the Google Apps, including the Android Marketplace.
Also, strangely enough, when installing my first app from the Market, I had to install it with the device physically in landscape mode, as the installation failed when the device was being held in portrait orientation. This seemed to clear up after the first app was installed.
I stumbled across this thread tonight, as I was searching for a solution to this exact problem while updating a friends Nook Color to CM 7.1. This did the trick for me.
Good luck!
Frank

Thank you Frank! I am going to finish up my current task then break out the Nook and cross my fingers that this will work! I will let you know!

I, too, am having problems
I don't mean to thread-jack, but I am also having problems with gapps.
Following this thread: http://forum.xda-developers.com/showthread.php?t=1000957
The version of CM7 I placed on my card is "cm_encore_full-253.zip". The steps all the way through putting that on the card, putting that in the Nook, booting, it all worked fine. I DID notice the line that said something along the lines of looking for the gapps installation, not finding it, and skipping that step.
I downloaded the Gapps ("gapps-gb-20110828-signed.zip") onto my computer. I shut off my NC, took out the SD card, and went to put it into my computer. Lo and behold, my computer can't read the SD card. It tells me it needs to be formatted before it can be used.
Uh. How am I supposed to get anything on the sd card?! I can't even format it to start over - Windows fails to format it.
I tried plugging in my NC to my computer - I at least got the CM7SDCARD to open, but it doesn't appear to be everything (there's no "boot" folder there). I tried moving the zip file to just the main directory of what I saw, and booted into recovery mode, but nothing happened.
Any assistance would be appreciated!

U
caseystain said:
I don't mean to thread-jack, but I am also having problems with gapps.
Following this thread: http://forum.xda-developers.com/showthread.php?t=1000957
The version of CM7 I placed on my card is "cm_encore_full-253.zip". The steps all the way through putting that on the card, putting that in the Nook, booting, it all worked fine. I DID notice the line that said something along the lines of looking for the gapps installation, not finding it, and skipping that step.
I downloaded the Gapps ("gapps-gb-20110828-signed.zip") onto my computer. I shut off my NC, took out the SD card, and went to put it into my computer. Lo and behold, my computer can't read the SD card. It tells me it needs to be formatted before it can be used.
Uh. How am I supposed to get anything on the sd card?! I can't even format it to start over - Windows fails to format it.
I tried plugging in my NC to my computer - I at least got the CM7SDCARD to open, but it doesn't appear to be everything (there's no "boot" folder there). I tried moving the zip file to just the main directory of what I saw, and booted into recovery mode, but nothing happened.
Any assistance would be appreciated!
Click to expand...
Click to collapse
Look at my post here. It tells you how to make the boot partition show up in your system. In your case download the rar rev 1 and follow the directions (per edit 2) on how to manually put the file on your system.
http://forum.xda-developers.com/showthread.php?p=22858059
Edit: You sound like a newby, so in order to do this you need the program "root explorer" which you buy on the market. Very useful program for later use too.
If you don't feel like trying this, get a different card reader or computer to see if that helps reading the card.
Edit 2: Also look here for a more recent nightly that has a few bugs fixed. It was built in January and 253 was in November.
http://forum.xda-developers.com/showthread.php?p=23198390

[Q] Backup from TWRP with USB

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.

exFAT and NTFS drivers for Lenovo Yoga Tablet 2 - a solution!

I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Edit: Now it has a CWM/TWRP installation zip for easy use!

Lurker0 said:
I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Click to expand...
Click to collapse
Thanks a lot for putting effort into this! I haven't tried it yet, but I'd suggest to create an app/APK which installs the files necessary and which features some buttons for mounting and unmounting. A CWM package is not such a good idea due to the fact that we have only temporary CWM and hence installing would still be a bit painful. This app could be something like a Yoga tablet 2 toolkit, which could maybe even include my sharpness fix

I've created CWM/TWRP installation zip with exFAT and NTFS drivers, and mounting script. It can be downloaded from here:
https://github.com/Lurker00/Android-fs/releases
Now, if you have rooted your Lenovo Yoga Tablet 2 (any screen size), and have SuperSU installed, just download UPDATE-android-fs-1.0.1-install.zip, install the same way, and start using exFAT (strongly recommended!) or NTFS (not recommended!) microSD.
To safely unmount for hot unplug, use Android settings. For mount after hot plug, better to reboot your tablet.
Note: the microSD file system is checked before mounting, and, if errors are found, it is mounted as read-only. So, if you find out that you can't write to the microSD, safely remove it and check (allowing to fix errors) it under Windows. It is strongly recommended to check and fix under Windows, because both exFAT and NTFS are produced by Microsoft, and no open source software is able to correct the file system errors correctly!
I have Yoga Tablet 2 8''. But the installation zip contains binary files for a number of platforms, and may work on other Lenovo Android devices. Being manually installed, the drivers are confirmed to work on:
Lenovo Vibe Z2 Pro
Lenovo Vibe Z2
Lenovo S90
so I see no a reason why they will not work being installed via recovery console.

I almost thought my Yoga 2-850F is broken as it was impossible to mount or format any micro SD card. Even when I tried formatting the card with my android phone using various file systems (i.e. exfat, ext4 etc.), I would always get an error. Finally, just flashing the zip did the trick. Thanks for the script!

I've updated the drivers to version 1.0.2:
1. One more supolicy rule added to the mounting script. Without it, unmount from Android Settings didn't work.
I didn't put per-platform binaries this time, because the recovery zip contains them all.

I'm sorry for so frequent updates, but
exFAT/NTFS fuse drivers binaries for Android v1.0.3
The problem is that the original exFAT driver was designed to update the file system only at unmount events, but the current Android never unmounts microSD mounted not by Android's vold process Meaning, file system corruption may happen on a reboot or power off.
Version 1.0.2 partially addresses that issue, and is stable enough. Only freshly created directories can be damaged by a reboot, and only if there were no any file operations after that, i.e. a rare case. Version 1.0.3 ensures that the file system is kept consistent almost always. It can be damaged only by removing microSD card during write operation.
Nevertheless, I plan to make at least one more release, to keep microSD clean, when there are no pending writes. Also, I'd try to improve the write performance compared to 1.0.3, without a penalty of the file system consistency.

I just have released
exFAT/NTFS fuse drivers binaries for Android v1.0.4
and I can say I'm quite satisfied with both performance and robustness of the resulting exFAT driver (no changes were made to ntfs-3g). So, I believe, it is the final build for a while.

Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though

Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.

Kalachnikos said:
Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.
Click to expand...
Click to collapse
I didn't upgrade to Lollipop myself, and I don't want to.
The driver and the mounting script are reported to work under Lollipop, but, for auto-mount on boot, they rely on /system/etc/install-recovery.sh script modified by SuperSU to launch with required privileges on system boot, which is not the case for Lollipop. It works flawlessly under Kitkat though.
You can find the detailed instructions at the github place from the link above. It's as easy as to root.

Hi,
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Many thanks !

You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.

Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I'm still on kit-kat, and rooted. I've yet to install CWM/TWRP though, so that's the first step. I'm pretty limited on tech skills so that might be an issue, but I'll see how it goes ; if it's a simple zip flash then great, otherwise things may get too out of hands
If/when I get around to testing, I'll keep you posted - but in the meantime many thanks for the work on this!

Thank you for your work. It works with exfat microsd 64 go sandisk and my lenovo 1050F tablet under lollipop.
I don't know how android system works, sorry for newbie questions
I try to have my external SD mounted in R/W at launch time.
In superSU, i change the following parameter : activate su on starting to enable but it does not work.
I have read that /system/etc/install-recovery.sh is executed by super-su. I can see at the end of this shell /system/etc/install-recovery-2.sh is called but it does not mount the SD in R/W...
Any help is appreciated! Thank you.

Unfortunately, Lollipop has more protection, and it launches install-recovery.sh in a very restricted environment, not enough for the mounting script to work properly. And I don't know a way to launch my script at the boot time with required privileges under Lollipop. One of the reasons I don't want to "upgrade" my 830LC to 5.0.1!

I have a Lenovo yoga tablet 2 830LC, upgraded to Lollipop 5.0.1 recently. There are no proper root guides for the Lollipop version anywhere on the forum, and since I'm interested in rooting my device and also be able to write to the external sd card, I request you to guide me on this. I'm sorry if this isn't the proper thread for my request but would be appreciated much.

zach181 said:
Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though
Click to expand...
Click to collapse
Hi.. i hv rooted and in that process flashed supersu thru temp recovery twrp... now iam not sure how to activate again twrp... any advise...thanks

Same way you did it when rooted. It is launched one time only.

mmlbbntr said:
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Click to expand...
Click to collapse
Yeah, it's a shame that Lenovo hasn't included exFAT support.
Read on...
Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I love you, man! :good:
I just got your drivers to work on a Lenovo Tab 2 A10-70F running Android 5.0.1.
Yes, the install-recovery-2.sh mounting script doesn't work there, because it runs in a restrictive security context on Lollipop, if I've understood it correctly.
I flashed your update zip, noticed that it didn't work, then searched for some other options. I thought about init.d, but that isn't supported on this tablet either.
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
One needs to have SuperSU and busybox installed, and flash your update zip with a custom recovery (this one works for the Tab 2 A10-70, F & L).
Then create /system/su.d directory and move the /system/etc/install-recovery-2.sh script there. It can be named anything, I renamed it "/system/su.d/00mount_exfat_ntfs.sh".
I'm not too sure about the permissions, I used 755 for both the directory and the script.
In the SuperSU settings (accessible in the SuperSU app), the option "mount namespace separation" must be disabled.
I have a 64GB SanDisk Ultra microSDXC card, but for some reason it wouldn't want to work with exFAT on this tablet at first.
/dev/block/mmcblk1p1 did not show up while the card was inserted, only /dev/block/mmcblk1.
I formatted the card with NTFS, and that worked. I changed it back to exFAT, and then it finally did show up. Weird.
Anyway, would you recommend exFAT or NTFS, Lurker0?
I've used this card with NTFS on an older tablet, and it was rock solid, which I can't say about my experience with exFAT.
One minor caveat: the card isn't automatically mounted on insertion. Mounting requires another execution of the mounting script, either by rebooting or running "su -c /system/su.d/00mount_exfat_ntfs.sh".
Is there any way to make that automatic?
Thanks again.

Tzul said:
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
Click to expand...
Click to collapse
Thank you for finding! I'll read more and try to update my package.
Tzul said:
Anyway, would you recommend exFAT or NTFS, Lurker0?
Click to expand...
Click to collapse
NTFS is not flash-friendly, so I believe exFAT is better.
Tzul said:
Is there any way to make that automatic?
Click to expand...
Click to collapse
It requires to write an application to watch for system mount events and run that script. I'm lazy to do it

TWRP 3.2.1 for H901

The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it. I've personally used this version to do a backup and restore but can't guarantee there won't be issues. If there are while you are still in twrp you should go to the advanced section and copy the log to your external sd card. This log will help them diagnose any issues.
The project is located at: https://twrpbuilder.github.io
Their XDA thread is located here: https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
If you already have TWRP installed installation is as follows: Click Install, choose Image file, navigate to where the TWRP img file is located on your external sdcard and flash that img to the recovery partition. Back out to the root dir and you can select reboot then recovery...it should bounce you right back into recovery and you should see the new version loaded. If you have root in the rom and run into issues the app "flashify" can reflash TWRP 3.0 so make sure you also have it's img available.
This is pretty much only for folks who already have twrp to update to the latest. If you are on nougat you are still stuck until an exploit is released that works for nougat the way dirtycow did for marshmallow and below. *update* an exploit to give root to nougat users is now available thanks to @runningnak3d here: https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942

Reserved Post #1

Reserved Post #2

famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://www.androidfilehost.com/?fid=8180705828505018
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
Click to expand...
Click to collapse
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:

NYLimited said:
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:
Click to expand...
Click to collapse
You are correct. For some reason a few characters got truncated. I've corrected the url in post #1.

famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it.
Click to expand...
Click to collapse
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:

NYLimited said:
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:
Click to expand...
Click to collapse
I've passed on the date issue. Uncertain if he'll generate another build though.

famewolf said:
I've passed on the date issue. Uncertain if he'll generate another build though.
Click to expand...
Click to collapse
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?

NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.

NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
As to the dimming, you can check in settings to see if something can be configured however each person compiling twrp can set their own options as to how they want it to function. There is no guarantee or expectation that Person B is going to use the same options as Person A. You are of course free to compile your own copy configured the way you would prefer it to behave but the process was enough of a pain in the butt I just requested twrpbuilder to generate one as I kept getting errors. The process to compile it also appears poorly documented.

sabresfan said:
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.
Click to expand...
Click to collapse
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
famewolf said:
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
Click to expand...
Click to collapse
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...

NYLimited said:
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...
Click to expand...
Click to collapse
A fairly recent app/utility created by @kdrag0n called Tipatch brings a long-needed resolution to the table regarding "full backups" of Data using TWRP. In a nutshell, Tipatch installs to your Android device as a basic APK. Within the simple GUI, once root permissions are granted (In-Place Patching) Tipatch will decompile, patch, recompile and flash the patched TWRP to /recovery, effectively patching your TWRP build to backup the contents of Internal Storage (emulated SD card) as part of Data itself, so that backups will now include those Internal Storage contents such as downloads, photos, videos, game data, and other various files. I've tried it on this particular build of TWRP and it works without any issues. There are options to patch TWRP without root permissions as well. There are Windows, Mac & Linux versions available too. If you are patching TWRP on a device with an A/B partitioning scheme, the patched TWRP can be installed on both A & B using a one-click option. Of course, one insurmountable caveat to patching TWRP with Tipatch is that wiping Data now will also wipe Internal Storage (emulated SD card). In short, the utility works on pretty well all device types and chipset platforms (Exynos, Kirin, Snapdragon, MediaTek, etc.). The latest Tipatch update, v1.6, includes support for TWRP builds that use LZMA compression, and removes the now-misleading notification previously listed when backing up Data -- that Internal Storage (/data/media/ path / emulated SD card) contents are not backed up. Anyway guys, here is a link to the Tipatch Discussion & Support thread: https://forum.xda-developers.com/android/apps-games/app-twrp-tipatch-backup-internal-t3831217
The latest Tipatch v1.6 app is also available on the Play Store and many other app & apk repos for Android. Versions for Windows, Mac and Linux can be downloaded using the above link.