Database Info

[Q] So today I updated CWM using ROM Manager...

And now I can't boot into recovery, it simply freezes at the "Asus" screen.
A quick flip through the forums reveals that it wasn't the smartest thing I have ever done. I can cold boot into Linux and the transformer works fine but I'd like to get everything up and operational.
I tried using the RecoveryInstaller.apk from gnufabio to no avail. Could someone perhaps provide some assistance on what I should do next? It should be noted that I don't have the faintest clue on how to do the 'adb push' operations I've read about.
TIA

PERI
Use my tool, just ignore the rooting stuff since I'm assuming you're already rooted.
Everytime the tab reboots during the tool, make sure to be hold down Volume-Down and cold boot into Android, then continue the script. Once it has flashed recovery you can close it, it doesn't need the root stuff.
Don't use ROM manager
ToD

Hi and thanks for the help and quick response.
I downloaded PERI and followed the instructions except for the part regarding SU as I already have it installed. For each reboot I ended up having to cold boot into linux.
Unfortunately, the final step where the .bat reboots while I hold the vol -, then hit vol +, gets stuck at the "Booting recovery kernel image" part and will not progress.
I'm not currently running ICS but gingerbread. I probably should have mentioned that earlier, sorry.
What should I try next?

Peri only works on ICS.
Now why on Earth are you running GB on the transformer??? Where did you even get a GB rom?
Do you mean Honeycomb?

Ooops (again)! Yes, you are correct. It was a Honeycomb ROM. An old version of Revolver.

gotreef said:
Ooops (again)! Yes, you are correct. It was a Honeycomb ROM. An old version of Revolver.
Click to expand...
Click to collapse
whats your tf's serial number?

Hi,
The Model is TF101 and the serial starts with B60. Does that help? I know that there are several variants of the transformer out there and I'm not sure what the differentiating markings are.

Nvflash for Sbkv1 is now your best bet, since you have a b60 you can use it on windows fine, good luck :]
Search 'Nvflash unbricking released' and you'll find it.

NV Flash worked like a charm. I really appreciate it, I don't think I would have found that program on my own.

Nextbook Next7P YF0511 series dmesg

Hi all - newb here, first post. I just picked up a pair of Nextbook Next7P tablets off eBay, cheap. One is stuck in a bootloop at the poining finger screen. It doesn't get past this screen, and when the spinning logo stops, then it just starts again, and just keeps repeating this action. The other had a black screen, and thankfully, I had already read in another post in these forums where someone suggested using a LED flashlight on the screen. I was able to see the clock on the lock screen, found the unlock icon, got it unlocked, and eventually found my way to the screen settings, and was able to adjust the backlighting. So now this one tablet is working normally.
Yesterday, I hooked this tablet up to my laptop, after setting the USB Debugging on. I was able to "pull" the system folder and the data folder, so those are now copied to my laptop. I also used the command:
adb shell dmesg > dmesg
I have attached the dmesg file here.
I don't know how to get out of the boot loop on that one tablet, and I think the answer is that I will have to load a new rom. However, since my serial number starts with YF0511, this means my tablet is an early one, and the roms do not work on this tablet.
So my goal here is to find out what specifically is different about these early models, and maybe we would be able to develop or mix a rom using the kernel or modules from this rom, and putting them into the rescue kit, or into a rooted rom.
Maybe someone with a later model could use the adb and post their dmesg file, and we can compare to see what's different. In the long run it will benefit all of us who have early tablets, we could upgrade the roms and maybe even get ICS going.

Update ...
I've made some headway since my last post above. I found a rom for the YF0811 serial number range by Finless, and I decided to go ahead and try this on my boot looped tablet. The rom worked, and appears to be the same rom as my other tablet, which is the original stock rom - never been updated.
So although my original intention was to get some kind of rom development going for the YF0511, there is really no need to do this, the YF0811 roms are the roms to use.
I have seen many posts by people with YF0511 serial numbers, and in virtually every case, they were stuck because they couldn't find a rom for their serial number range. I do hope this will help someone get their tablet working again.

help please
crackitopen said:
I've made some headway since my last post above. I found a rom for the YF0811 serial number range by Finless, and I decided to go ahead and try this on my boot looped tablet. The rom worked, and appears to be the same rom as my other tablet, which is the original stock rom - never been updated.
So although my original intention was to get some kind of rom development going for the YF0511, there is really no need to do this, the YF0811 roms are the roms to use.
I have seen many posts by people with YF0511 serial numbers, and in virtually every case, they were stuck because they couldn't find a rom for their serial number range. I do hope this will help someone get their tablet working again.
Click to expand...
Click to collapse
hello,
I am using next 7p with serial number YF0711 since I bought it I tried to unlock it but all effort has failed,can you please tell me how to unlock it and which rom to use? my email add is [email protected]

khalifat, if you check over on the freaktab forums, in the rom developers kitchen, there are some nextbook roms by Finless Bob. If you go there, you will see in the list Nextbook 7 Premium #0811 Custom Rom with Market 3.4.4 by Finless Version 1.4. I don't think I am permitted to post a link to that.
Anyways, if you get there, that custom rom should work for you. There is also on the same page, further down, a #0811 stock rom. The stock rom will also work, but of course will be lacking in any enhancements.
I have run both of these successfully on my Nextbook 7 premium, with serial YF0511... and everything was working, including wifi. I used the stock rom to get my tablet out of a boot loop, then I tried the rooted rom.
Edit: the rom download contains the rockchip flashing tool and instructions.

[Q] How do you tell the difference between TF101 types

So here I am wanting to break the installed version of ICS on my tablet... I followed the general guidelines on how to root and install the new OS (Revolution). I get myself to this point where I have the zip file on my MSD card and I go to the Power up and - volume to enter into the set up and I have 2 options, one is to boot from the current version I believe that it is a linux version) and the second is the ASUS Recovery image.
I think that I have the one that I can not be changed, is this true? Am I doing something wrong (should I have the TF101 attached by USB to the computer while I am doing this)? Is it possible to change the OS by expanding the zip file into the respective folders and attempt a reboot or will this process create a brick? I am interested in playing with the Ubuntu OS on my tablet too, just to get some experience, I am the computer guy in my area and I have a lot of people that I have talked into the TF101 since it came out and they have been asking if I can figure out this.
Thank you very much for any assistance.

MrWiz1969 said:
So here I am wanting to break the installed version of ICS on my tablet... I followed the general guidelines on how to root and install the new OS (Revolution). I get myself to this point where I have the zip file on my MSD card and I go to the Power up and - volume to enter into the set up and I have 2 options, one is to boot from the current version I believe that it is a linux version) and the second is the ASUS Recovery image.
I think that I have the one that I can not be changed, is this true? Am I doing something wrong (should I have the TF101 attached by USB to the computer while I am doing this)? Is it possible to change the OS by expanding the zip file into the respective folders and attempt a reboot or will this process create a brick? I am interested in playing with the Ubuntu OS on my tablet too, just to get some experience, I am the computer guy in my area and I have a lot of people that I have talked into the TF101 since it came out and they have been asking if I can figure out this.
Thank you very much for any assistance.
Click to expand...
Click to collapse
Check the bottom of the tablet near the port normally it says there or check and see if you have 3g setting if you do then 3g from if not ur wifi only
A.R.H.D. 3.6 ICS Custom KingBeatz Audio

MrWiz1969 said:
So here I am wanting to break the installed version of ICS on my tablet... I followed the general guidelines on how to root and install the new OS (Revolution). I get myself to this point where I have the zip file on my MSD card and I go to the Power up and - volume to enter into the set up and I have 2 options, one is to boot from the current version I believe that it is a linux version) and the second is the ASUS Recovery image.
I think that I have the one that I can not be changed, is this true? Am I doing something wrong (should I have the TF101 attached by USB to the computer while I am doing this)? Is it possible to change the OS by expanding the zip file into the respective folders and attempt a reboot or will this process create a brick? I am interested in playing with the Ubuntu OS on my tablet too, just to get some experience, I am the computer guy in my area and I have a lot of people that I have talked into the TF101 since it came out and they have been asking if I can figure out this.
Thank you very much for any assistance.
Click to expand...
Click to collapse
You need to root and flash a custom recovery before you can flash a custom ROM
Once you have done that, you can then do what you just did, only this time you will enter a recovery capable of flashing custom ROMs, the stock ASUS Recovery can not
Use this to root and flash recovery - this can flash both SBK1 & 2 version of the TF101 so no need to worry about that
http://forum.xda-developers.com/showthread.php?t=1688012
Then follow the ROMs instructions to flash inside of recovery

Also look at the serial number of your TF101, Does it start with B60 or lower (sbkv1) or b70 or higher or a c? (Sbkv2).
Is it 3G? (NvFlash won't work Sbkv3/???)
Is it a slider? (Also won't work)
Afaik it's only those 3 variants for the TF101
You can also use my PERI tool for an easy recovery install, then place the Rom zipfile you want to install on the sdcard and use the new recovery to flash it.
Dl peri (Link in my signature) then run and plug in tablet, will install recovery, then place rom zip and flash in recovery... Easy peasy.

Okay, i already rooted my tablet so i am that far, I am going to create a custom recovery now (I didn't know that, so thank you). My tablet starts with b70 so it is one of those crossover ones. I am not famillar enough with Perl to be effective with it but if all else fails I will follow your instructions and thank you, too (if i need help with that can I PM you?
I had to work the past couple of days and i have off tomorrow so I will be attempting it Wednesday and I will keep you all posted.
Now any suggestions on which OS I should start with? I was thinking about Revolution, however I am a little partial to Ubuntu since I have it a my second OS on my laptop.
thanks again for your help, again.

Hey Everyone, it took a couple of days but I finally got it to work... I used the One-Touch program for windows and it was a piece of cake. I actually had it up and running a few weeks ago and I have been running Revolution. I need to back up this edition and I am going to try out Tubuntu next week just to get some experience with the different OS's.
thanks again for your help.
Dale Freed
Sent from my Transformer TF101 using xda app-developers app

Need some quick help

So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?

Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium

Any ideas?
Sent from my LG-LS970 using xda premium

Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.

No one can help?
Sent from my LG-LS970 using xda premium

Well that sucks...
Sent from my LG-LS970 using xda premium

Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.

I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.

I'd like to install a Jelly Bean Mod please

Hello again,
I would like to install the least buggy Jelly Bean ROM onto my ASUS Transformer Pad TF300T. I have never rooted my Tablet before and I am on the latest OTA update by ASUS
Android Version 4.2.1
Build JOP40D.WW_epad-10.6.1.27.5-20130902
I very much would appreciate some hand holding on this whole process. I have signed up to the CyanogenMod website but as yet not had any replies.
I don't really know what ROM to go for as its a minefield, but I would like the most stable Jelly Bean version. Not too keen on moving over to Kit Kat yet.
I have never done this before and I have quite a bit of trepidation about the whole process but as it is, my official ASUS Jelly Bean operating system is laggy and the battery drain is exceptionally noticeable. The tablet can drain empty on Stand By within a couple of days. I have tried all the tricks to extend battery life, including charging Tablet and battery spereately, Cold Boots and Fresh installs but nothing helps.
Cheers

the lemming said:
I don't really know what ROM to go for as its a minefield, but I would like the most stable Jelly Bean version. Not too keen on moving over to Kit Kat yet.
Click to expand...
Click to collapse
If you ask 5 people about this you will get at least 10 opinions...
I choose not to vote on that part of your question.
I have never done this before and I have quite a bit of trepidation about the whole process
Click to expand...
Click to collapse
The most important point is to select the right recovery version for your bootloader/ROM. As you are going to install a 4.2 ROM, I suggest TWRP 2.5.0.0-42. Not the latest, but proven and stable. Make sure to pick the -42 version matching your bootloader. The next point is: don't use the wipe data option on the bootloader screen, but use the wipe options in recovery instead.
If you follow these two points, you avoid most of the issues that get reported over and over again.
Sent from my TF300T using Tapatalk

f69m said:
The most important point is to select the right recovery version for your bootloader/ROM. As you are going to install a 4.2 ROM, I suggest TWRP 2.5.0.0-42. Not the latest, but proven and stable. Make sure to pick the -42 version matching your bootloader. The next point is: don't use the wipe data option on the bootloader screen, but use the wipe options in recovery instead.
If you follow these two points, you avoid most of the issues that get reported over and over again.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Hello
Thank you for replying. I am very green at all this and I don't want to mess things up. You mention getting a matching boot loader. How do I check what bootloader I posses and where do I find the correct stuff?
I now next to nothing about this process other than bricking my Samsung Ace phone a year ago and I have not dabbled in this since then. I am willing to get my hands dirty but I want to know how to get out of trouble should I do something stupid, which will most definitely happen.
Are you able to post a link to a tutorial that will help me out?
Cheers

the lemming said:
Thank you for replying. I am very green at all this and I don't want to mess things up. You mention getting a matching boot loader. How do I check what bootloader I posses and where do I find the correct stuff?
Click to expand...
Click to collapse
You can see the version of your bootloader at the top left of the bootloader screen. It should match the last Asus stock ROM version you installed: 10.6.1.27.5 in your case. This is the latest bootloader available and should work fine with all up-to-date 4.2 ROMs. Read the first post carefully, it should mention, which bootloader versions are supported. No nee to update.
Note that flashing custom ROMs will not touch your existing bootloader.
I now next to nothing about this process other than bricking my Samsung Ace phone a year ago and I have not dabbled in this since then. I am willing to get my hands dirty but I want to know how to get out of trouble should I do something stupid, which will most definitely happen.
Click to expand...
Click to collapse
Have a look at nvflash flatline for your bootloader 4.2. It allows you to extract some files from your device. If you keep those safe, you are almost brick-safe, as you can then use nvflash to recover your tablet from most known issues.
http://forum.xda-developers.com/showthread.php?t=2545610
Are you able to post a link tersion o a tutorial that will help me out?
Click to expand...
Click to collapse
I am not aware of a guide specifically for flashing custom ROMs, but most ROMs should have good instructions in the first post. Anyhow, you can browse the stickies in the General forum. They have a lot of good information.
Sent from my TF300T using Tapatalk