I wanted to make a thread to let everyone know how the port is coming. So here it is.
Right now we have an incomplete device tree, found here:
https://github.com/Azimoto9/android_device_samsung_cprimeltemtr
We're currently working on getting a recovery to build so that we can try to build cm.
But heres the thing,
its literally just two people actually working on the project, and we need some help. So if you're a developer or even want to become a developer and are willing to put time in, whether to learn or help us port cm, we need you.
A great resource for learning android development is XDA-University.com. Between that and the cyanogenmod wiki, it's how I am still learning what to do. Unfortunately there is no generic guide on how to port cm to a device (or at least not a complete one).
So if you would like to contribute in some way, head over to webchat.freenode.net and join the channel #G360T1 or message me on XDA. if webchat isnt working for you, you can use Hexchat for windows or a similar irc client.
So that was both an update on current progress and a plea to the community for help on this one. Thanks for reading.
Looking forward to this and willing to help any way I can!
People believe that if they manage to get Cyanogenmod for our Core Prime, is compatible with the g360m? Since we have this model in Latin America, and not stand lagwiz :v . Regards
fededelg said:
People believe that if they manage to get Cyanogenmod for our Core Prime, is compatible with the g360m? Since we have this model in Latin America, and not stand lagwiz :v . Regards
Click to expand...
Click to collapse
Maybe, but it may require some variant work.
I feel like I gotta say that it's so hard to know what's going on in IRC. I feel totally uninformed. At least with XDA we can look back and see what we missed and get caught up. I wish I could run IRC 24/7 to stay in the loop, but unfortunately I can't.
Sent from my SM-G360T1 using Tapatalk
bogarty said:
I feel like I gotta say that it's so hard to know what's going on in IRC. I feel totally uninformed. At least with XDA we can look back and see what we missed and get caught up. I wish I could run IRC 24/7 to stay in the loop, but unfortunately I can't.
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
I might actually be able to help with that. I can try to make my bot output logs somehow, but it may require some work, so don't expect it instantly, lol.
This is great news. I'd like to take this as an opportunity to learn some new things but unfortunately I don't quite have much time to invest at the moment. I'll be keeping an eye on this and if free time opens up I'll be jumping in. I have some basic knowledge of the ins and outs of android and linux but I know I definitely need to learn a lot more.
We're getting closer... ?
Sent from my SM-G360T1 using Tapatalk
I ll contribute with this project but need some files from this device
Dreamstar said:
I ll contribute with this project but need some files from this device
Click to expand...
Click to collapse
Which files
Sent from my SM-G360T1 using Tapatalk
Boot.img , Recovery.img , and partition blocks
Dreamstar said:
Boot.img , Recovery.img , and partition blocks
Click to expand...
Click to collapse
How do I or where do I get the partition noob here
https://www.androidfilehost.com/?fid=24351979186683928
Or here is the rooted stock firmware if that helps
is this project still alive?
Yes, freenode #g360t1 is where you can find more regular updates. @galaxykeks
Sent from my SM-T350 using Tapatalk
Dreamstar said:
Boot.img , Recovery.img , and partition blocks
Click to expand...
Click to collapse
About partition blocks, would you want partition dumps? Or the listing of all of the partitions?
"Partition Blocks"...
Forgive me for speaking out of turn, but I'm guessing what was really being asked for was the partition image table (pit file). I find myself in need of the very same thing. even Odin requires one if you are repartitioning the phone -OR- just rewriting the table to repair incidental damage (believe it or not partition table damage does happen, really, lol). Heimdall wants one too. Somehow while trying to root my G360T1 I got TWRP to flash ok. I booted into it just once;; something was unstable, it rebooted randomly and disappeared. No matter what I try it just boots to the Samsung logo and hangs, kernel and/or recovery. The stock firmware has issues writing any one of the .mbn component firmware files, seemingly random in choice which one. the phone display reports "SECURE CHECK FAIL:" and the odin logfile shows "FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed." I thought aboot.mbn was the only partition Samsung was locking....
Anyway, the problem is that I now have no access to the partition table so I can retrieve a copy. Download mode is all that works. A pit file for this beast is nowhere apparent no matter how diligently my browser search engines are applied to the problem. At least I could be sure the firmware gets written to at the proper locations (bricked an S3 that way:cyclops
That's all that's keeping me from offering to help with the port. I am/was a software engineer with spare cycles, a development environment including Ubuntu linux, as well as a keen interest in diving into deeper android waters (e.g. building the kernel).I'm pretty sure i'm ready and equal to the challenge. Maybe I wouldn't make as many bricks if I knew a bit more, lol. And hey, I've finally got my personal assistant with me 24/7 and I've got a multicore Linux computer in my pocket no matter where I go. I like it!
OK, I yield the thread...
riches2rags I will be happy to get you the PIT file when I get a free moment, hopefully within the next hour or so
Edit: Doing it now, sorry for the holdup
@riches2rags sorry again for the holdup. I generated this PIT file with the android emulator app, from a completely stock rooted firmware. I had made a lot of changes previously, so I wiped everything except external SD (including internal storage), used Odin to flash the official firmware, booted up the startup wizard, skipping everything but Wi-Fi settings, and rooted. Then I installed the android terminal app using the apk file and dd-ed the file I link to below (long story short, as stock as possible):
https://www.androidfilehost.com/?fid=24459283995298587
Thanks thisisapoorusernamechoice! I just d/l'd it. I'm tired & it's late so I won't get to try it for a few hours, but I'm stoked.
On a side note, I see Hartford as your location. As in Connecticut, right? Funny, I grew up across the river in Glastonbury and got my BSEE/BSCS degrees at UConn ('83). Small world
riches2rags said:
On a side note, I see Hartford as your location. As in Connecticut, right? Funny, I grew up across the river in Glastonbury and got my BSEE/BSCS degrees at UConn ('83). Small world
Click to expand...
Click to collapse
Wow it really is a small world, I grew up in Bolton, right next to Glastonbury, and I played soccer in Glastonbury all the time, they have really nice indoor and outdoor facilities. And I can't even count how many people I know who went to UConn, including both my paternal grandparents. Cool stuff :good:
Related
Please note, this is not compatible with the JB OTA - use the app in the Play store instead for now. Thanks!
Howdy all! So, it's time for me to dig out my release thread template... you know what that means?
The LG Optimus G is now unlocked.
Both the AT&T Version and the Sprint Version have been successfully unlocked with this method.
(To answer your question, if you're wondering, we're going to work on the Canadian version next, then the Korean version)
First off, I'd like to write a few words to LG:
Dear LG, a product will rise and fall on the shoulders of it's community.
If you lock a device, and shut out your community, you lose the backing of a very vocal group of people. When you lose the backing of your community, they no longer recommend your product, and you lose money. HTC has discovered this recently.
Please support your development community, we understand product security plays a role here, but ensure that you cater to your community still.
The second you try to fight your development community by locking them out of your products is the second that I will cease to recommend your products.
Keep this in mind, and I assure you that you will find yourself on the top of the game.
With all of that said, let's get back to the goodies.
What is this?!
This is Project FreeGee, silly!
Have an Optimus G ? This project will allow you to unlock your bootloader, and install whatever you want.
Click to expand...
Click to collapse
How does this work?
For the moment, that is a trade secret. Suffice it to say that we put some ones and zeros in the right places, and good things happen.
This is also my opportunity to say do not allow any OTAs to install without asking if they are compatible. LG could possibly patch this in such a manner that makes it rather hard to ever exploit it again.
Click to expand...
Click to collapse
I'm a skeptic. I demand proof!
Alrighty, here it is:
Once again, taken with my HTC Vivid, that would rather mute me than let me speak.
Damn "nose elimination"! I am not noise, and I will not be silenced! (mmhmhmhpmhmp!!)
Click to expand...
Click to collapse
Okay, I'm game. Where do I get it?
Version 0.3 has a confirmed bug-- camera app crashes phone after a few seconds!
If you have 0.3 installed, simply download this, extract the .zip, and extract the .tar file. Inside the freegee-working directory, you'll find boot-att-freegee.img .
Boot your phone to fastboot, then fastboot flash boot /path/to/boot-att-freegee.img
I will release a quick fix .zip for flashing in CWM tomorrow.
Current Version: 0.5
Changelog:
New in v0.5 Removed LG Security check. You are now free to remove any and all apps.
http://downloads.codefi.re/thecubed/lgoptimusg/att/freegee/FreeGee-0.5_ATT.zip
Currently, the download is Windows-only. I will make a OSX/Linux/Windows version soon!
Click to expand...
Click to collapse
FAQ
Can I flash an OTA after installing this?
No. Flashing an OTA could contain a new bootloader, and it would replace the one we have put on your device. If you flash the new OTA, and it replaces the bootloader but not the boot.img, you could be left in a situation where you could not boot the phone due to a security error. Once you're in that position, the only thing you can do is LGNPST back to stock-- and even then, it is possible that an OTA could enable an anti-rollback feature which would disable LGNPST.
Does this mean I can flash custom ROMs now?
Yes. However, the custom ROM must be made for your device. We're working on a decrapified stock ROM, and AOSP ROMs as well. Be patient for those to come.
Can I install a Nexus 4 system image and boot.img and have it work?
We've tested that, and the answer is no, not yet. Some work needs to be done, but once we figure it out, we'll have a quick and easy AOSP ROM.
Does this mean that we can use the Nexus 4 sources (kernel and android) ?
Short answer: Yes.
This phone is essentially a Nexus 4, with minor differences in GPIOs, memory address space, and partition table layouts.
Kernel source is iffy, since we've got Eco mode and a few other things that actually make me like the Optimus kernel more than the Nexus kernel.
However, this discussion is best suited for a new post.
How can I uninstall this?
I'm working on an easy-uninstall for this as well. Stay tuned for the links...
Click to expand...
Click to collapse
Important Information
To enter bootloader, hold volume UP and power.
Upon entering the bootloader, you will notice that there is no 'menu' to enter fastboot or recovery. Unfortunately, since the stars didn't align properly, we were unable to tell the new bootloader where to load the images that contain the menu from.
In light of that, you'll have to navigate the menu blind. Use the volume keys to change selection, and the power key to select.
The choices are (in order of pressing volume down):
Start - boot the phone normally [already selected]
Restart Bootloader - reboot into the bootloader
Recovery Mode - enter recovery (CWM)
Power Off - powers the phone off
So, to get to Recovery, you would press volume down twice then power.
If you have trouble with this, watch my video below for a demonstration.
Click to expand...
Click to collapse
Instructions!
Please note: this requires root before you can install this! If you haven't rooted your phone yet, now is the time to do so.
Also, ensure that you have ADB drivers installed. This WILL NOT WORK without them.
Before we begin: please make sure you have USB Debugging turned on, your phone is in "Charge Only" mode, and your phone's screen is on and unlocked.
This will allow you to see the root access prompt if your phone asks for it.
Download the .zip from this post
Extract it somewhere on your hard drive
Ensure your screen is on and unlocked
Run the "freegee.bat" script, and follow the instructions.
Do not run this as administrator! the install will fail if you do so.
Once the unlock is complete, check to make sure you have a "backups" folder now in the folder where you put FreeGee. If not, DO NOT REBOOT your phone.
Even a failed unlock will still show the 'congratulations you're unlocked!' text, read the output to see if you have errors!
You should not see any "adb.exe not found" errors, or "tar: invalid magic" errors. Those would be errors in the script.
An error which you can ignore is "No space left on device" after it says erasing old recovery and boot. That's just a side effect of how we clear the old images out.
Click to expand...
Click to collapse
Contact Information
"Mister Cubed, how do I talk to you?"
That's easy! Hop on IRC and join me on Freenode in #lg-optimus-g . I'm in there as IOMonster (or IOMonster_desk, or IOMonster_work, depending on where I am)
There's also a lot of other cool people in there too!
When you hop in IRC, if you've got a question, just ask it. Don't say "halp! i does brick'd my phone, and i dunno wat to does?!!", but rather "can anyone help? my phone is stuck in fastboot mode, and I can't get out of it. I flashed <xyz> and now I'm stuck here."
Asking your full question (even though it might be a long message) helps us figure out the best way to assist you, without us having to lead the conversation and ask all the questions for you.
Also, on IRC (for those of you who have never used IRC) if you say someone's name, it will 'ping' (also called 'highlight') them. This tells us that someone is talking to us. So, if you pop in IRC and say "IOMonster, it worked!", I'll get a notification, and will probably say "that's awesome!" in response.
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the assistance of the following people:
Shelnutt2
g33k3r
kmdm
synergy
jcase
sextape
xboxfanj
...and the support of the entire #lg-optimus-g IRC channel
A project like this is really only a sum of it's parts, and in our case, we're over 9,000!
Please make sure to tell someone on this list that they're awesome if you see them on IRC or (*gasp!*) in real life.
Click to expand...
Click to collapse
All right, that about sums up my post. Did I forget anything? Let me know below...
Can't wait!
Great work guys! Cant wait to lend a hand getting this to us Canadians!!
Yes!
Sent from my LG-E970 using Tapatalk 2
Here we go. Lets make this LG OG what it should have been from the beginning.
Thanks for all the hard work.
Sent from my LG-E970 using xda premium
Thanks once again to you and the project team for your efforts and congratulations on the work completed so far! I will definitely be a willing participant when you guys get around to the Korean model(s). Unsure how much difference there will be in the 3 carriers' for the Korean devices.
Sent from my LG-F180L using xda app-developers app
woot!
I dont even have an lg og and im excited.
Hey thecubed,
Do you guys have the group set up, so I can donate?:good:
Wooo thanks guys. I'll definitely be donating this Friday when I get paid. This was really quick. =D Great work to the whole team.
Sent from my LG-E970 using xda premium
TheCubed!! You (and your team) are my HERO! Thank you for all your hard work.
Q : Is there an option we need to set that will not allow LG to install any OTA updates without my permission? The last update was pushed to my phone and I had no option to stop it from happening.
Awesome work....can't wait...thank you very much!!
Sweet
Looking forward to the official release. Thanks for the good work.
you guys are awesome
Now I can retire my Inspire 4G. I tend to wait for pretty massive spec bumps to happen before I upgrade, and ditching the landscape sliding qwerty was a big deal. However, I'll be damned to something awful before having a phone incapable of a few dozen GB's of capacity. F*** the cloud.
I'm going to best buy later today. Thank you, thecubed. Ideally I'd just like to subscribe to you on Amazon Payments for a while, otherwise I would forget.
Got it
Globalrebel said:
Q : Is there an option we need to set that will not allow LG to install any OTA updates without my permission? The last update was pushed to my phone and I had no option to stop it from happening.
Click to expand...
Click to collapse
I'm wondering the same..
I'm ordering an LGOG when I get home today. It'll be here by Wednesday most likely.
I'll be in touch on IRC. (OverTheStars)
this is great, I thought about not buying this device until you did this! I was going to wait!
just got the phone ....bring on some pure jelly!!!!
when is this going public?
cant wait lol
Did this make it out yet? How's the testing going?
And now we need some ROM devs.
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!
I'm just stepping over to the big-dog conversation for a hot minute because there's just not much goin' on for sch-l435 yet (Verizon S4 Mini).
Really, I'm wanting to install ClockworkMod recovery so that I can create full backups. Some of you will get a good laugh out of this next bit ...
I bought my brand new mini, pulled it from the box, rooted, tweaked, designed, froze some bloat (TB) and then thought "I gotta back this baby up properly".
So, I downloaded a recovery install image from here: http://www.clockworkmod.com/rommanager - the version that reads Samsung Galaxy S4 (Verizon)
... but installed it using LINUX COMMANDS FOR THE WRONG DEVICE and NUKED my internal memory hahaha. I was tired. I literally copied/pasted linux commands for some obscure tablet. Total fail on my part.
She's fully repaired, courtesy of these guys: http://mobiletechvideos.mybigcommerce.com/
So, here I am and I still would like to have software that reliably clones/zips/contains an extractable backup with all of the settings and cache intact. TWRP just doesn't feel right. Something about it seems off/unreliable.
Questions I have for you, great owners of the larger, superior device
(a) is my phone formatted in the very same way as yours in terms of directories and volume info?
(b) will your version of Clockwork recovery work with the Mini?
(c) If not, is there an alternative solution that will *reliably* compress a cloned copy of my phone into a singular zip file that can later be extracted should my phone get wonky?
Shanks!
Just trying to help here .. I think people will need to know much more about the device in order to help you. I'm no dev just trying to get you closer to where you want to be.
Good luck! Hope your bootloader is unlocked
Sent from my SCH-I545 using xda app-developers app
Oh, I think there's plenty of information in my initial post to start off with, ie: what phone I'm using, what I'm intending to do, the yet-to-be-explored development status of said model (sch-l435) and my reasoning for questions to the owner's of it's big brother.
I'm game to provide further *specific* information upon request.
Whatever it takes.
RobinDean said:
Oh, I think there's plenty of information in my initial post to start off with, ie: what phone I'm using, what I'm intending to do, the yet-to-be-explored development status of said model (sch-l435) and my reasoning for questions to the owner's of it's big brother.
I'm game to provide further *specific* information upon request.
Whatever it takes.
Click to expand...
Click to collapse
don't expect alot here as this is the S4 forum...sooner or later a forum should be set for the mini
I respectfully appreciate that and should anyone know anything regarding my issue off-hand, feel free to PM me. I'll bow-out of the topic here so as to keep my intrusion to a minimum.
RobinDean said:
I respectfully appreciate that and should anyone know anything regarding my issue off-hand, feel free to PM me. I'll bow-out of the topic here so as to keep my intrusion to a minimum.
Click to expand...
Click to collapse
most likely the bootloader is locked in same manor as S4 is and you can't load a recovery on it like you tried to do.
I used linux commands initially, which is what fried the phone (got it back, good as new).
Are rooted S4 users able to install CWM Recovery independently in any way or are you guys forced to flash a ROM that happens to include it?
RobinDean said:
I used linux commands initially, which is what fried the phone (got it back, good as new).
Are rooted S4 users able to install CWM Recovery independently in any way or are you guys forced to flash a ROM that happens to include it?
Click to expand...
Click to collapse
Can't do either. ...since bootloader is totally locked down since mdk. Our only Avenue is safestrap and a few compatible roms
safestrap enabled, Hyperdrive driven
[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 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