Database Info

BL1.1 + BL 1.2 - ClockworkMod Recovery 4.0.1.5

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!

[Q] ClockworkMod Recovery 6 - no sdcard, no internal dirs! Help?

Bear with me, a noob in the woods....
Installed older version of CWM (5.2.8 maybe?) and it worked fine except no access to external sdcard. It did, however, let me browse around the tablet's internal folders and so I could install from there. But... because I wanted to do restores onto an external 8meg sdcard I have (and one I have proven the Asus can write to happily with OS loaded)... I decided to update CWM to ver 6.0.1.2. I did the update via the old version in a recovery session. But now, I get no options at all for directories I can access. Or am I being dense here? the sdcard will not mount and is not accessible. (Even tried reformatting it.)
I would like to install either a version of TWRP or a version of CWM that will let me access both internal directories and external sdcard.
The good news? I can still boot to my EOS (ver 79) customized ver of Jelly Bean. So I have the working OS... just no way to change my Recovery system into something useable. To replace it, it has to work to let me replace it! (Catch 22 big-time.)
Thanks for any help.

[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

TF300TG looking for TWRP with access to external Sdcard

I have a TF300TG, bootloader 10.6.2.11 unlocked with asus tool.
I have tried various TWRP-Versions including 2.6.0.0, 2.6.30, 2.8.5.0. and Kang TWRP 2.8.7.2
2.6.3.0 is not working since it cant mount anything
2.6.0.0, 2.8.5.0, Kang TWRP 2.8.7.2 are working but I have no access to the external sdcard also I have access to the card in the file manager after booting into JB 4.2.1
I would like to know if there is a version of TWRP wich allows me to access my external card and where to download it.
I would love to use it for Backup and recovery.
Thanks in advance for your help
Tom

Paule_Phone said:
I would like to know if there is a version of TWRP wich allows me to access my external card and where to download it.
I would love to use it for Backup and recovery.
Thanks in advance for your help
Tom
Click to expand...
Click to collapse
Please try on your own risk "Kang TWRP [email protected]" https://www.androidfilehost.com/?fid=24052804347781183.
This TWRP is developed especially for TF300T. But it should work with TF33TG as well if you are on the boot loader of the last ASUS stock rom "Jelly Bean".

Thanks ebonit, but no change. No access to external sdcard in Twrp including TWRP File Manager, but access when bootet into JB.
However KangTWRP seems to work, but without access to sdcard. What strikes me is that I have access to the card once bootet into JB 4.2.1
Further hinds welcome

Looks like a very bad SD card, well formated and working in Windows and Android but NOT in TWRP. Problem is solved with new Card.
Thanks for your help.

[ROM][UBIFS][6.0.1]_CM BASED MOKEEOS_R11_Max_MT6572

#________MK60.1-M432-UNOFFICIAL________#
DISCLAIMER
Android 6.0 MokeeOS BETA-001 MK60.1-M432-20190906-UNOFFICIAL.zip designed for UBI + UBIFS R11 max chinaphone board variant Q6_MB_V1.0 only, this software comes on an as is basis with no warranties or gaurantees of any kind.
this is the first ever version of Android 6 for a ubifs device please hit the thanks button if you like my work
SYSTEM INFO
This version of MokeeOS is LineageOS 13.0 source that has been rethemed by the Mokee Open Source Devs this is actual Android 6 and requires stock KK kernel 3.4.67 in order to upgrade
Build compiled from eMMC Micromax A102 HW source replacing everything necessary in order for it to run on UBI + UBIFS blocks using prebuilt kernel & pre modified boot.img containing a storage fix to make 4GB userdata partition through recovery,
FEATURES AND NOTES
• Build comes preloaded with nanogapps_arm_6.0 so no need for gapps installation.
• Build comes pre-rooted with lineageOS root which can be found in developer options.
• Internal storage is system reserved and is user inaccessible, only the sdcard partition is user accessible in which most of your /data is set to be stored so i advise 10GB or more SDcard size.
• you will see a corrupt sdcard in settings under storage this is the ext4 /data partition if you format this you will royally stuff things up so dont do it or youll need to reflash the rom
• you may notice that your device now appears as htc_a16ul or HTC desire 530 in other words this is strictly only to pass googles stupid new device verification this build contains 0% htc sources
• video codecs have been updated but please do note its still a TN display its still horrible but bearable now.
• camera has been interpolated for better camera quality
Clearmotion added to increase the video recordings quality and smooth out the choppy slow video recording
• Bluetooth is using full unmodified micromax drivers from the source if you have problems with it comment
• if you dont want a slow device use a decent class 10 minimum sdcard with a high read write rate, remember this is your /data partition i suggest 16GB minimum or more due to the memory transfer technology controller in the larger cards being much more stable than quite frankly sub standard 8GB class 10 controllers or lower, you get what you pay for dont stinge on the sdcard.
WORKING
• ril (single and dualsim)
• wifi
• bluetooth
• mtp,adb
• secure storage
• basic phone functions
NOT WORKING
• Offline charging animation does not work but still charges.
• Camera cannot capture pictures or video camera crashes this is an app fault use cameringo or footeej
• Screenshots do not work due to internal being currently system reserved and not user accessible
• File manager crashes when first opened after first boot after this is fine but still p**ses me off so will fix when after other major bugs are fixed.
• not a bug but will sit on bootlogo for a minute or two on first boot before triggering the backlight and playing the bootanimation be patient
FLASHING
• RUN A FACTORY RESET WITH YOUR STOCK RECOVERY BEFORE DOING ANYTHING.
• Unzip MMB29M*****.zip and load the scatter file into SP flash tool & flash my recovery.
• Insert a Clas (10) no lower SDcard into the device after flashing.
• Power on to my compiled recovery by holding the power + volume up buttons until the recovery screen displays.
• Go to advanced, select partition SDcard, select 4096MB, i recommend selecting 128MB of swap after as this will compress it into an actual block or ram setting it to 256MB may impede performance.
• Once complete transfer MK60.1-M432-UNOFFICIAL-20190906.zip to the VFAT sdcard partiton by using the second recovery in links below
• Once transferred flash back first recovery go to main menu, select wipe, run a factory reset first, then select wipe all data pre flash,
• Once complete go back to main menu, select mounts you will see a partition under /persist format it so it can wipe the old unused partition and create the persist partition.
• Select mount system after as recovery cannot mount system in script, go back to main menu.
• Select install, then from sdcard, select the .zip and select install,
• You will be greeted with an on screen aroma- installer i repurposed from 2012 which has been completely re written and Mokee themed by me, follow the steps on screen & wait for install to finish.
• Flash the boot.img patch straight after the flashing the rom.zip
• Reboot no need to wipe cache or dalvik
Welcome to Android 6 Via MokeeOS/LineageOS
#________________LINKS__________________#
Recovery for flashing MokeeOS UPDATED
https://drive.google.com/file/d/1vggA-qFjsej2BdacsHUqnFOBx-izrCzK/view?usp=drivesdk
Recovery for transfering rom to sdcard as usb daemon dosent work on above recovery
https://drive.google.com/file/d/1Xv49Qr9cZtH18EtkYwLO5NNcFrTvUtLh/view?usp=drivesdk
BETA-001
MOKEE MK60.1-M432-UNOFFICIAL-20190906
https://drive.google.com/file/d/1CTYHHmefFesOHAIwfb8eF_2QBgeZDp6G/view?usp=drivesdk
[PATCH] BOOTIMG 2019-09-10 patches will be merged with the next update so you wont have to flash a patch.
https://drive.google.com/file/d/1SWn6JAzCynwlub8NGBCZ6VrdGs1nC42_/view?usp=drivesdk

hi Matty
I receive an error message when I try to flash your recovery. ERROR: S_INVALID_ARGUMENTS (1002)

SiXtyNiNe said:
hi Matty
I receive an error message when I try to flash your recovery. ERROR: S_INVALID_ARGUMENTS (1002)
Click to expand...
Click to collapse
I just checked recovery and scatter on my end all is working properly,
What version of SP flash tool are you using also Are you taking the battery out and reinserting before connecting to the pc for flash thats an important one or youll get flash erros You could also try to rename the recovery file to recovery.img instead of it having a default of no file extension but i cant see that being the problem,.
If you still get the problem use the scatter file from cyanogenmod 11 rom partitions are the same as same device

Matty1993 said:
I just checked recovery and scatter on my end all is working properly,
What version of SP flash tool are you using also Are you taking the battery out and reinserting before connecting to the pc for flash thats an important one or youll get flash erros You could also try to rename the recovery file to recovery.img instead of it having a default of no file extension but i cant see that being the problem,.
If you still get the problem use the scatter file from cyanogenmod 11 rom partitions are the same as same device
Click to expand...
Click to collapse
my newly updated version is 5.1916.00 but the same did not work. now I flashed the recovery only, with the scatter file contained in the cyanogenmod 11 and it worked. I'll go ahead I'll let you know

SiXtyNiNe said:
my newly updated version is 5.1916.00 but the same did not work. now I flashed the recovery only, with the scatter file contained in the cyanogenmod 11 and it worked. I'll go ahead I'll let you know
Click to expand...
Click to collapse
Hey mate sorry for late reply im on australian time,
Cool glad it worked out for you ill edit the .zip and reupload with a new scatter for everyone else,
Ill be uploading a boot.img patch aswell as i forgot to take a voldmanaged path out in the fstab so you may of gotten stuck on the starting apps screen boot patch will be up soon im on it now

Links have been updated and have added a second recovery to transfer the .zip to sdcard as the usb storage daemon seems kaput on the installation recovery,
Boot.img patch has been provided flash straight after installing mokeeOS

Pictures of build

Matty1993 said:
Hey mate sorry for late reply im on australian time,
Cool glad it worked out for you ill edit the .zip and reupload with a new scatter for everyone else,
Ill be uploading a boot.img patch aswell as i forgot to take a voldmanaged path out in the fstab so you may of gotten stuck on the starting apps screen boot patch will be up soon im on it now
Click to expand...
Click to collapse
Thanks for your help! for now I have only loaded the recovery, because I did not have time to flash the firmware inside. I will try Monday morning because I am away from home ... again thank you so much.

hi Matty ...the phone is stuck at the "starting apps". ok I realized now that I need to install the patch...

ok all done after new flash. Everything seems to work but everything seems a little slow for now ... and anyway I always have the problem of absence of imei. is there the possibility of being able to rewrite it in the Vnand?

SiXtyNiNe said:
ok all done after new flash. Everything seems to work but everything seems a little slow for now ... and anyway I always have the problem of absence of imei. is there the possibility of being able to rewrite it in the Vnand?
Click to expand...
Click to collapse
Hey mate,
Sorry for late reply just seen your comment
Yeah mokee is deffo a bit slower than my CM builds you should of seen it before i made all the swap changes and tweaks to it though that was slow lol but if you logged into your google account at the setupwiz it may run somewhat slow for a little bit as it will be downloading and applying updates to google applications, if this is the case usually leaving it for half hour to download and apply updates then rebooting it to apply the changes usually does the trick.
And still no imei ?? thats odd all needed files to rewrite the imei for new build are contained in sec files and are flashed straight after permissions are set,
Ill take another look at the boot.img's initrd and add all the protect info into a singular init. File and set it to be imported instead of adding the protect info manually to each init at its designated stages and ill upload once done this should fix the issue hopefully.
Ive nearly gotten just normal LineageOS 13.0 working properly for release also finally got internal storage mounted now after emulating it just need to work out external storage mounting for external storage but if i cant figure that out ill just release it anyway as beta build as its still completely useable as it is and is much much faster than mokee from my beta testing today on the device so fingers crossed
Anyhow ill let you know once the new boot patch is up so we can hopefully get your rild and nvd working again.

New patch is up in the links on the OP
i corrupted my imei just to to make sure the patch will work for you and is all good should restore nvd no problemo now and give you back your imei number
if flashing just the patch dosent work factory reset then format system and reflash the rom then the patch but you shouldnt need to do all that tho
Also fixed is MTP, ADB & Secure Storage which is set to hold the encrypted data on the external storage

thank you so much for your support you are great! ... I try the procedure even if I missed a bit on the steps, I don't understand what I have to do first and what I have to do then ... anyway I try.
---------- Post added at 01:46 PM ---------- Previous post was at 01:17 PM ----------
for flahing the rom what recovery should I use? first or second?

I flash new and I have new imei! ...but something wrong because the phone tells me that the sd card is damaged, if the phone format the message fades, but anyway there is not in the mem section. and the internal memory is very little.
---------- Post added at 03:03 PM ---------- Previous post was at 02:58 PM ----------
P.S.
the camera does not work. probably due to the sd card problem.
And if I switch off the phone it won't start up anymore! there is something wrong with my steps

SiXtyNiNe said:
I flash new and I have new imei! ...but something wrong because the phone tells me that the sd card is damaged, if the phone format the message fades, but anyway there is not in the mem section. and the internal memory is very little.
---------- Post added at 03:03 PM ---------- Previous post was at 02:58 PM ----------
P.S.
the camera does not work. probably due to the sd card problem.
And if I switch off the phone it won't start up anymore! there is something wrong with my steps
Click to expand...
Click to collapse
The damaged sdcard isnt actually damaged as per is explained in the OP the system is only saying its damaged as its expecting the sdcard to be in vfat partition format but as /data is now on the sdcard as ext4 this is why it states that,
Camera dosent work also as explained in the OP has something to do with the app download cameringo,
If you formated the sdcard then you will need to reflash the rom again or it wont boot back up as you wiped the ext4 partition from the sdcard, so partition the sdcard through recovery again then re install the .zip then the patch and remember dont format the sdcard or as per OP things will go very wrong,
Been looking for the flag that controls that message to have it not show up if i cant be othered looking for it i may just add a prop to disable it in the build file on next update strange though i have to say my LineageOS 13 build doesnt display the message but yet both are lineageos 13 source,
Glad the imei is back now though youll have a useable phone once you do my steps above

hey friend thanks! I'm having fun with your work ... ok now I understand that I don't have to format the sd card ... but is it normal that the phone then only sees the little internal memory left? then I don't understand the sixth step ... (Once complete transfer MK60.1-M432-UNOFFICIAL-20190906.zip to the VFAT sdcard partiton by using the second recovery in links below) why do I have to use the other recovery?

SiXtyNiNe said:
hey friend thanks! I'm having fun with your work ... ok now I understand that I don't have to format the sd card ... but is it normal that the phone then only sees the little internal memory left? then I don't understand the sixth step ... (Once complete transfer MK60.1-M432-UNOFFICIAL-20190906.zip to the VFAT sdcard partiton by using the second recovery in links below) why do I have to use the other recovery?
Click to expand...
Click to collapse
You should see that your /data partition in your settings under storage should be 3.7 - 3.9GB
the system will state that there is not enough memory for some things as internal isnt mounted under internal when the apps expect them to be internal
i had to repath all internal stuff to be stored on external storage hence how i got secure storage to be set to sdcard1 which is external storage also and both are vfat so was only thing i could really do atm i as i cant mount both internal and external storage as they both wont show up if i do
and i cant set just normal internal storage for use or the camera and gallery apps and what not that rely on external storage wont work,
hence why i megered everything to be set to the bigger partition, if you can see my dilema storage is tricky with these devices am trying to work out storage paths and symlinks to mount both but so far no such success as of yet ive managed to merge all storage asserts to a singular init so its easier for me to work with so i can get it to hopefully mount both sooner or later

hi matty. I have this situation right now (picture in attachment) but I can't install any apps. all stuck on download. and even putting the files on Vfat from PC, when I install everything it remains locked on "install". then if I open a download link from the browser, I have a message that says I don't have a sd card inserted.

SiXtyNiNe said:
hi matty. I have this situation right now (picture in attachment) but I can't install any apps. all stuck on download. and even putting the files on Vfat from PC, when I install everything it remains locked on "install". then if I open a download link from the browser, I have a message that says I don't have a sd card inserted.
Click to expand...
Click to collapse
Downloads files from browser and apps from play store on my end perfectly fine so thats strange...
Your data looks ok and is mounted and the system is recognising that the sdcard as mounted and in use from what disk info is showing also so not sure on why its not recognising theres no external storage available when thats the storage path i used for external and also merged for internal
Ill have another look into it see if i cant re create the issue to get it solved for you anyway
If i cant get it fixed on your end ive got an unreleased version of cyanogenmod 12.1 which is android 5.1 i also compiled for our Q6_MB_V1.0 but never released as id gotten a 6.0 build working the next day so if i cant fix storage on this then ill try om that as storage changes are differnt and more close to 4.4 varying some minor changes so will be easier to mount both until i get LineageOS 13.0 external storage fixed as its quite tricky with all the differnt partitiion fs's from /system which is UBIFS (unsorted block image file system) + UBI (unsorted block image) that ubifs sits on in which UBI also sits on its MTD flash media transition layer, then /cache is yaffs2 coverted from ubifs using the old [email protected] block with swap added and /data is now emmc ext4 format using a partition on the sdcard,
Mounting system so things would boot was the main problem i faced but as /data is on the emmc external card getting it to properly mount through fstab via vold is quite tricky as the system path is
/dev/block/platform/mtk-msdc.1/mmcblk0 with also 0p1 0p2 and a 288mb 0p3 i also made for the next update but if i use in the fstab
/devices/platform/mtk-msdc.1/mmc0/mmc* with
Voldmanaged=sdcard0,auto,emulatedsd it wont mount internal and stops mountinf sdcard1 which also uses /devices/platform/mtk-msdc.1 you probably dont understand all this but ill get there with it eventually i spent 2 years already learning everything about ubifs to build these newer versions of android as before i released this the only version of android to be found for a ubifs device was 4.4.2 KK which has major security flaws so i wont be quitting on it any time soon

# UPDATES
MokeeOS Updates have been held back for the coming week or two as i have far to many projects on the go and am now using windows based software to recompile for updates as my linux rig is dead your patience is appreciated.
My new LineageOS 13.0 build will be released in the coming days for everyone instead luckily i could pump that out before the rig blew
I can confirm that as of sunday both internal & External storage are now working properly on 13.0 and are mounted and user accessible,
appropriate performance tweaks have also been made for the device hardware.
All i need to do now is fix the camera and link will be posted here to the new thread.
Thanks