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.
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!
Can you run a new version of stock android on any low end device.
If yes - even if it needs some development - how?
Thanks
Do you mean download the OS from a new device and upload it to your old device?
Probably not.
Why not just get Cyanogen Mod (unlock the device first if you care about that).
What I meant is that, not all devices get the newest version of android, some devices get dropped out from the manufacturers.
Cyanogendmod is great , but again some devices never get supported by cyanogenmod.
So what if I can get any device that has no updates from the manufacturer, and cyanogenmod doesn't support it, and create put the newest version of android on it, is that possible
Theoretically, it is possible, but depends on so many things...
For example:
What kind of phone?
What kind of processor?
Is there source code for the kernel available from the manufacturer?
Is the bootloader unlocked to allow custom recoveries?
What update is it on?
Are you capable of coding?
Understand logcats?
Are the original firmware and tools available to reinstall the stock system if something goes wrong?
Stuff like this is the tip of the iceberg...
That's exactly what I'm asking for,
I Know some coding, I can root the device, install a custom recovery, and get a recovery version of the stock system,
I can get the phone type, and the processor type, and what update the device is on,
I know it takes some coding to do what I'm asking for, but i don't know what to code, or how. basically I don't know where to start.
What I want to do, is to be able to install any version of android on a device (doesn't need to be all the devices), Like the way windows or Linux works on PCs.
I know it isn't easy as installing windows, but as "es0tericcha0s" mentioned it is hard but possible.
Any Advice
desoky725 said:
That's exactly what I'm asking for,
I Know some coding, I can root the device, install a custom recovery, and get a recovery version of the stock system,
I can get the phone type, and the processor type, and what update the device is on,
I know it takes some coding to do what I'm asking for, but i don't know what to code, or how. basically I don't know where to start.
What I want to do, is to be able to install any version of android on a device (doesn't need to be all the devices), Like the way windows or Linux works on PCs.
I know it isn't easy as installing windows, but as "es0tericcha0s" mentioned it is hard but possible.
Any Advice
Click to expand...
Click to collapse
What device are you using? Your best bet is to find a similar phone using the same processing package that has development started so you can compare source code. Trying to make your own rom without source code would be near impossible due to issues with drivers and what not.
Hi,
I just got a new tab Lenovo M10 TB-X605F.
I tried to unlock it with fastboot-adb (minimal kit).
When I enter "fastboot devices" the serial n° displays.
But each command I tried (fastboot oem unlock, unlock-go, flashing, flashing unlock...) get the same asnwer : "FAILED (remote: unknown command)".
Does anyone know a solution?
Thank you.
I also had problems with the out-of-the-box version of fastboot.
Solution is to upgrade to Pie, because the update allows bootloader unlocking. Easiest way is to load the rescue ROM using LMSA, then let the tablet fetch the OTAs.
To learn more have a look at @Chaser42's root thread for the P10. Also in that thread @Long_Sam has a step-by-step guide for the M10.
I've also posted an updated magisk_patched .img for TB-X605F running S210097_190927 to that thread. Be careful, though. Make sure your build and model number are the same as mine before using it:
build number: X605F_S210097_190927_ROW
model number: TB-X605F (hardware code 63)
Check the sticker on the back of your tablet for the hardware code. It's in brackets after the S/N.
So mine reads: "S/N: XXXXXXXX (63)".
Thank you very, very much Yahoo Mike!
I'll try it as soon as possible!
did you have oem unlock on in developer mode?
Yes
thanks, but i wonder if i can get twrp on the tablet
turboperson123 said:
thanks, but i wonder if i can get twrp on the tablet
Click to expand...
Click to collapse
I don't know yet.
Root is ok, thanks of the links in YahooMike's post. :good:
Monpseud0 said:
I don't know yet.
Root is ok, thanks of the links in YahooMike's post. :good:
Click to expand...
Click to collapse
I would love to get custom recovery for these tablets. I submitted a request for the P10 (TB-X705F) to the guys that port TWRP images to new devices. However, I think they are completely overloaded with request so we won't see anything soon. I was working with a guy that was making an image but he got busy with real life and hasn't been able to complete it.
I'm about ready to learn Android kitchen and cook up some TWRP images myself. I've read all the documentation. I just might be able to do it if I can find the time. If I can successfully make an image for the P10 then I can also make one for the M10 and all other variants. Hopefully I'm not being overly ambitious. Wish me luck.
Chaser
TWRP is OK. I found the way to flash it somewhere in this forum. It works. Now, it is waiting for a custom ROM to flash!
Chasser, if you do that, You're my hero ! I'd like to help you but I don't know anything about building a ROM. So I wish you the best! Can't sait!
Chaser42 said:
I would love to get custom recovery for these tablets. I submitted a request for the P10 (TB-X705F) to the guys that port TWRP images to new devices. However, I think they are completely overloaded with request so we won't see anything soon. I was working with a guy that was making an image but he got busy with real life and hasn't been able to complete it.
I'm about ready to learn Android kitchen and cook up some TWRP images myself. I've read all the documentation. I just might be able to do it if I can find the time. If I can successfully make an image for the P10 then I can also make one for the M10 and all other variants. Hopefully I'm not being overly ambitious. Wish me luck.
Chaser
Click to expand...
Click to collapse
I've got some time this week. Happy to help with the TWRP port. A basic setup shouldn't take long, especially if we ignore forced data encryption.
If you're eventually going to a install custom ROM, then you'll be wiping the /data partition anyway. So probably best to avoid the nightmare of trying to crack the encryption in TWRP - at least to begin with.
If it's really true that the P10 is just an M10 with some bells and whistles added, then I suspect we'll get away with using the same kernel image for all these tablets X605F/L & X705F/L in recovery. That means we can all use the same TWRP img. Fingers crossed.
But until we have some custom ROMs, the stock boot.img will need to be patched to remove encryption. Otherwise the next time you reboot, it'll just re-encrypt the data partition. Those images will be different for each tablet.
Have you got a github repo set up for recovery tree? We should probably start a new thread for unofficial TWRP (X605F/L & X705F/L) as well. I'm happy to kick it all off, if you haven't done so already.
Yahoo Mike said:
I've got some time this week. Happy to help with the TWRP port. A basic setup shouldn't take long, especially if we ignore forced data encryption.
If you're eventually going to a install custom ROM, then you'll be wiping the /data partition anyway. So probably best to avoid the nightmare of trying to crack the encryption in TWRP - at least to begin with.
If it's really true that the P10 is just an M10 with some bells and whistles added, then I suspect we'll get away with using the same kernel image for all these tablets X605F/L & X705F/L in recovery. That means we can all use the same TWRP img. Fingers crossed.
But until we have some custom ROMs, the stock boot.img will need to be patched to remove encryption. Otherwise the next time you reboot, it'll just re-encrypt the data partition. Those images will be different for each tablet.
Have you got a github repo set up for recovery tree? We should probably start a new thread for unofficial TWRP (X605F/L & X705F/L) as well. I'm happy to kick it all off, if you haven't done so already.
Click to expand...
Click to collapse
The P10 and M10 are so similar, we could probably Port it for all of the different variants if other people are willing to help out and test. On my end I only have P10 and my test P10.
Currently I don't have a Linux machine but I saw that he made a version that works on Android. I think you I know a lot more about the process than I do. I'm just pretty good at reading documentation and coming up to speed on stuff that I've never done before. And this stuff isn't really over-the-top technology-wise so I figured it might be a neat project to tackle.
And speaking of custom roms, I think I saw that somebody had an unofficial lineage ROM started for these devices. I'll have to double-check that. And I was thinking about the stock ROM, encryption doesn't happen until after LMSA is done with the rescue and the tablet reboots. I'm not a big expert in what happens when the initial ROM is flashed but it feels like there's some sort of script running that handles a bunch of batch processes. I know that you can modify any of the files that you want before you do the rescue. Wouldn't it be nice if all we had to do is comment out some lines in the script so that encryption doesn't happen at all? Perhaps I'm being a bit too optimistic.
My big problem in the near future is time. I'm going to be very busy with my kids in the next few weeks. So I'm definitely not a position right now where I can spearhead that project. But we'll have to see how it goes. I'm sure I love some availability if you need my help.
Chaser
Yahoo Mike said:
I've got some time this week. Happy to help with the TWRP port. A basic setup shouldn't take long, especially if we ignore forced data encryption.
If you're eventually going to a install custom ROM, then you'll be wiping the /data partition anyway. So probably best to avoid the nightmare of trying to crack the encryption in TWRP - at least to begin with.
If it's really true that the P10 is just an M10 with some bells and whistles added, then I suspect we'll get away with using the same kernel image for all these tablets X605F/L & X705F/L in recovery. That means we can all use the same TWRP img. Fingers crossed.
But until we have some custom ROMs, the stock boot.img will need to be patched to remove encryption. Otherwise the next time you reboot, it'll just re-encrypt the data partition. Those images will be different for each tablet.
Have you got a github repo set up for recovery tree? We should probably start a new thread for unofficial TWRP (X605F/L & X705F/L) as well. I'm happy to kick it all off, if you haven't done so already.
Click to expand...
Click to collapse
Hi guys
I got TWRP on m'y M10. Thanks to Turboperson123
https://forum.xda-developers.com/general/help/lenovo-tb-x605f-twrp-t3976707?goto=newpost
There isn't much development done on this phone and there aren't any updates for stock ROM due to come out. So I've decided to try and port LineageOS from another phone with the same chipset. Problem is that when I follow any guide I can seem to find on here, nothing ever is as the guide states. The copy and paste method doesn't work because the names of the files don't match when I extract the boot.img's. Not to mention that I can't even get the system.img to extract whatsoever. I've tried various tools and have only ever had one tell me about the system.img, and that took hours. It still wouldn't extract it either though. I'm not brand new to Android, it's just been several years since I've really decided to play with them. Currently I have TWRP 3.2.1 installed with the stock ROM rooted with Magisk 24. Even simple modifications on the stock ROM, such as debloating, will cause every app on the phone to not work anymore after a reboot. Ultimately causing me to reflash the stock ROM and going through the root process all over again. Can someone please point me in the proper direction to get rid of this terrible stock ROM and begin building my own port? Thank you ahead of time.
Hello,
Anybody know of any good resources that can help me compile the kernel from my phone with a Linux base ROM/IMG like LineageOS or KaliNethunter? I can do the leg work, If I can find some solid documentation. The phone is rooted, bootloader unlocked, and carrier unlocked. I imagine you can compile the image, by using the Kernel from the stock image, and somehow using ADB to decompile and recompile the images?
I am new to this terminology, but not to jail breaking and rooting. The main thing is compiling systems with kernels, I've done it in Linux before, but the concept is still foreign. I'll understand more about it by the time I read a reply.
Thank you for any help or suggestions on where to start.
Edit:
Also, so long as I'm flashing images with fastboot, do I still run the risk of bricking the phone? I know there is always a risk, but it's safer than microsd updates, yes? Just keep a stock IMG file, and flash it if the kernel doesn't compile correctly?
Found this after posting https://forum.xda-developers.com/t/reference-how-to-compile-an-android-kernel.3627297/ . Going to add resources here. Multiple people have requested this, would like to get it working for everyone.