[Q] Asus Transformer, not looking good for me.. - Eee Pad Transformer General

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..

Related

SOLVED : Managed the impossible - Bricked my Defy+ - PLEASE help !

Here are the facts:
1. My defy+ with red lens had this rom :Android 2.3.5 "Gingerbread" DEFY+ 4.5.1-134-DFP-125 - CEE LINK
2. took the stupid decision to flash this A.2.3.6-MIUI-XIUIv4.04-13.06-DEFY+/red-fixed'sbf from this thread http://forum.xda-developers.com/showthread.php?t=1691901
3. the phone did not boot, remained at the black screen with the white writings on it so i decided to flash the image that i had (read point 1)
4. flash went relatively ok but now my phone is stuck at the animated motorola boot logo
5. if i take the battery out and power it on with the volume down i encounter a triangle with a "!" in the middle next to an green android - the 3e menu is missing - can't do a thing
if i power the phone with volume up the bootloader says "Bootloader 09.10, Battery OK, OK to program, Connect USB, Data Cable"
6. tried the following with no luck:
- let it run the animated boot loop for 10-12 minutes - hoping that will come out of it
- flashed it several times
- tried this http://forum.xda-developers.com/showthread.php?t=1618718 and it's exactly how it;s acting mine and i quote: "If that doesn't happen,it will ask you to reboot manaully and your phone will be stuck in MOTO logo.
- Now remove your USB cable and remove battery. Hold power button and vol + button, you will get that screen.
- Now connect usb, now it result should say pass.
- Press the power button and start the phone. First boot will take some time (Min of 10 minutes or more). "
I am tired, upset and kinda desperate... i thought it will never brick and... surprise
yo did not break your phone... that's almost impossible...
did you tried to flash a defy+ sbf from here http://sbf.droid-developers.org/umts_jordanplus/list.php using rsd lite???
try that first and later came back with results
dude, this is the wrong area but as you are desperate.... did you try to find some post
that could help you with your problem?
i'm sure that somebody already have the same problem as you do... so,
try searching for it in the general section
i can't help you with that, i have a green lens defy
best of luck
#edit
try doing what the guy above said
Questions go in the Q&A section
Did you do a full wipe from STOCK recovery prior to flashing your sbf? You MUST do a full wipe before you flash any sbf or you could bootloop. Reading your post it sounds like you can get to stock recovery (volume down +power) once you reach the triangle screen you describe press vol up, and vol down at the same time to get your menu and do a full wipe
Ok, brought it back to life!
First of all i want to thank all of you who wrote me in thread and private.
Second, yeah, i was pretty desperate mostly because i tried so many solutions, read so much and the thought that i was gonna empty the battery without finding a solution was really stressfull.
What did i miss? At step 6 what i should have done is press the volume up AND down at the same time to make the 3e Menu show up then wipe cache and everything and tadaaa... phone started.
Unfortunately it took me almost all night to figure out, read countless threads, googled like crazy till i found someone who posted the right and complete solution
Once again, many, many thanks guys
PS.
# espaciosalter20
i did several times with several images
# zyxwvut
i wanted to do a full wipe but the menu was not there, i thought that powering the phone with volume down pressed was enough to make the menu show up and do the wipe but unfortunately this was not the case... you had to press the volume up and down at the same time to make the 3e menu show up... stupid if u ask me... also not many ppl pointed this out in many tutorials/hints/threads so i had a hard time finding this piece of vital information.
edit said:
Ok, brought it back to life!
First of all i want to thank all of you who wrote me in thread and private.
Second, yeah, i was pretty desperate mostly because i tried so many solutions, read so much and the thought that i was gonna empty the battery without finding a solution was really stressfull.
What did i miss? At step 6 what i should have done is press the volume up AND down at the same time to make the 3e Menu show up then wipe cache and everything and tadaaa... phone started.
Unfortunately it took me almost all night to figure out, read countless threads, googled like crazy till i found someone who posted the right and complete solution
Once again, many, many thanks guys
PS.
# espaciosalter20
i did several times with several images
# zyxwvut
i wanted to do a full wipe but the menu was not there, i thought that powering the phone with volume down pressed was enough to make the menu show up and do the wipe but unfortunately this was not the case... you had to press the volume up and down at the same time to make the 3e menu show up... stupid if u ask me... also not many ppl pointed this out in many tutorials/hints/threads so i had a hard time finding this piece of vital information.
Click to expand...
Click to collapse
Next time, please, make a full wipe ALWAYS before flashing... Yo can do that even in custom recovery (not need to do in stock all times, just when things go really mess up )

huge need for help

First, I want to thank all the people who bring their contribution to this forum. This is by far the best resource place.
However, I couldn't find the solution to my problem, at least until now.
I had my Asus TF101 updated to the ICS and after that, the problems begin.
If I attempt to reboot it, it remains stuck to the screen with:
Eee Pad
Asus
Inspiring inovation....
powered by Nvidia tegra
Pressing pwr+vol dwn leads to the same screen with some lines saying:
"Checking for RCK.. press vol up in 5 sec to enter RCK"
If I press vol up
it remains stuck after a last line appears saying:
"Booting recovery kernel image"...it stays like that forever.
If I dont press vol up, it goes to a 2nd screen with two options in the middle: "wipe data" and the little green android man
If I chose wipe data, after confirming with volume buttons, it says:
"please wait a few minutes....
booting recovery kernel image"
If I chose the android, now it starts the cold boot linux, and that's practically the only way I can started.
That's basically the story.. It is imposible to get any update needing a reboot, incl firmware update (there is one attempting to install for the last two weeks)
For the reference, here are the versions installed:
Android version 4.0.3
Kernel version 2.6.39.4
[email protected]#1
Build number: IML74K.US_epad-9.2.1.24-20120503
Tried a couple of solutions, incl NVFalsh, Viper mod and easy flasher, without success. It is also possible that I didn't use them appropriately.
I am almost desperately looking for a solution, so any help is greatly appreciated. If it comes in a form of step by step type it would definitively help even more.
Thanks a million for taking time to read this and to reply!!
what model/sn do you have?
Model TF101
SN: B40KAS031804
Thx!
Ok then NVFlash is a good option.
this should work i think
http://forum.xda-developers.com/showthread.php?t=1683311
drivers are the most common problem with it so make sure you have the right ones
mrevankyle said:
Ok then NVFlash is a good option.
this should work i think
http://forum.xda-developers.com/showthread.php?t=1683311
drivers are the most common problem with it so make sure you have the right ones
Click to expand...
Click to collapse
Many tanks!!!

[Q] a500 with forgotten password and unable to restore unrooted tab

A coworker has given me an a500 to try and restore to a working conditiion. Here is the story I was given... Tablet was working fine but he had a pop up informing of an update. He ignored it for awhile but finally let it update and after it rebooted he was presented with a password screen. He has no clue what the password is. I don't know what the tablet was updated to and to my knowledge it is not rooted.
I have tried erasing user data by holding down volume up and power and toggling the screen lock switch back and fourth after the tablet vibrates. Tablet displays
Erasing Cache before SD update.
SD update cmd:recovery
--update_package=sdcard:update.zip.
Then displays in red Secure boot: image sos checksum fail. I have had a couple different update.zip files on the sdcard when trying this but none are successful and it never seems to erase user data as it always asks for a password.
I have also tried an EUU update and putting the tablet into apx mode manually but this to fails. I was able to get the CPUID off of the device using a thread on this forum and an Ubuntu installation.
I have poured over numberous threads and tried many things over the last couple days and have had no luck. I am look for some help in either just erasing user data so we can go through set up again or downgrading/rooting or what ever it takes to get the tablet in a usable state again. I have a little knowledge of rooting and using adb and have never tried ubuntu until this weekend.
Thanks
Can someone help me with this? Any suggestions?
jggrnaut said:
Can someone help me with this? Any suggestions?
Click to expand...
Click to collapse
theres a thread titled "will pay to get my tab fixed" actually there are 2, but in one of them I think the problem was resolved....I'll post a link to it if i can find it
oh... u say u used an update.zip - make sure it isnt still on yr sdcard???
out of interest what happens when u press power + vol UP - just wondering what bootloader the tab has...doing this will tell us
what part of apx mode failed???
i guess you've seen the SOS/LNX checksum thread???
you have a serious failure here, but hopefully not irrecoverable....fingers crossed
Hi, Thanks for responding. Its taken me a while to get back to this because of Thanksgiving and a project at work.
The update.zip is on the sd card. How do I move it the tablet?
When I press power + vol up the tablet vibrates then displays acer on the center of the screen. It then displays in the corner of the screen:
Erasing Cache before SD Update...
SD update cmd:recovery
--update_package=SDCARD:update.zip
Secure boot: image SOS checksum fail!
With the EUU update I run the PBJ20upgrade.exe. I then let it time out and manually put the tablet in apx mode. I then put in my CPUID and hit next. The tablet vibrates and displaces entering Acer download mode but the PBJ20upgrade.exe program displays that the upgrade process failed as soon as it vibrates.
The EUU update i tried was titled EUUs_SBK_Acer_A501_0.017.01_PA_ATT
Thanks again for the help

Updating to 4.3 error, no command, is my phone dead? :(

I literally just got the 4.3 OTA update. Phone was fully charged... like 98%. I went ahead and let it update. It rebooted, and it got about 75% into updating and then the icon switched to the sideways android with the red caution symbol and said "Error". I let it sit there for awhile hoping it would do something. It didn't, so I held down power to reboot. It rebooted to the same icon, but now says "No command". I did the vol up/power to get into the wipe/reboot options. I went ahead and rebooted. Every single time... I see the Google logo for like a min, then to the sad android logo w/ "No command". Now I can't even get that far, the indicator light flashes red. I've read that indicates a totally drained battery. Not sure how it can go from full charged to fully drained in a matter of minutes. However on the issue of the error and no command, is my device dead? I've never rooted it or used custom roms. I got the N4 for the pure vanilla stock experience, so I never felt rooting was needed. Any advice? Should I just call Google and request replacement?
I would try a few things first before calling Google. Sometimes the battery doesn't show its correct percentage, it's pretty common on my N4 as far as I can tell. Maybe you've just run out of battery. Let it charge for half an hour or so and then try it again.
If you can't boot to system after that, turn off your phone, press and hold volume down and power buttons at the same time for a few seconds until it boots to bootloader. If you can't boot to bootloader after doing this let it charge for more time, an hour or two.
Sometimes, after the battery has run dry completely it is really hard to turn the phone on (I've even seen this behavior on my 7 years old Nokia). One question, does a charging animation shows up when you plug your phone?
Mercado_Negro said:
I would try a few things first before calling Google. Sometimes the battery doesn't show its correct percentage, it's pretty common on my N4 as far as I can tell. Maybe you've just run out of battery. Let it charge for half an hour or so and then try it again.
If you can't boot to system after that, turn off your phone, press and hold volume down and power buttons at the same time for a few seconds until it boots to bootloader. If you can't boot to bootloader after doing this let it charge for more time, an hour or two.
Sometimes, after the battery has run dry completely it is really hard to turn the phone on (I've even seen this behavior on my 7 years old Nokia). One question, does a charging animation shows up when you plug your phone?
Click to expand...
Click to collapse
It's been charging now for a little over an hour. No animation or indication the battery may be drained other than the red indicator light when I try to go to into the boot loader. Still can't do anything. If I power it on, I see Google logo for awhile, then sad Android icon and "no command". If I try to go into bootloader, just red indicator light and black screen. All while plugged in.
I just don't understand how it went from fully charged to drained in minutes. It was plugged in for hours today. In fact I initiated the OTA update only about 20-30 min after taking it off the charger.
Unplug your device, press and hold the power and volume down buttons for a few seconds until it boots to the bootloader. Now plug your phone again and let it charge.
Mercado_Negro said:
Unplug your device, press and hold the power and volume down buttons for a few seconds until it boots to the bootloader. Now plug your phone again and let it charge.
Click to expand...
Click to collapse
Alright, it's now been charging for 3 hours. I did what you just suggested. All that happens is I see a white Google logo for about 10 seconds, then it goes black. I think the device is off at this point. Stupid question I'm sure... I can't dock my phone to my computer to get any of my data at the "no command" screen can I? It needs to be fully booted, right?
Get into recovery, wipe cache, then it "should" boot.
ksilver89 said:
Get into recovery, wipe cache, then it "should" boot.
Click to expand...
Click to collapse
Like I said above, I'm not able to. I hold down power + vol up and it just shows white Google logo then goes black.
Well hmmm. I just did power + vol down for the hell of it, and I have a menu. Selected "recovery mod" and it just went straight to the sad Android icon with "No command".
I'm not sure what to make of all the stuff I see on this menu...
https://dl.dropboxusercontent.com/u/28754710/20130730_100302.jpg
Here is a short video of what I get from that menu when trying to go into recovery...
https://dl.dropboxusercontent.com/u/28754710/20130730_100936.mp4
For the sake of simplicity, learn how to use Fastboot. You should find more than enough information in the General section.
All you need to do is run this command in bootloader mode.
Code:
fastboot format cache
Edit:
Just saw the video, press vol up + power together in the recovery to access the menu.
ksilver89 said:
For the sake of simplicity, learn how to use Fastboot. You should find more than enough information in the General section.
All you need to do is run this command in bootloader mode.
Code:
fastboot format cache
Edit:
Just saw the video, press vol up + power together in the recovery to access the menu.
Click to expand...
Click to collapse
Again... like I said before vol up + power does nothing. I can take a video if you like.
Disregard the above. Got it into recovery. I guess my pushing was off or something. I took the rigid case off and made it easier to press the vol button. Let's see what happens now.
Alright. Got into recovery, did a wipe data/factory reset, still no dice. This time it rebooted several times, Google white logo each time, then finally a sad Android icon with "No command". Guessing next step is to download it and try updating via ADB?... or just say screw it and call Google and initiate a replacement?
Alright, it is screwed. Long guide here: http://forum.xda-developers.com/showthread.php?t=2010312
Short guide:
1. You need basically 3 things, the factory image, fastboot, and nexus 4 drivers
2. Download and setup all of them.
3. Extract the factory image tgz file TWICE until you see a folder.
4. Place "fastboot" into that folder.
5. Unlock your bootloader, shift + right click inside the folder, Open command window here. Run "fastboot oem unlock" and read the agreement (it's screwed anyway), select Yes if agree.
6. Once unlocked, run "flash-all".
7. Go running around your house for 10 mins.
Warning: This operation will wipe everything in your phone, if there's any crucial data, edit flash-all.bat to remove "-w" flag, and remove userdata.img in the occam zip.
Edit:
Or probably you can just get a toolkit...
ksilver89 said:
Alright, it is screwed. Long guide here: http://forum.xda-developers.com/showthread.php?t=2010312
Short guide:
1. You need basically 3 things, the factory image, fastboot, and nexus 4 drivers
2. Download and setup all of them.
3. Extract the factory image tgz file TWICE until you see a folder.
4. Place "fastboot" into that folder.
5. Unlock your bootloader, shift + right click inside the folder, Open command window here. Run "fastboot oem unlock" and read the agreement (it's screwed anyway), select Yes if agree.
6. Once unlocked, run "flash-all".
7. Go running around your house for 10 mins.
Warning: This operation will wipe everything in your phone, if there's any crucial data, edit flash-all.bat to remove "-w" flag, and remove userdata.img in the occam zip.
Edit:
Or probably you can just get a toolkit...
Click to expand...
Click to collapse
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
pixelbat said:
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
Click to expand...
Click to collapse
Yes, what he suggested should get you up and running again (if not, then yes your phone needs a replacement). I saw the video and the image. I'm pretty sure your system was wiped somehow and that's why you can't boot to it anymore. If what he suggested fails I can walk you through the steps to flash each factory image separately.
What would you do if the nexus 4 drivers wont install?
I have similar problem, I got the 4.3 update ota and it crashed half way through and now it gets stuck on the X logo. I was trying to follow a guide (http://forum.xda-developers.com/showthread.php?t=2010312) to install 4.3 back onto the device but failed at the first hurdle, when plugin the phone in it fails on the driver software installation - mtp usb device failed.
Is there any other way to do it?
pixelbat said:
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
Click to expand...
Click to collapse
unplug your phone. reboot into bootloader (vol down + power) but don't plug it in
downloaded the file posted in this topic from the google website.
http://forum.xda-developers.com/showthread.php?p=44088784
once you download it, extract it to a folder
then open up flash_all.bat in notepad, and it will say -w near the end. remove that (leaving it would wipe all of your data) and save the file
then run it, it will say waiting for device. plug your phone in and it will start updating
flipfamous said:
What would you do if the nexus 4 drivers wont install?
I have similar problem, I got the 4.3 update ota and it crashed half way through and now it gets stuck on the X logo. I was trying to follow a guide (http://forum.xda-developers.com/showthread.php?t=2010312) to install 4.3 back onto the device but failed at the first hurdle, when plugin the phone in it fails on the driver software installation - mtp usb device failed.
Is there any other way to do it?
Click to expand...
Click to collapse
Which driver did you try to install? Naked Drivers 0.72? What OS (Win8, Win7, etc)?
Plug your device in, go to control panel, click on Device Manager, scan for hardware changes or select the device with a yellow exclamation mark. Click on "Update driver" and search for the drivers in your PC (where you downloaded them). That should work.
Just Boot from a ubuntu live cd, install fastboot with apt-get and get started
Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta

Bricked....but different than what others are describing

Ok guys, I somehow managed to brick my beloved G2.
Not exactly sure how I managed to do it. I had just flashed the latest Paranoid Android rom and tried to reboot the phone and it locked up.
Here's what I'm getting when I try to boot the phone:
It very briefly flashes the pink/white LG logo then goes to a blank/black screen with the following info in the upper left of the screen:
[640] Fastboot mode started
[690] udc_started()
[850] -- reset --
[860] -- portcharge --
[910] fastboot: processing commands
Then it just sits there. I tried opening a command window and executing "fastboot reboot-bootloader". The phone responds and reboots, but gives the same info as above. Then I tried "fastboot continue". Here's what it spits out:
[76930] fastboot: continue
[76880] partition_get_size 16777216 bytes
[77050] Loading boot image (5564416): start
[77300] Loading boot image (5564416): done
[77350] ERROR: Appended Device Tree Blob not found
At this point I'm totaly out of ideas. And I don't want to mess things up any more than what I've already done.
So am I screwed? Or is this recoverable?
Oh, BTW, it's a Verizon LG G2, and I had TWRP installed. I had successfully been using TWRP and flashing a few other ROMs and I have a couple backups on the phone if I can get into recovery.
Any help is greatly appreciated!!
Have you tried the button combo to get into recovery and restore a back-up (I believe it's holding vol down and power until LG logo, then releasing and holding them again).
As a last resort, have to tried returning to stock (which will erase everything)
http://forum.xda-developers.com/showthread.php?t=2448960
Yeah, I tried the buttons but the phone just comes up into the screen that I mentioned before.
I didn't try going back to stock as shown in the link you posted, but I'm in the process of trying another method of unbricking the phone.
Here's the link:
http://forum.xda-developers.com/showthread.php?t=2471370&highlight=bricked
Well that didn't work. I can get the phone into download mode and the LG software recognizes the phone but the phone doesn't do anything. It just sits at the update screen, at 0%.
Any ideas, guys?
My idea is to steer clear of these so called stable ROMs. ..I been check-in md5s like no bodies business on this phone. I only trust Scott and Jake right now.
Sent from my VS980 4G using XDA Premium 4 mobile app
Did you try the vzw specific method to return to stock?
Not yet but I will give it a try. I'm currently downloading the rom's tot file. It's big and it's taking forever. I'll post back if I have any luck.
Thanks guys.
I have had a similar issue fast boot mode started black screen then stuck on boot loop. Have u resolved or want my steps?
Sent from my LG-D801 using XDA Premium 4 mobile app
---------- Post added at 04:06 AM ---------- Previous post was at 04:01 AM ----------
While on black screen hold power and volume down till u get lg screen
Then keep holding it will go black and led light flashes red like 10 times.
Then let go it should be powered off.
If it isnt or is hold same buttons down again. Depending on what it does I held same buttons till LG logo came up again. Either it will quickly flash or flash the logo for like 5 secs. If 5 secs then let go and quickly hold power button. If not hold all three buttons and see.
Its happed to me like 3 or 4 times and thru trial and error i managed to get white hard reset screen then hit power. Or security error screen and i used the same steps. Let me know
Sent from my LG-D801 using XDA Premium 4 mobile app
It finished downloading while I was asleep so I haven't actually finished this method. Yeah, before I go any further, what did you do to fix your phone? I'd really appreciate it!
scheirere said:
It finished downloading while I was asleep so I haven't actually finished this method. Yeah, before I go any further, what did you do to fix your phone? I'd really appreciate it!
Click to expand...
Click to collapse
Doh! It was right in front of me, in your post, if I'd just read the entire thing!!
Anyhow.....OMG!! Got it the first time. Just like you described it. Just for anyone else that falls into this problem:
Hold power & down volume buttons until it powers off....and stays off, then release buttons. Then hold same buttons again (power & down volume) until the LG logo comes up and stays up. (You'll know it's going to stay up......because if it doesn't....the logo is only visible for a second at most before it goes back to the black fastboot screen.) Then release and hit power button again. It came up to a white factory reset screen, as razrlover described. Hit the power button to accept the factory reset......... At this point my phone booted into TWRP and I was able to restore a previous backup. Boom.....just like it didn't even happen!!
But here's the big question....what happened??????? I know I'm not alone with this problem now. What did we do to get stuck like we did??
Anyone with any ideas? Hopefully we can figure this out so no one else has this problem.

Categories

Resources