Related
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
naveen_reloaded said:
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
Click to expand...
Click to collapse
Hi, repartitioning doesnt need to be done with a new rom install.
IF THIS IS A CLEAN INSTALL
you dont HAVE to install it through flashing a new recovery using fastboot
you just need a working newer CWM , or a working TWRP that you can boot
if you can boot to an older Clockwordmod recovery in any form, you can flash a newer version of CWM to the internal by using a zip file , this user has a couple of the newest ones hosted here:
newbtrigger69 said:
https://www.mediafire.com/folder/3j4kxa3bwkrs1/CLOCKWORKMODS <--------------------------------------------- my compilation of a few important CWM versions in case u dont like twrp (like me).
Click to expand...
Click to collapse
after you flash the new recovery, remove the SDcard, power completely down,
press and hold the "N" NOOK button, and hold the power button for just a second or 2 after you see the tablet boot, and you should be prompted for the new recovery that you just flashed.
---
the newer recoveries have an option on the boot menu to start fastboot. So, if you really wanted to follow the instructions to the letter, get or make a working sd card of a newer CWM recovery, boot to it, then as long as your adb/utilities folder on your PC has fastboot in it, you can fastboot the recovery-0.2.img as is in the cm11 thread.
I found I never had to use fastboot before this cm11 install , so I didnt even have the fastboot on my pc side and had to hunt it down.
my first several installs of CM11 were done using an older boot sdcard that had TWRP recovery on it and it works fine.
----
it will probably be a lot easier it you have a working tablet, to have the copied the zips for cm11 and the gapps you want to install to the tablets
internal memory first, before flashing the new recovery internally
---------- (I completely forgot this other possibility, I'm always just doing clean installs)
IF YOU WANT CM to automatically upgrade though the CM updater process on a running CM10
then , yes you need the newer recovery, and it probably is best if it is the recovery-0.2.img the developer posted in the CM11 thread.
I've never tried it so I dont know how well it migrates your "stuff" from CM10 to CM11
theres a lot of changes to the way storage is mounted in CM11 , and the CM updating process is an important thing they are trying to make as seamless as possible.
If theres stuff on the tablet you really need, I'd save it first before doing any kind of major upgrade like this.
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
naveen_reloaded said:
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
Click to expand...
Click to collapse
the latest nightlies of CM11 on a 16GB tablet (has 1GB RAM) are fantastic. best thing ever, especially if you replace the kernel with one that user:demetris has supplied.
I havent run the CM11 on an 8GB (512MB RAM) tablet yet, but it really is a good package.
Its kinda like when Windows 7 came out, its what should have been released instead of XP or Windows 98, its really, really good.
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
naveen_reloaded said:
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
Click to expand...
Click to collapse
hmmm...
Ive seen fastboot on other devices, Kindle Fires, which I think have a motherboard thats a close match to the NOOK tablet.
on the Kindle, you can force fastboot by using a special cable.
if you need fastboot on the NOOK, the recovery program that you execute at boot has to have the option to start fastboot.
you can boot a recovery that has that option from an internal recovery (CWM newer versions have it, I dont remember about older versions)
or you can boot from an SD card you make that boots a CWM recovery
in any scenario, for fastboot to work, you need a working ADB setup and the fastboot program on your PC
------
you can completely install CM11 without replacing the internal recovery partition of your NOOK which is what that fastboot instruction is trying to get you to do.
the special internal recovery, as I understand it, is only for compatability with the automated CM updating process.
you can boot from an SD card that has CWM 6.0.4.x , or TWRP , and as long as the CM 11 nightly is on the SDcard too, or in the NOOK internal memory, you can flash it.
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
naveen_reloaded said:
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
Click to expand...
Click to collapse
--------- assuming you want to update your NOOK's INTERNAL software, and not run CM11 from an SDcard
I apologize had wrong file linked first post
this zip file should be flashable through your current CWM (6MB)
http://www.mediafire.com/download/0f5fjkjvxp1hga0/flashable_CWM_6.0.4.5(2).zip
http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2
it should update your internal recovery to cwm 6.0.4.5
then you should be able to flash the CM11 nightly and gapps without error
--------------------------
a different (I think slightly more dangerous) way to load the newer recovey to your internal was posted here:
http://forum.xda-developers.com/showpost.php?p=48317620&postcount=15
get the newest recovery image file -
File: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-0.2.img
md5sum: e2a87c433171b3d97d852d27aea1ff49
-------
You can install it from a terminal emulator, if you want to.
1. Download the cwm-recovery.img file referenced in the first post of the thread.
2. Copy this file to the internal memory of your Nook Tablet. Rename this file to cwm.img.
3. On your Nook Tablet, launch Android Terminal Emulator (ATE).
4. In ATE, type in 'su' [ENTER]. Grant it access when prompted.
5. In ATE, type in 'cd /emmc' [ENTER]. This will change your file system current directory to /emmc, which corresponds to the internal storage drive.
6. In ATE, type in 'ls' [ENTER]. This will list the contents of the /emmc directory. You should see the cwm.img file you copied over and renamed earlier (step 2).
7. In ATE, type in 'dd if=/emmc/cwm.img of=/dev/block/mmcblk0p3' [ENTER]. This will write the contents of the cwm.img file to partition 3 of device mmcblk0 (internal memory).
You should now be able to reboot and use cwm. CAREFUL, as you could brick your device if you get step 7 wrong.
nvm
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
naveen_reloaded said:
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
Click to expand...
Click to collapse
Great!
re: reboot recovery
you have to unlock developer options first by going into
Settings/ About Tablet / Build Number
and tapping the "build number" field 7 times.
then you see a new settings group "developer options",
and in there is advanced reboot and other things.
---------- Post added at 04:24 AM ---------- Previous post was at 04:21 AM ----------
are you on an 8GB / 512 MB ram, or a 16GB 1GB RAM Nook tablet?
Lol , just found that reboot to recovery , came here to say i found , you already replied.
Installing bexus kernel.
Thanks a lot for your help.
One thing though. The scroll stuttering issue is there . Its as if the screen refresh rate or frames per second is not upto the mark , scrolling is very stuttering.
Is there any way to increase or solve this issue ? Please
this is killing the whole tablet and the purpose i want to use this tablet .. ie to read books.
I use 16Gb/1GB tablet
ok ran into issue
After flashing gapps and installing kernel , i am stuck with andoid.phone stopped working error as soon as the tablet boots.
What is the gapps to be used for CM 11 on tablet and is bexus interfering with the gapps ?
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
naveen_reloaded said:
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
Click to expand...
Click to collapse
I would not enable the multi touch, thats just asking for even more trouble.
I think you should consider a total re wipe , and start over
on a 16GB Nook Tablet, the nightly just by itself should run fine
i just downloaded and opened a 71mb pdf file with no issues whatsoever
opens in Adobe reader just fine, scrolling and zooming and searching is perfectly acceptable, nothing I would describe as a stutter
----
if you HAD enabled the multi touch while you were on CM10, I'd consider reflashing the stock LCD firmware before you put CM11 back on it
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
naveen_reloaded said:
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
Click to expand...
Click to collapse
to me, seeing a white page while adobe pdf loads the next buffer of pages several pagesahead is normal
I dont see anything abnormal while swiping slowly
re: LCD firmware
if you were on CM10, and fashed the 10 point LCD firmware, then I think you would need to rebuild the unit back to CM10, and reflash the stock LCD firmware.
I dont know how to explain , but look carefully when scrolling (slowly) , you will see tests stuttering as its been scrolled .
I am on CM 11 , do you want me to go to CM 10 ? and flash that firmware?
https://play.google.com/store/apps/details?id=com.aatt.fpsm&hl=en
Used this app and saw that fps varies and it varies like from 7 - 50 during reading pdf.
On slow scrolling of pdf , it only shows 11 or so fps , which is why i think shows the stuttering effect
Used the same app on my GS3 to see the difference and it holds its FPS at 60+ and not dropping below 50.
I think if i can make this tablet to render everything at 30+ fps i might not feel this stuttering effect.
Which PDF reader are you using?
I don't have any stuttering issue on the Mantano Reader.
Hi all,
to make it plain and short: I messed up.
I have a GT-S5830i which I unrooted according to the Sticky Note in the forum, installed CWM Recovery and then 'installed from ZIP' a CM9_cooperve_Beta_05.zip that I found in one of the posts in the forum. The installation went on without error message but since then the phone does not make it beyond the initial screen "Samsung Galaxy Ace GT-S5830i". I can start recovery mode and Download mode. In reovery mode I can format cache, data, sdcard, sd-ext but *not* system. Error Message: "E: format_volume: make_ext4fs failed on /dev/block/st19"
I have tried already several methods according to the forum, e.g.
1) 'install from ZIP' older Cyanogenmod
2) the tool ext4_formatter.zip
3) re-flash with ODIN with several tar-ROMs, all failed. Odin finds the phone (since I start Odin as Admin now), but after I hit 'start' it tries to establish a connection to the phone and ends after a while with 'Failed'
I'm basically lost now, don't know what else to do. Any advise is appreciated (it's my mom's phone, she is getting impatient )
Thx, cheers!
Xala
Hi @xalarsk , So you can't format your /system partition , which is required for installation of your rom ,, you need to try this method from here mate . Follow my instruction from the line @post#4 :"1. Download one of the newest ,,," to the end of the post and please do not use CM9 beta , because it is unstable and will wreak havoc with your system eventually . ( either cm7 or cm11 is the place you should go for CyanogenMod experience for cooperVe device ).
If you fail at any level please give us your logcat ( error massage ) for better support for your Odin process you mentioned .
Cygwin not working
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
xalarsk said:
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
Click to expand...
Click to collapse
Cygwin was meant for windows platform to get the native Linux environment/command line you already got there . You can create a virtual instance of the windows 7 inside virtualbox or any kind of apps you are preferring such as Vmware/Parallel etc etc to get the job done .
Splitfus2 only supports windows platform as far as i know mate,,, either vitalization as i said or the pre-made zip package ( which is clearly not .exe file ,, push the download now and get yourself a descent downland manager,, tested and zip packaged delivered ) from here is the feasible approach for your problem .
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
xalarsk said:
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
Click to expand...
Click to collapse
Another fellow had similar issue with my attachment that was corrected here @ post#27
Unbricked, SD card not recognized
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
xalarsk said:
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
Click to expand...
Click to collapse
Mostly this happened because of the bug inside CM9 beta you used . Study this topic mate i troubleshooted while ago for a sample of the symptoms external SD card would show after unstable ICS usage .
Also as an alternative to the method i instructed there , you can format/Re-partition your SD card by putting it inside card reader and using app such as free MiniTool Partition Wizard "Gparted" tool for Linux users Or "iPartiton" for Mac users etc etc ,, to get the job done . You can find several tutorials inside XDA for this matter mate.
Phone works with CM7.2, can I upgrade to CM9?
Hi again,
first of all, props to @ehsanotaku, I will hit the 'Thanks' buttons.
Now, this is a bit beyond the topic, but I'd like to ask anyway for recommendations of CM9 roms. The one I picked from a post inside this forum bricked my phone and made me start this thread, I don't want to go down this road again. So I'd be glad for any recommendation of a stable ROM that will put my phone beyond Android 4.0.
Cheers again,
Xala
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
hojnikb said:
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
Click to expand...
Click to collapse
ok not going to excruciating details of symptoms and explaining all of your errors for now just please read my advice @ post2 of this topic and follow the procedures accordingly and finished it with formatter tools and cm7 instructions you will find there ., after that you can install Kitkat Smart R2 like you are coming from another CM7 build instruction . btw some problem regarding super user privileges and play store 492-498 infamous bug was reported for this fairly new development .
I have had this problem on your ‘assist’ thread for two days now and had 101 views but no reply. I am trying here.
I am trying to put a more advanced rom from your site on to my Samsung 7.7 p6810.
Each time I try to install one I get a Status 7 error.
So far I have tried
lollipop_cm-12.1_20151006-unofficial-p6810.zip
omni-6.0.1_20160115-p6810-homemade.zip
Both have that error.
I started with cwm-20120710-p6810.tar
I thought that twrp might not produce the error so loaded:-
twrp-2.6.3.0-p6810.tar
I am using twrp and that still has the error.
I used Odin3_v3.10.6 to load the cwm and later the twrp.
I copied root.zip to the 7.7 and flashed that with the initially installed CWM
Can some kind soul suggest what I might be doing wrong? I see something about editing scrips in the zip files. I guess I could to that but (a) I am warned it is dangerous if the software is for the wrong machine and that is what I understand a Status 7 signal is saying.
And (b) it is going to be very tedious if I have to edit every new zip file as I experiment with your (nightly) upgrades.
Killing the Status 7 must be the way forward.
However, In desperation I have tried editing those first few lines of the updater script with Notepad ++ but I still get a Status 7 error.
Firstly I am getting no blue line on the TWRP progress bar - whereas I do on the Restore that I have to use rather more often than I would like.
My error message on a file that has those top lines removed from the script says:-
Applyparsedperms ; lstetfilecon of system/lost+found to ubject_r:system_file:s0 failed. Operation not supported on transport set metadata_recursive: some changed failed.
Then the Status 7 msg.
What should I try now, please?
Tony. London UK
I could not resist another try.
I flashed a newer version of TWRP. (Daniels 2.8.7.1) It worked fine as regards making a backup.
I then decided to install one of the errant roms and in the process wiped my whole machine. The right hand wipe button caused the damage. I was then left with a machine that would only produce TWRP.
However, having fiddle around so much over the last three days I guessed that if I used the recovery mode of TWRP it would be seen by my PC. I used Explorer to copy a root.zip, a lollipop zip and a marshmallow zip.
I used TWRP to install the root zip and it worked. I then took a flyer and put on the lollipop that had failed almost two dozen times before. Wowee, it installed.
I could see it was working so I have now put on the marshmallow. OK, I realise the marshmallow is not yet fully developed but I am only using this particular 7.7 to experiment with so that does not matter, yet.
Conclusion. I am not sure whether the newer TWRP is the solution or whether wiping the whole system cleared some rubbish.
Anyway. I am now there.
If anyone looks at this message I would value any comments - and also love to know how I configure a third party rom so it is recognised by google and the playstore. I want to re-install some of my apps and currently playstore does not know who I am.
Tony
Years ago, I installed CyanogenMod onto an old Samsung phone with no trouble. A few weeks back, I was given a Barnes & Noble Nook Tablet 16 GB. The UI is pretty limited and I don't want a B&N account, so I thought I'd unleash the beast and install the full Android OS on it.
I read through various HOWTOs including "Install CM for acclaim" from the CyanogenMod Wiki.
I have formatted an 8 GB SD-card with a single FAT32 partition which has been flagged as bootable.
I downloaded and extracted CWM-based-Recovery v5.5.0.4 to the SD-card.
The device booted to recovery mode OK.
I first tried to install "cm-13.0-20160629-NIGHTLY-acclaim".
It failed with the well known OTA update / Status 7 error.
Reading up on this, the main advice is to try an earlier version, maybe even the last stable release.
I then tried "cm-10.2.1-acclaim" which is from all the way back in 2014.
It failed with just "E: Error in /sdcard/cm-10.2.1-acclaim Status 0.
A web search didn't return anything useful.
Next up, I tried the next release CM11: "cm-11-20140210-SNAPSHOT-M3-acclaim".
I got the same failure as with CM10.
Finally I tired the last snapshot before the latest nightly releases: "cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NI-acclaim"
This time it is back to the Status 7 failure.
Considering all the successful HOWTOs I have read and the procedure is basically the same in each one and I have tried searching these forums.
I can only assume I am missing something really basic.
I checked on whether I need to root the device, as I had to with the old Samsung phone, but it seems the B&N Nook Tablet has root access by default.
So, can someone please help?
Thanks!
alloydog said:
Years ago, I installed CyanogenMod onto an old Samsung phone with no trouble. A few weeks back, I was given a Barnes & Noble Nook Tablet 16 GB. The UI is pretty limited and I don't want a B&N account, so I thought I'd unleash the beast and install the full Android OS on it.
I read through various HOWTOs including "Install CM for acclaim" from the CyanogenMod Wiki.
I have formatted an 8 GB SD-card with a single FAT32 partition which has been flagged as bootable.
I downloaded and extracted CWM-based-Recovery v5.5.0.4 to the SD-card.
The device booted to recovery mode OK.
I first tried to install "cm-13.0-20160629-NIGHTLY-acclaim".
It failed with the well known OTA update / Status 7 error.
Reading up on this, the main advice is to try an earlier version, maybe even the last stable release.
I then tried "cm-10.2.1-acclaim" which is from all the way back in 2014.
It failed with just "E: Error in /sdcard/cm-10.2.1-acclaim Status 0.
A web search didn't return anything useful.
Next up, I tried the next release CM11: "cm-11-20140210-SNAPSHOT-M3-acclaim".
I got the same failure as with CM10.
Finally I tired the last snapshot before the latest nightly releases: "cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NI-acclaim"
This time it is back to the Status 7 failure.
Considering all the successful HOWTOs I have read and the procedure is basically the same in each one and I have tried searching these forums.
I can only assume I am missing something really basic.
I checked on whether I need to root the device, as I had to with the old Samsung phone, but it seems the B&N Nook Tablet has root access by default.
So, can someone please help?
Thanks!
Click to expand...
Click to collapse
The CWM version you are trying to use is too old, I think, even for CM 10.2
Thanks, I thought it might be something like that, but one tutorial said it didn't matter. I have been trying to find a newer version of ClockworkMod, but can only find image (img) files that don't seem to work: I used the gnome-disk-utility 3.10.0, UDisks 2.1.3 to write the image (recovery.img extracted from flashable_CWM_6.0.4.8_chrmhoffmann.zip), but it just makes an empty SD-card - that is, when I check the card with GParted, there are no usable partitions.
I have just found "cm-13.0-20160629-NIGHTLY-acclaim-recovery.img" but I cannot find any clear instructions what to do with it next.
Do I just write the image to the SD-card with the image writer? Because then I get a warning that the target disk is over7 GB bigger than the image and end up with an empty SD-card.
alloydog said:
Thanks, I thought it might be something like that, but one tutorial said it didn't matter. I have been trying to find a newer version of ClockworkMod, but can only find image (img) files that don't seem to work: I used the gnome-disk-utility 3.10.0, UDisks 2.1.3 to write the image (recovery.img extracted from flashable_CWM_6.0.4.8_chrmhoffmann.zip), but it just makes an empty SD-card - that is, when I check the card with GParted, there are no usable partitions.
I have just found "cm-13.0-20160629-NIGHTLY-acclaim-recovery.img" but I cannot find any clear instructions what to do with it next.
Do I just write the image to the SD-card with the image writer? Because then I get a warning that the target disk is over7 GB bigger than the image and end up with an empty SD-card.
Click to expand...
Click to collapse
I can't speak to the CM 13 since I haven't gone there (yet). I followed the excellent instructions by @digixmax for CM 10.2 and (more recently) CM 12.1. In some cases there is no working CWM version and you have to use a version of TWRP. Late in the second thread there are a variety of file combinations people found that worked for them. But the instructions--if followed exactly--work, or at least they did for me.
TWRP worked perfectly for me. However I had to flash CM10.2 before I could go higher, otherwise trying to flash CM13 made TWRP reboot outright with no warnings while on stock. I'm sure since it was on Android 2.3 it needed to have the newer partition table to install to.
Hi,
I've been trying to find a custom recovery for the new Asus Tinkerboard, which is based on a RK3288 chipset, running Android 6.0.1, so I can install zip files from sdcard etc.
The generic CWM 6.0.5.1 by @Oma7144 *almost* works, but it usually hangs after saying can't open /dev/block/...../misc (no such file or directory).
The one time it got past this it gave me the menu option for reboot/install zip etc, but I couldn't move up and down the menu with my USB-attached keyboard.
Does anyone know if there's a later build, or a tinkerboard-specific one anywhere?
Thanks,
Iain
iainfm said:
Hi,
I've been trying to find a custom recovery for the new Asus Tinkerboard, which is based on a RK3288 chipset, running Android 6.0.1, so I can install zip files from sdcard etc.
The generic CWM 6.0.5.1 by @Oma7144 *almost* works, but it usually hangs after saying can't open /dev/block/...../misc (no such file or directory).
The one time it got past this it gave me the menu option for reboot/install zip etc, but I couldn't move up and down the menu with my USB-attached keyboard.
Does anyone know if there's a later build, or a tinkerboard-specific one anywhere?
Thanks,
Iain
Click to expand...
Click to collapse
Hey lain,
Did you solved your problem till now?
i think the big problem is that the Tinker board is not so popolar at the moment and you see this specialy on xda that there are not much to find about it.
I have the TB too and i am actually very active at the Tinker board community Forum but also there are not much solutions for some things i need or want for example bluetooth functions to use it as a headset.
But try your luck there and ask your question.
Greets
Check out TWRP Builder
iainfm said:
Hi,
I've been trying to find a custom recovery for the new Asus Tinkerboard, which is based on a RK3288 chipset, running Android 6.0.1, so I can install zip files from sdcard etc.
The generic CWM 6.0.5.1 by @Oma7144 *almost* works, but it usually hangs after saying can't open /dev/block/...../misc (no such file or directory).
The one time it got past this it gave me the menu option for reboot/install zip etc, but I couldn't move up and down the menu with my USB-attached keyboard.
Does anyone know if there's a later build, or a tinkerboard-specific one anywhere?
Thanks,
Iain
Click to expand...
Click to collapse
They already compiled a working I'm going of TWRP and it can be downloaded thru the site or app. Heads up thou, I have a TB S with 7.1.2 and it would not work, just bootlooped or wouldn't return to recovery at all. Let me know if that works for you, the img number is 630 I believe, just follow the instructions, I already rooted and installed play on mine before doing this
supasleeze said:
They already compiled a working I'm going of TWRP and it can be downloaded thru the site or app. Heads up thou, I have a TB S with 7.1.2 and it would not work, just bootlooped or wouldn't return to recovery at all. Let me know if that works for you, the img number is 630 I believe, just follow the instructions, I already rooted and installed play on mine before doing this
Click to expand...
Click to collapse
had same issue, not sure if mine is s or not, i think it's just the regular TB.
the port poorly ported or it's just intentional anti-leech. if you look in the fstab files, you'll see it...
honestly, the best way would be to port it by yourself. i'm gonna try doing that sometime this month, no guarantees though