Related
Hey!
This is the issue: when I try to turn the phone on by just pressing the red button it goes directly to the fastboor menu. If I try to go to the recovery from there shows "TATTOO" for hours. If i try to go to the recovery dirctly by pressing HOME+ red button, it firsto shows the fastmenu for a second and tries to boot unsuccessfully. During this boot tries, I try to get some info with adb logcat, but the device is not casting anything. And well, if a picture is worth a thousand words, I guess a video is way better:
youtube.com/watch?v=zAejyMIVNGk (newbie, no urls!)
sorry for my english
And well, I have no idea how I got to this, this used to be my phone, but I bought a Nexus One and gave this to my sister, who has no idea what happened (as usual). Oh, this morning somehow I managed to get to the recovery menu, and booted until the android bootscreen, then vibrated and died again. I got to the recovery again, made a nandroid backup and wiped all data, it booted successfully, but the rom had no home application and ran really bad.
I was about to try to make a goldcard and install the stock RUU rom, but if I have no adb I cannot make one...
Any idea?
PS: the rom was nFinity 1.18 (2.2 Froyo) and the recovery was the lastest Clockwork.
PS2: I just realized that in every place I say fastboot I mean HBOOT, sorry again
sounds like recovery is still there, if you hold home + menu when phone if off , and then click red power button you should get recovery menu.
Then hopefully you can try full wipe and install a rom , rember the first time u boot a rom might take a few minutes
let me know how it goes
Yup, not using that method but I can manage to get to recovery sometimes. I'm trying to flash another ROM, but for some reason it doesn't let me. I've tried KalimochoAz (gingerbread) and HDCR (donut) and says something about assertion failed when checking if the device was click on the first case and in the second, complains about unsupported stuff...
I was about to try another roms by random but the SD does not refresh or even mounts, there must be something really messed up with this phone...
You can try to flash your stock rom from fastboot.
You don't need a goldcard, just run the update utility on pc, go to your temp directory and take the rom.zip file, rename it to CLICIMG.zip, copy it to sd card, put card on device and on fastboot menu pres vol down to start flashing the rom. I is the same version with the rom that device has before rooting, you will not get any errors.
I think there's a little misunderstanding here, mainly because of my confusion, it's not the fastboot menu qhat I get, but the HBOOT menu, and pressing the back button in order to access fastboot doesn't work...
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
manutenfruits said:
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
Click to expand...
Click to collapse
Of course will not work like this.
You must first run the RUU utility on pc and while is open to search your temp directory(maybe is inside another folder) for rom.zip file. This is the rom, the executable is an installation program which contain the rom and the app to flash the rom from pc packaged. You need only the rom.zip for flashing from sd card.
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
manutenfruits said:
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
Click to expand...
Click to collapse
You don't need to go so far. Just run the ruu utility and when the first screen appears go to temp dir(c:\users\you user's name\local\appdata\temp on windows 7). The executable is an encrypted package and when you run it extracts all included files and then starts the installation program. These files will deleted after this program exits(when the installation complete or an error occurs)
Cool! I just renamed it to CLICLIMG.zip and I finally loaded. The problem now is that when it finishes, instead of asking me to flash it, says
"CID Incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No"
While running the RUU I made sure that it was for HTC Tattoo since it showed me the device during the steps. And I got it from a post describing the steps to flash it using the goldcard.
Furthermore, this error is something similar to what happened when I tried to flash from the recovery. This is REALLY weird...
Probably this isn't the sama as your device's stock rom. I think goldcard needed for flashing any htc original rom, but without goldcard only the device's version will be flashed successfully. Try to download other original roms if you don't know which you had before.
Here is a site with shipped roms for tattoo:
http://www.shipped-roms.com/index.php?category=android&model=Click
The RUU wasn't a problem, I tried now with a goldcard and flashed successfully! I could not get ADB connection to make it, but I once made one and still had the .img in my mail inbox.
But still nothing has changed...
pressing on drives me to the HBOOT screen, whose only options that work are "simlock" to flash CLICIMG.zip, and recovery (freezes on "TATTOO")
EDIT: does not freeze, but goes back to HBOOT after a while... ¬¬
You say that now you have the stock HTC rom and again you cannot boot it and instead the device reboots again to HBOOT?
Then maybe you have a hardware problem which leads to this behaviour.
OK, now I guess it still has warranty, but the problem is that I rooted it.
But now that I flashed somehow the original rom, should be no problem right?
Yes, if you successfully flash the stock rom, you're not root any more.
had that problem to, but theres easy fix for it without doing all whats being sayd here
Even tho phone dont boot annymore and stays on logo plug in the usb cable
and work with adb shell and reflash recovery (to be good tattoo-hack.ko etc tricks need to be done before doing it or you get errors)
http://forum.xda-developers.com/showthread.php?t=716282 step 1.5 and tools from step 1.3
and ether get Amon RA recovery or clockworkmod and use
Code:
./flash_image recovery /sdcard/recovery.img
then reboot into recovery
HTML:
adb shell "reboot recovery"
mount usb put in a custom rom and flash it
if all done well should work (had same problem)
bascly adb still work even if you think you bricked phone just have to let it "startup"
Greetings
I'm afraid that won't work. I've been trying all the time with adb logcat and adb devices unsuccesfully. I thought that the TATTOO bootscreeb would give me some feedback in all cases, but now doesn't seem to work...
I've had similar problems when trying to flash nfinityGB.
My problem was that I missed something on the way from
- creating a gold card
- rooting device
- installing recovery
- flashing rom
All I did was to download and execute "RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe" (or any other ruu).
Be shure to have SDK with all drivers installed properly.
After this your device is in unrooted (original) state as dancer_69 already told you.
Now you can decide whether to claim warranty or properly follow the guides on xda to get root and flash custom roms.
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
manutenfruits said:
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
Click to expand...
Click to collapse
Something like this thought when I said that maybe is a hardware problem.
Hi everyone
I have a Huawei U8800 which I can no longer boot (it gets stuck at the white Huawei screen). I can, however, access the 'pink screen' (vol+, vol-, power button) and the files when connecting it to my computer, but entering recovery mode (vol+, power button) does not seem to work.
I am an utter noob, so my approach to solve my problem would be to simply take the phone back to the shop, but first I would like to erase my personal data. Is this possible in my case, without voiding my warranty? In case it is not, could you perhaps tell me how I could go about fixing the phone myself (in such a case I would also be willing to scrap the warranty)?
Thanks a lot in advance!
PS: I have not rooted the phone or done anything like that, all I did was installing a couple of apps, so it's pretty much in its original state.
You should be able to flash one of the original roms and the phone would boot if there're no hardware problems.
The original roms were removed from the huawei website but if you search the site there were plenty links afaik.
Thanks dionero. The trouble is that I am too much of a noob to understand what exactly you mean by 'flash one of the original roms'. Could you please provide some more detail? Thanks a lot
Here is a rom with instructions on how to flash :
http://forum.xda-developers.com/showpost.php?p=17591131&postcount=1
Thanks again! I will give it a go later on today.
Did you manage to recover the phone?
Thanks for asking! First I need to go and buy a micro SD card, as that seems to be required for the process. But I'll post an update once that's done and I've attempted the recovery. Thanks again for your time!!
Hi,
finally the micro SD card has been delivered - I'll never buy from that shop again, what long shipping times!
Anyway, I'm afraid the recovery did not work. The phone did react, said it was performing the upgrade, and it the end it even displayed the "Upgrade completed" message. Attempts to reboot, however, still don't let me get any further than the Huawei screen
One further observation I have made (even before the attempted recovery, but ever since the phone stopped booting): when the phone is switched off (which nowadays can only be accomplished by removing the battery), and I plug it into the power outlet, it immediately starts its booting attempt. When the phone was still alright, however, it would recharge its battery without trying to boot immediately. I don't know whether that's important, but maybe someone can make use of this information!?
Well, in case anyone on here has got some more suggestions as to what else I could try I would be really grateful. Thanks a lot for your time and effort, and for reading this!
How long did you wait at the Huawei screen? First start takes longer time and it should reboot multiple times. Anyway, you should try flashing one of the recoveries, 5.0.2.3 for example. You can find it in the development section. With that you should wipe cache and data, delete dalvik cache and then try to start it.
I'm on mobile so I can't give you a good tutorial, but recovery should be fairly easy to install (look for stockwell's recovery).
Sent from my u8800 using XDA App
Thanks, Blefish, for your reply. I tried recovery flashing at some point along the way, and I tried it again now, this time using the version you suggested. Still I simply cannot boot into recovery mode. I can either get the "pink screen", or simply the white Huawei screen, even if I press Vol+ and the power button (I've also tried pressing them for different amounts of time, but all to no avail)
Oh, and as an answer to your question: I waited for maybe 15 minutes or so.
Sorry wrong info
1. Download a stock rom.
2. Create a folder on the SD card named "dload"
3. Copy UPDATE.APP and UPDATE_CUST.APP from stock rom archive to dload folder
4. Insert sdcart to phone
5. Switch on phone with press vol+ and vol- buttons
6. The installation will start automatically
Thanks ufukyayla, but what you're suggesting is exactly what dionero had suggested earlier, and unfortunately it did not work.
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
My tf101 cannot enter recovery anymore
when i try to enter recovery ,
there is a " ! " on the robot , then tf101 reboot automatically
then freeze on the ASUS logo page
I cannot boot up the machine in normal mode too !
my tf101 is B70 version, someone help..thanks
! with the Android guy is recovry, stock recovery.
instead of Vol up to get into revovery, wait till you get options to cold boot or wipe device.
try booting that way.
also what were uou doing when it gotvstuck at that screen?
baseballfanz said:
! with the Android guy is recovry, stock recovery.
instead of Vol up to get into revovery, wait till you get options to cold boot or wipe device.
try booting that way.
also what were uou doing when it gotvstuck at that screen?
Click to expand...
Click to collapse
i tried cold boot , but it said cold booting up linux .. but no response
i tried wipe device , but it still freeze on ASUA screen too
yesterday, i try to root and install CWM via Prime V4.5
then the device comes this .....
Thanks ...
Never heard of that root utility before. You may not have used the right rooting utility for your device which can cause a brick situation. Also, are u sure u dont have the tf 101 and not thr tf prime? The vipermod utility found in the tf prime forum will root ics for both the 101 and prime. My suggestion is that u make sure u have the right device and search the right forum for brick recovery, unroot, or return to stock threads. They are usually found in the development sections.
Sent from my SGH-I777 using XDA
viperMod PrimeTime 4.5 will only root the TF101 and shouldn't be used to install CWM. That's why it bricked.
cholywell said:
viperMod PrimeTime 4.5 will only root the TF101 and shouldn't be used to install CWM. That's why it bricked.
Click to expand...
Click to collapse
i had an issue that was caused by lack of sleep last night that i might be able to help this guy out.he never used it to flash CWM.. he rooted it and never flashed from within the CWM app. The stock recovery doesn't have options for choosing files ect..
victor1144 said:
My tf101 cannot enter recovery anymore
when i try to enter recovery ,
there is a " ! " on the robot , then tf101 reboot automatically
then freeze on the ASUS logo page
I cannot boot up the machine in normal mode too !
my tf101 is B70 version, someone help..thanks
Click to expand...
Click to collapse
I might be able to help you... I saw your post around 4am. I had the same problem kinda. Was asleep most the day (got done at 6am).
I rooted with viperMod PrimeTime and it worked !
BUT i forgot to FLASH CWM RECOVERY from inside the app and proceeded to install the new ROM after root was made USING the CWM app. What happened in my case , the CWM app restarted trying to flash the new ROM, WITHOUT CWM being my recovery instead rebooted to STOCK recovery and something glitched up. I had the same thing as you stuck on Eee pad never re-starting. Cold boot wouldn't work or full wipe..In my case something conflicted.
Below is the NVFlash of the 3.2 Build of 8.6.5.13 (Latest Build). You need to re-flash again using APX threw your USB connected to a PC (it self installs) :
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
the links are in Grey btw and says US version, ect ..read everything but its very straight forward... ill explain what i did toward the end of the post to simplify it since it took awhile to figure it out. Ill add side comments threw the process that explains better than the link.
Attention: These tools are designed to bring your device back to working condition. They are great for getting back to stock if you need to send your device in for repair or you need to downgrade to stock in order to root your device, etc.
Instructions for Windows users:
1. download the file from the original link i gave above. NVFlash of the 3.2 Build of 8.6.5.13 (Latest Build) USWindows
2. unpack zip to desktop.
3. Press Volume up and Power at the same time on your Transformer to enter APX mode, connect to pc (hold for about 7 seconds). Basically, Power off.. THAN, power and Volume up at the same time to enter APX mode. IMPORTANT!! the screen remains BLACK like its frozen ,with no writing or indication something is happening. that's normal and the original poster in the link never mentioned it. That is APX mode..
4. drivers for APX are in there if you need them..inside the windows downloaded file its called NVFLASH towards the bottom
On your PC go Device manager.. if APX is working correctly and the Transformer is in APX mode it will appear as an exclamation on the device manager named APX.. you cant miss it.. it stands out. On my Windows 7 PC it changed and said Asus USB (or something like that)
5. double click Run Download.bat file and let run! everything is prepackaged so no copying files, etc. In the same file you downloaded that you unzipped named Windows its the 4th file that says "download" with a gear looking icons.
Your Transformer (based on what happened with mine) will go threw a self install like its pushing files and flashing it..the black screen looks like its being pushed the files and reflashing without a recovery. Your going back to stock. if you dont see anything on your Transformer screen after running/double clicking the Download.bat file ....Right click on APX in the device manager , properties, Drivers, update Firmware, choose manual install and find the Downloaded.bat file and click it. That should do the trick..I did both and only noticed the Transformer lighting up after manually pushing it threw APX.
6. After the device reboots power it off. Then hold vol- and power until you get the option to erase your data.... Select the option to wipe data.
7. Download the latest update from the Asus website if applicable and follow the manual instructions. This step may not be necessary if your OTA update worked or my nvflash is the latest version. US update on there site is 9.2.1.17.Its the only one...
What i did was go back to stock since i didn't see any interesting ROMS..Point is THAT unbricked my device by flashing it in APX mode when it was connected to the PC.
I did use ViperMod again to Root, but used the Clockwork mod app in my Transformer to FLASH CWM RECOVERY to try a few ROMS out.
After trying a few of them out i choose to revert everything to stock, unrooted and reflashed STOCK recovery.
Hopefully that helps you out.. it did work for me...
Thank you so much it worked great
Lantek23 said:
Thank you so much it worked great
Click to expand...
Click to collapse
Glad i could help
Sorry to dig up slightly old threads, but I have a question for you. I have a TF101 that I was trying to update to ICS. It is currently running 3.2 courtesy of the unbricking tool listed in this thread. I had to unstore it as it was bricked from a bad install. That was many moons ago. It won't show an updaate listed, so I decided to go with the manual route. I downloaded the appropriate update (my device lists WW version) loaded it on an SD card had the install prompt come up and rebooted to install... For a split second it shows the android with the gears like it is installing the update and then shows the android with a triangle and exclamation mark. After that, nothing. I have to reboot to get it off that screen. Upon booting, I get a message saying system update failed (2) unknown error. Any ideas?
If Im not mistaken, the zip file you download (I guess from asus?) contains another zip.
Thats the zip you should place on your SD card, did you do that?
Also try renaming that zip to EP101_SDUPDATE.zip (the one extracted)
I already had the zip extracted, and renaming didn't do anything.
Killa357 said:
I already had the zip extracted, and renaming didn't do anything.
Click to expand...
Click to collapse
Are you rooted? Did you remove any system apps?
Another thing to try is on your micro sd card, make a folder name ASUS and inside that folder another folder call Update, inside the Update folder put the extracted zip file (don't rename). Turn off TF and turn it back on, see if it will detect the update file.
If that fail, you did mentioned you use the unbricking tool, use that NVFlash to flash a compatible ICS ROM
It isn't rooted anymore since I ran the unbricking tool, and no system files were modified. Placing it in Asus>Update folder didn't work. I may end up having to really do things manually...
Killa357 said:
It isn't rooted anymore since I ran the unbricking tool, and no system files were modified. Placing it in Asus>Update folder didn't work. I may end up having to really do things manually...
Click to expand...
Click to collapse
You don't need to be root to use NVFlash.
Just when with a slightly older version of the update and it worked. There may be something wrong with the file Asus has hosted.
Hi
I have a slightly different problem. I have rooted my B60 serial number, it has the ICS from ASUS on it and it boots fine, its rooted and it works. Now the problem is I thought lets try a clockwork mod and play with custom roms.
So I set my win 7 up to adb etc, and pressed power button volume button - and off to recovery I went...
but all I got was a little green android on its back chest open and an exclamtion mark. No adb fastboot devices command.
I seem not to have a recovery nor a way of forcing a custom recovery.
Should I NV flash or just be happy the tab works and leave well alone?
Any other answers since a lack of recovery may come back to haunt me sooner or later.
I also tried the power button vol uyp for 7 secs and nothing happens I can get to the cold boot erase data option on power down, don't want to do that yet since Im not sure what data gets erased and I may have a totally non working tab.
Use RecoveryInstaller to install cwm recovery
Use RecoveryInstaller to install cwm recovery
This is my problem I can't get recovery - nor can I get adb to see the device. It shows as a hard drive/storage device but not in adb.
As the title indicates, I soft-bricked my G2 via bad rom flash (wrong version of CM)
This post will be my outline of how I got my phone out of this mess and operating perfectly.
I foolishly made the mistake of not making a backup so as a result, I have scoured numerous forums and pushed my google-fu to it's limits. Biggest tip I can advise (as if it needs to be said again) is to backup before you do any flashing. If things go south though, here's what happened to me and how I fixed it all.
I rooted and installed TWRP 2.6.3.2 then did full wipe and flashed the wrong G2 version of CM from the internal storage. Rebooted and got the "udc_start()" message of sadness.
Hard reset the device by doing the power button/volume down thing which involves the following:
fully black screen except for tiny little message saying something like UDC_Start() and some other jibberish. Basically it doesn't do anything.
Hold down the power button for about 12~15 seconds. After 10 seconds the phone display will shut off and the LG logo will pop back up. KEEP HOLDING THE POWER BUTTON DOWN.
The screen will shut off again.
Now holding the volume down button, press and hold it and the power button together until the LG logo comes up again.
Release the buttons and then quickly hold down the power button again until you get a device reset screen.
hit the power button to confirm and it will load up TWRP.
I was relieved to be back in recovery but it dawned on me that the wrong version of CM is the only rom I had on my phone. Performing a factory reset does not fix the issue.. just kicks me back to that UDC error.
Next level googling engaged. I had the CORRECT ROM and a couple others for my device downloaded but I had to somehow get them onto the internal storage so that I could flash them.
HOWEVER, I also discovered in the hellfire rom thread, there are issues with TWRP version 2.6.3.2 flashing roms and that flashing the PHILZ recovery from within TWRP (just like flashing a new rom) to replace TWRP would work. I didn't want to take any chances so I got that zip file from here.
http://forum.xda-developers.com/showthread.php?t=2201860
To get these zip files onto the device, ADB push command was the trick.
I grabbed this (if the link is broken, google search for ADB fast boot zip)
http://d-h.st/iqA
And extracted the files to a folder on the desktop.
Next, after reading through some ADB push threads, I copied the zip files into the ADB folder on the desktop and then in windows explorer, hover the mouse over that ADB folder and then shift + right click the folder and in the pop up menu, select "Open command prompt window here"
it's efficiency - not laziness
then with the phone connected via usb cable to the computer, in that prompt type this
adb push ROMNAME.zip /sdcard/
After a short wait, it showed a couple hundred megs worth of a file was transferred. I repeated the command again with the PHILZ recovery zip name and again, it showed completing the transfer.
Time to get to work.
From TWRP, I went to flash a zip, pointed to the PHILZ zip file and successfully flashed that, went back to the main menu and then told it to reboot back into recovery.
I was greeted with the snazzy PHILZ recovery interface.
I then told it to do a wipe for a new ROM install and then after that completed, went to flash a zip, pointed it to the correct version of CM this time and flash was successful.
Crossed my fingers and rebooted the device and SUCCESS! Up and running perfectly.
hopefully this helps those who find themselves in the unfortunate soft brick scenario or something similar that I was in.
Great stuff. I'm sure this saved a couple of lives. Comment bump for ya.
Sent from my LG-D802 using Tapatalk