ive looking and i couldnt find one. does anyone have one that i dont need to have an unlocked bootloader?
Not physically possible. If you need customization, use root with the stock rom and be very careful not to brick.
how would it not be possible? just use a stock kernel and you should be good. thats what we did with the atrix 2 since the bootloaders locked.
Don't think you can put a custom recovery on without unlocking the bootloader. No recovery = no flashing ROMs
vegandroid said:
how would it not be possible? just use a stock kernel and you should be good. thats what we did with the atrix 2 since the bootloaders locked.
Click to expand...
Click to collapse
Don't even start on that bootstrap debacle with moto phones. It was absolutely horrid for flashing anything and was not nearly powerful enough for me. The hassle of using a neutered recovery instead of the real thing is just not worth it, even considering the warrantee.
le rustle face
Keion said:
Don't even start on that bootstrap debacle with moto phones. It was absolutely horrid for flashing anything and was not nearly powerful enough for me. The hassle of using a neutered recovery instead of the real thing is just not worth it, even considering the warrantee.
le rustle face
Click to expand...
Click to collapse
.... I fail to see the point of your post. I didn't ask for your opinion on Motorola or what works best for you. Style on topic dude.
Sent from my SAMSUNG-SGH-I747 using xda premium
So there is a way to install custom ROM's without unlocking the bootloader? If so, I'd love to know how!!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
The problem is, the methods used on those Motorola phones are very hackish, and not recommended if alternatives are present. And since the TF700 is unlockable, its extremely unlikely those methods will ever be duplicated since those who want to mod can do so without restrictions.
Just look at the OG Atrix community... the instant an unlockable bootloader was leaked, development for those hackish methods immediately halted. Someone ported 2nd init days or weeks before that happened, and nothing was ever written to use it because it simply wasnt needed anymore.
jtrosky said:
So there is a way to install custom ROM's without unlocking the bootloader? If so, I'd love to know how!!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
+1. If there was any way to get around Asus's crappy unlocking the bootloader voids the warranty thing I'd jump right on it. I also didn't know that type of thing was possible...
vegandroid said:
ive looking and i couldnt find one. does anyone have one that i dont need to have an unlocked bootloader?
Click to expand...
Click to collapse
Did I read that you were going to try to port paranoidandroid to the TF700 last night or was that one of my weird obsessive Infinity dreams ?? I wish you luck if you are going to try - we need a few more devs around these parts.
I personally wasn't worrying about voiding the warranty considering it rooting voided on all the other devices I've had. I'm more waiting for a reason to unlock the boot loader. It's just a nice bonus that rooting doesn't.
I just say wait till you have a reason, and feel comfortable that the device you got is good.
Did I read that you were going to try to port paranoidandroid to the TF700 last night or was that one of my weird obsessive Infinity dreams ?? I wish you luck if you are going to try - we need a few more devs around these parts.
Click to expand...
Click to collapse
When i can get jellybean then ill work on it. Im super busy with school and work, but i need to set some time aside to port it for tf700. i just cant spare the time to completely port JB too right now.
Jotokun said:
The problem is, the methods used on those Motorola phones are very hackish, and not recommended if alternatives are present. And since the TF700 is unlockable, its extremely unlikely those methods will ever be duplicated since those who want to mod can do so without restrictions.
Just look at the OG Atrix community... the instant an unlockable bootloader was leaked, development for those hackish methods immediately halted. Someone ported 2nd init days or weeks before that happened, and nothing was ever written to use it because it simply wasnt needed anymore.
Click to expand...
Click to collapse
Makes a lot of sense, thanks!
Personally, I'm still interested in a way to flash custom ROM's without unlocking the bootloader, even if it is "hack'ish".
As a good example, I unlocked the bootloader on my original TF700 after I had it for about 3 weeks. I figured that I was good to go - no major flaws... And then about 2 weeks later, the damn thing died on me, so I was stuck with a less-than-45-day-old device that had no warranty!!
I'm just saying - if there is a way to flash ROM's without voiding my warranty, I'd be *very* interested in doing that, even if it was a little hack'ish!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
its rather hard to install custom roms without an unlocked bootloader.
Consider this: You have a computer that boots directly into windows. Now you have administrator access to the computer however you can't change the boot priority, what disks it boots from, or anything having to do with how the thing starts up. Usually when you want to install an operating system, say windows xp, you would put the disk in, boot from the CD, and install it. Well we have no "boot from CD" option, everything pertaining to that is locked down by Asus.
I know other phones have found ways to sidetrack around that but honestly, with how unreliable they are its often not worth it. Asus has this thing locked down pretty well that its damn near impossible to get enough access to load anything custom at startup (even the unlock they gave us is garbage, if that fails your screwed).
If you want to load something custom you are best to get a third party warrenty and use the unlock.
pileot said:
its rather hard to install custom roms without an unlocked bootloader.
Consider this: You have a computer that boots directly into windows. Now you have administrator access to the computer however you can't change the boot priority, what disks it boots from, or anything having to do with how the thing starts up. Usually when you want to install an operating system, say windows xp, you would put the disk in, boot from the CD, and install it. Well we have no "boot from CD" option, everything pertaining to that is locked down by Asus.
I know other phones have found ways to sidetrack around that but honestly, with how unreliable they are its often not worth it. Asus has this thing locked down pretty well that its damn near impossible to get enough access to load anything custom at startup (even the unlock they gave us is garbage, if that fails your screwed).
If you want to load something custom you are best to get a third party warrenty and use the unlock.
Click to expand...
Click to collapse
Even with those methods, you're still restricted. For example, the Motorola phone hacks can run custom roms, but are still stuck with the stock motorola kernels. That means a (somewhat dirty) AOSP rom can be made around the kernel, but a true clean Cyanogenmod or anything requiring kernel level hacks are not possible.
Related
Apologies if this is already common knowledge?
It looks as though the B70 Transformers are coming with locked boot loaders, is that the case?
The never-ending battle.
Tuesday, August 2nd, 2011 - 10:21 am - Android, General, Transformer
Been a while since last post, but it appears ASUS’s counter move have finally come.
All signs point to that with the B70 revision of the Transformer, they have changed the Secure Boot Key.
At the same time they appear to have disabled downgrades in the more recent revisions of the firmware (the one B70 comes with!)
This means: At this point it’s not possible to root B70 revision ASUS Transformers. We will of course see what we can do to find a way around it, but keep in mind neither of us have access to a B70 revision model nor do we intend to spend the money needed to get one.
It was a good run, and congrats to all those with pre-B70 revision devices and bummer for everyone who bought newer revision devices hoping to root
Thanks,
RaYmAn & Bumble-Bee
Click to expand...
Click to collapse
http://androidroot.mobi/2011/08/02/the-never-ending-battle/
I'm not remarkably familiar with the different segments, but I'm rooted now (on a device from last month, so B6), but I still have my standard bootloader and recovery. Does this make a difference to rooting, or just to custom ROM's?
This means: At this point it’s not possible to root B70 revision ASUS Transformers.
Click to expand...
Click to collapse
I think it applies to both? (But I'm no expert on these things).
I wonder if any new Asus software updates will also change the secure boot key and prevent other B revisions from being rooted once updated?
Makes me glad mine's B3. Just hope I dont have to return it at any point. Thanks for posting this info though. Interesting stuff.
I'm guessing suddenly lightbleed that nobody notices and creaking that you have to listen out for will all of a sudden be unimportant...
I'm not remarkably familiar with the different segments, but I'm rooted now (on a device from last month, so B6), but I still have my standard bootloader and recovery. Does this make a difference to rooting, or just to custom ROM's?
Click to expand...
Click to collapse
The secure boot key controls access to the tablet in NVFlash mode.
Without it basicallly you can't use NVFlash to update the Firmware on the tablet but it's possible that there might be other rooting methods that don't rely on NVFlash.
Instead these rely on exploiting bugs in the Android OS which can then be used to write data to areas of the tablet that shouldn't and so do things like install custom recovery modes that can then be used to load custom/insecure ROMs etc
(it's how the tablet was rooted before we gained access to the SBK)
I'm sure some bright spark will get it sorted anyways. These things don't remain unchallenged for long.
Now did we get the SBK last time? Someone had to have leaked it; I find it hard to believe it was brute-forced.
Ugh.... Why oh why are they doing this?? Don't they realize that one of their "pros" over Apple devices is becuase they lock them down so much - Why would they go and do that to their products now??? I thought I was finally moving towards freedom by getting away from Apple!!! <sigh>
Sent from my Transformer TF101 using Tapatalk
jtrosky said:
Ugh.... Why oh why are they doing this?? Don't they realize that one of their "pros" over Apple devices is becuase they lock them down so much - Why would they go and do that to their products now??? I thought I was finally moving towards freedom by getting away from Apple!!! <sigh>
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
the thing is wheather we like it or not ..they are their units and they will do what they want. Doesn't mean someone won't crack it like they always do. Just finding some that have been exchanged that have been rooted is enough to tick them off. Just reading here and finding out what s done with them is enough to tick them off. Look at what Motorola is doing. They made a statement that if you want to run a custom rom go somewhere else.
No they are OUR units and WE will do what WE want with them and if they do not like it then they can stick it where the sun does not shine.
There is no need for Asus to do this to the newcomers. It is just plain wrong.
Asus seems to go in the wrong way.
CrazyPeter said:
I'm guessing suddenly lightbleed that nobody notices and creaking that you have to listen out for will all of a sudden be unimportant...
Click to expand...
Click to collapse
ROTFLMAO! Thanks Crazy......very astute!
Do they really think that locking the bootloader will ATTRACT more customers?? If anything, it can only hurt sales...
I can't imagine that a whole lot of transformers get returned rooted - most people who are willing to root them know better than that (I would think)... I just don't get the reasoning behind it. How does it benefit them?
Sent from my Transformer TF101 using Tapatalk
I wonder what Asus will do with the Transformer 2.
Less of an upgrade itch at the moment.
I was thinking of buying Transformer near future (1-2 weeks), but now Im starting to wonder, is there anyway to see which revision tablet is before purchasing? Maybe serial number will tell it somehow?
I dont wanna buy locked tablet...
I'm guessing its just to hinder people from returning or RMA'ing units for light bleeds or creeking
Sent from Hogwarts
bytetemplar said:
I was thinking of buying Transformer near future (1-2 weeks), but now Im starting to wonder, is there anyway to see which revision tablet is before purchasing? Maybe serial number will tell it somehow?
I dont wanna buy locked tablet...
Click to expand...
Click to collapse
The serial number is located on the back of the pkg. You will be able to see it before you purchase it.
Is there anyway to safely tell if this is the case? I recently got a B70 and was able to root mine. I just wnat to make sure that I am not affected by this, and if I am want does that mean?
bytetemplar said:
I was thinking of buying Transformer near future (1-2 weeks), but now Im starting to wonder, is there anyway to see which revision tablet is before purchasing? Maybe serial number will tell it somehow?
I dont wanna buy locked tablet...
Click to expand...
Click to collapse
The serial will start with B70, so you will be able to tell. It's not like the B70 won't be cracked, anyways. There may be benefits to the later revision, as well.
As for Asus' thoughts on locking it down, they have a responsibility to shareholders to protect the IP(intellectual property) on the device. Buying a Transformer does not give you license to their IP. If shareholders feel they are not acting in accordance, they can basically sue Asus for shares/profit.
Personally, I wish the entire bootchain was open-source, but we knew it wasn't right from the beginning, so Asus is within it's rights.
Now, the good news. If we can buy enough stock in Asus, we can vote to open the IP base. If we reallllly buy alot, we might even win.
Once again, let me state, their decision sucks, but it's probably more for the shareholders than the company itself.
Hi all,
after having read a lot on different accessible Android tablets, I have decided to purchase a T700. Seeing the speed on YouTube and reading about this device have convinced me to make that step.
Now, the order is placed, but receipt is still a few days away, I am reading this site and have the feeling that actually the device is not so smooth when kept original. I do wish to have a smooth working device but keep away from as much flashing as possible.
As my signature might indicate, I have some flashing experience, but I still feel myself noob for each and every new device I get.
My Desire HD has always been stock, not even rooted.
My OneX+ is rooted and unlocked after a short while, I use TitaniumBackup and deleted some Bloatware, but have no wish to flash any custom roms.
I just feel that flashing a device new and new to get it perfect is aking too much time. My rooted and unlocked OneX+ is fast enough, no tweaking needed.
This is the state I would like my T700 to be in. Fast and smooth with allowance to have the device do what I want.
Means I do want root, but if not necessary would not like to unlock / flash or anything else.
Can You advice me on the steps I should or should not do to get such state.
-should I make sure not to use any OTA after receipt
-should I root after receipt and upgrade to JB after that (and eventually root once more)
I will be reading around more before I will get my hands on the device, but I would really like to make the correct steps.
I'd be grateful for your opinions.
Thanks in advance,
Ruud
To be honest, the TF700 does have some performance issues with the stock firmware. I would *highly* recommend that you install a custom ROM - more specifically, I'd recommend the "CleanROM Inheritance" custom ROM specifically for your TF700, which will make it *very* fast and smooth.
Of course, in order to install a custom ROM, such as CleanROM Inheritance, you will need to unlock the bootloader on your device, which *will* void your warranty! If that is a concern (it was for me), I would recommend a third-party warranty service such as SquareTrade. With a coupon, you can get 2 years of coverage (including "accidental coverage") for about $80. This way, if you do brick your device while trying to flash a custom ROM, you will be covered.
Trust me, $80 is a small price to pay for complete peace-of-mind for 2 years, especially considering the performance gain with CleanROM. Hell, even if I run the TF700 over with my car, it will still be covered under warranty...
Just my opinion, of course!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hi,
Thanks, although this was not exactly what I wanted to hear.
So even if I would unpack and let all OTA updates run up to JB, give it a complete refresh, I would still be unhappy with the performance, right ?
The insurance is nice, but as I am to use it in Russia, I would not know if I am covered for these things.
It is actually not the fact that I am afraid to loose warranty. All devices I did unlock were done after reading the different threads here and I was always lucky to get the job done without serious issues. My OneX+ is still brandnew and I presume I do not have warranty anymore anyway as I rooted and unlocked it already.
What I was hoping for is to get a smooth device without the need to go through this process, I guess your answer says I am not .
regards,
Ruud
Before doping the OTA updates use NVflash. Eventos though you are no considering flashing ROMs now it will be a good insurance in the case you change tour mind in the future.
Enviado de meu Galaxy Nexus usando o Tapatalk 2
raladoshow said:
Before doping the OTA updates use NVflash.
Click to expand...
Click to collapse
To be more exact: version 9.4.5.26 is the last version that can be used to *prepare* NVFlash access. To use NVFlash on the TF700, you need a tool called "wheelie" and a blob file with data extracted from your device (it's encrypted with a device-specific key). Later bootloaders are locked down, even after unlocking the device, so it is no longer possible to obtain this file. So before upgrading anything, be sure to read about the procedure on http://androidroot.mobi/t3_nvflash/ .
There is also a thread in the development section that explains the details.
Hi guys,
these looks like very good advises. Before reading in to them, let me say ; "Thanks" !
regards,
Ruud
Hey guys,
I'm just about to receive my Infinity and have been reading through the posts here. I've read quite a few horror stories about people bricking their tablets, not being able to power it up, etc etc.
I'm not sure what version of Android it'll be running when I get it so I'd like to know what are the things I should really be avoiding when using the lock tool, flashing the boot loader and the rom (cromix :good: )?
From the impression I've got, the device seems very fickle/easy to brick/break. Am I wrong in thinking that?
The TF700 users here seem like a helpful bunch so hopefully I could get a few pointers on things NOT to do....
Cheers!
jonlad1 said:
Hey guys,
I'm just about to receive my Infinity and have been reading through the posts here. I've read quite a few horror stories about people bricking their tablets, not being able to power it up, etc etc.
I'm not sure what version of Android it'll be running when I get it so I'd like to know what are the things I should really be avoiding when using the lock tool, flashing the boot loader and the rom (cromix :good: )?
From the impression I've got, the device seems very fickle/easy to brick/break. Am I wrong in thinking that?
The TF700 users here seem like a helpful bunch so hopefully I could get a few pointers on things NOT to do....
Cheers!
Click to expand...
Click to collapse
Hi, and welcome to the community!
First things first: check the unit thoroughly for the known issues (screen bleed, loose screen bonding, etc. Several threads in here concerning the most frequent issues.
1) If you happen to get a pre-.30 firmware (which is unlikely at this point in time), install Nvflash first and pull the backups. That might save you form not only severe headaches but a pretty stack of dollars too, if the excrement hits the ventilator.
2) Try and see if the unlock tool works. In a relatively large percentage of 700s, it doesn't. That would solve your problem instantly. (You can then proceed to update to the latest stock ROM, but no custom ROM'in' for you then. That << smiley is actually very mean, because that would be some major suck.)
3) Whatever you do, ONLY use the most recent versions of whatever recovery has your preference. Also update the bootloader to the version your ROM of choice requires!
4) Unless you have extensive experience with flashing and ROMs in general, it might be prudent to pick a stock-based ROM (i.e. CROMI-X). If you comfortable with the odd bug here and there, you might try an AOSP/AOKP/CM-based ROM and see if they fit your bill.
CROMI-X has a great OP with all the updates to bootloader and such you'll need.
5) Don't do anything if you're not sure when starting out. The 700 is not particularly easy to brick, but it is relatively hard to fix in some cases that on other devices (Samsung's comes to mind) would just mean reflashing some stuff (in Odin/Heimdall).
Have fun!
Marty
MartyHulskemper said:
Hi, and welcome to the community!
2) Try and see if the unlock tool works. In a relatively large percentage of 700s, it doesn't. That would solve your problem instantly. (You can then proceed to update to the latest stock ROM, but no custom ROM'in' for you then. That << smiley is actually very mean, because that would be some major suck.)
Marty
Click to expand...
Click to collapse
Hey mate,
Thanks for the info
With the unlock tool, has anyone reported any issues from trying to use it? If it doesnt work, will it just say it didnt work? I cant brick from just using the tool can I?
Cheers!
jonlad1 said:
Hey mate,
Thanks for the info
With the unlock tool, has anyone reported any issues from trying to use it? If it doesnt work, will it just say it didnt work? I cant brick from just using the tool can I?
Cheers!
Click to expand...
Click to collapse
If it doesn't work it just gives some error message. I haven't heard of anyone bricking because the unlock tool failed, so you should be safe there. As far as I'm aware the only issue you'll have from the unlock tool not working is just the fact that you're not going to be unlocked lol.
Sent from my ADR6425LVW using XDA Premium.
jonlad1 said:
Hey guys,
I'm just about to receive my Infinity and have been reading through the posts here. I've read quite a few horror stories about people bricking their tablets, not being able to power it up, etc etc.
I'm not sure what version of Android it'll be running when I get it so I'd like to know what are the things I should really be avoiding when using the lock tool, flashing the boot loader and the rom (cromix :good: )?
From the impression I've got, the device seems very fickle/easy to brick/break. Am I wrong in thinking that?
The TF700 users here seem like a helpful bunch so hopefully I could get a few pointers on things NOT to do....
Cheers!
Click to expand...
Click to collapse
I'm with Martin on this:
Until you are sure that your tab is not a lemon with major hardware issues I would not unlock it.
You can root it and start playing around with some more advanced settings in the meantime. Wouldn't it really suck if you unlocked and a day or week later the digitizer would go bad? Asus could say: Sorry, pal - you're unlocked, you're out of warranty.
They have repaired even unlocked devices under warranty, but you can't count on it. And in some cases the repaired tablet came back with a permanently locked bootloader....
So give it a few weeks, in the meantime start reading the relevant thread of your favorite custom ROM(s) to get a feel for them, and familiarize yourself with the process and lingo of flashing.
You could start here:
http://forum.xda-developers.com/showthread.php?t=2204100
I feel a little sheepish since we basically hijacked the original thread, but since the original topic is pretty much outdated and not active anymore, I guess it is ok. I kinda walked a user through the whole process of rooting/flashing a custom rom etc.
Start with post #191. In #193 I wrote a step-by-step guide which HeartWare42 fleshed out even more in post #220.
Note anything you don't understand and Google it.
Read 3 times, ask twice, flash once )
berndblb said:
I'm with Martin on this:
Until you are sure that your tab is not a lemon with major hardware issues I would not unlock it.
You can root it and start playing around with some more advanced settings in the meantime. Wouldn't it really suck if you unlocked and a day or week later the digitizer would go bad? Asus could say: Sorry, pal - you're unlocked, you're out of warranty.
They have repaired even unlocked devices under warranty, but you can't count on it. And in some cases the repaired tablet came back with a permanently locked bootloader....
So give it a few weeks, in the meantime start reading the relevant thread of your favorite custom ROM(s) to get a feel for them, and familiarize yourself with the process and lingo of flashing.
You could start here:
http://forum.xda-developers.com/showthread.php?t=2204100
I feel a little sheepish since we basically hijacked the original thread, but since the original topic is pretty much outdated and not active anymore, I guess it is ok. I kinda walked a user through the whole process of rooting/flashing a custom rom etc.
Start with post #191. In #193 I wrote a step-by-step guide which HeartWare42 fleshed out even more in post #220.
Note anything you don't understand and Google it.
Read 3 times, ask twice, flash once )
Click to expand...
Click to collapse
Thanks for the info guys, I'll check the hardware first!
jonlad1 said:
Hey guys,
I'm just about to receive my Infinity and have been reading through the posts here. I've read quite a few horror stories about people bricking their tablets, not being able to power it up, etc etc.
I'm not sure what version of Android it'll be running when I get it so I'd like to know what are the things I should really be avoiding when using the lock tool, flashing the boot loader and the rom (cromix :good: )?
From the impression I've got, the device seems very fickle/easy to brick/break. Am I wrong in thinking that?
The TF700 users here seem like a helpful bunch so hopefully I could get a few pointers on things NOT to do....
Cheers!
Click to expand...
Click to collapse
Hi there,
When I had bought my tf700 I did'nt have a clue what custom rom is.
I was totally naive and ignorant as to Android technology.
I was disappointed with my TF700 performance and lived with it for a couple of months.
Afterwards, I searched the internet until I have found this marvellous forum (which attracts OCDs like the fire attracts moth).
I read and read and read and read, and read more and asked the fine users of this fine forum if I got it all right,
and then one springy night on the end of March 2013, something happened.
A magic...
"I took the red pill" , unlocked my TF700, pushed TWRP and flashed CROMI.
Everything went super.
Ever since then I follow Sbdags CROMI-X thread and keep update my firmware.
Just to remind you - I am not a Computer wizard, my occupation has got almost nothing to do with electronics and I am not a kid (actually I am 37 with many obligations like family and work - so my spare time is scarce).
And here I am - master of my TF700!
So - everything is possible!
And if you follow instructions and restrict yourself to the right method - you can be rest assured you won't brick your device.
Actually It's like cooking: you should find a good recipe and act accordingly.
Cheers
So I finally got it delivered today
It looks good, no damage, screen bleed that i can see. Screen seems fine.
Its running JRO3C.US_epad-10.4.4.25-20121228
JB 4.1.1
I'm not really sure where to go from here - should I wait a few days or just unlock and put CROMI-X on now?
Speed of the system isnt bad, transitions seem a bit slow, havent really installed a bunch of apps yet...
jonlad1 said:
So I finally got it delivered today
It looks good, no damage, screen bleed that i can see. Screen seems fine.
Its running JRO3C.US_epad-10.4.4.25-20121228
JB 4.1.1
I'm not really sure where to go from here - should I wait a few days or just unlock and put CROMI-X on now?
Speed of the system isnt bad, transitions seem a bit slow, havent really installed a bunch of apps yet...
Click to expand...
Click to collapse
You are itching to do it, right?
I can tell, you can hardly wait....
Well, the rational next step would be to wait a week, or two, or however long you can stand it, and then unlock etc.
But where's the fun in rational, right?
Well, while you decide - why not upgrade it to JB 4.2.1? Saves you a bootloader flash and clean install later....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
You are itching to do it, right?
I can tell, you can hardly wait....
Well, the rational next step would be to wait a week, or two, or however long you can stand it, and then unlock etc.
But where's the fun in rational, right?
Well, while you decide - why not upgrade it to JB 4.2.1? Saves you a bootloader flash and clean install later....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Is 4.2.1 worth the update? I read that 4.2.1 caused a few issues for some people....
I probably will just flash it It feels like it should run quicker, take Maps for example. seems REALLY laggy but on my N7 it was fine?
jonlad1 said:
Is 4.2.1 worth the update? I read that 4.2.1 caused a few issues for some people....
I probably will just flash it It feels like it should run quicker, take Maps for example. seems REALLY laggy but on my N7 it was fine?
Click to expand...
Click to collapse
JB 4.2 was better for most people, others had issues with Bluetooth tethering and some other stuff...
The reason I recommend you upgrade to stock 4.2 is mainly that then you automatically would have the correct bootloader on our tablet.
For Cromi-X you need the 4.2 bootloader. If you are on 4.1 you have to flash it before you flash Cromi-X, if you are already on 4.2 you're good to go. One less thing that could go wrong....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
JB 4.2 was better for most people, others had issues with Bluetooth tethering and some other stuff...
The reason I recommend you upgrade to stock 4.2 is mainly that then you automatically would have the correct bootloader on our tablet.
For Cromi-X you need the 4.2 bootloader. If you are on 4.1 you have to flash it before you flash Cromi-X, if you are already on 4.2 you're good to go. One less thing that could go wrong....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
That makes sense, I'll get that updated tonight, cheers
Does CROMIx improve the laggy transitions/Maps/Browser?
jonlad1 said:
That makes sense, I'll get that updated tonight, cheers
Does CROMIx improve the laggy transitions/Maps/Browser?
Click to expand...
Click to collapse
It improves e-v-e-r-y-t-h-i-n-g
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
It improves e-v-e-r-y-t-h-i-n-g
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
SOLD!
jonlad1 said:
SOLD!
Click to expand...
Click to collapse
You will not be disappointed. Welcome to the OCFD corner.
Now that I think of it: http://hope4ocd.com/checklist.php is missing the "Needing the have the latest and greatest x.x.xxxxx version of your ROM", or "Needing to flash at least 5 ROMs a week". Can we petition that?
Hmm, I just tried to update via OTA and it said my system is up to date? I'm on 4.1.1?
EDIT - ok, updated manually. Trying to use the unlock tool but getting "Unkown Error. This may be a connection issue" - is that what'll happen if it's not gonna work for me?
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
You could have got the Nook HD+ 32GB for $180 and dead easy to root and put CM 10.1 or Carbon on it and no concern of bricking it. Stock 2.1 on the HD+ is barely ok (very barely), but CM 10.1 rocks.
A little smaller tablet, but same great display resolution. I use this more than my iPad 4 now, which is both a compliment to the HD+ and an insult to how much I paid for the iPad 4.
jonlad1 said:
Hmm, I just tried to update via OTA and it said my system is up to date? I'm on 4.1.1?
EDIT - ok, updated manually. Trying to use the unlock tool but getting "Unkown Error. This may be a connection issue" - is that what'll happen if it's not gonna work for me?
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Click to expand...
Click to collapse
Personally, when I had this problem, I just tried to run the app every day for a week oe so and it eventually works, but others have had to use tricks. Use the search for unlock, you will find several ideas about fixing it.
Okay, so I know this phone doesn't exactly win the spec war, but it's awesome and would make a fantastic rooted phone. Unfortunately there isn't a forum here on XDA for the device (either because it's too new or there isn't a demand for it)
Do you guys think a forum will be made for this device? It'd be nice to at least have a place to say what root methods DON'T work (I've tried a few)
Thanks for the help, XDA rules!
I second this. I am planning on buying a new phone and after researching numerous phones out there based on my tastes and constraints, I think this phone works very well (another is Samsung Galaxy Exhibit 2). One flaw that I heard is the amount of storage in this phone is around 4gb. Without a way to put apps on an external SD card (which I believe would require a custom ROM), the storage would probably fill up pretty quickly. So it'll be great if XDA opened a forum for this phone.
As a side note if anyone can point to other devices that fit my needs I would be grateful:
- Less than 4.2" screen (preferably 4").
- Android only
I don't have any financial constraints or any favorite companies.
Thanks!
What root method did you find worked? Did you try framaroot? Also have you found any Roms?
Sent from my SPH-D710VMUB using Tapatalk 2
bbradf44 said:
What root method did you find worked? Did you try framaroot? Also have you found any Roms?
Sent from my SPH-D710VMUB using Tapatalk 2
Click to expand...
Click to collapse
I used Motochopper, worked like a charm. make sure you have the LG Optimus f3 drivers on your computer.(found on LG website)
habitforming said:
I used Motochopper, worked like a charm. make sure you have the LG Optimus f3 drivers on your computer.(found on LG website)
Click to expand...
Click to collapse
Ratified. Motochopper worked flawlessly for me as well.
richardpwnsner said:
Ratified. Motochopper worked flawlessly for me as well.[/QUOT
Anyone find a tethering ap that works?
Click to expand...
Click to collapse
wolfu11 said:
richardpwnsner said:
Ratified. Motochopper worked flawlessly for me as well.[/QUOT
Anyone find a tethering ap that works?
Click to expand...
Click to collapse
Do tethering apps need to be phone specific? I don't have data, but I'll let you know if I come across one.
Click to expand...
Click to collapse
Bad news
I have created the recovery tree, and have created a recovery.img for this phone. ok now heres the bad news OUR lg optimus f3 has a stock 3.4 kernel with a locked bootloader. Even worse news is that 3.4 "locking" features a sha5 hash system for its image/partitions (recovery, boot, and bootloader). Even worse news there is no known (or atleast what i know or have heard) way to get around this. The phone will be forever locked until lg updates or allows said lock to be removed. I have flashed the recovery and have had no damage to my device but it just sticks at "unsecure recovery" and does a hard reset (factory restore) every time i try to play with it which is a huge flaw if you ask me.
I have hexedited the bootloader and found that there is indeed "juicy" strings within that may tell to a future unlock these strings being
-Device UnLock!, so Boot Success!!
-oem unlock
-ERROR: Could not do normal boot. Reverting to fastboot mode
Also these strings could just be defualt with all lg bootloaders meaning....there is no hope.
My phone is without a soul and I will never be buy lg again.
If anyone is able to get into fastboot
1. PM ME
2. run : fastboot oem unlock
Again root for this phone works great as long as you dont touch recovery, bootloader, or boot partitions
inyourface09 said:
I have created the recovery tree, and have created a recovery.img for this phone. ok now heres the bad news OUR lg optimus f3 has a stock 3.4 kernel with a locked bootloader. Even worse news is that 3.4 "locking" features a sha5 hash system for its image/partitions (recovery, boot, and bootloader). Even worse news there is no known (or atleast what i know or have heard) way to get around this. The phone will be forever locked until lg updates or allows said lock to be removed. I have flashed the recovery and have had no damage to my device but it just sticks at "unsecure recovery" and does a hard reset (factory restore) every time i try to play with it which is a huge flaw if you ask me.
I have hexedited the bootloader and found that there is indeed "juicy" strings within that may tell to a future unlock these strings being
-Device UnLock!, so Boot Success!!
-oem unlock
-ERROR: Could not do normal boot. Reverting to fastboot mode
Also these strings could just be defualt with all lg bootloaders meaning....there is no hope.
My phone is without a soul and I will never be buy lg again.
If anyone is able to get into fastboot
1. PM ME
2. run : fastboot oem unlock
Again root for this phone works great as long as you dont touch recovery, bootloader, or boot partitions
Click to expand...
Click to collapse
Ugh. Thanks for the work. This is bad news indeed. I'll keep poking around and let you know if I find anything.
richardpwnsner said:
Ugh. Thanks for the work. This is bad news indeed. I'll keep poking around and let you know if I find anything.
Click to expand...
Click to collapse
Out of curiosity, any chance Loki would work? I'd be willing to give it a go if there's a decent chance—still within the 14 day exchange window .
Will motochopper work on any carrier version of this phone? Thanks!
jjfad said:
Will motochopper work on any carrier version of this phone? Thanks!
Click to expand...
Click to collapse
I've seen confirmations on three carriers (can't remember which ones off the top of my head, sorry [edit-well, T-Mobile and Virgin Mobile come to mind now]), so I'd assume the answer is yes. Regardless, I have yet to see anyone complain about adverse affects, so no reason not to try (though, grain of salt—I'm brand new to android).
For anyone that has this, how are the antennas on this phone?
I just ordered one from tmo and am hoping to get better reception at my house than from my Samsung or HTC.
Sent from my SGH-T999 using xda app-developers app
Steve5400 said:
For anyone that has this, how are the antennas on this phone?
I just ordered one from tmo and am hoping to get better reception at my house than from my Samsung or HTC.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
They seem better and with WIFI calling built in the phone hasn't skipped a beat.
Check my way!
http://forum.xda-developers.com/showthread.php?t=2420178&highlight=rooting+lg+optimus+f3
I failed rooting my phone with Windows system, maybe cause I'm not familiar with the process or I was just to lazy, but it does work if you use motochopper. Try looking it up youtube. You could try my method, it should work on Jellybean 4.1.2!
richardpwnsner said:
Out of curiosity, any chance Loki would work? I'd be willing to give it a go if there's a decent chance—still within the 14 day exchange window .
Click to expand...
Click to collapse
BAHAHA me to man i think im down to 10 days. Im trying to get some attention but i need someone who knows little endian, and their way around bootloaders. Id be willing to donate to someone who can help me out, also to support the other 3 variants (if the aboot differs).
I have a recovery created also and a device tree (needs gpio support for kernel).
And to awnser your question, yes loki will work IF i can get the needed values so that when recovery/boot is read into memory that it overwrites the security check feature in aboot. If the wrong values are give you may end up with a brick (very slim chance)
My return window just closed . If it helps, you can pull the open source from LG's website and merge it with the android source. I also discovered an even easier solution: set up the LG Sync application, and select the "upgrade recovery option". Then, when it begins downloading, remove your phone, set Windows (or your relevant OS) to show hidden files and folders, and go the the Program Data folder. There should be something like "PHONEAX" under the LG Electronics folder that will contain the full stock kdz file when the download is complete.
It's really kind of surprising that there's absolutely no dev love out there for the F3. I suppose it's because the phone is entry level, but it's really not that bad but for the storage. I got it as a gift, so no complaints here—of course, if anyone wants to donate a Note or Galaxy gratis, I suppose I'd be willing to switch .
I had a Galaxy S4 from Verizon. I switched to T-Mobile Because believe it or not the network is stronger where I work. Also, there pricing on plans cannot be beat. But, I digress. The Galaxy S4 being a Verizon device never really functioned the way it was supposed to on T-Mobiles network. It was unlocked however was still useless for 4G LTE and while I could do better than edge in some places, those places were few and far between. I started to assess what it is I actually used my phone for these days. I'm not into modding with custom ROMS and kernels anymore and I'm not much of a multi-tasker either so I decided that I did not need the super power device anymore. The specs on this phone are perfect for what I need my phone to do. Its been a long time since I have gone beyond rooting to remove bloat and tether. I agree that the storage on this sucks. I don't understand why there are any devices anymore that come with less than 32gb internal. storage is the cheapest thing that can be added to a device and its not as though it uses much physical space. other than the storage I will say that I am impressed with the quality of this device and I don't know that I would even put this as low as "entry level device." I would say its more of a mid-grade device. I am also happy with the reception on this device and its nice to have a compact phone again that actually fits comfortably in my hand and on my belt.
yutzyscott said:
I had a Galaxy S4 from Verizon. I switched to T-Mobile Because believe it or not the network is stronger where I work. Also, there pricing on plans cannot be beat. But, I digress. The Galaxy S4 being a Verizon device never really functioned the way it was supposed to on T-Mobiles network. It was unlocked however was still useless for 4G LTE and while I could do better than edge in some places, those places were few and far between. I started to assess what it is I actually used my phone for these days. I'm not into modding with custom ROMS and kernels anymore and I'm not much of a multi-tasker either so I decided that I did not need the super power device anymore. The specs on this phone are perfect for what I need my phone to do. Its been a long time since I have gone beyond rooting to remove bloat and tether. I agree that the storage on this sucks. I don't understand why there are any devices anymore that come with less than 32gb internal. storage is the cheapest thing that can be added to a device and its not as though it uses much physical space. other than the storage I will say that I am impressed with the quality of this device and I don't know that I would even put this as low as "entry level device." I would say its more of a mid-grade device. I am also happy with the reception on this device and its nice to have a compact phone again that actually fits comfortably in my hand and on my belt.
Click to expand...
Click to collapse
No argument here. I like it well enough, but I'm (1) a closet geek; and (2) a heavy multitasker, so given the option I'd prefer something with more screen space (I just graduated from law school, so I do a lot of reading on the go). As a phone, however, you really couldn't ask for more—the size otherwise pretty much perfect, it's relatively snappy with most applications, and once debloated the stock launcher is pretty good.
That being said, the second I see a safe way to deal with the bootloader pop up, I'm diving in, no question .
Decided to share my home screens.
Sent from my LG-P659 using XDA Premium 4 mobile app
Morning all,
I have recently received my CAT S60 and I have to say, I am extremely pleased with the device out of the box. It is solid, extremely well built, battery life is amazing and camera quality is far better than the reviews led me to believe. Call quality is also the best I have ever had on any handset.
Unfortunately, I have never before owned a device without root. I have rooted most of my phones + installed a custom rom within a couple of days of opening the box. Sadly, this time round I've bought a less-popular device which is quite new and there is no existing support.
I am able to do most of the root-requiring functions with this phone (flashlight via button from locked, skip tracks with volume etc) using software workarounds, but I am already butting up against things that are pissing me off because I don't have system access, and I am so used to having it.
I've read horror stories about the lockdown function Qualcomm have applied to the 617 chips, but I now see that some phones with this chip have already been rooted (Motorola) so I am wondering, what are the chances that I will see root or a root exploit for this phone in the near future?
I'm not sure that I would sell the device over not being able to gain root, but it is really really annoying me.
I would be interested too. I couldnt even figure out how to set the s60 to downloadmode (If there is such a mode at all) to flash a custom recovery like twrp. Recoverymode is the usual volume up before poweron.
heinzherbert said:
I would be interested too. I couldnt even figure out how to set the s60 to downloadmode (If there is such a mode at all) to flash a custom recovery like twrp. Recoverymode is the usual volume up before poweron.
Click to expand...
Click to collapse
Recovery mode is volume up and power button together for 3 to 4 seconds
There is a switch in developer options to allow bootloader to be unlocked. Maybe this, combined with factory recovery menu will set us free? Flash a modified factory rom with root enabled? The stock ROM is very clean.
bandario said:
There is a switch in developer options to allow bootloader to be unlocked. Maybe this, combined with factory recovery menu will set us free? Flash a modified factory rom with root enabled? The stock ROM is very clean.
Click to expand...
Click to collapse
There is an option to unlock bootloader. It's called OEM unlocking
So, flicking this switch should unlock the bootloader???
That gives me a bit of hope for some development on this handset. None of the previous cat phones have seen any real development.
bandario said:
So, flicking this switch should unlock the bootloader???
That gives me a bit of hope for some development on this handset. None of the previous cat phones have seen any real development.
Click to expand...
Click to collapse
To be honest flicking that switch does nothing for me. I am unsure how to unlock the bootloader
On S60 bootloader is locked.
No fastboot, but you will be able to select recovery mode.
bump. I'd like to see this phone rooted.
Any progress on this or has anyone tried yet?
My SONY Z1C died on me the other day and I'd need to know if there's at least a chance to root this one.
I'm considering getting the S60 but only if I'm able to root it. An unrooted phone is barely usable to me...
Greetz and thanks in advance,
Unr3aL67
haven't tried rooting mine yet. Not felt the need to yet TBH
Mine is working pretty good without root. Only reason I'd want root honestly is to make backups, and perhaps uninstall a couple apps, but the bloatware is minimal.
Sent from my S60 using Tapatalk
Since the original question was "Is this rootable?" and lately answers have come in the form of "I haven't tried rooting mine" .... which doesn't seem much like an answer at all, to be honest .... I want to join the OP in asking this question. For those of us who have grown accustomed to the freedom and flexibility of having root access to our devices, it would be really nice to know (before making a decision to purchase) whether it is possible to obtain root on the CAT S60.
Does anyone know where to get a zip of the ROM?
After the Arstechnica review this may be my next phone. However, I really require a way to root it so that I can use iptables.
Anyone had any luck?
In response to your query we regret to inform you that we do not offer any assistance or tools to root our devices.
Click to expand...
Click to collapse
I tried contacting support about help to root, got the above back. It's a work phone so maybe it's better that I don't mess with it.
If anyone is going to root or make a custom recovery, it'll need to be without any support from the manufacturer. I mostly miss Xposed Framework for adblocking, less frequent notifications and the ability to longpress the back key to enable/disable screen rotation, the ROM itself is 99% "stock" otherwise and I have no complaints on that front.
In response to your query we regret to inform you that we do not offer any assistance or tools to root our devices.
Click to expand...
Click to collapse
This is, of course, their right, and buyer beware if you wanted a rootable phone. Still, I can't keep from being annoyed at this attitude; if I'm paying them good money for my devices, I want the freedom to do with it everything that I want, including modifying it and knowingly voiding my warranty, or even breaking it outright, if that's what makes me happy. Especially now that rooting/jailbreaking is a thing. Wanting to keep on controlling and limiting how people are able to use your product after you've sold it to them always sticks in my craw.
I guess I'll be passing on what otherwise looks like a perfect phone for me, unless some shining hero (or heroine) manages to figure out how to root a CAT S60 anyway, despite what the manufacturer might wish.
Tangib1e said:
This is, of course, their right, and buyer beware if you wanted a rootable phone. Still, I can't keep from being annoyed at this attitude; if I'm paying them good money for my devices, I want the freedom to do with it everything that I want, including modifying it and knowingly voiding my warranty, or even breaking it outright, if that's what makes me happy. Especially now that rooting/jailbreaking is a thing. Wanting to keep on controlling and limiting how people are able to use your product after you've sold it to them always sticks in my craw.
I guess I'll be passing on what otherwise looks like a perfect phone for me, unless some shining hero (or heroine) manages to figure out how to root a CAT S60 anyway, despite what the manufacturer might wish.
Click to expand...
Click to collapse
It is indeed a great phone, but the camera is sub-par. The focus takes an age compared to my Z5 Compact. I would wait for the second-generation version unless you critically need FLIR as a feature.
I've done a bit of poking around. I suspect that the bootloader could be unlocked with the commands "adb reboot bootloader" followed by "fastboot oem unlock-go".
I'm not going to do that at this point because without a custom ROM to flash there is no point in me voiding my warranty, but I believe it should be possible with USB debugging enabled, and the bootloader confirmed as unlockable.
I think this is how root will arrive on this device: by way of modifying a flashable ROM and flashing it to the device using QFIL as you would any other Qualcomm device.
The tools are all there in front of us, we just need someone with the knowledge to create that modified rom file....at this point I can't even find a factory rom to flash.
Given the recent speed and quality enhancements made available through the stock camera app, I also suspect that doing this will send us backwards to a much ****tier camera as has been the case with many sony handsets in the past.
bandario said:
There is a switch in developer options to allow bootloader to be unlocked. Maybe this, combined with factory recovery menu will set us free? Flash a modified factory rom with root enabled? The stock ROM is very clean.
Click to expand...
Click to collapse
Chuggers said:
There is an option to unlock bootloader. It's called OEM unlocking
Click to expand...
Click to collapse
bandario said:
So, flicking this switch should unlock the bootloader???
That gives me a bit of hope for some development on this handset. None of the previous cat phones have seen any real development.
Click to expand...
Click to collapse
That switch is available in a lot of devices and does nothing on a lot of them
Sent from my Lenovo A7010a48 using XDA Labs