Related
hi dudes can you help?
My desire hd stucks on htc logo when i start it... and also when i go to recovery mode to install a new ROM (when pressed power button and volume down key) it shows me a mobile picture with red triangle with "!" and can't go further... What should i do, so i install i new Android ROM... Thankyou for your replies
How exactly did this happen in the first place?
Secondly I think you should try to flash a new recovery from fastboot. I have forgot how to do it but that is the way forward. Somebody should reply with details on that
king_slavcho said:
when i go to recovery mode to install a new ROM (when pressed power button and volume down key) it shows me a mobile picture with red triangle with "!"
Click to expand...
Click to collapse
That is the stock recovery. Either you don't have a custom recovery installed or you haven't rooted & removed S-OFF.
Use [TOOL] Advanced Ace Hack Kit (UPDATED 25-10-2011) to root & flash a custom recovery.
how do i install it... as i came up to conclusion - i should copy the zip file into my mobile and then install it from recovery... but as i said when i start the recovery mode, it stucks on a mobile pic with red exclamation in triangle and here, i am stuck, so as further as i know i should flash it from PC... Can you explain me completly what should i do with this hack kit... Thanks for your replies
Or, how about you go to the Development Section, read through the guides, including the one I provided a link to and learn how to do it. Its not rocket science. If after reading through it you still think its too hard, sadly Custom ROMs aren't for you.
king_slavcho said:
how do i install it... as i came up to conclusion - i should copy the zip file into my mobile and then install it from recovery... but as i said when i start the recovery mode, it stucks on a mobile pic with red exclamation in triangle and here, i am stuck, so as further as i know i should flash it from PC... Can you explain me completly what should i do with this hack kit... Thanks for your replies
Click to expand...
Click to collapse
Download the hack it, and extract it if you need to. There will be a file called the 'Effen Manual' which you need to read before you do anything. It gives you instructions for Windows, OSX and Linux, so pick the relevant one.
It's really quite simply, just follow the guide, which involves running a script from the cmd or terminal, and wait for it to do its thing. Takes about 6-10 minutes on average.
Hope it goes well
hmm i read the effen manual done everything it says but one thing i cant do... Can't turn on the debugging mode because android does not start... Is there any other way to turn the debugging mode on?
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.
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Jesmuris said:
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try going into fastboot and flashing the stock rom from google.
gmaxpwnage said:
Try going into fastboot and flashing the stock rom from google.
Click to expand...
Click to collapse
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Jesmuris said:
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Click to expand...
Click to collapse
Ok, found out on the no command screen I can hold power and hit vlm up and it brings me to system recovery with these options. Reboot system, apply update from ADB, wipe data/factory reset, wipe cache partition.
Not sure what to do sadly
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Johnsonyc said:
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Click to expand...
Click to collapse
Ok thank you, trying this now will update:good:
Didn't work Will try other method
Jesmuris said:
Didn't work Will try other method
Click to expand...
Click to collapse
Sorry to hear this bad news Hope the other method work for you!
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I had a similar experience (kind of). I had issues side-loading 4.2.2 -> 4.3 on my N4. After it finished update and rebooted I got a black screen and nothing more. I ran through it and tried to update to 4.3 again, and then it worked.
Even though it worked I've been noticing issues with it. For example, I now can no longer uninstall anything. When I attempt to uninstall any app, the phone reboots. I'm backing up now with Titanium and am about to flash. I was hoping there would be a quick fix here, but such is life. Viva la impatience.
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
oneguy77 said:
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
Click to expand...
Click to collapse
This is what I eventually followed to get mine working. I just did scenario 2 and that worked perfectly for me, so far no issues, just having to get things back to where I had them before. The second link is actually more detailed. Just make sure you follow step by step. I guess i could have not done step D10 but wanted to make sure this route worked for me. Thank you again for those who pointed me in the right direction
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
FYI if you flash to stock android 4.3 and you have the 16 GB Nexus 4, make sure that after you re-flash you have the full 16 GB and not 8 GB (unless you want to re-setup your phone twice like me). If you get this problem you can wipe cache and data from recovery and voila, all of your free space is back.
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
zpilot said:
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
Click to expand...
Click to collapse
If this is what I think it is, I was having the same problem. If I went into Control Panel on my PC and it would say that the driver is failing to load. To fix this I uninstalled the driver, rebooted, reinstalled Google USB Driver from the Android SDK Manager, restarted, and all was well after that.
I really have no explanation for why this fixed it, or it didn't work before, because other than fastboot, everything was working flawlessly with getting my phone to communicate with my PC.
First off ive read almost every thread on the a500 in the past few days, ive downloaded the tools,came across alot of dead links, tried to follow them and i just cant get it to come back to life...my head is spinning trying to understand all this... ill explain what i know and all i have done so far...any help would be greatly appreciated
this is my dads a500 i did update it ota to the latest version of android stock for it a few months ago. he uses it every day
he was using it playing a game, it froze up, he tried a reboot...now it wont go past acer screen
in recovery i get the dead android guy with red exclamation point over him, if i dont switch the screen lock it will try fast boot 00.03.12 ics bootloader from usb...with no result
tried to boot to recovery with the update.zip on a newly formatted fat32 1gig micro sd card....and nothing was i using the right zip?
"Acer_A500_7.014.01_041.203.01_COM_GEN1_1333444043393_2fe1ad59_decrypted"
in apx mode...apx flash tool will recognize it...but i never get anything on the tab screen confirming it is in apx mode...no boot loader or messages at all
Ive tried to install a bundle with apx flash from blackthunder...it went through the whole install process...but no result, i dont know if it was connected properly and everything the same.
my though is my bootloader is messed up... so i guess my question is how can i fix it if i cant connect correctly through apx mode or recovery mode... did i do something wrong? not install something i should have?
i downloaded a500 manager and apx flash, ics root, sbcalc, babsector,
any help with be greatly appreciated
thanks Jim
I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?
toopty said:
I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?
Click to expand...
Click to collapse
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!
cgillie92 said:
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!
Click to expand...
Click to collapse
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.
toopty said:
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.
Click to expand...
Click to collapse
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.
cgillie92 said:
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.
Click to expand...
Click to collapse
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.
toopty said:
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.
Click to expand...
Click to collapse
I hope someone helps us out. I really cant afford a new one because the warranty is void. I was going back to stock because of all of the little bugs that need to be ironed out in roms. cause kit kat is around the corner hopefully and my problem virtually is the same i might have had my brightness on auto or something prior to that.
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.
Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
After following the instructions on the above link i was able to get fastboot status on my phone. It did not fully restore my phone however. I was able to flash twrp via fastboot. I was then able to boot into twrp and run the command at this link via twrp terminal http://forum.xda-developers.com/showthread.php?t=2451696
Thanks to everyone for all your help.
toopty said:
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.
Click to expand...
Click to collapse
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/
cgillie92 said:
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/
Click to expand...
Click to collapse
Ignore all the message, unplug you phone get ready to type the command, plug it in and immediately press enter to run the command. it took some trial and error, and i had to use this other post to help me out. I actually got fastboot working first, then used this post to http://forum.xda-developers.com/showthread.php?t=2477595 to get download mode working, and to flash twrp recovery. After that i used this post to run the command line from with twrp. http://forum.xda-developers.com/showthread.php?t=2451696 . I didn't have to flash the factory tot to my phone, but i have that option now because download mode is working. This process will work, there is hope for you getting your phone back. I'm fully recovered. I decided 12B is not worth it in the mean time, but if you want 12B you need to flash the factory tot and then upgrade. There is a way to root 12B, but as of this time you are unable to get Custom Recovery on it.