Database Users

[Q] Asus Transformer, not looking good for me..

Hi all, I think i am in a bad place right now. I followed the steps to root my device from here " http://forum.xda-developers.com/showthread.php?t=1035197 " After getting to the stage where i do the Reboot of the device (Step 12) it reboots to the EEE Pad Asus Screen and it never left that screen.. I have tried the E101 files to get it to boot again..
If i power off the device it will just automatically turn back on.
If i power off and then press VOL_DN and Power i get to the press VOL_UP within 5 seconds to enter RCK. It then shows Booting recover kernel image and goes no further. i have downloaded sever firmware files, etc and renamed them as was told in other threads to EP101_SDUPDATE.ZIP and it still just hangs at that screen.
If i power off and then do the VOL_DN and Power and then ignore the VOL_UP part i go to the next screen that has the Pulsing WIPE Data Icon with Press VOL_UP to execute or VOL_DN to Cancel.
If i do the wipe data i get the following response wiping user data please wait a few mins. and then after a short pause of that a response in red returns the following information:
MAGIC Value Mismatch: shows garbled characters after the colon
Critical Failure: Unable to start Kernel
Unrecoverable bootloader error (0x00000002)
If i don't do the wipe data and get the skipping wipe and cold booting linux the exact same error above appears..
I have been search now for about 6 or 7 hours on the net and am at wits end to get this working. If only NVFlash worked.. I am thinking this might be my only fix...
Any help would be extremely appreciated. Sad thing is i told myself to leave well enough alone and not to frig with this. LOL. Damed teckies we can't leave things the way they are and just use them we have to mess around with them. Be no fun if we didn't..
Thanks for any input anyone may have..
Craig

I would go on the irc and see if anyone can help u there. Freenode #asus-transformer
Sent from my Samsung Epic

Thanks they helped me out, they found where i was going wrong in the walkthrough and got me booting up..

New kernel version; unrootable?

i replaced my GT 10.1 (wifi version) with a new one, since the old one had that rainbow screen problem.
anyway, i'm trying to root the new one, following this guide
http://www.youtube.com/watch?v=0eAQzxwEVjY
and i _CANNOT_ boot into recovery. period. the android symbol DOES NOT pop up at all.
i installed the samsung usb drivers supplied with the video, and tried booting into recovery with usb debugging enabled AND disabled, same problem both times!
even tried rebooting with the usb cable disconnected, as if that would help
in every case, i hold volume down and the power button, the tablet begins booting, is displays the "galaxy tab 10.1" boot image. Normally the android recovery logo would flash by for a split second after doing this, but nope, goes straight to black
what the crap is going on?
Kernel version;
2.6.36.3
[email protected] #1
build number;
HMJ37.UEKMB P7510UEKMB

Interesting your kernel appears to be older I have sep-63 #1

nandihno said:
Interesting your kernel appears to be older I have sep-63 #1
Click to expand...
Click to collapse
might that be the cause of these problems? i'm not sure if the recovery menu wasn't in there before the newest kernel version
edit: oh, wow, i forgot to check for a software update as soon as i got the new tablet, it's loading up a new one
edit2: there we go, i'm getting the recovery android image popping up
now to spend twenty minutes trying to time it so it activates, since it goes by at 200 miles an hour

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

Osbor said:
might that be the cause of these problems? i'm not sure if the recovery menu wasn't in there before the newest kernel version
edit: oh, wow, i forgot to check for a software update as soon as i got the new tablet, it's loading up a new one
edit2: there we go, i'm getting the recovery android image popping up
now to spend twenty minutes trying to time it so it activates, since it goes by at 200 miles an hour
Click to expand...
Click to collapse
Yes, that happened to me. Continue to hold down the vol - and the power button, even after the recovery screen flashes by. The GTab will reboot again and the recovery screen will flash by again, but this time after you release the buttons, the recovery mode will display. At least, it did on my GTab. Give it a try...

Osbor said:
in every case, i hold volume down and the power button, the tablet begins booting, is displays the "galaxy tab 10.1" boot image. Normally the android recovery logo would flash by for a split second after doing this, but nope, goes straight to black
Click to expand...
Click to collapse
Hold VOL- and Power until the Tab powers up, but let go of Power just after you see the logo.
Holding down Power for about 5 seconds for any reason will cause the Tab to reboot.

Model: GT-P7510MA (wifi-only, no sd card)
Build HMJ37.UEKME
Android 3.1
Kernel 2.6.36.3 ([email protected] #1)
Instructions are clear and root was successful. Hooray!
I was 'tarding out hard here and could not has root. bran hurting
I tried this about a month ago and gave up after spending 3 or 4 hours, breaking it several times and needing factory resets or stock flashes to recover. Something about trying to push an unsigned bootloader and it was saving me from myself.
SuperOneClick does not work on these. In fact, most of the instructions on xda do not work or mention in bold red scary text about how you must not use this mod. It is hard to tell what is still valid and what is headed for the rubbish heap.

[Q] ms2 - bootloop - last chance?

hi there...
just installed CM7 this weekend. worked fine for 2 days
After restarting the ms2, it got stuck in a bootloop.
I can flash a sbf with rsd lite from, finishes OK, but when it says, rebooting, well...
it still stuck in a bootloop.
In recovery mode, i can do a cache wipe and factory reset. But there is a error message at the bottom, telling:
E: Can't open /cache/recovery/command
E: Can't open /cache/recovery/caller
Could I successfully flash with RSDlite from Linux? which version?
Is there a way to restore the ms2 from dev console?
Thanks a lot

Do you test to Wipe Data with stock moto recovery ?
Here step 7 to 11
I think your request must be on "General" section

I suspected it might be related the CyanogenMod intstall. But move to "general" if necessary
Have done steps 7 - 11
but still ms2 bootloops
OMG - if broke it - my wife kills me

I hope your wife don't kill you LOL
See this thread and particulary this with r2beta0 tips:
EVEALEX62 said:
I have do this (all step 1 to 11 because "boot up the phone manually" ) with the sbf 2.2.2 officiel but modify whith this post :
r2beta0 said:
I don't know if this is going to help, but you could try that anyway:
- Download MotoAndroidDepacker (utility to unpack/repack SBF's)
- Choose one stock SBF (2.2 FR for example)
- Open and unpack it with the utility
- Rename CG66.smg to CG37.smg (you are going to use preinstall image as data image, both are ext3, but has different sizes. Don't know if it's going to work).
- Use utility to open folder with unpacked images and repack it
- Put phone in bootloader mode and flash the repacked SBF (rebuilt/firmware.sbf)
- Post results here
Click to expand...
Click to collapse
Click to expand...
Click to collapse

I did exactly the same, as in the other thread.
And thank god, my ms2 booted up
So everything seems fine for now und no one should get killed
Many Thanks!

Nice for you

Moved to proper forum.

Hi all, Emiliano from Italy. I firstly wanted to thank you all for your support.
Even being my first post here, I've been following you since some time.
My problem looks exactly the same: bootloop... bootloop... bootloop.
No matter how many I tried flashing back the original ROM for my M2 (SBF file always worked before!!! so I'm sure is the correct one for my smartphone).
I tried also the procedure with depacking described above with no progresses.
Anyway I already had noticed that after renaming cg66 to cg37, depacker wasn't able to see it in the list of cgs before repacking, so that final fbs was 300MB less.
Something wrong I made? (tried on 2 pcs with Vista Home and Business)
Unluckily I cannot even try to wipe data because I cannot enter in recovery mode (On + X -> Android robot with mark -> but nothing happens after pressing magnifying lens or any other key).
Could someone, please, help me before using my bricked M2 for building a new house?

Devilsball said:
Hi all, Emiliano from Italy. I firstly wanted to thank you all for your support.
Even being my first post here, I've been following you since some time.
My problem looks exactly the same: bootloop... bootloop... bootloop.
No matter how many I tried flashing back the original ROM for my M2 (SBF file always worked before!!! so I'm sure is the correct one for my smartphone).
I tried also the procedure with depacking described above with no progresses.
Anyway I already had noticed that after renaming cg66 to cg37, depacker wasn't able to see it in the list of cgs before repacking, so that final fbs was 300MB less.
Something wrong I made? (tried on 2 pcs with Vista Home and Business)
Unluckily I cannot even try to wipe data because I cannot enter in recovery mode (On + X -> Android robot with mark -> but nothing happens after pressing magnifying lens or any other key).
Could someone, please, help me before using my bricked M2 for building a new house?
Click to expand...
Click to collapse
Hi
Have the same problem here since 6 months now,
Just to see if it s the same thing as me, try this please:
In my case i can t acces recovery, only way is to hold X and plug the phone to the wall, did not resolve nthing for me, but maybe you re luckier...
post results...
C ya

Hi Amir4Life,
thanks for reply and for your suggestion.
Unluckily I cannot access recovery mode.
All I get when pressing X is the green robot with Exclamation mark, but no matter which key I press after, it gets stuck at that point (so that I'm bound to take away battery to turn smartphone off) and cannot access or see any menu to operate wipe.
Tried also reflashing other roms through rds lite (bootloader works efficiently) or through ubuntu live cd "sbf_flash system", but the only fsb that always worked for me turns out to be a bootloop when rebooting.
Unluckily nothing seems to help me in this situation, so far.
It's still a bootlpop and no access to recovery mode.
Thanks anyway for your help and happy and special new year to you all!

At the 'exclamation sign + green android guy' screen, you have to press 'vol up + vol down' together.
Now you will get the options like 'wipe data' etc. etc. Scroll through options using vol up or vol down and select using power button.

sahilarora911 said:
At the 'exclamation sign + green android guy' screen, you have to press 'vol up + vol down' together.
Now you will get the options like 'wipe data' etc. etc. Scroll through options using vol up or vol down and select using power button.
Click to expand...
Click to collapse
Thanks Sahilarora,
If I had read you before I would have saved a lot of time trying all possibile combinations of keys on the keboards (since magnifying glasses didn't work)!!
Then just by chance I discovered myself volume up + down while pressing chaotically all buttons and it worked to my best suprise, showing me finally the belated list of options, together with blessed wipe data factory
Since yesterday evening my Milestone 2 is wonderfully working again, as fresh as a daisy!
Thank you so much for your contribution, hoping it could help also Amir4Life and oll pthers in a similar situation.
Happy new year (started in the best way).

Glad for you, I was about to tell to do what sahilarora911 told ya,
I expect i m the only one who stays with brick'd phone... my luck.
C ya

Amir4Life said:
Glad for you, I was about to tell to do what sahilarora911 told ya,
I expect i m the only one who stays with brick'd phone... my luck.
C ya
Click to expand...
Click to collapse
Could explain in details which is your problem, and which methods have you already tried to solve it?
If not me, maybe someone else could help you.

Hi Emiliano! It seems to be that we share the same problem. Did you found a fix to it? Thanks!

Devilsball said:
Hi Amir4Life,
thanks for reply and for your suggestion.
Unluckily I cannot access recovery mode.
All I get when pressing X is the green robot with Exclamation mark, but no matter which key I press after, it gets stuck at that point (so that I'm bound to take away battery to turn smartphone off) and cannot access or see any menu to operate wipe.
Tried also reflashing other roms through rds lite (bootloader works efficiently) or through ubuntu live cd "sbf_flash system", but the only fsb that always worked for me turns out to be a bootloop when rebooting.
Unluckily nothing seems to help me in this situation, so far.
It's still a bootlpop and no access to recovery mode.
Thanks anyway for your help and happy and special new year to you all!
Click to expand...
Click to collapse
thank you ...................

[Q] A500 Boot Issues...need assistance

I've searched and found a few similar (not identical) problems that people were having, and tried some of the solutions, and none have worked.
I'm trying to fix this stock Acer A500 for a friend. It will boot up part way, goes past the acer screen and android screen, but then stops at a black screen with 'android system' in the upper left corner, the home and back buttons in the bottom left, and the time, signal, and battery life logos in the bottom right. Then there's the Power Off thing in the center of the screen, and it says shutting down but it never shuts down.
I boot into the stock recovery mode, and it says in the upper left on the acer screen:
erasing cache before SD update
SD update cmd: recovery
--update_package=sdcard:update.zip
booting recovery kernel image
then it shows the android with the turning gears, then goes straight to the android with the warning symbol.
Since I can't get into the OS, i have no idea which version or specific model this is, but i downloaded a few different honeycomb update.zips, and put those on the SD card, and when i tried booting with those, the loading bar pops up under the android logo, and it goes to about 1/3 of completion before switching back to the warning symbol.
I tried downloading what im pretty sure was a full version of jellybean for this tablet, and it went straight to the warning symbol, no loading bar. same when i tried renaming the file update.zip >.>
im clearly very new to all this, but i'd really like to get this thing working.
is there a way to do a factory reset without booting all the way into the OS?
im not sure because it seems like the only file its looking for in recovery mode is update.zip.
if anyone has any bright ideas, id appreciate the help.
Also, not sure if this is relevant, but when i boot it normally, and it goes to the 'shutting down' screen, the battery level indicator says its almost dead, but i can leave it plugged in for hours and nothing changes at all.
EDIT: Also, it won't even boot if the power cable is not connected.

Similar issue hope there is a solution
I have a similar problem. Tablet was working fine, sitting on docking station. Returned to it the next day and when I went to wake it, it would not wake. Rebooted it but will not reboot. Sits on the ANDROID screen after the ASUS title screen indefinitely. If I try and boot into recovery it fails at "update.zip" and I see the broken Android image laying there.
Is there a means to restore it from PC via the usb cable and can someone please post a very noob friendly walk through step-by-step?
Greatly appreciate any positive advice!

Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD

zardoz99 said:
Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
So, dead chip? So soon? Nice.

NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
Yep.. 14 months old in my case. Contacted Acer and said "what about a fix?" They said, "no chance unless you cross our palms with lots of silver."
So, bought a Samsung Note 10.1 instead. Acer can "stuff it". I won't be buying a tablet from them again. Considering that I bought their "flagship" product of the A501 with the 64GB memory, this is truly unacceptable.
I was incredibly careful with it and certainly never did anything to void the warranty. But, you only get 12 months and then it's over.

NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?

skurtov said:
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?
Click to expand...
Click to collapse
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!

NoOneSpecific said:
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD

skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
I'll have him PM you when he is able.
Thanks!

skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!

coluwyvurne said:
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!
Click to expand...
Click to collapse
You are quite right sir, however the button combination I am most familiar with is holding the power and the reset button (the one you have to stick the paper clip in) when you first start it up. It should then either say APX mode on the screen or be blank, either way the computer will identify it as a APX device and automatically install the drivers.
Going into APX MODE manualy
You enter APX mode by holding down the Reset button(with paper clip). Do not release it. Hold down power for 3 secs and then release it. After another second, release the reset button.
Your Windows PC should then detect your device and install the APX driver. You should then have an APX USB device installed. If you do not have an APX USB device listed in your system tray, you cannot proceed.
The screen of your tablet is black.
Quoted from Civato
Click to expand...
Click to collapse
The next course of action is to get the SBK, from what it sounds like the tablet didn't write a partition properly and that's why it's not booting. So what you can do is wipe out the partitions and install a custom bootloader and recovery. Not only does it fix things but it also opens up his world to custom roms . Okay, back to the matter at hand, I don't know if he has his SBK or not, and if he does skip the step to find it and just run babsector below. If not then follow the next step.
You'll have to pull the UID from the tablet using this method described here:
http://git.pappkartong.se/?p=a500/apxuid.git;a=snapshot;h=HEAD;sf=tgz
There's a readme
After getting the UID and calculating your SBK you'll just go to the next step.
All credit goes to user eppeP.
Click to expand...
Click to collapse
Run this file hosted here:
http://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
And this file basically rewrites and formats the partitions out installs a custom bootloader and recovery
Credit goes to Danny2 for finding this and posting it.
Click to expand...
Click to collapse
Once this is done, pick a new rom. I prefer the Civato ones, load it on a SD, boot to recovery, erase dalvik cache, cache, do a factory reset wipe (from the recovery menu!), then wipe system, flash the rom and go on your merry way

Many thanks for the reply.
As per your instructions, I have booted the tablet into APX mode. However, as I do not know the UID of the device, I've had to try to run the utilities to create a driver for the device and then pull UID from the tablet...
I am able to create the driver for the device and install it with driver signing off in Windows, but I can't figure out how to run the script to get the UID. I notice the file in the package you directed me to contains an .SLN file, which would indicate it is a programming solution file. I have Visual Studio on my system but it cannot open this particular .SLN file.
How would I run what's in the package to pull out the UID of the tablet?
Any help getting past this hurdle would be much appreciated!

[Q] Cannot get CyanogenMod v0.9 to install - can't get CWM to reboot into recovery

ThinkPad Tablet A400
Android v. 4.0.3
Have an app that needs to run on Android 4.1 and quickly found out this 2 year old device was pretty much left unsupported since about 3 months after I bought it in May of 2012. So, I located the links to xda-developers and dove into the install process.
Got the device to Root following install directions etc.
Cannot get the device to reboot into recovery mode from ROM Manager nor via ROM Installer.
Tried installing the CyanogenMod v0.9 anyway from inside either aforementioned utility (from the .zip file), just reboots back to the normal state.
I'd pay to download & install Android 4.1 on this device, seriously...just lost 6 hours of time attempting to do this ROM upgrade.
any suggestions?

First thing that comes to mind is that you should use the volume up button multi-press on device power-up to get to Recovery Mode.

pwstein said:
First thing that comes to mind is that you should use the volume up button multi-press on device power-up to get to Recovery Mode.
Click to expand...
Click to collapse
I've tried various combinations of that Vol button....still stubbornly refuses to go to CWM.
Now, I am running Android 4.0.3..perhaps that is the issue, ie. perhaps the CWM image file was intended to be used on TPTs running Android 3.x.
It'd be nice to go to a site and buy a $50 OS load....

Well....wonders never cease. I happened across a post talking about the TECHNIQUE to reboot the TPT into CWM...so, sure enough...I got the puppy into CWM.
HERE 'tis for the rest of us nuves out there:
Entering/Booting CWM Recovery on the Thinkpad Tablet
Shut down your Thinkpad Tablet
Press the power button until the Tablet vibrates
Keep pressing and releasing the volume up button until you see Booting Recovery Kernel Image in the upper left corner. It's all about timing of when the volume up button is pressed. That's why it's a good idea to just keep on pressing and releasing the button until the message appears.

Well i continued on with the Jelly Bean load from the xda-developers...and after reboot to ver 0.92 the tpt seemed to freeze on the os boot screen.
So, i fell back to the 4.0.3 os and will read-up on what can freeze the reboot into 4.1 android.
CWM is a cool program..gotta say it.

Can't get it to install CWM
Tried numerous times but now I have lost my original recovery and it just loops,
Changed permissions but won't go and when I am in the recovery boot after pushing the volume button it just reboots as there is nothing there suggestions?

Honestly, the best thing you could do is get something newer/better supported. I hate saying that, because I bought the 64gb version right around the same time you did. The tablet had so much potential with the pen, USB, sd slot, and even pci-e, but it suffered from non-existant Lenovo support, and very little dev support. Koshu's work on it was amazing, but without trim I feel like I have to constantly wipe and start fresh to do anything with it. Clearing dalvik from time to time helps, but not as much.