So here's the deal. I got TF from best buy. It is a B70. Honestly, I'm usually more careful and meticulous about things, but I attempted to root it without checking whether or not it was rootable. I did not check the SBK. It says it's version 1 now, but I'm wondering if it's possible that it changed when I did the following:
I used the One-Click Universal root for stock firmware - V4 and needless to say it didn't exactly work right. I also told it to install CWM recovery. It said update success while running the script except when it got to the last part where the TF is suppose to reboot. It just stayed there and didn't do anything.
So I rebooted it, and I got bootloops at the initial boot screen before it even tried to boot android. I didn't give up though(I've done much worse to some of my phones). When I put it into recovery to my surprise CWM came up. However, after a short time it would freeze and I'd have to hold the power button until it started the bootloops again.
So here is what I did after that. I loaded revolution HD and wipe zips on an SD card. This took some practice at getting right, because I had to make them as easily accessible as possible in CWM so that I could run them before it froze. I messed around with this a lot and sometimes it will freeze right as the zip is getting started. You just have to try again. Once the zip gets going though it won't freeze. Well, I got rev. HD to install, and it booted fine. Rooted and all.
I went back and flashed the latest CWM available for the TF, and that stopped the CWM freezing as well.
I followed the root method exactly, and as explained, it didn't work right. What I am honestly wondering is if my B70 had SBK2 and somehow I was able to sort of fawk it up and then root it?
I don't understand the exact process, and maybe it did just come with SBK1 and it was a freak process...So I may just sound like an idiot right now, but I wanted to bring it up anyway; since I know a lot of people with B70 and B80 can't root yet.
ph0tios said:
So here's the deal. I got TF from best buy. It is a B70. Honestly, I'm usually more careful and meticulous about things, but I attempted to root it without checking whether or not it was rootable. I did not check the SBK. It says it's version 1 now, but I'm wondering if it's possible that it changed when I did the following:
Click to expand...
Click to collapse
You can not change the SBK. You probably have an early build B7O
baseballfanz said:
You can not change the SBK. You probably have an early build B7O
Click to expand...
Click to collapse
Yeah I was guessing that is the case. I just figured I'd ask since it went a little haywire when I attempted to root it.
whats the first 8 of the s/n
Related
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>
Yeah, I wasn't thinking at all. I ran my update check, got excited and just did it. It wasn't until after the fact that I really realized what I might have done.
Well, here's everything that happened/is happening.
I was trying to root my pad and get cwm. The pad was running stock 3.1 at the time this.
Well, after a bit of reading and looking around, I decided the easiest way would be to use the batch script located here: http://forum.xda-developers.com/showthread.php?t=1185104
After setting everything up, I ran the script. My tablet was rooted, I could gain superuser access, and busybox was installed as well...however, I could not get into recovery. At all.
In the zip for the rootkit there are two versions of recovery.img, one to use if the other doesn't work...
Well they both didn't work.
So I play around on my tablet for a while and read about 3.2, check my updates and see that I can get the 3.2 update. I do it, install it.
Stupid.
Now the pad is stuck on the Eee Pad screen with the Asus and nVidia Tegra logo.
I can get into APX mode as well as make the tablet attempt to boot into recovery (though it just hangs on "Booting recovery kernel image").
Can't even turn it all the way off, it just hangs.
I tried downloading the v5 (now v6) script from the above thread, and used all of the options included within, including the 3.2 root & recovery. To no avail.
Seems pretty grim.
My phone is a Samsung Epic which I've rooted, flashed roms, upgraded/downgraded Android... With the phone there's a program to completely unroot and flash back to stock. Is there something like that with tablets?
I might've dived into rooting my tablet before reading enough, I read a significant amount before I did anything to my phone, but I convinced myself the prior experience would make this easy. Obviously not the case.
So...any help would be hugely appreciated. Even if it's just telling me that there's not really anything I can do, because I'll be able to take it back for another (though that can be complicated and is preferably avoided).
since you can get to apx mode try nvflash with stockrom to 8.4.4.5 by following these instructions.
http://tabletroms.com/forums/showthread.php?1071-Factory-3.1-NVFlash-Recovery-Roms&p=9968
You'll then need to upgrade to 8.4.4.11 then to 8.6.5.6 before attempting to root using the v5 beta batch root script http://forum.xda-developers.com/showthread.php?t=1185104
That should get you out of trouble. good luck.
IMHO the problem is the recovery.
The ota updates rely on the stock recovery image for doing its dirty work; for what you wrote, it seems that you have installed cwm...
In the batch script hit "5" to reinstall stock boot+recovery us images.
If this won't work, try the woonie's hint.
Hope this helps.
woonie said:
since you can get to apx mode try nvflash with stockrom to 8.4.4.5 by following these instructions.
http://tabletroms.com/forums/showthread.php?1071-Factory-3.1-NVFlash-Recovery-Roms&p=9968
You'll then need to upgrade to 8.4.4.11 then to 8.6.5.6 before attempting to root using the v5 beta batch root script http://forum.xda-developers.com/showthread.php?t=1185104
That should get you out of trouble. good luck.
Click to expand...
Click to collapse
Woonie is correct, I did this to myself last week. After using NVFlash to get back to stock 8.4.4.5, do not let the pad restore settings from your gmail account. Wait for that until after you have it upgraded to 8.6.5.6 and rooted it again to sync up to your account.
http://forum.xda-developers.com/showthread.php?t=1192072&page=2
I follow jhanford's post and get this done.
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
I noticed after taking one of the lineage updates I lost root. I tried to reroot with odin and managed to pork my phone quite good. It took me until about now to get it rooted, unlocked and finally TWRP loaded. Recovery was fighting me the most. Refused to install in odin. I finally got a working rom on it so it would boot. Used casual to root and unlock but TWRP failed in that as well. I finally tried a TWRP app (not the official one, I couldn't get that to work) and I may have my phone back now. Waiting to see if my backup is going to work. Welp, it didn't like the restore and I got the ! triangle saying go back to verizon.
While I was looking through my drives I noticed I have a ton of files but don't know exactly what they are. I've had this phone since I pre-ordered it so at one time the files were valid. What files exactly do I need to totally unpork a phone? I have odin 3.07, the VRALEC bootchain, the VRALF one but odin says it's invalid, and a file called combination_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship. Using them I can get my phone back to seemingly stock.
Is there a better way? Or at least a way to totally start from scratch and hopefully get lineage back on? I know not to take any of the OTAs since they will relock the bootloader. I don't like that it seemed that it was going to automatically install the update but I'll just keep the phone off until I can sort it. I also have a bunch of other files across 3 computers so if there is a file that's needed but isn't posted somewhere there is a chance I might have it already.
I've been searching for the past day and I've found tons of info but some things don't work and some only kinda work. Any help would be much appreciated.
More info: I am on 4.04 so the bootloader should not be locked. The phone is beat up and the USB connector is wonky. Only a few cables will work and I have to make sure it doesn't move or it will disconnect. It does mention that the secureboot is enabled in download.
I've had it rooted, running a stockish rom and managed to get TWRP on it but when I went to restore my lineage backup, it all went to hell.
So I'm now having issues with the bootloader. ON the download screen it says custom binary download yes (5 counts), Current binary samsung official, system status official and secureboot enable. Pretty sure that means casual didn't work. I have root but not bootloader. Is there another option than casual? I've seen ez unlock 1.2 mentioned but the links are dead.
Why am I remembering flashing something in stock recovery? It's been a long, long time since I've gone back this far. I feel like I'm close since I saw the unlocked screen last night but restoring screwed that all up.
This doesn't make sense. I installed TWRP but it still says the same as above leading me to think my bootloader is not unlocked. I don't get the unlocked boot screen either.
How can I install TWRP with a locked bootloader?
Well it's obious that I can get root, install TWRP but for some reason casual will not unlock the bootloader. I can't seem to find the old thread nor any files to just unlock the bootloader. I know somehow I did it last night as I saw the unlocked screen it's just damned if I can do it now. It must have been another file I had at home but don't have here on the laptop.
It's damn frustrating since this time yesterday I had a working phone running nougat and my dumb ass broke it.
I know this forum is a bit dead, as expected for a 5 year old phone but hopefully someone will see this and have some sage like advice.
Turns out It takes almost a week and a mixture of 3-4 guides here. Some Odin, some Casual, some TWRP flashing and luck. FInally I'm back to where I was before I hit the wrong button.