Related
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
EDIT
Ok guys... I found this...
forum.xda-developers.com/showthread.php?t=589642
It's about hacking spls. Any dev help is appreciated
-------------------------------------
Sent via the XDA Tapatalk App
philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
dude, are you out of your mind????????????
what do you mean? we did not do as the tutorial???? i have flashed my phone over 20-30 times. i did the root perfectly and the brick happenned after 20-30 flashes.
there are even developers who bricked their phones. think before making such comments and better inform yourself first!!!!
starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Please, stop this kind of message .... You will pay a new one to the guy who will brick it ? No ...
And you are talking of something you seems to don't know very well... Some devices have been bricked only by appliyng the 2 steps of the simple root process (without custom rom, a2SD ..) ...
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Man, maybe you should first read and than not post such a s**t. I bricked mine, too, and i think i know what i'm doing. If you would know about what you talk you would see that the cause for the bricked desires is not yet adressed, and that it could happen to anyone who rooted the phone
philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
Click to expand...
Click to collapse
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.
stingerpl said:
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.
Click to expand...
Click to collapse
I dunno man? My usb has been playing up recently. Been rooted since r1 and now I'm having trouble getting in recovery. Get a new and wonderful message everytime!
I've just put it down to my pc being a lazy f*ck! Hahahaha!! I just keep trying 'til it decides to do what I'm telling it to. Always get there in the end, there's no way I'm "unrooting". If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.
MrBadgerMilk said:
If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.
Click to expand...
Click to collapse
Ditto!
10char
Seriously guys, i just don't know how you manage to **** up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.
phentex said:
Seriously guys, i just don't know how you manage to f**k up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.
Click to expand...
Click to collapse
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.
since HTC released the kernel code, I thought it would be easier to revert back to enterily stock
Re: Unrooted :( til we get a stable root. Who's working on this? [THINK TANK?]
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App
starchildx said:
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
And ? Like a lot of those who have bricked their device the 21th flash ....
Seeing as you can't flash over the SPL and radio anyway, once you are successfully rooted, it's probably impossible to get to a state of full bricking. Anything will be recoverable with a gold card and/or a RUU.
Unlike many others, I only got root because I wanted access to paid apps. AFAIK root is needed for that. So I'm running the stock rooted ROM, and the radio update, provided by Paul. I won't flash anything until a rooted 2.2 ROM is out...and who knows...maybe after 2.2 the bricking problem will be gone?
socktug said:
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.
Click to expand...
Click to collapse
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Have flashed a fair few times using all the methords posted on the modaco and XDA forums. all worked flawlessly..... but i too have kept on stock ROM.
Wont flash Customem ROMs untill im either a developer or the spl gets fully opened.
And socktugs right watch your launguage please all
EDIT: As per Stingerpl Suggests if you notice a bootloop occuring take the battery out ASAP!!
It is generally a good idea to take your battery out on first bootloop, go to recovery and nandroid restore. Might save your USB from bricking
I still can't understand why someone would want to unroot because of this. You're already past the risky procedure.
I guess a fully function root need some info about the current root. Anyone know what exploits was used and how its been applied?
maybe the problem is exotic hardware in the pc/laptop. i'm using a standart motherboard with a intel chipset, i never had any problems with rooting or unlocking or flashing any device.
for the people that have problems under linux, what do dmesg say ?
potter1984 said:
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Click to expand...
Click to collapse
Maybe the boot loop has something to do with it... but there are simple ways to avoid a boot loop.
I flashed my desire several times... and had bootloops occur several times. None bricked my phone.. fortunatley!
The reason i found for my boot loops, was NOT WIPING EVERYTHING!
I have read on modaco forums, that Paul's recovery does not clear the dalvik cache, when it is on a partitioned sd card. Maybe it is something to do with the rooting process (no rw access).
The only answer I found, was to re-partition the sdcard everytime. thus wiping all partitions.
So as with any rom you download... READ THE F`ING MANUAL!! its always best to do a FULL wipe. Then your getting the rom, as the developer wanted you to have it.
So not a solution, but some words of advice for noobs! And hopefully we can avoid too many more bricks!!
I will keep monitoring this thread and will update the title if / when we have any developments.
Maybe we need to pray for an engineering SPL
OK so I followed a youtube video tutorial on rooting,and I think it's the boot.img that messed everything up. It would boot up before but it was stuck on the Google screen, the OS didn't load. So I found a GRH78 or something Nandroid backup and ran that, but the capacative buttons don't work, the screen isn't calibrated correctly and the phone radio isn't correct either. Then I remembered my Nexus S was the newer GT-I9023 GRI54 and I need a GRI54 NANDROID stock backup (which I can't seem to find!)
Guys, what do you suggest I do at this point? I can't revert to stock (I've been trying)
I just got this Nexus S and have been spending hours trying to restore firmwares, finding it online, but now I know I need the GRI54 Android 2.3.3 backup, and if anyone has that I'd be super happy
I really need help
you most likely need the 9023 method of rooting
see the stickied guides
I fixed it. I downloaded a GT-I9023 GRI45 firmware file off of somewhere here (<3 xda forums) it wasn't a nandroid backup, but I used the clockworkmod to install it and surprisingly, it booted up again. (of course, I had the crappy 2.1 installed before so maybe this acted as an 'update' and fixed all the problems, but anyways it works smooth now as it did before )
I knew I could figure it out.
Not to be an ass, but I think there's a lot of difference between bricking a phone and being unable to boot. You've never bricked your phone, since you could still switch ROMs by using the Recovery.
This is a misleading title. Bricking is when you just can't enter not even the bootloader/Recovery.
you are 100% right
unfortunately many people keep getting those 2 terms confused, and use it inappropriately
every body needs to chip in and help newbies learn the correct terminology.
thank you
boolean22 said:
Not to be an ass, but I think there's a lot of difference between bricking a phone and being unable to boot. You've never bricked your phone, since you could still switch ROMs by using the Recovery.
This is a misleading title. Bricking is when you just can't enter not even the bootloader/Recovery.
Click to expand...
Click to collapse
Looks like I've managed to act and look like a fool...
I tried to root my Nexus S with Superboot, unaware that it was version-specific (I should have known that ). To make a long story short, I tried to root my phone with Superboot which is written for android 2.3.3, while I'm running 2.3.4.
The phone can get to fastboot/recovery, but won't boot. I googled to find how revert to a stock 2.3.3 or 2.3.4, but somehow did not find what I was looking for.
Phone was vanilla, I hadn't installed anything specific on it besides twitter, FB, etc.
From a powered-off phone, how would I manage to revert to a clean phone ?
Thanks for your help, people.
-- Jeff
<EDIT:
All the solutions I've seen required CWM or similar, and a rooted phone. Since my problems started because I wanted to root my NS, I figured that I was out of luck for a while, and a non-working phone was out of question.
I went at my retailer and managed to get a new phone free of charge I *****-footed around the fact I was installing an unsupported (by the carrier) update/app, the clerk wasn't very familiar with the NS so it went well with them and they gave me a new phone
/EDIT>
Greetings!
I'm new to all this so I apologize if I'm posting in the wrong place. Please forgive me if I am.
I've spent the last hour searching all over these forums and the web in general for the answer to my question, but I haven't seen a resolution.
I have now tried the SuperOneClick root for my Nexus One about a dozen times, and it keeps freezing on "Running psneuter..." and never ever goes any further.
I have tried this on two different computers, I installed the USB drivers from the Android SDK, and I have USB debugging turned on. I've followed those instructions for what happens when you get in the loop, even though they don't seem to apply to this exact situation.
There have been a few other threads here that seem to be about this topic, but they simply die out with no apparent resolution.
Please help! I just don't know what I'm doing wrong.
Any ideas? I'd really like to root my phone, but I'm not sure what I'm doing wrong...
Yeah, USB debugging on is fine..
Have you tried the gingerbreak APK?
digitalface said:
Yeah, USB debugging on is fine..
Have you tried the gingerbreak APK?
Click to expand...
Click to collapse
I apologize for being such a noob to all this, but I'm not familiar with what that was. All anyone talks about in the "blogosphere" is SuperOneClick.
Does the gingerbreak APK simply root the phone and not mod it? For the moment I really just need to root. Eventually I want to MOD too, but first I want to get Titanium Backup Pro on there so I can save some game data before I MOD.
Again, sorry for being such a newbie. I haven't done rooting/modding since my G1 about 18 months ago, and things have changed since that...
I have to admit, I'm surprised how many posts I've seen with the exact problem I'm having, yet nobody has responded with an answer to this issue. There are dozens of comments on the Shortfuse site from other people who are stuck at "Running psneuter," and there are no fixes or even responses, really.
There seem to be many smart people on these forums, so it's strange that this hasn't been worked out or even addressed...
Exact same problem as above.. Locks at "running psneuter"
Pulling the usb then goes to ***IF IT KEEPS LOOPING.. Etc *** and then killing ADP server..
Nexus one
2.3.4
GRJ22
From what little I've been able to get out of others here, it seems that the problem is there's no exploit for 2.3.4 yet.
However, I found a guide to rooting here: http://goo.gl/oCWvR
It requires you to have an unlocked bootloader, a process that basically wipes your phone, so be aware of that. But I'm all rooted now so it's definitely possible to do.
Good luck!
I used the exact same guide.. went to post it to a thread here but as I have low post count I cant post links..
Bootloader was already unlocked.
Heh, well, once you get to SIX posts like I have, you're clearly a big-shot poster But yeah, that's a very good guide.
In the end, though, it wasn't what did it for me. I was still having issues with it, but it got fastboot on my system and got me started. I then followed the instructions on Cyanogen's site and put a different recovery on there in order to get CM7 installed on my phone.
I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
There's a script in the thread that gives you cwm on boot. The catch is it goes to recovery first EVERYTIME you boot.
ubersoft said:
I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
Click to expand...
Click to collapse
In the situation that you describe, even the CWM on boot that mtnlion mentioned, still may not get you into CWM. In that case your ONLY option is to flash the fxz file with rsd lite, that will restore you to a full stock out of the box atrix 2, which you then have to re-root, then re-install bootstrap, then restore your backup.
Sorry there is not an easier way right now, but until the bootloader is unlocked we can't flash CWM, so that we can get to it, as you would the default android recovery, because that does require the default recovery to be replaced, and an unlocked bootloader is required for that to work.
Safestrap is really a tool that is only useful to those actually developing, or people that we have asked to test something out, and since lfaber06 and I don't have a version to release to the public that we are happy with yet, that is not an option.
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
ubersoft said:
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
Click to expand...
Click to collapse
No, if you get a bad flash you still may not be able to get into CWM, since it requires files that are actually in the Android ROM, to fully work. Read my post above ^^^
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
ubersoft said:
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
Click to expand...
Click to collapse
No, it is perfectly safe, but the restore is just a little more complex than you had to deal with, with other phones. I have done exactly what I mentioned above SEVERAL times, with out issue, since I am doing a ton of dev work on this phone.
The ROMs that are out there are great right now, and lfaber06s ROM is really good, and I will be releasing a version of CM7 very soon. If you wait for a bootloader unlock, it may never come, or at least it may not be very soon.
The worst thing that happens is that you have to flash the fxz, which it is documented how to do that with RSD lite very well in the noob thread here. then you can restore your backup with out issue, it is just a few extra steps.
Bootstrap is really safe as is all of lfaber06 Roms right now. I have no problem recommending either of his roms to anyone. They are both very good. As Jim has stated the only problems we have is if something wrong happens on boot, but with the fastboot files, RSD lite, and the one click root method you have everything available to get you right back to where you were before you flashed.
I can promise you everything works very good as I have soft bricked my phone so many rimes in the last 2 weeks that I have become very efficient at getting back to stock, rooting and then flashing a backup with bootstrap and can be back in business n around 20 mins. Just always be near a computer when you start flashing things. One thing that will help out is to keep a backup of the bootstrap on tour SD card so if you have something go wrong you don't have to redownload it again.
We have a very good group of people here and if anyone has any problems we can get you through them and back running
Well there we are then!
So after getting a clearer picture of the situation (thanks for the explanation) I blocked off most of the night, installed bootstrap, then installed lfaber06's Supercharged v4. It took forever, but it worked flawlessly.
Thanks everyone for your patience and encouragement.
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