Related
Hi there,
OK so, after spending like...a day getting some form of recovery on my Streak, the only thing that worked was Streakmod. Ok, awesome. I must have read 100's of guides to install Streakmod, but none of them seem to work for me! Bah! So, here's what I do, just so it ain't all me bein' crazy an' all:
Download StreakDroid 1.6.1
Put update-1.6.1.zip in the root of the sd card
I make a text file called "install.txt" in the root of the sd card.
In the "install.txt" file, put:
"adwlauncher
volboost
tabmail
bios"
Although the only one that really matters is adwlauncher. Right. Now, I boot into recovery, select ...Update.pkg and I get into Streakmod Recovery. Then restore to factory settings, dalvic cache, (even battery, just to be sure), and system cache orwhateveritscalled. Also fix permissions, even though that probably wouldn't do anything. Then I select install from update.zip, and then choose zip file. I select update-1.6.1 and it all goes smoothly. After it's finished installing, I restore to factory settings, wipe the caches again. I don't think I did "fix permissions" but hey that shouldn't matter. Ok. Click Reboot. It boots up, takes ages.
Now, on the times i've done this and put bios in the install.txt, it's does most the boot, then gets stuck. either on "achieving root" or "Initialising......../". Or it might restart the boot animation, indefinitely.
If I don't put the boot animation in, it goes all the way up to the lockscreen, I can see that there needs to be a pattern entered, but the touchscreen doesn't regester my inputs and after about 8 seconds it reboots anyway. BUT it only reboots to the start of the default boot image, the dell being ripped apart by the STREAKDROID in the middle of it. it will then just keep pulsating DJ Steven and then go back to only dell, and then get ripped apart, and the process starts all over again.
I've also tried having only ADW Launcher in the install.txt file, too. That didn't help, it did the same as it does if you dont put bios in.
So I was wondering, what should I do? I desperately want to liberate my streak from the clutches of stock, but every route is blocked. Any ideas on how I can get Streakmod working? Thankyou so much.
I hope I've explained this well enough, but it's kinda hard!
If it's any help, ROM Manager (premium) doesn't show any custom rom's if I click "Download Rom's". It also wont let me flash clockwork mod, or any of the older versions.
Thanks so much!
Reward!
{The person who posts the answer on how to fix this (and if it works) will get rewarded in the form of a £5 paypal donation!}
The wipe using the recovery doesnt work (although it says it is successful). You need to wipe using the factory reset option on the original recovery and then install the streakdroid update package using the custom recovery.
I ve faced the same problem before and dont worry.. the wipe fixes the problem!
Thanks a bunch
Would you like your £5 donation?
Yes!! thank you!
Hi All, first time poster, long time lurker.
I previously had CM7 installed on my fascinate and that was the first time I ever rooted so it was a tad buggy and there were two CWM recoveries (JT’s red 2.5 & CWM 4.X fixed for CM7) installed. To get to JT’s I did the three finger salute, and to get to 4.X, I used long held the power button in CM7 and rebooted into recovery. Anyways I decided to right my wrongs and flash CM7 from scratch. I followed these instructions to the letter (started with Post #2 then moved onto post #1) ([http :// w w w .fascinateforums. c o m/forum/fascinate-rs-guides/2961-how-upgrade-cyanogenmod7.html[/url]) [sorry could not post links... please edit spaces for it to work], multiple times, and could not get it to work. If anyone could shed some advice, it would be greatly appreciated.
A brief overview of what I did.
1. Phone had CM7 Installed, w/ CWM4.0.1.0 and JT’s Red CWM 2.5… decided to reflash from the very beginning.
2. Downloaded DL09 & Atlas v2.2 PIT as defined in Post #2 in the instructions provided in the previous link.
3. Used odined, put DL09 in PDA, Atlasa v2.2 in PIT, checked off re-partition, and Started Odin. Success.
4. Did not turn on the phone, instead connected into Odin immediately after and flashed CWM4 that was fixed for CM7. Success
5. Used three finger method and got into blue CWM4.0.1.0
6. Wiped data three times… wiped cache three times… wiped Dalvik three times.
a.Note: While wiping data, it did not allow me to wipe “datadata” and skipped that part
b.Note: While wiping Dalvik, it said that it had wiped dalvik but the line to it mentioned a path not being found..?
7. Flashed the 7/17 build. Now the trouble begins…
a.Recovery says “Checking status of bml/mtd” then “installation complete.” Phone reboots into the SAMSUNG splash screen then to the SAMSUNG & CM7 splash screen. It never makes it to the skateborder screen and is just stuck on the SAMSUNG & CM7 screen.
b. How long am I supposed to wait here? I waited 10 minutes and it was still stuck… so I just battery pulled. Phone is restored to stock now (using steps 1-2).
I tried this method at least 3-4 times and it always gets stuck on the Samsung & CM7 Splash Screen and just stays there… I am probably doing something wrong but can’t catch it.
I also another method. In step 5, I also went to mount/storage in recovery and wiped /system in addition to wiping data/cache/dalvik. Afterwards I flash the 7/17 build and instead of it being stuck in Samsung & CM7 splash screen it was stuck in an infinite bootloop from SAMSUNG -> SAMSUNG & CM7 -> Recovery (for a quick second) and back to SAMSUNG. When it loops back to recovery it quickly says “Can’t mount” then “installation aborted” and then continues the infinite loop to Samsung => Samung/CM7, etc…
Currently i followed steps 1-2 above and got the phone back to stock and have been using it ever since like that. I miss CM7...
Any help would be greatly appreciated. This forum has provided a plethora of wealth, and I would love to contribute back one day.
Many thanks,
Pat
This may be placebo more than anything, but when I was having problems, I went back to the EB01 stock with atlas as opposed to DL09 and then rooted manually to rooted stock using super one click before flashing the fixed CWM. Things worked great after that.
Also, if all else fails, flash CM7 7/4 and then upgrade from there... even though 7/17 should be fine, 7/4 was considered the jumping off point for a while.
pmanliu said:
Hi All, first time poster, long time lurker.
I previously had CM7 installed on my fascinate and that was the first time I ever rooted so it was a tad buggy and there were two CWM recoveries (JT’s red 2.5 & CWM 4.X fixed for CM7) installed. To get to JT’s I did the three finger salute, and to get to 4.X, I used long held the power button in CM7 and rebooted into recovery. Anyways I decided to right my wrongs and flash CM7 from scratch. I followed these instructions to the letter (started with Post #2 then moved onto post #1) ([http :// w w w .fascinateforums. c o m/forum/fascinate-rs-guides/2961-how-upgrade-cyanogenmod7.html[/url]) [sorry could not post links... please edit spaces for it to work], multiple times, and could not get it to work. If anyone could shed some advice, it would be greatly appreciated.
A brief overview of what I did.
1. Phone had CM7 Installed, w/ CWM4.0.1.0 and JT’s Red CWM 2.5… decided to reflash from the very beginning.
2. Downloaded DL09 & Atlas v2.2 PIT as defined in Post #2 in the instructions provided in the previous link.
3. Used odined, put DL09 in PDA, Atlasa v2.2 in PIT, checked off re-partition, and Started Odin. Success.
4. Did not turn on the phone, instead connected into Odin immediately after and flashed CWM4 that was fixed for CM7. Success
5. Used three finger method and got into blue CWM4.0.1.0
6. Wiped data three times… wiped cache three times… wiped Dalvik three times.
a.Note: While wiping data, it did not allow me to wipe “datadata” and skipped that part
b.Note: While wiping Dalvik, it said that it had wiped dalvik but the line to it mentioned a path not being found..?
7. Flashed the 7/17 build. Now the trouble begins…
a.Recovery says “Checking status of bml/mtd” then “installation complete.” Phone reboots into the SAMSUNG splash screen then to the SAMSUNG & CM7 splash screen. It never makes it to the skateborder screen and is just stuck on the SAMSUNG & CM7 screen.
b. How long am I supposed to wait here? I waited 10 minutes and it was still stuck… so I just battery pulled. Phone is restored to stock now (using steps 1-2).
I tried this method at least 3-4 times and it always gets stuck on the Samsung & CM7 Splash Screen and just stays there… I am probably doing something wrong but can’t catch it.
I also another method. In step 5, I also went to mount/storage in recovery and wiped /system in addition to wiping data/cache/dalvik. Afterwards I flash the 7/17 build and instead of it being stuck in Samsung & CM7 splash screen it was stuck in an infinite bootloop from SAMSUNG -> SAMSUNG & CM7 -> Recovery (for a quick second) and back to SAMSUNG. When it loops back to recovery it quickly says “Can’t mount” then “installation aborted” and then continues the infinite loop to Samsung => Samung/CM7, etc…
Currently i followed steps 1-2 above and got the phone back to stock and have been using it ever since like that. I miss CM7...
Any help would be greatly appreciated. This forum has provided a plethora of wealth, and I would love to contribute back one day.
Many thanks,
Pat
Click to expand...
Click to collapse
In step three of your post you have to fully reboot after flashing dl09 with the atlas pit file to convert all your files back to rfs before trying to install cm7...by pushing the dl09 w/atlas pit and not rebooting youre not fully completing the dl09 install so pretty much you just needed to reboot fully after flashing dl09 thats all.
If your sitting on a running dl09 now, then just do everything you did before minus the atlas pit and dl09...basically flash recovery...boot immediately into cwr and flash the same build using your same method...you probably won't have the data/data wiping problem anymore either!
Edit..you can also try the previous posters instructions as they have worked for me as well in fact every time I have to go back the eb01 file is what I use but most have no trouble with dl09
Sent from my SCH-I500 using XDA App
OMG im having the exact problem and for me that eb01 install did no difference i was also Stuck on SAMSUNG & Cm7 and by the way there is no 7/04 build because JT updated his site and there is none left
izzjkjoe said:
OMG im having the exact problem and for me that eb01 install did no difference i was also Stuck on SAMSUNG & Cm7 and by the way there is no 7/04 build because JT updated his site and there is none left
Click to expand...
Click to collapse
Have you tried booting up the phone after the initial first two steps (PDA +atlas 2.2 Pit)?
I'm at work and have not been able to try anything yet... will do when i get home in a hour
I have tried full reboot after flashing DL09 and it still doesnt work... gets me into a boot loop again. It did fix the wiping datadata issue but no luck with CM7...
I also tried EB01 without any luck.
Additionally i tried JT's 2.5 CWM (Red) and also a newer CWM 3.x...
none of these work. This is day 3 of my rooting problems... thanks for the replies, any more advice would be greatly appreciated...
Try it again and record your steps exactly and post them and I'll try and see what went wrong...it could just be a corrupt download of one of your files or just a simple missed step. What build are you on and what rom are you trying to go to?
Edit: this is what I have done multiple time without a hitch
regardless of what build and rom your on..
-pull your battery
-odin official vzw EB01 (pda button only..just a reminder) and the atlas
2.2 pit file and check the repartition box (I use odin v.1.7, but it shouldn't matter) and let odin do it's thing
-install battery and fully boot and let it sit for a minute our two after it loads
-pull battery
-odin recovery jt's 3-30 fix all... (found in nitsuj's sticky in the development section under recoveries)
-insert battery
immediately three finger boot into recovery and wipe everything
-flash newest cm7 build..I can't remember the date (I used the 7/4 build to get on to cm7 but it has been removed but the latest on will work)
-reboot fully
-use power button menu and select reboot..recovery to get to new blue recovery
-Flash newest cm7 build (if applicable), gapps and or mtd kernel if desired without wiping
-reboot, and enjoy cm7
Sent from my SCH-I500 using XDA App
Just saw your post. Will give it a try now.
When i'm in a bootloop and it hits the recovery part of the loop, i was able to get the error message (via using a camcorder lol)
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
hope this helps,
many thanks
patrick
-----
edit:
tried your method to the dot. I get stuck on trying to flash CM7. Now instead of boot looping it just says
E: Error in /sdcard/cm7new/update-cm-7.1.0-fascinate-kang-0717-signed.zip
(status 7)
installation aborted.
i'm redownloading the update and will see if replacing it on the sd card will work. Otherwise...
-----
redownloaded & replaced the cm7 zip file on SD card. No success.
No luck w/ your method posted either...
Oi...
this is upsetting
Download the recovery in the cm7 thread and repeat the same steps but use the recovery from the cm7 thread instead of 3-30 fix all and that should work
Sent from my SCH-I500 using XDA App
efan450 said:
Download the recovery in the cm7 thread and repeat the same steps but use the recovery from the cm7 thread instead of 3-30 fix all and that should work
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Did that... just goes back into the bootloop from recovery => SAMSUNG => SAMSUNG/CM7 (not the skateborder screen) and gives me this errorr:
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
------
edit:
okay i decided to flash MIUI fascinate 1.7.15 instead of CM7 and see if that works.
Well MIUI is running, but the weird thing is i still get SAMSUNG/CM7 boot screen before the MIUI boot screen comes up...
i am so confused!
I went through that same nightmare trying to install MIUI. CM7 or MIUI would give me status 7, and sometimes CM7 would go through, but just bootloop like you mentioned.
I tried about everything, and the only thing that worked for me was to first flash the 7/4 CM7 release for CWM 4.x, then flash MIUI over that. With any luck, the same will work for you for newer CM7 releases.
Unfortunately, like someone mentioned, the file was removed for some reason or another. I've still got it, so I reuploaded it for you, but jt, if there was some particular reason it was removed, say the word and I'll delete this copy. Otherwise, it's probably best to keep it up for people with this issue.
So basically, wipe data/cache/etc., flash the 7/4 CM7 release. Get that running, then reboot into recovery from CM7. Don't use the three-button method. Then wipe again, and flash the zip for whatever release you want.
mediafire.com/?u1n0wcqbwpuvts2
Download that file and flash that...it's how I got in to cm7 for the first time from eb01...if you are still on miui you can flash this with the blue recovery, wipe all and install
Sent from my SCH-I500 using XDA App
Many thanks to both your help! It has been of great assistance.
I downloaded the CM7 file posted, and will flash tomorrow. MIUI is running on it's first shot, and i'm entranced by it (for the time being).
However i am liking CM7 better, although both have many similarities
pmanliu said:
Many thanks to both your help! It has been of great assistance.
I downloaded the CM7 file posted, and will flash tomorrow. MIUI is running on it's first shot, and i'm entranced by it (for the time being).
However i am liking CM7 better, although both have many similarities
Click to expand...
Click to collapse
No problem, glad to help. If you end up flashing it, give us an update. Hopefully it'll work that way.
I used Cyanogenmod for a while back when I was more into stock ROMs. On different devices, though. It wasn't bad. But I flashed MIUI a few days ago and haven't looked back since. It's a great ROM. MIUI or CM7 is your choice, and I haven't used CM7 enough to say much about it, but MIUI has my full support. I never thought I'd switch from UKB so easily.
efan450 said:
Try it again and record your steps exactly and post them and I'll try and see what went wrong...it could just be a corrupt download of one of your files or just a simple missed step. What build are you on and what rom are you trying to go to?
Edit: this is what I have done multiple time without a hitch
regardless of what build and rom your on..
-pull your battery
-odin official vzw EB01 (pda button only..just a reminder) and the atlas
2.2 pit file and check the repartition box (I use odin v.1.7, but it shouldn't matter) and let odin do it's thing
-install battery and fully boot and let it sit for a minute our two after it loads
-pull battery
-odin recovery jt's 3-30 fix all... (found in nitsuj's sticky in the development section under recoveries)
-insert battery
immediately three finger boot into recovery and wipe everything
-flash newest cm7 build..I can't remember the date (I used the 7/4 build to get on to cm7 but it has been removed but the latest on will work)
-reboot fully
-use power button menu and select reboot..recovery to get to new blue recovery
-Flash newest cm7 build (if applicable), gapps and or mtd kernel if desired without wiping
-reboot, and enjoy cm7
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
So you never used jt's cm7 fix odin package?
Nope..I was able to go to cm7 with cwm3-30 fix all with no problem and I was able to go to it from otb's 3.x.x.x recovery...either way I've been back and fourth a few times but never had to use the 4.x.x.x. fixed recovery...maybe I'm just lucky but I know a few others have had success with those recoveries as well...you just flash it like normal...wipe everything and install the 7/17 build...reboot...and just make sure if you want to flash gapps or the glitch kernel you use the power button menu to reboot recovery...no three finger booting anymore.
Sent from my SCH-I500 using XDA App
Solution
pmanliu said:
Did that... just goes back into the bootloop from recovery => SAMSUNG => SAMSUNG/CM7 (not the skateborder screen) and gives me this errorr:
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
Click to expand...
Click to collapse
I was getting the exact same thing.
Started after I flashed the glitch v12 kernel on top of nightly #29. No problems.
Then I used ROM Manager to download nightly #35
Rebooted into CWM 4.0.1.5 orange via power button
Navigated to CWM folder to find nightly #35 to install from zip
Selected to install, checked for BML/MTD, said complete, auto rebooted
Boot loop with the above quoted errors, never gets to skateboard logo
Tried adb solutions, not enough time to issue adb commands before reboot
three fingered into cwm4 dark blue, got the usual expected E: can't find errors
tried restoring nandroid backup, auto reboots, no change, same errors as in quote
three fingered into cwm4 dark blue, tried flashing nightly #35 from RM download, no change
3fgered back into cwm4 dblue, flashed nightly #29 from SD that I had previously direct downloaded from cm7 nightly website, phone checked bml/mtd status, auto-rebooted, completed install.
Phone booted up normal with cm7 kernel, nightly #29, Data had been wiped
Used power button to reboot into recovery 4.0.1.5 orange
restored nandroid backup, rebooted
all is good! bazinga.
What I've learned from this is that using ROM Manager to download nightlies is risky. It may work fine if you use ROM Manager to download, wipe, and install, but if it fails during any of those (which it seems to do frequently) you could be out of luck with a headache. Best practice seems to be to download nightly directly from the cm7 website or copy it from your computer to the SD card and reboot via the power button into recovery and install that known good copy you downloaded via the cm7 website in the browser or transfered from your computer to the SD card. ROM Manager does something weird. This has occurred to me 3 separate times with ROM manager and with different nightlies. Also, it is worth noting that jt does not support the Glitch kernel for use with CM7 nightlies and a lot of issues seem to stem from using it. It is amazing when it works, but seems to add a lot of risk. YMMV
Let me know if this has helped or if anyone has any questions. Sorry for it being long, just trying to be thorough as there was no info out there to help me when this happened so I hope I can be of help to someone else.
ok so yesterday i rooted my telus fascinate and i was going to isntall the MIUI rom. Following a guides instructions i installed rom manager and did a clockwork mod recovery, i then put the rom on my root file of my sd card and tried to install it through the "install rom from sd card option" on the app. Problem was i only got into the stock recovery mode and not the clockwork one it aslo gave me signature failures. I then followed the guide of this video:
http://http://www.youtube.com/watch?v=Q7xV0yE9ZcA
when i installed the kernel everything went fine but then after i got into CW recovery and installed the rom my phone booted and it just kept repeating the normal splash screen (it said galaxy I9000 instead) followed by a screen that said something like cryogenic mod. I got freaked out from here and tried to install stock kernels to get my phone running. As of right now my phone will boot but only stay on the splash screen. I can not access recovery mode. I really need some help, thanks.
these are some of the files i used:
the rom i used,
http://http://forum.xda-developers.com/showthread.php?t=1150045
the kernel i used,
http://http://forum.xda-developers.com/showthread.php?t=822756
thanks
the links are broken. Did you install a rom / kernal specifically for the telus fascinate?
i believe it could have been for the galaxy I9000,
ill try to fix the links btw
update*
i managed to get it into clockwork recovery mode by holding the dam buttons for a solid 5 minutes, after doing this i pressed factory reset, now my phone is stuck saying:
-- wiping data...
Formatting DATA
0_0' im not having a great day
http://forum.xda-developers.com/showthread.php?t=1227807Until I know what version miui and kernal you are trying to flash, it's hard to help. It definately sounds like your phone is soft bricked tho.
Edit* Here are some links you should read up on.
http://forum.xda-developers.com/showthread.php?t=923712
http://forum.xda-developers.com/showthread.php?t=1227807
try to type this inot your browser:
http://forum.xda-developers.com/showthread.php?t=1150045
aswell as this:
http://forum.xda-developers.com/showthread.php?t=822756
it takes a little longer but i cant fix the links sorry.
So as of now i got i managed to wipe all of the data on my phone and i am in recovery mode, if i click reboot it does the same thing and stays on the boot screen. If i click the mod from the sd card it flashes from the normal model number screen to one saying cryogen mod. It then keeps going back and forth with a flash of a screen that has a bunch of commands on it for about 2 seconds
brodydj said:
try to type this inot your browser:
http://forum.xda-developers.com/showthread.php?t=1150045
aswell as this:
http://forum.xda-developers.com/showthread.php?t=822756
it takes a little longer but i cant fix the links sorry.
So as of now i got i managed to wipe all of the data on my phone and i am in recovery mode, if i click reboot it does the same thing and stays on the boot screen. If i click the mod from the sd card it flashes from the normal model number screen to one saying cryogen mod. It then keeps going back and forth with a flash of a screen that has a bunch of commands on it for about 2 seconds
Click to expand...
Click to collapse
The rom you are trying to flash is for a i500 fascinate. I suggest taking the time to do alot of research before you turn the phone into an expensive paperweight. Read this link!!
http://forum.xda-developers.com/showthread.php?t=921285
K well i ran that rom and it works now but he only problem is i dont have any cell service, do you know how to fix that. I know that you are probably laughing at my mild retardism at this subject but i am a big noob. As for what you said in your previous reply is their an MIUI version for the fascinate from telus because i basically rooted my phone so i could get this rom.
thanks
Update*
i followed the instructions on the link you posted and chose the rom for MIUI I9000 as the one i was going to install but when i istall zip from sd it only says installed correctly and then when i reboot it keeps changing from the sgh-t959d to the galaxy s cyanogen screen
yea your boot looped now. I would run the rom that worked just install the compatible radio and kernal for it and you should get cell service back.
ok thanks i got all my cell service back and i got the MIUI rom to work. Now to just ry to remember all the apps i had
Your welcome...glad you got everything working!
Hello. I'm a 55 year-old newbie to the wonderful world of Android, courtesy of my kid's continuously-rebooting Dell Streak 5 (AT&T, USA). It all started with the Froyo 2.2 OTA update in late 2011. The Streak would not boot after that update completed (WiFi - FIOS). We called Dell, and they advised that we Factory Reset it. That worked, and we thought all was well. Now several months later and 2000 factory resets later, my kid requested an iPhone for Christmas, and I re-claimed the Streak. I called Dell last week, and of course they wasted several hours of my time, ultimately telling me that my phone was out of warranty, but that for $249 I could buy a new phone. I advised several reps and a supervisor that Dell's OTA 2.2 update caused the problem, and that I should not be charged for any resolution to that problem. End of that story - here I am, after spending all of Saturday and most of Sunday attempting to downgrade back to 1.6. Here's what I have done:
I used SuperOneClick and successfully rooted the phone
I have used many recovery mods, ALL of which seem to lead to a black screen after selecting option 2. However, the Clockworkmod "alternate" recovery method did work. I downloaded a 4399 stock recovery zipped file, copied it to the Streak's SD card, then renamed the entire zipped file to "Update.zip". Then I used FastBoot, and flashed the Clockworkmod alternate recovery "recovery.alt.img" to the Streak. I used fastboot to reboot the Streak, then held the two Volume buttons, selected Option 2, and made my way through the awkward menu - but ultimately I was able to install "Update.zip" successfully. Upon the reboot, I am stuck with the Dell logo. I have tried factory resetting at this point, starting again from "scratch", only to return to the same old story: stuck at Dell logo. I read somewhere that it could take 10 minutes for the Streak to boot, but I have waited for 30 minutes plus.
An hour ago I was too frustrated to continue trying to downgrade to 1.6, so I read this thread: http://forum.xda-developers.com/showthread.php?t=1334487. I used the clockwork 3.0.1.9 recovery method, and attempted to upgrade to 2.3.?. This was not an "alternate" method (which had not worked in two days), but after flashing the recovery.img to the Streak, and using the 2.3.? "Update.pkg" on the SD card, the Streak did begin to verify the package - then it started the update, then - REBOOT. The first time this happened, I waited for 30 minutes, thinking that the upgrade was happening in the background while displaying the Dell logo, as Windows updates sometimes do. But then I yanked the battery, and started that process again. The next time and every subsequent attempt to perform this upgrade results in a reboot as the "verifying package" is occurring.
At this point I feel as though I am spinning my wheels, so I'm putting out an All Points Bulletin for some advice and/or help.
Thanks in advance! John in Dallas
John, have you tried with another update.pkg? The thread you link to is from sreak 7, could that be the issue? If I was you I would try one of the 407 deodexed ROMS from http://forum.xda-developers.com/showthread.php?t=1376896
I did not realize that thread was for the Streak 7. Thanks for pointing that out. I have tried several others, but nothing like what you have provided.
Being new to this technology, I have not yet quite grasped all the terminology and theory. Can I mix and match the recovery images with the Update packages? For example, where "TheManii" states that StreakMod must be pre-installed, then he provides a (407) base_v1.zip , is it OK for me to use the Clockworkmod recovery.alt.img (which has seemingly worked well on my Streak) with his base_v1.zip? Or MUST I use the StreakMod recovery image in conjunction with his base_v1.zip?
I assume that I am supposed to follow the same procedure as before:
- Save the base_v1.zip to the Streak's SD card - renamed to "Update.zip"
- use "fastboot mode" to transfer the recovery.img from PC to the Streak
- boot the Streak into recovery mode, select option 2
- then select the recovery option to load from the "Update.zip" on the SD
How long should it take to install the base and the update?
I understand that the "base" is just that, and I will also need to flash the "update", but the other "bloat" stuff is optional.
I will give this a try shortly - then re-post. Thank you!
I am not the expert here, but from what I've gathered you need the correct recovery image only when you are flashing an official update, since those updates come as encrypted ".pkg" files. I think (please check also the threads on flashing modified ROMs) that ROMs that end on ".zip" are not encrypted and don't need a special recovery file. I hope someone with actual experience on this can confirm if I am correct.
Edit: I just notice that the thread I linked to specifies that installing the matching "pkg" is a prerequisite to installing the "zip" -- this is admittedly more complex than I thought it would be. You are probably better off just installing one of the stock ROMs first just to recover your Streak -- I had recently updated to the 407 (Korean) Gingerbread ROM and like it very much; there are instructions of puttiing it here: http://forum.xda-developers.com/showthread.php?t=1416718
John,
To flash a stock ROM you need a stock recovery.
To flash a custom ROM you need StreakMod Recovery.
Even if the files are not altered any ROM packaged as a zip is a "custom" rom.
To get you started (and get your Streak working) you should flash a stock ROM. I recommend BB 351 as the most stable stock ROM.
Put the pkg file for 351 on the root of your SD card named update.pkg
Use fastboot to flash the 351 recovery,
Use fastboot reboot to reboot the Streak and as it reboots hold both volume buttons to get to recovery
Select option 2 to install 351.
If you decide to use a different stock ROM the instructions are the same, just use the correct files.
If you really want Gingerbread then flash the latest stock GB ROM and then install the DSC version of GB. See the DSC thread in the development section for info.
I've been looking for a downloadable "BB 351" since you posted - cannot locate it. I found the base 351 zipped file, but not the "pkg". Any hints?
Also, when I first attempted that "407 - base_v1.zip" installation, I used clockworkmod, named the base_v1.zip to "Update.zip", and it worked to a small degree. After confirming that the installation was successful, I rebooted the Streak, and after 3 minutes I saw a "O" logo with "elloh" beneath it. Unfortunately it never entered into a "home page" - but rather the Streak reverted to the Dell logo, and that was that.
You might try the links in my signature to find what you need - the wiki is a good place to start.
Edit: the reason you had no success with the zip you flashed is because a ROM flashed from a zip is incomplete. That is why you need to flash the stock rom it is based on first. The ROMs packaged as zips do not install some needed system files, that is why you see instructions to install those first.
You have more reading to do before you understand the process of updating/modding the Streak.
I did locate the BB 351 package just seconds after posting that I could not find it. I've now bookmarked it. I continue to have not-so-good luck.
On the "407" Base_v1.zip installation, suggested by the first poster, the installation went further than any other attempt. I actually saw the "O" with "olleh" beneath it onscreen for a few minutes, but then, poof, it was gone - replaced by the Dell logo. If I am successful, will the Dell logo still be displayed, or will the "O" or some other logo replace the Dell logo upon a successful installation?
After downloading the 351 package and corresponding recovery.img, I reached one point where the status indicator bar reached 100%, but then everything apparently froze. Rather than panic and quickly yank the battery, I left it alone for 15 more minutes. There was no change, so I removed the battery and started again. Now, after many more attempts, I see the "Verifying Update", and then the Streak reboots. Each time I leave it for several minutes in hope that it is installing the Update in the background. But nothing happens. Just reboot after reboot - with Dell logo.
I know that I am very close, so I am not giving up. But I am worn out - PLUS the Super Bowl is starting right now. I'll pick this up again tomorrow night.
If anyone has any ideas or suggestions, please post - remembering that I'm a newbie and may not understand your technical slang, although I am a Telecom Engineer now working exclusively with VoIP, so I am technical. It's been fun tinkering so far, but it would be nice to reach a happy ending! Cheers.
John - North Texas
Thanks for that tip, Marvin02. I do understand. Applying the base was step 1. I did not perform step 2: applying the update. Without the update, the base could not "launch". Unfortunately today I have returned to the wonderful world of IP Telephony, Gateways, UC, and Linux. At this moment I have no battery for the Streak, as I gave it to my daughter during the Christmas break. Yesterday I was using my son's battery, but he returned to college yesterday evening. I ordered a battery last Thursday, and it is due to arrive today. I was shocked to discover that the Streak cannot power on with only external power - it requires a battery.
I also know that I have merely scratched the surface of this technology. After I recover this Streak, I plan to install a ROM Manager, perform a backup, then experiment with other mods. But right now the mission is to revive the Streak paperweight.
Thanks!
ROM Manager and similar apps don't play well with the Streak. Don't use them.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
When you tried to install BB 407 you were installing a gingerbread ROM.
BB351 is a Froyo ROM. There have been some reports of problems reverting from GB to Froyo.
I suggest that you use fastboot to flash:
The recovery for BB 351 or BB 360
amss.mbn
dsp1.mb1
Then reboot to recovery and try installing the update.pkg.
For some reason some Streaks need the baseband files flashed first before the Froyo ROM will install properly. This happened with my Streak when reverting from GB.
blackscreen after selecting option 2
When i select option 2 from the recovery screen it is just a black screen. is there a way to fix this?
upgrade to Longthorn 2.6 is the most one I like
I flash the ROM to Longthorn 2.6. Strictly follow up the step.
My Dell Streak 5 now faster than before, no Dell Stage respone error anymore.
flashing light also resolved (read the instruction in [ROM] Longthorn 2.6 topic.)
i was trying to update my dellstreak5 i was on dell offical rom 2.2.2 fyro
http://forum.xda-developers.com/showthread.php?t=1314898
i followed gudline 4 and and DSCv2.0-rel on my dell streak root of sd card
and entered into fastboot mode and run fastboot.bat from 'DSC_flashme2_2'
and then my phone reboot and i press both volume buttons and it keeps restarting and i pull the battry out.
and then press power and volume buttons together and enter into dell menu and follow the instruction and i started installing coustom rom
and after 1 min it got stuck and said "error >7 installation failed assert failed" and i did a reset from back of dell menu and guidline stated and now it give 3 lights and keeps on dell logo plzz help me !!!
error details
installing phonix kernel
assert failed: package_extract_file("boot.img"."/tmp/boot.img")
E: Error in /sdcard/dscv.2.0-rel.zip
(status 7 )
installation aborted
this is the error that this rom gives to me
Some additional information is needed. Let us know everything you did to get you to this point, including which recovery you installed.
help
Strephon Alkhalikoi said:
Some additional information is needed. Let us know everything you did to get you to this point, including which recovery you installed.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1314898
let me explain u what i did step by step
1) i downloaded http://www.littlemaruko.com/Nopteam/DSCv2.0-rel.zip
2) and then http://n0p.8bit.fm/streak/updDSCv2.3.zip
3) DSC ROM "flash me before installing" pack.
[email protected] (this link gives me DSC_flashme2_2 folder) above 3 links are in above thread i mentioned under dsc rom downloads
4) and put 2 zip files DSCv2.0-rel and updDSCv2.3 on the root of sd card which i get from step 1 & 2
5) and pull battret out and put it back in and go into fastboot mode then after 20 sec connect my dell streak5 to pc through usb and from DSC_flashme2_2 folder (which i get it from step 3) i run flash.cmd it makes my phone to reboot
6) i pull the battrey out and disconnect the usb cable
7) i enter into dell menu by holding both volume buttons and power button then go to update from zip on sd card select DSCv2.0-rel.zip and it start installing and at the end it gives error and then i move back on dell menu and factory reset it ..
and ends up f**king myself :'( help me plz im noob to andriod stuff its my first attempt to do a custom rom
help
Strephon Alkhalikoi said:
Some additional information is needed. Let us know everything you did to get you to this point, including which recovery you installed.
Click to expand...
Click to collapse
dont know about recovery..... i just did all thing which i writed in my above post .... nothing more than that ...!!!!
If you don't know which recovery you installed, it's highly likely you didn't install one at all. This would explain why you can't install the ROM.
You must be rooted and have a custom recovery installed in order to install a custom ROM.
Strephon Alkhalikoi said:
If you don't know which recovery you installed, it's highly likely you didn't install one at all. This would explain why you can't install the ROM.
You must be rooted and have a custom recovery installed in order to install a custom ROM.
Click to expand...
Click to collapse
@ Strephon Alkhalikoi
he skips the worst part of all.. installing 406 or 407 first...
@ asfandnasar
since you are a beginner, knowing the basic upgrade from froyo to gb is crucial... then the usage mastering part.. then once you are familiar with those of gb, you can then try to use custom rom...
not straight away and do the shortcut...
you need to try to use original stock rom of 406 or 407 first before attempting to install a custom rom you know... but you missed it big time... reallllly big time...
deysmacro said:
he skips the worst part of all.. installing 406 or 407 first...
Click to expand...
Click to collapse
Installing 407 isn't a requirement for either DSC ROM, especially since _n0p_ disabled the baseband check in the Phoenix kernel. In fact, both _n0p_ and I offer the 366 baseband for use with our respective versions of DSC as it works better than the 407 baseband.
However, the fact the OP is skipping steps is going to lead to disaster. He really needs to look at the various guides we have here and understand what he is doing, before he turns his device into a nice, shiny paperweight.
help
Strephon Alkhalikoi said:
Installing 407 isn't a requirement for either DSC ROM, especially since _n0p_ disabled the baseband check in the Phoenix kernel. In fact, both _n0p_ and I offer the 366 baseband for use with our respective versions of DSC as it works better than the 407 baseband.
However, the fact the OP is skipping steps is going to lead to disaster. He really needs to look at the various guides we have here and understand what he is doing, before he turns his device into a nice, shiny paperweight.
Click to expand...
Click to collapse
this is the guid i followed...... if i do a streakmod recovery on dellstreak 5 would i be able to install this rom by the following method
4.Guidelines for migrating from Stock Froyo ROMs.
Running a custom ROM has its advantages and disadvantage (you woid your warranty), advantages are many thou nandroid backups, speed , flexibility, root ability, imporved battery life, tweaks to make your Streak do more than you are used to, quick response from the devs for daily issues etc.
Custom ROMs dont come in .pkg format as do OTA from Dell, but custom ROMs do come in .zip files, which then need to be flashed (installed) into your Streak.To make this possible you need first to install a modified image called StreakMod which would make it possible for you to install DSC. StreakMod is provided also from DSC in the pack DSC_flashme2.zip provided by (_n0p_).
Download the DSC_flashme2.zip provided by (_n0p_) All you need is working Windows installation (32bit versions are tested) and the latest drivers form Dell installed on the PC.
You need to download the main DSC ROM only form the links provided on the first post of DSC in XDA thread, copy it on the root of your SDcard where they can be easily accesed, or you can open a folder called DSC, and you can put there all the zip files from DSC, but remmember the place , as you will need to find those files later from StreakMod menu.
You need to extract the content of the DSC_flashme2.zip file on any folder you like or the default folder offered by the system, DSC_flashme , but be sure to be easily accesed, you can remove the folder to any place you like after the flashing process,
Now be sure you have charged your streak to 100% before you start installing DSC. DO NOT connect your Streak with the PC using the usb connector yet. Power your streak on and immedialty press the camera button, you will see a white screen, this is called the FASTBOOT mode "Wait for SD detect...." then you will see "FastBoot" tap on it and the streak will enter the FastBoot-Mode , you will see "Wait for USB FastBoot detect ...." wait 20 seconds then plug your usb connector to the mobile and after some seconds you will see "FASTBOOT_MODE", now you are ready to turn to your PC again and .....
After the folder is in place, locate the flash.bat and double click on it, a windows DOS terminal will open, follow the instructions there and reboot immediatly after you see the Dell logo within seconds you need to press and keep pressed both volume butons on the side of and then you will have access to Dell menu, select the second option by using the Volume buttons to go up and down the menu, once the second choice "upgrade...." press the camera button and wait several seconds, then a Dell logo with a triangle will appear, that is the StreakMod menu, try navigating the menu up and down with the volume buttons, and once second choice there " update using zip" is highlighted, press the camera button , then you will go to a another menu , where using the same volume buttons , you can navigate thru to find the place where you uploaded the DSC zip file , then once highlaghted press the camara button again and you will see the DSC_script doing its job, once finished , you need to press back button, and go back to the first menu where you select reboot. Once streak is rebooting agian keep your fingers press on both volume buttons, where you will see the Dell menu, now chose the first option, factory reset,streak will reboot by itself, let it reboot , you will see Dell logo, and then the DSC boot animation, wait now patience, if you have done all the above , nothing can go wrong, wait a little , then wait some more , bcs a lot of files is being genearated for first time, etc so this process can take some time, 15 minutes, if you have seen the DSC boot animation, it means everything is ok, otherwise you need to repeat the process again.
Ok, so after installing StreakMod through the flashme pack did you immediately reboot into StreakMod or did you let the Streak boot normally? If you let it boot normally, you wiped out StreakMod. If you didn't, the copy of DSC you downloaded could have been corrupted in the transmission. In that case you'll need to download it again.
help
Strephon Alkhalikoi said:
Ok, so after installing StreakMod through the flashme pack did you immediately reboot into StreakMod or did you let the Streak boot normally? If you let it boot normally, you wiped out StreakMod. If you didn't, the copy of DSC you downloaded could have been corrupted in the transmission. In that case you'll need to download it again.
Click to expand...
Click to collapse
i just run flash.cmd from DSC_flashme2_2 folder
http://www.4shared.com/photo/xk2wHzjH/help_222.html ( in this picture u could see what i did i write a note and show files as well
http://www.4shared.com/photo/h4hMBKUp/help.html(in this picture u can see the links where i downloaded all that files correct me if im nt downloading it from right place
no need to pull the battery after flash me2
Sent from my Dell Streak using xda premium
As I expected, you're having no success with this because you aren't following the instructions given when you run the flash.cmd file in the flashme pack. As a result, StreakMod recovery is not being installed and thus you're still on the stock recovery. _n0p_ and StreakOwner have made this as simple as possible by telling you exactly what to do in order to get this done. If you cannot follow those instructions, then do not attempt to install a custom ROM at this time. You'll turn your device into a very expensive paperweight.
One piece of advice I will provide you: look for the thread in the development section titled "Everything you always wanted to know about the Streak but were too busy bricking it" and start reading the information found at each link within it. It covers basic information every Streak owner needs to know; information not covered in the brief instructions given in the flash.cmd file in the flashme pack. Once you read those links, then attempt to install the ROM.
EDIT: In the future, embed your images onto XDA's servers, rather than using 4shared. 4shared requires registration, and I could not see your images until I had logged in to my account there.
done
Aaryana said:
no need to pull the battery after flash me2
Sent from my Dell Streak using xda premium
Click to expand...
Click to collapse
first time when i flash it.... it stuck on dell logo and not going into dell menu and then i pull battry out .... now i did it and sucessfully entered into the dell menu and done i installed the rom no error occured ..... but im doing this costom rom because of random reboot and this problem remain same.... but i done it
thankx for helping guys im really gr8full .... if anyone of u know how to fix this random reboot thing....
done but still getting random reboot
Strephon Alkhalikoi said:
As I expected, you're having no success with this because you aren't following the instructions given when you run the flash.cmd file in the flashme pack. As a result, StreakMod recovery is not being installed and thus you're still on the stock recovery. _n0p_ and StreakOwner have made this as simple as possible by telling you exactly what to do in order to get this done. If you cannot follow those instructions, then do not attempt to install a custom ROM at this time. You'll turn your device into a very expensive paperweight.
One piece of advice I will provide you: look for the thread in the development section titled "Everything you always wanted to know about the Streak but were too busy bricking it" and start reading the information found at each link within it. It covers basic information every Streak owner needs to know; information not covered in the brief instructions given in the flash.cmd file in the flashme pack. Once you read those links, then attempt to install the ROM.
EDIT: In the future, embed your images onto XDA's servers, rather than using 4shared. 4shared requires registration, and I could not see your images until I had logged in to my account there.
Click to expand...
Click to collapse
thankx
after ur last comment i tried it again ..... and i finaly done it ... i will read that thread too.... but i was doing that rom bcz i read in post its the most stable rom ... but no luck its like fyro 2.2 ... do u know how to fix that random reboot thing
thankx for ur help again u guys r awsome
Give it time to stablize. I find on a fresh installation of my version of the ROM I will have random spontaneous reboots for a few days and then they almost completely disappear. I say "almost completely" because on very rare occasions I will get one when I least expect it.
Make sure you have done both wipes as instructed in the DSC instructions.
thanks
Strephon Alkhalikoi said:
Give it time to stablize. I find on a fresh installation of my version of the ROM I will have random spontaneous reboots for a few days and then they almost completely disappear. I say "almost completely" because on very rare occasions I will get one when I least expect it.
Make sure you have done both wipes as instructed in the DSC instructions.
Click to expand...
Click to collapse
yup i did both wipes and premisses fix as well .... hope so it will get stable ... thanks for helping
help
Strephon Alkhalikoi said:
Give it time to stablize. I find on a fresh installation of my version of the ROM I will have random spontaneous reboots for a few days and then they almost completely disappear. I say "almost completely" because on very rare occasions I will get one when I least expect it.
Make sure you have done both wipes as instructed in the DSC instructions.
Click to expand...
Click to collapse
it aint getting stable .... and this problem is getting worse day by day .....
when it is in my pocket it automatically restart ... and stuck on dell logo and become hot like hell .... easy to make me feel on my leg .....
i can just listen to music and radio thats all i can do with my dell streak without having a restart any suggestion ???
None, unfortunately. _n0p_ hasn't been able to pin down the cause.