Database Develop

My G1 is stuffed, but not bricked. Mount from Recovery? Wave invites for help.

Ok. So yesterday night I was trying to give my G1 a new ROM. I wasn't really concentrating. I was tired. I've done it successfully before. I was following the instructions on Cyanogen Wiki for phones already with custom SPL and OTA.
Something screwed up, I did the firstROM a while ago so it probably wasn't the right one. Maybe it needed deathspl.
Regardless, it is now stuck on the T-Mobile G1 screen (and its stuck, I've left it for an entire night: still stuck) . I can take out the battery and boot into recovery mode. So at this point I basically need to mount my SD through USB (i dont have adapter) so I can start from scratch with SPLs, Radios and Images. This is the problem.
I've read you can do it by pressing Alt+X, going into console/terminal and type some commands in. I press Alt+X but nothing happens. I'll tell you what happens when I do other things:
---------
Alt+S= E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (Invalid argument)
Can't mount sdcard
Alt+A= <<same thing except for last line:>> E:Can't mount SDCARD:
Move apps+dalvik-cache to SD: Error: run apps2sd via adb
Apply sdcard:update.zip: Can't mount sdcard
Apply sdcard:choose zip: E: CAn't mount SDCARD:
Wipe data/factory reset: Data wipe complete.
Nandroid v2.2 backup: Can't mount sdcard
Nandroid v2.2 restore: Can't mount sdcard, aborting.
Format SD : fat32+ext2+swap: Format complete!
Format SD : fat32: Format complete
Repair ext filesystem: Error : run e2fsck via adb!
Convert ext2 to ext3: Error : run upgrade_fs via adb!
Fix package uid mismatches: Error : run fix_permissions via adb!
-----------
Alrighty. So its royally stuffed up.
Please help! I'm telling myself its not bricked, because it has small but definite programs and calculations running.
It mentions adb, and I have used it in the past to skip through a tutorial (back when you couldn't skip through it) because it needed internet connection and at the time I didnt have data transfer on my SIM, but I did have Wireless. How exactly I did this escapes. Do I need to download anything?
I have no idea if this helps, but I was trying to think of a sort of prize for anybody to help and I have Google Wave invites. Whether thats a big deal or not, I have no idea.
Please help!

Well you can assure yourself that you are not bricked.
First check your SPL and Radio.
If they are:
SPL=1.33.2005
Radio=2.26.19.26I
then your good in that area.
you just need to wipe everything and retry the ROM.
If not then you might want to get the latest stuff and try again that way.

Thanks
Thanks.
But how do I check?
I can't get into the proper Android OS, the three states my phone can be in are:
Off
Stuck on T-Mobile Screen
Recovery Mode
Also, how can I get some new stuff on my SD card if I the only things I have are: the phone described above (i.e. the only workable state being recovery mode), an SD card and a USB cable.
Whats your email so I can send you an invite if you want it?

lachy95 said:
Thanks.
But how do I check?
I can't get into the proper Android OS, the three states my phone can be in are:
Off
Stuck on T-Mobile Screen
Recovery Mode
Also, how can I get some new stuff on my SD card if I the only things I have are: the phone described above (i.e. the only workable state being recovery mode), an SD card and a USB cable.
Whats your email so I can send you an invite if you want it?
Click to expand...
Click to collapse
To see you SPL and Radio do this:
Turn off phone
Hold Home and End Call buttons.
If you see:
Hboot-1.33.2005 or something like that then that means that you have the latest SPL
Radio-2.22.19.26I then you have the latest Radio too.
First we need to check to see what your SPL and radio is before you try to do anything that involves flashing ROMs
What recovery image do you have?

Can't see it
When I press Home + End Call I can see is:
Android System Recovery:
<the options I described before, with their errors>
The above is in green font, the background is black with an HTC logo, at the very bottom is white font that says this:
Build: RAv1.2.1G
Sorry for not replying as fast as could. I mega-ly appreciate this so I'll try to be more vigilant.
I'll look around for other key combos to get some more info.

lachy95 said:
When I press Home + End Call I can see is:
Android System Recovery:
<the options I described before, with their errors>
The above is in green font, the background is black with an HTC logo, at the very bottom is white font that says this:
Build: RAv1.2.1G
Sorry for not replying as fast as could. I mega-ly appreciate this so I'll try to be more vigilant.
I'll look around for other key combos to get some more info.
Click to expand...
Click to collapse
And I just did that! I pressed back + home and got a white background with three skateboarding androids with this text:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA*****)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
CLEARSTORAGE
Delete all user data?
<ACTION> Yes
<POWER> No
--------
Well thats atleast one step we've bypassed. Stay with me here.
Alrighty so I know the Radio and SPL, and apparently they are up to date.
What next?

From your above post, it seems your SDcard is not being read by your phone. Not sure what the issue is there.
But, if you can get it recognized by the phone, try the following:
It seems you have ADB set up, you may be in luck.
Connect the USB cable in recovery and type these commands on cmd prompt in Windows:
adb shell
ums_enable
This should mount your phone to your PC.
You can now move in necessary files to save your phone.
I suggest doing a FULL WIPE, then reflashing a ROM such as CM 4.2.14.1 (latest build).
If that doesn't work, you may have to start over by flashing DREAIMG.nbh (RC29), flashing latest radio, flashing SPL, DON'T REBOOT, then flashing rom RIGHT AFTER SPL.
Good luck, keep us updated.

Nearly There
Ok. So I got adb up and running.
I ran adb devices and it was blank so I followed part 2 of:
<do google search for "the unlockr hot to set up adb usb drivers for android devices>
After reinstalling drivers via USBDeview:
My Device Manager is now registering my phone as the Android Composite ADB Interface, but when I run adb devices it still has a blank list.
Keep in mind I am in recovery mode.
When I try and run adb shell, it errors with 'no device found' so I need to do this devices command successfully.
Does anybody know whats happening?

lachy95 said:
Ok. So I got adb up and running.
I ran adb devices and it was blank so I followed part 2 of:
<do google search for "the unlockr hot to set up adb usb drivers for android devices>
After reinstalling drivers via USBDeview:
My Device Manager is now registering my phone as the Android Composite ADB Interface, but when I run adb devices it still has a blank list.
Keep in mind I am in recovery mode.
When I try and run adb shell, it errors with 'no device found' so I need to do this devices command successfully.
Does anybody know whats happening?
Click to expand...
Click to collapse
Try running it while the Phone is on instead of recovery.

Say run terminal and post the output of:
cat /proc/cmdline
By the way you can still flash images using fastboot mode.

Its stuck
When you say 'on' do you mean on the T-Mobile Screen?

Thanks
Thanks again guys this is really good and I think we're getting close. OK. Here's an update as of right now:
My computer recognizes my phone in T-Mobile Logo, Fastboot (or thing with three skating Androids, Home and Back), and Recovery.
When I cd to my tools folder I can run adb commands but when I run 'adb devices' it shows:
List of devices attached
....
No serial number or anything. I've reinstalled the drivers.
When I do the command 'run terminal' it says 'run' is not recognized as an internal or external command blah blah
This is the same with 'cat /proc/cmdline'
I still can't run terminal with Alt+X in recovery mode (at least, nothing happens)
My phone cannot turn 'on'. It is stuck on the T-Mobile Screen.
What should I do?

lachy95 said:
When you say 'on' do you mean on the T-Mobile Screen?
Click to expand...
Click to collapse
Normal boot.

That doesn't work.
How can I see it in adb devices?
Argh!
Any ideas just throw them out there.

Have you tried another sdcard? That's the first thing I would try if the phone is complaining about not being able to read it.

Check ur drivers.
sounds like u need to update them.
Try the attachment

Technochris1 said:
Check ur drivers.
sounds like u need to update them.
Try the attachment
Click to expand...
Click to collapse
It works!
Sweet Technochris1, Sweet, sweet person. Thou hath skills and prowess!
I uninstalled the drivers then installed yours. Now adb devices is functioning and sees my device! Now to mount, transfer and fix! I'm indebted to you greatly, for you fixed my phone and everybody else on this thread! Thank you so much.

Usb Driver Problems

Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying

magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one

I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.

mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up

magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".

nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything

Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.

alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?

http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery

when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right

have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone

tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"

I believe you can also try "./fastboot-mac flash recovery ./recovery.img"

Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!

you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829

fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder

[Q] zio 2.2 update failed

keep getting this message even though I have installed drivers..pc says they work..phone registers that usb is connected..debugging is selected...what am I doing wrong here...thanks
Update Failed
Please check the PC side and devise side status.
1. Power on your devise and select USB debugging on your phone
-Press Menu and then tap Settings>Applications>Development
-Tap the USB debugging check box if it's not selected
-The USB cable must be connected to your devise and PC
2. Check your driver is installed correctly.
3. Close all other applications in the device and PC.

is your antivirus/internet security shut off?
Have you removed all instances of the drivers (confirmed through device mgr&ctl panel), rebooted an installed the drivers again (making sure phone is not connected until post-install)?
What OS are you running?

running windows7..will check on the antivirus...try reloading USB drives...back in minute with update...lol

32bit or 64bit?

nt sure...wife's laptop..window 7 home premium? Edit...64 bit..sorry

topherdownfrown said:
nt sure...wife's laptop..window 7 home premium? Edit...64 bit..sorry
Click to expand...
Click to collapse
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.

will try after work..thank you..post result later.

Spz0 said:
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.
Click to expand...
Click to collapse
Exactly. I tried for 4 hours on my Windows 7 Home Premium 64 bit machine with no luck. Drivers were installing properly from the CD included with the phone, but the update would always fail at 98%. First try on my older Vista 32 bit machine the update went right through the first time with absolutely no issues.

Don't give up
Spz0 said:
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.
Click to expand...
Click to collapse
I agree. However, I got the "failed to update" message even when I tried to install using my desktop computer that's running Vista32. BUT, then I installed the drivers (the ones that came with the update) to my Toshiba netbook (running Windows 7 Starter). The first update failed, same as before. So I disconnected my Zio, and rebooted it. I plugged it back into the netbook, ran the update installer, and it installed in like 7 minutes. Works great too. So far none of the issues that have been brought up on other threads.

edit: froyo 2.2.1 installed successfully on the Zio in less than 10 mins. i forgot to unmount the damn sd card and this was the really why my phone froze on the "modem download mode" and why the install GUI on pc dissapeared.
piece of cake! thanks a lot guys for posting this update and for creating the Zio forum.
installed the zio m6000 drivers directly from retail cd and ran the kyocera updater. i'm running Win XP on an old-school Dell optiplex.
anyway the update has been taking up at least 20 mins now. the screen on my Zio is black and the message "modem download mode" (i figure that its the tethering part) appears.
why is this update taking so long?

I've heard of varying times. Myself, it only took 6 mins or so, others had to wait more like 20-30.
What does the update program say?

OMG!!!! Its happening to me too! HELP!!! I get error code [0x50015001]. SDcard is out, uninstalled modem driver and installed the one that came with the upate, and still 98% then failed. Any help PLEASE?????

itrustno1 said:
OMG!!!! Its happening to me too! HELP!!! I get error code [0x50015001]. SDcard is out, uninstalled modem driver and installed the one that came with the upate, and still 98% then failed. Any help PLEASE?????
Click to expand...
Click to collapse
don't panic!
you have to follow the directions straight to the teeth on the install instructions.
1. make sure that you have the correct Zio usb drivers installed on your PC.
2. when the installer window (GUI) pops up, read the instructions. make sure that USB debugging is 'checked.' usb debugging option is the settings.
3. make sure that you unmount your sd card (not pulled out).
4. i reset my Zio to factory default right before i updated 2.2
5. if the update installer didn't appear at first then run it again and watch the progress.

Turn your phone off, Hold the volume + (up) and - (down) and the power button to place your phone into Modem Download Mode.
Make sure you have the Kyocera M6000 Drivers installed on your machine properly first. Once you are sure the drivers are installed correctly you can plug your phone in... wait a minute or so before you launch the update file.
I have installed the update to my phone 3 times with no problems other than when I extracted the file from the zip, I found it worked best running it without extracting the file. I have Win 7 32bit and it takes about 5 - 6 minutes to update.
If all else fails. You might have to download the sdk manager and use fastboot and flash the boot image then do the update and it will put the phone into recovery.

Spz0 said:
I've heard of varying times. Myself, it only took 6 mins or so, others had to wait more like 20-30.
What does the update program say?
Click to expand...
Click to collapse
By the way, The updater says 5 - 10 minutes.

Success!!!! ok...I dont know if it mattered but I also installed the future dial suite on the zio disk...I went through first and erased all other zio usb drivers before reinstalling the disk versions...plugged in phone..drivers got the OK..then ran the installer..took 5 minutes plus 2 for reboot..lol..
Also...fyi..I did this to my wifes phone but forgot to factory reset...all of her programs and contacts including adw ex remained intact after update (smoke from ears) oh well..thank god for titanium backup..

So does that confirm my thoughts of when I updated the other day to fix a goof after my original update. My apps and everything were still there after the update. So that must mean that the update from 1.6 to 2.2 does not format the phone unless go into the phone settings and do a factory reset.

Im at the end of my chain, please help me. My zio is stuck on the black screen "modem download mode" ever since the 98% thing happened. Try after try i keep getting error code. Im using windows vista 32-bit, i got the disc that came with my zio, i think i may have opened/extracted the zips wrong or didnt install in order or something. I think i uninstalled everything to do with this from my cpu even the zips so i can start fresh with ANY help i can get.

Uninstall the drivers for your zio that you have currently installed. Install the drivers that are on the site for the update download. Turn the phone off, unplug your battery for about 10 seconds if you need to. Hold + up and - down on the volume and the power button to put your phone into Modem Download Mode manually. Give the computer a minute to recognize the device. Run the updater again and if it fails or gives you an error message I would reccomend downloading the updater again. I have been able to run the updater several times already with no issues.
If you are still having problems, you may need to download sdk-manager if you do not have it already. You can always just use fastboot to erase the system and then run the update. The update will then set up the system partition and update the phone.
I had to do this just a few hours ago after I semi-bricked my phone while messing around with the cpu. What I did to get it working again after "bricking" it was...
1. you will need to have the android folder for the sdk-manager in the root of your hard drive to make it easier, unless you know where it is located.
2. Open command prompt and change to the tools directory within the sdk-manager folder. Mine was located in C:\Android\SDK-Manager\Tools
3. You may need to find the AdbWinApi.dll file, mine was located in the platform-tools directory so I just copied it to the main Android folder then copied fastboot from the tools directory and also placed that into the main Android folder.
4. Put your phone into fastboot. Hold Volume + up and the send and power keys. You can do "fastboot -w" and it will wipe user data and cache. You will need to type "fastboot erase system" and it will erase the system partition. Now type "fastboot reboot" and your phone will restart.
5. Put your phone in Modem Download Mode and run the updater.

Mattix724 said:
Uninstall the drivers for your zio that you have currently installed. Install the drivers that are on the site for the update download. Turn the phone off, unplug your battery for about 10 seconds if you need to. Hold + up and - down on the volume and the power button to put your phone into Modem Download Mode manually. Give the computer a minute to recognize the device. Run the updater again and if it fails or gives you an error message I would reccomend downloading the updater again. I have been able to run the updater several times already with no issues.
If you are still having problems, you may need to download sdk-manager if you do not have it already. You can always just use fastboot to erase the system and then run the update. The update will then set up the system partition and update the phone.
I had to do this just a few hours ago after I semi-bricked my phone while messing around with the cpu. What I did to get it working again after "bricking" it was...
1. you will need to have the android folder for the sdk-manager in the root of your hard drive to make it easier, unless you know where it is located.
2. Open command prompt and change to the tools directory within the sdk-manager folder. Mine was located in C:\Android\SDK-Manager\Tools
3. You may need to find the AdbWinApi.dll file, mine was located in the platform-tools directory so I just copied it to the main Android folder then copied fastboot from the tools directory and also placed that into the main Android folder.
4. Put your phone into fastboot. Hold Volume + up and the send and power keys. You can do "fastboot -w" and it will wipe user data and cache. You will need to type "fastboot erase system" and it will erase the system partition. Now type "fastboot reboot" and your phone will restart.
5. Put your phone in Modem Download Mode and run the updater.
Click to expand...
Click to collapse
okay, let me give that a shot, stay with me please!!!!!!

[Guide] Absolute Newbie's Guide to Rooting a Streak 7 that has Stock Honeycomb

Obviously this guide owes a huge bunch of thanks to "TheManii", "Giveen" and other folks who can't be named on this forum. I have tested this on both a Streak 7 WiFi and a Streak 7 4G. In both cases they had the Stock Honeycomb already on them. So if you are coming from some other version of Android you may wish to reconsider
1) Download the Fastboot+ADB.zip file for Clockwork Mod 5.0.2.7 from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
2) Download the Clockwork mod 5.0.2.7 file from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
3) Go into Settings->Applications and turn on "Run Applications from Unknown Sources"
4) Go to Development Settings and select "USB Debugging"
5) Unpack the Fastboot+ADB file into a directory on your computer where you can find it again
6) Attach the Streak to your PC, and copy the "Drivers.zip" file from the root directory of the Streak (/sdcard) to the same directory where you unpacked the Fastboot file
7) Turn off your Streak after you have copied this file, and disconnect it from the PC
8) Unpack the drivers.zip file and find the "Setup.MSI" file. Execute this file to install the drivers you will need
9) Put your Streak into Fastboot mode - i.e. turn it off, then turn it on by pressing the Power button while holding the Vol DOWN (-) at the same time. This can take up to 20 seconds
10) You will get some red text followed by a white line saying something about Fastboot USB downloading is active
11) Connect the streak to the PC now, and it should install an Android ADB driver. Depending on what you have already setup you may get some drivers installed successfully, and some not. In general if you've been following this guide, you'll be ok
12) Open a command line for the folder where you have fastboot and your recovery image (ClockWorkMod) - in windows navigate to the folder, and hold the shift key while right clicking
13) On the command line type the following:
fastboot -i 0x413C flash recovery recovery.img (where recovery.img is the ClockworkMod or other recovery file)
14) On the command line type the following:
fastboot -i 0x413C reboot
15) Your device should now reboot
16) To get it to reboot into CWM, turn the Streak off, and then turn it on again while holding the Power Button and Volume UP (+) at the same time. This may take up to 30 seconds
From here you would follow the normal CWM options to install just the root files (Superuser7 for one example) or install a custom ROM.

It turns out steps 9 - 15 are also a great way to fix the problem when your Streak comes up and starts asking for a Password when you never setup a password. For some reason installing one of the custom ROMS also installs a version of CWM that is not as recent as the 5 series, which can lead to issues with the signature verification (i.e. when things go "boom", Android sees the partition as encrypted rather than just "locked"). So steps 9 - 15 allow you to put in a later CWM which does a proper wipe, and you're back in business. Have to reinstall apps, but the data is left alone.
Just in case I'm not the only one who has run into this

Ok, I used this guide to modify my Dell Streak 7 wifi. After I was done my screen kept flickering and I put it back to stock thanks to AndroidOVERALL putting together a post on how to complete the restore.
I have searched about the screen flickering but didn't find a resolution. Maybe I missed it, but it seemed that others had the same issue and it was either a hardware problem, the brightness was adjusted, or auto rotate was disabled. I tried adjusting the brightness settings and many other settings but the issue was not resolved until I returned everything to stock.
I have a Dell streak 7 wifi, US version with Honeycomb.
Please point me in the right direction if this issue has been resolved and I missed it. If not any suggestions?

Did you load a custom ROM after following these steps, or did you just reboot aft getting CWM installed. Usually the flickering comes from an issue with the video driver (so can be software if a bad driver, or hardware if it's only marginally in spec).

For any one who gets to the end of the steps and now can boot in go CWM but doesn't know what to do about getting rooted.
Very very Simple.
Download Superuser7.zip
http://www.tablet-cables.com/streak/tools/root/Superuser7.zip
Have your Streak booted normally and USB cable hooked up.
Move to the internal Memory Superuser7.zip
power off device
Power back on using Vol UP & Power Button
Select 2. Software upgrade via update.pkg on SD card and press power
CWM will load.
Select install zip from sd card and power to enter.
select Choose zip from internal sd card and power.
use Vol UP to go backwards to your files and select Superuser7.zip and hit power
move down to YES - Install Superuser7.zip and hit power
thats it. its rooted.
goto ++++++++ Go Back+++++++
and reboot system now
and let it reboot.
Not necessary, but I'd suggest running Superuser and hitting the Knob icon top right (settings) and scrolling down and updating Super User.
Hope this helps someone who may not know where to get Superuser7 and what to do after following the great guide above.

thanks!
nothing sucks worse than a bad download -- happend TWICE! (dayum!)
got rewt?

Help?
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?

blastedmax said:
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
Click to expand...
Click to collapse
It's saying that it is looking for an SD Card and not finding it, so that certainly makes sense. However, it sounds like it is looking for "update.pkg" rather than "superuser.zip", so is it possible you accidentally selected the "Update" option in CWM rather than the option to select a file?

He doesnt have clockwork mod installed, you must have CWM installed to flash zips

OK, I have a new Streak 7 t-mobile with HC 3.2. I plug it to the pc running xp sp3, and it needs drivers for MTP and Streak7. I pointed to the Fastboot+ADB folder I extracted for the Streak7 driver and it installed Android ADB Interface. Pointing there for MTP fails to find a driver. I can't get to the internal SD to get the drivers.zip because my computer won't recognize the Streak until the MTP driver is installed. After installing an MTP driver from the net, I can see the internal and external SD. I copied everything to a single folder labelled STREAK in c:\ and unplug the Streak from the pc. I put the Streak into fastboot mode (Volume - & Power), wait about 10 seconds, then plug it into the usb port. The computer see the Fastboot device and needs a driver. I point it to the STREAK folder (former Fastboot+ADB) but it didn't find a driver it liked. I tried to install manually, but there is no Android 1.0 or Android ABD Interface devices in my list. I do see Android USB Devices, but it is empty when I click on it. ANYBODY else get this, and how do I move forward? I followed the guide to the letter, and appreciate all the work & effort you guys put into making these root methods available. The Streak7 is a cool little device, but I think it will be cooler once I root it. I have rooted my Epic 4g and the wife's Evo 4g on this same computer, and I do have the Android SDK installed (even though I don't know how to use it).
OK, so I used all the same files I have here and was able to successfully get Clockwork flashed & gain root. I dunno why the xp machines don't like these files. I tried 3 other xp laptops before getting to my wife's Windows 7 laptop, which worked just as described in the very well-written guides. #MindBottling!

I cannot even find the drivers.zip in step6. WIN7x64 and a brand new tmobile streak 7. where is this thing? I looked through all the folders and subfolders.

Drivers.zip is in the main directory of the Streak. Open up ES File Manager or a similar program and you should see it. To get it to your PC, attach the Streak via USB and let it mount as external storage (default behavior I believe).

In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Since this should be a common file for all SD7 units, can someone please email that file to me so i can get past step 6. [email protected]

cidand1 said:
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Click to expand...
Click to collapse
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
That said, I also can't guarantee this process will work for someone starting with Froyo. I do know there may be an issue with which version of CWM you can use in that case. As such, you may want to check one of the other guides to be sure.

EwanG said:
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
Click to expand...
Click to collapse
Explain please? Shouldn't drivers be present no matter how it's shipped? Mine came with Froyo with drivers, I OTA'd to HC and I still have them.

Ya I bought this from dell directly about 3 weeks ago. From what I have been reading on XDA, mine is definitely different. Its a tmobile streak 7.
Android 2.2.2
Kernel : 2.6.32.9
OEM ver: GLUNB1A133633
Build : 15420
Another thing I noticed is that even trying to load CWmod through fastboot, my computer does not recognize the DS7 in fastboot mode. The drivers in the fastboot+ADB zip file dont work on my computer as fastboot drivers (or maybe I should try another CPU). My cpu is an AMD 64; running win7 pro 64; i need some serious help.

I think I bricked!
Ok I followed the directions from here to root my tablet.
http://www.cesgeekbook.com/2011/12/root-dell-streak-7-with-honeycomb-32.html
All went well! Everything worked and I was rooted! did the Superuser7. Clockwork came up and installed. All went right! So I was pleased. I figured I would later than put on a ROM cause it was late. Well was going to do so and tried to go into clockwork via ROM manager. Didn't work! Kept rebooting! So I figured I would try the pother way "Press Power and +" then click to Install from SD Card to go into Clockwork. That didn't work either! Then Now it won't reboot at all! I can get into fastboot and I can get into the bootloader. But that's it! I tried to do a Factory Reset and nothing! it just stays on the Dell boot screen. Anyway to fix the problem? If so, please give me step by step directions on how to do it.

Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.

EwanG said:
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
Click to expand...
Click to collapse
Didn't know about the Rom Manager issue. I guess it's only good to use on cell phones? Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers. But since it's not reading the tablet. I can not reinstall CWM. The version I installed was the one from the 1st page. It's a fairly simple thing to do. But just need to get the device to be read by my laptop.
I have contacted Dell and explained to them the problem. They did say that I can return it to get it fixed. but still kind of hoping I can do it from home.

Marvelous0ne said:
Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers.
Click to expand...
Click to collapse
Not sure what you mean when you say the laptop is not reading the tablet in fastboot mode. When in fastboot it should NOT show up as attached storage. The best way to tell if it is "really" seeing the Streak 7 is in step 13 - which uses an id rather than a device name so that it should work even if the tablet isn't fully identified. If you try to perform step 13 while in fastboot, what message are you getting?

[Q] DS7 stuck on setup wizard

Hi,
I'm using a TMobile 4G DS7 in Europe (no SIM card); last week as I restarted it (battery was very low) I started receiving error messages (Email app has stopped unexpectedly, then Gmail and you name it...) and was sent back to the setup wizard.The DS7 was running on the original setup, no OS upgrade had been done.
I tried a factory reboot which didn't change anything.
I started reading this forum and tried the 3 options which are described
1- updating with a 306 .pkg file on the SDCard
the following takes place
Booting kernel recovery Image
Blue text
Finding update package
Opening update package
Verifying update package
Install modem error . System will upgrade again. (90% bar)
Screen turns black then reboots
and back to square one !
Trying other packages results in an error message, process stops at verifying update package .
2- Fastboot mode
I downloaded and installed the drivers
I put DS7 in fastboot mode and get the fwg :
Username : cmbuild hostname : ***** buildnumber : ******
Build on Mar 11 2011 17:19:36
Starting Fastboot USB download protocol
On PC I go to the directory where the fastboot.exe is stored .
When I type < Fastboot devices>
I get <? fastboot> which seems to indicate that no device is identified ( under Config panel in Windows I can see that the device is recognized as an Android device) ....
3- NVFlash mode
I put the DS7 in NVFlash mode connected it to my PC . The config panel showed there was a prob (yellow triangle). I installed the driver .... and now the device does not even appear when I go Config panel / System
So I get nowhere under any of the 3 options ; can I just throw away my DS7 or is there still some hope ? things I haven't done correctly ?
Any help suggestion would be most appreciated.
Thx in advance to whoever wil read this thread.
FG

the ???? Device under fastboot is normal
ONce you put the device into NVFlash mode and you install the drivers, open up Device Manager and look under the USB section, you should see something about Nvidia recovery mode.

giveen said:
the ???? Device under fastboot is normal
ONce you put the device into NVFlash mode and you install the drivers, open up Device Manager and look under the USB section, you should see something about Nvidia recovery mode.
Click to expand...
Click to collapse
You're right. I flashed everything went all right but after "pinbooting" no change still stuck.

FGMareil said:
You're right. I flashed everything went all right but after "pinbooting" no change still stuck.
Click to expand...
Click to collapse
You might be in read-only mode, which can only be fixed by Dell

giveen said:
You might be in read-only mode, which can only be fixed by Dell
Click to expand...
Click to collapse
The OP stated that the battery was low which is one reason some have claimed to cause this.