Related
Hello,
After a failed upgrade I'm getting an error when booting the tablet. There is no actuall error just the EEE PAD startup screen, but it does not move from there.
Cold boot gave no results, wipe data gave no results, and the RCK give me a 'dead' android charater after 20 seconds.... Otherwise when trying to boot normally it is stuck on the EEE PAD screen.
Letting the battery drains was not much help either.
Thank you
Your device is bricked, and AFAIK you will only be able to unbrick it if we get an unlocked bootloader. That way you will be able to flash a new ROM through recovery with an SDcard
You've just put me off rooting my TF300.
Sorry to read about your trouble.
Why should this deter you from rooting? Just don't flash things from other devices, and you'll be fine.
Yeah just make sure to follow directions
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
You've already taken the most important step - reading, reading and reading before you do anything that you're not comfortable with.
Take your time and continue reading. Find out for yourself who knows their stuff and does a really good job explaining the steps. Learning and understanding are key to not bricking your device.
I waited a couple of months before I finally took the plunge with my Droid Charge. The difference in just rooting and debloating was like night and day. As delivered by Verizon, the phone sucked. Now I love it.
While waiting for the TF300, I immersed myself into the Prime forum just to see what's up. Hit the TF300 forum as soon as created. Knew exactly what to do and not do when I received it.
There's a ton of good info here on your device, how to use it, great apps and games, and support when you need it. There's no rush as there's nothing you have to do. It really is supposed to be fun!
Thank you for the comments...
Well,
Thank you for the comments. I am not exactely a newbie. I've roote my phones many times many way. And I did the same to my Zepad before it finally broke down.
I did read the instruction and follow them carefully. Having said that my mistake was to assume that the ZT201 rom would work since the one I downloaded did not!
Now that I am fairly sure there is nothing I can do about it (except use nvflash, but I would need to find some information such as the secure boot key, etc...) does anyone know if Asus can unbrick it? Maybe I should send them the device....
maugino said:
Well,
Thank you for the comments. I am not exactely a newbie. I've roote my phones many times many way. And I did the same to my Zepad before it finally broke down.
I did read the instruction and follow them carefully. Having said that my mistake was to assume that the ZT201 rom would work since the one I downloaded did not!
Now that I am fairly sure there is nothing I can do about it (except use nvflash, but I would need to find some information such as the secure boot key, etc...) does anyone know if Asus can unbrick it? Maybe I should send them the device....
Click to expand...
Click to collapse
Sorry for the misunderstanding - no slight intended. I believe we were actually responding to the post of not wanting to root.
I've been working with a tablet for 1 1/2 weeks. First ASUS device. Samsung phones are quite different (locked vs unlocked bootloaders). I'd love to help but I'm woefully unqualified. All I can suggest is looking in the TF101 and Prime forums since they're both from ASUS...
Seriously - best of luck with it.
just send it in for an RMA. that's your only hope.
demandarin said:
just send it in for an RMA. that's your only hope.
Click to expand...
Click to collapse
That's what I thought (or 'feared' to be more truthful). Thanks.
Warm Regards
Reilly1812 said:
Sorry for the misunderstanding - no slight intended. I believe we were actually responding to the post of not wanting to root.
I've been working with a tablet for 1 1/2 weeks. First ASUS device. Samsung phones are quite different (locked vs unlocked bootloaders). I'd love to help but I'm woefully unqualified. All I can suggest is looking in the TF101 and Prime forums since they're both from ASUS...
Seriously - best of luck with it.
Click to expand...
Click to collapse
No offense taken... You are quite right anyway, Samsung is different, the Zepad even more so. I was merely stating a fact: I may not be a pro (if I were I would not have done this stupid thing), but I do not consider myself to be a newby and I am open to suggestion to fix it, but it seems that my best shot is to return to vendor.
Thanks for the encouragement. Really appreciate (I'm having a dark moment!)
Warm Regards
Please let us know how this works out for you (hopefully for the best!)
Sent from my SCH-I510 using XDA
Will NVFlash work on this tablet??
jgaf said:
Your device is bricked, and AFAIK you will only be able to unbrick it if we get an unlocked bootloader. That way you will be able to flash a new ROM through recovery with an SDcard
Click to expand...
Click to collapse
Its not bricked
Brick means it wont switch on!!!!!!
Probably soft bricked at most!
Have you ever used ADB?
Is the device rooted? Probably not going by the date?
Dear community
Got my TF300TG a day yesterday and I'm hardcore trying to figure out, how Asus' android world works. I know old htc, new htc, motorola and samsung but Asus is new to me. I'm happy they didnt go overboard with their customisation if the OS, but I'm thoroughly angrx about the whole bootloader story. But who isnt, so...
From what I figured out till now is that the TG is obviously quite a different device than the T and not the same with simply a added gsm unit. Stuff is not simply interchangeable. I also learnt that the JB bootloader makes things a lot more difficult. Since my tablet came with some ICS (havent yet got asus' version naming scheme, but the build ends with .22 so I figure thats what younguys are referring to with .30, .40 etc) and I'd like to get the added niceness of JB but avoid the bootloader update, I wonder if that is possible. Maybe strip an update package from the updater component and flash it. Or so.
Oh, and I'm not yet unlocked, I'm a flashaholic on my smartphones and a CM addict, but because of asus tight assed warrqnty policy I didnt dare to unlock the tablet till now. I'll eventually get to it, probably.
Thanks in advance.
Sent from my ASUS Transformer Pad TF300TG using XDA Premium HD app
So I guess no one ever tried? Gnaa...
Well then, hypothetically, taking stuff out of the update.zip will break it's sign, so trying to do this very cheap by just removing stuff from the update package wont work, a little more sophistication is needed. Resigning the zip also wont work, we dont have asus keys. And maybe or possibly definitely, I havent searched, the ICS bootloader wont even load JB. The other way round I believe I can remember, the kernel throws a kernel panic but thats irrelevant, its the ICS bootloader and JB system I'm interested in...
So if anybody could shed some light on my issue, highly appreciated of course.
Sent from my ASUS Transformer Pad TF300TG using XDA Premium HD app
I've unlocked, rooted and ROM'ed probably 100 times on 25 different Android phones and tablets, this looks like my first official TF700 paperweight.
I saw another thread with a couple of people who did the same boneheaded thing I did: tried to install CWM the wrong way. Can't get into the ASUS recovery any more, either I hold volume down and get "Booting into recovery" (then hangs, no adb), or I hold volume up instead and I get a blank screen but it IS recognized as an APX device.
NVFLASH can't do anything at this point, the other thread had no good news either. Why ASUS can't have a "reset to factory recovery and bootloader" option is beyond me. Too late to return to NewEgg.
ASUS tech support would give me an RMA, BUT the big problem there is that since I put this awesome Skinomi cover on it, the sticker with the S/N had to go (hindsight is 20/20). I have a second TF700 that I unlocked, rooted, and installed CWM the right way. Is there any way using NVFLASH to get the blob from there and putting it on my bricked TF700 or is the blob encrypted to the device? I'm likely out of luck if I try to take the S/N sticker from my second TF700 and put it on the bricked one, ASUS will croak on that most likely.
Are there ANY other options? Short of just opening it up and looking at what's inside? That's a $600 visit I'd like to avoid.
Thanks.
ScaryBob said:
ASUS tech support would give me an RMA, BUT the big problem there is that since I put this awesome Skinomi cover on it, the sticker with the S/N had to go (hindsight is 20/20).
Click to expand...
Click to collapse
Are you saying that Asus won't even initiate the RMA process because you don't know what the serial number is?
What about the box - do you still have it? The serial number is on the box as well...
I would *hope* that the Asus warranty doesn't need to have that stupid sticker in order to get warranty coverage!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Are you saying that Asus won't even initiate the RMA process because you don't know what the serial number is?
What about the box - do you still have it? The serial number is on the box as well...
I would *hope* that the Asus warranty doesn't need to have that stupid sticker in order to get warranty coverage!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply.
I used to keep EVERY original box... and yes, I do remember the serial number being there, but the ONE TIME I need the serial number, and all it is is a flimsy sticker on the device itself... And the ONE TIME I don't have the box.
I was able to get the RMA created, but I had to use the serial # of my second TF700. So now, the only way I can send it in would be to move the sticker. I have a funny feeling they'll just send it back saying that this is not the Droid we were RMA'ing for.
It also seems like they would have SOME WAY to just let the end user put back a stock bootloader on the device, then we would all save a lot of time! Other than the fantastic learning experience here, I really want to find a way to salvage this completely useless but fascinating piece of technology.
I wonder if NVidia could help with this... probably not. I guess I'll look.
There must be some way to get a stock bootloader back on my TF700!!!!
Wait a minute man can you boot on Fastboot mode? When you turn on with volume down you can choose the mode to start?
ScaryBob said:
I was able to get the RMA created, but I had to use the serial # of my second TF700. So now, the only way I can send it in would be to move the sticker. I have a funny feeling they'll just send it back saying that this is not the Droid we were RMA'ing for.
Click to expand...
Click to collapse
Chance is high, for it is embedded in the system somewhere and I doubt they will let the opportunity slip to make you pay. Unfortunately.
As a previous replicant asked: does fastboot work? You could push over a new recovery.img then...
MartyHulskemper said:
Chance is high, for it is embedded in the system somewhere and I doubt they will let the opportunity slip to make you pay. Unfortunately.
As a previous replicant asked: does fastboot work? You could push over a new recovery.img then...
Click to expand...
Click to collapse
Right, so if the serial# is etched in a tiny bit of truly ROM, why are they so hell bent on seeing the sticker... I'd gladly pay $50 for a program, blob, or special key sequence that can get me back to a stock bootloader. That would cost ASUS really nothing to provide in terms of loyalty to their brand and saving them countless hours in tech support.
No, I don't think fastboot works. I never get the "fastboot" message on the screen -- either it's stuck on "Booting recovery kernel image" with Power/VolumeDown or a blank screen with Power/VolumeUp (and then recognized with the APX driver). I've tried adb, fastboot, nvflash in both modes, and nada. Is one of those SUPPOSED to work in either of those scenarios? If so, I'll try again... it has now gone beyond the economics and is now in the realm of "the principle of the thing" or "I climbed the mountain because it's there". Plus, I'd really still like to have two operating TF700s.
ScaryBob said:
Right, so if the serial# is etched in a tiny bit of truly ROM, why are they so hell bent on seeing the sticker... I'd gladly pay $50 for a program, blob, or special key sequence that can get me back to a stock bootloader. That would cost ASUS really nothing to provide in terms of loyalty to their brand and saving them countless hours in tech support.
No, I don't think fastboot works. I never get the "fastboot" message on the screen -- either it's stuck on "Booting recovery kernel image" with Power/VolumeDown or a blank screen with Power/VolumeUp (and then recognized with the APX driver). I've tried adb, fastboot, nvflash in both modes, and nada. Is one of those SUPPOSED to work in either of those scenarios? If so, I'll try again... it has now gone beyond the economics and is now in the realm of "the principle of the thing" or "I climbed the mountain because it's there". Plus, I'd really still like to have two operating TF700s.
Click to expand...
Click to collapse
I haven't heard of anyone coming back from where you are. I wish you luck. If you are able to recover somehow on your own, you will be giving this community a great gift by sharing your secret.
Personally, I think I'd send it in for an RMA without any serial number sticker. Did anyone at Asus say that the sticker needs to be in place in order to get warranty coverage? Like you said, I'm sure that they can validate the serial number somehow. Even if you gave the wrong serial number by "mistake" when setting up the RMA, they should be able to tell that it's actually covered by warranty if they can get the serial number. If not, they you have nothing to worry about. So, either way, you should be fine!
Unless they specifically said that "no sticker = no coverage" (which I hope is not the case)...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hi:
My tf700t is bricked, no fastboot, only apx after a bad CMW installation, is there any way to restore or re flash using the tools and obvious understanding that you guys have. I really don’t want to send the device back to asus, and will be willing to donate to your site / cause / developers account if you guys could assist me in this matter. Thanks in advance for your time.
jtrosky said:
Personally, I think I'd send it in for an RMA without any serial number sticker. Did anyone at Asus say that the sticker needs to be in place in order to get warranty coverage? Like you said, I'm sure that they can validate the serial number somehow. Even if you gave the wrong serial number by "mistake" when setting up the RMA, they should be able to tell that it's actually covered by warranty if they can get the serial number. If not, they you have nothing to worry about. So, either way, you should be fine!
Unless they specifically said that "no sticker = no coverage" (which I hope is not the case)...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I suppose that is an option -- it's not doing me any good as a brick, the worst they can do is send it back.
I think you'll find that the serial number is probably identified inside the tab somewhere, anyway...
danger-rat said:
I think you'll find that the serial number is probably identified inside the tab somewhere, anyway...
Click to expand...
Click to collapse
In the OP that was mentioned as well, but with the sidenote he didn't really want to open it up.
Mmmh... fastboot not working is not good... not good at all. I don't see any other option then than sending it back and see what ASUS does with it. As you said, the worst they can do is send it back... No, actually.... The worst they can do is repair it, permalock the bootloader and THEN send it back.
MartyHulskemper said:
No, actually.... The worst they can do is repair it, permalock the bootloader and THEN send it back.
Click to expand...
Click to collapse
...and charge $380 for it (there was some quote in another thread).
_that said:
...and charge $380 for it (there was some quote in another thread).
Click to expand...
Click to collapse
No, that's if they do absolutely nothing but write a check. (In that thread, at least in my memory, nothing was even actually done on that 700. )
when you guys mean "bad CWM install" what exactly does that mean so we can make sure we can save a few extra souls from doom?
Im pretty sure that is when they install CWM through the Rom Manager app.
mj23kb24 said:
Im pretty sure that is when they install CWM through the Rom Manager app.
Click to expand...
Click to collapse
Yes, since a few days after release (at most), we've known that Rom Manager is not compatible with the TF700. That's why you do not see it in any tutorial. Failure to read before doing leads to bricks in very, very many cases, and the 700's case is no different.
As we've concluded before, in terms of OP relevancy, I guess that sending you expensive baby in anyway would we the way to go (now if you'd only have fastboot available...).
Hey guys, you bunch seem like a smart group, so I hope yous dont mind if i post my problem here as well. Its an odd problem actually. I have CWM, fastboot, all working on my infinity, but cannot for the life of me get it to boot anything. It hangs at the first Asus splash screen and wont move from there. Ive flashed various different roms and recovery always says its successfully installed, but when i reboot it doesnt move past the first splash asus screen. Any ideas, i kinda have exams this week and my notes are on my tablet stupid me. Cheers fellas.
Sent from my GT-I9300 using xda app-developers app
WoodenAnts said:
Hey guys, you bunch seem like a smart group, so I hope yous dont mind if i post my problem here as well. Its an odd problem actually. I have CWM, fastboot, all working on my infinity, but cannot for the life of me get it to boot anything. It hangs at the first Asus splash screen and wont move from there. Ive flashed various different roms and recovery always says its successfully installed, but when i reboot it doesnt move past the first splash asus screen. Any ideas, i kinda have exams this week and my notes are on my tablet stupid me. Cheers fellas.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
You need to provide some more info, are you on Jelly Bean or ICS? When this issue started? More details = higher chances to get help and solve your issue.
Lol sorry, i should know this by know. Was a long day. Uhh yes i was on a JB custom rom When the issue started. The rom had a couple hickups so i wanted to go back to my old one, so i did the nornal, nandroid, titanium backup, etc and flashed new rom. I believe what it did was delete the recovery image that it had, and then attempt to put on a new recovery as some roms do (to much annoyance) but this particular time it failed to install the new recovery for one reason or another. So i had no recovery for a while till i flashed it with fastboot, cwm 6.0.14 i think. So i tried doing a restore before this all happened, and recovery said it successfully restored, but when i reboot, it holds on the asus splash screen. Same with any Roms. And yes I wiped everything as well. Is that enough info?
Sent from my GT-I9300 using xda app-developers app
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.
Before the hate police flood my new thread - yes I have searched xda for the answer(s) - but haven't had any luck. I've searched for 2 weeks before writing this.
I did a stupid thing. My device is unlocked and rooted but still had the Asus OS and i tried to change the fonts. Now it won't get past the ASUS boot screen. I also don't get the 3 (or 4 or 5) icons that are supposed to come up.
I've tried the power/volume buttons, motochopper, the Asus unlock (probably unnecessary) and a number of other things my searches but no luck.
I'm trying to find a step-by-step guide that can possibly help me with my particular problem.
After I completely get it going again I am going to install Cyanogen or KKrombi or some other OS.
This is a process that I am famliar with and have been doing since my T-Mobile G1 to my OPO without problem, but this time I am stumped.
Thank you for your time and help. Just point me to another thread or something & I'll take it from there.
How did you try to change the fonts??
Never heard before that somebody hard bricked the tablet that way and that's what you did it seems. Hate to tell you this, but if you cannot get into the bootloader (screen with 3 icons) this tablet is toast.
berndblb said:
How did you try to change the fonts??
Never heard before that somebody hard bricked the tablet that way and that's what you did it seems. Hate to tell you this, but if you cannot get into the bootloader (screen with 3 icons) this tablet is toast.
Click to expand...
Click to collapse
Bugger. I used Rom Manager to do it. It's funny I saw the icons once but not since.
Yeah bricked sounds right.
dnmoscato said:
Bugger. I used Rom Manager to do it. It's funny I saw the icons once but not since.
Yeah bricked sounds right.
Click to expand...
Click to collapse
Yep, using ROM Manager has bricked quite a few of these babies. That explains it. Sorry man....
I know you mentioned using various tools already, but have you tried fastboot commands with it connected directly to your computer?
Sent from my Nexus 6 using Tapatalk
It's something that I've tried but never been able to do it correctly - well not since my G1 - and that was step-by-step from Cyanogenmod pre-Inc.
Didn't see bernblb's second reply. If he says it is bricked, then it most likely is. I haven't toiled around on my TF700 for a long time now.
Sent from my Nexus 6 using Tapatalk
Yeah it probably is. My own fault. Trouble is it really suited my wants and needs. Guess it's back to Swappa.