I am looking to port a custom ROM to the Blu Dash 5.5 a Mediatek 6582 device, any suggestions?
TD378
Any answers???
Sent from my N9521 using Tapatalk
No answer so started to port one on my own. Got the ROM to boot after several changes to original. Still have a few issues to work out.
TD378
Any progress???
Sent from my N9521 using Tapatalk
Have to fix camera and Bluetooth issues.
TD378
Please keep me updated on your progress.Thanks!!!
Sent from my N9521 using Tapatalk
Hi, I´ve ported a rom for BluDash 5.5 based on Resurrection, just let me know if someone want for share
Few questions about your port...
1: Is the default camera working properly?
2: Are you able to connect to any Bluetooth device?
3: When you reboot the device, are any manual changes you make kept? Example. Background, icons, etc?
I have created multiple boot animations and logos for this device. I have a variant of CM 12.1 but the issues I asked above are preventing me from posting everything.
Any input will be appreciated.
TD378
Rom Ported Blu Dash 5.5
Hi, well, I've ported this rom keeping in mind that I have not found no one a custom rom across the web, phone is not mine but I behaved for someone and the reason is that the original rom already had problems with the length battery charging and then booting, he stayed in the logo and the last time no longer started, I clarify that I am not a developer, I'm just an enthusiast and my english is very bad.
Consider the following points; Of 12 roms that I ported these have different bugs would therefore be better not to share, this rom is lightweight and has good length battery, I think it is based on cm but not sure, the native camera works well, just need SD card, bluetooth working properly, it boots normal, there is nothing to set back, known bug; when connected to the PC does not recognize internal memory but yes SD, I think it is a minor problem, give it a day to stabilize better, I used recovery Philz Touch, anyway if someone wants to improve it you feel free to do so, it's for Blu Dash 5.5 firmware D470u but I think that rolls in others.
Is the ROM good for everyday use?
It seems you ported it somehow to run of the sdcard not internal memory. Are you able to use both internal memory and sdcard?
TD378
ROM is not ported with propose of run from SD card, probably characteristics from origin, phone runs properly almost twenty days without major probs, I think is good for a day use, of fact it haven't a SD card inside, runs without it
What are the minor issue you have with current port? They may help me with my port.
TD378
TechDad378 said:
What are the minor issue you have with current port? They may help me with my port.
TD378
Click to expand...
Click to collapse
Well, minor issues are;
- Some apps like Memo from Chensi ask for SD card but others like Colornote not, I think that for some reason some apps can't read internal memory.
- when a notification is on status bar I displayed to down scrollbar but at third or fourth time it's unable.
- When connected to pc don't appear internal memory but yes SD card.
I didn't see more issues, probably few errors from porting, considering that 2 of these issues keep relation with internal memory
The screen on my device cracked causing it to no longer be useful. If anyone wishes to continue work on this rom, please let me know and I will provide you the information I have completed.
Please how do i install a custom recovery on my blu dash 5.5? because i've searched and can't find any.
solozeeh said:
Please how do i install a custom recovery on my blu dash 5.5? because i've searched and can't find any.
Click to expand...
Click to collapse
This link used for root...
https://forum.xda-developers.com/showthread.php?t=1982587
This link for recovery...
https://forum.xda-developers.com/showthread.php?t=2748169
Follow the tuts. Hope that helps!
TD378
Divided we stall
United we install
solozeeh said:
Please how do i install a custom recovery on my blu dash 5.5? because i've searched and can't find any.
Click to expand...
Click to collapse
Tomorrow I will upload and suppose that you don't have a custom rom or are you ok with stock rom?
solozeeh said:
Please how do i install a custom recovery on my blu dash 5.5? because i've searched and can't find any.
Click to expand...
Click to collapse
First extract this zip in desktop, download SP FlashTool for mediatek, extract it and open, click on scatter-loading and navigate to your unzipped folder till "MT6582_Android_scatter.txt", turn off device, connect terminal usb first only to pc, click on "Download" button in SP FlashTool and now connnect to device, process will take just a few seconds, close programm, disconnect device and go to recovery holding volume up and power at same time till appears a menu with 3 options (recovery, fastboot and reboot normal), rapidly release power button and select recovery navigating with vol+, it´s done
What recovery did you use with your upload?
TD378
Divided we stall
United we install
It's a ported recovery from other mt6582
Related
Hello,
Last night, I tried to modify the Screen DPI on my tablet ASD Digital MID 162... After the device restart, splash screen not ending... I reset my build.prop to the default value, and make a wipe cache with Adb and instead of write wipe /cache, I write wipe only... And my device don't boot and I can't use adb shell... The error is : "Permission denied (13)"
Someonee can help me ? Please ><
(Sorry for my bad english, I'm french)
How did you modify the DPI exactly?
Through an app?
Editing the build.prop?
Laughing at you while eating Jellybeans
Sounds like a messed up build prop and the device is bricked..
Yes I've modify the DPI in build.prop file...
What can I do for repair the boot ?
One help ?
Gonna have to reflash. You pretty much wiped your device so you will need to reinstall the os
Wayne Tech S-III
I know that, I have to reinstall the OS.. But I don't have recovery mod on my tablet... The only one I have it's an recovery stock (I think, I'm not sure).. I can do "adb ls/", "adb pull and push" , that's all... One idea ?
[I've tried to push a shell in /system/bin in recovery mode, but I've got a error (permission denied), I want to push a shell for execute "flash_image" tools with an new OS .img file for solve the problem ]
I've had similar problems with my myTouch when I've done things it didn't like. Providing that you can boot to the stock recovery that gives you the options to reboot or apply update then your almost saved. Because if that's the case then ya can
copy the custom recovery.zip file over to the root of your sdcard (I used a computer for that as when I killed my phone it wouldn't boot past sock recovery or boot-looping)
rename it to update.zip then boot into stock recovery,
apply the update from sd and your device should, hopefully, temporarily start the custom recovery so that you can
wipe re-flash or restore from backup.
This all assumes that your device has a way for you to access the sdcard without your device.
Hope this helps/use at your own risk
Sent from either my SPH-D700 or myTouch3Gs
I go to make a meditation on this idea... The problem is that I can't do anythings with the "stock recovery", It's just a screen with an open [dead] droid with red exclamation mark, and that's all. Nothing to do when I push one touch like Volume - or +, but when I boot with another key as Power Up, A black screen appeared, and it's all... (I want to show a photo with a screenshot, but I'm a new user, I can't :'( , I've no luck !!!! >< )
SteakFrite said:
I go to make a meditation on this idea... The problem is that I can't do anythings with the "stock recovery", It's just a screen with an open [dead] droid with red exclamation mark, and that's all. Nothing to do when I push one touch like Volume - or +, but when I boot with another key as Power Up, A black screen appeared, and it's all... (I want to show a photo with a screenshot, but I'm a new user, I can't :'( , I've no luck !!!! >< )
Click to expand...
Click to collapse
That is not recovery that is the kernel panic screen. Only option is an Odin install of stock
SteakFrite said:
I go to make a meditation on this idea... The problem is that I can't do anythings with the "stock recovery", It's just a screen with an open [dead] droid with red exclamation mark, and that's all. Nothing to do when I push one touch like Volume - or +, but when I boot with another key as Power Up, A black screen appeared, and it's all... (I want to show a photo with a screenshot, but I'm a new user, I can't :'( , I've no luck !!!! >< )
Click to expand...
Click to collapse
Ok so I read the post about kernel panic screen and agree mostly, however, I've seen the panic screen and gotten past it with a combo of volume + and power button at the same time, it then returns an error message on how recovery wasn't able to be read from its expected source, it then blanks out for a moment and boots the stock recovery, from there I apply the update.zip that I renamed and placed there with a computer, and then everything is good again.
Note: I don't have the specific device you do, or know the method that you usually used to use to boot into recovery.
Usually, its a combo of two or three buttons like on my htc product it's volume up and power button and on my Samsung its volume down and power and camera button. Note: when I do actually get into a custom recovery on my htc the power button then changes to turning the screen off and on instead of selecting things, which made it a hair pulling experience until I figured out that the directional pad on my device was the select button. (Moral of the story, power button sometimes controls the power to the screen, sometimes its used for selecting things, odd but be persistent and try combos because I thought my phone was killed till I hit the power button a second time and the screen came right back on.)
Odin should resolve the issue though for sure if fiddling around with your devices' buttons get to be frustrating, I just figure that any time I touch a computer to re-root my phone I've not done enough trouble shooting.
One other thing you can try is a targeted google search
Eg: 'solved [device name] [issue with device] site:[address of site to search]
So for example when I had a problem with my Samsung I used
'Solved epic 4g bootloop site:xda
Note I had to shorten the site as I'm not allowed just yet to post links but you'll want to include the .com
You can also replace the site: with similar: to search sites that are like xda with similar results.
What's the name and manufacture of your device? I'll see what I can dig up for you.
Sent from either my SPH-D700 or myTouch3Gs
Good ! Thank's youuuuu !! I've can access recovery mod with combo of Volume + and Power... My device is "ASD Digital 162"... Tonight, I go to make an update.zip with an android OS img file... Thank's !!
Where I can find an image file of my Rom ?
This device don't have many popularity on google, and he have no constructor website... Where can I find a ROM or Custom Rom ?
For information, I've one another tablet (Exactely same device) arround of me.. Can I extract the ROM or a backup that could me restore the Android OS ? I don't want do stupid things with the other tablet also like I do this time...
(I want to precise... On my SdCard, a folder named "nandroid" has apparead , he content kernel file, system .img file, cache .img file, etc etc.., if you have any suggest on what can I do with it )
SteakFrite said:
This device don't have many popularity on google, and he have no constructor website... Where can I find a ROM or Custom Rom ?
Click to expand...
Click to collapse
I'll be seeing what I can dig up in the next day or so. Have you any links to shair; such as the guide(s) you've used?
SteakFrite said:
For information, I've one another tablet (Exactely same device) arround of me.. Can I extract the ROM or a backup that could me restore the Android OS ? I don't want do stupid things with the other tablet also like I do this time...
Click to expand...
Click to collapse
You could try it, though I wouldn't as internal hardware can differ inside identical devices, you could end up 'super' bricking your device which I don't think is a real term it just sounds less scary than 'muten' bricking. The phonomonon can be observed when someone flashes an epic 4g touch rom on to an epic 4g and things are never the same. Not saying that's the case just my perinoa speeking up here.
Actually I think there are guides floting around on how to make and scrub your own custom rom, maybe you could do a full copy of the working device though the usb debug bridge, scrub the user data and dependencies from the copy and push it to the not-yet working device... or you could blase the path allready well troden.
SteakFrite;40339439 said:
(I want to precise... On my SdCard, a folder named "nandroid" has apparead , he content kernel file, system .img file, cache .img file, etc etc.., if you have any suggest on what can I do with it )
Click to expand...
Click to collapse
now when you're going to your sd card are you talking removable sd or internal?
Some devices don't have an external or its inaccessible,
other devices make it confusing by also having a partition on the internall memory labled sdcard which looks a lot like the sd card that can be un mounted and re mounted (I believe it to be confusing because the sdcard is also lables sdcard),
And yet others are really easy to spot because its the only thing labled and removeable as an sdcard
Any who if your talking about viewing your sdcard with prisice then likely what your viewing is the old contents of the card (what ever you had on it before this learning experieance snuck up on you) and I would treat it like pizza from last night's party. Meaning that the backed up apps could be used and there could very well be a good backup in there if you made one in the before time, but I wouldn't force my device to choke down leftovers when I could start anew.
SteakFrite said:
Good ! Thank's youuuuu !! I've can access recovery mod with combo of Volume + and Power... My device is "ASD Digital 162"... Tonight, I go to make an update.zip with an android OS img file... Thank's !!
Click to expand...
Click to collapse
You're Welcome; knew you weren't out of options.
Make sure to reroot from the start of what ever guide you used (as a gard against myself and the decisions I make I always keep my costom recovery flash zip for all my devices in the root of my sdcard and labled as update.zip or whatever the manufacture's recovery software by defaults to looking for. That way I can always reinstall if the device still turns on.) as you'll likely want to flash and mod with furver, I know I always do, keep a clear head and it should all work out.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
...
It's a external sd card... And the file and folder are lost.
Exist an universal Custom ROM Android 4.2 ? I didn't found any official rom for this tablet...
SteakFrite said:
It's a external sd card... And the file and folder are lost.
Exist an universal Custom ROM Android 4.2 ? I didn't found any official rom for this tablet...
Click to expand...
Click to collapse
Yeah just spent the last hour or so looking for asd mid 162 tablet in google, tried a few modifide search quaries, and such to no avail. Saw your question on a few other boards too. I've a feeling that you've run into the same problem with low popularity and lack of documentation. If you got any other discripters I can use for searching I'll be back on the case after work today
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
S0AndS0 said:
Yeah just spent the last hour or so looking for asd mid 162 tablet in google, tried a few modifide search quaries, and such to no avail. Saw your question on a few other boards too. I've a feeling that you've run into the same problem with low popularity and lack of documentation. If you got any other discripters I can use for searching I'll be back on the case after work today
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
Click to expand...
Click to collapse
On recovery screen, is marked "SDK : MID-A13-Android4.2-V1.0-20130121"...
This tablet is the 9' inch model of ASD Digital 142...
Looks like that's the rom, could try flashing it again, just google the 'a13 9 inch tablet' and you'll find info on allwinner.
Happen to know what the ASD stands for? All I'm getting is autism results. (Which putting the word autism in this thread and adding '[minus sine]autism' might help)
Sent from either my SPH-D700 or myTouch3Gs
I haven't understand...
I don't understand what you say... :/
Can you use easiest word or terms ? (If possible)
Sorry about that.
The first part of last post was discribing a search quary I used to find info on the rom you may be using. Looks like a cross platform compatible rom on the face of it but I'm still looking into it.
The second part of last post was stating that when I search for your devices' model 'asd digital' I'm getting results for human medical problems and not hardware related information. So I put the main word that was triggering that into this thread so that I can then search 'asd digital -autizem' and cut those results automaticly from the google search results.
Still working on this with you, just have split atention with trying to finish my first guide for android/linux dulebooting (unrelated to the issuess that curently plage you but still may be worth a look at when you've a system up and running again.)
At this point doing a restore from a working device's backup like you where saying might be the best bet on reviving the simi-bricked device, but I'll have to do some more reading before I really feel comfortible sugesting that you go though all that.
Now that you where able to boot a recovery screen; have you tried anything to get it back up and running? Such as restoring from a backup created after rooting the first time around?
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
link to guide for Debian Kit I'm working on for you.
https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=sharing
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.
Please excuse asking questions as a first post, but I'm at the stage where I'm stumped and a search isn't helping.
Mlais MX28 fresh from MM pre-rooted. Managed to get the ROM backed up and CWM installed with Rua1's excellent MTK Droid Root & Tools. However, removing the Chinese useless (for me - no offence intended) apks proved not to be happening from the one-click button in that excellent piece of software. No bother, thought I, I'll just use adb and remove the relevant apks manually from /system/app. Famous last words.
Here's where things get really odd. I can mount root fine using the usual procedure but mount -o rw,remount /[email protected] /system works once and once only. Even stranger is that the first time gets you a rw mounted filesystem for about 10 seconds, at which point it gets remounted ro and no amount of faff will get it back to rw without a full power off and restart. All it does is spits out
Code:
mount: Read-only file system
Any ideas, please? I suspect there's some write protection going on but I haven't the first idea where to look.
Edit: Having done a little more searching on this issue, it seems there's a few Acers with the same behaviour, caused by a compiled-in kernel option. Looks like it may well be "wait for a custom ROM" is the answer. Not sure if rolling our own is possible unless anyone knows where to get the Mediatek sources for this device from?
Anyway, :good: to all those who have viewed my question. It's appreciated.
Edit 2: There's an S4UI ROM on needrom<dot>com that is rumoured to have solved this issue. Note that if you have installed CWM using the "magic" MTK Droid Root & Tools method, chances are you can't mount /system rw using ADB in CWM either - I suspect they share the same kernel. I haven't tried the S4UI ROM myself as the recovery needed to install it seems to be in Chinese. Possible solution for anyone with a grasp of that language and script but that someone isn't me
[Q] Mlais MX28 Recovery in Chinese Any help with translation
Hello, bud Any help yet also gut stuck in this.
I'm afraid not at the moment. The S4UI ROM on needrom does indeed enable /system rw but the WiFi and Bluetooth will not activate. Replacing mtk_stp_wmt.ko in /system/lib/modules/ with the version from the stock ROM that should fix this issue, doesn't fix this issue. It's a shame as the S4UI ROM is rather pleasant to use and if I could get that fully operational I expect I would be quite happy with this device. Oddly, the stock ROM came back with a different MAC for the WiFi. As I restored from a backup created with MTKDR&T, this is a little perplexing.
I'll update if I find any more clues.
{Possible solution/nasty hack]
Here's a way to get full /system access on the stock ROM. It requires
Clockwork Mod recovery
ADB
Courage
Install/create Clockwork Mod with MTKDR&T. Now boot into recovery by holding Vol+ and power until the boot selection screen appears and then select recovery with Vol+ and press Vol- to accept.
Do not mount /system in CWM.
On your ADB equipped computer, start
Code:
adb shell
Now issue the following at the root shell prompt:
Code:
tune2fs -e continue /dev/block/mmcblk0p5
Reboot the system and enjoy the power of full root.
This may well be a nasty hack. I was convinced the issue was a protected kernel module but it seems the ext4fs image of the system block is corrupt in some way and the default error action is to mount -o ro. We're disabling that default action and letting the mount remain unchanged.
As always with these things, proceed at your own risk. If you break it, you have the privilege of keeping both bits.
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
codedmax said:
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
Click to expand...
Click to collapse
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Chron0s said:
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Click to expand...
Click to collapse
Very Well concerned,
once again good job, but how do i go about implementing this,
would you be kind enough to put in some more details on the file system code and CWM flashing with MTK Droid root & Tool did you manage to get a translation on the chinese langauage recovery problem,
(a tutorial is just fine) Thanks alot bud.
Okay, give me a little time to set it all up for screenshots as I don't generally use Windows unless I have to. It's all fairly straightforward. The CWM installation is four clicks and some waiting and repairing the /system block is a couple of commands.
Oscarblue48 has a tutorial on installing CWM on Mediatek devices here or here if your MX28 isn't rooted which is the procedure I followed. Then it's just a case of booting into CWM, connecting your device to USB and using adb's shell to fsck the filesystem on that block.
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
codedmax said:
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
Click to expand...
Click to collapse
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Chron0s said:
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Click to expand...
Click to collapse
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times.
As with most mtk gps can not finding a lock in hows it with your device.
codedmax said:
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
Click to expand...
Click to collapse
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
codedmax said:
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times. As with most mtk gps can not finding a lock in hows it with your device.
Click to expand...
Click to collapse
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Chron0s said:
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Click to expand...
Click to collapse
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
codedmax said:
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
Click to expand...
Click to collapse
Good stuff. Once you have the gps.conf set up, try using Mobileuncle Tools to pull in the EPO (extended prediction orbit, basically a nice big list of keplers for the satellites so it knows which to expect to be in view at a given time without having to scan the sky for what's actually there) data which should stabilise the GPS even further.
codedmax said:
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Click to expand...
Click to collapse
I wonder if it's the bodged Trebuchet they're using? It's a bit of a disaster as they've taken the CM launcher, bodged bits of MIUI into it and given the whole thing a "that'll do" look and feel. I replaced it with the real Trebuchet after a thorough decrapify, along with the AOSP stock keyboard. There's a "modified" apk of Trebuchet (all the dev did was lower the base API level so it would install on 4.1) floating about on the 'net somewhere. The various KitKat-alikes work fairly well but I wanted something open source that I could slam into /system/app without worrying.
It has taken a lot of faff to get to this stage but I now have a very usable and fast device for not a great deal of outlay.
gordo100 said:
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
Click to expand...
Click to collapse
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Chron0s said:
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Click to expand...
Click to collapse
Many thanks for your help. I have a back up of my mlais, i have a back up with mtk droid and tools 2.5.3 ( new version ), but when i put it on the flash tools, the cache and user is missing, and it´s imposible to download it. and then i put a recovery CWM on the mlais with droid and tools ( very easy ), and use a nandroid back up, it´s no problem, but the internal sd partition is always changed : 1 gb for apps and 1.75 for sd internal, i´m very sad because i would like back to the 2,3 gb for apps ( original partition )
Yes... always fat32 sd cards of course, but i have problems with the sd up to 8 gb, the mlais freeze, or sd desmount ( it´s imposible sometimes write in sd external ) i don´t find the problem with this... i have the rom stock : 115.
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Many thanks for your help !
gordo100 said:
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Click to expand...
Click to collapse
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Chron0s said:
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Click to expand...
Click to collapse
Many thanks Chronos!, The problem is also with the official ROMS on mlais.com/mlaismx28 i don´t understand it...
Please i need help to back restore the partitions of my sd internal ( ROM ), i would like back to 2,3 gb for apps, actually i have only 0,98 gb and 1,75 gb internal store.
I think that the solution is back up for flash tools and reflash with the rom stock ( the back up of mlais mx28 of my friend, he have other new mx28 )
But my BIG problem with the flash with flash tools is the USER DATA and CACHE is always empty, and then it´s imposible to reflash it it´s always and error : Rom changed PTM ...
Please, what can i do for have USER DATA and CACHE with mtk droid and tools 2.5.3 versión?? ( in this version to click User data and Cache with to do the back it´s imposible, this option is missing in 2.5.3. version )
http://dl.xda-developers.com/attachdl/b2f11c741aab592a8f66616d932af983/533c2dcc/2/6/6/4/5/2/2/Sin_t_tulo.jpg
[ROM] Official Update
Hello guys, there's a new rom update for the mx28
Official Mlais MX28 version: Mlais_MX28_20140312
www.needrom.com/mobile/mlais-mx28-2/
Try it out seems, it works perfect.
Cheers!!
I WANT TO START OFF BY SAYING THAT THIS IS THE FIRST TIME I HAVE MADE A THREAD ON THIS SITE.
I FEEL MY ISSUE IS UNIQUE AND ALL HELP WILL BE MUCH APPRECIATED. THANK YOU
Click to expand...
Click to collapse
The tablet that I am dealing with is a "Cruz Velocity Mini Tablet" running android 2.0 and no means of installing apk's.
Currently this is the situation:
A friend of mine lent me her Chinese reader tablet.
I told her that I could probably flash a newer version of Android on it, thinking that I could finally try my hand at making a ROM because I know for a fact that there aren't many ROMs if any at all out there for a chinese off brand reader like this.
After rooting the tablet I deleted the pre installed bloatware via ADB commands (shell) including a file manager (Astro) that I believe was the only way that you could browse files on the tablet, as well as some other pre installed applications that must have been necessary in retrospect. There is no existing vending capability or market application.
I am looking to make a custom ROM (Using android Kitchen and Cywign) through following this tutorial by lokeshsaini94 yet I feel like following that tutorial won't even get me where I need to be.
Click to expand...
Click to collapse
Things that I have tried at this point include:
Attempting to connect the tablet to my computer with the SD inserted (with and without debugging turned on) [Failed to show up on my computer as a device or anything]
Downloading the APK that I need from a file sharing website [Downloads fail]
Uploading the APK that I need to my Google drive and downloading it from the tablet [Says waiting for data connection and doesn't download even though connected to our WiFi]
Inserting the SD card into my computer, copying the APK I need over to it, then inserting the SD card back into the tablet, going into the browser and typing "File:///sdcard/<name here>.apk" to install an APK but getting an error in the installer after pushing 'install' -> 'Application not installed'
Trying to perform a factory reset; this simply makes the tablet reboot with everything the same as it was before.
Essentially guys and gals, my tablet here is running Android 2.0, I want to update it by making my own rom for it to something at least >4.0, and it seems that I've made things worse and have no way out of this mess. I think I've essentially bricked it even though it still works. :silly:
What do I need to do to make a custom ROM let alone flash/wipe this tablet?
All help will be incredibly valuable
There should be plenty of info here http://www.slatedroid.com/forum/93-velocity-micro-cruz-reader/ to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Still no paddles
es0tericcha0s said:
There should be plenty of info here < > to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Click to expand...
Click to collapse
Thank you very much for your response. It looks like on that website I've already found multiple useful roms!
In fact I already downloaded one and put it onto the SD card. Apparently for these tablets you're supposed to, while powered off, turn it back on by holding the power button and the volume up button but all this seems to do as a whole load of nothing.
I fear that what I've done to it by deleting potentially sensitive programs previously, I have somehow managed to make this process impossible.
Is there some kind of way that I can plug this tablet into my computer and be able to completely wipe it so I can, at the very least, have a functional tablet that will work at all? I've done approximately 5 factory data resets yet the background image that my friend has on the tablet as well as seemingly every single setting and application is remaining untouched..
Try the ones here that also install a custom recovery: http://www.slatedroid.com/topic/33586-a-clockworkmod-rom-compendium-for-the-cruz-reader/
You'll want to make sure and rename the file exactly as mentioned there on the OP. Install instructions are included too. I don't think there is a way to reload via the PC. The right zip should get everything working properly.
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