Database Users

[Q] Unable to upgrade from... (solved, but questions) **UPDated**

Hi fellow streak users. Hopefully I'm asking questions in the right place.
Background:
I have read a fair amount of threads on upgrading the streak. I had 1.6, GUASBA111100 (build 6267? from memory), and received the dell 2.2 update notification. Downloaded the update and selected it when it downloaded. The phone re-booted, then sat at a black screen. There it sat for many hours. I tried re-downloading the update many times, but it does the same thing.
I got sick of this and started digging on the web. A simple method seemed to be to rename the file Update.pkg and put it on the root of the sdcard. It then sits at the dell logo. Forever. I have downloaded more images, roms, recoveries than I want to admit. I have attempted following fastboot instructions. They all fail on the reboot.
Currently the phone will not start up at all. Is it really possible to brick the phone?
What I'm trying to do.
Given all the bad publicity I have read about the current 2.2 from dell, I am hoping to install steve's latest version. I am hoping someone has some time and patience to explain how to do this. (commands and which files to use) (as the phone does not seem to respond to all the methods flooding multiple forums).
If you need further information, please ask.

Try flashing the stock recovery for the 1.6 build you have then it should boot as normal. Make sure all the other versions you have are not in the "fastboot" c:/ folder.

OK, here's the update. It's a bit jumbled and random, but I have been up for at least 18 hours fiddling...
I was unable to find the stock recovery for the 1.6 build I had. Probably lots of mismatched files were flashed unnecessarily. Nothing would touch the 'carrier unlocked US version' I had. That is until I tried QDL tool upgrade M 2.7.4.8 Now I suspect it is a beta version of 2.2 that it puts on the phone. It's slow and featureless. But it was the only thing that worked. From there I managed to make clockwork recovery work, and worked my way from steve's 1.4.6 to 1.5.1 to 1.5.2 Somewhere here the phone chucked a spaz and I discovered my phone had been booted off the network (showed no signal coverage). I began to suspect something to do with the imei being blocked (Another streak I was playing with is locked to O2, but came with a rebelsim installed - apparently illegal in australia). I checked the IMEI and it had mysteriously changed. (I suspect it had somehow been put to all zeroes, and something somewhere had given it a 'different' one.) Anyway, I used the QDL tool again, and the original one came back.
Finally what worked for me: QDL tool to flash 2.2, flashthe new amss.mbn, flash clockwork recovery, put steves 1.4.6 on SDcard and flash, then flash 1.5.3
(I couldn't tell you where I downloaded the files that worked. Your results (people who are still seeking action to try and upgrade their software) may vary. All I can say is that now I have downloaded half the internet and installed all the computer drivers, I have hit on a combination that works for me on this computer).
Steve, Thankyou! It's fast, snappy. It has those settings I love to twiddle.
Thank you to everyone else that has either directly or indirectly helped me with your description of how you got yours working.
Thank you for the hosting of the ROMS. I like that you don't have to wait 45 seconds and/or join to download.
A few comments:
I downloaded so many roms and files that it wasn't funny. The problem is that they are all named Update.zip, amss.mbn etc. When they are all in the download folder... Some people just provided the files, others packaged them with a batch file to automate the process. If I was to download them all again, I would download them into folders labelling them...
There seems to be a wide variety of situations/variables that dictate 'what you need to do and how you need to do it' to change roms in the phone. There are half a dozen comprehensive guides on the net, yet all different. I was quite confused. It almost needs some sort of chart where you can pick where you are at the moment, where you want to be, then follow those instructions.
I was also bamboozled with the different tools. QDL, flashboot, ADB etc. I have a bit of an idea, but I'm sure others are equally confused. I know the information is 'out there' but to have it all in one place. What do some of the files do. Why might you need to flash them. Which files are erased by the stock ROM if you don't do anything with them. What does it do when you flash a recovery? How long does it stay on the phone?
There are several parts of the phone that get upgraded. Not sure I have it right, but QDLtool upgrades the modem software (amongst other things) Other things you change is the baseband, SDcard contents etc. (Trying to connect what software files go to what places to what hardware in the phone.)
I do have several questions that have arisen.
1. Am I right in thinking you must flash steves 1.4.6 before you can flash the latest 1.5.3?
2. QDLtools: In theory is it possible to replace the files somehow so it puts steve's latest ROM straight on?
3. Rebelsim: (The small amount of information I have suggests it is illegal in australia) Does it block or change the imei? Can the carrier tell if you are using one?? (not that I use one, apparently they don't work on 2.2)
(that's all for the moment.)

i have been having problems with doing my streak aswell and still am but
ato answer one of your questions that i found out while downloading the whole internet is that the QDL tool can be used to put steves on
here is the instructions i just copied off the qdl page i would of posted a link but i am a new member so i cant post inks yet
Beyond QDLTool
Using QDLTool will get you to a pre-release of v2.2. From here, you’ll want to upgrade to a newer release. The two options that people tend to choose from are to either go up to the official v2.2 ROM from Dell, or install DJ_Steve’s latest ROM.
Official ROM
If you want to go to the latest official ROM from Dell, simply set up your wifi connection, then go to Settings -> About Phone -> System updates. The latest update can then be downloaded and installed, updating your Streak.
Latest Streakdroid ROM
If you want to upgrade to the latest Streakdroid ROM (1.5.3), either from the QDLTool install or from the latest official build, you can follow these steps:
1.Go to the downloads section and grab StreakMod Recovery, the latest 1.5.3 Update and the AMSS for 1.5.1+ (the update and amss are under Roms, StreakMod Recovery is under Recovery)
2.Copy the update-1.5.3.zip file onto the root of your SD card.
3.Extract recovery.img from the StreakMod recovery and place it, along with amss.mbn, into the same directory as QDLTool (QDLTool has a copy of fastboot)
4.Shut down your Streak, then hold down the camera button (all the way) as you turn it back on.
5.The screen should turn white; press ‘Fastboot’ in the top right hand of the screen.
6.Plug in the USB cable – the Streak should now display ‘FASTBOOT_MODE’ at the bottom of the screen.
7.Open a command window and use ‘cd’ to change to the same directory as qdltool.
8.Run: fastboot -i 0x413c flash recovery recovery.img
9.Run: fastboot -i 0x413c flash amss amss.mbn
10.Run: fastboot -i 0x413c reboot
11.As the Streak starts to reboot, hold down both volume buttons.
12.The recovery menu should come up; select option 2 (Upgrade)
13.A Dell logo and an exclamation mark should appear; press power or menu to open StreakMod’s main menu
14.Select ‘apply sdcard:update.zip’ then ‘chose zip on sd card’
15.Find the update-1.5.3.zip file, select it and apply the zip.
16.When the update finishes, press back a couple of times then select the option to reboot your Streak.
17.The Streak will restart. It will take about 5 minutes to complete, but you are now on the latest v1.5.3

at moment i am following the qdl guide to getting the steve rom on my phone so will let you know how it has gone but with that guide the installation at moment seemed seemless now got to see if it goes off the dell logo after a while if not got to recovery but lets hope

no luck so far
stuck on the logo screen but asked for help now its a waiting game

Cheers for that!
Sent from my Dell Streak using XDA App

Is it necessary to use QDLTool to get to the pre-release 2.2 if I am on 1.6 or can I just follow steps 1-17?
The reason I ask is that QDLTool for me just stops at "Check version ... " so I have not been able to complete running it.

i dont know if it is necessary
are all the drivers installed?
i used to have a prob where it kept failing me but all i had to do was change usb port
and got it working but i was running 2.1 stock at the time but that was buggy and crap UI
have you tried just puting 2.1 or 2.2 on your SD card and updating that way

i finally got my streak sorted
i started from scratch
first i installed clockwork mod using fastboot
then installed very version of steves roms in order starting with 1.1.1
and worked my way down and when i installed 1.5.0 i then ran flashed the amss that is required if you want to get the newer versions then installed the rest of the updates and when i got to 1.5.3 i also installed the camera fix
i found it best to put all steves rom zip files onto your SD card at once then it saves having to keep putting one of after another
also after every update leave the phone for a few mins because it does take a lil time to sort the updates out
THE ROM UPDATES (at top also has the AMSS that need flashing)
http://streakdroid.com/?page_id=15&category=1
Camera fix and the comandlines for the AMSS update
http://forum.xda-developers.com/showthread.php?t=802405
clockwork
http://streakdroid.com/?page_id=15&did=9

I don't know if all the drivers are installed. Is there a way to check? I cannot even get into FASTBOOT (POWER + CAMERA) mode and the Streak is just in an infinite reset loop.
Just a note, the older StreakFlash QDLTool completes completely but the newer one in Repairtool just sits infinitely at "Check Version ... "

what operating system you using on your computer

rahbone said:
what operating system you using on your computer
Click to expand...
Click to collapse
Nice of you to ask, as indirectly that was the issue. I outlined it over at the forum mydellmini dot com. Sorry, cannot post hyperlinks as yet. Issue has been resolved. Looking now to load 1.5.3

why not spam a few more posts on here then u can do links when u want 2 in future
you just need 3 more posts i believe the you can do links

QDL repair tool question`

Mod...if this belongs in the android development, please move it.
Does anyone know if you can put a different image file using the QDL tool?
I was wanting to play around with Steve's 1.5x version, but don't want to brick
the phone. The QDL tools is just too easy to use.

I had suggested the same thing at streaksmart forums and nobody seemed inclined to consider it. Looking through the files included with QDL it seemed like it might be possible to do this. Just based on file names, that is.
I am not a dev, just a newbie, so maybe smarter brains would be able to advise.

No smarter here but why not back up the tool you have now, then replace files on copy and try it. If it doesnt work just reuse original tool to get you back. Just out of curiosity what version did the tool give you initially. Cause mine put me to Steves 1.4.6 so if yours is different then its likely good to go.
Sent from my Dell Streak using XDA App

I believe QDLTool validates the images before it will load them, so I don't think simply replacing them with the ones from DJ_Steve's rom would work .. then again, its not something I've tested yet either

Mine shows up as:
version 2.2
Baseband GAUSB1A130500-US
Kernel 2.6.32.9-perf
OEM GAUSB1A130500
Build 10688
brunswick000 said:
No smarter here but why not back up the tool you have now, then replace files on copy and try it. If it doesnt work just reuse original tool to get you back. Just out of curiosity what version did the tool give you initially. Cause mine put me to Steves 1.4.6 so if yours is different then its likely good to go.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse

Does anyone know who developed the QDL tool?
Perhaps we could get a sticky or something for that, if it can be developed
further. Once you get the driver problem worked out so windows 7 works with
it, it's pretty much a one click solution to flashing.
kantras said:
I believe QDLTool validates the images before it will load them, so I don't think simply replacing them with the ones from DJ_Steve's rom would work .. then again, its not something I've tested yet either
Click to expand...
Click to collapse

anyone think about emailing the guy?? [email protected]

brunswick000 said:
No smarter here but why not back up the tool you have now, then replace files on copy and try it. If it doesnt work just reuse original tool to get you back. Just out of curiosity what version did the tool give you initially. Cause mine put me to Steves 1.4.6 so if yours is different then its likely good to go.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
QDL drops you at Official 2.2 (build 10688) , BB 305. How did you get 1.4.6 out of it? Did you swap the update files as you suggested?

i believe this should answer your question
Beyond QDLTool
Using QDLTool will get you to a pre-release of v2.2. From here, you’ll want to upgrade to a newer release. The two options that people tend to choose from are to either go up to the official v2.2 ROM from Dell, or install DJ_Steve’s latest ROM.
Official ROM
If you want to go to the latest official ROM from Dell, simply set up your wifi connection, then go to Settings -> About Phone -> System updates. The latest update can then be downloaded and installed, updating your Streak.
DJ_Steve’s latest vanilla ROM
If you want to upgrade to the latest vanilla ROM (1.5.2), either from the QDLTool install or from the latest official build, you can follow these steps:
1.Go to the downloads section and grab StreakMod Recovery, the latest 1.5.2 Update and the AMSS for 1.5.1+ (the update and amss are under Roms, StreakMod Recovery is under Recovery)
2.Copy the update-1.5.2.zip file onto the root of your SD card.
3.Extract recovery.img from the StreakMod recovery and place it, along with amss.mbn, into the same directory as QDLTool (QDLTool has a copy of fastboot)
4.Shut down your Streak, then hold down the camera button (all the way) as you turn it back on.
5.The screen should turn white; press ‘Fastboot’ in the top right hand of the screen.
6.Plug in the USB cable – the Streak should now display ‘FASTBOOT_MODE’ at the bottom of the screen.
7.Open a command window and use ‘cd’ to change to the same directory as qdltool.
8.Run: fastboot -i 0x413c flash recovery recovery.img
9.Run: fastboot -i 0x413c flash amss amss.mbn
10.Run: fastboot -i 0x413c reboot
11.As the Streak starts to reboot, hold down both volume buttons.
12.The recovery menu should come up; select option 2 (Upgrade)
13.A Dell logo and an exclamation mark should appear; press power or menu to open StreakMod’s main menu
14.Select ‘apply sdcard:update.zip’ then ‘chose zip on sd card’
15.Find the update-1.5.2.zip file, select it and apply the zip.
16.When the update finishes, press back a couple of times then select the option to reboot your Streak.
17.The Streak will restart. It will take about 5 minutes to complete, but you are now on the latest v1.5.2

Help!!
Hey I'm hoping that you guys can help me. So I picked up a streak from a buddy a few days ago its running 2.2 build 10688 and bb 305 I would like to go to dj steves 1.6.1 because I hear that's the best one to run and from what I have looked up it gets highest scores in bench mark. Anyways I dont have pc I have a mac, so I have 1.5.1 cause streakdroid says you have to do 1.5.1 then 1.6.1 next I have amss.mbn 1.5.1+ or whatever and the recovery.img. So my question is i open terminal and put the phone in fast boot and plug it in blah blah it says fast boot mode on the bottom left so I know it is connected but what do I put in the command as the path so I can access it to flash everything over because I have no clue what the path is and no clue how to figure it out because there is no how tos for a mac.. Thanks for whoever will help me id love to get this streak going fast and smooth! Thanks everyone!!! One other question I also need to know where to put the amss and recivery.img iv already put 1.5.1.zip and 1.6.1.zip on the root of my sd!! Thanks again!!!!!!!

[Q] Can't use recovery, but fastboot works fine

On my phone, can not boot into recovery mode. No matter how many times I try to use the home and power button. I even went to youtube to watch a video on it to make sure I was doing it right.
I have installed clockwork recovery via fastboot many many times, using different versions. I also have tried it with different roms installed.
I wonder if it is because the first rom I installed was superfast froyo, which says recovery is not working. I also installed swiftdroid 2.0, which also wouldn't let me use recovery. Though I forgot to try to reboot into recovery from the android menu when I had swiftdroid installed.
It's not a big deal anymore, since I accomplished what I wanted. I installed Froyo Optimum V3 with data2system via fastboot, and it worked fine. I now have 245mb on the phone so it is all good. When I installed it I just installed boot.img, cache.img, and system.img each to their respective partition, and data.img to userdata partition. So far, everything works fine.
However, it does bother me a little that recovery isn't currently working, I'm sure I'll find the answer sooner or later. Anyone have any ideas?

Hello as I can see you recently uppdated from stock 2.1? Then something went wrong and you used a rom that does not support recovery. Please tell what .kdz you flashed
EDIT: http://forum.xda-developers.com/showpost.php?p=13205397&postcount=26

lavero.burgos said:
Hello as I can see you recently uppdated from stock 2.1? Then something went wrong and you used a rom that does not support recovery. Please tell what .kdz you flashed
EDIT: http://forum.xda-developers.com/showpost.php?p=13205397&postcount=26
Click to expand...
Click to collapse
All Fastboot ROMs support recovery regardless of their version.
Try this:
Go into fastboot and open a Command Prompt and type:
Code:
cd <location of SDK Tools>
fastboot erase recovery
fastboot flash recovery nameofrecoveryimage.img
fastboot reboot
This fixed my problem I had when I first flashed fastboot onto my GT540, don't know if it will work for you or not, but its worth a try
Hope it helps,
Jack

Original poster here. Changed name for obvious reasons.
I think something did go wrong during the initial upgrade to 2.1. I forgot to mention a couple of things now that I think about it.
I used this link for most of my information:
http://forum.xda-developers.com/showthread.php?t=1032744
I first installed the european rom listed in that thread via KDZ. I never get an LG screen during boot up. I don't remember if the stock 1.6 had an LG screen or not. I think upgraded to what was then called "super fast froyo 2.2." I then wanted to install a rom with data2system, when was when I realized restore wasn't working. I then tried to downgrade back to the european rom via KDZ. It didn't work. Whenever I booted the phone, all I got was a black screen similar to the fast boot screen. I re-installed the european rom via KDZ, same results. Installed "swift droid 2.0" via fast boot, no recover. Then I installed I installed Froyo Optimum V3 with data2system, via fastboot, which is where I am now, still with no lg screen during boot-up.
Thanks you for your help, and i will try the link posted by JackG256 when I have time.

typci said:
Original poster here. Changed name for obvious reasons.
I think something did go wrong during the initial upgrade to 2.1. I forgot to mention a couple of things now that I think about it.
I used this link for most of my information:
http://forum.xda-developers.com/showthread.php?t=1032744
I first installed the european rom listed in that thread via KDZ. I never get an LG screen during boot up. I don't remember if the stock 1.6 had an LG screen or not. I think upgraded to what was then called "super fast froyo 2.2." I then wanted to install a rom with data2system, when was when I realized data to system wasn't working. I then tried to downgrade back to the european rom via KDZ. It didn't work. Whenever I booted the phone, all I got was a black screen similar to the fast boot screen. I re-installed the european rom via KDZ, same results. Installed "swift droid 2.0" via fast boot, no recover. Then I installed I installed Froyo Optimum V3 with data2system, via fastboot, which is where I am now, still with no lg screen during boot-up.
Thanks you for your help, and i will try the link posted by JackG256 when I have time.
Click to expand...
Click to collapse
Actually the link you see was the one posted by me lol i recently posted on my reference guide thread aboutcases when you brick your phone and possible fixes, there is one for your problem.
Also as i have read plenty about this kind of things i can assure that not all the kdz with fastboot support recovery that is a myth , there is a recovery_rom.kdz, there is out.kdz and other .kdz roms that has a purpose.
My theory is that not all the LG GT540 are the same thing, why? because simple if you read all the threads of users that have had issues with their phone saying this ROM worked for me and then another user saying that it didnt for him but other rom did the job. There are so many .kdz ROMS and even more are been released, but modified to support fastboot and recovery.
So if you do a bit more of research you can find original stock .kdz roms and their modified version requested by many users marginalized because of their location.
Hope you fix yor phone with the one posted in my thread, good luck! you will need it.

I think you are correct about not all gt540 are the same. I have an "international version." When I was installing drivers, it was a very complicated issue, and most of the drivers I found didn't work. I had to use the drivers supplied by LG via their lgmobile update program, to get my phone interact correctly with my computer. Luckily, I have alot of experience with flashing and custom roms for other electronic devices. So I know how to handle bad flashes, and other problems for the most part. Right now, my gt540 is fine, no recovery, but the custom rom is working just fine. Next time I want to swap out custom roms, probably when the android 3.3 builds become very stable, I'll play around with some KDZs and try to get recovery working.
Thanks for your help.

If you want to try with more kdz then you should try with one modified by mur4ik for data2system method.
Sent from my GT540 using XDA App

Rogers Recovery Img

Can anyone help me out here. I need the stock recovery.img, or one that is compatible with the Rogers 2.2.1 update "Streak_339_14896_32.pkg"
Need to return a defective unit that has Steves Rom on it and id like to return it to stock first for warranty reasons.
Please help
Bit confused about the MultiRecoveryFlasher too. Does this flash the recovery and the update.pkg all in one? So many ways to do things it becomes confusing for beginners. Any help is sincerely appreciated.

http://mirror2.streakdroid.com/manii/339/recovery.img

http://forum.xda-developers.com/wiki/index.php?title=File:Dell_Streak.png#Official
The WIKI is a great resource, check it out sometime.

So with this recovery and the original udate I should be able to flash my steak back to orig recovery and stock 2.2 with the repair tool the same way I went from that original rom to Steve's 1.9.0?
Sent from my Dell Streak using XDA Premium App

Not Android Development
Please post in the correct Forums
Moving to General

Firstly, sorry for posting in the wrong section. First time for that.
Secondly, can anyone answer my question in regards to using the QDL Tool to flash the stock recovery.img that corresponds to Rogers official 2.2.1 update?
Or, can I just flash the recovery.img in fastboot mode and then apply the official update via ClockWork?
Need to get rid of clockwork too though so Ive got myself all confused
The multirecoveryflasher seems like it would do everything I need, but it doesn't include the img file I need for Rogers. Unless one of the ones in there is compatible??
Man, I wish I paid more attention in info tech in school

I don't think you can flash a stock recovery with cwm. Use multi recovery flasher.
Sent from StreakZilla using XDA app.

@ eSZee,
Im inclined to think that you are right about that. My only concern was that none of the options in the multirecoveryflasher are what I need. I have the official rogers recovery img and the official Rogers update pkg, so I need to know if I can somehow add them to the program or not. Or, alternatively, can I just use one of the existing options in the program and then update the rom in the stock recovery by choosing the Rogers update pkg? Sooooooo confused. Anyway, ive got to get it figured out as I only have a certain number of days to ship the unit back, otherwise they charge you full price for it.
To complicate things futher.....the screen is F'ed so I cant make anything out on it. I can see the right side of the screen....a bit. Not ideal since in landscape mode everything is listed on the left. Uggghhhhh!

brunswick000 said:
Or, alternatively, can I just use one of the existing options in the program and then update the rom in the stock recovery by choosing the Rogers update pkg?
Click to expand...
Click to collapse
rename the rogers img update.pkg and pop it on the root of your sd.
In fastboot, flash the recovery menitoned in Manii's post above.
the command should be:
fastboot -i 0x413c flash recovery recovery.img
or similar. Then:
fastboot -i 0x413c reboot
Hold in both the up and down volume keys to enter recovery and update from sd card. I think its the 2nd option, but i'm sure someone will correct me if i'm wrong.

Ok got the correct recovery img flashed no problem. Now my question is of a more "blind" advise type. I can boot into recovery mode. Generally when you do so the option to "update vie update.pkg" or whatever is already highlighted and you just go ahead and push the camera button. Now this is where I need help. Since my screen is basically a blur I need to know how many times to push the up or down volume keys to navigate to the correct option to select "install:update.pkg", and then again how many times to get to the update.pkg in the following screen. If I can get this info from someone still running a stock recovery img I can finish, and ship this baby back for warranty without worry.
Pllllleeeeaaaaaseeeeee someone help me out.

Ok so I found some info that basically says what order to push what buttons and I think that ive successfully returned my phone to stock.
My new question.....Is there any way short of turning on the device and checking in the settings to see the "about phone" info? I cannot see any of it to be sure I was successful. Anyway to hook it up to the computer to gain this info?

Turn on your phone and check. After that restart into recovery and reset to factory defaults. Better safe than sorry.
Sent from StreakZilla using XDA app.

I might be in a similar situation, I have a Streak running Streakdroid 1.8.1 that I nandroid-flashed back to the original v2.2 baseband GAUSB1A13800 build 10688 (the version that is installed when you use QDLTool)
I want to get my Streak as close to stock as possible for waranty issues (ear speaker is crackling / dieing).
Will flashing the above recovery.img bring me to the original Rogers baseband ? I don't have any nandroid bkp of v1.6 because it was impossible to install CWR or Streakmod R on that version (see all my old post on the topic).
Alternatively, if anyone has a nandroid backup if their Rogers system with Streak_339_14896_32.pkg , that would also be appreciated ;-)

I doubt you'll be able to find the stock 1.6 ROM. But, you can put the Rogers 2.2 update on there. That's what I've done twice now and have no issues from Rogers. It is the 339 ROM, and I'm quite certain you can find it in Manii's index of ROMs. Just search it with google - index of manii 339. Should be your first hit. Good luck. At least you don't have to do it without being able to see the screen.
Sent from my Dell Streak using XDA Premium App

[Q] Taboonay 2.1 suddenly unable to connect to WiFi

I flashed Taboonay 2.1 to my Icona Tab A500 last night. Everything was great. I retrieved all my usual apps and previously purchased apps back down from the market, network was working fine. Turned on tab this morning and it is unable to connect to wifi. Keeps trying several times and then says the attempt has been disabled. It sees the Motorola Surfboard but can't connect. I thought I would try to re-flash since the .zip was still on my external SD. I attempted to boot into CWM but it won't come up. It just says loading image and never goes into CWM, that's it. So, I have no ability to connect by Wifi and am unable to download Acer Recovery Installer in order to re-install CWM. Apparently the CWM image is corrupt. The CWM ROM Manager Premium is still on my desktop but it can't do any sort of recovery because if I bring it up and choose "_install .zip from SDCard" it reboots into recovery mode and can't load the recovery image either. Does anyone have any ideas? Taboonay 2.1 is Android 3.2 it has the xda ad hoc wifi patch in it (which has never been quite right) in my opinion. So I found a copy of the 3.1 wpa_supplicant file and installed it into the /system/bin folder using root explorer to set the permission correctly after renaming the one installed by Taboonay to wpa_supplicant.old and re-enabled Wifi. Still it would not connect. The only difference I could see was that it no longer could see ad hoc wifi networks but still would not connect to my infrastructure wifi although it could see it. This particular wpa_supplicant file that I went back to came from Acer 3.1 stock ROM and worked perfectly under 3.1. I'm basically out of business at this point with no network and no way to flash a new ROM or restore a backup. Does anyone have any idea what to do next. Has anyone else had wifi issues with Taboonay 2.1? I did see an update 2.1b for Taboonay 2.1, but I can't get into CWM to apply it. I might as well be totally bricked. I can connect to the tablet and have full access to the 2 SD cards via Windows and a USB cable, but I can't download Acer's Installation Recovery from the market from a Windows browser. I'm sure its not the router because 3 Windows 7 SP2 Computers can connect to it and so can my wireless HP printer. Everything seems to be a Catch 22. Help! Anyone had trouble with Wifi on Taboonay? Does anyone have any ideas or how to get out of this situation? Any suggestion would be appreciated.

Hey gradyzero sorry to see the trouble buddy but the tabooney 2.1b update is made for wifi updates issues and SU perm, im currently running tabooney 2.1b and full with new market and i have no issues. As far as the recovery have you tried new THORS 1.5 cwm can you try using adb to push recovery.img to the tablet, or maybe using terminal emulator theres a new 1.5 cwm update you can try doing that. just extract recovery img to internal sd and go into thors website "google it" and follow every step except for #3
good luck buddy if not hit me up side PM ill see what i can do atleast to try to get recovery back

I don't think I had restored the terminal program back yet let me check. The apk is something I haven't tried. Thanks for the suggestion. I have thor's 1.5 update on my SD card but not quite sure what use it can be until I can get the ability to connect to boot up in recovery. I'll go to his web site and read the instructions there again, overlooking step 3. I have read them once before but didn't have this problem so I just grabbed the download and planned to update it after the Taboonay flash. Figured it would just have to be redone after the flash anyway. Thank for you idea. I should be able get an .apk onto the SD from Windows and should be able to install it. Again, thanks much buddy. I'll post back to this thread what the outcome is.

Restoration of boot image doesn't resolve the problem.
Okay Crashpsycho I download an Acer Install Recovery apk and CWM Launcher 1.0.0.0 apk. Both appeared to install correctly. Acer Install Recovery came up and I was able to choose to install CWM 1.3.4 image. However, when I reboot into recovery I still stop at "Booting recovery kernel image". So reinstalleing the CWM 1.3.4 image that the Acer Install Recovery show as an option didn't fix anything. Any ideas about why recovery might stop when loading the kernel image? When it says "the Kernel Image" is it talking about the base Linux kernel? I seem to recall reading somewhere that Taboonay replaced the Linux kernel with its own version. Is that true? I thought maybe the recovery image was corrupt but assuming the Acer Install Recovery really did reinstall the recovery CWM 1.3.4 image as it said, then something else is wrong. I did manage to get a terminal program installed so I'll try your second suggestion to force the CWM 1.5 image using adb. If Taboonay really did replace the stock Linux kernel, I have no idea how to recover from that. I'm not quit sure exactly where a recovery image goes and so I suspect that adb will ask for the destination. Maybe I'm wrong but do you know? Does adb know automatically where to install a recovery image? If the Linux kernel has to be replaced then I could get bricked if Tabtoonay won't boot up because a different Linux kernel is installed. What is your thinking about all of this? This is getting heavy. Thanks again for your help. Anyone else that has any fresh ideas is encouraged to jump in here and post to this thread. I'll post back here with the results once I try to force the CWM 1.5 image.

Installing other kernel solved issues for me, using thor kernel 3.5

installing 1.5 use terminal emu, extract the recovery.img from zip folder and place on root of sd go to thors website tegraowners and follow all steps except #3 and that will force 1.5 to tablet. have you tried installing stock recovery image using the acer recovery app

So Sector51 are you telling me you had the same issue. Where booting into recovery locked at loading kernel image? I'll try your suggestion. If it doesn't require you to be able to boot into recovery which I can't. Thanks for the tip.

Crashpsycho, I just completed the terminal method you suggested and followed all the instructions except #3 wihch was a mount, if I remember correctly. I extracted the image file from Thor's 1.5 put it on my external SD by copying it from Windows and then went through Thor's instructions step by step. Recovery boot still hangs at loading kernel image. Thor actually says to install itsmagic into /data/local directory both in his adb push and in his terminal emu methodology. There is no copy of itsmagic in his distribution and I can't find such a file on my tablet. BTW, I also tried the adb push from Windows but the recovery image is pushed to the SDCard so I assume he intents for me to then boot into recovery and to install it. So that's not going to work unless I have itsmagic. The Windows adb method also pushes itsmagic out to the /data/local folder but I can't complete that part and I think it is critical to both methods. Any idea where I get this file? Google search returns nothing except that one entry has been removed due to copyright issues. I think that it is the key to installing from the SDcard. I remember seeing that file on my rooted 3.1 but apparently Taboonay removed it. Can you enlighten me on itsmagic? What is it? Where do I get it? I have currently installed the Stock USA 1.31.06_COM_GEN1 recovery in Acer Recovery but reboot into recovery still hangs at loading kernel image.
This is another side issue but do you know if it would be possible to install the Taboonay 2.1b manually. Is it an update zip or a ROM flash? I'm beginning to think that if I could get back my Wifi back I would just forget the recovery reboot as a last resort. I'm going to investigate what is involved in the kernel update suggested by Sector51. But basically I'm not doing anything else until I can fully complete thor's 1.5 update. Man, I've spent 3 entire days trying to resolve this. I'm going bonkers. It certainly gives me a bad taste for Taboonay that probably isn't deserved because I don't see other post about this particular issue. So please educated me on itsmagic and we'll go from there. Thanks dude for all you help.

I found a copy of itsmagic here on xda. Downloaded it and completly went through the terminal emu process exactly as posted on Thoor's Website for 1.5. Everything seemed to work this time including the execution of itsmagic which spit out a nasty message to Acer something about Its Magic. Acer why did you say the bootloader is locked when it isn't? So this tells me that everything should now be good. I rebooted into recovery and this time it acted a bit different. It still said loading boot kernel but then in about 30 seconds rebooted back to Taboonay automatically. So I'm stumped. Does anyone have and new ideas? BTW, the 1.5 recovery image has a date of 29 Feb 2008. Is that right?

Finally suceeded with 1.5 Recovery, Thanks
This message is specifically addressed to Crashpsycho and Sector51. After four attempts I was finally successful at getting Thor's 1.5 recovery booted. I immediately backed up the current version of Taboonay 2.1 and then applied the 2.1b update. Everything in term of recovery is now good. One problem, the update did not fix the the WiFi problem as I am still unable to connect via WiFi. But that's a totally different issue, which I can deal with. Meantime thank to both of you for generously taking you time to help me resolve this recovery boot problem. I would still like to know what I did wrong during the original ROM flash to Taboonay 2.1 to destroy itsmagic. As well as what I did wrong in my first 4 attempts at repairing the recovery. However, I won't dwell on that as I need to proceed on with working on the WiFi issue. Thanks a million to both of you for all your help and suggestions. You are both what makes xda a truly wonderful and unique place for lovers of mobile devices. I am a programer and web developer and I hope I can contribute eventually to the growing Android mania. I personally think it will eventually dominate the table and phone market, if it already hasn't done so retail wise. I'll return to lurker stats for a while and learn more about the SDK while I try to resolve the WiFi issue. One side note, I recently flashed my HTC HD2 phone from Window mobile 6.5 to Widows mobile 7.5. That involved the flashing of 3 ROMs and then upgrading the OS. It runs beautifully and was much more complicated than what should have been a relatively simple task of upgrading to Taboonay 2.1. I'm sure I missed some small detail that caused the problem with the Icona Tab. You guys helped me greatly and I hope to be able to return the favor at some point. So I consider this issue closed and the moderator should feel free to consider it resolve. xda is power to the people.
Final Note: The adb push from Windows was the last attempt and was apparently the one that successfully fixed everything. As a certified Unix Engineer and somewhat of a Linux expert I opted to use the terminal emulator technique since I knew the commands and what they were doing, but typing in a long stream of commands is always more prone to user error. My advice to anyone else with this problem is to install the Windows Android SDK and use adb push to update as it appears the most recent version takes care of most all the permission issues and is almost fool proof. Again thanks to you guys. The Problem is resolved. Mister Moderator consider this thread closed and resolved.

great job man atleast you got the recovery to work. i cant say much for the wifi issue or what happen to recovery i would say if anything the issue must have came from the wifi ad hoc patch/change but im not fully technically skilled to say that it really was but great job hope you get it back up and going

I am enbrased to admit this but I feel it only fair since so many people attempted to help me. I've search around and apparenty no one has run into this here yet, but it needs to be posted for future reference. Most all of my boot recovery issues took place while the tablet was docked in the Acer A500 docking station. When I have trouble in recovery mode, with the image loading message just hanging up, 100% of the time removing the tablet from the docking station resoves the problem. Just thought I should pass this on. I know it is stupid that I didn't realize this before now. If you are docked, don't boot into recovery' not even with1.5 installed. I have no idea why this is true, but it is. If you have the Acer docking station DO NOT BOOT IN TO RECOVERY WHILE DOCKED!

Open up Rom Manager and click "Fix Permissions" let it do its thing then restart. That worked for me.