Hi. I have a Asus TF701T. It is not Unlocked/hacked etc. Its about a month old. Over the weekend there was some auto update. When the tablet rebooted it was stuck on the boot/startup screen with the rotating circle.
I have trawled though the forums here and found a case with the same symptoms but there is no solution posted.
http://forum.xda-developers.com/transformer-tf701/help/locked-tf701t-stuck-infinite-boot-t2824737
Here's what I have observed for my case. I boot up with "Power + Vol down" and the fastboot screen appears ...
" Android macallan-user bootloader <1.00.e> released by “ww_epad-10.14.1.147-20131022” "
I am then faced with 3 options … RCK, Android, Wipe Data
With no MicroSD inserted I tried the above options in this sequence.
1.) Select “Wipe Data” – Screen moves on to android robot on his back with red exclamation mark. He falls on his back after about 2 seconds.
2.) Select “Android” – Goes back to boot screen and rotating circle. Nothing further.
3.) Select “RCK” – Screen moves on to android robot on his back with red exclamation mark. He falls on his back after about 2 seconds.
OK ... then I needed to get firmware on the microSD (formatted FAT32, 32gig).... I then went to ….
http://www.asus.com/uk/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
and downloaded the “WW_10_26_1_18_SDupdate” … and followed the instructions.
So, after placing the “T4_SDUPDATE” in the root of the microSD and inserting it into the TF701T. Rebooted with “Power+Vol down” … got back to the boot loader screen with the above mentioned 3 options. Did the following.
1.) Select “Wipe Data” – Screen goes to Green android with updating blue bar … the bar shows progress for about 3 minutes. Then on his back with red exclamation mark.
2.) Select “Android” – Goes back to boot screen and rotating circle. Nothing further.
3.) Select “RCK” – Screen goes to Green android with updating blue bar … the bar shows progress for about 3 minutes. Then on his back with red exclamation mark.
I have tried the same approach with other versions of the firmware:
UL-K00C-WW-10.14.1.47-user.ZIP
UL-K00C-WW-10.26.1.7-user.ZIP
UL-K00C-WW-10.26.1.18-user.ZIP
UL-K00C-WW-11.4.1.17-user.ZIP
None of these worked. In fact, after copying these individual files to the root of the empty microSD, I found that when I select RCK or WipeDate, then the android falls over within 2 seconds (NOT minutes).
Interestingly, if I rename the zip files to “T4_SDUPDATE” then there seems to be progress but the android falls over after about 2-3 minutes. This suggests that the bootloader is expecting a firmware zip file with that name.
I am at a loss. I don’t know what else to do. Any help will be much appreciated.
same problem
I'M having the same problem, I was using the tablet and it shut down by it self and now is stuck on a black screen and when trying to wipe data or recover it gives me the red exclamation. Did you find a solution?
same problem!
any solution?
Related
Since yesterday I own a g1 developer version, when turning the phone on by teh power button all I see is a red, green, blue & white background with the following text..:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
Serial0
When turning the phone on by the power button & the home button I get a white triangle with a exclamation mark, from there, the ALT+L button gives me the following:
Android system recovery utility
E: can't open /cache/recovery/command
From here you can reboot the phone, apply sdcard:update.zip or wipe data/factory reset.
I've tried different update.zip version, but when de update is going to install the following error appeared (Some update.zip versions give this, some give a line 2 error)
"faillure line 1: assert file_contains(“SYSTEM:build.prop, en nog een hele lap tekst..
Could it be that I use the wrong update.zip? Anyone a suggestion? All I want is the phone working..
a good tutorial how to patch and upgrade your phone can be found on the cyanogen mod page http://www.cyanogenmod.com/ in the wiki section. There is a foolproof description especially for the develloper version, just search for it!
From what I understand ADP1 uses different recovery procedures than retail G1s. Check HTC's ADP1 site for more details and to download a recovery image.
wrong section dude
now that you have a dream, u might want to avoid asking questions in the dev area...u will get burnt to a crisp very quickly
the search button (and google) is your best friend...use them before posting
I've followed this
1 Download the DREAIMG.nbh:
2 Place "DREAIMG.nbh" on the root of your SD card.
3 Turn your phone off.
4 Start up in bootloader mode by holding Camera + Power.
5 Hit power button to start the update.
6 Once the install completes hit action(trackball down) and your phone will reboot.
The phone is installing the update, but after a reboot it gives the same color screen I've had before.
Sounds like your camera button is messed up/stuck. Try blowing some compressed air in there or something like that, see if that helps.
I don't think it has anything to do with the camerabutton.. When I leaving the .nbh file on the sd card, en I turn the phone on, it comes with the color screen.. If the camerabutton is active, he should start the update..
Alright, I´ve made some progres..
Trough this site http://www.htcforums.com/threads/3298-POSSIBLE-SCREEN-OF-DEATH I came hier https://android.clients.google.com/updates/partner/signed-kila-ota-148830.de6a94ca.zip
This zip file is nog up anymore, downloaded it somewhere else & renamed it to update.zip, placed it on a sd card. Booted the phone with the home en power button, -> ALT + L -> ALT + S.. This is the first rom which is going to install..
Installing from sdcard...
Finding update package...
Openen update package...
verifying update package.. takes a minute
installing update...
formatting boot
extracting radio image
formatting system
copying files
After this a manual reboot with back & power button, the phone shows a kind of chip met a arrow, automatic reboot, show a white box with a arrow pointing to a phone, automatic reboot & again the rainbow screen.
Well, tried a lot, searched the internet, but can't get it to wrok..
hello, i am new too this site, and i am in the process of rooting my zio. i heard that xda was one of the best places to find a rom. but i can't seem to find out where to go to download one or even check them out. i'm trying to be very cautious about this process. so if someone could please direct me in the right location i would be forever grateful.
Zio
2.2.1
cricket wireless
sincerely,
jduncan
There is only one rom for this phone and that is the Open Zio Rom. it is in this section under the Zio M6000 Android Development section, make sure you follow all instructions to the letter. This includes Backing up your current Rom and wiping it to install the new one.
Edit Here is the direct liink to the OP - http://forum.xda-developers.com/showthread.php?t=1073889
I just got a Zio 2 days ago, and the basic process is this:
1) Get ClockwordMod Recovery for the Zio here - follow the instructions in that post, to the letter - but ONLY when you're actually ready to get the ROM installed because you need to copy it to the microSD storage card *first* so CWM can install it.
2) Get OpenZio ROM 2.1.2 from here - download it, but do NOT extract the Zip archive. It needs to remain a Zip file.
3) Plug in the Zio making sure you have a microSD card in it that can hold the OpenZio ROM archive (openZIO_ROM_2.1.2_Spz0.zip 81MB) - hopefully you're using something like a 2GB or larger microSD card so you've got space. Copy the Zip archive to the root of the microSD card (makes it easier to find).
Also note: this ROM does not run off the microSD card like some phones are capable of, the Zio can't do such things, at least that I'm aware of.
4) Once the ROM archive is copied to the Zio, and while the Zio is still plugged into the computer (because you're about to use the boot over USB capability it offers, aka fastboot), shut the Zio down completely.
5) When the Zio is powered off, press the Send (green) and Power (red) buttons at the same time and hold them for roughly 10 seconds or so, might be less on your phone, I don't know. What you'll see is the Kyocera logo (probably) on the screen and some white text in the upper left side.
When you've waited about 10 seconds, let the Send and Power button go. If everything is working properly, your computer should notify you that a USB device is now attached - with Windows you'll get that "duh-dunk" sound.
6) Follow the instructions for Clockwordmod Recovery as noted in step 1 - now is when you follow them to the letter. Open the command prompt, change to the directory, run the command:
fastboot boot clockwork-recovery.img (press Enter)
After a few seconds it should finish the process on screen (on the computer) and you'll note activity on the Zio itself, after a few more seconds you should see a blank screen with green text options at the top. Use the Volume control buttons to move up and down the selections, use the button under the scroll ball (press the ball down till you feel it "click") to make the selection highlighted.
Use the normal Back softkey to back up a step, etc. You can also use the Home softkey to go back to the main CWM menu at any time.
6) Choose the "Install from zip" option, browse for the file the openZIO_ROM_2.1.2_Spz0.zip file in the root of the microSD card, say yes to the confirmation messages, and wait for it to flash the ROM. When it's done, press Back or Home to get back to the main CWM menu, then select "Reboot the phone" and that's about it.
It should reboot into OpenZio 2.1.2 from that point on. If you don't see the somewhat familiar green Android with the glowing silver-gray circle and the green-swishy water pattern, well... I didn't the first time I did this until I read someplace that OpenZio is best installed on a device that has just been freshly restore to the stock 2.2.1 image from Cricket - as Spz0 said in the OpenZio thread, this ROM is for the Cricket Zio but it might work on the Sprint model. It's your choice to try it if you've got the Sprint model.
Because I wasn't getting any noticeable improvements in performance, I decided to go back to the factory Cricket Zio image (found here and THEN I installed OpenZio and THEN I noticed a boost in most everything.
So, the proper method is make sure it's got a factory/stock 2.2.1 installation on it, then install OpenZio 2.1.2 on top of that, and when it boots the first time (it'll take longer, of course), you should see that little green robot and then swirly water mist thingy... you're good to go if you do.
Hope this helps...
Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didnt get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.
Solution
Attention: If you want your media files, backup your current state first. Go to backup and restore -> backup. Then do steps written below. Backup will be in CWM folder on your sdcard.
This is called a soft-brick. It's good that you can access download and recovery mode using 3 button combinations. First, download a stock Gingerbread ROM for your device model and put it on your sdcard. Boot into CWM and select Wipe user data -> Yes. Wipe Cache Partition -> Yes. Go to Advanced menu and select Wipe Dalvik cache -> Yes. Now return to previous menu and select install zip from sdcard -> choose zip from sdcard -> select name.of.downloaded.rom.zip -> Yes -> Wait 1-2 minutes to flash -> Wipe user data -> Wipe Cache Partition -> Wipe Dalvik Cache. Then select Reboot system now from main menu, and wait 4-5 minutes for it to boot first time.
DaniTheMan said:
Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didn't get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.
Click to expand...
Click to collapse
Hello everybody.
i have updated my tablet and stuck now on the welcome screen page.
I have installed this version : ASUS MeMO Pad (ME572C)Software Image Version: V12.14.1.12 For WW SKU only* from this page http://www.asus.com/de/Tablets/ASUS_MeMO_Pad_7_ME572C/HelpDesk_Download/
i have fellowed this instruction here :
ME572c recovery
Today I did it : I changed a setting I shouldn't and my Memo became unusable (boot loop ?); even factory reset didn't do the trick...
So now I can make a How-to for recovery and rooting ;o)
Recovery (stock firmware) :
==> You'll need a MicroSD card on wich you have to put a file with you PC (or another device)
Prepare SD :
- Get update file from Asus (mine was UL-K007-WW-11.8.3.30-user.zip for 8.3.30 version and WW device)
- Copy file to FAT formatted MicroSD and rename it "MOFD_SDUPDATE.zip"
Go to droidboot mode :
- turn the K007 on with "Power" and "Volume UP" keys and keep'em pressed
- release "Power" when the screen turns on
- then release "Vol UP" a few second later when the Asus logo disappears
Flash :
- insert MicroSD into K007 slot
- Select "SD Download" using "Vol DOWN" key then confirm with "Power"
==> It will flash the device with the original Asus firmware and reboot to display the first launch wizard...
Not sent from my K007...
I found the instructions here: http://forum.xda-developers.com/memo-pad-7/general/me572c-root-debloat-t2992131
Now everytime i boot with power button + volume up i got this screen (picture one and two)
When i try to boot into recovery, the tablet always try to update the system. When an sd card is insert with FW V12.14.1.12 it install it, but nothing changed. When no sd card is insert, a failure come (picture 3)
Everytime after the fifth settings page ( the time settings picture 4) the app go back to first page (picture 5)
I can not get out off the welcome app. even sliding up from the bottom of the screen. Or slide from the top i see no bottoms and no settings
opps. sorry. bad suggestion and deleted
If you see picture 3, just hold power button and press volume-up button. Now you are into the recovery menu and you can do " wipe data/factory reset ".
Hello.
Yesterday I was copying a file to an external disk. But I didn't look at the charge percentage, I'm out of charge. And I couldn't pick up the phone again.
But I was able to enter TWRP and Download mode.
I tried to wipe System, repair System, change file system of the System but just some errors like: E: /system not mounted and when I click System in mount menu nothing happened.
And I flash Stock ROM to my phone. Then TWRP was gone but the blue "system update" screen came up. After a few seconds, some text started to appear on the screen.
I found someone using the same phone as me and getting the same error:
Note 5 bricked after update
Symptoms: Turn phone on it goes to System updating and then spits me out at a black and white screen with messages of stats failed efs mount. Then proceeds to reboot and the process repeats it's self until the battery dies. What i've done to...
forum.xda-developers.com
How can I fix?