BL1.1 + BL 1.2 - ClockworkMod Recovery 4.0.1.5 - G Tablet General

Yes, once again, I take no credit for the actual recovery... all credit goes to koush (clockworkmod) and bekit... I merely modified the recovery so that there is a bootloader 1.1 & bootloader 1.2 version...
DOWNLOAD [BOOTLOADER 1.1]
DOWNLOAD [BOOTLOADER 1.2]
NVFLASH INSTALLATION INSTRUCTIONS:
1. Boot into APX mode
2. If you are using Windows, make sure the APX drivers are installed
3. Use the following command to flash the recovery using NVFlash
nvflash --bl bootloader.bin --download 9 recovery-clockwork-4.0.1.5-smb_a1002_bl1.1.img [BL1.1]​nvflash --bl bootloader.bin --download 9 recovery-clockwork-4.0.1.5-smb_a1002_bl1.2.img [BL1.2]​
ANDROID RECOVERY (STOCK/CWM) INSTALLATION INSTRUCTIONS:
1. Create an update zip (you can use the update zip of any existing recovery zip and replace the recovery.img)
2. Reboot into recovery mods
3. Flash the update zip
IMPORTANT INFORMATION:
1. This version of ClockworkMod Recovery is capable of understanding internal storage vs. external storage. By default, if an external storage device (SD card) is detected, the recovery mounts that device as the SDCARD (/sdcard). In this case, the internal storage is accessible if it is explicitly mounted via the Mounts & Storage menu in the recovery screen. The internal storage is mounted as EMMC (/emmc).
2. If there is no external storage device, as a fallback to preserve all functionalities, the internal storage is automatically mounted as the SDCARD (/sdcard).
3. Like all ClockworkMod recoveries, all the basic functionalities like flashing ROMs, backing up the system, etc. work off the SDCARD. So if you have an external storage device (SD card), the recovery will use the external storage for all functionalities. At the moment, if you have an external storage device (SD card), you cannot use the internal storage (EMMC) for any recovery functionalities.
IMPORTANT:
1. Make sure you use the correct recovery based on you bootloader version, or you will not be able to access the recovery and you will have to NVFlash the recovery again.
2. Internal storage is mounted as /emmc and external as /sdcard, so copy update zips to the external storage.
3. If you do not have external storage, I believe the recovery should auto mount the internal storage as /sdcard.
4. Familiarise yourself with NVFlash so that you will be able to recover you tablet should, in the unlikeliest of events, you soft brick you device.
CREDITS:
koush (clockworkmod) for the ClockworkMod Recovery
bekit for making the first ClockworkMod Recovery for the GTablet
pershoot for the 1.1 & 1.2 kernel
MODS: If you feel this should go under the Development thread, please move it...

Thank You for sharing this tool.
Do you know what does this release differ from the cwm3.0.2.8 rev5 that some of us have been using on 1.2 bootloader ?
Thanks
Dave

I don't know for sure... there were some jumps in the recovery numbering... and I never kept track exactly... but it probably contains some small fixes... and has the ability to make use of an external sd card, including formatting and partitioning it

Anecdotally speaking, backups and restores get faster with each new version. CWM v5 on my phone backs up SO fast.
Glad to see v4 for gtab.
Thanks!
MC

I'm running the old green one (version 2). Works great. Will drop the new one tonight.
sent from my superfast Calkulin+Clemsyn Gtablet with Clemsyn Kernal *now with Nitrous Oxide* using Tapatalk

I flashed this internally via flash_image from /sdcard and got some errors (I've seen this before with a successful flash) flashed again to be sure and it showed [not flashing header is the same]
Shutdown and booted into recovery but it just hung on the birds showing [recovery key detected]
Flashed it again via Clockwork 3028 as an update.zip (4015)
This time I got into recovery.
Doesn't seem to be any way to switch between Internal/External SD
If an ExternalSD is inserted it is used/mounted as /sdcard and if no External is inserted than the InternalSD is used/mounted as /sdcard as well (also applies via USB).
I guess the full benefit here would be that you can now format/partition both InternalSD (emmc) and ExternalSD (sdcard) if External is indeed inserted.
Thanks for this Craig, it's always nice to have options.

Partition SD doesn't work.

Had to NVflash my way back to version 3. I was sitting at version 2, which I had zero problems with, except certain files require using 3+. Yours (4) has some weird issues with mounting the "internal" SD card. The only one I could see was external. No matter what way I mounted it.
sent from my Calkulin+Clemsyn 7 Gtablet with Clemsyn Kernal using Tapatalk

Sharpe351 said:
Had to NVflash my way back to version 3. I was sitting at version 2, which I had zero problems with, except certain files require using 3+. Yours (4) has some weird issues with mounting the "internal" SD card. The only one I could see was external. No matter what way I mounted it.
sent from my Calkulin+Clemsyn 7 Gtablet with Clemsyn Kernal using Tapatalk
Click to expand...
Click to collapse
If you remove the microSD and then boot into CWM it will mount the internal SD. (Yeah, strange.)
~Nick
Sent from my Calkulin+Clemsyn gtab using Tapatalk

Sharpe351 said:
Had to NVflash my way back to version 3. I was sitting at version 2, which I had zero problems with, except certain files require using 3+. Yours (4) has some weird issues with mounting the "internal" SD card. The only one I could see was external. No matter what way I mounted it.
sent from my Calkulin+Clemsyn 7 Gtablet with Clemsyn Kernal using Tapatalk
Click to expand...
Click to collapse
Well, that's how the newer Clockwork recoveries work... if there is an external SD card present, it will be mounted as /sdcard.... while the internal storage can be mounted as /emmc (through the Mounts & Storage menu)... to keep things consistent with the way storage devices are mounted in CM7 and most Gingerbread ROMs...
But the recovery is smart enough to understand that you may not have an external SD card, in which case, the internal storage is mounted as /sdcard.

craigacgomez said:
while the internal storage can be mounted as /emmc (through the Mounts & Storage menu)...
Click to expand...
Click to collapse
I have an ExternalSD inserted and I mount InternalSD as /emmc however, when I go to backup/restore > restore, I only see External, so what is going on, am I misunderstanding something here.

Just noticed, mount USB doesn't work with this (bl 1.2 ver).
MC

OK, perhaps I jumped a gun here and took for granted that people are aware of the way CWM recovery exactly works... I have updated the OP with more details...

craigacgomez said:
OK, perhaps I jumped a gun here and took for granted that people are aware of the way CWM recovery exactly works... I have updated the OP with more details...
Click to expand...
Click to collapse
The problem is you think it works one way and everyone else is used to something else. I have used CWM Recovery on a lot of different devices, and I've NEVER had to mount emmc as the internal storage card. IMHO I think you have it backwards. It (internal storage) was ALWAYS the default. ALL the other versions floating around here are built that way also. Especially for the Gtab. I've used version 2 and version 3 and both default to the internal SD card. The recovery on both of my phones mounts the same way.
sent from my Calkulin+Clemsyn 7 Gtablet with Clemsyn Kernal using Tapatalk

Sharpe351 said:
The problem is you think it works one way and everyone else is used to something else. I have used CWM Recovery on a lot of different devices, and I've NEVER had to mount emmc as the internal storage card. IMHO I think you have it backwards. It (internal storage) was ALWAYS the default. ALL the other versions floating around here are built that way also. Especially for the Gtab. I've used version 2 and version 3 and both default to the internal SD card. The recovery on both of my phones mounts the same way.
sent from my Calkulin+Clemsyn 7 Gtablet with Clemsyn Kernal using Tapatalk
Click to expand...
Click to collapse
@Sharpe351, maybe it's time to clarify the way things are and how things work... habit vs. standard implementations...
1. bekit forked the original CWM recovery and built it for the GTablet. We often still use this version which is dubbed as CWM recovery 0.8 (I believe this was synonymous to CWM recovery version 2.5.0.8). This recovery was capable of understanding only one memory mount point and bekit set it up to mount the internal storage as the SDCard and everything worked off the internal storage. Any external storage device present was not easily accessible via the recovery console.
2. bekit also built a version of CWM recovery 0.8 which ignored the internal storage and mounted the external storage devices as the SDCard. If the external storage devices is missing, the recovery is almost useless.
[In the above 2 recoveries, the availability of storages were mutually exclusive]
3. As the ability for multiple storage detection entered the CWM source, bekit then built CWM recovery to follow "standards"... these "standards" matched the mount points of the CyanogenMod ROM and the recovery... internal storage as "emmc" and external storage as "sdcard". So the external storage device became the operational storage for the recovery. This was the CWM recovery version 2.5.1.2.
4. Soon came CWM recovery 2.5.1.3, where the same "standards" were followed, but this version introduced the "fallback". If there is no external storage device, the recovery automatically mounts the internal storage as the SDCard.
5. All future 2.5.1.x version of CWM recovery for the GTablet (which was now part of the mainstream CWM recovery list) followed the "standards" approach along with the "fallback". IMHO, none of the CWM recovery 2.5.1.x were well known and commonly used. All 2.x.x.x recoveries were compatible with only the 1.1 bootloader.
6. With the introduction of the 1.2 bootloader branch, I believe roebeet introduced the CWM recovery 3.0.2.8 Rev 2. This once again was built for a "single storage" device, and hence only has the capability of mounting the internal storage as the SDCard. An external storage device is virtually useless in this recovery.
7. Roebeet further fine-tuned this recovery and dubbed it as CWM recovery 3.0.2.8 Rev 5, which still considered the GTablet as a "single storage device" and mounted the internal storage as the SDCard.
8. CWM recovery 4.0.1.5 was originally built as part of the mainstream CWM recovery list... a continuation after the 2.5.1.x releases. This recovery was built similar to the 2.5.1.x releases, were the "standards" of storage mounting were followed and the "fallback" to internal storage kept the recovery functional if a external storage device was not present. This was
9. I took the CWM recovery 4.0.1.5, and while keeping every standard CWM recovery functionality untouched, customised the recovery for both bootloaders. It follows the mounting "standards" and has the "fallback".
To summarise this post, we have be accustomed to using recovery version where the recovery was built as a "single storage" recovery and only understand the internal storage... CWM v.0.8 for BL1.1 and CWM 3.0.2.8.rev.5 for BL1.2.
This is not how "standard" CWM recoveries for multi-storage devices work. These recoveries use the external storage as the SDCard by default and mount the internal storage as the SDCard in the absence of an external storage device. All CWM recoveries built from the CWM tree for the GTablet, unless customised otherwise, will follow this approach.

Well this may be the case, but the 5 android devices I've owned or currently own all used CWM the same way. Installed directly from the app on my device. Sdcard is internal storage and emmc is external. The same way my current gingerbread rom on my phone sees it as well.
I'm not trying to get into a pissing contest with you, this is my experience.
sent from my Calkulin+Clemsyn 7 Gtablet with Clemsyn Kernal using Tapatalk

Sharpe351 said:
Well this may be the case, but the 5 android devices I've owned or currently own all used CWM the same way. Installed directly from the app on my device. Sdcard is internal storage and emmc is external. The same way my current gingerbread rom on my phone sees it as well.
I'm not trying to get into a pissing contest with you, this is my experience.
sent from my Calkulin+Clemsyn 7 Gtablet with Clemsyn Kernal using Tapatalk
Click to expand...
Click to collapse
Oh.. yeah... this is, and should be, a healthy debate... and your experience is from what you have running on your devices... perhaps some info about the devices you own... the recovery version, ROM versions... I'll dig in a bit and let you know what's the difference... but let's keep this other device talk off topic... perhaps via PM...

...and I feel stupid, I usually have an extra sd card in my tab, but took it out as part of the process of helping the Flashback team and Clemsyn identify causes for SOD on BL 1.2, otherwise I would've noticed it mount the external SD and remembered to mount internal if I want to see it.
MC

craigacgomez said:
Oh.. yeah... this is, and should be, a healthy debate... and your experience is from what you have running on your devices... perhaps some info about the devices you own... the recovery version, ROM versions... I'll dig in a bit and let you know what's the difference... but let's keep this other device talk off topic... perhaps via PM...
Click to expand...
Click to collapse
Outside of our healthy debate, can this CWM be modified to work the other way? As in seeing the internal storage as SD card? BTW, just checked, the newest version of CWM I had was 3.x.x.x... not sure if it makes a difference. My phone now uses a custom built recovery just for the ported CM7 I'm using now (IHO for Optimus V) . It sees only 1 SDcard. There is only 1 SDcard.
-Mike
sent from my Brilliant Corners Gtablet with Clemsyn Kernal using Tapatalk

Sharpe351 said:
Outside of our healthy debate, can this CWM be modified to work the other way? As in seeing the internal storage as SD card? BTW, just checked, the newest version of CWM I had was 3.x.x.x... not sure if it makes a difference. My phone now uses a custom built recovery just for the ported CM7 I'm using now (IHO for Optimus V) . It sees only 1 SDcard. There is only 1 SDcard.
-Mike
sent from my Brilliant Corners Gtablet with Clemsyn Kernal using Tapatalk
Click to expand...
Click to collapse
Well, I've never done any "real" recovery coding till date... but it's something I plan on investigating... so I'll definitely give it a shot!

Related

[Q] Phone won't recognize internal storage from SD partition

Hello everyone -- like everyone always says, I did quite a bit of research before posting this, but I can't seem to find the right answer for me.
(I use Cyanogenmod 7 on my HTC Hero (Sprint).)
After using ROM Manager to partition my SD card (it says it successfully partitioned, and the phone boots fine), my phone won't recognize its new internal storage. Like when I go to "manage applications" it only shows my 156 MB, not the 512 MB like I expected from my ROM Manager partition.
The only other person I've found who said the same thing, after quite a bit of searching, said ROM Manager wouldn't work for him for some reason, but Amon_RA did.
So I flashed Amon_RA, partitioned the SD card that way too, and my phone still will not recognize its internal storage. I set the partition w/ Amon_RA to 700+ MB and rebooted but the phone again only says I have 156 MB of internal storage.
I would use ClockworkMod, but the highest level supported for the HTC Hero doesn't have the partition mode. And considering how the other two programs were unable to partition it, I feel like it's more a mistake on my end.
Am I making some dumb mistake on the last step? I don't know of many other options I can be messing up -- in the case of ROM Manager, I simply enter in my specifications (I've tried with no swap and small swap) and it does that fine and boots fine. My phone just doesn't recognize the internal memory.
I forgot to add -- when I go under Cyanogenmod's settings --> application settings --> the "Use internal storage" option is grayed out, saying "This device doesn't have extended internal storage."
Format the sdcard,Delete all of the partitions you have made and try again using clockworkmod (An older version would be nice thats what i use).Then make a partition through the recovery's menu set the swap size to 0 and select ext2/3
You can also try an ext-4 partition
[email protected] said:
Format the sdcard,Delete all of the partitions you have made and try again using clockworkmod (An older version would be nice thats what i use).Then make a partition through the recovery's menu set the swap size to 0 and select ext2/3
You can also try an ext-4 partition
Click to expand...
Click to collapse
Thanks for the reply! Clockworkmod's website says the latest supported version for the HTC Hero (CDMA) is 2.5.0.7 -- do you know of a version that would be safe for me to use that will also support partitioning? Also, I've read that ROM Manager simply uses Clockworkmod to partition SD cards, so would using Clockworkmod itself offer a better solution than my failed ROM Manager efforts?
After reading your post, I used the 2.5.0.7 CWM to format my SD card and Ext, then I flashed and booted Amon_RA again to wipe the partitions. I then used Amon_RA to partition my card (with no swap as you specified). And I used Amon_RA to upgrade my Ext2 to Ext3. After rebooting, my "Use internal storage -- This device doesn't have expanded internal storage" was still grayed out and the internal memory still showed me at 156 MB.
I returned to Clockworkmod to mount /sdcard and /sd-ext (which I had never tried before). Still no new internal memory, same checkbox grayed out.
Am I being a total idiot here? Thanks for any help in advance!
I don't mean to spam this thread, but upon returning to Clockworkmod 2.5.0.7 to reformat the SD card and try again -- I find that it still offers me the option to mount /sdcard and mount /sd-ext.
Does this mean that my previous mounting didn't take? Maybe this is the source of my problem, that my phone won't let me permanently mount the /sdcard or /sd-ext. Any ideas along these lines?
Edit: I went back, formatted and re-installed partitions w/ Amon_RA (no upgrade from Ext2-->Ext3 this time though). After the box was still grayed out and my internal storage still 156 MB, I went back to CWM to mount /sdcard and /sd-ext -- then I simply rebooted CWM, and it STILL said I had the option to mount /sdcard and /sd-ext.
gjs16 said:
Thanks for the reply! Clockworkmod's website says the latest supported version for the HTC Hero (CDMA) is 2.5.0.7 -- do you know of a version that would be safe for me to use that will also support partitioning? Also, I've read that ROM Manager simply uses Clockworkmod to partition SD cards, so would using Clockworkmod itself offer a better solution than my failed ROM Manager efforts?
After reading your post, I used the 2.5.0.7 CWM to format my SD card and Ext, then I flashed and booted Amon_RA again to wipe the partitions. I then used Amon_RA to partition my card (with no swap as you specified). And I used Amon_RA to upgrade my Ext2 to Ext3. After rebooting, my "Use internal storage -- This device doesn't have expanded internal storage" was still grayed out and the internal memory still showed me at 156 MB.
I returned to Clockworkmod to mount /sdcard and /sd-ext (which I had never tried before). Still no new internal memory, same checkbox grayed out.
Am I being a total idiot here? Thanks for any help in advance!
Click to expand...
Click to collapse
the version is ok
i think you should better use windows to remove partitions (with disk management)I dont know if the problem persists then try a different sdcard(maybe a friend's)
Hi,
I'm running Cyan 7 on Legend and having the same problem.
The option for 'expanded internal memory' is still grayed out, no matter what!
I tried using CMW to partition, it only gave me maximum 512 MB while I wanted 1 GB but whatever. That doesn't work.
I tried Ubuntu live CD to format and partition the card into 2 parts, first FAT and second ext3/ext4 -> doesn't work.
The last option is to use an app called S2E from the market. It does the job, but still isn't the official supporting of expanded internal memory from Cyan.
There's a tutorial how to manually partition the card. It mentioned using rm 1 command to remove the partition. However I found that it was impossible because the recovery was running on that partition and thus cannot remove itself.
Any other solution?!
Thanks guys!
For gjs16: mounting partitions in recovery are only in effect when you are in that recovery session; once you boot the phone the mounts are gone.
I was looking into this CM7/Use internal storage thing myself (I'm playing with my old Nexus One) which is how I came upong this thread. I think this option works "out-of-box" only on devices that have some internal flash in addition to an sd-card slot, like the Samsung Galaxy S (2 GB ROM for apps + 8/16 GB internal storage + sd-card slot).
So, this is just a guess but I think you'd have to play with the mount points, perhaps with symlinks, to make it work with a partitioned sd-card, so that CM7 recognizes the fs structure the way it is handled in e.g. SGS.
Edit. This solution worked for my NX1+CM7: http://forum.xda-developers.com/showpost.php?p=18911182&postcount=1784
Just flash this right after flashing CM7 (and gapps if you want them). It mounts the sd-ext to /data so you can have all the space you need for your apps...

[MOD] Data2SD (Enhanced) - I/O Fix

At the suggestion of several users, I am forking the previous thread. I am planning on supporting several ROMs and this is the best course to keep everything organized and provide support.
What is this?
Background:
The speed of the flash memory in the Transformer line of tablets is very poor. This is very apparent when installing or updating applications from the Play Store, copying files over USB, or using an app that caches lots of data like a web browser. The tablet will hiccup and stutter due to the I/O bottleneck. Running Androbench shows random write speeds averaging less than .2MB/sec.
The workaround:
Utilizing a fast, class 10 microSD card, we can move the /data partition to something significantly faster. The /data partition is where apps are installed to and where they store their configuration information and data. By redirecting /data to these fast microSD cards, we eliminate this bottleneck from our devices. With a properly fast card, users have reported a complete elimination of I/O related hiccups and system freezes. I have based my enhancements on the initial work by TweakerL on the Transformer Prime. Credit to fordwolden to porting his work to the Infinity.
The enhancements:
Previous implementations of this mod had the internal data partition mounted to /data2, with the media subfolder (your internal user storage) only available via root apps. There were symlinks set up at /sdcardi, etc, but these still required root permission to access. This is due to permissions on the /data partition and applies to both /data and /data2. Google gets around this by creating a "virtual" sdcard that points to /data/media. I have created a second "virtual" sdcard that points to /data2/media. This mod creates the scenario below:
/data = ext4 partition on microSD (fast)
/data2 = ext4 partition on internal storage (slow)
New changes:
/data/media -> Virtual SD Card Daemon -> /storage/sdcard0
/data2/media -> Virtual SD Card Daemon -> /storage/sdcardi
/sdcardi -> Symlink -> /storage/sdcardi
/mnt/sdcardi -> Symlink -> /storage/sdcardi
/storage/sdcardi is the virtual SD card for the internal storage. You should see all the files you had saved to this space before using data2sd. These files should be accessibly by any standard non-root Android app.
Note to kernel developers: This mod is more than just changes to the kernel. In order for the internal storage to be properly mounted at /storage/sdcardi, I have modded the Virtual SD Card Daemon that comes with Android. The stock binary is /system/bin/sdcard. I made a copy, modified it using a hex editor, called it /system/bin/sdcardi, and included it in my flashable zips. If you wish to make a data2sd version of your kernel, you must include this file in your zip. Additionally, be sure to add the "service sdcardi" line to your init.cardhu.rc that I have in mine.
Installation
Requirements
1) Class 10 microSD, at least 8gb
2) A computer with card reader
3) Partitioning software. Recommended: gparted LiveCD
Instructions
1) Decide how big you want to make the ext4 partition for /data. Remember, this is going to be the space for installing applications AND the /sdcard space that games will use the cache their extra data. Kindle books, Dropbox files, pics from the camera WILL ALL GO HERE. Personally, I decided to make the ext4 partition the whole 64gb of my card.
The ext4 partition has to be partition #2 on the microSD card. Why? This is to give people with large cards the option of creating a FAT32 or NTFS area as partition #1. This allows the card to be read by a Windows or Mac computer using a card reader. I use my tablet as my card reader with the USB cable, so I wasn't worried about this. I used gparted to create a small 8mb unformatted partition as partition #1, then a second 64gb partition to fill the rest of the card. I formatted this second partition in ext4.
2) Format your microSD card - Download Gparted Live CD (http://goo.gl/dJQAu) and use Imgburn (http://goo.gl/33MY9) to write to disc. Boot to Gparted using your CD after setting the CD as the primary boot device in your BIOS. Once in Gparted, create the 2 partitions described above, the first partition is Fat32, the second partition is ext4 or ext2. Set both partitions to type: Primary.
3) Insert microSD into tablet and flash any data2sd kernel for your ROM. (Note: Flashing any ROM will overwrite your data2sd kernel. You will have to re-flash the data2sd kernel if you change ROM or even upgrade your current one) After booting back into Android, you should be greeted with the Setup Wizard. Remember, this is a fresh /data partition, so it's a clean slate. It's a good idea to take a TitaniumBackup** ahead of time. I am experimenting with ways to make the transition more painless.
**Note about taking a TitaniumBackup before switching to data2sd. After the conversion, your internal storage will be mounted to /sdcardi. By default, TitaniumBackup looks for previous backups in /sdcard not in /sdcardi. You have two choices. Copy the TitaniumBackup folder from /sdcardi to /sdcard and restart the app, or change the backup location to /sdcardi/TitaniumBackup in the app preferences. Either of these options should work fine.
Optional: Verify data2sd is working. Pick any method you like:
a) Open a file explorer such as Root Explorer, ES, etc. You should see /sdcard and /sdcardi and be able to browse the files within. /sdcard is your ext4 partion on the microSD while /sdcardi is the internal storage. You should able to copy data between them.
b) Download "Androbench" app from the market and run "micro" sdcard check, if you see 0.4mb/sec or more in random write you're on data2sd.
c) Power off your device, remove your microSD card, then power back on your device. You should received an error message "Encryption unsuccessful". Insert microSD and reboot to fix.
Uninstallation
Don't like data2sd? Just flash a non-data2sd kernel using recovery and when you boot back into Android your /data will be on the internal storage. This could also be accomplished by flashing your ROM on top of itself without wiping.
Troubleshooting
1) Grab the mount-data2sd.zip from the second post.
2) Boot into TWRP and flash the mount-data2sd.zip. This will mount the microSD as /data in recovery. It will allow us to wipe it, format, etc using recovery.
3) Wipe "Internal Storage". This will erase the entire ext4 partition on your microSD.
4) Flash ROM
5) Flash data2sd kernel for ROM
*CAUTION*: If you don't flash mount-data2sd.zip before your wipe, you will be wiping your internal memory.
Download data2SD kernels
These are flashable zips. It will disable journaling on the microSD ext4 partition. You do not have to do this manually! Flash these after flashing the ROM.
CyanogenMOD 10.1 - beta2: http://d-h.st/rOe (Based on 4-2 nightly and may behave unexpectedly on other builds)
CleanROM 3.2.2: http://d-h.st/sCa - WORKS WITH CleanROM 3.3!
clemsynTFUniversalCyano650GPUFsyncver3: http://d-h.st/duw
ClemsynTFUniversalStock: http://d-h.st/IBm
clemsynTFUniversal650GPUver7 (Stock/CleanROM): http://d-h.st/S4k
Recovery
I made a flashable zip to help the recovery console understand our modification. By default, if you go into recovery and do a factory reset, it is formatting the /data partition on the internal storage. The issue same applies to nandroids. We may be using the second partition of our microSD card for /data, but the recovery does not know this. It will look to the internal /data partition during backup and restores.
This zip does not make any modifications to your tablet or copy any files. It simply updates your recovery mount points. The changes are temporary and are lost during the next reboot. You will need to flash it each time you boot into recovery.
After flashing this zip you will be able to:
1) Wipe data / Factory reset. The /data partition on the microSD will be wiped
2) Backup and restore nandroids. The /data partition on the microSD will be backed up or restored.
3) Choose "Flash zip from internal sdcard" and browse the files on the internal storage
4) Access and flash zips from the microSD storage. Choose "Flash zip from internal sdcard" and notice the !microSD folder at the top. This is a symlink that will kick you over to the microSD storage. This !microSD folder appears on your internal storage after you flash this zip for the first time. It remains unless you delete it. Even so, next time you enter recovery this !microSD symlink will not go anywhere until you flash this zip.
Please report your experience with this.
http://d-h.st/pPe
This one too.
So this is basically flashable on CleanRom 2.3 right? Only thing wrong is that it doesn't show up in windows over USB? I can live with that as long as apps can read it in the Android OS itself.
can I use flash this on cleanrom 2.3 to diasable journalling on my ext4 partition
Diogenes5 said:
So this is basically flashable on CleanRom 2.3 right? Only thing wrong is that it doesn't show up in windows over USB? I can live with that as long as apps can read it in the Android OS itself.
Click to expand...
Click to collapse
Nope. This has changes to framework-res.apk which is ROM specific. I will post a CleanROM 2.3 version in a few minutes for you guys.
Thanks - Appreciate your hard work
---------- Post added at 08:46 PM ---------- Previous post was at 08:37 PM ----------
wow that was fast-thanks
---------- Post added at 08:58 PM ---------- Previous post was at 08:46 PM ----------
i was getting 6000 with clemsyn -I got low 5000's with this new mod
clownberg said:
i was getting 6000 with clemsyn -I got low 5000's with this new mod
Click to expand...
Click to collapse
This is not clemsyn's kernel, this is the stock CleanROM 2.3 kernel. I will mod clemsyn's latest kernel and post it for you.
Mistar Muffin said:
This is not clemsyn's kernel, this is the stock CleanROM 2.3 kernel. I will mod clemsyn's latest kernel and post it for you.
Click to expand...
Click to collapse
Unable to have it work with cleanrom. Boot loop
titou00075 said:
Unable to have it work with cleanrom. Boot loop
Click to expand...
Click to collapse
Use recovery to wipe the /cache partition. Due to the changes in framework-res.apk this may be necessary if you aren't coming from a completely clean install of a ROM.
I just booted to recovery and wiped my microSD /data partition. I also wiped /cache and /system. I installed CleanROM 2.3 and in the same recovery session I flashed the clemsynTF700ver22GPU650VC-data2sd kernel and it booted right up.
May be a stupid question but do you still need TWO primary partitions on the SD card (i.e., first is FAT32 while second is Ext4 and used by the mod)? If this isn't necessary or not possible, should the recovery (i.e., installation) files be placed in internal storage?
Forgot to mention I'm using Windows 7 MTP and CleanROM 2.3
Mistar Muffin said:
Use recovery to wipe the /cache partition. Due to the changes in framework-res.apk this may be necessary if you aren't coming from a completely clean install of a ROM.
I just booted to recovery and wiped my microSD /data partition. I also wiped /cache and /system. I installed CleanROM 2.3 and in the same recovery session I flashed the clemsynTF700ver22GPU650VC-data2sd kernel and it booted right up.
Click to expand...
Click to collapse
Ok thanks. Will do:thumbup:
Your Awesome, Thank you!
cheers
Thanks Gonna try this.
done the work install all three files in the OP, however it is taking a long time to boot....Can someone give me an idea as to how long this normally take onn first bootup after a fresh install?
please advise
tyfoxx
Couldyou make one for blackbean? i tried thecm 1029,but it doesnt boot. Would greatly appreciate it.
Sweet
I just ran every shortcut I could think of:
I used Mini partition tool to reduce reduce my 32 gig fat down to 16 gigs & then created a 16 gig ext4 partition.
Wiped everything in twrp and re flashed Clean 2.3 then the new zip.
All I can say is WOW.
Restored everything. Works great no more stalls and stable so far. Hope it stays this way. Now to focus on battery life.
Sent from my HTC Ruby using xda app-developers app
Diogenes5 said:
Restored everything. Works great no more stalls and stable so far. Hope it stays this way. Now to focus on battery life.
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
Glad it's working! I've prepared a little treat for everyone to make our recovery lives a little easier. Need to test a few more things before I post!
I'm running CleanROM 2.3 and ClemsynTF700ver22GPU650VC (awesome combo, btw). If I want to use this MOD, should I need to flash first CleanROM-2.3-data2sd.zip and later ClemsynTF700ver22GPU650VC-data2sd.zip, right? Of course, also, formating my microSD using ext4.
Awesome work here Mistar!!!! Thank you so very much for this!!! Gonna replace my SanDisk 32gb Class 4 card with a SanDisk 64gb Class 10 before I run this on CleanRom. I'm super excited about this mod!!!!!! Thanks a million!!!!!!
Sent from my EVO 4G LTE using xda premium

[Q] I cannot boot into my ROM (recovery only). How to restore ROM and boot into it?

Hi,
I'm running an Transformer TF101 with Clockwork Mod Recovery v5.8.3.4.
However some time ago I removed the zip file with the ROM from within the SD Card memory space - that of course being actually the internal 16GB of storage and not a MicroSD.
Since I cannot boot into any ROM and I haven't got a zip file with my ROM on my Internal Storage, what do I have to do to install a ROM back onto my transformer. It seems that unless I boot into the ROM itself (which by the looks of things has been wiped) I cannot access the internal memory storage.
Please help. How do I fix this and make it running again?
I have a very similar issue. I can boot to the ROM but there doesn't seem to be a launcher so throws up a load of errors.
Essentially I cannot access any external memory in the ROM or recovery so need the same instructions.
Cheers
Sent from my GT-i9100 using xda premium
mikber18 said:
Hi,
I'm running an Transformer TF101 with Clockwork Mod Recovery v5.8.3.4.
However some time ago I removed the zip file with the ROM from within the SD Card memory space - that of course being actually the internal 16GB of storage and not a MicroSD.
Since I cannot boot into any ROM and I haven't got a zip file with my ROM on my Internal Storage, what do I have to do to install a ROM back onto my transformer. It seems that unless I boot into the ROM itself (which by the looks of things has been wiped) I cannot access the internal memory storage.
Please help. How do I fix this and make it running again?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1688012 Follow the instructions in this thread. This will completely wipe your device and bring it back to stock no matter what SBK version of TF you have. You can then also choose to install a custom recovery as well as root it all from right here. Then you can install a custom rom back on. I also recommend using a recovery that uses the internal storage or external as it is much safer. You can always take out the SD, put a rom on it, replace it and boot into recovery. Much easier than using Easy Flash.

[ROOT][TWRP RECOVERY] Onda V972 Quad-core | Allwinner A31

Hello, Everybody!
CAUTION : I'm not responsible for any damage to your device.Use at your own risk
I want to introduce to you a Team Win Recovery Project 2.4.1.0 for Onda V972.
I think it will be usefull and for Onda V812, and V971, maybe other A31 tablets.
That TWRP works on 32 Gb version of Onda V972.
Installation TWRP Recovery on Onda V972
Before installing TWRP, you need to get root. All latest stock firmware comes with root, you need only install Superuser or SuperSU from Play Market
Download the Onda_V972_TWRP.zip from that post and extract it to any folder on your computer.
Copy all three files from your computer internal disk (ONDA_MID on you computer and /sdcard on tablet)
Install the application Terminal on the tablet and run it.
From the terminal emulator enter the following command:
Code:
su
Press Enter. Allow access to the application or SuperSU SuperUser
Code:
busybox sh /sdcard/install-recovery.sh
Press Enter. This command installs new recovery to your tablet.
Code:
busybox sh /sdcard/reboot-recovery.sh
Press Enter. This will load the device mode recovery.
You can also use the standard way of loading in recovery - While the tablet is off press Home button and holding it press the Power button untill 4 core logo appears.
If something goes wrong, you need to flash the firmware via Stock PhoenixSuit and during flashing select "YES" to the question about formatting.
It is not bug free version, there is a error: Unable to mount '/recovery' I will try to fix all bugs.
I repeat: Use it on your own risk!
Credits:
Thanks to Dees_Troy and all TWRP team for great work!
Thanks to darkrickpr from slatedroid for base TWRP
Thanks to hariprasadiit for his CWM port and his post.
Thanks, i love you
Its gréât
Envoyé depuis mon GT-I9100 avec Tapatalk
ankar84 said:
Hello, Everybody!
CAUTION : I'm not responsible for any damage to your device.Use at your own risk
I want to introduce to you a Team Win Recovery Project 2.4.1.0 for Onda V972.
I think it will be usefull and for Onda V812, and V971, maybe other A31 tablets.
That TWRP works on 32 Gb version of Onda V972.
Installation TWRP Recovery on Onda V972
Before installing TWRP, you need to get root. All latest stock firmware comes with root, you need only install Superuser or SuperSU from Play Market
Download the Onda_V972_TWRP.zip from that post and extract it to any folder on your computer.
Copy all three files from your computer internal disk (ONDA_MID on you computer and /sdcard on tablet)
Install the application Terminal on the tablet and run it.
From the terminal emulator enter the following command:
Code:
su
Press Enter. Allow access to the application or SuperSU SuperUser
Code:
busybox sh /sdcard/install-recovery.sh
Press Enter. This command installs new recovery to your tablet.
Code:
busybox sh /sdcard/reboot-recovery.sh
Press Enter. This will load the device mode recovery.
You can also use the standard way of loading in recovery - While the tablet is off press Home button and holding it press the Power button untill 4 core logo appears.
If something goes wrong, you need to flash the firmware via Stock PhoenixSuit and during flashing select "YES" to the question about formatting.
It is not bug free version, there is a error: Unable to mount '/recovery' I will try to fix all bugs.
I repeat: Use it on your own risk!
Credits:
Thanks to Dees_Troy and all TWRP team for great work!
Thanks to darkrickpr from slatedroid for base TWRP
Thanks to hariprasadiit for his CWM port and his post.
Click to expand...
Click to collapse
Thanks!!
Tried and installed! However it boots into the device recovery....no TWRP!! ..........did I commit an error??
aryanitinkumar said:
Thanks!!
Tried and installed! However it boots into the device recovery....no TWRP!! ..........did I commit an error??
Click to expand...
Click to collapse
Probably yes, a mistake was made.
If you load the default recovery, the installation on TWRP was not successful.
Did you get done after command busybox sh install-recovery.sh?
Do you got root?
Please, do screenshots of installation process and post them here.
ankar84 said:
Probably yes, a mistake was made.
If you load the default recovery, the installation on TWRP was not successful.
Did you get done after command busybox sh install-recovery.sh?
Do you got root?
Please, do screenshots of installation process and post them here.
Click to expand...
Click to collapse
Thanks......it worked! However, I m not able to make a back up on ext card.......any clues??
Thanks a million ................works great!!!
Thanks for your Recovery, it´s great ¡¡¡
But don´t mount the external sdcard, and for the developers is very much important.
Can you review this, please?
Sorry for my english
Greetings from Spain :good:
Very thanks for you work
Bye.
Hi again.
After various checks, really mount internal memory like external.
Where say "using internal memory" show the contents of external SD.
not if I explain well...
TWRP_Onda_v972_ver02
STEVE_MARS said:
Hi again.
After various checks, really mount internal memory like external.
Where say "using internal memory" show the contents of external SD.
not if I explain well...
Click to expand...
Click to collapse
Hi, Steve!
I take this opportunity to thank you for the excellent work SuperNova!
As regards that TWRP, I told, that it`s like an alpha version with a lot of bugs, and not everything working propertly. I just tested installing custom rom (SuperNova 3.1 and Iberica v.2) and it`s worked. And on my forum I asked people who have 32 Gb version of tablet if they can to install custom on their tablet, and they confirmed, that it`s work pretty good.
Just want to clarify a bit more on that as is currently working of that alpha version of TWRP.
When you boot into TWRP without external microSD card your internal memory (/sdcard on tablet and ONDA_MID on computer) will be Internal Storage in Mount menu of TWRP
When you boot into TWRP with external microSD card it will mount like a Internal Storage again, and there is no tablet real /sdcard mounted.
I also would like to note that in the Mount menu, item Mount SDCard will not work! Never! Now we are working on fix that problem.
But now, I made a new version, lets call it TWRP_Onda_v972_ver02 and it can mount both ext-sd and internal memory. But ext-sd you need to mount manualy, and we are working on that too.
In new version:
Internal Storage is a internal tablet memory (/sdcard on tablet and ONDA_MID on computer) Mounts at /sdcard
SD-Ext is a External microSD card, don`t forget to mount it manualy. Mounts at /sd-ext
Many thanks, my friend.
Now I can do the next Supernova wirh Aroma Installer :good:.
Greetings.
ankar84 said:
Hi, Steve!
I take this opportunity to thank you for the excellent work SuperNova!
As regards that TWRP, I told, that it`s like an alpha version with a lot of bugs, and not everything working propertly. I just tested installing custom rom (SuperNova 3.1 and Iberica v.2) and it`s worked. And on my forum I asked people who have 32 Gb version of tablet if they can to install custom on their tablet, and they confirmed, that it`s work pretty good.
Just want to clarify a bit more on that as is currently working of that alpha version of TWRP.
When you boot into TWRP without external microSD card your internal memory (/sdcard on tablet and ONDA_MID on computer) will be Internal Storage in Mount menu of TWRP
When you boot into TWRP with external microSD card it will mount like a Internal Storage again, and there is no tablet real /sdcard mounted.
I also would like to note that in the Mount menu, item Mount SDCard will not work! Never! Now we are working on fix that problem.
But now, I made a new version, lets call it TWRP_Onda_v972_ver02 and it can mount both ext-sd and internal memory. But ext-sd you need to mount manualy, and we are working on that too.
In new version:
Internal Storage is a internal tablet memory (/sdcard on tablet and ONDA_MID on computer) Mounts at /sdcard
SD-Ext is a External microSD card, don`t forget to mount it manualy. Mounts at /sd-ext
Click to expand...
Click to collapse
Thanks ankar84! It really had been so helpful and I had been able to install both SN & Iberica successfully :good:. Can you please guide how to update the new recovery on the earlier one. Will the new recovery overwrite the earlier one by simple installation?
Thanks in advance!!
---------- Post added at 12:02 PM ---------- Previous post was at 12:00 PM ----------
Thanks ankar84! It really had been so helpful and I had been able to install both SN & Iberica successfully . Can you please guide how to update the new recovery on the earlier one. Will the new recovery overwrite the earlier one by simple installation?
Thanks in advance!!
aryanitinkumar said:
Thanks ankar84! It really had been so helpful and I had been able to install both SN & Iberica successfully :good:. Can you please guide how to update the new recovery on the earlier one. Will the new recovery overwrite the earlier one by simple installation?
Click to expand...
Click to collapse
Hi, aryanitinkumar!
New recovery always overwrite the earlier one, so there is no big manual about installing new TWRP on old TWRP.
Today I compiled a new TWRP version for Onda V972 based on lastest stable TWRP 2.4.4.0
The internal and external memory mounts properly.
The internal memory is mounted in /sdcard
External memory is installed in the /external_sd
You can store backups on both the internal and the external memory.
External card mounted automatically.
Checked the backup and restore - worked great!
But now I publised on 4pda.ru to 32Gb version owners test it on their tablets. If everything will be good, I will publish it here!
ankar84 said:
Hi, aryanitinkumar!
New recovery always overwrite the earlier one, so there is no big manual about installing new TWRP on old TWRP.
Today I compiled a new TWRP version for Onda V972 based on lastest stable TWRP 2.4.4.0
The internal and external memory mounts properly.
The internal memory is mounted in /sdcard
External memory is installed in the /external_sd
You can store backups on both the internal and the external memory.
External card mounted automatically.
Checked the backup and restore - worked great!
But now I publised on 4pda.ru to 32Gb version owners test it on their tablets. If everything will be good, I will publish it here!
Click to expand...
Click to collapse
Thank you Ankar84 for your revert!
Would certainly wait for the latest version!!!:good:
Would you care to share the 4pda link would certainly test it as well!!!
Thanks!!
TWRP is compatible to the new firmware v1 of sdk 2.0 ?
Envoyé depuis mon GT-I9100 avec Tapatalk
MrDho said:
TWRP is compatible to the new firmware v1 of sdk 2.0 ?
Envoyé depuis mon GT-I9100 avec Tapatalk
Click to expand...
Click to collapse
Yeah!! Its fully compatible....works gr8 for me....however, I have installed the first version Onda_V972_TWRP!
Hi everybody, I do need some help. A few days ago, the tablet badly cusched. After restarting it, I noticed some application were missing, so I restarted again and got the green Emergency screen...
I wiped the tablet with PhoenixSuit and reinstalled the rom and everything went fine, but now every time I restart the tablet it looks like \cache and \data are wiped. That is, if I change settings or install any application and restart the tablet, these are all missing as if the tablet has just been flashed new. This happens with every rom I tried to flash. I confirm that I have no problem in accessing the recover (both stock and CWM).
As you can guess the tablet in these conditions is useless, any suggestion will be very appreciated!
TWRP based on lastest 2.4.4.0 for Onda V972 by ankar84
Well. On my main forum 4pda.ru nobody wanted to test latest stable version of TWRP. Apparently everyone is busy updating the firmware to version 2.0. So, I decided to publish TWRP stable version here. But, please note, I have no positive results of using this version of TWRP for 32 GB version of the tablet.
TWRP based on lastest 2.4.4.0 for Onda V972 by ankar84​Download: Ya.Disk | Mega
Differences between TWRP and CWM Recovery
Graphical user interface with full touch control.
Batch patches (up to 10p in the queue).
Customizable backup/restore. You can choose which partitions to backup/restore if you want to use compression and generate md5-sum set their own names backup and delete unwanted right from recovery
Displays the time (time zone adjusted separately), battery.
Saving settings of the recovery on microSD-card.
Built in Terminal Emulator.
The ability to connect the two cards to the computer as a USB-carriers.
Built-in file manager, with copy, move, delete, rename, change permissions.
A detailed log file.
Theming support.
TWRP based on latest stable version 2.4.4.0
Internal and External memory are mounted properly.
Internal memory installed in the /sdcard
External Memory installed in the /external_sd
You can store backups on a Internal and External memory as well.
External card is automatically mounted
Checked backup and restore - work
Team Win Project site
Compile manual
Thread on XDA
ankar84 said:
Well. On my main forum 4pda.ru nobody wanted to test latest stable version of TWRP. Apparently everyone is busy updating the firmware to version 2.0. So, I decided to publish TWRP stable version here. But, please note, I have no positive results of using this version of TWRP for 32 GB version of the tablet.
TWRP based on lastest 2.4.4.0 for Onda V972 by ankar84​Download: Ya.Disk | Mega
Differences between TWRP and CWM Recovery
Graphical user interface with full touch control.
Batch patches (up to 10p in the queue).
Customizable backup/restore. You can choose which partitions to backup/restore if you want to use compression and generate md5-sum set their own names backup and delete unwanted right from recovery
Displays the time (time zone adjusted separately), battery.
Saving settings of the recovery on microSD-card.
Built in Terminal Emulator.
The ability to connect the two cards to the computer as a USB-carriers.
Built-in file manager, with copy, move, delete, rename, change permissions.
A detailed log file.
Theming support.
TWRP based on latest stable version 2.4.4.0
Internal and External memory are mounted properly.
Internal memory installed in the /sdcard
External Memory installed in the /external_sd
You can store backups on a Internal and External memory as well.
External card is automatically mounted
Checked backup and restore - work
Team Win Project site
Compile manual
Thread on XDA
Click to expand...
Click to collapse
Thanks Ankar84...........would surely post update in regards....but later!
I had been using the very first version of TWRP posted by your good self and the same has worked great on my V 972-32 Gb version.
Yes first one worked well here too. Gonna try this one now.
Sent from my unknown using Tapatalk HD
---------- Post added at 10:51 AM ---------- Previous post was at 09:57 AM ----------
Can't download:
Mega is for chrome browser only and Onda is not compatible for download
I registered to yandex, I see the file but don't find a way to get it on the tablet..... frustrating
Sent from my unknown using Tapatalk HD
skippie17700 said:
Can't download:
Click to expand...
Click to collapse
ok, uploaded file here, see updates in post

[root tool] Toshiba Thrive 10.1" ICS

(Now, I know this is not in the right section or even in the device's page, but...)
Forewarning: I am NOT responsible for any damages caused by running this tool. (You ran it, not me.) Also, do NOT use on the Thrive 7 or ANY of the Excites! The Thrive 7 has an entirely different bootloader/partition layout than the 10.
Pio_masaki and I have been working hard for almost a year to get root on the ICS version of the Toshiba Thrive 10.
Last night, I was able to finally sneak past sealime.ko and have it work.
It uses the "root any ICS device" tool, with special modifications specifically for the Thrive 10.
(can't post any links, so it's on the "thrive-hackers" github page.)
Special note: While it is set up for OSX ADB, I have not been able to find any binaries.
Are you saying that we are close to a root method for Thrives running Toshiba ICS?
rohads said:
Are you saying that we are close to a root method for Thrives running Toshiba ICS?
Click to expand...
Click to collapse
Saying there is a method to root it now, yes, we got around sealime.ko. This means we can flash the HC bootloader which is unlocked, which allows custom recovery and kernels/ramdisks (boot.img) to be used.
BTW the link is https://github.com/Thrive-Hackers
congrats guys ! very awesome work !
jdsingles deodexed ROM w/ agat63's 1.3 kernel Suped up w/ CB 6.26.13
More specifically, it bypasses sealime to flash the unlocked bootloader. What we did was we MVd /dev/block/mmcblk0p6 to 0p9. It's a pure fluke Pio and I found out that it works. We found out that sealime was explicitly blocking write to 0p6, so he semi-sarcastically said to move it. I ran the mv command, whadda ya know? It worked!
'Course, getting the tool completed wasn't as simple as that...
PS: Could we get this moved to the Toshiba Thrive Development section?
Have instructions been written for the process?
worked for me
I used this tool on Jul 8 and it worked very well. I got it from thriveforums dot org. Thank you pio_masaki and AmEv.
I tried changing the recovery to the latest TWRP using "fastboot flash recovery twrp-2.4.1.0.img" while in bootloader. I was not able to, though as it kept giving me errors.
Does this bootloader not allow flashing a recovery? I noticed the rootme script uses adb commands to push the CWM recovery.
I am now running Dale's latest deodexed rooted ICS rom with the CWM recovery he included.
Other unrelated lessons learned:
If you can't mount your SD card in recovery, try a different card!
And, Dale packages his update.zip inside the downloaded zip file!
navyguy said:
I used this tool on Jul 8 and it worked very well. I got it from thriveforums dot org. Thank you pio_masaki and AmEv.
I tried changing the recovery to the latest TWRP using "fastboot flash recovery twrp-2.4.1.0.img" while in bootloader. I was not able to, though as it kept giving me errors.
Does this bootloader not allow flashing a recovery? I noticed the rootme script uses adb commands to push the CWM recovery.
I am now running Dale's latest deodexed rooted ICS rom with the CWM recovery he included.
Other unrelated lessons learned:
If you can't mount your SD card in recovery, try a different card!
And, Dale packages his update.zip inside the downloaded zip file!
Click to expand...
Click to collapse
Try fastboot flash:raw.
Is there any need to do a backup before rooting?
TubaMeister said:
Is there any need to do a backup before rooting?
Click to expand...
Click to collapse
Not explicitly, but it wouln't hurt in case your tablet got into contact with allspark.... er, the bootloader didn't flash, and you're stuck in a bootloop.
easy root and CWM recovery
walk thru
http://www.youtube.com/watch?v=MXeYJhKCgX8
adb driver
http://www.thriveforums.org/forum/t...vers-usb-adb-driver-installation-package.html
root tool
https://github.com/thrive-hackers/thrive-10-inch-ics-root,
follow this to install CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
follow to install touch CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
ROMs
http://www.thriveforums.org/forum/dalepl/
Uh oh
robyn402 said:
walk thru
http://www.youtube.com/watch?v=MXeYJhKCgX8
adb driver
http://www.thriveforums.org/forum/t...vers-usb-adb-driver-installation-package.html
root tool
https://github.com/thrive-hackers/thrive-10-inch-ics-root,
follow this to install CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
follow to install touch CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
ROMs
http://www.thriveforums.org/forum/dalepl/
Click to expand...
Click to collapse
I installed the drivers, used the root tool, the restore was successful, but now the tablet is stuck in a boot-loop mode.
The root tool was running, there was a line that said the screen would go blank, which it did, and it stayed there for several hours. When I came back to check on it, the tablet was off, so I turned it on. That's when I found the boot loop. It'll get to the home page, tell me that nova launcher has stopped, then loop back to the moving stars section of the boot screen.
Any ideas on what to do now?
DLeach4512,
if CWM is still alive, so just flash any ROM via CWM (flashing wipes all your data that exist in internal memory, so you need to make backup via CWM if you wish to save your data; and after flashing ROM you can import all data via Titanium Backup)
Kyonex said:
DLeach4512,
if CWM is still alive, so just flash any ROM via CWM (flashing wipes all your data that exist in internal memory, so you need to make backup via CWM if you wish to save your data; and after flashing ROM you can import all data via Titanium Backup)
Click to expand...
Click to collapse
You know, I feel kinda dumb because I didn't even try that!
Now i've tried it, and I see I can get into CWM.
I put a ROM on an SD card on my PC, then put that SD card into the Thrive and used CWM to install the .zip of the ROM I selected, and it won't install. It starts, then it says Installation aborted, but won't tell me why.
Any ideas where I should start unraveling this mystery?
1. check that your recovery is CWM and not stock recovery
2. check that you put on SD archive that contain folders named system and META-INF, file like boot.img, something other maybe (many ROMs archive contain "archive in archive", so you need to unpack archive from main archive and than put that internal archive on SD); after checking that all right try to flash that archive again
3. try another sdcard (full sized SDHC + formated in FAT32)
DLeach4512 said:
You know, I feel kinda dumb because I didn't even try that!
Now i've tried it, and I see I can get into CWM.
I put a ROM on an SD card on my PC, then put that SD card into the Thrive and used CWM to install the .zip of the ROM I selected, and it won't install. It starts, then it says Installation aborted, but won't tell me why.
Any ideas where I should start unraveling this mystery?
Click to expand...
Click to collapse
also make sure you open the zip and place the update.zip on your card -
From my GSIII - jd's Stock/Rooted/Deodexed 4.3
Kyonex said:
1. check that your recovery is CWM and not stock recovery
2. check that you put on SD archive that contain folders named system and META-INF, file like boot.img, something other maybe (many ROMs archive contain "archive in archive", so you need to unpack archive from main archive and than put that internal archive on SD); after checking that all right try to flash that archive again
3. try another sdcard (full sized SDHC + formated in FAT32)
Click to expand...
Click to collapse
Excellent!
1) I had to extract "update.zip" from the ROM I had downloaded.
2) I re-formatted the card I was using to FAT32 instead of FAT.
3) I was able to get the install started with no trouble after following your directions.
BIG THANK YOU FOR THAT!
I got a successful install message, and then it booted!
Thanks a million!
Problems after Mount Changes
I changed the mount as described on thriveforums.org to allow apks and data to go to the external sd rather than "shared" internal memory.
I now have the situation with less free memory available on the sd card than on internal. The CWM backups went on the physical card- a 32 G one almost full. Will look for a major mfr 64 Gig.
One or so issues with the revised mounts where the external sd card is now internal. They relate to making backups with dalepl's latest CWM 6.0.1: where to put CWM backups for now and are they being made correctly with the revised mounts?
The backup made prior to the mount change looks normal: a single, dated/numbered folder about 2.6 Gb, 6 files: boot.img, cache.ext4.tar, data.ext4.tar, nandroid.md5, recovery.img and system.ext4.tar. However, the one made after the mount change also has a dated, numbered folder of only 15.8 Mb and 7 files: .android_secure.vfat.dup, boot.img, cache.ext4.dup, data.ext4.dup, nandroid.md5, recovery.img and system.ext4.dup. There is a second folder associated with the later bu called "blobs", which is huge --2.76 Gb, 3292 folders and 6581 files. Is this an expected result and any one think it might be a valid bu?
Also, it went on to the external SD (now "internal") and total storage use is now almost 28 Gb out of 30.2. I now have the situation with less free memory available on the sd card than on internal. The stuff there looks ok, pix movies and music plus CWM bups of 5.5 G and App_Backup_Restore archived apks at 2.8 Gb. So, I copied the cwm backups folder to the real internal memory, now sdcard2. I assume this true internal memory might get wiped during a restore so, this is not a valid storage site for this? And, if I put copies on a spare card, will that really work if my downloaded apps are on the original card, eg does the CWM backup copy the external card apps?
As I note, for some reason this 'blobs' folder won't copy easily to a USB via the Thrive or Win 7 pc. It also won't copy to a Win 7 HD partition where I store my Thrive stuff. (Update: I was able to do a wireless transfer to my pc and then, from there, to a spare SD card.)
Any thoughts? Should I go back and change the mounts to default?
BTW, I find FolderMount has no real use with the changed mount on the Thrive unless someone tells me otherwise. With the Thrive mounting the external card as internal, files go to the physical card.
gberpa,
I don't understand your question - it is very long. But I know that custom recovery (CWM / TWRP) itself remounts sdcard and internal memory before wipe process so it will wipe correct memory (only internal memory). If you need to change the ROM you don't need to worry about mounting paths because after wipe mounting paths will be restored to original.
Partition layout of Toshiba Thrive 10.1" ICS
AmEv said:
Also, do NOT use on the Thrive 7 or ANY of the Excites! The Thrive 7 has an entirely different bootloader/partition layout than the 10.
Click to expand...
Click to collapse
Can you give us information on the Toshiba Thrive 10.1" ICS partition layout and their names, please?
We would like to compare it to ours Toshiba Excite Pro (AT10LE-A, tostab12BA). A Dirty Cow enabled KingoRoot has given us a temporary root.
[Q] How Root Toshiba Excite Pro AT10LE-A-108 by dexxxZ
https://forum.xda-developers.com/showthread.php?t=2583677&page=6
Sent from my takee 1 using XDA Labs

Categories

Resources