Acer a100 bricked, any chance of recovery? - Acer Iconia Tab A100

Acer Iconia a100
i Bricked it, it sits at the acer screen. no signs of loading. It responds to all of the vol + power +
scape combinations. I get bootloader error when i try that combination, the sd update just hangs there i
grabbed flexreaver rom and renamed it update with the file type being a zip and still no cigar.
I wanted to run the fastest most bare rom as possible i think the problem was that i did NOT have the
bootloader unlocked. I tried one idea where you run somekind of batch file and on my tab itself it
stated that the bootloader was NOT unlocked. i have no idea where to go from here. When i go into usb
mode or db it does not connect with the computer i cannot see or add or remvoe file, but i can connect
with msdos to run batches.
I have spent hours looking for a solution and found help only in outdated links, foriegn languages
and a500 tutorials. I have an acer A100. Any help offered to me is much appreciated but if you are going
to help me please be thorough and leave me alot of details please, i do not have the understanding
or the command it takes to successfully unbrick my tablet. So.. Any ideas?

kungfaux17 said:
Acer Iconia a100
i Bricked it, it sits at the acer screen. no signs of loading. It responds to all of the vol + power +
scape combinations. I get bootloader error when i try that combination, the sd update just hangs there i
grabbed flexreaver rom and renamed it update with the file type being a zip and still no cigar.
I wanted to run the fastest most bare rom as possible i think the problem was that i did NOT have the
bootloader unlocked. I tried one idea where you run somekind of batch file and on my tab itself it
stated that the bootloader was NOT unlocked. i have no idea where to go from here. When i go into usb
mode or db it does not connect with the computer i cannot see or add or remvoe file, but i can connect
with msdos to run batches.
I have spent hours looking for a solution and found help only in outdated links, foriegn languages
and a500 tutorials. I have an acer A100. Any help offered to me is much appreciated but if you are going
to help me please be thorough and leave me alot of details please, i do not have the understanding
or the command it takes to successfully unbrick my tablet. So.. Any ideas?
Click to expand...
Click to collapse
I think we need a lot more information in a clear manner.
From the beginning, what did you do? Do you have ICS or HC? Rooted? Did you try to unlock the boot loader? Try to install a recovery?
What batch file did you run, what was it for?
At what point in all of those answers did it stop booting?
Have you hard reset?
You say the computer can not see it but say you can run batch files on it, which is it? Are they seeing it or just running anyways? What boot loader version does it say in the upper left corner?
All if this information provided clearly will tell us exactly where you stand and if it can be corrected.
Tapatalked from my Galaxy S II.

boot loader v0.03.06-ics:starting fastboot usb download..
I had the tablet rooted and i had not updated to the OTA update.
i have only tried the vol+power combos and i tried to rename a rom to update.zip so i could do that update reboot thing and it just hangs..i tried a pin the reset hole still nothing..
i had tried zeronulls bootloader unlock at that point was when my tablet bricked.. since then ive tried to run fastboot_recovery but it doesnt work. i can connect my device with usb and it will respond to certain batches acer a100 unbrick (a100-recovery-win/a100-push-tools) but i cannot access any of the files on the sd card through my computer.

kungfaux17 said:
boot loader v0.03.06-ics:starting fastboot usb download..
I had the tablet rooted and i had not updated to the OTA update.
i have only tried the vol+power combos and i tried to rename a rom to update.zip so i could do that update reboot thing and it just hangs..i tried a pin the reset hole still nothing..
i had tried zeronulls bootloader unlock at that point was when my tablet bricked.. since then ive tried to run fastboot_recovery but it doesnt work. i can connect my device with usb and it will respond to certain batches acer a100 unbrick (a100-recovery-win/a100-push-tools) but i cannot access any of the files on the sd card through my computer.
Click to expand...
Click to collapse
Go to where it says download protocal then in the folder with adb and fast boot from those zips you downloaded open a command prompt, CD to that folder then type
fastboot oem unlock then get ready for the volume keys.
You missed the unlock that's probably why it got jammed up.
So....find the folder you unzipped the boot loader unlock stuff to, copy it to c:\unlock
Open a command prompt, type
cd c:\unlock
Then type
fastboot oem unlock
Place one hand on the tab so you have a finger on each volume button
Hit enter
On the tab press volume up then volume down (furthest from lock switch then closest to lock switch) as soon as the unlock screen comes up.
Gotta be quick if you miss it try again.
Tapatalked from my Galaxy S II.

ha! youre amazing!.. i got it.. ok, now then it still hangs at the acer screen but now it says bootloader version 0.03.06-ics (unlock mode)
what do i do next?

kungfaux17 said:
ha! youre amazing!.. i got it.. ok, now then it still hangs at the acer screen but now it says bootloader version 0.03.06-ics (unlock mode)
what do i do next?
Click to expand...
Click to collapse
Maybe hard reset or just install a custom recovery and then install a custom rom or something lol limitless possibilities now.
Tapatalked from my Galaxy S II.

Acer A100 BRICK NEED ADVICE

marvz_tech said:
Acer A100 BRICK NEED ADVICE
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27938361
Brick thread, good place to browse.
Tapatalked from my HTC DNA - ReVolt

Related

[Q] HTC Desire Stuck at Why so serious?

hi i have used evo3 on my htc desire to root and then used alpharev and boht said succussfull. Now phone starts and only shoes joker and written why so serious? doesnt go further at all. any help please
Regards
got a bootloop.. try running an RUU file (this will flash back to stack, get rid of root)
then try to root again, just a different method?
hope this helps!
how to flash with ruu if your phone is stuck not even being detected by PC. any detail please thanks regards
faisal_sherry said:
how to flash with ruu if your phone is stuck not even being detected by PC. any detail please thanks regards
Click to expand...
Click to collapse
First of all: be sure you know what you're doing. The below listed solutions might help but might also end up bricking your phone dead.
If you can enter fastboot (back while powering on the phone) and if you have a nandroid backup, you can try to flash it back using the fastboot flash command.
OR
It's possible to run the RUU update while in fastboot or hboot usb mode (back button while powering on the phone) I had the modified usb drivers installed http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install, not sure if that is needed - but the original drivers didn't work very well with my setup in general: Win7 x64 , also I uninstalled HTC Sync.
OR
If that fails, you can try to extract the rom.zip from the RUU and flash it manually (help on extracting http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html ) JUST DON'T USE THE ROM FROM THAT TUTORIAL, THE LINK IS JUST FOR REFERENCE ON HOW TO EXTRACT THE rom.zip
The offcial RUU are in this thread, just BE SURE TO USE THE CORRECT ONE http://forum.xda-developers.com/showthread.php?t=695667
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom.zip
@quanchi, thanks for your help i'll try and let you know tomorrow thanks again
Regards
hi i have tried the method putting phone in fastboot mode pressing back and power phone was detected and then flashed with this rom 'RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed'' and it was successufll now my phone is not turning on when i press power it vibrates but nothing on the screen but good thing is when i connect the phone with pc it still detects it its not brick yet i think any help
Regards
faisal_sherry said:
hi i have tried the method putting phone in fastboot mode pressing back and power phone was detected and then flashed with this rom 'RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed'' and it was successufll now my phone is not turning on when i press power it vibrates but nothing on the screen but good thing is when i connect the phone with pc it still detects it its not brick yet i think any help
Regards
Click to expand...
Click to collapse
Is your phone SLCD? I reckon you may have flashed an incorrect RUU, in which case you'll need to get a more up-to-date one and flash it again. In case that's the most recent one for T-Mobile, you'll need to make a gold card and then flash a generic RUU. Hope that helps.
hi thanks for your reply i don't know what is slcd? and let me tell you the stat of the phone now
when i press power phone vibrates i can see button lights on the phone but nothing on the lcd screed. Phone is not going in boot mode when i press back and power nothing happens, volume up and power nothing happens. Phone is being recognized in device manager as a usb mass storage and i can see battery light on the top of the screen as well. I dont know what is the real state of my phone and what do you call it but its a t mobile UK phone that's what i know and what should i do now thanks
Regards
SLCD is a type of display present in some Desires, earliest Desires had an AMOLED display. You most probably flashed your SLCD Desire with RUU prepared for an AMOLED Desire, hence the display problems. Search the forum for "SLCD BRICK". Your phone should be able to enter fastboot/hboot, but doesn't display anything because the display handling is screwed up. Before trying to resolve your situation BE SURE TO READ ALL THE INFO ON SLCD UNBRICKING.
I have no experience with SLCD models so can't help you much on the subject, but there are numerous threads on xda detailing dealing with this particular issue.
I don't want to sound rude or holier than thou (as I had my share of bricks and semi bricks) but I did write that you should make sure you get the correct RRU...
best of luck
Sent from my HTC Desire using XDA App
hi thanks for your reply i'll try n post the result here
Regards
So here I will describe what I did to solve the exact same issue.
Remove the battery from the phone
Copy the proper RUU file to the root of my SD card naming it PB99IMG.zip
Insert battery
Power on phone holding the power and the back buttons until the fastboot menu opens
Choose recovery
Then it will go through a bunch of stuff and ask you if you want to flash the file you put on the SD card, I said yes then a few minutes later Bobs your uncle I was back to factory.
faisal_sherry said:
hi thanks for your reply i'll try n post the result here
Regards
Click to expand...
Click to collapse
Faisal, it seems apparent that your device is an SLCD Desire. When you put Alpharev on it, it did S-OFF and your boot got corrupted for some reason and looped. When you ran the RUU (which was incompatible for your SLCD, and actually meant for an AMOLED Desire), you effectively unrooted it, though not restoring it.
Check my thread for a similiar problem.
If you had made a Goldcard earlier, you're in luck. You can restore your device with a generic SLCD RUU available for your device, by either running the RUU or by flashing the rom.zip from the RUU.exe file (Tip. This file gets extracted to %TEMP% folder when you run an RUU)
Things you need to know before you try solving your problem:
Know how to use adb from the command prompt,
Search for the links to shipped-roms site containing the list of Bravo (Desire) ROMS
How to create and use a goldcard
How to navigate to the temporary folder of your Windows PC
How to turn your device on into Recovery mode and Fastboot without seeing the screen
Simple search on XDA can unravel these simple mysteries.
Now, the steps to go about solving your problem:
Find out if you have a generic unbranded HTC Desire, or a branded one. A branded Desire has a special Code which prevents you from flashing a ROM meant for any other brand and also blocks a Generic RUU. If you're from India, it is branded with HTC Asia_India. If you're unbranded, things are looking much easier for you, as generic RUUs for SLCD are easily available.
Check if you have a goldcard (A goldcard is a special microsd card you made while your device was in working condition. It will allow you to restore your device using a generic RUU or an OTA)
If you dont have a goldcard, you might try to see if Recovery can be booted up. Poweroff phone, then power it on by pressing Vol- and Poweron key, then wait 30sec and press Vol Down and Poweron button again. At this time, phone gets detected in Windows (as shown by the icon in the bottom right of taskbar and a notification sound.
Type:
Code:
adb devices
If this displays a code SH**** after "List of devices", you're in luck. You can issue an adb command and get a CID of your device, following which you can create a goldcard.
After creating a goldcard, it will allow you to run a generic SLCD RUU. Check my thread for a latest RUU.
If you dont have a goldcard, and adb doesnt show the device in Recovery mode, it means Recovery is corrupted too. In this case, Power off device. Then Poweron by pressing Back key and Power on key. Again try adb devices command. If it shows the device, follow the steps of previous step.
You can also create a goldcard by putting your microsd card into a friend's phone and following the steps needed to create a gold card
If adb doesnt show your device in either Fastboot (previous step) or in Recovery, then you're in trouble. The only way to unbrick your softbricked device is to get a Generic RUU for your device (Check shipped roms site, or search XDA), and flash it. There is also a method if you have the original OTA zip for your device. Check teppic74's posts on XDA for this method.
If you have an Indian Desire, you're done for as I found out. If you dont have a goldcard for an Indian Desire, or the OTA zip, you have no option than to return it to HTC. Dont worry about Warranty being lost if it is a new phone. HTC has to repair it according to their Warranty policy.
Goodluck. I've summarized all methods available to unbrick an SLCD. For more details on any one method, try searching with the appropriate keywords from my post. It's all on XDA.
@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
"switch off phone. press and hold volume down. press power. release volume down after 5 seconds. wait for 30 seconds. press volume down. press power. the phone should vibrate. wait 40 seconds. the phone should be in recovery."
pc detects the phone but when i run ruu it doesn't find the phone and i have OTA downloaded as well and i have copied to micro sd but i dont know how to use this OTA. i'm sorry for being very basic
Regards
faisal_sherry said:
@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
"switch off phone. press and hold volume down. press power. release volume down after 5 seconds. wait for 30 seconds. press volume down. press power. the phone should vibrate. wait 40 seconds. the phone should be in recovery."
pc detects the phone but when i run ruu it doesn't find the phone and i have OTA downloaded as well and i have copied to micro sd but i dont know how to use this OTA. i'm sorry for being very basic
Regards
Click to expand...
Click to collapse
@Faisal,
No prob. Everyone is a newbie at the beginning!
But, you need to search and find out some things on XDA, and there are a lot of newbie centric guides over here which explain procedures step by step..
You need to do these by yourself though:
1. Install Android SDK. It just involves downloading the setup file, running it, and finding out where in Windows it has been installed. In the main installation folder, there is a Folder called Tools. You need to open a command prompt in that folder and run adb.exe for most of the procedures. Follow this guide to install the SDK.
2. After you have the sdk installed, boot your phone into recovery using the procedure you quoted. As you said, the phone will be detected in Windows. At this point, run the following command from a command prompt in your tools folder.
Code:
adb devices
This will output "List of devices" followed by a code starting with SH. If it does, you're in luck. You can now create a goldcard, and proceed. Follow this guide for this.
3. If the "adb devices" does not show any devices (in recovery/Boot mode), and you dont have a goldcard, you've run out of luck, pal. Honestly, no one on any forum has solved the issue with this combo.
There would still be a solution, if you have the RUU. I dont see why your RUU does not run. Try to run it in one of the following modes.
a. Switch off phone
Switch it on by pressing Back key followed by Back+Power key, then slowly releasing Powerkey while keeping Back key. This is the bootloader mode.
b. Recovery mode. Power off, power on by Vol down + Power key, then slowly release Power key. After 30 sec, press Vol down once, then power key once. Wait 1 min and see if pc detects device. Else press power key once again.
In either of these modes, the RUU you downloaded should down. If it is the incorrect RUU for your location, it will give a customer id error. If it has an incorrect bootloader version, it will show a Bootloader version error. In either of these cases, try the newest generic SLCD RUU from shipped roms. If this still gives one of the above errors, your phone is a branded phone. In this case, you WILL NEED a gold card to work.
Note that if adb devices shows your phone, then you can create a goldcard at this point.
If adb does not show your devices, and the latest generic RUU does not run, and you cant find a correct RUU for your device, then tough luck. I am yet to find a solution to this problem. Return it to HTC.
faisal_sherry said:
@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
Click to expand...
Click to collapse
Yes, you need to have HTC sync installed for the drivers. But the HTC sync main program should not remain in the system tray (bottom right). If it is, close it by rightclicking and Exiting.
The problem with what devin mm said is that an SLCD desire doesnt show anything on screen if bricked. Yet, recovery may be selectable for some, without seeing anything. But if you ran the RUU, then most probably the recovery itself is corrupted and selecting a zip file on memory card wont be possible at this point.
Sorry that I wont be able to follow this thread for the next few days. I'm travelling, and since my Desire is with HTC repair centre, no Net. Hopefully, someone else on XDA can help out with any more qns..

Bootloader working but can't load recovery mode to restore ROM

Hi all,
Hope someone can help, I have a desire HD that has some issues.
Long story short the phone was acting up and was flashed with a non official ROM. It was working originally but after about a week it started acting up, with apps force closing, phone crashing altogether etc.
I am trying to get the phone back to a state that Vodafone in Australia will be able to warranty the phone in.
The current situation is that when the phone turns on, it'll load straight to the bootloader/hboot. Recovery mode does not work - it dumps you in to fastboot menu and fails to load.
System restore from boot menu does not work either, and there is no rom at all so USB debugging is a no go, and there appears to be no way to flash the ROM.
Any ideas? Any help would be greatly appreciated.
Thanks
Sent from my GT-P7100 using XDA App
Use adb / fastboot to push a new recovery to the phone (I hope you left USB debugging enabled).
Sent from my Ericsson T39m
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Sent from my GT-P7100 using XDA App
CrystalCastle said:
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Sent from my GT-P7100 using XDA App
Click to expand...
Click to collapse
ooh i tested it in my DHD and don´t works...how can be possible that don´t works adb parameters, but fastboot commander works perfectly??
maybe we have anything that works badly in our PC´s.. i´m in it...
ei crystal!! has you tested with FASTBOOT COMMANDER? if you download it you can flash a new recovery from this tool... its intuitive...
you only must to download the tool
download the recovery (lastest CWM in the DHD android development forum)
put the file in the paragraph that says "RECOVERY:not file set" and then push FLASH IT"".maybe you enjoy...
remember to put your device into boot loader
CrystalCastle said:
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Click to expand...
Click to collapse
How did you check to see if adb shell can see the device?
Run an pb98.img from the bootlaoder
Sent from my Motorola Startac running Atari 2600 software!
Mr_JMM said:
How did you check to see if adb shell can see the device?
Click to expand...
Click to collapse
adb get-state
result:
unknown
Code:
adb devices
But this does depend on you having previously ticked USB Debugging option before you had all these problems (no way to check now without being able to boot the phone).
If this fails you may have to try the previous suggestion of putting a PD98IMG on your sdcard then going into fastboot on the phone.
Mr_JMM said:
But this does depend on you having previously ticked USB Debugging option before you had all these problems (no way to check now without being able to boot the phone).
If this fails you may have to try the previous suggestion of putting a PD98IMG on your sdcard then going into fastboot on the phone.
Click to expand...
Click to collapse
Currently there is no Rom on the Phone. Just put PD98IMG.zip on the SD card which seems to be updating. Does it normally take a while to Update all the Sections?
Can take anything from 5 to 20+ minutes.
Seems to be taking ages to even get past [1]. Is that normal? Hasn't done anything. It says "Updating" yet I'm still yet to see it get past "[1] BOOTLOADER"
Just to confirm...
1. Turn phone off
2. Put PD98IMG file onto ROOT of sd card
3. Use vol- and power button to get to Fastboot
4. Scroll and select Bootloader (HBOOT)
(might automatically do last step when you boot phone)
Phone will show a message to say it is looking for the file then unpack it and install.
Mr_JMM said:
Just to confirm...
1. Turn phone off
2. Put PD98IMG file onto ROOT of sd card
3. Use vol- and power button to get to Fastboot
4. Scroll and select Bootloader (HBOOT)
(might automatically do last step when you boot phone)
Phone will show a message to say it is looking for the file then unpack it and install.
Click to expand...
Click to collapse
Confirmed dude. Doesn't seem to be doing much though. It has been stuck on "updating BOOTLOADER". It has trying to update it for more then 30mins now
It has a big list of 12 things it wants to update however it hasn't moved past the first file "BOOTLOADER" in over 30mins.
Did you confirm the MD5HASH of the file before putting it on the card?
Could you put a link to where you got the file from please?
http://forum.xda-developers.com/showthread.php?t=905003
Thank you.
Are you still connected to the PC? If so disconnect and try again.
Did you confirm the MD5HASH?
Have you got another SD card you can try? If not, reformat the current one and put the PD98IMG file on it again and try again.
The Device fails to even turn on now dude. Thanks anyway man
!!!???!!!
Damn. Do you just get the orange flashing light when you try to turn the phone on?
Take out SD Card and try.
If nothing works the bright side is you can send it to HTC and say "I woke up, turned it on and it's dead". Chances are they'll never be able to tell how it happened.
Many people did this when the Clockwork recovery bug bricked loads of phones.
Sorry but stay positive. Always a sliver lining.
Thank you
thanks for your great guidance to get back to recovery. I followed your tips and made it.
thanks a lot once again.
SERGI.3210 said:
ooh i tested it in my DHD and don´t works...how can be possible that don´t works adb parameters, but fastboot commander works perfectly??
maybe we have anything that works badly in our PC´s.. i´m in it...
ei crystal!! has you tested with FASTBOOT COMMANDER? if you download it you can flash a new recovery from this tool... its intuitive...
you only must to download the tool
download the recovery (lastest CWM in the DHD android development forum)
put the file in the paragraph that says "RECOVERY:not file set" and then push FLASH IT"".maybe you enjoy...
remember to put your device into boot loader
Click to expand...
Click to collapse

[Q] Did I brick my desire?

Hi.
I was recently experiencing some problems with my desire and I believe that I might have rushed into bricking it.
I woke up the day of the bricking. I had just installed the newest version of GingerVillain (version 2.4). My phone had run out of power the day before so I started recharging it. After it had charged for a couple of hours I went to the market to update some apps. During the update my phone suddently rebooted. I thought that it was nothing and went back to the market and continued updating. A few minutes later it rebooted agian. It kept on rebooting with less and less time in between after each attempt until it chose to reboot at the splash screen continuesly.
This is when I thought of starting the phone in recovery and do a NAND restore. As I tried to enter the recovery mode the phone froze at a black screen. I pulled out the battery and retried a couple of times without success.
I read a little on the internet about ADB and tried doing some stuff but I kept on getting errors when running commands in the tools directory. At this point I was getting desperate because I needed the phone to work as I was expecting an important call. I tried flashing a new RUU (through the installer on my PC) while the phone was in fastboot (but without using any ADB and CMD stuff). After this installation almost had finished I got an error saying that the version of the rom wasn't the right one for my phone and the phone shut off.
Since then I haven't been able to boot it into bootloader or even boot it at all. Whenever I hold down power + volume down nothing happends and if I try only pressing the power button the phone vibrates and other than that nothing else happends. Not even the screen turns on.
I since then set up ADB and got it working. I then tried to see if the phone was still able to fastboot through the following commands:
Code:
adb devices
and
Code:
fastboot devices
but found that this was not the case.
Whenever the battery is in the phone though, the bottom of the phone starts to get warm, a little like it's actually using the battery to perform some actions or something. I was also able to recharge it through my computer.
I really need a phone and as it seems I have got my hands on a spare one, but only for a limited time. I'm really thinking of handing it in to the HTC Concept Store so they can send it to the repair department and hopefully get it back as fast as possible.
Its seems.. S-LCD Brick
try This
http://forum.xda-developers.com/showthread.php?t=748498
or
http://forum.xda-developers.com/showthread.php?t=831734
Ohh dude! I BELIEVE YOU MIGHT JUST HAVE SAVED MY LIFE! TY! TY! TY! TY!
My stationary just killed itself because of the hot weather and a little bit too much work. If I was going to hand in my phone and they couldn't repair it since I had "destroyed" it, I would be forced to buy a new one, and with that I wouldn't be able to afford new components for my stationary.
I will get right on with trying this method as soon as I get home and then I will give feedback asap. It will probably be the most fun "digging in the dark" I will ever do if it turns out to work.
I was almost sure I had killed my beautiful phone, and with it only being a couple of months old that would have been a pain in the ass.
Once again TY so much!!
I have been at this for almost 4 hours now and still no result. I believe the guides could have been more noob friendly. I've been to hell and back reading all the kinds of guides out there to get it all to work and now I'm tired and believe I won't be able to fix this, or atleast doesn't have the capacity to keep on trying.
I pretty much believe that I had this SLCD-brick, but trying out different RUU's is killing me inside and stealing my time. I'd rather just hand in the phone and recieve it as it was from the beginning again to start all over.
Trying to repair a smartphone with a blackscreen is is not something I have the capacity to do. Besides I have my recently deseased stationary computer to take care of as well.
I do have a goldcard, pushed the PB99IMG.zip file to my /sdcard/ through adb and tried starting up fastboot and do as described here.
But somehow I did not find any changes to the problem and the guide itself was wierdly written although the only guide I could find on this problem.
But now I'm giving up. I seriously just hope they will repair my device at no cost.
Regards,
Me
Man.. what happen when you connect your mobile to PC.. is it showing android device and under that bootloader interface.. dont lose hope... lets try some steps...
connect your mobile to PC and see in your device manager.. can you see android.. if yes than your driver are installed...
than remove the phone from pc.. take out the battery.. and put back battery.. and start by volume down and power.. and than after 10 sec just press power button again.. and connect to pc again... and cehck device manager.. and you should see the same if not.. than install your adb driver.
Point is.. install ADB driver.. when you are on hboot screen.. as well fastboot screen..
Than your RUU will detect your phone.
Well I tried all the steps for this. I can see the phone when booting it with the following combos:
Code:
1: Volume down + Power
2: Power
1: Volume down + Power
2: Volume down
3: Power
When using the first method I should as far as I can understand myself enter fastboot and the other one is recovery. Even when running the fastboot devices / adb devices commands in ADB it tells me what state my devices in, that is either fastboot or recovery. So that's for certain.
I tried running the following RUU when I had connected my device with fastboot:
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
The RUU found my device and I ended up with a 140 Error. I read in some guide that this error could be to blame of different windows drivers so I tried grabbing the rom.zip from the RUU (from Temp folder) and renamed it to PB99IMG.zip and put it on the phone. As I couldn't get access to my SD card since I can't see what's on my screen in fastboot and recovery mode I used:
Code:
adb push PB99IMG.zip /sdcard/
with the PB99IMG.zip placed in my tools folder for the transfer. It completed and now the PB99IMG.zip should be placed on the root of my sdcard.
As a notice I live in Denmark and the above RUU should as far as I can understand be the one I need and should as well be SLCD compatible.
When I try to trace the steps in the "not able to see your screen guide" placed here I get none of the desired outcomes:
http://forum.xda-developers.com/showthread.php?t=880268
I find the guide a little but confusing though. When to use the right commands to trace through a black screen fastboot/recovery and stuff isn't really "noob"-friendly.
When I tried using the following command I didn't get the desired result either:
Code:
fastboot oem gencheckpt
Which should return a HTC_<number> that could tell me whether my phone is branded or not, but instead resulted in an error. As far as I can remember I did make my sdcard a goldcard when I rooted my phone, without knowing whether I would need it, so this number should be irrelevant. So I kept on going at this point.
I have basicly tried everything that I can find guides for and have traced all the steps in detail as far as I understand the guides anyhow. I feel like at a dead end. I am having doubtsg whether the PB99IMG.zip is run when I boot my phone.
Having a clean slate (but still the PB99IMG.zip on the sdcard I have now tried the following:
Code:
Volume down + Power
Windows reported a connected Android 1.0 device and the Android Bootloader Interface.
Power once more (should now be in fastboot)
fastboot devices
confirmed the above, but using ADB devices only return a result if the phone is in recovery mode
So far so good..
I'll give this one more day which will be when I return home at 17:00 today. Then I'll head to tech support at my HTC Store.
Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..
jhonybravo4u said:
Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..
Click to expand...
Click to collapse
Okay. I'll try this and should I run it while in recovery like I did with the other one?
Does it matter if my SD card is out of the phone?
EDIT 1:
I tried with the sdcard out of the phone and with the RUU installed through windows. I now see a HTC Logo on the screen.. and an installing bar below the logo.. Seems like you were my divine interception mate.. ty a lot. I will write once the installation is done.. whether or not it succeeds.
EDIT 2:
My phone is now working. Booted with HTC Sense and a pin code request. Currently setting it up.
I guess I should now be able to re-root it again and get back to the state I was in before I SLCD-bricked it.. or what?
And in what way do I easiest remove that PM99IMG.zip file from the sdcard..? I booted my phone without the sdcard in it to avoid it running the PM99IMG.zip file..
One little question more.. I don't have any phone signal.. could this be to blame for the radio? I can connect to wifi though.. or can I simply run that other RUU I used earlier with the bootloader error to get back my signal?
So happy right now..
EDIT 3:
Nvm. I tried shutting down the phone, put in the sdcard, boot it up again. I found that the ADB push command on that PM99IMG.zip file didn't work. The file wasn't there.. and I suddently got back my signal. Only question is, can I now re-root it again and get back to my previous state without any problems?
Yes Ofcourse you can re root it.. with Unrevoked rooting wont be a big problem... and as soon as you root... just take a nandroid backup from it and be safe..
Enjoy the victory you earned... .. ;-)

[Q] Help desperately needed - Galaxy Nexus not booting after installing Jelly Belly!

I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
bluroot said:
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
Click to expand...
Click to collapse
the proper term to use here is bootloop
ur phone bootlooped and u need to flash back the stock firware via odin
go back in the dev section and find somethng relatd to odin
remmbr bfre flashing any rom u shud always backup ur rom via clockworkmod
u must have done something wrng while flashng jellybean mod...take the steps crrctly
EDIT:- http://forum.xda-developers.com/showthread.php?t=1827685
heres the link to fix ur phone
properly take the steps plzz
bluroot said:
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
Click to expand...
Click to collapse
Are u able to boot into CWM recovery, Power and both volume up and down?
garner said:
Are u able to boot into CWM recovery, Power and both volume up and down?
Click to expand...
Click to collapse
When I do, I have that "Downloading..do not turn off the target!" message. Why this - I did remove the supersu file, although I think I left my clockworkmod file on the root because now you have to re-flash that every time you use it. Now I have no option other than "Start" - any chance of breaking through now?
bluroot said:
When I do, I have that "Downloading..do not turn off the target!" message. Why this - I did remove the supersu file, although I think I left my clockworkmod file on the root because now you have to re-flash that every time you use it. Now I have no option other than "Start" - any chance of breaking through now?
Click to expand...
Click to collapse
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Zepius said:
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Click to expand...
Click to collapse
Do you mean that I need to continually rock the Volume key up and down while holding the Power button? Volume Up with Power put it in boot mode, and when I tried rocking it a couple of times I got the same result. It I understand you correctly, the idea sounds tricky. Is this supposed to work on a Galaxy Nexus?
press and hold both ends of the volume button and the power button... its really not that hard.
Zepius said:
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Click to expand...
Click to collapse
What I really should have done was slow down, or quit while I was ahead to get some rest last night! I had researched the root process for my phone ad nauseum, which I know is why I succeeded at getting ClockworkMod safely installed. By the time that was done I was tired, but I counldn't stand the thought of living without my files loaded on my phone - I was in the bad state of needing too much to complete what I had intended to do. I see I had the wrong impression that ClockworkMod would take care of the whole process once I had that working, guess it didn't. When you've been through the process of installing a hundred versions of Windows and Linux on a PC, which never needs to be pre-wiped (the new OS does that), who would have thunk it's that much different with a phone computer?
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
This is another thing I never would have guessed without being told specifically, that it's even possible to hold down both ends of a rocker switch and have it do a different function - I tried this, and now it works! I had used my PC to root my phone last night, and right now I'm at work, where there will be time to go through this in a couple of hours. I took a brief look at the tutorial recommended by Zepius, and am wondering if I am set to proceed. I plan on using my work PC, not the one at home with the drivers I used to root my phone. Nobody else uses it and I have never used it for anything phone-related. Can I presume any drivers which I'm warned should be uninstalled would be on the PC which is used, and not the phone?
bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
Sorry, I had to work, but now there's time and I thought I would try my work PC, which is virgin (so to speak) of mobile devices and drivers. It's a Windows XP system, and right now it's not looking good because when my phone is plugged in, there isn't a "Portable Devices" or "Mobile" category under Device Manager. Do I have a better chance of this working on my home Windows 7 system?
bluroot said:
Sorry, I had to work, but now there's time and I thought I would try my work PC, which is virgin (so to speak) of mobile devices and drivers. It's a Windows XP system, and right now it's not looking good because when my phone is plugged in, there isn't a "Portable Devices" or "Mobile" category under Device Manager. Do I have a better chance of this working on my home Windows 7 system?
Click to expand...
Click to collapse
I guess that's a never-mind, I should have had my phone on! It's in Fastboot mode now, but I still don't know if what I see in Device Manager is good for what I'm trying to do. No portable device, phone, nor galaxy nexus, but what did change is I have "Broadcom Nextreme 57xx Gigabit Controller" appearing under "Network Adapters". Is this a problem to be dealt with differently when your phone is bricked?
bluroot said:
I guess that's a never-mind, I should have had my phone on! It's in Fastboot mode now, but I still don't know if what I see in Device Manager is good for what I'm trying to do. No portable device, phone, nor galaxy nexus, but what did change is I have "Broadcom Nextreme 57xx Gigabit Controller" appearing under "Network Adapters". Is this a problem to be dealt with differently when your phone is bricked?
Click to expand...
Click to collapse
1) your phone is not bricked. dont call it that
2) best way to check if your drivers are installed correctly
open a command prompt in the folder where your fastboot.exe is and type: fastboot devices
if you get a device ID, your drivers are setup properly for fastboot
3) at this point, just return to stock: http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
1) your phone is not bricked. dont call it that
2) best way to check if your drivers are installed correctly
open a command prompt in the folder where your fastboot.exe is and type: fastboot devices
if you get a device ID, your drivers are setup properly for fastboot
3) at this point, just return to stock: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
I got a device ID (long string of characters) on that fastboot command, but I'm still concerned that my phone won't talk to Device Manager at all. Windows 7 doesn't pop up a connection window when it's plugged in, should that be expected?
What I mean by "not talking to Device Manager" is that the only item under Portable devices is just E:\ - no device listed here! The tutorial in your signature hinges on there being a device listed "without thde yellow exclamation point", for the installation of new drivers, therefore I don't know how to follow it from here. The adk drivers which were used to root my phone (they were good, the problem began when I tried to flash a rom and missed a step or three) are stil there, but I'll replace them if I can find a process which can talk to my phone in it's present state.
On a side note (and only because it held me up in responding tonight from my Windows system), is this site partial to Firefox? I am able for the first time to login, and I wonder if it isn't because I quit trying to through my Windows 7 system. It has only Windows IE, and Chrome (which couldn't even browse this site). I am currently on my Ubuntu system with Firefox.
good lord... you have a device ID so just use the fastboot commands... start at part D
Zepius said:
good lord... you have a device ID so just use the fastboot commands... start at part D
Click to expand...
Click to collapse
I said much the same myself.
For the fastboot devices test, I have a string of characters, but no device name, only "fastboot" on the single output line with those characters. Is this a valid device ID?
"...just use fastboot" Ok, but how? Should (can I) even do this use fastboot to transfer files to my phone under it's somewhat anonymous status with Windows? Since last night's fiasco nothing was named under "Portable Devices", only "E:\" was displayed. I have no graphical display in the file manager, so how am I supposed to transfer the necessary files to the root of my phone? I don't even see a way of addressing it to install drivers now.
I will need drivers because I attempted to follow this tutorial (which doesn't account for what I am (not) seeing on my system. I got as far as uninstalling the good drivers which I used last night in favor of what was offered for use with the tutorial, and now Device Manager doesn't even have a Portable Devices category. The "Universal Naked Driver" was to replace my uninstalled drivers, and interestingly the contents of it's expanded folders don't even contain fastboot (the adb package which I used last night did). In light of this, how am I supposed to have even fastboot?
I hate to be a PIA about this, but I guess I'm more a n00b than was presumed in this tutorial - it's either that or my situation really is too different that I can use it as is. Could I please get a few clues in light of what the tutorial doesn't address? Do I have any means of installing anything and transferring files with my device-PC communications as they are, and if so how can I do it? I'll give it a run if I understand how.
Thanks.
Zepius said:
good lord... you have a device ID so just use the fastboot commands... start at part D
Click to expand...
Click to collapse
I see now that Part D calls for flashing JO03C from my PC, not the device root, ok.
Also, after rebooting my laptop, the E:\ is back under Portable Devices in Device Manager. When I double-click this I get the statement
Device: Portable Devices
Manufacturer: Generic-
Location: on UMBus Enumerator
I don't think this looks better than the Microsoft default, but is it good enough for what I need to do?
I still have the driver package android-sdk-windows, which contains adb and fastboot, so perhaps I should just use this according to Part D and see what happens?
bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
Seriously I respect the fact that your a noob we was all here once but if it your device is boot-looping all you need to do is the above
garner said:
Seriously I respect the fact that your a noob we was all here once but if it your device is boot-looping all you need to do is the above
Click to expand...
Click to collapse
Good god, I never should have read Zepius's tutorial - I didn't need my PC at all! If I understood what bananagranola had said, I could have saved a lot of time!
Oh, no, now I can't connect with the server!
Could I have possibly lost my radio from what I did earlier? I was able to boot up, and I was upgraded to 4.2.1 when I did the data wipe. Starting over, I should have had a prompt to connect with gmail and download my contacts, but this didn't happen. My People app is unpopulated, so I chose to connect to "sign into an account". While I am sure of my login input, it didn't recognize this, and then the process ended with a "couldn't finish - couldn't open connection with the server" error. Any clue where to go from here?
Some standard apps are missing too, including the Play Store app!

A bit harder than a soft brick

Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
mikla90 said:
Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
Click to expand...
Click to collapse
hope you can access fastboot. if yes you can install recovery and ifwi files from fastboot
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Using xfstk tool
mikla90 said:
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Click to expand...
Click to collapse
open Xfstk Tool and click Tab -MRD/AO/BO +MOOR Ao+CRC then go to settings under option menu - enable GP Flag Override Option and Enter value - 0x80000807 and save (OK), then choose files -
FW Dnx - dnx_fwr.bin
IFWI - ifwi.bin
OS IMAGE - droidboot_dnx.img.POS_sign.bin
AND connect phone, press begin and Xfstk tool detect the phone and install the required files and you will able to get Normal Fastboot mode and install the firmware by fastboot / Asus Flash tool / or -SDUPDATE Zip file.
-------------------
Press Thanks Button, If i am helped you
-------------------
In the end, after about 20 times, XFSTK did flash what should have. Now, I'm back in business. I changed nothing, just kept trying.

Categories

Resources