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!
Related
Hey Guys,
This is my first post. I have had my SGP for about a year and I thought I would try and install a custom rom. But I think it may have soft bricked my device and I am not sure how to fix it. I was hoping someone may be able to help.
Device: YP-GB70EW(B) 16GB
First tried to flash with this firmware: Eryigit_Rom_PDA_YP-G70_G70ZCKPA.R.3.5-Defult
Odin seemed to flash it fine but when the device rebooted it just loaded the samsung screen and stopped.
so then I tried to go back to stock firmware:CODE_G70ZCKPA_CL767152_REV01_user_low_ship_HOME.tar.md5
and I get the same issue. right how I have the device pungged into my computer and it is on the battery charge screen.
can someone please help me twith a step by step how to fix. I would reely like to get a the first rom I tried working on my device.
Thanks,
Andrew
aday12345 said:
Hey Guys,
This is my first post. I have had my SGP for about a year and I thought I would try and install a custom rom. But I think it may have soft bricked my device and I am not sure how to fix it. I was hoping someone may be able to help.
Device: YP-GB70EW(B) 16GB
First tried to flash with this firmware: Eryigit_Rom_PDA_YP-G70_G70ZCKPA.R.3.5-Defult
Odin seemed to flash it fine but when the device rebooted it just loaded the samsung screen and stopped.
so then I tried to go back to stock firmware:CODE_G70ZCKPA_CL767152_REV01_user_low_ship_HOME.tar.md5
and I get the same issue. right how I have the device pungged into my computer and it is on the battery charge screen.
can someone please help me twith a step by step how to fix. I would reely like to get a the first rom I tried working on my device.
Thanks,
Andrew
Click to expand...
Click to collapse
Well you softbricked your device because y ou took a rom that's not meant for your device. You have a YP-GB70 which is the korean galaxy player 5.0. The erygit and the stock rom are for YP-G70 US and Intl so you will need to find a stock korean rom in order to get it back to normal.
Have you tried wiping data and and do a factory reset in recovery mode BEFORE flashing the firmware?
zaclimon said:
Well you softbricked your device because y ou took a rom that's not meant for your device. You have a YP-GB70 which is the korean galaxy player 5.0. The erygit and the stock rom are for YP-G70 US and Intl so you will need to find a stock korean rom in order to get it back to normal.
Click to expand...
Click to collapse
Korean official ROM are available here:
http://ts.daumcdn.net/custom/blog/8...me.html?http://supportgp.tistory.com/notice/2
don't forget to wipe before flashing
good luck
Thanks I will give the korean stock rom a try.
I thought that Intl was for everywhere but the US.
does anyone know of a good rom like Eryigit that will work on my device?
WT Ho said:
Have you tried wiping data and and do a factory reset in recovery mode BEFORE flashing the firmware?
Click to expand...
Click to collapse
no as I followed the odin flashing instructions that where in the Eryigit rom thread and it said do do the wipe after flashing and some people said that it did not even need to be done at all.
but how I am past that point as the device will not boot past the samsung screen (I assume the samsung screen is the bootloader)
lolo9393 said:
Korean official ROM are available here:
don't forget to wipe before flashing
good luck
Click to expand...
Click to collapse
Thanks,
But how do I do a wipe before flashing with odin if all I have is the samsung boot screen. (I can also get it into download mode)
wipe is done outside odin.*easy"
push and hold together home+vol+power for some seconds then follow given instruction.
lolo9393 said:
wipe is done outside odin.*easy"
push and hold together home+vol+power for some seconds then follow given instruction.
Click to expand...
Click to collapse
thanks for you help I will give that a try does it mater if it is vol + or vol -
aday12345 said:
Thanks,
But how do I do a wipe before flashing with odin if all I have is the samsung boot screen. (I can also get it into download mode)
Click to expand...
Click to collapse
Hey lolo9393,
once I get my device back up on stock I would like to try a good custom rom I have noticed you chatting on some of the other threads and was hoping you can point me to a good stable rom that I can install (ICS would be nice but not required)
No problem,
In case you are ready for custom roms you can investigate the very light and fast* Rice Rom With Ktensi White Wine Theme Rom Build2.
It is rooted and has no more bloatware.
http://soon-s.tistory.com/m/post/view/id/4
Other good choice is the GreenROM HD4.0. It is rooted, fully fonctionnal and bug free.
http://greenview.tistory.com/31
But if you really 'need' ICS ,for me not mature enough and buggy, you can try (at your own risk) this was done by our korean friends.
http://greenview.tistory.com/39
let me know the progress!
anyway, my own feeling about this "very good" device and the peacefull use i have of it (I am not a furious gamer) I don't need ICS, only root is required and mandatory.
regards
lolo9393 said:
No problem,
In case you are ready for custom roms you can investigate the very light and fast* Rice Rom With Ktensi White Wine Theme Rom Build2.
It is rooted and has no more bloatware.
http://soon-s.tistory.com/m/post/view/id/4
Other good choice is the GreenROM HD4.0. It is rooted, fully fonctionnal and bug free.
http://greenview.tistory.com/31
But if you really 'need' ICS ,for me not mature enough and buggy, you can try (at your own risk) this was done by our korean friends.
http://greenview.tistory.com/39
let me know the progress!
anyway, my own feeling about this "very good" device and the peacefull use i have of it (I am not a furious gamer) I don't need ICS, only root is required and mandatory.
regards
Click to expand...
Click to collapse
I agree about ICS (I hope we will see some more options in the future)
I also just need root, want to get rid of the bloat, I would also like to be able to mount a usb flash drive that would be nice.
lolo9393 said:
No problem,
In case you are ready for custom roms you can investigate the very light and fast* Rice Rom With Ktensi White Wine Theme Rom Build2.
It is rooted and has no more bloatware.
http://soon-s.tistory.com/m/post/view/id/4
Other good choice is the GreenROM HD4.0. It is rooted, fully fonctionnal and bug free.
http://greenview.tistory.com/31
But if you really 'need' ICS ,for me not mature enough and buggy, you can try (at your own risk) this was done by our korean friends.
http://greenview.tistory.com/39
let me know the progress!
anyway, my own feeling about this "very good" device and the peacefull use i have of it (I am not a furious gamer) I don't need ICS, only root is required and mandatory.
regards
Click to expand...
Click to collapse
Hey lolo9393,
Sorry to keep bugging you I am just trying to dig my seft out of this mess....
I flashed "CODE_GB70KRKPL_CL985547_REV01_user_low_ship_HOME.tar" and I have got closer but it is still not working now my device gets to the samsung boot screen then it will play the little startup tune and display the "Galaxy Player" label but then it keeps looping on the "Galaxy Player" label.
I did do the wipe data/factory reset and the wipe cashe partition before applying the rom.
when I wipe data I get a bunch of errors:
- e:format_volume: rfs format failed on /dev/block/mmcblk0p16 (/data)
- e:format_volume: rfs format failed on /dev/block/mmcblk0p14 (/dbdata)
- e:format_volume: rfs format failed on /dev/block/mmcblk0p15 (/cashe)
when I wipe cashe:
- e:failed to mount /cashe (no such file or diectory)
- e:Can't mount /cashe/recovery/log
- e:Can't open /cashe/recovery/log
- e:failed to mount /cashe (no such file or diectory)
- e:Can't mount /cashe/recovery/last_log
- e:Can't open /cashe/recovery/last_log
- e:failed to mount /cashe (no such file or diectory)
also do you know of another source for the "Rice Rom With Ktensi White Wine Theme Rom Build2" I click on the TAR image on the page and the link looks to be dead
You are at the point I was six months ago while "playing" with new kernel that was supposed to give me many advantages. What i got was a permanent hard brick with the same advices "devblock not formated".
seems you have some memory block "un formated". It is not related to the pit file, don't touch it please!!!
only means is to put your hands into the grease (don't no if this sentence is english but sound well)
go there and do it in a calm and peacefull area!
http://forum.xda-developers.com/showthread.php?t=1676606
courage
lolo9393 said:
You are at the point I was six months ago while "playing" with new kernel that was supposed to give me many advantages. What i got was a permanent hard brick with the same advices "devblock not formated".
seems you have some memory block "un formated". It is not related to the pit file, don't touch it please!!!
only means is to put your hands into the grease (don't no if this sentence is english but sound well)
go there and do it in a calm and peacefull area!
http://forum.xda-developers.com/showthread.php?t=1676606
courage
Click to expand...
Click to collapse
Thanks,
now this makes me nervous, as I have no knowledge of linux.
I read the thread you provided and if I am right I need to follow th links in the post (#39) that you provided.
I will give this a try and let you know....
Hey lolo9393,
I am not having much luck here, I have installed the SDK tried to run "adb shell" and I get "devices not found". I also tried "adb devices" and no devices are listed. The only way I can get a device to show in the list is when my device is in recovery mode but "adb shell" will still not work.
Any idea?
I have a yp-gb70'stock firm
Sent from my galaxy s using XDA
aday12345 said:
Hey lolo9393,
I am not having much luck here, I have installed the SDK tried to run "adb shell" and I get "devices not found". I also tried "adb devices" and no devices are listed. The only way I can get a device to show in the list is when my device is in recovery mode but "adb shell" will still not work.
Any idea?
Click to expand...
Click to collapse
I know this is "the not easy step" to start because we are not skilled enough.
It is like the drivers are not installed.
have a check again, procedure did work well for me.
seems important
-quote
* Install root kernel via ODIN (said RJ's kernel)
* Start your device normally (do not put your device in DOWNLOAD mode), it's OK if it hangs.
unquote from Chongkwan post n°8
Try again and be patient, it always take time to understand "the first time".
ok I am back, but I want to be rooted....
It does not look like the "Rice Rom With Ktensi White Wine Theme Rom" is available from the link you gave me. (click on the TAR image and I get a 404)
do you have another source?
Again thanks for you help, I would not have been able to do it with out you
Congratulations man,
Just for my knowledge, what was your issue with adb?
What you need is official KPL FW and the rooting kernel, it is what I have today and makes me satisfy I will go with ICS when fully debuged, no hurry!
I have found, thanks to our Russian colleagues, this very good and well organised post:
http://4pda.ru/forum/index.php?showtopic=272433&st=560#entry11474838
4pda.ru is awesome site, we have much to learn from them; only detail is I don't read russian (sadly said)
You have everything needed available here.
In case you really want the "Rice Rom With Ktensi White Wine Theme Rom" lauch a request in the forum to find a new link.
rgds
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!
[update 2] I just summarized a way to backup and restore (all based on other great DEV's work, just put in one place) your TS before your play with your TS here: http://forum.xda-developers.com/showthread.php?p=52820278#post52820278
Go check it if you plan to root your TS!
[update] With the help of cheahcl, I got the latest F/W for 4th List 1/8/2100. With the MTK SP_Flash_Tool, I was able to upload a corrected F/W for my TS and everything goes back to normal!
Thanks for cheahcl for his dump and Lokifish Marz for his All in one tools! You guys really saved my day! (and my TS).
A Quick summary: Do NOT use any method on XDA yet to root or change TWRP recovery! It seems the TS of 4th list is different in some way than the ones before which render most of stuffs here invalid. However, fear not to play around since now we have a way to go back to stock!
In my experience, I found that it's really difficult to truly brick a MTK based system. The system will just reject flashing at slightest sign that a F/W is not compatible. The only cache is you need to have the "correct" F/W specifically for your TS!
In my observation, OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in (At least F/W configuration) of the 3rd or earlier 1/8/2100.
------------------------below is my original story of what I tried and failed--------------------------
Just got mine (1/8/2100) 5 hrs ago! I am on the 4th list. The delivery in FAST!
The watch starts normally. I played with it for a while, than decided to root it, install TWRP and apply the security hack made by +Lokifish Marz
Now I have a brick! Just after 30 min I receive the watch!
<<Can anyone help me here?>>
First of all, in respecting to all great DEVs, I have NO intention to blame anyone else but myself. (I did this to my own watch!)
Second, I have been rooting Android since Cupcake day, so I am not a Noob... (or so I think...) I am very familiar with ADB/fastboot... and use almost daily.
So here is the guide to brick. If Anyone have any idea please help me out!
--------------------------------------------------------------------------------------------------
1st, I tried to use this tool to root+TWRP+scurity patch http://forum.xda-developers.com/showthread.php?t=2713183&page=2 knowing it's NOT tested against 1/8/2100. I just tried anyway... The script went with a lot of errors, it seems the script cannot locate correct files but still push the security patched files into the /system/app (and other places).
I turn on the watch, but it just stuck at boot logo (the orange "Truesmart" logo without animation)
Also, the Recovery is still stock, TWRP is no where to be seen.
Since ADB still works, I adb reboot couple times, pull the battery, let the watch run for 2hrs, etc... Nothing works. The watch just stuck at the boot logo.
Than I follow this thread http://forum.xda-developers.com/showthread.php?t=2641261 and http://forum.xda-developers.com/showthread.php?t=2641261 with Stock firmware downloaded from http://d-h.st/users/Lokifish Marz/?fld_id=30814#files (Omate_1-8_2100_TrueSmart_20140328.zip)
I installed all drivers, restarts my Win 7 (x86) pc (several times), and after several attempts the Flashtool just flash in the Firmware.
The Tools flash with a green Check mark, indicating everything is ok!
However the watch just become a brick after this....
Than this completed the brick process! Now the watch won't even turn on, when I try to use Flash tool again, it always say S_FT_ENABLE_DRAM_FAIL. Google this and you find it's due to flashing wrong F/W, but I don't know where went wrong!
Anyone else have same problem or it's just me? Anyone have solution?
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
funky0308 said:
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Ha! Very true! I think you are right! I believe Omate have many segmentation on their HW/SW, even with same model number.... A lot of things changes between versions which makes the "factory image" not compatible....
Anyone has the latest (4th list) 1/8/2100 TS who could dump their whole image for me would be helpful...
I would like to help you but mine is 2nd list and it's still on customs office...
Omate shipment experts, you just gotta love them....
Sent from my C6903 using Tapatalk
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Lokifish Marz said:
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Click to expand...
Click to collapse
Thanks Lokifish for your comment... Is there anyway to get a latest F/W? If you know anyone I could contact, please PM me... Thanks!
Anyone have yet received a 1/8/2100 on 4th list could PM me a Factory F/W dump?
I tried another XP PC with all steps checked and rechecked but still... No luck...
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
cheahcl said:
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
Click to expand...
Click to collapse
Thanks a lot! First of all, Currently don't do anything posted on XDA yet since most of them will not work with this version of TS... (This is where I am now...)
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. it's okay to just provide the file you got after finishing the step "C) Read back the ROM with MTK Droid Tools" I should be able to do the Step D) and after myself.
Thanks a lot for your help!
Lokifish Marz said:
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
Click to expand...
Click to collapse
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
ok will get it to tonight. about 6 hours time. cheers
lssong99 said:
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
Click to expand...
Click to collapse
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Lokifish Marz said:
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Click to expand...
Click to collapse
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
lssong99 said:
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
cheahcl said:
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
Click to expand...
Click to collapse
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
lssong99 said:
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
Click to expand...
Click to collapse
don't sweat it, haha i needed to backup my original firmware as well anyways, seeing how scarce it is around here and all the weird discrepancies in HW/SW versions. good to know i can always fall back on this file. haha yeah i've also backed up my imei. time to play around and see.
cheers
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Spoetnicus said:
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Click to expand...
Click to collapse
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
lssong99 said:
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
Click to expand...
Click to collapse
Thanks!
Im pretty sure that I was on 'Omate_TrueSmart_20140513.103530_V2.0' before I bricked it, so that gives hope
I dont have it with me right now, but Ill try it as soon as I get back home on monday
Thanks again for the tutorials and reply
lssong99 said:
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Click to expand...
Click to collapse
HEY! It worked
I'm back at a functional Truesmart
Thank you soo much
And in case three smiley's aren't enough:
Also, quick note for other people bricking their phone, my issue (after I bricked it again), was that I used an app to change the density property, which broke the boot of the watch.
The app that broke my watch was: https://play.google.com/store/apps/details?id=com.birdapi.android.dpi
Hi,
I followed your instructions, but my God damned Windows 8.1 doesn't see my God damned Android 4.4.2, so I "adb devices" command -- pc doesn't see my Android. "file transfer (MTP) files" command is useless.
Is there any of you in the whole wide world could help me?
My phone is in recovery mode can't boot stuck in boot loop.
Nobody answeres. This is said to be the best geeks' forum.
Sorry, I am disappointed, fed up, etc. as none of you give a damn about my f***ing problem.
Thx if any...
You could try using the latest adb and some universal driver ***,
but not much use from ADB really, if it has a stock recovery Then also
making update zip s could be problematic... signing...
Best to try contacting the manufacturer or seller, what ever, and try to get the firmware + tools.
http://smartnavon.eu/
http://hungaroflotta.hu/page-7.html
http://hungaroflotta.hu/contact.html
If no luck, try to find out its soc. You could even try to open the damn thing...
Or just assume it's a MTK. If so -> MTK drivers, DroidTool, Wwr, SP_FlashTool, etc..
and make a backup. Worked ok? Good! Now find someone having the same piece of...
and ask her to do the same and share his system...
Good luck! :fingers-crossed::good:
*** For example this installer of mine. Contains universal adb driver and adb/fastboot downloader
https://forum.xda-developers.com/an...taller-universal-adb-driver-package-t3595277/
Thx 4 UR reply!
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Don't open it yet! :laugh: I did a bit more searching. It's a MT6572. This "dazexy" fellow
most likely can help if you cannot get that factory firmware.
http://forum.gsmhosting.com/vbb/f29...nfinity-box-725574-post10962286/#post10962286
(gsmhosting is not working at the moment, so here is the page at google's cache:
http://webcache.googleusercontent.c...rum.gsmhosting.com/vbb/10962286-post1173.html )
At least he helped "kaller1" at the same forum.... see the second post here.
(if needed you can find kaller1's email by clicking his paypal donate button)
http://forum.gsmhosting.com/vbb/f82...nck-dongle-1314877/index147.html#post11354667
(gsmhosting is not working at the moment, so here is the page at google's cache:
http://webcache.googleusercontent.c...d-phones-via-nck-dongle-1314877/index147.html )
Some more helpful people having d402??
https://mobilarena.hu/tema/navon_mizu_d402/hsz_1-50.html
So no worry, I think your problem will be solved. :highfive: (Hopefully...)
(if it is that Navon Mizu D402, as I assumed because of this post
https://forum.xda-developers.com/showthread.php?t=3501143 )
edit: gsmhosting works again. The second link (kaller1) updated to be more accurate.
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Here is another fellow who gives a damn. "donrico" is sharing the full rom here
http://forum.gsmkabelek.com/showthread.php?28404-navon-d402-rom&p=250246&viewfull=1#post250246
Because that 4shared site is a bit nasty, i copied it to mega, here
https://mega.nz/#!v4MgVIbJ!htsUcjHSrwwGIDuTeNRMAXKhxZOvVxJ8mnY3vMZoVks
Taking a full backup first might be a good idea.
SP_Flashtool should do the trick. You probably
can use the scatter file from that rom dump.
Or make your own: https://forum.hovatek.com/thread-21970.html
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Sub forum changed... Okay, let us continue here if needed.
Though you should be able to fix that damn thing now...
:victory:
Thank you so much for making such a hard effort to help me! ?
I'll do my best and will keep you informed.
Partitions "nvram" and in in my case also "pro_info" are important backups.
Nvram contains IMEI values etc... anyway it can be important to save it/them.
And pro_info might have some extra values defined in it. At least if the device
has some faked firmware showing wrong hardware values like in my case.
Then there might be some real values needed, defined there along with the faked ones...
I'm no MTK expert but managed to fix my tablet by restoring those partitions...
Ehh!
I've read all the info you linked. ????
OMG!
Well, I guess that I should download the rom.
After that do I have to do all the instructions?
How will my pc be able to see my phone?
I need no data backup.
I swear I got in touch with the store in which I bought the data cable and asked if it is really a data cable and not just a charging one.
I can do anything I just need to know the steps to be taken one by one.
There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Thanks for your kind reply in advance!
Nikkka said:
Ehh!
1. After that do I have to do all the instructions?
2. How will my pc be able to see my phone?
<snip>
3. There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Thanks for your kind reply in advance!
Click to expand...
Click to collapse
1. I can relate your "shock". That Wwr route isn't the easiest one, I can imagine.
Haven't done it myself. Maybe that SP_FlashTool + scatter file is enough for
the backup. If you have those IMEI numbers saved you probably can skip
the backup, but as I said I'm no expert, so you might want to do some
Googling before deciding anything...
2. Install the MTK drivers (search). any tool will need them too.
3. IDK. Maybe someone else has an answer to this?
Checked. The stock recovery doesn't use test keys, so making update zip is not possible.
Nikkka said:
Ehh!
There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Click to expand...
Click to collapse
Checked SELinuxModeChanger's info - and its source code too.
It shouldn't do any writing that factory reset wouldn't remove.
https://forum.xda-developers.com/showthread.php?t=2524485
CXZa said:
Checked. The stock recovery doesn't use test keys, so making update zip is not possible.
Click to expand...
Click to collapse
Easiest would be that the vendor would give you a full OTA/recovery update zip package.
(Not such that just patches the old one. ) That most likely would fix it.
CXZa said:
Checked SELinuxModeChanger's info - and its source code too.
It shouldn't do any writing that factory reset wouldn't remove.
https://forum.xda-developers.com/showthread.php?t=2524485
Easiest would be that the vendor would give you a full OTA/recovery update zip package.
(Not such that just patches the old one. ) That most likely would fix it.
Click to expand...
Click to collapse
Yep. Thanks.
Well, actually the antivirus Zemana asked if I wanted to make SELinuxModeChanger a part of the system/a system file. I agreed. I made the wrong decision. I used ES File Manager to delete SELinuxModeChanger. Well, I succeeded in half... but failed to delete it from all system maps and couldn't reinstall it again. Rebooted... The rest is history...
I guess phone thinks that it has a corrupted system and that's why it doesn't boot.
Navon... They never ever update. No system security patches ever.
Actually, 1 yr ago I had a problem nobody was able to help. I was advised to take my phone to Navon asking for refurbishing. I had no money and I wanted to fix the problem myself anyway. It took a year, but I found out how to fix it. ES File Manager was the key.
Nikkka said:
Navon... They never ever update. No system security patches ever.
Actually, 1 yr ago I had a problem nobody was able to help. I was advised to take my phone to Navon asking for refurbishing. I had no money and I wanted to fix the problem myself anyway. It took a year, but I found out how to fix it. ES File Manager was the key.
Click to expand...
Click to collapse
Yes I have seen that post. For "fun" I added the fota values from your build.prop to
my tablet and installed the apks needed for the OTA update. The OTA server
http://adups.cn didn't respond. It seems that the programs needs to be
updated or they don't provide updates for the older models...
Something to read....
How to use SP Flash tool to backup Mediatek firmware
https://forum.hovatek.com/thread-526.html
How to Flash Stock Rom using Smart Phone Flash Tool
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
How to Flash IMEI
https://androidmtk.com/use-sn-write-tool
How to Backup and Restore IMEI/ NVRAM data on Mediatek Chipset Android Device
h t t p s://w w w . getdroidtips.com/backup-restore-imei-nvram-data-mediatek/
(Bad site, sorry. While the info in this article might be ok, all at this site is not.
So better to search if the info can be found elsewhere.)
+ lots of more similar articles + videos. Almost too much really...
CXZa said:
Yes I have seen that post. For "fun" I added the fota values from your build.prop to
my tablet and installed the apks needed for the OTA update. The OTA server
http://adups.cn didn't respond. It seems that the programs needs to be
updated or they don't provide updates for the older models...
Something to read....
How to use SP Flash tool to backup Mediatek firmware
https://forum.hovatek.com/thread-526.html
How to Flash Stock Rom using Smart Phone Flash Tool
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
How to Flash IMEI
https://androidmtk.com/use-sn-write-tool
How to Backup and Restore IMEI/ NVRAM data on Mediatek Chipset Android Device
https://www.getdroidtips.com/backup-restore-imei-nvram-data-mediatek/
+ lots of more similar articles + videos. Almost too much really...
Click to expand...
Click to collapse
Thank you so much for your trying to help me!
I guess I need some time to let it go for a while.
It came across my mind that 1 yr ago my phone was rooted also. Do you think that having my phone rooted makes Recovery Mode especially Factory Reset disabled?
Unfortunately twrp is not compatible with KitKat.
I guess it will be a hard effort to make my phone work again. I seem to give it up. Unfortunately, sending the phone to Navon for refurbishing... would cost too much and phone must be sent by post (!!!). It is a great phone, but customer service at Navon is...
Nikkka said:
It came across my mind that 1 yr ago my phone was rooted also. Do you think that having my phone rooted makes Recovery Mode especially Factory Reset disabled?
Unfortunately twrp is not compatible with KitKat.
Click to expand...
Click to collapse
I don't think that rooting is causing it. How do you know that
Factory Reset doesn't work?
You have a twrp for it? Older one, or what do you mean?
Nikkka said:
I guess it will be a hard effort to make my phone work again.
Click to expand...
Click to collapse
Maybe not that hard if you're able to connect to PC... but..
(it looks like that at the moment I cannot make a connection either, LOL
re-installing the drivers probably fixes it, IDK, have to check it some day... )
---
That OTA update needed (at least) one program more (to be run as a service).
Did that too. And I also disabled the firewall that was blocking the connection. :laugh:
It just says that my system is up to date. (Changing version numbers etc. doesn't help).
The server response hints to http://europedownhw.mayitek.com/ site
that seems to be dead...
Navon...
https://forum.hovatek.com/thread-25956-post-155741.html#pid155741
Oh yeah? http://smartnavon.eu/smartphones/navon-t503 (not even an old model)
https://logout.hu/bejegyzes/cappa72/sp_flashtool_readback_kiolvaso_opcio_hasznalata_gy.html
https://itcafe.hu/tema/android_dual_sim_ket_sim_okostelefonok_topikja/hsz_16132-16132.html
[QUOTE
CXZa said:
I don't think that rooting is causing it. How do you know that
Factory Reset doesn't work?
You have a twrp for it? Older one, or what do you mean?
Factory Reset doesn't work. I mean that in Recovery Mode it doesn't matter how many times I do Factory Reset nothing happens.
I have no twrp. Only KingRoot was able to root my phone. TWRP said my phone not compatible with it.
Click to expand...
Click to collapse
Nikkka said:
Thank you so much for your trying to help me!
I guess I need some time to let it go for a while.
Click to expand...
Click to collapse
While you're are letting go, you could read some stuff linked below. Good
instructions. What to do and what not to do. (Unlike at that "getdroidtips"
site I linked earlier. Some of the tips and articles there are total rubbish.
Mixed stuff copied somewhere else, I guess. Some might work, but not all.
Also they use wrong words in article names to get better Google rankings.)
SP Flash Tool + MediaTek MT65xx drivers download and installation guide including bricked devices
Download MTK Drivers (32 & 64 bit) XP Vista Win7 Win8
Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Drivers installation tutorial (Might be useful with win8 too.)
Download SP Flash Tool v3 & v5 – Latest versions ( Tip: read to the end)
Remove, Disable & Uninstall MTK USB Drivers and inactive COM Ports – USBDeview (if having driver problems)
(And I also sent you some info in Hungarian already in the previous post. Backup etc.)
Again. just for fun sake, I tried again if my MTK tablet/phone would be recognized by SP flash tool.
No luck. Previously it wasn't a problem. Still, the adb/fastboot works okay.
So, some problem with MTK drivers. I have used SP_Flashtool, BeTools,, even older ones
like WiseLinkTool. And maybe some that were between those two.
Well, I don't have any good reason to fix those driver problems at the moment,
everything works ok, but still it kind of sucks.
Anyway adb/fastboot works okay. And that is the problem mentioned originally in the title.
So, does the fastboot work?
With fastboot, if it works, you might be able to boot some modified recovery without flashing and then maybe do some backups etc.
My adb driver package, mentioned in my signature has some options to remove the
old adb installations and the old (maybe problematic) values from the registry...
USBDeview is better choice in some situations though...
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