Database Info

[Q] Booting into CWM after installing Oma JB v1.2.2 on Cube U9GT2

Hi all,
I have loaded the Oma JB v1.2.2 ROM onto my Cube U9GT2, and want to boot into CWM recovery mode so I can apply the required fix from the zipped file on my SD.
The ROM loaded on fine, and checked out ok, but the problem I have is not being able to load CWM after the update.
I have tried volume down on powering up, but all I get is a black screen (screen illuminated, but all black). From reading I thought all I needed to do was hold volume down while powering on, wait for some text to appear, then switch to volume up till loaded. Also, if I try to power up without using volume down I get the same illuminated but black screen, no booting up.
If I flash the Evolution ROM back on it works again no problem, but I would like to try the Oma JB v1.2.2.
Am I missing something obvious?
Any advice would be greatly appreciated.
Cheers

Hey,
Thanks for including all the necessary details.
To me it just seems like some sort of bug. I would recommend ditching the ROM itself. Obviously, it cannot access the CWM files but as to fixing it, I wouldn't know.
I can't say any more really as I have never experienced this.
Sorry about that.

Hello,
Funny !!! I have exactly the opposite problem ! I have also a window N90 tablet (U9GT2 clone). I have tried to install Oma JB v1.2.2 ROM onto my device. For me, I can't load android, I can only boot and the device crashes, on a screen (remember me windows). Impossible to turn on the device but I can access the CWM recovery mode and can apply the zip fix ! To enter the recovery mode I push volume down on powering on. The device is no more recognized by XP and RKandroid can not find the tablet !!!
Do you know if it is possible to install a new Rom from the CWM recovery mode ?
Thanks a lot your help
ck

spicysi said:
Hi all,
I have loaded the Oma JB v1.2.2 ROM onto my Cube U9GT2, and want to boot into CWM recovery mode so I can apply the required fix from the zipped file on my SD.
The ROM loaded on fine, and checked out ok, but the problem I have is not being able to load CWM after the update.
I have tried volume down on powering up, but all I get is a black screen (screen illuminated, but all black). From reading I thought all I needed to do was hold volume down while powering on, wait for some text to appear, then switch to volume up till loaded. Also, if I try to power up without using volume down I get the same illuminated but black screen, no booting up.
If I flash the Evolution ROM back on it works again no problem, but I would like to try the Oma JB v1.2.2.
Am I missing something obvious?
Any advice would be greatly appreciated.
Cheers
Click to expand...
Click to collapse
You should press both Volume up & Volume down button same time to enter CWM. That's how it works in my U9GT2 with Oma JB 1.2.1
---------- Post added at 07:48 PM ---------- Previous post was at 07:40 PM ----------
ck32 said:
Hello,
Funny !!! I have exactly the opposite problem ! I have also a window N90 tablet (U9GT2 clone). I have tried to install Oma JB v1.2.2 ROM onto my device. For me, I can't load android, I can only boot and the device crashes, on a screen (remember me windows). Impossible to turn on the device but I can access the CWM recovery mode and can apply the zip fix ! To enter the recovery mode I push volume down on powering on. The device is no more recognized by XP and RKandroid can not find the tablet !!!
Do you know if it is possible to install a new Rom from the CWM recovery mode ?
Thanks a lot your help
ck
Click to expand...
Click to collapse
It's possible if you have backup of working ROM and can restore it, otherwise propably not.
---------- Post added at 07:52 PM ---------- Previous post was at 07:48 PM ----------
j0vi said:
You should press both Volume up & Volume down button same time to enter CWM. That's how it works in my U9GT2 with Oma JB 1.2.1
---------- Post added at 07:48 PM ---------- Previous post was at 07:40 PM ----------
It's possible if you have backup of working ROM and can restore it, otherwise propably not.
Click to expand...
Click to collapse
To get to flashing mode in Windows
1. Shutdown your U9GT2
2. Press Volume down
3. While keeping Volume down pressed plug in USB cable (U9GT2 display stays blank. Do not press Power button)
4. Run RKAndroidTool.exe as Administrator

j0vi said:
You should press both Volume up & Volume down button same time to enter CWM. That's how it works in my U9GT2 with Oma JB 1.2.1
I have the same problem, can't get it to boot neither CWM recovery.
Click to expand...
Click to collapse

Boot looping on the Eee Pad Screen

Hey guys,
So I looked tried to charge my tablet one day, and it decided to boot loop to the Eee pad screen and continue to do that. I tried to enter recovery and it then tried to restore a backup that I had, it said there was some kind of error and CWM wouldn't work after that. I tried doing a cold reboot but nothing worked. Also I tried EasyFlash and I don't think I did that right either. I was on CM 10 before this happened with Rogue Recovery. What are the steps that I need to take in order to get my tablet up and running again.
PS: I know that there are threads about bootlooping but none of them helped much.

I would love some help...:crying:

Try easy flasher again, it will work.. what problems you faced when u used easy flash?
Sent from my Transformer using xda app-developers app

udupa82 said:
Try easy flasher again, it will work.. what problems you faced when u used easy flash?
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
It seems like I can't get it into apx mode properly. I installed the drivers and when I plug it in it shows nvidia... under USB universal in device manager. Not sure what I am doing wrong.
Sent from my MB865 using Tapatalk

Hi.
I have had this problem for four times after trying to flash to a custom ROM, and now my tablet is perfectly functionable.
If you used EasyFlasher to get a custom ROM and now it's bootlooping OR if you tried to root your device and its bootlooping OR if you do not know what you have to do, then check the ways below:
====================
W1:
Power up the device. When it starts bootlooping, hold both Power + Volume DOWN buttons until it will say that you should press volume up or it will enter RCK mod. When that will appear, do nothing. Just let it enter RCK mod and it should wprk. If not, then do W2.
W2:
Look under your TF101 and see if the S/N starts with B60 or under or B90. Start EasyFlasher and select the FIRST button at launch if it is B60 or under or the second if you have B90. In the EasyFlasher's folder you will see a folder with a name like "update" or "puthere". Now go to Asus' TF101 page, to downloads (Link coming soon, until then try to find it) and select the latest (first you find) firmware.Do NOT use a custom rom or you will hard brick it! Download it to the folder I said above. DO NOT EXTRACT IT. Now, make sure your tablet is at least 50% charged so it can successfully flash the stock rom. Then, connect it to your PC and press the Power + Volume UP buttons on your tablet for like 10 seconds. There must be now a NVIDIA driver in your Device Manager. Go back to EasyFlasher and press "Flash/Unbrick/Root". If anything pops up, check carefully what it says. It will probably say to be sure it is in APX mode and if you want to cpntinue. Press yes or OK. A CMD box will appear, exxtracting the firmware you put in that folder. Let the PC and the tablet do it's work. Do not use the tablet while this happens or it may really becolme unusable forever. After it extracts, another CMD box will pop up, flashing the stock fw. If EasyFlasher will say something like "system.bin - 0kb" then the update will fail and your tablet will get HARD BRICKED. In this case, PM me and I will help you. Okay. Now, your TF101's screen should turn on and say "!!!UPDATE SUCCESSFULL!!!" for like three times, and all the CMD windows from your PC should dissapear. The EasyFlasher should now stop installing the fw. Hold your tablet's power button for 5-10 seconds and release. You should now be able to start your device without bootloops. If there still are bootloops, then, do the W1.
====================
I have had alot of experience in bricked tablets, and those ways should wor. For more infos or TeamViewer help, PM me.
I hope I helped,
Kevin.
Sent from my Transformer TF101 using xda app-developers app
---------- Post added at 04:23 PM ---------- Previous post was at 04:19 PM ----------
kindacrazyazn said:
It seems like I can't get it into apx mode properly. I installed the drivers and when I plug it in it shows nvidia... under USB universal in device manager. Not sure what I am doing wrong.
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
When it says to make sure that you are in APX mode, just hold Power + Vol UP buttons for 10 seconds then press ok. The drivers you have must show up as a NVIDIA driver in Device Manager when you hold that buttons. Do what I said in the previous post, it helped me four times lol.
Sent from my Transformer TF101 using xda app-developers app

[Q] What can I do? tf300t seems bricked, holding buttons doesn't help, no apx

Hi,
This is my first post. Been reading posts for awhile to make sure I'm doing the most I can on my own for my Galaxy S3 and my TF300 but I think I finally hit the wall.
Here's the si
Got a TF300T, unlocked it fine (using SDK and command line through all this) rooted to CWM with fastboot,that didn't work right so I flashed to TWRP, put on paranoid android that didn't take so decided to put back to stock to start fresh. Put it back to stock, unrooted. Looks like I used the wrong version firmware (some keys on my board weren't mapped right, press comma, get semi colon). So I checked and found the newer version firmware, was in the process of loading using command line, accidentally pressed enter while loading so it looks like it was doubling up and looks like it froze so I stopped it by holding on and Vol Down now it won't turn back on.
Now I know that's probably what's causing my problem. But now I get nothign on the screen, I've tried using the tips I've heard on here: reset hole, holding On and Vol Up to get into apx mode etc but nothing is working.
I've searched on the forums but I haven't found anything for my particular problem but maybe I'm not asking the right questions.
I'd really appreciate any help, spent too much on this to give up.
Thanks

Mine transformer tf300 can be turned on, but then it get's stuck on the bootscreen with the text bootloader unlocked. I can't turn it off normally, holding vol - & power button does nothing. To turn it of I need to let the battery run out or press the vol + button & reset hole.
I found a tutorial on youtube how to unbrick it ( I am not able to add the link because I am new).
The tutorials uses apx mode. Here is where my problems start. When I press the vol + button and connect my tablet to my laptop it does enter apx mode and it is shown in the device manager.
But I need to force install the driver acording to the tutorial but I don't know what driver I need to install. I've tried the drivers from the asus website and the driverd for adb. but nothing.
Can anyone tell me which driver I have to install? Because getting in to apx mode is the only way I can get any responce from my tablet. When connected I see apx device connected in the device manager, but nothing in my computer where my disks and removable disks show up.

"poorbil" i have the same issiue you have with the tf300.in my situation i succsesfully installed the APX drivers but i can't find a guide how to use it.maybe we can help eachother.here is my yahoo idky2006_18
Please send me the youtube link and i will send you the link with the drivers for APX.if you have teamviewer i can assist you if dont know how to do it.
Sorry for my bad english.
Sent from my GT-I9100 using xda premium
---------- Post added at 05:18 PM ---------- Previous post was at 05:05 PM ----------
oky2006_18
Sent from my GT-I9100 using xda premium

vio_87 said:
"poorbil" i have the same issiue you have with the tf300.in my situation i succsesfully installed the APX drivers but i can't find a guide how to use it.maybe we can help eachother.here is my yahoo idky2006_18
Please send me the youtube link and i will send you the link with the drivers for APX.if you have teamviewer i can assist you if dont know how to do it.
Sorry for my bad english.
Sent from my GT-I9100 using xda premium
---------- Post added at 05:18 PM ---------- Previous post was at 05:05 PM ----------
oky2006_18
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Like a Sir

[Q] Bricked?

Hi,
My Transformer TF101 would not start, it got stuck at the ASUS boot screen. So I thought that I would restore the device by flashing stock rom using EasyFlasher. But I ran into problem...
I put the device into APX mode and updated the driver from Universal Naked Driver 0.72.
Once I do "Flash Asus stock zip / Unbrick" from EasyFlasher 0.8.3 a command window appear (see attached picture) and after a while the text in the windows stops at
[+] Sending bootloader...
Sending file: 100 %
The screen of my transformer lights up and says the following:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 033c20c140e04117
I waited several hours in this state but nothing happens. If I unplug the transformer from my PC I am not able to reboot it, the only thing that seems to work is power button + volume up to start APX mode and then connect to the PC.
Does anybody have some idea what could be wrong? I am thankful for all suggestions.

Hi.
Happy new year ...
Suggestions
power button + volume Down, after volume up ---> to start RECOVERY mode ????
---------- Post added at 12:01 PM ---------- Previous post was at 11:56 AM ----------
then reinstalled a rom, or restore backup...

I got a new (to me) TF101 for my OH for Christmas - I seem to remember the serial number was not mentioned in EasyFlasher either - however cutting a long story short, EasyFlasher didn't work, but I googled and used PIRI and was rooted and booted in no time at all. Hope this helps you.

Hi,
Thanks for the suggestions. Unfortunately I cannot boot into recovery, nothing happens when I press volume down + power. Since I cannot start it I cannot use adb so I guess the only option is to flash recovery/stock rom in APX mode. But here is where I run into problem, nothings happens after the bootloader is sent to the device as I wrote earlier.

joooeeel said:
Hi,
Thanks for the suggestions. Unfortunately I cannot boot into recovery, nothing happens when I press volume down + power. Since I cannot start it I cannot use adb so I guess the only option is to flash recovery/stock rom in APX mode. But here is where I run into problem, nothings happens after the bootloader is sent to the device as I wrote earlier.
Click to expand...
Click to collapse
Since you can still use the APX mode you should be able to restore the stock firmware.
From my experience EasyFlash works like a charm. But it has no option to install the APX drivers. You also need to download the stock image from the Thread.
Did a restore to stock just a few days ago.
Looking at your command you did not tell wheelie to install any ROM after the bootloader.

Adb in recovery

Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8

Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.

Keithn said:
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Click to expand...
Click to collapse
Could you send me stock recovery so I can take a look inside the init.rc

Yeah, I'll do that today
Sent from my One M8

Keithn said:
Yeah, I'll do that today
Sent from my One M8
Click to expand...
Click to collapse
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc

Unjustified Dev said:
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Click to expand...
Click to collapse
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.

Keithn said:
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Click to expand...
Click to collapse
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working

Unjustified Dev said:
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Click to expand...
Click to collapse
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.

Keithn said:
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Click to expand...
Click to collapse
This is crazy does adb work in the recovery you compile from their git?

Unjustified Dev said:
This is crazy does adb work in the recovery you compile from their git?
Click to expand...
Click to collapse
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.

Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
Keithn said:
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Click to expand...
Click to collapse
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????

MRobbo80 said:
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
Click to expand...
Click to collapse
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.

Keithn said:
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Click to expand...
Click to collapse
My screen is black I can not see any options I am using the custom new cwm

Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet

Keithn said:
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Click to expand...
Click to collapse
sorry not sure how to boot in to fastboot?

MRobbo80 said:
sorry not sure how to boot in to fastboot?
Click to expand...
Click to collapse
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.

Keithn said:
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Click to expand...
Click to collapse
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really

MRobbo80 said:
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
Click to expand...
Click to collapse
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.

Keithn said:
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Click to expand...
Click to collapse
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
Click to expand...
Click to collapse
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.

MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
Click to expand...
Click to collapse
No problem good to hear :good: