Has any one of you guys here successfully compiled and booted up a kernel for the A31s? I downloaded and installed the toolchain already, and decided to cobble up one out of curiosity (and partly to get a Dragonrise USB joystick to work on my device), but I'm at a bit of a loss as to how to build one. I know there are instructions at Linux-Sunxi, but there doesn't seem to be a specific guide on the 32, only for A23, A20 and the A1x.
I made some progress on this but got stuck
blakegriplingph said:
Has any one of you guys here successfully compiled and booted up a kernel for the A31s? I downloaded and installed the toolchain already, and decided to cobble up one out of curiosity (and partly to get a Dragonrise USB joystick to work on my device), but I'm at a bit of a loss as to how to build one. I know there are instructions at Linux-Sunxi, but there doesn't seem to be a specific guide on the 32, only for A23, A20 and the A1x.
Click to expand...
Click to collapse
I was able to make a little more progress. I was able to download the sdk, whose link I cannot post because I am a new user, and successfully downloaded and built a stock image but when I use the pheonix suite to update the tablet it just hangs.
I suspect that hardware is different from what is available with the stock SDK and tried to build my own target but that did not work either. Any help or pointers would be great. Even an explanation as to why the pheonix suite update too hangs at the beginning of the update process.
obsktr said:
I was able to make a little more progress. I was able to download the sdk, whose link I cannot post because I am a new user, and successfully downloaded and built a stock image but when I use the pheonix suite to update the tablet it just hangs.
I suspect that hardware is different from what is available with the stock SDK and tried to build my own target but that did not work either. Any help or pointers would be great. Even an explanation as to why the pheonix suite update too hangs at the beginning of the update process.
Click to expand...
Click to collapse
I made some progress with the SDK too, and in my case I used the Fiber-3G target for Android along with the a31s kernel config. Both SDKs work, but my probs with the aforementioned SDKs is that they're riddled with issues - RTC isn't persistent in SDK 3.3, besides the LCD displaying funky coloured spots in some high-contrast areas. SDK 4.5 could've been perfect if it wasn't for the screen turning white whenever I put the tab to sleep.
I'd like to extract the kernel config on the one that came with my tab, but the problem here is that it didn't came with config.gz support, and my question here is that will extract-ikconfig work on those kernels?
blakegriplingph said:
I made some progress with the SDK too, and in my case I used the Fiber-3G target for Android along with the a31s kernel config. Both SDKs work, but my probs with the aforementioned SDKs is that they're riddled with issues - RTC isn't persistent in SDK 3.3, besides the LCD displaying funky coloured spots in some high-contrast areas. SDK 4.5 could've been perfect if it wasn't for the screen turning white whenever I put the tab to sleep.
I'd like to extract the kernel config on the one that came with my tab, but the problem here is that it didn't came with config.gz support, and my question here is that will extract-ikconfig work on those kernels?
Click to expand...
Click to collapse
Could you share how you got the SDK to work? Did you just do a stock build of fiber-3g. What compiled did you use? Did you use the pheonix suite to install the image?
Seedy
obsktr said:
Could you share how you got the SDK to work? Did you just do a stock build of fiber-3g. What compiled did you use? Did you use the pheonix suite to install the image?
Seedy
Click to expand...
Click to collapse
Yeah, all I did was to use fiber-3g, provided that you already cooked up a kernel, and yes I did use Phoenixsuit for flashing it. The tutorial at https://olimex.wordpress.com/2014/0...d-4-2-2-for-a20-olinuxino-micro-from-scratch/ should work, though since it's for the A20 you do need to change some specific parts in it. Let me know if you come across some hurdles, dude, I'll see what I can do with it.
blakegriplingph said:
Yeah, all I did was to use fiber-3g, provided that you already cooked up a kernel, and yes I did use Phoenixsuit for flashing it. The tutorial at .. should work, though since it's for the A20 you do need to change some specific parts in it. Let me know if you come across some hurdles, dude, I'll see what I can do with it.
Click to expand...
Click to collapse
Thanks for the link. It is very similar to the PDF file that came with the SDK, but did not work at all. I have tried building with 3 different combos: fiber_3g, fiber_w02 and fiber_a31st with the same problem. I do get an image file after the build which is placed in the lichee/tools/pack_brandy/, but when I use phoenixsuite to flash it, it just says it will take 0 minutes and then hangs there.
Pheonix suite detects my board with the following model: fiber_wifibt_mtk and I cannot find this model when I run lunch. I tried creating a spec for it and changing the target name to match but that did not work. My rational was that perhaps pheonix suite saw a model mismatch and then stopped but I guess something else is wrong.
Any help or tips would be grate
Hmm, are the drivers for Phoenix properly installed? Can you flash a stock image, or at least a known working image to your device?
Related
Development on the phone I have has gotten as far as rooting stock (SCH-I110, Samsung Illusion). As I've toyed around with my Nook, I like the idea of cutting edge software still running on older hardware. Yes, yes, I realize that this is a "cheap phone" and not "in demand" and "why don't you just go and get a S2 or S3", but isn't the whole idea of open source the ability for people to learn? I've loved reaping the benefits of others' hard work, but it's time to get my own hands dirty...
Basically it comes down to this: I need to be pointed in the right place to learn how to build recovery for my device (ie CWM).
It's currently rooted, running stock and busybox, but that's as far as I have gotten. The source code HAS been released already, so it's out there. I've tried to read up about Odin in order to figure out how to pull a recovery image and start building, but just about every tutorial I've come across teaches people how to cook their own ROMs after CWM or TWRP is already installed. I'm not quite there yet.
So if anyone has a good place that contains information on building recovery, thank you for your help in advance. I just need a little direction.
Ok, so I pulled a boot.img off the phone as well as a system.tar. I used the boot.img on builder.cyanogenmod.com and have the following output files:
android_device_unknown_unknown.zip
inputrecovery.img
manifest.xml
recovery.img
The recovery image can be found here: http://builder.clockworkmod.com/redirect/5dbb87a058d1bb5fcd0bcbeca347c45b.img
I did see on the console output that it was building for CM10.1. Is this going to be an issue?
Thanks for helping an Android Noobie.
Would this be any help: http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
XyanumX said:
Would this be any help: http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Click to expand...
Click to collapse
Yeah, that was one source I was reading. I saw his note about initramfs, though. I believe the Illusion uses it as opposed to the standard boot image format, so his guide doesn't work. Thanks for suggesting it, though!
Hello, i wannt to Dev the Samsung Galaxy XCover by XDA so i start with a Singl Thread,
How to Root GT-S5690?
Flash this File in recovery!
http://forum.xda-developers.com/attachment.php?attachmentid=2252551&stc=1&d=1378997325
How to get CWM Recovery for GT-S5690?
Flash this File throut ODIN in PDA Section and its working!
http://forum.xda-developers.com/attachment.php?attachmentid=2252549&stc=1&d=1378997296
Some Custom Roms and CWM coming soooooon,....im working at that! :laugh::highfive::laugh::highfive::laugh:
MFG Marion808
it´s working! how did you build that? is there a possibility of ics or jb?
Thanks
marion808 said:
Hello, i wannt to Dev the Samsung Galaxy XCover by XDA so i start with a Singl Thread,
How to Root GT-S5690?
Flash this File in recovery!
http://forum.xda-developers.com/attachment.php?attachmentid=2252551&stc=1&d=1378997325
How to get CWM Recovery for GT-S5690?
Flash this File throut ODIN in PDA Section and its working!
http://forum.xda-developers.com/attachment.php?attachmentid=2252549&stc=1&d=1378997296
Some Custom Roms and CWM coming soooooon,....im working at that! :laugh::highfive::laugh::highfive::laugh:
MFG Marion808
Click to expand...
Click to collapse
Hi,
Your rooting method doesn't seem to work on my phone. I get no error during flash of the zip file but when I reboot, the phone isn't rooted.
FYI I'm using a fresh install of the S5690XXLL1_S5690LUXLL1 Rom.
Am I missing something here ?
Using another method found on a French forum, I can get root to work.
ClockworkMod Recovery installation worked flawlessly and that's great news :good:
Your work is much appreciated and it would be nice of you if you could give us a heads-up on what you're up to.
Thanks a bunch anyway.
Thanks
Thanks. Confirmed this is a working root and CWM recovery method.
Looking forward for custom roms, preferable CM based.
I got my phone rooted but no cvm.. they all gives me error msg..
how's this project doing? I would love to see custom roms for this device
My try with ICS for xcover:
https://github.com/manakeri/android_device_samsung_xcover
manakeri said:
My try with ICS for xcover:
//github.com/manakeri/android_device_samsung_xcover
Click to expand...
Click to collapse
hello to every one!
so how's the work on ICs going for this old phone?
I hope you still active!
maybe i can beta test your ROM?
keep it up!
gt-s5690 cwm test result
root zip is not working, what worked is
http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
SuperSU from chainfire.
Backup is not working with default settings , you must choose 'tar' format .
Restore is halt on /system restore.
manakeri said:
My try with ICS for xcover:
https://github.com/manakeri/android_device_samsung_xcover
Click to expand...
Click to collapse
Can I BETA test your rom
There isn't that much to test yet, struggling to get the RIL working.
Haven't found any info about marvell's RIL.
And the development has been on a break for couple months now, because I'm so busy with "real life".
Sent from my GT-S5690 using Tapatalk 2
good phone, low memory
Naturely real life is more important.
I have been checking your post about this regularly in the hope of unbloating my xcover because of the little memory the phone has.
I wish i could help. I know computers and some php and stuff, but phones, not a clue.
So we'll wait patiently for you to make our day :victory:
How to build?
manakeri said:
And the development has been on a break for couple months now, because I'm so busy with "real life".
Click to expand...
Click to collapse
Hi manakeri,
thanks for your efforts!
I would like to help doing some low-level (RIL, camerca, GPS etc.) stuff, but I don't really know how to start. There is no build/envsetup.sh, which I could source into my shell. I am used to do Linux development on and for Debian and similar Linux distributions, so working with the Android framework is quite new to me. Could you point me to some howto or give some hints?
Regards,
Benedikt
Are you still working on it?
I would like to participate. My brother has a XCover, but he needs it for daily use, so i am not really able to flash anything right now.
Could you point out how you start everything, and which sources you use?
1+
bwildenhain said:
Hi manakeri,
thanks for your efforts!
I would like to help doing some low-level (RIL, camerca, GPS etc.) stuff, but I don't really know how to start. There is no build/envsetup.sh, which I could source into my shell. I am used to do Linux development on and for Debian and similar Linux distributions, so working with the Android framework is quite new to me. Could you point me to some howto or give some hints?
Regards,
Benedikt
Click to expand...
Click to collapse
dehein said:
Are you still working on it?
I would like to participate. My brother has a XCover, but he needs it for daily use, so i am not really able to flash anything right now.
Could you point out how you start everything, and which sources you use?
Click to expand...
Click to collapse
First you'll need the tools:
http://forum.xda-developers.com/showthread.php?t=2464683
And then something like that:
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync
git clone git://github.com/manakeri/android_device_samsung_xcover.git device/samsung/xcover
cd device/samsung/xcover/ && ./extract-files.sh && cd ../../..
cp device/samsung/xcover/armv7-a.mk build/core/combo/arch/arm/
cp device/samsung/xcover/overlay/bootable/recovery/ui.c bootable/recovery/ui.c
cp device/samsung/xcover/overlay/bootable/recovery/ui.c bootable/recovery/ui.c
cp device/samsung/xcover/overlay/development/build/sdk.atree development/build/sdk.atree
rm -rf development/samples
. build/envsetup.h
cd vendor/cm && ./get-prebuilts && cd ../..
brunch cm_xcover-eng
Could be I forgot something, but if you get problems, ask.
I'll try to answer in at least couple of days.
compiling cm9 for s5690
manakeri said:
1+
Could be I forgot something, but if you get problems, ask.
I'll try to answer in at least couple of days.
Click to expand...
Click to collapse
Hi manakeri,
thanks for you instructions
Now I got some zip file:
out/target/product/xcover/cm-9-20140225-UNOFFICIAL-xcover.zip, 134M
I installed CWM, told it to install that file, cleared dalvik cache and even did a factory reset, but always got nothing more than a black screen (with backlight on) when trying to boot and couldn't use logcat as some executable within /system/bin... was missing.
If I had a development board I would simply put my computer onto the serial port and probably see what's going on, but I would like to avoid opening the phones case as I don't believe it would stay waterproof in that case. So how could I get some useful debugging info by using software?
Regards,
Benedikt
If I remember right, you need to format both data and system partition using the CWM.
Sent from my GT-S5690 using Tapatalk 2
bwildenhain said:
Hi manakeri,
thanks for you instructions
Now I got some zip file:
out/target/product/xcover/cm-9-20140225-UNOFFICIAL-xcover.zip, 134M
I installed CWM, told it to install that file, cleared dalvik cache and even did a factory reset, but always got nothing more than a black screen (with backlight on) when trying to boot and couldn't use logcat as some executable within /system/bin... was missing.
If I had a development board I would simply put my computer onto the serial port and probably see what's going on, but I would like to avoid opening the phones case as I don't believe it would stay waterproof in that case. So how could I get some useful debugging info by using software?
Regards,
Benedikt
Click to expand...
Click to collapse
Hello bwildenhain,
Please share with us your xperience, regarding the CM9 ROM built by you.
Thank you.
Have a nice day !
PS Sorry for my English
Hello cbacsro,
cbacsro said:
Please share with us your xperience, regarding the CM9 ROM built by you.
Click to expand...
Click to collapse
unfortunately I wasn't able to get it running yet. I tried to install both cm-9-20140225-UNOFFICIAL-xcover.zip and cm_xcover-ota-eng.$USER.zip, both after doing a factory reset, but could not boot CM.
@manakeri
I installed the new CWM by using device/samsung/xcover/scripts/recovery.sh (and manually executing the last uncommented lines), pushed the cm-zip file to the sdcard and then booted to CWM and there did a factory reset and applied one of the cm-zipfiles. Is there anything I forgot?
Regards,
Benedikt
Are those uart pins?
Hello,
I hope not to be disturbing by bumping such an old thread - also hope this is the right thread since it does not seem that the s5690 has its own subforum. What for an insignificant little device. Anyways we've been active and I am currently trying to find the UART pins of the S5690. I have taken a scan of the circuit board and cropped it a bit to show which pins I think might be UART. However, I'm quite in a bind right now: My BusPirate is not here yet. Just had to order one, and now it's going once around the world. Interestingly enough, it seems the mainboard can be run without having the other modules (like touch or camera) connected.
If anybody has experiance with UART (and has a xcover of which one does not fear to void the warranty or brick it or whatever), it would be nice if it got verified.
These four pins seem to be perfect canidates however: Next to processor, four in a group, and one seems to be GND.
Link to photo file (add together yourself, I'm not gonna spam to get rid of that damn 10 post cap. I'd also advise to visit the image hoster with an adblocker):
i7. imgchili .net/47012/47012110_s5690_uart_info.png
(I created that Image by scanning the circuit board with a common flatbed scanner in high resolution, just if you're wondering - makes it way easier to find stuff. Then found those pins, tested them for GND, cropped the original image and included the info you see in it with GIMP).
ppps: I assume it would be too much to ask somebody to write a pxa95x framebuffer driver for the last linux kernel that supported pxa95x devices...
Edit: Oh, the thread is still active. I should *really* get some sleep.
Edit2: @bwildenhain
This is taken from an Email conversation I had with manakeri:
otezun said:
Hey, just wanted to inform you. I just reflashed the phone to 2.3.6. Then rooted it with KERUK, from k0k0s download stuff. Anyways, after I rooted the phone, I installed CWM as you said, with your recovery image. I made factory reset, wiped cache, wiped dalvik cache, formatted /system and /data. Then installed my compiled Cyanogenmod 9.
Click to expand...
Click to collapse
Hehe, documentation is everything...the fat text are the steps I think where absolutely crucial to get cyanogenmod to work. Not sure though. Also @ getting infos from phone without opening it - I think that is possible if you have the right resistance cable. Like USB Jig cable with other resistor, put it onto power and it boots into UART mode, usually giving some kinda shell if I understand it correctly. However, I think you also need special hardware for that too.
However, do not take usual infos in "Fun with resistors", it does not seem to work with the s5690. Or do and tell us how it worked out. Depends on how far you want to go.
Edit 3:
I allowed myself to add some wiki pages to the github wiki.
The wiki now should contain most relevant information on getting started. Also got a bit of structure into it. However, I cannot guarantee that all of the information is correct. Be wise and use your brain.
Check it out at: https ://github. com/manakeri/android_device_samsung_xcover/wiki
Installing CM
Yesterday I installed CWM and rooted my Xcover. Last night I compiled the Xcover branch of CM9 made by manakeri using Builduntu made by sylentprofet.
I just managed to successfully install CyanogenMod by installing cm_xcover-ota-eng.android.zip (aka cm_xcover-ota-eng.$USER.zip). Before installing I performed a factory reset, wiped cache, formatted /system and formatted /data.
It boots fine, and I will experiment with the coming days! Hopefully development will restart soon!
Does anyone know if it's possible to build an update.img but to just update the kernel and recovery? I'm pretty sure it must be possible.
Yes, it should be possible to just update these.
I guess you should look at how they build an image to install recovery only. Like when they install custom recoveries.
robertut said:
Yes, it should be possible to just update these.
I guess you should look at how they build an image to install recovery only. Like when they install custom recoveries.
Click to expand...
Click to collapse
Yeah I thought so. I'll be brave and try it as it'll be a damn sight easier to build the update with just recovery and kernel when I'm doing the 1st boot logo's and easier for everyone that wants a boot logo.
Goose247 said:
Does anyone know if it's possible to build an update.img but to just update the kernel and recovery? I'm pretty sure it must be possible.
Click to expand...
Click to collapse
Yes, you can !! Simply replace kernel and recovery Everything will be fine. But all the rest should be for your processor RK3188 or RK3066. ( system.img and boot.img )
Malaysk said:
Yes, you can !! Simply replace kernel and recovery Everything will be fine. But all the rest should be for your processor RK3188 or RK3066. ( system.img and boot.img )
Click to expand...
Click to collapse
We're thinking about creating an update.img containing only the kernel.img and recovery.img, and without the system and boot. Just to replace the boot logo, and not the whole system completely.
robertut said:
We're thinking about creating an update.img containing only the kernel.img and recovery.img, and without the system and boot. Just to replace the boot logo, and not the whole system completely.
Click to expand...
Click to collapse
Oh I understand - it will not work, I think. In recovery is to check if all the files - kernel , recovery.img, system.img and boot.img.
Malaysk said:
Oh I understand - it will not work, I think. In recovery is to check if all the files - kernel , recovery.img, system.img and boot.img.
Click to expand...
Click to collapse
It should be possible. The recovery will only update the files that exist. If it doesn't find boot.img for example, it will skip it.
It should be possible. At least when using custom recovery.
Anyway, There is a way to flash a recovery IMG without using recovery using a shell script, maybe this should work for kernel also...stg like this http://forum.xda-developers.com/showthread.php?t=2102679
I have use that method before on an android tv box. You should find a correct recovery.IMG for those devices though
If the kernel could not be flashed that way, you can install a custom recovery and install the kernel and the stock recovery.img using a flashable zip.
Unfortunately, this is the only Android system I've worked on where updates have to be done with .img updates. It's not really for my benefit, it's for all the peeps I'm creating boot logo's for. Asking them to use a custom recovery or installing it using terminal emulator is more hassle than the way they have to do it at the minute. Not to worry
how do you guys compile the update.img ?
I tried few times with
RK3xxx_firmware_tools_5.99.07.00
extract, change kernel, build
the update.img does not install
RK3188
doctorman said:
how do you guys compile the update.img ?
I tried few times with
RK3xxx_firmware_tools_5.99.07.00
extract, change kernel, build
the update.img does not install
RK3188
Click to expand...
Click to collapse
RK3066 IMG Mod Tool
works, despite it's name it will unpack and pack the update.img for both RK3066 and RK3188, since they are packed the same.
jakejm79 said:
RK3066 IMG Mod Tool
works, despite it's name it will unpack and pack the update.img for both RK3066 and RK3188, since they are packed the same.
Click to expand...
Click to collapse
any link to it?
found this
http://rockchipfirmware.com/developer-tools
but I guess that program is only for linux and not windows
doctorman said:
any link to it?
found this
http://rockchipfirmware.com/developer-tools
but I guess that program is only for linux and not windows
Click to expand...
Click to collapse
There is lot resources on rk3188 around there
https://www.entertainmentbox.com/droidsticks-latest-rk3188-q7-firmware-download/
http://www.cnx-software.com/2014/11/10/android-5-0-lollipop-now-boots-on-rockchip-rk3188-tablets/
http://www.rockchipfirmware.com/forum-library
I used first two links and played with some generic Lollipop AOSP. Managed to install kernel and system partitions and to boot.
In third link you have rs232 low level integration described. It is used for MCU integration.
Didnt bother to extract libs and stock apps and try to rebuild with them. It would take some time and I have none to spare.
Anyhow, LP (and even MM) is not hard to get running on these units. Problem is with mumbo-jumbo stock apps that need to be rebuilt in order to comply with changed API and security model in LP/MM.
But even that is not too hard. Reverse engineer, get code / libs for rs232 and just change handlers in apps to confirm with new standards.
---------- Post added at 08:11 AM ---------- Previous post was at 08:00 AM ----------
doctorman said:
any link to it?
found this
http://rockchipfirmware.com/developer-tools
but I guess that program is only for linux and not windows
Click to expand...
Click to collapse
Here you have Windows tools
http://www.rockchip.nl/downloads/
Also you may contact their NL division. They are I EU so they should provide more support in accordance to good business practices.
doctorman said:
any link to it?
found this
http://rockchipfirmware.com/developer-tools
but I guess that program is only for linux and not windows
Click to expand...
Click to collapse
See attached, you can ignore the parameter file in the archive. If you want to mount the system.img files or others then you will want linux to mount them.
doctorman said:
how do you guys compile the update.img ?
I tried few times with
RK3xxx_firmware_tools_5.99.07.00
extract, change kernel, build
the update.img does not install
RK3188
Click to expand...
Click to collapse
My problem seems to be the image I was using had white background and in ASCII PPM format that increases the size and kernel does not install
made the background black
and indexed the colors to 224 colors in the image and the kernel was created without error
but after install my own logo nor malaysk logo shows
it now reverts to the original head units boot logo.
A note to anyone considering cooking an update.img for RK3188 800x480 devices in particular ('cos that's what I've got) but for any 2DIN car stereo head unit device really. It's more a request, but something I feel is a must-have for every ROM.
ADD A NOTIFICATION BAR SHORTCUT
THAT SWITCHES OFF THE SCREEN!
Essentially what I'm looking for is what came with the OEM KitKat 4.4.2 ROM preinstalled in my Eonon G2110F. During night driving, I could slide the Notification bar down, tap an icon that looked like a X in a box, and the screen would switch off. If I had a music app. or the AM/FM radio going, they would continue to play, and turning a knob or clicking a button on the unit would light the screen.
Thanks for listening!
djshotty said:
A note to anyone considering cooking an update.img for RK3188 800x480 devices in particular ('cos that's what I've got) but for any 2DIN car stereo head unit device really. It's more a request, but something I feel is a must-have for every ROM.
ADD A NOTIFICATION BAR SHORTCUT
THAT SWITCHES OFF THE SCREEN!
Essentially what I'm looking for is what came with the OEM KitKat 4.4.2 ROM preinstalled in my Eonon G2110F. During night driving, I could slide the Notification bar down, tap an icon that looked like a X in a box, and the screen would switch off. If I had a music app. or the AM/FM radio going, they would continue to play, and turning a knob or clicking a button on the unit would light the screen.
Thanks for listening!
Click to expand...
Click to collapse
It is called Malaysk ROM.. does what you want with screen saver and button
now please reduce the size of the font you used
jakejm79 said:
See attached, you can ignore the parameter file in the archive. If you want to mount the system.img files or others then you will want linux to mount them.
Click to expand...
Click to collapse
how do I use that in windows?
I just heard back from the developer of RK3xxx_firmware_tools_5.99.07.00 that the update.img I make with that tool can not be flashed in Recovery. and that is my problem, so I can use RK3xxx_firmware_tools_5.99.07.00 to modify the logo in kernel.img and package it all up with another program I guess
so what is the easiest way to repackage the update.img for flash in recovery of the device?
Question for our developers that have made recovery flashable update.img @Goose247 @Malaysk @dsa8310
Watched few videos on how to use the mod tool and they all use RK batch tool to flash the image... can the .img be flashed in recovery?
doctorman said:
It is called Malaysk ROM.. does what you want with screen saver and button
now please reduce the size of the font you used
Click to expand...
Click to collapse
Well that's just silly! I've gone through every Settings menu in the latest Malaysk ROM I'm still to find how to place a 'button' on the Notifications bar to switch the screen off. I only ask questions when I've exhausted all avenues of research. With that, do you have a way of enabling such a shortcut on my unit's Home screen, or even better, the Notification bar?
doctorman said:
how do I use that in windows?
I just heard back from the developer of RK3xxx_firmware_tools_5.99.07.00 that the update.img I make with that tool can not be flashed in Recovery. and that is my problem, so I can use RK3xxx_firmware_tools_5.99.07.00 to modify the logo in kernel.img and package it all up with another program I guess
so what is the easiest way to repackage the update.img for flash in recovery of the device?
Question for our developers that have made recovery flashable update.img @Goose247 @Malaysk @dsa8310
Watched few videos on how to use the mod tool and they all use RK batch tool to flash the image... can the .img be flashed in recovery?
Click to expand...
Click to collapse
When I did the boot logo changing service (when it worked), everyone I did it for installed the rom through recovery. I did a LOT of boot logos for other people and they all installed through recovery (choosing not to wipe to keep their settings, installed apps etc.) and I am pretty sure I had a 100% success rate with no complaints.
Perhaps the problem is you are trying to change the boot logo for a new rom and it simply won't work. Trying to change the boot logo for any Malaysk rom built after Feb (I think), it simply won't work. If you try mix and match and use stock kernel's and/or recovery's with Malaysk's rom you run the risk of bricking your unit. You are just going to have to accept the fact that you cannot change the boot logo on newer built roms.
I personally use an older rom so that using a custom boot logo will work.
Hi,
I have a Rockchip tablet RK312x Android version 4.4. I also have the stock image for it.
What I want to do? Update the android version to at least 5.0.
What I have done so far?
Tried to understand how AOSP works, how building ROMs work. Downloaded AOSP 5.1.1. Completed a test build for one of the nexus devices just to be sure the process completes 100%.
Extracted the stock image to get .img files for boot, kernel, misc, recovery, resource, system and uboot.
My question: Is it possible to upgrade the tablet without going the entire creating .mk files and building from scratch route?
Are there any complete step by step guides on this? I tried searching and did find many but not one of them was complete, covering the process that I want to do in a simple manner.
So many of you had a look at this thread and no replies yet. I am all new to this. So sorry if my questions don't make sense. But if you have any experience in building roms, I need your help.
Still, any help would be highly appreciated.
There is no simple manner to this. As your device was not officially upgrade you will have to do alot of work to hack the kernel to work with the new OS. Then you will have to heck all the drivers to work and even then it might not work at all. I would start by finding out if the oem released the kernel source code for the device. Judging from the name I am betting not.
Is there any consolidated info on this new script? I have yet to find any such thread (still searching).
I have it downloaded, and I have the python img extract script.
I was thinking of copying over the main script files with the new Android 11 images.
Is there any reason why I should not do that?
I think the trick is MSM uses the EDL flash mode, which seems to be able to bring back ANY corruption in the R/W part of the phone, no matter how bad it is messed up. I assume it only uploads signed code, and we couldn't just inject our own images into/through it like we can through fastboot.
Neat trick, though, if we can... no more stuck bootloops or wrong slot errors...
I'd also love to see it run on Linux so I don't need to keep Win images around to use it... wonder if the protocol is documented anywhere to be able to reverse engineer it? Probably over my capabilities by far.
@SomeRandomGuy
Thanks for the reply. FYI, I just tried it on my BE89BA and I replaced all the images with the latest available Android 11 images (extracted with the python script). No dice. Qualcomm crash dump screen.
I'm trying a few different things. I'll post here once I get a result that works.
TheArkive said:
@SomeRandomGuy
Thanks for the reply. FYI, I just tried it on my BE89BA and I replaced all the images with the latest available Android 11 images (extracted with the python script). No dice. Qualcomm crash dump screen.
I'm trying a few different things. I'll post here once I get a result that works.
Click to expand...
Click to collapse
Have you tried going the Install.bin route?
ninjasinabag said:
Have you tried going the Install.bin route?
Click to expand...
Click to collapse
If someone links or outlines the install.bin idea i can give it a shot.
ninjasinabag said:
Have you tried going the Install.bin route?
Click to expand...
Click to collapse
I'm sorry @ninjasinabag , I've never heard of this with respect to a OnePlus phone... and my search-fu is failing me... could you give us a hint what this entails?