hello, several days earlier, my eepad transformer got bricked without reason,
i tried to flash it with NVflash, but still didn't work.
i have rf B50 at the time.
after googling and searching in the internet, i didn't find any good solution, so i decided to claim the warranty to the asus service center,
and after 3 days, i got my transformer back, the customer service told me that there's a malfunction in my transformer's mainboard / generally a hardware issues, so they replaced the mainboard with a new one.
well, i didn't ask them what version of mainboard did they replace to my TF, i just afraid they would know that i have rooted my tf before where it'll cancel the warranty lol.
so now i want to root/install a custom rom into my tf, but i still couldnt find out what B version is my hardware ,well if im guessing , it'll be between b70 or b80, but i still don't want to take the risk though,
so im asking , is there any way to check the hardware version of my TF now? with software/application?
since the version of course didn't matched again with the box/warranty card,
if there isn't any way, what risk could i possibly have with doing random method to root my transformer?
if it's bricked, can i reflash it with nvflash? did the latest version(b80?) can be reflashed with nvflash?
sorry for the long questions,
i hope i'll get the answer i want
On those models NVFlash still won't work.
There is a tool called SBKDetect in the Developer sub-forum. You can check with that. If you have V2, then NVFlash won't work, but it is possible to root with other method.
thx for the info, i'll go search the sbkdetect right away,
btw, what root method is working for the b70/b80 right now? and which one is the safest/working method?
im a little bit confused, since i always use nvflash to reflashing and rooting.
uman01 said:
thx for the info, i'll go search the sbkdetect right away,
btw, what root method is working for the b70/b80 right now? and which one is the safest/working method?
im a little bit confused, since i always use nvflash to reflashing and rooting.
Click to expand...
Click to collapse
Razorclaw
http://forum.xda-developers.com/showthread.php?t=1345049
all right, i rooted my tf with the razorclaw method , thx for your help, i think i'll start learning how to install custom rom without nvflash now
oh yes, and one more question, if my transformer got bricked again, not in hardware issue, i mean like normal brick where you can save it with nvflash,
is it possible to unbrick the b70/b80 asus transformer?
if yes, what method can i use?
not soft bricked where you still can turn on your transformer/enter recovery mode,
but normal bricked where you cant even turn on your transformer, but for the b50/b60 still can be saved by using nvflash method
uman01 said:
oh yes, and one more question, if my transformer got bricked again, not in hardware issue, i mean like normal brick where you can save it with nvflash,
is it possible to unbrick the b70/b80 asus transformer?
if yes, what method can i use?
not soft bricked where you still can turn on your transformer/enter recovery mode,
but normal bricked where you cant even turn on your transformer, but for the b50/b60 still can be saved by using nvflash method
Click to expand...
Click to collapse
AFAIK no. Only possibility is NVFlash, but that does not work for those ATM.
all right, thanks for the info
i'll be more careful than in customizing my tf from now on
Related
Purchased an Asus Transformer about 2 weeks ago on Amazon and received a B07...the screen on it ended up having some discoloration on the sides where when something black was playing, you could see white/green discoloration marks near the edge...needless to say, I sent it back to Amazon and they just sent me a B05. Did I get lucky?
Cause I'm looking to root...And apparently I can root this model, but not the last one?
I have Windows 7. There's seems to be several different methods to root this device. I'm running 8.3.2.9.
Is it best to upgrade to Honeycomb 3.2 before you root, or after? Or should I stay with 3.1 Honeycomb...someone let me know and send me some links/files I need to get to root!
Appreciate it mucho!
Simply use the NVFlash method, that's the easiest way to do!
http://forum.xda-developers.com/showthread.php?t=1123429
Do I need to update my firmware or update to HC 3.2 before I NVFlash?
Ultimately what I'm wanting is a rooted Honeycomb 3.2 tablet...
Well, you need to grab an NVFlash package. In this very part of the TF101 forum, you'll find a lot of (actually, 3) ROMs what are rooted, optimized, and fine-tuned. I suggest you to try Prime 1.9, it's really great!
So, all you have to do is to download the NVFlash version of Prime (or any other ROM you want to install), and follow the NVFlash instructions. It will update your TF to 3.2, root it, etc.
You do not need to update to anything, as NVFlash is totally separate from Android - imagine it like a safety switch, what can be flipped if your device gets bricked (=means it won't really switch on due to software problems). It's a separate mode, can not be modified, etc.
Read this
http://forum.xda-developers.com/showthread.php?t=1268458
You should have posted in the Q&A section.
Asking a bloody obvious stupid question to which you require an answer in a DEV section is fail.
sorry to barge in but i am going to get a transformer in a few hours and i am thinking i could easily install custom roms out of the box? also does this work on all models?
CaNsA is right this shouldnt be here.
GTFO
10chars
Moderators are still too slow in here...
Sent from my Transformer TF101 using Tapatalk
TheScPCrew said:
Purchased an Asus Transformer about 2 weeks ago on Amazon and received a B07...the screen on it ended up having some discoloration on the sides where when something black was playing, you could see white/green discoloration marks near the edge...needless to say, I sent it back to Amazon and they just sent me a B05. Did I get lucky?
Cause I'm looking to root...And apparently I can root this model, but not the last one?
I have Windows 7. There's seems to be several different methods to root this device. I'm running 8.3.2.9.
Is it best to upgrade to Honeycomb 3.2 before you root, or after? Or should I stay with 3.1 Honeycomb...someone let me know and send me some links/files I need to get to root!
Appreciate it mucho!
Click to expand...
Click to collapse
Actually you're on a firmware that can still be root using
the old method.
Your choice but NVFlash is probably better.
ADB
http://androidroot.mobi/technical/asus-eee-pad-transformer-tf101-root-cwm-recovery/
NVFlash
http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
TheScPCrew said:
Do I need to update my firmware or update to HC 3.2 before I NVFlash?
Ultimately what I'm wanting is a rooted Honeycomb 3.2 tablet...
Click to expand...
Click to collapse
No you don't need to upgrade. NVFlash work for all firmware.
Hey all,
Sorry but I'm new at rooting and android in general. I just picked up a transformer for black friday and am debating rooting it. I was wondering if nvflash will work with my tablet (B90...sbkv2) and if not, if you have any idea if/when it will be made to work with it. I don't want to root and flash another rom onto the tablet if there's a large risk of bricking it. Also, I was just wondering in general what the chances are for bricking a tablet by flashing a rom.
Thanks a lot!
dkleinrodick said:
Hey all,
Sorry but I'm new at rooting and android in general. I just picked up a transformer for black friday and am debating rooting it. I was wondering if nvflash will work with my tablet (B90...sbkv2) and if not, if you have any idea if/when it will be made to work with it. I don't want to root and flash another rom onto the tablet if there's a large risk of bricking it. Also, I was just wondering in general what the chances are for bricking a tablet by flashing a rom.
Thanks a lot!
Click to expand...
Click to collapse
NvFlash won't work, but the guide below works without problems. There is little chance of bricking it, but the chance still exists.
TBH, I have never seen someone with a completely bricked tablet due to software reasons. Software problems are fixable in most cases, altough it can take a few days to find the right fix.
One legal notice: I won't pay if you brick your tablet, so you don't have to believe me. And rooting will probably break the warranty.
http://forum.xda-developers.com/showthread.php?t=1347388
I was wondering about this too. I have a B90 and my biggest concern is if flashing a custom ROM glitches and messes up recovery.
It happened on my phone recently, and I was stuck with no recovery or firmware but luckily had an equivalent of NVFlash. I'd be worried if I didn't have this available, just in case.
How is CWM installed? Is it likely to become damaged or lost? Or is it deeper embedded to stop that from happening?
I really wanna get a custom ROM on it but I'm absolutely terrified of bricking it given there's no fallback :/
I used Debugfs tool to root and superuser was installed. I downloaded the OTA RootKeeper and Titanium Backup and backed up my apps. I opened OTA RootKeeper and temporarily disabled root. I then opened the notification bar and clicked on Asus firmware update, I then got the page asking me if i wanted to install or postpone and I chose install. The screen went dark a then a short while later I got the screen with android lying on its back with a red exclamation point and then a notice that the update failed. I went to settings>about tablet and checked for firmware update and got there is no firmware update available. I am still on ICS 4.0.3 and build.26. So, how do I update to JB? Thanks
Since first posting this question I have d/l ASUS Transformer Pad TF700T Firmware: V10.4.4.20 Only for US SKU (Android 4.1.1 . I extracted the files so that I now have updatelauncher.zip. But, when I boot into recovery it says it failed because itcould not find the update zip. I am rooted and I have the Voodoo Rootkeeper app that I use to temporarily disable root before I boot into recovery.
I called Asus support about the automatic OTA update not installing and he told me not to worry that it will show again shortly. Will it still show up automatically if I am rooted and if it does do I have to use the OTA Rootkeeper to temporarily unroot?
If you plan to unlock your device, consider doing it before upgrading anything so that you can pull the blob for nvflash - this is no longer possible once you upgrade.
_that said:
If you plan to unlock your device, consider doing it before upgrading anything so that you can pull the blob for nvflash - this is no longer possible once you upgrade.
Click to expand...
Click to collapse
I tried the nvflash but I am not advanced enough to do it. Doing nvflash on this device is a lot more complicated than on my Viewsonic G tab. I have faith that someone in the community will figure out how to nvflash in JB. The last time I tried onthe TF700 I bricked it and had to send it back to Amazon, luckily I was sill in the 30 day period.
Can you help me to install JB?
lartomar2002 said:
I tried the nvflash but I am not advanced enough to do it. Doing nvflash on this device is a lot more complicated than on my Viewsonic G tab. I have faith that someone in the community will figure out how to nvflash in JB. The last time I tried onthe TF700 I bricked it and had to send it back to Amazon, luckily I was sill in the 30 day period.
Can you help me to install JB?
Click to expand...
Click to collapse
Do you plan to unlock your device so you can use custom rom later? We need to know up front so you don't waist too much time.
buhohitr said:
Do you plan to unlock your device so you can use custom rom later? We need to know up front so you don't waist too much time.
Click to expand...
Click to collapse
This is my dilemma. On the first TF700 I unlocked and rooted it but when I tried to setup NVflash I got stuck. and could not figure out which of the drivers to use or where to put them. I called in a Windows expert and he spent a little time with it and then he threw his hands up and stopped because he did not want to take the chance of bricking the tablet. Because he could not do it he did not charge me. I then contacted a computer repair service and the person I. talked to said he could do it. Long story short he could not do it properly also but because he had to come to my house his company required he charge me. I will not tell you what I had to pay him, needless to say it was outrages. So I tried my hand at it again and that is when I. bricked it and luckily got a RMA from Amazon. My wife was so upset with me and at what we had to pay for and that we got nothing in return for. The whole situation was more than I am willing to go through again. I nor my wife are young anymore and can not afford the blood pressure spikes we had. I made a promise to her that I would not attempt to. setup nvflash with this replacement tablet. I know I do not need nvflash to install a custom rom but it can sure save your butt if you mess up. So, to answer your question I would have to say no I will not unlock it and lose my warranty. I can not afford to lose the $485.00 I paid for it. I truly wish it was different, I no longer have the "nerves of steel" that is required. So, can you help me to update to stock JB with the info I gave in the previous post?
No need to temp unroot either, for next time....
53fireman said:
No need to temp unroot either, for next time....[/QUOTE/]
Do you mean the "next time" that the Asus stock JB firmware update appears in the notification bar?
Click to expand...
Click to collapse
Hey guys,
I sent my device to Asus a couple of days ago for repairs.
Asus did a great job on repairing my screen, but... um..
they have undone my root access and they've also relocked my bootloader, I think, although I can't get any OTAs.
Original question was:
What can I do to get my root again, because the scripts of sparky's tool don't seem to work anymore...
Sorry for this noobish question, but I swear that this has never happened to me before (and I have unlocked and rooted numerous devices)
What kind of sorcery is going on?!
Click to expand...
Click to collapse
Then I found the answer thanks to these amazing guys answering and trying to help.
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
It might seem complicated, but it really isn't.
Good uck to those who follow(ed) my path
adelancker said:
Hey guys,
I sent my device to Asus a couple of days ago for repairs.
Asus did a great job on repairing my screen, but... um..
they have undone my root access and unlocked bootloader.
Click to expand...
Click to collapse
You mean relocked your bootloader?
...or actually unlocked it?
Thats OK said:
You mean relocked your bootloader?
...or actually unlocked it?
Click to expand...
Click to collapse
Sorry for that!
I meant that they relocked my bootloader, but still I can't get any OTAs
Thanks for the answer by the way.
I'd like to get it back to CR asap, since I really like that ROM, but noone has helped be yet
That is, until you arrived!
Ah
If we can get you successfully unlocked then the flashing can begin.
Have you tried unlocking via the Asus unlock .apk?
Seem as tho some tab owners have had problems with the Asus unlock tool.
I actually have the exact same problem.
Tablet back from screen repairs and now my root is gone, clean JB is installed and I can't seem to unlock (I wasn't unlocked before though).
I tried unlocking within the newest firmware with the ASUS Unlock app, failed with the "Unknown error occured, this could be a network problem".
Then I decided to atleast fix me root so I downgraded to .30 (ICS) and RootDebugFS fixed my root access.
Still my unlocking fails.
My serial is still the same btw.
DarkFire1985 said:
I actually have the exact same problem.
Tablet back from screen repairs and now my root is gone, clean JB is installed and I can't seem to unlock (I wasn't unlocked before though).
I tried unlocking within the newest firmware with the ASUS Unlock app, failed with the "Unknown error occured, this could be a network problem".
Then I decided to atleast fix me root so I downgraded to .30 (ICS) and RootDebugFS fixed my root access.
Still my unlocking fails.
My serial is still the same btw.
Click to expand...
Click to collapse
Thanks! I guess I'll downgrade to .30 as well, root it there and maybe attempt to unlock my bootloader.
I really wish to have CR again, so there's no option that this will not work (eventually)
Thats OK said:
Ah
If we can get you successfully unlocked then the flashing can begin.
Have you tried unlocking via the Asus unlock .apk?
Seem as tho some tab owners have had problems with the Asus unlock tool.
Click to expand...
Click to collapse
Shouldn't I first have root?
Or directly try to unlock the bootloader.
adelancker said:
Shouldn't I first have root?
Or directly try to unlock the bootloader.
Click to expand...
Click to collapse
My own experience included unlocking as a first step.
The reason was that I found it ultimately easier to install the CWM recovery thru ADB.
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1 <<<< The confusing guide is here.
After some study then trial we were successful!
Are you familiar with fastboot or opening a terminal (DOS like cmd window) on the PC?
ADB (Android Development Bridge) is a command prompt that will speak to the tablet thru a USB connection.
All of this is available with Androids platform tools.
I keep a tools folder on my PCs desktop so I don't have to search for it. (Platform tools can be downloaded)
I know all this is somewhat intimidating on first encounter...hopefully we can walk thru and get things up and loaded.
Thats OK said:
My own experience included unlocking as a first step.
The reason was that I found it ultimately easier to install the CWM recovery thru ADB.
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1 <<<< The confusing guide is here.
After some study then trial we were successful!
Are you familiar with fastboot or opening a terminal (DOS like cmd window) on the PC?
ADB (Android Development Bridge) is a command prompt that will speak to the tablet thru a USB connection.
All of this is available with Androids platform tools.
I keep a tools folder on my PCs desktop so I don't have to search for it. (Platform tools can be downloaded)
I know all this is somewhat intimidating on first encounter...hopefully we can walk thru and get things up and loaded.
Click to expand...
Click to collapse
Thanks for all the help!
It's not the first time I root (and/or) unlock a bootloader. It's just that now, those super easy root command methods don't work anymore. I have done completely manual rooting in the past, but I am not sure that will work either.
Besides, I got adb running before on my Infinity, but I'll make sure to downgrade to ICS first before doing anything else.
Here's what I am going to do:
1) downgrade to .30
2) try to root (with or without sparky's tool )
3) unlock bootloader (although I'm not sure if that'll work, judging from the comment of the Dutchman above)
I'll let you know in this thread if it worked or not.
My prediction: root will work, unlocking bootloader won't, since it's already been unlocked one and therefore my serial number is already in their database!
So i got my infinity like 2 weeks ago. The first thing i tried to do was to root it. I plugged in my device, installed drivers and checked unknown sources and usb debugging. I opened debugfs and tried to root my device but it suddenly closes. Whats likely to be the problem. And no i dont have asus sync installed.
P.S i returned my infinity on amazon as there was a hardware problem. Ill get the new one in a couple of days.
Thanks in advance.
Good luck with trying to get it unlocked (again)! If it doesn't work out in the end, you might want to drop Gary Key a line. Even if he is currently serving the USA himself, he might give you a pointer or a contact inside ASUS' support division. It's likely this is a "serial number in database" issue -- I'd like to believe that with some handiwork, this should be relatively simple issue to tackle, IF the engineers have access to that database at all. (With only Gary's answers to go on, I'd say ASUS HQ seems to keep its cards close to the chest.)
There's no way around the bootloader checking the staging partitions, right? Damn shame we can't just flash to it directly, ODIN style (which admittedly was not a perfect solution, but it is better than being locked out of your on device, essentially).
MartyHulskemper said:
Good luck with trying to get it unlocked (again)! If it doesn't work out in the end, you might want to drop Gary Key a line. Even if he is currently serving the USA himself, he might give you a pointer or a contact inside ASUS' support division. It's likely this is a "serial number in database" issue -- I'd like to believe that with some handiwork, this should be relatively simple issue to tackle, IF the engineers have access to that database at all. (With only Gary's answers to go on, I'd say ASUS HQ seems to keep its cards close to the chest.)
There's no way around the bootloader checking the staging partitions, right? Damn shame we can't just flash to it directly, ODIN style (which admittedly was not a perfect solution, but it is better than being locked out of your on device, essentially).
Click to expand...
Click to collapse
Thanks for the support!
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
DarkFire1985 said:
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
Click to expand...
Click to collapse
Hmm... No idea what that could be.
I managed to unlock it, but that was after I reverted to ICS .30 (not obligatory, from what I understood ) I didn't use the Unlock Tool from the Asus website itself but an older (ex-official) Unlock Tool. (v7) I think it was.
I'll have a look and see if I can find it.
That might be the same as the one from the ASUS website but if you could provide me the file or md5 sum I can compare it.
adelancker said:
Thanks for the support!
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
Click to expand...
Click to collapse
So glad to read that you have been successful.
...and do have fun flashing\updating\customizing!
DarkFire1985 said:
That might be the same as the one from the ASUS website but if you could provide me the file or md5 sum I can compare it.
Click to expand...
Click to collapse
The unlock tools provided by ASUS to unlock the TF201, TF300 and TF700 have been proven to be identical files (by checksum verification) --- no need to reinvent the wheel there.
The unlock step indeed is crucial -- and it depends on ASUS' database. If you can't get past that, there'll no flashing available in terms of recoveries (and therefore no custom ROMs either). Have you tried dropping Gary a line yet?
No not yet. Will do that.
Sent from my ASUS Transformer Pad TF700T using xda premium
DarkFire1985 said:
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
Click to expand...
Click to collapse
Maybe you should have a look here. Seems like there were a couple of guys capable of unlocking it after all, and they were in the same situation as you.
I checked and the bootloader unlock tool was indeed an offial asus one. I downgraded before unlocking, but I saw you did too...
No idea what else I can do to help.
Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?
NeoMatrixJR said:
Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
Click to expand...
Click to collapse
For unlock your tablet, the only way is to use the UNLOCK TOOL V7
After, once your tablet unlocked without problem
You can just followed this guide : [ROOT/ROM] Root Stock/Deodex Firmware 10.4.2.20 (US/WW) | Insecure kernel !.
It's exactly for you.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
Click to expand...
Click to collapse
No way by this side...If you use the Unlock tool, you loose your warranty, it's one fact
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?
Click to expand...
Click to collapse
And actually and for my part the most functional as recovery is TWRP, but if you want to use CWM, no problem for use it too