Database Users

Up shat creek

Did the 1 click root successful and loaded up cyanogen 6 and then tried thinking I was a big dog and screwed around and f'd up my phone,it won't get past any of the recovery screens,I will link what I have gone through over at nof.net,sorry for the link but I suck at typing because it takes me forever so please read,also I will paypal 20 bucks who can get me out of this debacle. Thanks.
oops can't link cause I'm new but If you are kind enough to go to nexusoneforums.net and read it ,It's titled In deep doodoo.
Basically it won't boot past the x no matter what i do,but I can see everything is still on my memory card through my laptop

direct link to his post
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/8483-deep-doodoo.html

thank you
10 char

I think you need to locate a stock, signed update zip file and put it on your sd card. I'd do this seperate from the phone. Take the card out and put it in your laptop or whatever you have to read it.
I'd then get back to where your were on page four of your other thread where it says apply update zip.
you don't know if you have the stock recovery img still? or Ra or clockwork?
your phone isn't broke, I wouldn't worry too much.
You also don't know if you bootloader is unlocked or not?
heres frf91 full if you choose to go this route http://www.mediafire.com/?xniymzimojg

Stock ROM's here: http://www.mediafire.com/n1passion
Sounds to me like you need to relax a little and read a bit more before jumping in with both feet... Rooting isn't necessarily for everyone.

I won't ever ever attempt this again.

Macklessdaddy said:
I won't ever ever attempt this again.
Click to expand...
Click to collapse
ahh don't do that! I don't even want to begin to count how many bootloops I've had, I'm pretty sure I've seen more of that X than I have of my home screen. I think once you've messed up once and had someone help you to fix it it kinda implants into your head how to fix it in the future. My only advice for future attempts is to Nandroid backup (make sure you have atleast 1 sure working back up, then do further updated back ups along side it)

Can someone tell me which file I need in post #5 for a tmobile n1.Thanks

http://www.mediafire.com/?xniymzimojg

jbrinkley,I downloaded the file and put it on the memory card,but I'm still getting the same x screen,anything else I can try.

I won't ever ever attempt this again.
Click to expand...
Click to collapse
The only way to master something is through multiple failures
Sent from my Nexus One using XDA App

Somebody help me,I had no clue this phone meant so much to me.

wrench115 said:
The only way to master something is through multiple failures
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I don't want to fail with my phone.Trust me when and If I get it working I will stay in my lane and leave the rooting to you guys.

Flashing back to thw original stock rom should fix it there's a link posted above. Atleast it worked when I had a g1 and royally screwed up. I would try that first.
Sent from my Nexus One using XDA App

I cant,or obviously don't know how to flash back to the original rom.Don't mean to sound ungrateful but it appears nobody is reading about the problem I'm having ,again I'm stuck at the x and can't get out.

I will paypal 20 bucks to the person who helps me out of this mess

OK, relax... take a deep breath... and try this out...
1. Download a full ROM zip (e.g. Passion-EPE54B.zip) from http://mediafire.com/n1passion
2. Pop out your SD card and pop that zip onto your SD card, be sure to rename it to PASSIMG.zip
3. Boot into bootloader mode (power off -> trackball + power)
4. The phone should pick up the PASSIMG.zip and ask you if you would like to update it... select yes!!
This will restore you to the stock EPE54B image, you can then download the FRF91 OTA or re-root you phone...

Craig,I downloaded the file from post#9 and renamed it PASSIMG.zip and went to bootloader and the x came up again,do I need to use the 54 one you were talking about to get to 91,sorry but I'm smartphone illiterate as hell.I get a message that says no image or wrong image
If I try to apply sd card update I get this message
failed to open\sdcard\update.zip(no such file or directory)
E signature verification failed
Installation aborted
Does it matter where on the memory card the file is at?

what we don't know is what recovery you have, if you bootloader is unlocked or not.
I don't know anything about that one click method. if you have a nandroid file on you sd look in there and see if you have actual backups.
and now i can't remember if you got to the restore menu or not.

jbrinkley said:
what we don't know is what recovery you have, if you bootloader is unlocked or not.
I don't know anything about that one click method. if you have a nandroid file on you sd look in there and see if you have actual backups.
and now i can't remember if you got to the restore menu or not.
Click to expand...
Click to collapse
bootloader not locked,under clockwork mod I see recovery and there is 3 backups under recovery

Important for woot.com [Sprint] Tab Owners

So there may be several of you reading this posting that got your Tab from woot.com. I have been working on getting my hands around this tablet since day 1 and I wanted to stress to each and every one of you that plan on rooting or flashing anything to get yourself a new SD card asap... I found, as well as many others, that the SD card that came from Samsung (16GB) seems to be a problem for the device when it comes to flashing kernels and roms...
I finally was able to get Honeycomb on my device after swapping the 16GB SD card out with a 2GB SD card I had laying around at work. I couldn't get any of the CWM kernels to actually do as it was planned to do until now...
Just wanted to share!

Because I find it important to share what I learned, here are the steps I followed, in as best detail as I can, to obtain root, CwM 3.0, and Spacemoose1's HC Alpha 2.5 build:
First of all a few things to note, some of which is specified above in my previous posting, replace the SD card with another one that’s not from Samsung (as it appears this caused several issues). Odin 1.7 (with .pit) and Heimdall (with 1.1.1 binaries) are your best friends, download them both. Make sure for using Heimdall you have the Microsoft Visual C++ 2010 Redistributable Package (x86). For Odin make sure you have the EA24 .tar, this will be your get out of jail free card if you mess something up (Lord knows I’ve done this like 20 times trying). This simply allows you to reflash your Sprint Tab back to EA24 and you can start over.
Here are the steps I followed to get to where I am now:
-- Took the OTA updates from DJ30 (out of the box at this) to EA24 (eventually started here after using Odin several times) to EB28.
-- Enabled USB debugging (always important to have this one on and, if you’re like me, stay awake so I don’t let the thing fall asleep on me and unknown sources).
-- Obtained root with SuperOneClick (this is very easy to do, literally one click root) and rebooted as specified by SuperOneClick’s direction. I verified root by observing Super User in my apps and downloading terminal emulator, typing “su” in the window and selecting enter to be shown # to verify root.
-- I downloaded the latest and greatest kernel (zImage) and ROM from Spacemoose1’s build thread and placed a copy of the zImage file on my desktop for quick access and the ROM on my SD card of the Tab.
-- Next I unplugged the device from the computer, powered down, and put it in to download mode by holding down the power button and volume down until the shoveling android is shown. I then plugged in my device to the computer and opened up my Heimdall folder I extracted to my desktop and navigated to the Drivers folder and double-clicked the zadig.exe to install the drivers. I selected options and list all devices. From the drop down I selected Samsung USB Composite Device and selected install drivers. If everything goes well it will say drivers are installed successfully.
-- I didn’t leave download mode, I proceeded to flash the zImage file from Heimdall. I opened Heimdall Frontend and, on the left side of the application, selected browse to find the zImage file I placed on my desktop. I ensured the checkbox to the left of the field was checked and selected start. If everything is successful it will flash your kernel and reboot in to recovery and freeze at the Samsung logo. I held down the power button for about 8 seconds until the screen cut off. When the battery icon was shown (with the green color showing amount of charge) I held down the power and volume up button to enter recovery mode. It will attempt to backup and fail, don’t sweat it. Wipe data/factory reset and then wipe cache, then reboot the Tab. It will freeze at the Samsung logo again; just hold power down for about 8 seconds until it turns off. When the battery icon is shown (with the green color showing amount of charge) I held down the power and volume up button to enter recovery mode. This time the device will resume backing up and complete successfully. Once it’s completed, to flash Honeycomb you will need to select install zip from SD card and then select zip from SD and choose the latest ROM that you downloaded and placed on your SD card. It will flash so let it do its thing. It will reboot and eventually load Honeycomb.
MOST IMPORTANTLY JUST READ AND IF YOU'RE NOT SURE ABOUT SOMETHING PM ME AND I'LL SEE IF I CAN HELP!

I also have a sprint refurb woot tab and did not have this issue.
I flashed to hc just fine using superoneclick -> special sprint tab cwm instructions thread (uses heimdall) -> cwm update using sm1's zip file.

Thisrobot said:
I also have a sprint refurb woot tab and did not have this issue.
I flashed to hc just fine using superoneclick -> special sprint tab cwm instructions thread (uses heimdall) -> cwm update using sm1's zip file.
Click to expand...
Click to collapse
Yeah I've seen mixed reviews on how to go about things and many Sprint users, including woot.com Tab owners, experiencing a wide array of issues or none at all. I think documenting all the various issues will give us a better chance of figuring out different approaches that'll be specific to each user.
Just wanted to share another story in detail. Thanks for your input!

I'm one of the one's having no issues at all. I took both updates, rooted the thing and disabled the activation. Have no desire to do anything with it beyond that though. HC just strikes me as half baked. If/when the GB update comes down OTA I'll take it, but I have no plans to flash any ROMS or anything. Only issue I've noticed is that if I don't reboot it every other day or so it develops serious lag. If unaddressed it becomes completely and totally unresponsive. Rebooting it fixes the problem. I may just program Tasker to reboot it at night.

A. Nonymous said:
I'm one of the one's having no issues at all. I took both updates, rooted the thing and disabled the activation. Have no desire to do anything with it beyond that though. HC just strikes me as half baked. If/when the GB update comes down OTA I'll take it, but I have no plans to flash any ROMS or anything. Only issue I've noticed is that if I don't reboot it every other day or so it develops serious lag. If unaddressed it becomes completely and totally unresponsive. Rebooting it fixes the problem. I may just program Tasker to reboot it at night.
Click to expand...
Click to collapse
i noticed a similar slowdown when my tab was on for long periods of time.. If you are using Dolphin HD, install the addon "browse faster." it kills unnecessary processes and makes scrolling/switching tabs more responsive.
OR, you can hold the home key-> hit the task manager button->exit all and/or under the ram tab clear memory.
These work fine for me, and at this point i pretty much never have to reboot because of slow perf.

The original microSD card was unrecognized out of the box, but formatting it on another device worked. Try doing that and putting the card back in.

s44 said:
The original microSD card was unrecognized out of the box, but formatting it on another device worked. Try doing that and putting the card back in.
Click to expand...
Click to collapse
I'll have to give it a shot, even though I just bought a 32GB one for it..

anyone else getting a constant conversion to ext4 when you reboot into CWM? I swapped out the stock sd card for a 1gb card i had laying around, it runs through the conversion, and can read the sd card, but as soon as I flash the HC rom and reboot it just sits at the samsung bootlogo. I power it down, and go back into recovery and it runs the conversion again. The only time it doesn't run the conversion is if i put the stock sd card in, then it just says can't mount /sdcard. this is getting really annoying. I've got an Epic 4g and stuff like this just doesn't happen, so I'm wondering what the heck the issue with the Tab is.
So, figured out anytime I was getting stuck in the ext4 conversion loop for recovery, that I needed to go back and flash the recovery via heimdall again. It seemed every 3rd flash would work. Annoying, but at least now I know.

My card pooped out and they gave me a $20 credit. Time for a class 10 16gb card. Maybe the dead one will come back to life!
- Z

I bought a refurbished Sprint Galaxy Tab from meritline.com. Probably of similar heritage to the one Woot was selling.
So far my 16GB SDCARD has worked without any problem. I have (just for the heck of it) ordered a 32GB Class 10 card to use in the Galaxy Tab.
Am waiting for Spacemoose1 to release a Honeycomb beta version. Will probably dive into HC at that point.
And if someone figures out how to get Netflix flying on the Galaxy Tab I'd be interested to hear all about it.

Another question -
Since my Sprint Galaxy Tab does NOT have any active data plan, will it still acquire OTA updates? Mostly I'm curious about the upcoming, promised Gingerbread update from Samsung.
Or will I have to manually install it. Since KIES does not function on these CDMA tablets it leaves me wondering just how this update will find its way to my Galaxy Tab.

I also don't have a data plan with sprint, and I've received OTA updates (possibly pulled down via wifi) so hopefully if we do get lucky enough to get an official GB update, it'll come OTA even without a data plan..

pvtjoker42 said:
I also don't have a data plan with sprint, and I've received OTA updates (possibly pulled down via wifi) so hopefully if we do get lucky enough to get an official GB update, it'll come OTA even without a data plan..
Click to expand...
Click to collapse
My Samsung Fascinate is on a data plan with Verizon. When an OTA download is available and I request the update via the phone settings, it ALWAYS cautions that it is about to disable the WiFi in order to access the OTA update.
I do not know if the same is true of Sprint as I've never had an activated Sprint phone . Seriously hope not as it might make it less than straight forward to acquire the OTA updates such as Gingerbread.
Time will tell.

warranty on a refurbished galaxy tab
Hawk521,
I am thinking of buying the one from meritline too. I am concerned as to who did the refurbishing. Was it Samsung? How come there is only a 90 day warranty as opposed to a year for a new one? Is it worth spending more for the full warranty?

pvtjoker42 said:
anyone else getting a constant conversion to ext4 when you reboot into CWM? I swapped out the stock sd card for a 1gb card i had laying around, it runs through the conversion, and can read the sd card, but as soon as I flash the HC rom and reboot it just sits at the samsung bootlogo. I power it down, and go back into recovery and it runs the conversion again. The only time it doesn't run the conversion is if i put the stock sd card in, then it just says can't mount /sdcard. this is getting really annoying. I've got an Epic 4g and stuff like this just doesn't happen, so I'm wondering what the heck the issue with the Tab is.
So, figured out anytime I was getting stuck in the ext4 conversion loop for recovery, that I needed to go back and flash the recovery via heimdall again. It seemed every 3rd flash would work. Annoying, but at least now I know.
Click to expand...
Click to collapse
I got around this by formatting, partitioning and converting to ext4 using my Evo4G.

alans75 said:
Hawk521,
I am thinking of buying the one from meritline too. I am concerned as to who did the refurbishing. Was it Samsung? How come there is only a 90 day warranty as opposed to a year for a new one? Is it worth spending more for the full warranty?
Click to expand...
Click to collapse
I don't know who did the refurbishing. On items like this that have only been on the market for 7 months or so, most 'refurbs' are likely simple product returns from buyers who were not happy for one reason or another. I've bought lots of refurb items over the years and have yet to have any regrets.
FWIW, mine came in a brand new looking oem box, the power supply and cables were still in the oem packaging and all documentation was pristine.
If it suits your needs go for it. Sure beats spending $350+ bucks on one. I'm not using any Sprint 3G data plan - just treating this as a WiFi only tab.
Also, just today it leaked out that Sprint will be providing an OTA update to Gingerbread starting on July 5th, 2011.
http://www.engadget.com/2011/06/30/sprint-updating-the-samsung-galaxy-tab-with-gingerbread-on-july/

pvtjoker42 said:
anyone else getting a constant conversion to ext4 when you reboot into CWM?
Click to expand...
Click to collapse
After it fails the first time (and while you're still in the CWM utility ROM go and clear the two cache settings prior to restarting into CWM rom again. Clearing the caches (one is under the advance setting) will clean things up so that upon the next bootup CWM will properly convert to ext4.
At least that is what I've seen several times now.
Good luck with it.

Gingerbread for Sprint on July 5th?
Has anyone had any luck with the July 5th Gingerbread upgrade that Google and Sprint have indicated would begin downloading on July 5th?
I realize they may roll the update out over several days, but so far my attempts to prod the update manually have met with no results.
If anyone has better luck please post it here. Also note if your Galaxy Tab has a current Sprint data plan, or if it is like mine, a refurb that has no current contract for data.
Watching and waiting...

Hawk521 said:
Has anyone had any luck with the July 5th Gingerbread upgrade that Google and Sprint have indicated would begin downloading on July 5th?
I realize they may roll the update out over several days, but so far my attempts to prod the update manually have met with no results.
If anyone has better luck please post it here. Also note if your Galaxy Tab has a current Sprint data plan, or if it is like mine, a refurb that has no current contract for data.
Watching and waiting...
Click to expand...
Click to collapse
My non-activated sprint galaxy tab just only show me "Unknown Error", when I try Setting->About My Galaxy Tab->System Updates->Update Firmware.

[Q] Cant get 3.1

24 hours with the tab...
I am new to the tab and i am not going to root yet. I want to use it as ASUS intends it to be, for right now.
Anyways, it came 3.0.1, and i when i ask it to update it tells me no new updates are available. Battery is fully charged, wifi signal is great.
Anything else i can do?
PS- I am saving a review until i get the update, but typing this message was at best frustrating.
Cheers!

Im trying to figure this out as well. Im planning on calling Asus today and ask for help I'll share how to do it as soon ask figure it out
Sent from my SGH-T959 using XDA App

Agnog said:
Anyways, it came 3.0.1, and i when i ask it to update it tells me no new updates are available. Battery is fully charged, wifi signal is great.
Anything else i can do?
Click to expand...
Click to collapse
Download the update manually from the Asus website, save it in your TF's internal memory, then try going to the update page and it should detect the file and allow you to install it. If it doesn't come up straightaway try rebooting your TF and try the update page again.

jonitfcfan said:
Download the update manually from the Asus website, save it in your TF's internal memory, then try going to the update page and it should detect the file and allow you to install it. If it doesn't come up straightaway try rebooting your TF and try the update page again.
Click to expand...
Click to collapse
Something isn't right because your tablet should update automatically once it gets a connection.

I think you an install the update manually.
1)Download the firmware from Asus, unzip it and put the contents for the ASUS/Updates/ folder on the root directory of the external SD card. Rename it to EP101_SDUPDATE.zip
2) Boot into recovery - hold volume down, press power button. Your TF will turn on and say it's going to blow up in 5 secs. Press volume up within 5 secs. Don't delay because you could wipe your data if you press volume up too late.
3) get some popcorn and watch the magic happen. Afterwards, it will reboot, you'll see a progress bar to indicate that it is flashing. Then it should boot into sweet honeycomb.
4) Delete or rename the EP101_SDUPDATE.zip for something else, or else it will flash every time you go to stock recovery.
Edit: I think the firmware has to match your current build, i.E., US, TW, WW. Check your build info to be sure.

gee one said:
I think you an install the update manually.
1)Download the firmware from Asus, unzip it and put the contents for the ASUS/Updates/ folder on the root directory of the external SD card. Rename it to EP101_SDUPDATE.zip
2) Boot into recovery - hold volume down, press power button. Your TF will turn on and say it's going to blow up in 5 secs. Press volume up within 5 secs. Don't delay because you could wipe your data if you press volume up too late.
3) get some popcorn and watch the magic happen. Afterwards, it will reboot, you'll see a progress bar to indicate that it is flashing. Then it should boot into sweet honeycomb.
4) Delete or rename the EP101_SDUPDATE.zip for something else, or else it will flash every time you go to stock recovery.
Edit: I think the firmware has to match your current build, i.E., US, TW, WW. Check your build info to be sure.
Click to expand...
Click to collapse
I am following your instructions and all I am getting is the Android with the exclamation mark symbol when I reboot from recovery.

Agnog said:
I am following your instructions and all I am getting is the Android with the exclamation mark symbol when I reboot from recovery.
Click to expand...
Click to collapse
Nevermind, I got it. I was being dumb.
3.1 goodness.

Agnog said:
Nevermind, I got it. I was being dumb.
3.1 goodness.
Click to expand...
Click to collapse
What you do to get it to work im having the same issue with the exclamation mark symbol.........
EDIT
....ok i took a shot and did EXACTLY (read carefully) what was in the directions... i removed all the folders that were part of the udpate ( ASUS\UPDATE) I put the .zip on the root of the sdmicro... this contradicts what the SOP says to do with the manual update but hey it works ...thanks
EDIT EDIT
This should be added to the STICKIY as a way to update!!

gremmie said:
What you do to get it to work im having the same issue with the exclamation mark symbol.........
EDIT
....ok i took a shot and did EXACTLY (read carefully) what was in the directions... i removed all the folders that were part of the udpate ( ASUS\UPDATE) I put the .zip on the root of the sdmicro... this contradicts what the SOP says to do with the manual update but hey it works ...thanks
EDIT EDIT
This should be added to the STICKIY as a way to update!!
Click to expand...
Click to collapse
Agreed. I misunderstood the directions at first - my fault for being a noob. I ended up using the full SD slot on my dock, but the math was the same.
HUGE thanks to gee one.

[Q] stuck at shut down screen after interrupting update

tl;dr: Interrupted update. cant do jack. tried acer tech support. failed
I grew bored with waiting the two minutes for my tablet to install the new update. so i stood up and hit the power button to put it to sleep like a boss. then i cam back later, the lock screen was unresponsive
i figured out be double tapping the pwr button i was able to unlock the tablet to see the powering down screen (see attachment). I can get to the setting menu, but evrytime i try to mess around in it, the window closes itself.
an interesting note is that the time is wrong, and the battery suddenly went from 100% to 15%
I called acer tech support, and with ther guidance...
pressed the reset button to no effect
powered on holding the pwr & vol- buttons down to get an error (see attachment). then the tablet turns off.
Ive dled some "update.zip" files i found online that are supposedly used to unbrick the tab... but i just got the same error picture(see attachment)
one other thing i tried was to hold the power and vol+ buttons. this cleared a chache, but had no other effect.
I am a noob at droid, but not to tech. i would like to avoid perma bricking, and im unsure about mailing this in. waiting is gay. I would like to restore it to factory settings w/o rooting it etc. as ive never done that before. but im not opposed to installing a CFW if it somes to that...
Im looking for ideas guys here guys. wtf is wrong with this thing?

Haha
Lmao "hit the power button to put it to sleep like a boss", funny ****.
Can't help you though sorry

ive been around he web, and have seen this exact series of symptoms happen to a handful of other guys... i haven figured out a solution yet, and it is looking more and more like ill be sending it in via warranty
my best guess at this point is i have corrupted a crucial system file. as to why i can do jack in the factorys recovery mode... idk. but then again, idk what the factorys recovery mode should look like or how it would function. youtube only shows CWR... which i dont have
if i believed i could anything reasonably withing my abilities, i would... but voiding the warranty on a long shot seems dumb.
still ANY ideas would be great

I too faced exactly the same problem today.. Dunno why this is happening... I am too worried now... Kindly post the solution as you find them...
Am sure calling tech-support is just waste of time..
Thanks in advance..

IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.

npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??

stuck on same screen also!
My friend and i who both purchased this Acer Iconia tab are both having the same problem. We both received a message on the tablets to do the update. We both got stuck and have gone thru tech line and there is no remedy. She was able to return hers within the 15 day period; I on the other hand am a week over that so have to mail it to Acer for repair. I'm thinking this is more than a cooincidence and there is a problem more spread... Acer would neither verify or confirm....

buntzmehta said:
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??
Click to expand...
Click to collapse
He said the root of his SDCARD. You can take out the sdcard and put it in a sd cardreader on a computer and copy the file to it then put it back in the tablet. The file worked for him so it might be worth trying. Just have patience while it is loading as some of these updates take a while to load and sometimes you may not see anything happening but it is. The more patches and roms you load on Android the more you'll learn to just leave it alone and let the updates finish. Its pretty rare for updates to be messed up. Its usually people getting anxious and clicking on stuff.
Good luck
Sent from my A501 using Tapatalk

still stuck on shutdown screen any updates?
Anyone had any luck with a fix? If not --sending it to Acer for warranty repair after the hurricane hits..Sure hope this isn't a wide spreasd Acer issue do to the new download. Wish I could just return the thing all together. Worked well while I had it a whole 3 weeks...... Thanks in advance for any information.

npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
Thanks a lot dear npena.. you are simply great.. i was very anxious initially to try your method as no other member here who face the same problem thanked or recommended your suggestion...
I tried it and it worked... I am really very thankful to you...
Cheers..
you are my hero indeed.. thank once again..
BuntZ

Friends, who face this problem you must try it... it just takes few mins b4 you can get your acer tab to work again beautifully without loosing any settings or installed apps... they remain intact...

Yay!
Glad you got it running again - had a similar problem when doing a ota update myself, was so worried I bricked the tab, went thru about 7 update.zip files until I found one that magically worked, letting me get back into the system and flash the correct rom for my region

hi! i have the same problem with my a500. I write a guide to solve this problem. Problem in firmware. here is the gude http://forum.xda-developers.com/showthread.php?t=1572622

Lost all hope...

It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.

Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
So where are you at right now. What rom and what exactly have you done to your tab.

Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD

shaun298 said:
So where are you at right now. What rom and what exactly have you done to your tab.
Click to expand...
Click to collapse
At this moment right now, my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.

Moscow Desire said:
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
Click to expand...
Click to collapse
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.

Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.

Mkami said:
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Click to expand...
Click to collapse
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD

cruise350 said:
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Click to expand...
Click to collapse
What do you mean by RUU? Also I've tried a couple of the OTA updates, when I first got the tab it was on 3.1 HC didn't even update it or anything, just had a custom ICS ROM on it. Do you think you can post the steps or anything on how to do this properly and go fresh? It would be sincerely appreciate buddy.

Moscow Desire said:
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
Click to expand...
Click to collapse
Hmmm....I'm not even sure what I am doing wrong but whatever it is, it seems to be not working. I looked for you post for the earlier person that you did, but don't know what it is under. By the way when I first bought the tab it was under 3.1 HC and after getting flexreaper it became to ICS 4.0.3...
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.

Mkami said:
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Click to expand...
Click to collapse
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.

im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire

lcd047 said:
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
Click to expand...
Click to collapse
You're right! I was able to fix it and boot up to the usual! Thanks mate!

chismay said:
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
Click to expand...
Click to collapse
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!

Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Mkami said:
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Click to expand...
Click to collapse

tkirton said:
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Click to expand...
Click to collapse
Hahaha! Good job on guessing all that! I just followed your order from step to step and I was about to boot up normally! Everything might be erased and stuff, but hey at least I have my tablet working again :good: Case solved!