Related
I'm sure this has been covered before, but I can't get any answers. (When I search, I keep finding threads asking the same question and being told to search...)
I know I've seen a thread somewhere with some info. If anybody knows where this is and can post a link...
I've downloaded the kernel source for 2.1 from samsung and have been able to compile it. I took a voodoo kernel zip and unzipped it - replaced zImage with mine, and zipped it back up. When I use clockwork to flash the zip file, it goes into a reboot cycle. I figure this should work since the kernel versions are the same and my kernel should just use the existing modules, (in the same way it appears the voodoo kernel does).
I'm guessing I'm packaging it wrong, but I'd like to see a whole build procedure to make sure I didn't miss anything.
EDIT: Also, I'm running Ubuntu and its getting annoying to boot back and forth between Linux/Windows to use ODIN. Are there better ways to test kernels?
Thanks in advance.
Did you add the ramdisk? I use odin in virtualbox under ubuntu. There's a thread in the i9000 development forum that explains how to do it.
The ramdisk is finicky as hell. It's much simpler to start from a known good one. The voodoo project has one posted. You can also extract one from a working kernel.
Damn that ramdisk. It seems that only one way of adding it to the kernel works. I could never get the gzipped cpio file to go into the kernel. Have to ungzip/cpio and create the stupid list. But thats probably your issue.
http://forum.xda-developers.com/showthread.php?t=697938
This should have all the info you need to get started, need further help or clarification, can ask a dev. or do a google search
Thanks guys for the quick responses. I'm going to try and pack intramfs with my kernel and try again. I'll let you know how it goes.
A friend of mine found this link as well - I'll be trying to use that as well.
forum.xda-developers.[com]/showthread.php?t=777380
Why Samsung chose to write a Linux ROM flasher in Windows boggles my mind. It won't even run under WINE. What were they thinking?
dattaway said:
Why Samsung chose to write a Linux ROM flasher in Windows boggles my mind. It won't even run under WINE. What were they thinking?
Click to expand...
Click to collapse
They were probably thinking that most people run Windows...which would be a safe assumption.
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!
Don't forget to hit the thanks button.
http://superstarmobility.weebly.com/
New thread: http://forum.xda-developers.com/android/development/twrp-m1-lg-k7-t3462130.
(Above TWRP can be flashed with Flashify from Playstore)
Instructions from video:
With phone powered off, hold POWER and VOLUME DOWN buttons until LG logo shows. Release POWER then quickly press and hold again until factory reset menu comes up. Select YES and you will be booted into recovery instead of a factory reset ; )
Thanks @czarsuperstar!
V2 with the proper cmd line from m1 aka LG K7
Reserved.
This the real deal?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
Of course. You looked at the video?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
I've used it and can confirm, first tested it with fastboot without flashing of course(use adb to get to the bootloader: adb reboot bootloader , then fastboot:fastboot boot "twrp.img file, tested then rebooted into bootloader, then flashed via fastboot:fastboot flash "twrp.img file") instructions are for any random person that come by i know you know how to do all this
concerned xda citizen
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
The first twrp was from a htc phone. This is from lg leon lte. Same manufacturer. I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon twrp is missing the options seen on this one. Don't use it. But I'm working on cm_m1 so continue to use the old one and when your phone can't come on have fun getting in recovery. Make it better.
Recovery log
Make a log.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
Check out the LG L70 it's the same way to get in recovery. This must be your first LG phone.
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Go spam the other thread. Over 200 downloads and no problems but there was problems right away with the first version. For your info download Twrp c50 from the Twrp site examine it and ask why it's incomplete. That's why I linked the video of the Twrp from the site and same problems. Bye and leave me be. Hd2 check it out. Czarsuperstar's HTC HD2 android custom roms. Check it out and leave me alone. Thanks for your concern. Oh and for your info we have the same keyboard configuration as the LG Leon. There's a device tree. Google it. Google is your friend bro.
NASSTYROME said:
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Click to expand...
Click to collapse
not saying a official twrp isn't preferable, but man you got to learn how to talk to people, you were just short of cursing the dude out, and as far as the recovery the thing is solid(tested backup, flash and restore/ anyhow we got LGUP if you **** up so its not a huge deal), but anyone on this site shouldn't take someones word for things like recovery's and you should always test boot before you flash, also you don't seem to understand the first rule of xda-whatever happens to your device is on you, been that way since the og day's- talking politely to others is the way to go about things, people wont listen if you combative.
Kernel
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Didn't work, after selecting yes twice, my phone just starts like normal, doesn't go to TWRP or factory restore, it is there though because I can boot to it from the flashify app, ah well.
wait...my bad, I was highlighting the wrong one, lol, works great, thanks
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
callihn said:
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
Click to expand...
Click to collapse
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
[email protected] said:
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
Click to expand...
Click to collapse
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
callihn said:
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
Click to expand...
Click to collapse
I'm working on building it from source but keep getting errors and I'm trying it with another device that has Twrp (Moto E 2015) and followed the directions to the T and no luck. So I am trying......... Will let everyone know how it's going.
[email protected] said:
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Click to expand...
Click to collapse
kernel??????????????????????????
im down!
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.
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