Please help ,.. i got my tab brick,... im in HC 3.2 of my Acer iconia a100 then i try to root and i succeed ,.. and 2nd i try to unlock the boot loader ,... and thats my problem when i unlock the boot loader connected to pc my tab reboots and then i got stock in Acer Color green icon.
and every time that i turn on my tab always shows that acer icon i stock at that icon ,... and i try to flash it again by old stock rom HC 3.1 in CWM holding powed and volume up,.. boot shows " 1st Line : Erasing cache before SD update.... 2nd Line : SD update cmd: recovery 3rd Line : --update--package = SDCARD : update.zip 4th Line Booting recovery kernel image" at the upper left.... and stock also ,... how can i fix this problem,.. :crying:
romzrbp said:
Please help ,.. i got my tab brick,... im in HC 3.2 of my Acer iconia a100 then i try to root and i succeed ,.. and 2nd i try to unlock the boot loader ,... and thats my problem when i unlock the boot loader connected to pc my tab reboots and then i got stock in Acer Color green icon.
and every time that i turn on my tab always shows that acer icon i stock at that icon ,... and i try to flash it again by old stock rom HC 3.1 in CWM holding powed and volume up,.. boot shows " 1st Line : Erasing cache before SD update.... 2nd Line : SD update cmd: recovery 3rd Line : --update--package = SDCARD : update.zip 4th Line Booting recovery kernel image" at the upper left.... and stock also ,... how can i fix this problem,.. :crying:
Click to expand...
Click to collapse
What is the first line of the unlock bootloader "how to"?
ZeroNull said:
How to:
0. It has been tested on the A100 ICS firmware. This bootloader doesn't work with HC firmware.
Click to expand...
Click to collapse
Ok, now that being said. What bootloader is showing when you try to boot. Is it "3.06 ICS unlocked"?
If it is unlocked you have a chance by pushing the HC bootloader with fastboot. If not, your bricked for good, atm.
.
Romman0 said:
What is the first line of the unlock bootloader "how to"?
Ok, now that being said. What bootloader is showing when you try to boot. Is it "3.06 ICS unlocked"?
If it is unlocked you have a chance by pushing the HC bootloader with fastboot. If not, your bricked for good, atm.
.
Click to expand...
Click to collapse
i try to boot by holding volume up and power when tab turns on i switch the lock screen and it shows to the upper left " Bootloader v0.03.06-ICS: starting fastboot USB download protocol,... this is my 1st tab acer so i dont have any idea
romzrbp said:
i try to boot by holding volume up and power when tab turns on i switch the lock screen and it shows to the upper left " Bootloader v0.03.06-ICS: starting fastboot USB download protocol,... this is my 1st tab acer so i dont have any idea
Click to expand...
Click to collapse
Stop flashing random stuff! You're gonna wreck this thing for sure. First you flashed an ICS bootloader over HC, which it says not to, now you're flashing HC over it, which there are posts saying not to do. Installing a stock ROM from cwm is also asking to brick, theres even a sticky addressing this one. So stop doing stuff and READ!
you said you have cwm installed? Download any ICS ROM, like flex reaper, place it on your SD card and try to install that in cwm after wiping cache system data and dalvik cache.
Sent from my Galaxy Nexus using Tapatalk 2
Romman0 said:
What is the first line of the unlock bootloader "how to"?
Ok, now that being said. What bootloader is showing when you try to boot. Is it "3.06 ICS unlocked"?
If it is unlocked you have a chance by pushing the HC bootloader with fastboot. If not, your bricked for good, atm.
.
Click to expand...
Click to collapse
sir what if its locked??,..
i try to unlock it but it fails and then i got stocked at acer logo i think it already brick,.. and every time that i tried to install the stock rom im always stock in "update_package=sd card update.zip
booting recovery kernal image",.. and my flash boot mode is not unlocked....?,.. how can i fix this ?,.. there's any way to recover my tab ?
pio_masaki said:
Stop flashing random stuff! You're gonna wreck this thing for sure. First you flashed an ICS bootloader over HC, which it says not to, now you're flashing HC over it, which there are posts saying not to do. Installing a stock ROM from cwm is also asking to brick, theres even a sticky addressing this one. So stop doing stuff and READ!
you said you have cwm installed? Download any ICS ROM, like flex reaper, place it on your SD card and try to install that in cwm after wiping cache system data and dalvik cache.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i try to unlock the boot loader ,.. i know it was my fault ,.. i dint read that it works only in ICS rom ,...
*sigh * pio...why can't people read?
Sent via G2x on temasek b135.2 w/faux kernel v54
justjackyl said:
*sigh * pio...why can't people read?
Sent via G2x on temasek b135.2 w/faux kernel v54
Click to expand...
Click to collapse
how can i fix this ??,.. there's any other ways ??
romzrbp said:
how can i fix this ??,.. there's any other ways ??
Click to expand...
Click to collapse
pio_masaki said:
Stop flashing random stuff! You're gonna wreck this thing for sure. First you flashed an ICS bootloader over HC, which it says not to, now you're flashing HC over it, which there are posts saying not to do. Installing a stock ROM from cwm is also asking to brick, theres even a sticky addressing this one. So stop doing stuff and READ!
you said you have cwm installed? Download any ICS ROM, like flex reaper, place it on your SD card and try to install that in cwm after wiping cache system data and dalvik cache.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
There is all your answers. All of these members have taken their personal time set aside to create step-by-step guides. I don't mean to sound like a prick, but you OBVIOUSLY DID NOT READ THE GUIDES IN FULL, seeing as how YOU DID DAM NEAR EVERYTHING YOU SHOULDN'T HAVE.
I can't help you. The guides will/would've/could have helped you, but you didn't read them in full. Saying you did is a BOLD FACE LIE, or else you just outright decided to ignore the information and warnings that these members put together for users such as yourself. And you aren't the first. So the next line I am writing below this isn't meant just for you:
READ THE GUIDES COMPLETELY AND STOP DOING THE THINGS THE GUIDES SAY NOT TO DO! WHY DO WE BOTHER? AND THAN WE REALLY DON'T WANT TO HELP YOU ONE BIT. THIS IS HAPPENING TOO OFTEN. WAY TOO OFTEN WHEN WE HAVE FOOL PROOF GUIDES!! OMG YOU PEOPLE ARE DRIVING ME INSANE WITH THIS BS
I owned this tablet for 3 days before I rooted it. I read the guides completely, and I never had a single problem or even a brick/near bricked situation.
Sorry, I'm sure this pisses you off. Oh, well, the lack of anyone wanting to help themselves pisses me off to the point I no longer want to help any of you.
We shouldn't have to spoon feed the information that is VASTLY available in these forums.
F it. I'm done.
You can tell me to go F myself, the feeling is mutual.
I almost cracked my screen hitting thanks on that.
On topic: use a stock ICS ROM named update.zip on the root of your external SD card. Boot holding volume down (left) and let it install. If it errors, tell us clearly what it said. It will not unlock the boot loader, but may savee your device for another try.
Be clear people we can't help if you spout 400 line paragraphs with punctuation and random words thrown in. State the error given and when it occurs. Clearly.
Sent from my Galaxy Nexus using Tapatalk 2
justjackyl said:
There is all your answers. All of these members have taken their personal time set aside to create step-by-step guides. I don't mean to sound like a prick, but you OBVIOUSLY DID NOT READ THE GUIDES IN FULL, seeing as how YOU DID DAM NEAR EVERYTHING YOU SHOULDN'T HAVE.
I can't help you. The guides will/would've/could have helped you, but you didn't read them in full. Saying you did is a BOLD FACE LIE, or else you just outright decided to ignore the information and warnings that these members put together for users such as yourself. And you aren't the first. So the next line I am writing below this isn't meant just for you:
READ THE GUIDES COMPLETELY AND STOP DOING THE THINGS THE GUIDES SAY NOT TO DO! WHY DO WE BOTHER? AND THAN WE REALLY DON'T WANT TO HELP YOU ONE BIT. THIS IS HAPPENING TOO OFTEN. WAY TOO OFTEN WHEN WE HAVE FOOL PROOF GUIDES!! OMG YOU PEOPLE ARE DRIVING ME INSANE WITH THIS BS
I owned this tablet for 3 days before I rooted it. I read the guides completely, and I never had a single problem or even a brick/near bricked situation.
Sorry, I'm sure this pisses you off. Oh, well, the lack of anyone wanting to help themselves pisses me off to the point I no longer want to help any of you.
We shouldn't have to spoon feed the information that is VASTLY available in these forums.
F it. I'm done.
You can tell me to go F myself, the feeling is mutual.
Click to expand...
Click to collapse
hooooo!! sir thanks anyway ,.... i solved my problem,... i got unlocked my boot loader by typing this command "fastboot oem unlock" in fast boot ,... then "fastboot erase recovery",... then "fastboot flash recovery NAMEofRECOVERY.img" ,.. i flashed CWM 5.5.0.4,.. succeed ,... after that i flashed the rom and now it works properly,... oh my god im so very happy ,... thanks to all reply......
romzrbp said:
hooooo!! sir thanks anyway ,.... i solved my problem,... i got unlocked my boot loader by typing this command "fastboot oem unlock" in fast boot ,... then "fastboot erase recovery",... then "fastboot flash recovery NAMEofRECOVERY.img" ,.. i flashed CWM 5.5.0.4,.. succeed ,... after that i flashed the rom and now it works properly,... oh my god im so very happy ,... thanks to all reply......
Click to expand...
Click to collapse
my tab is now running in [ROM]ICS-"FLEX-A100-REAPER-RELIX_Rev2 (15-Sep-2012)ntfs-3Gusb-GoogleNow,...... :victory:
I really shouldn't have bit your head off. If you can't tell by looking in this general forum, so many people to not make the effort to help the,selves with the wealth of information made available to us.
Glad you read it, and got it working. Read pio's guide before you start modding. Really you should, word for word. I can't count the times I read it.
If you choose CM10, which is highly recommended, there is a walkthru tips guide, in my SIG.
romzrbp said:
my tab is now running in [ROM]ICS-"FLEX-A100-REAPER-RELIX_Rev2 (15-Sep-2012)ntfs-3Gusb-GoogleNow,...... :victory:
Click to expand...
Click to collapse
Wow nice. I'm glad you brought it back to life. Lesson learned I hope
Romman0 said:
Wow nice. I'm glad you brought it back to life. Lesson learned I hope
Click to expand...
Click to collapse
yes sir and thanks to all reply,.. i hope some newbie learn from what iv done ...
Related
Hello guys im very new to Android and i want to ask something.
Maybe its a noob question but what i did it.
I S Off my Wildfire S and i Permanently ROOT it this is all i done till now.
I never put some recovery things etc.
So today i saw something that i want to install on my device but i need to put 1st my device in recovery mode and install it then.
So when i went to recovery mode 1st for few seconds its show me a black screen with device and green arrows like all is normal and after a second showing me BIG RED TRIANGLE like something is wrong so what i think is
I dont have a recovery?!
I mean do i need to put it by myself?! this is why im not able to boot in recovery?
And if im right can someone provide me i mean show me where to look for this TUT what recovery to flash and how im sure there already have a quide and etc.
If someone can point me out i want to understand more about this devices what this recovery doing exactly i guess its recover something and maybe i can do backup etc.
Thank you in advance
I have the same issue. I used the instructions and SW at htcdev to unlock the bootloader, which worked fine. Went to try recovery and had the same issue as above. Had to take out the battery to get the phone back.
Ideas?
Dave
dvhttn said:
I have the same issue. I used the instructions and SW at htcdev to unlock the bootloader, which worked fine. Went to try recovery and had the same issue as above. Had to take out the battery to get the phone back.
Ideas?
Dave
Click to expand...
Click to collapse
I really think WE DO NOT HAVE RECOVERY installed lol
I dont know do this is posible but its seems like its posible so we must to wait someone more familiar to tell us
I think that we need to FLASH RECOVERY
it is useless stock recovery you can flash cwm recovery with this tool
Also, please post general questions, in the general section.
Sent from my HTC_A510c using Tapatalk
hi,
i need help my GN is not starting after I flashed a theme all i can just get into clock mode recovery even i didn't have any back up or any restore point it just shows google logo when i start. Please helppppppppppppppppppp pleaseeeeeee
thankzzz
now i am stuck on below attachment please help thnkzz so much for all reply till now
since you didn't do a Android your basically screwed so all you data is gone you only hope is to transfer a file through fastboot(can you even do that?) Or boot to Odin mode and flash a stock image
Sent from my Galaxy Nexus using XDA App
GSM or LTE Gnex? What ROM were you running?
Golden rule: Do a backup before doing anything to your phone!
Now all you can do is to download EXACTLY same ROM as you were using by now, wipe cache/dalvik-cache, flash this ROM once again and hope that i'll boot. If it won't you'll have to wipe /data is well.
Sleuth255 said:
GSM or LTE Gnex? What ROM were you running?
Click to expand...
Click to collapse
HI
its gsm i tried to flashed the same rom but still the same only i can access is to recovery
cordell507 said:
since you didn't do a Android your basically screwed so all you data is gone you only hope is to transfer a file through fastboot(can you even do that?) Or boot to Odin mode and flash a stock image
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
tnkz bro but i am new to android please help how to do it with Odin
well since you can boot into recovery try searching in your sdcard folders if youve left a ROM .zip there laying around and if this is the case just flash it and youre back on track
nonione said:
well since you can boot into recovery try searching in your sdcard folders if youve left a ROM .zip there laying around and if this is the case just flash it and youre back on track
Click to expand...
Click to collapse
unfortunatly i delete system file and data file also in recovery i tried to flash the zip update but no result helpppppppppppppppp
salym said:
unfortunatly i delete system file and data file also in recovery i tried to flash the zip update but no result helpppppppppppppppp
Click to expand...
Click to collapse
This will help you get back to stock
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile
Change your spark plugs.
Sent from my Nexus in Texas.
spaceman860 said:
This will help you get back to stock
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile
Click to expand...
Click to collapse
Hi bro i tired with Odin but stops on userdata any help thnkzzzz
salym said:
hi,
i need help my GN is not starting after I flashed a theme all i can just get into clock mode recovery even i didn't have any back up or any restore point it just shows google logo when i start. Please helppppppppppppppppppp pleaseeeeeee
thankzzz
Click to expand...
Click to collapse
i am stuck on this now please help
ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!
Sleuth255 said:
ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!
Click to expand...
Click to collapse
Still have a bootloader? Are you serious? You need to learn how to use an android device as well.
To the OP: Do a factory reset in Clockwork and go to mounts
and format /system. Flash the ROM zip. Profit.
Absolutely serious. Have you been reading this thread? The OP needs to start at ground zero and stop just trying every tool he/she sees. My purpose was to get this person to do some research and I was establishing a knowledge baseline. One plan I was considering was to help the OP install the GNex toolkit then locate stock images and obtain a working build. Your cryptic one liner bit should prove vastly more useful to this guy though. I'll let you have at it and go back to my dev work. lol at least this post was a good way to make sure gapps/root capabilities are properly cooked into my latest test build ....
Sent from my Full AOSP on Toro using xda premium
Sleuth255 said:
ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!
Click to expand...
Click to collapse
U r right i am not good in android but i tried to be and this happens, meanwhile nothing shows after i start the device it shows the !!!! mark with device the PC logo,this happens due to ODin actually the SUMSUNG ADB interface shows ! mark because i cant debug from device even no bootloader works any more thnkz for replying
*facepalm*
OP, you are holding it wrong.
I can think of at least 2 ways to recover from a situation like this. Both are well described in these forums (search works 99% of the time).
....
Oh come on, you don't have the zip of the last rom you flashed, get another one, hey, its free right? **** we dont know nothing about but we'll flash it anyways!
Man...If you have cwm recovery, you're safe. No need to go messing with fastboot (forget odin) just yet. Now stop wasting everybody's time and learn to help yourself.
Here's a few tags to get you started:
cwm, recovery, adb, bootloader, fastboot
bk201doesntexist said:
*facepalm*
OP, you are holding it wrong.
I can think of at least 2 ways to recover from a situation like this. Both are well described in these forums (search works 99% of the time).
....
Oh come on, you don't have the zip of the last rom you flashed, get another one, hey, its free right? **** we dont know nothing about but we'll flash it anyways!
Man...If you have cwm recovery, you're safe. No need to go messing with fastboot (forget odin) just yet. Now stop wasting everybody's time and learn to help yourself.
Here's a few tags to get you started:
cwm, recovery, adb, bootloader, fastboot
Click to expand...
Click to collapse
i tried more than one day on this issue its only starts with !!! mark on it nothing else, i have attached the pic i cant access any bootloader or any cwm or any thing all i did with Odin and stuck to attached pic even i start the device its shows the same pic.
http://www.youtube.com/watch?v=WdM2M8Nz6QQ this I used on Odin
thnkzz
As I suspected earlier, it appears that the OP may have trashed his bootloader partition when he tried using Odin to flash the 4.0.2 factory image (which includes a bootloader). At one point he had CWM but not any more since he can't boot to the recovery partition.
Another possibility is that the Odin tool itself places the device in this mode and it can't be manually reverted by starting up in fastboot mode. Looking at the picture, it literally appears that the phone is saying that a flashing operation is half finished but the phone has lost the PC connection... This would be a lot like what I've experienced with iPhones.
In either case, I can deduce that Odin is the tool to use to clear this softbrick.
Hopefully, it'll be flame-off now Sdobron. Perhaps you might want to help out here since I'm not up to speed on the Odin tool myself and would like to learn more about it.
@salym: I know this may be redundant but I need to establish your problem baseline empirically. Once again, can you verify that when you hold vol down/vol up then press power that you get the image you posted?
Use Fastboot!
Dude, it looks like your problem is with crappy boot sector.
While turning on your phone, hold both volume up and volume down buttons, and long press power button untill you feel single vibrate feedback.
Then connect your phone to the computer via USB, and if it doesn't detect drivers, google "samsung android usb driver". Additionally you can install PDANet application (X64 or x86 depending on you system).
THen download Fastboot - there are plenty of instructions how to flash it, and flash stock images (that come with radio, boot sector, rom itself, etc) - there are also plenty of discussions about how to do it. PM if you have any other questions!
Hello Members
I need a Official recovery.img dump for this ICS version
ACER_AV041_A100_0.002.00_ww_GEN1 link >>http://vache-android.com/v1/download.php?fileID=116
my recovery does not install update.zip patches and power key does not select any opition
http://youtu.be/CWFlA1W08wE
this is my bootloader version
Bootloader v0.03.11-ICS: Starting Fastboot USB download protocol
help me please
You Can make a backup this IMG with "Acer recovery tool" downloaded from the google play store
thanks
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
I just noticed something, you are aware that image you linked to is a A101 image, right?
masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
thanks now works
u save my tab
rollidark said:
thanks now works
u save my tab
Click to expand...
Click to collapse
I'm glad it worked out for you, but if this fixed your device that you made a previous bricked thread about, could you please to back, and post an update to that thread discribing what you did, and how you did it, to get the device back up again? It'll definatly help anyone else with this same issue.
You're welcomed, we are here to help each other after all. You should follow pio's advice and describe what you did so others can benefit from your experience. We have to make such info as readily available as possible.
Having the same issue described
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.
citricube said:
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.
Click to expand...
Click to collapse
He had a brick not a locked bootloader, you can't flash a bootloader directly if its locked with fast boot.
Tapatalked from my Galaxy S II.
Awesome
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:
citricube said:
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:
Click to expand...
Click to collapse
Wow that's a pretty bad run, what's wrong with either one?
Yes I know holy threadjack Batman
Tapatalked from my Galaxy S II.
masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks
liltyke said:
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks
Click to expand...
Click to collapse
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
adb reboot bootloader
Click to expand...
Click to collapse
once in fastboot
fastboot erase recovery
Click to expand...
Click to collapse
then
fastboot flash recovery "recovery.img file location"
Click to expand...
Click to collapse
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
fastboot reboot
Click to expand...
Click to collapse
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
Nicely done, masr1979!:good:
masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
thank you very much for the detailed explanation masr1979. I'll give it a shot when I get home from work.
Basically I got the rear camera replaced, it was working great. About a couple weeks later It's running sluggishly because I was running too many apps at once. So I decided to press the reset button while It was lagging out, next thing I know It's stuck at the silver android logo forever. I tried using some update.zip's but that just made the problem worse.
Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.
liltyke said:
Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.
Click to expand...
Click to collapse
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.
pio_masaki said:
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.
liltyke said:
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.
Click to expand...
Click to collapse
So...you flashed the bootloader to get back to HC and now it won't use update.zip? What about booting into android, does that still work? Or fast boot? Or uhm...I seem to recall having to do a hard reset to get the downgrade to work, have you done this too? I never downgraded just seemed pointless when I was already on ics so I'm not experienced with it, just recall seeing the boot loader needing a hard reset to work.
Tapatalked from my Galaxy S II.
No, I never flashed the bootloader, not unless that happens while trying to run an update.zip. adb and fastboot seem to be working. Based on the earlier instructions 'adb reboot bootloader' does restart the A100 and gives me the bootloader message at the top left of the screen. When I run the ' fastboot erase recovery' command I get the FAILED message in the command prompt window and also get a message in red text on the A100 saying 'Fastboot: not support the command in lockmode, failed to process command erase: recovery error (0x2)'. When I run the 'fastboot reboot' command the A100 does restart. So all that leads to believe that the communication from my computer to the A100 is ok.
Booting into Android. The A100 starts and works fine if that is what you are referring too. As far as the hard reset, if that's the process of holding down the volume button while powering up and flipping the lock switch back and forth to reset the unit, then yes I have done that and it does work. My whole goal here is to get the unit to running ICS legitimately and get updates from ACER. I don't care what I have to do, it's just a couple of the other threads mentioned the need to go back to HC to get the official ICS update. So that's why I tried that. But the last time a update.zip worked was when I flashed the leaked ICS. I have got the dead android logo every time since.
Sorry if some of this info is redundant from my earlier post, I just wanted to get it all in the same place.
Thanks again for your help.
I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!
still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?
phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:
Im Sorry guys to bother you but i need to root/flash custom roms and modify some stuff in my sister's galaxy w and i dont know anything about samsung system because im using sony since i was born and the system in sony was that i have to unlock bootloader then root then flash kernel then flash custom rom and if something goes wrong i hold the volume up and go into fastboot mode and get everything back to normal
So please if anyone can help me on how to root and flash and what are the right steps and if i got into a bootloop or something how can i get the phone back to stock
thanks in advance
aliiahmed.20 said:
Im Sorry guys to bother you but i need to root/flash custom roms and modify some stuff in my sister's galaxy w and i dont know anything about samsung system because im using sony since i was born and the system in sony was that i have to unlock bootloader then root then flash kernel then flash custom rom and if something goes wrong i hold the volume up and go into fastboot mode and get everything back to normal
So please if anyone can help me on how to root and flash and what are the right steps and if i got into a bootloop or something how can i get the phone back to stock
thanks in advance
Click to expand...
Click to collapse
Search before you ask any questions, by the way here is a link for the tread on how to root the phone : HERE
You dont have to unlock bootloader for the samsung phones, you just press the button and pray for the phone to work after that
Hope you got your answer here, Enjoy
Click the link below to go to my A to Z beginners guide.....
http://forum.xda-developers.com/showthread.php?t=1941028
it tells you EVERYTHING you need to know about rooting, recovery and custom ROMs..... all in one place.....
Sent from my Infected KitKat bar.....
MayB4ck said:
Search before you ask any questions, by the way here is a link for the tread on how to root the phone : HERE
You dont have to unlock bootloader for the samsung phones, you just press the button and pray for the phone to work after that
Hope you got your answer here, Enjoy
Click to expand...
Click to collapse
Yea thanks for the info but if anything go wrong or i get into a bootloop or a software brick how to fix the phone ?
(in sony i use flashtool to reflash the stock software even if the phone doesnt have a rom/kernel/recovery the flash mode will work)
aliiahmed.20 said:
Yea thanks for the info but if anything go wrong or i get into a bootloop or a software brick how to fix the phone ?
(in sony i use flashtool to reflash the stock software even if the phone doesnt have a rom/kernel/recovery the flash mode will work)
Click to expand...
Click to collapse
Odin is the Samsung equivalent of Sony's Flashtool. CWM is another lifesaver as it has wipe options built in that can help to get a phone to boot. CWM remains installed even if the main OS is removed........
Sent from my Infected KitKat bar.....
keithross39 said:
Odin is the Samsung equivalent of Sony's Flashtool. CWM is another lifesaver as it has wipe options built in that can help to get a phone to boot. CWM remains installed even if the main OS is removed........
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
Yeah I have used sony phone for a while and i have broken it (Hard bricked) when unlocking the bootloader, then I picked up a galaxy w and I am still in love with it, Its a single core but it can do miracles. I have soft bricked my phone many times, I sometimes delete the ROM i put on the sd card to have room for the kernel and other tweaks so i use Odin to just return the stock OS and then get a new ROM and flash it inside. There is not much risk and you cant go wrong with the phone. I fixed mine many times and i know how many frustration you get when doing such thing. I remember the first time when i bricked my phone by installing kernel for another android version, and then i booted up to CWM and wiped data/cache and flashed a new rom. Because of the long booting time i thought that its over, i broke my phone, but after sitting there for 10 mins. it finally booted up. Damn i was so happy then, i rooted my phone and installed a new rom for first time :victory:
MayB4ck said:
Yeah I have used sony phone for a while and i have broken it (Hard bricked) when unlocking the bootloader, then I picked up a galaxy w and I am still in love with it, Its a single core but it can do miracles. I have soft bricked my phone many times, I sometimes delete the ROM i put on the sd card to have room for the kernel and other tweaks so i use Odin to just return the stock OS and then get a new ROM and flash it inside. There is not much risk and you cant go wrong with the phone. I fixed mine many times and i know how many frustration you get when doing such thing. I remember the first time when i bricked my phone by installing kernel for another android version, and then i booted up to CWM and wiped data/cache and flashed a new rom. Because of the long booting time i thought that its over, i broke my phone, but after sitting there for 10 mins. it finally booted up. Damn i was so happy then, i rooted my phone and installed a new rom for first time :victory:
Click to expand...
Click to collapse
So can you give me a small guide on how to use Odin ?
You don't NEED to use Odin. The link I provided gives you easy to understand information about how to root, CWM and flash cusROMs 'in phone'......
It's how I did it, and it really is very easy to do/follow.......
Sent from my Infected KitKat bar.....