Database Info

[Q] [HELP] How to back up stock rom (& upgrade) for UNKNOWN brand tablet

Hi guys.
I've recently bought a android tablet,
the brand was MBI and the model was i7
(which is a not known brand ... can't find much info about it).
In my quest of rooting it, I've lost the bundled disc (with Win32 driver). after reading up tons of articles. I've decided to download google's USB driver and edit the .inf, the the tablet's VID & PID info. Somehow I managed to get adb working.
And for rooting, I've tried .apk and none of them work, then I proceed to SuperOneClick and it hung. Lastly I've tried the Easy Rooting Kit by ZoomLord and ta-da, my device is rooted!
Then I attempt to back up the stock rom in case of anything. But Rom Manager kept restarting the device whenever I run 'Back up current ROM'. And when I try to flash the ClockWork Recovery Rom .. the only option was 'Nook Color' & version 3.2.0.1, even Rom Manager reported recovery rom flash successfully, but whenever I try to boot to recovery mode, CWR is not running... and default recovery image doesn't allow me to back up my rom either.
So, in short, I hopes any of you could help me out on following:
1) How do I backup stock rom? or get any recovery rom working?
2) After that, can I just flash to any custom rom? e.g., CM7 Gingerbread ROM? although my device isn't in their supported list?
any help will be appreciated, thanks.

Now I'm trying this fastboot,
somehow when I entered fastboot mode (hold Vol+ & power the device on).
"FastBoot" was showed on center of the screen,
but whenever I issue # fastboot devices
the device will reboot itself ....
any idea? I was trying to flash recovery image via fastboot here

hello
did you manage to root your phone as I too got this tablets thanks

I have a same problem too.. can't use cwm after rooting. Now my mbi i7 tablet can't be used anymore. It just show blank screen after boot up. I can't revert it back to factory setting because the rom is corrupted & the update.zip file is missing. Can anybody upload the update.zip for mbi i7 tablet please.. - sorry 4 my bad english..
Sent from my GT-N8000 using xda app-developers app

[Q] TF101G stuck on boot,cannot access recovery. Any way to fix via adb maybe?

Flashed latest stock firmware 9.2.2.6 ww
Rooted using 1-Click Transformer Root http://forum.xda-developers.com/showthread.php?t=1689193
Flashed cwm from rom manager with no errors or smth.
Then decided to restore to factory defaults the usual way, through settings.
Now I can't boot the usual way (continous asus ring) & can't boot to recovery - green android robot with blue sphere rotating.
Still adb sees the device in recovery mode & I can push files, but can't do anything because can't flash these files
Is there a way to flash recovery without fastboot or flash a rom?

First, ROM Manager does not work with recovery installation on the Asus tablets. There is a warning in one of the forums here about it.
I would use PERI to push a new working recovery via ADB. Then push your ROM to the internal memory and flash it.
http://forum.xda-developers.com/showthread.php?t=1681155

frederuco said:
First, ROM Manager does not work with recovery installation on the Asus tablets. There is a warning in one of the forums here about it.
I would use PERI to push a new working recovery via ADB. Then push your ROM to the internal memory and flash it.
http://forum.xda-developers.com/showthread.php?t=1681155
Click to expand...
Click to collapse
Used OneclickrecoveryV0.4.
Now I cannot get access to adb: Volume Down + Power = Booting recovery kernel image
Also usual boot doesn't progress to Asus rotating ring, only Eee Pad logo.
Is there any way out of this "booting recovery kernel image"?

I left it turned off on a charger for several hours & decided to take a look once again before putting it into the box. Suddenly it just turned on & booted normally, wow!! )

Hey folks,
I'm currently facing the same problem.
I tried to root with 1-Click Transformer Root Tool v1.1. I received an error stating that busybox failed to install, also SuperSU wasn't installed. I started the 1-Click Tool again and it said that the Transformer is rooted. So I chose to install the CWM recovery but the script stated that the device was offline. That happened a couple of times, so I decided to install recovery via GooManager, which also failed ("no recovery was found for your device") and finally tried to flash twrp recovery using the terminal emulator - which worked - and rebooted the pad.
Since this reboot, it is not possible to boot the OS normally. It always gets stuck on the EEE pad splash screen, as cordlesspass describes. It's not possible to boot into recovery. I tried to fix this problem with PERI's tool which pushed and flashed the new recovery, but no change.
The only way to boot the OS is a cold boot. This works and the device behaves normally. I also tried to let it charge a couple of hours and then boot again, but no change. It still gets stuck.
I'm using no custom rom, only the latest stock fw.
Do you have any idea how to fix this problem?

AW: [Q] TF101G stuck on boot,cannot access recovery. Any way to fix via adb maybe?
So, for all those who have the same problem as I had, I found a solution and its a pretty easy one!
In my case, it seemed to be a permission problem concerning /dev/block/mmcblk0p3. So, I went through different threads and found a suitable solution here:
forum.xda-developers.com/showthread.php?t=1530337&page=20.
All you have to do is to enter terminal emulator on your device (or use adb alternatively) and enter:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
You should see the asus eee pad screen with a blue progression bar and then it should boot normally. Thanks to partio for this hint! :thumbup:
Sent from my Transformer TF101G using xda app-developers app

Device stuck in bootloop?

Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!

You cant't wipe data from bootloader menu, If you do that, you will get unrecoverable brick.

Sorry I believe I mislead you -> I wiped data from within CWM.
Anyway, I used this thread:
http://forum.xda-developers.com/showthread.php?t=1757077
I went back to stock and I think i'll stay there for a little while longer, this process made me nervous (I've rooted my thunderbolt, droid DNA, galaxy tab 2 7" and my friends phones) so anyway I believe I installed the wrong CWM and that caused errors trying to install a JB rom on a ICS CWM... If you have any insight let me know...

undergfx said:
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
Click to expand...
Click to collapse
My suggestion is to flash the latest stock JB blob.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Once you get it sorted then flash the latest twrp for jb.

Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Edit:
Ah didn't see your post. I did what you recommended, and actually, while my device said it was on 4.1.1 JB, when I hold pwr/vol down I see a completely different menu now than last time, so I wonder if perhaps my OTA didn't correctly load everything from the firmware update hmm...

undergfx said:
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Click to expand...
Click to collapse
The same way you flashed cwm.
Windows? Start - in search type cmd - press enter
In the cmd window cd to the directory with fastboot.
Hook cable between tablet and usb port on computer.
On tablet hold power and volume down till you see the bootloader menu.
Down volume till you are at the usb symbol - then volume up.
This should put you into fastboot mode - use the commands above.
Wait till the first command completes before you give the second command.
[INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc. You will find the stock firmware here as well as most other needs.
You will have to unzip to get the blob which you should place in the directory with fastboot.

Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.

undergfx said:
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
Click to expand...
Click to collapse
You're welcome.
Good Luck!

[Q] tf300t

Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!

Stravor said:
Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(

noahvt said:
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(
Click to expand...
Click to collapse
"Bricked" seems to be oftenly abused around here. Having ADB access and being able to boot into CWM, isn't there anything I can do to enable fastboot, force a bootloader downgrade or something?
Thanks!

This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app

noahvt said:
This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!

Stravor said:
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!
Click to expand...
Click to collapse
"ricked" may be abused, but I don't understand your situation very well, much less how you extricated yourself from it. If you're in a boot loop, you cannot complete the booting process (much like a tab with bootloader, recovery, but no OS installed). Without it, you have no access to ADB. Which in turn doesn't allow you to issue ADB commands. If additionally, you have no access to fastboot because volume down+power, and/or reset+volume down, does nothing (bootloader with icons absent), you cannot issue fastboot commands. Without the two, and the uselessness of APX mode, I'm not sure why that's not characteristic of a soft brick.
I have a mainboard that shows nothing but the initial Asus logo (not the one with boot animation, i.e., spinning dots) and "the device is unlocked." If I use either fastboot or ADB from PC, it returns with "waiting for device..." You were in the same boat, were you not? Looks like part of the firmware is still there (I assume if you replace the nand with a brand new, blank one, nothing would show up on display) , but the bootloader is messed up. If you'd succeeded in resurrecting your tab, then how do I rectify it, if you care to enlighten? Thank you in advance.

No recovery image working (soft-brick?)

I've played too much with my tablet and I made a damage: no recovery image
Current situation:
-Device is unlocked
-Bootloader is 1.00e released by ww_epad-10.6.1.14.10-20130801 a03
-Fastboot is working
-Installed and working ROM: ASUS stock JB 10.6.1.14.10 not rooted
I have tried with transformer toolkit to flash recovery but hangs during flash and no blue bar on the tablet.
I have tried with fastboot and it says OK and full blue bar appears on the tablet, but if I try to reboot and access recovery it stays stuck on "booting recovery kernel image"
Fastboot commands I used:
fastboot devices (connection ok)
fastboot erase recovery (ok)
fastboot -i 0x0B05 flash recovery twrp.blob (ok and blue bar)
fastboot reboot
I have tried many twrp versions from 2.5.0.0 to 2.8.6.0 but none works. I even tried CWM, same issue.
I have no more ideas how to recover this situation. can you help me?
Thanks in advance!

OK, self-solved, somewhat.
Managed to root Android with Kingo Root.
Installed app Rashr - http://forum.xda-developers.com/showthread.php?t=2334554 (before this tried both TWRP Manager and Flashify but they did not work and I read it's better to stay away from ROM Manager on ASUS tablets).
Managed to install CWM Recovery from the app.
Now, at least I have a recovery.
Probably I will find a way to go back to TWRP (hope so).

I would suggest you read berndb's guide in general and stop flashing random stuff onto your tablet.
It's only a matter of time before you do brick it.
Start with learning how to use fastboot and adb and getting your windows drivers up to date. Search for my post in the dev section for ones that work well.

Believe me, I'm not a newbie and I read tons of posts about this tablet including the guides you suggested.
Probably it will end as you predicted, but if this tablet would be at least "decent" I would have left it untouched with its stock rom.
But the price was very high and Asus abandoned its development after last crappy JB ROM, so we are all here hoping for a miracle ROM to make it work like it should.
Hopefully at the end of the year I will be in a position to buy a new tablet and certainly it won't be an ASUS.
Thanks anyway for your encouragement.
P.S.: In the end I left CWM as recovery because it was recommended for the ROM I chose (Techfusion+ V4 + Grimlock Kernel). Tablet fully working now and I have to say this is the best ROM I tested so far.
I think I will keep it until tablet's end of life.