Related
Hey guys I have a stock G1 that was given to me and I can't access the wifi settings thus I cannot sign in. I believe I have the latest update. Anyone know a way around this?
http://forum.xda-developers.com/showthread.php?t=452316
B-man007 said:
http://forum.xda-developers.com/showthread.php?t=452316
Click to expand...
Click to collapse
Does not work with the very latest AOSP update : (
cars1106 said:
Does not work with the very latest AOSP update : (
Click to expand...
Click to collapse
You need to root your phone.....Read the stickys at the top of this section to learn how
It has been rooted before. then I unrooted it gave it to someone to use, it got updated and I don't have a sim with data and now I can't do anything with it. I guess I will have to downgrade via SD stick somehow through the recovery menu and try and run the exploit again.
if your one of those one-click rooters....your out of luck
you will have to root the old fashion way.....hint: RC29 DREAIMG.nbh
B-man007 said:
if your one of those one-click rooters....your out of luck
you will have to root the old fashion way.....hint: RC29 DREAIMG.nbh
Click to expand...
Click to collapse
Yup, I had the same issue, downgrade to RC29, then follow this:
**Originally Posted by dizzydevil111**
please make sure you have rc29 or lower by typer (enter)reboot(enter)
if the phone reboots then you have rc 29 or lower.
if not, follow this guide to downgrade to rc29
2. Mount your SD card in Windows and reformat it as FAT32. The HTC
bootloader won't be able to see the RC29 (or RC7) image otherwise. Make
sure you back up all your files first!
3. Download the appropriate image (RC29 for USA or RC7 for UK) from
http://koushikdutta.blurryfox.com/G1/DREAIMG-RC29.zip or
http://koushikdutta.blurryfox.com/G1/DREAIMG-RC7.zip . This is a DOWNGRADE
to the Android version that contains a root shell bug (this exploit just
seems too easy). I got these files from the forum thread
http://forum.xda-developers.com/showthread.php?t=442480 .
4. Extract the DREAIMG.nbh file from the downloaded zip archive and copy it
to your SD card (again, for me, this had to be formatted as FAT32, not just
regular FAT which is the default). Don't put it in a folder, just stick it
directly on there.
5. Disconnect the SD card the right way (eject, unmount, or otherwise tell
your OS you are unplugging it) to make sure the data gets written. If you
used an SD card reader, put the SD card back in your phone.
6. Make sure your phone has a full battery, then turn it off. Turn it back
on by holding down the CAMERA and POWER buttons. This should get you into
the HTC bootloader (the funky red, green, and blue screen).
7. If everything was done correctly, the bootloader will detect the image.
You'll be taken to a different screen that asks you to press the POWER
button to install the image. Do this, but beware, you will lose all your
saved data on your phone (with the exception of things that are synced with
Google's servers, like contacts, calendar, Gmail, etc.).
8. Wait for the update to complete. The progress bar will fill up, then
all the steps will say OK beside them, and finally, it will ask you to press
the "action key" (I think this means click the trackball). DO NOT do
anything until you see this message. The progress bar needs to DISAPPEAR,
not just fill up.
9. You now have the stock RC29 installed. Take out the battery, put it
back in, and turn on your phone. It should ask you to activate your Google
account again -
once you have this done type on the phone again (enter)setprop persist.service.adb.enable 1(enter)
your pc should now pick this up as an android adb device
point it to the correct drivers found in the file called androidusbwindows
once that installs, extract the adb file anywhere on your pc. (best place is root directory)
open up a dos command prompt and type (cd ..<enter>)
then type (cd ..<enter>)
then type adbshell
should look like this thereafter
$
referring to the dollar sign
then copy the following line into your dos command prompt and press enter
(am start -a android.intent.action.MAIN -n com.android.settings/.Settings)
please make sure that you copy the contents of adbwin.zip in your ROOT FOLDER or else you will be going through hell
voila you should be able to access wifi
pm me if it worked for you
I am using NookieFroyo installed internally to EMMC from here:
http://forum.xda-developers.com/showthread.php?t=938200
This same problem was reported by someone else here:
http://forum.xda-developers.com/showpost.php?p=11117975&postcount=330
But I don't believe this is an issue specific that that particular ROM because everything was working in Market for me before Tues Feb 3, 2011; but now Market will only allow me to browse; but not download anything. This is also happening with honeybunches for me.
Anyway, Market is not working. It won't start the download of any app. I can still browse. I have tried in Settings>Applications and with Titanium Backup to clear Market cache and data... and I have rebooted the device. Still nothing.
I modified my build.prop to make the fingerprint look like a Nexus One and I was able to download 2 apps (espeak and colordict) and then it stopped working again after that. Won't even kick off the download.
Anybody else experiencing a problem with NookieFroyo and Market or have a workaround?
I should mention that I have a Nexus One and the market is working fine on it the entire time, so it isn't a problem with the Market or my internet connection. Also, I know of 2 other people report being unable to download anything in the market on NookieFroyo... and I am surprised that it isn't affecting more or that there aren't more reports.
You're definitely not alone in this. I'm having the same issue in Honeybunches. Market downloads appear to start downloading, but the app never installs and does not show up on the device.
I've seen this mentioned by other users as well in the Honeybunches topic in the dev forum.
Same here. Well I'm running nookie froyo from sd.
Sent from my Nexus One using XDA App
It got so bad that I went back to rooted 1.0.1... At the moment, I have been observing that the official Barnes and Noble OS v1.0.1 rooted is the most stable and functional configuration for the Nook Color.
I have been working on a how-to, to make it easier for people to get back from NookieFroyo on EMMC... to a rooted 1.0.1. (this should also work from a Nook Color that isn't booting at all from internal memory). Many thanks to the original contributors (attributed below). I am merely trying to itemize all the steps.
1) Download WinImage (win32diskimager won't work for the following steps...). You can get WinImage here:
http://www.winimage.com/
2) Download this Image and burn it to the SD card with WinImage (using the "Disk" -> "Restore Virtual Hard Disk Image on Physical Drive")... if you cannot see the file when you browse for it... it may be the file extension, change the browse window to look for "Files of Type" = All Files.
Image download link (it may be zipped or compressed, decompress first) - for some reason only WinImage will work for this task:
http://www.multiupload.com/5RY9YX429S
Got that from brianf21 here - http://forum.xda-developers.com/showthread.php?t=938200
3) Power off Nook, put SD card in. Power on Nook. It should boot into Clockwork Recovery screen (text menu)
4) Under mounts and store, format /data and format /system (volume buttons move up and down, N button selects, power button escapes)
5) Escape to main menu, go to "Install Zip from SD card" and install the 1.0.1 file (do not install the Froyo file). Wait until it finishes, do not interrupt this process.
6) Power off the Nook, remove the SD card. Power on Nook and register it online. As soon as you are done registration and see the Nook desktop, power off the Nook (do not let it run any updates, if it downloads the Elephant book, it's ok).
7) Download and burn this image to SD card (you can use either WinImage or win32diskimager for this):
http://legacyschool.us.to/nookdev/clockwork/rootpack_1gb-0.5.tar.gz
The remaining instructions are here (But I will itemize them more briefly for you below...)
http://legacyschool.us.to/nookdev/clockwork/rootpack-instructions.html
Much thanks to TheCubed for this thread - http://forum.xda-developers.com/showthread.php?t=922870
9) Insert the SD card (with rootpack written to it) and power on Nook. It will boot into Clockwork Recovery menu again. This time you do NOT need to format anything.
10) Go to "Install from ZIP" and go into the required folder, install "root.zip"
11) Install "googleapps.zip"
12) Install "block-1.1.zip"
13) Power off Nook. Remove SD card. Power on Nook.
Once your device reboots, you will be presented with a setup wizard. (Below instructions from GabrialDestruir’s AutoNooter post on XDA)
1. Upon boot unlock your screen.
If it asks you to select a default application, put a checkmark in the box, and select SoftKeys as the default application.
2. At the Android Welcome Screen skip Sign In.
3. Enable Location Services when given the option.
4. Connect to Wifi and launch Youtube from "Extras".
5. Click the Menu button (The one RIGHT of the Up Arrow).
6. Select "My Channel" and Login using your Gmail Account. (YOU MUST USE YOUR FULL GMAIL ADDRESS!)
7. Exit Youtube and Launch Gmail from "Extras".
8. Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
9. Open up Market and Accept Terms and Service.
10. Insert your SD card
11. Go to Settings > Device Info > SD Card > Unmount SD Card
12. Format SD Card
13. Install Dolphin Browser HD from market (and make it your default Browser)
When you install apps, they will appear under "Extras"
If you don't like the Barnes and Noble home-screen and want a different Launcher:
1) search the Market for ADW.Launcher and install it
2) Go to Extras -> SoftKeys and after you press it, there should be a bar at the bottom that has tools (second from the right). Select that
3) Virtual Home button > Normal Press > ADW Launcher
4) Virtual Home button > Long Press > Home
6) Back
Now any time you press the N button once, it will call up the "back", "home", "menu", "search", "softkeys prefs", "close softkeys" buttons.
Press the N button twice quickly, and it will bring you to ADW Launcher (a configurable desktop, with an application drawer button at the bottom, that works like most android devices)
You can still access the B&N Launcher by pressing the N to bring up softkeys, and then long-pressing the virtual home button.
I have discovered Kobo reader isn't downloading my books; but I tested Kindle works and Youtube works in the browser for me for sure. According to the documentation the YouTube app works for some people and not others. I will work on trying to figure out what the X-factors are on that.
Also, this still uses the older market; but I don't mind. At least it downloads, and seems to see more applications.
Also seeing this issue- angrybirds, facebook, & several other standard apps missing from Market. Tried changing ro.build.fingerprint a few different ways in build.prop as well as the clear cache/data on google services framework/market idea. Any other thoughts?
- JMG
I could use some help getting my bluetooth to work. I've tried several of the CM7 nightlys, their RC4, phiremod v5, v5.2, and v5.3. They all flash just fine, and work great, except when I try to turn on the bluetooth. When I go to the settings and try to turn it on, it just spends 30 seconds trying then goes back to having it off. I've flashed and re-flashed the system, and have read everything I can find, but don't know what I'm doing wrong.
My steps.
1) Downloaded 8gb_clockwork-0.1-ext4.tar.gz
2) Burned the contained img file to an sd card (used the dd command)
3) Copied system image to sd card (ie phiremod-nook-V5.3.zip)
4) Unmounted sd card and inserted it into my rooted nook
5) Turned nook on
6) Formated /system /data and /cashe
7) installed from sd card, selecting zipped image (ie phiremod-nook-V5.3.zip)
8) when complete, unmounted sd card
9) removed sd card
10) rebooted
11) it always fails to boot the first time, but works find after a restart.
Can anybody see what I'm doing wrong?
What works for me is pressing 'fix permissions' in rom manager then reboot and badabing.
Sent via Tehduck Uberdistro Encore RC4 n.33/Tapatalk Pro
luciferii said:
What works for me is pressing 'fix permissions' in rom manager then reboot and badabing.
Sent via Tehduck Uberdistro Encore RC4 n.33/Tapatalk Pro
Click to expand...
Click to collapse
That did the trick!, thank you very much luciferii
Just a note as I try to avoid "Fix Permissions" when possible-
Anyone with this problem MAY be able to turn bluetooth on by rebooting and enabling it as quickly as possible.
This seems to work most of the time for most people. Not always..
If not, fix permissions and a reboot does seem to take care of it the rest of the time.
rogerdugans said:
Just a note as I try to avoid "Fix Permissions" when possible-
Anyone with this problem MAY be able to turn bluetooth on by rebooting and enabling it as quickly as possible.
This seems to work most of the time for most people. Not always..
If not, fix permissions and a reboot does seem to take care of it the rest of the time.
Click to expand...
Click to collapse
Why would you avoid fix permissions? It just sets things to sane values.
As for me, the fix I heard and what worked for me was to turn off Wifi, Power off, power back on, turn on Bluetooth and let it init, then turn on Wifi. Now both will turn on.
khaytsus said:
Why would you avoid fix permissions? It just sets things to sane values.
Click to expand...
Click to collapse
Two reasons:
#1) While I am not afraid to mess with root access or abilities I also try to avoid doing so whenever I can. If I don't NEED to, I don't. Same way I work on my linux computers. And if I have done nothing to mess perms up they SHOULD be ok.
#2) I think the simplest fix is best, every time. (As long as it actually FIXES the problem, of course.)
If all that is actually NEEDED is a reboot and turning on bluetooth quickly, why do anything else?
I used ManualNooter 4-5-18 and then 4-6-16 and then did the permissions fix that they said to do.
Everything worked fine for about 3 days. I went to turn it on it showed the Nook Color logo and froze. Now it won't do anything.
The only thing I can do is boot from SD with ClockWork Mod but it won't read it correctly, can't mount, can restore zip's etc.
Tried to push the Boot.img which seemed to have worked, but when I try to push the System.img it dies with a protocol error and the Nook powers off.
Please please someone tell me they know how to fix this! I can even give access to the machine it's hooked up to and let you have at it!
shieldsit said:
I used ManualNooter 4-5-18 and then 4-6-16 and then did the permissions fix that they said to do.
Everything worked fine for about 3 days. I went to turn it on it showed the Nook Color logo and froze. Now it won't do anything.
The only thing I can do is boot from SD with ClockWork Mod but it won't read it correctly, can't mount, can restore zip's etc.
Tried to push the Boot.img which seemed to have worked, but when I try to push the System.img it dies with a protocol error and the Nook powers off.
Please please someone tell me they know how to fix this! I can even give access to the machine it's hooked up to and let you have at it!
Click to expand...
Click to collapse
I found that the automatic updates in Market screw up the latest manual nooter. Here's how I fixed the problem.
*IMPORTANT* You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
1. Wipe the device (8 failed boots) and clean the memory (press and hold n while booting and keeping the power key depressed).
2. Complete the B&N registration process.
3. Upgrade to the latest B&N firmware (I tried 1.2 manually)
4. Use CMW and manual nooter by following this http://forum.xda-developers.com/showthread.php?t=1054027&page=1 to root your Nook Color.
5. Use the Market to download Terminal Emulator (see https://market.android.com/details?id=jackpal.androidterm&hl=en for details)
6. type
$ su -
# pm disable com.android.vending.updater
Check out
http://forum.oxygen.im/viewtopic.php?id=919 for more on this.
You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
I'll go through these and see what happens, but I wouldn't call what's happening to mine a boot loop. Nothing shows on the screen at all unless I boot from SD card.
And thank you for replying and trying to help me. I'm lost without my Nook. If I get it working I'm not risking rooting it again.
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?