[Q] Build number 8558 - Streak 5 Q&A, Help & Troubleshooting

Anyone recognize this build number - 8558?
Running Android version - 2.2,
Baseband version - AUS_100908_01_BOSS_EVT3_F-US,
Kernel version - 2.6.32.9-perf,
OEM Version - AUS_100980_01_boss_evt3_froyo_release
Phone is rooted, and it says it has Clockworkmod Recovery 2.5.0.7, but when I try to reboot from ROM Manager it just boots into normal operation, if I try to boot into recovery manually, it goes to a black screen and hangs up.
By way of explanation, I just bought this Streak from eBay and want to check what I have now, before trying any customization. I've checked several sources but see no mention of a build 8558.
A follow-on question would be what is the best way to get from here to one of the custom GB ROMs?
I've found some excellent information on this forum, and have the greatest respect for all of you who contribute with such patience, wisdom, and good humor.
Thanks for any help

zancro said:
. . . .
Phone is rooted, and it says it has Clockworkmod Recovery 2.5.0.7, but when I try to reboot from ROM Manager it just boots into normal operation, if I try to boot into recovery manually, it goes to a black screen and hangs up.
. . . . . .
A follow-on question would be what is the best way to get from here to one of the custom GB ROMs?
. . . . .
Click to expand...
Click to collapse
ROM manager does not work well with the Streak. Best bet is to use StreakMod Recovery.
By GB rom I am guessing you mean gingerbread? There is only one gingerbread rom (gingerstreak) and that is in beta. Do you mean StreakDroid? Look at the development thread for your ROM choices. For a custom ROM the best bets are StreakDroid 1.9.1 or SimpleStreak. For a stock ROM I like BB 351, others prefer 354.
See this guide for flashing a rom and see my signature for more Streak info.

marvin02,
Thank you for the good information on ClockworkMod vs. StreakMod on the Dell Streak. I'll try installing StreakMod this evening. Once I have that working I'll consider the options for a custom ROM, but lean towards the Gingerbread derivatives. My understanding is that the two most noteworthy incentives for moving from FroYo to Gingerbread are battery conservation and wifi connectivity.
I've had the Streak for about two weeks now and am delighted with the features and performance, but would like better wifi consistency.
Not to beat a dead horse, but why can't I find anything on build 8558? Is a rare hybrid, a strange service provider ???
Again, I'm grateful for the advice.

zancro said:
marvin02,. . . .
Not to beat a dead horse, but why can't I find anything on build 8558? Is a rare hybrid, a strange service provider ???
Again, I'm grateful for the advice.
Click to expand...
Click to collapse
While Gingerbread may have advantages over froyo in theory, there is no 100% working GB rom for the Streak. Read the Gingerstreak thread in the dev section for more info.
As far as your build, do you know how to create a shortcut to an activity? The article I linked to shows how to use Anycut, which is s free app. Launcherpro and ADW have this feature built in. Create a shortcut to the activity DisplayVersionInfo. When you tap the shortcut you have created you will get more detailed info about your build. See the attached image. This may help someone figure out your version.
You should also contact TheManii as he is the maintainer of the Streak Wiki and has been collecting as many of the ROM files as he can. If your ROM is one that has not been seen before he will want to get the files, but you may have a customized ROM put on by a previous owner. Some of the values displayed in the Phone Info are just strings from the build.prop file and may not truly indicate what is behind the scenes.
Note : screenshots can be taken with drocap2 (check swap endian in the settings) or Screnshot by Kastorsoft if your phone is rooted.

8558 is the froyo (2.2) leak that is installed with streakflash.zip
I have a handful of leak roms but they arnt listed on the wiki as only released roms with actual rom version numbers are listed.
The streak itself is more interesting if that was what was actually preinstalled and not installed by someone after the fact. But the rom is one I already have

"Can't mount SD Card"
marvin02,
Thank you for the detailed instructions. I removed ROM Manager and used your guide to install StreakMod with fastboot. Just to be sure, I reran the rooting script using SuperOneClick ver 1.7. I verified Superuser and StreakMod were working, then downloaded, copied, and renamed the update.pkg file for build 351 on my 8Gb class 6 micro SDHC card.
Next, I reinserted the SDHC card into the Streak, and booted into recovery. All went well up to Step 11: Select option 2 on the screen..., I chose the second option and got a verification screen, and toggled to Yes. At that point I got an error message I don't understand.
"v0.3.2.8
--Installing: SDCARD:update.zip
Finding update package...
E: Can't mount /dev/block/mmcblk1p1
(No such file or directory)
Can't mount SDCARD:update.zip
Installation aborted."
The micro SDHC card is properly inserted so I'm assuming this has something to do with how the card is partitioned, but haven't got a clue what can be done to rectify the problem.
As before, any advice is gratefully received.

you cant install pkgs with clockwork, you have to install the matching stock recovery.
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak#Official

zancro said:
marvin02,
Thank you for the detailed instructions. I removed ROM Manager and used your guide to install StreakMod with fastboot.
Click to expand...
Click to collapse
That guide is by Radimus, I just pointed you to it.
zancro said:
Just to be sure, I reran the rooting script using SuperOneClick ver 1.7. I verified Superuser and StreakMod were working, then downloaded, copied, and renamed the update.pkg file for build 351 on my 8Gb class 6 micro SDHC card.
Click to expand...
Click to collapse
To install a stock rom you must use the stock recovery, not StreakMod. This might help.
Take some time and check out the links in my signature.

Build version 8558
TheMannii,
Thanks for clarifying build number info. I wish I knew more about the history of the Streak, but I bought it secondhand after waiting too long to buy a new retail unit. I already had AT&T service, so not much was required for the swap from Blackberry. Now I'm just trying to learn a bit about how to do updates, etc.
All the old-timers on the forum have really been kind and generous with their time for a newcomer. For the encouragement as well as the help, thank you.

/me sniggers @oldtimers

Thanks all; again, you called it correctly... I mislabelled the recovery.img file. After retracing my steps all is well and 351 is running well.

All's Well That Ends Well
marvin02,
You were dead on. I mislabeled the recovery.img file, so the previous version was not overwritten. I now have build 351 up and running, and all looks good.
Thank you.

Related

Clockworkmod broke my recovery, any suggestions?

SOLVED it myself - read below:
The super quick version:
During an attempted downgrade from 02 2.1 6941 (it was buggy as hell) back to ATT 1.6, I tried a method someone posted involving clockwork 1.8.1.7. Unfortunately, clockwork can only burn .zip clockwork formatted roms (you cannot simply rename a pkg a zip). All attempts to switch back to any other recovery program simply resulted in a black screen after selecting update - many recovery roms were tried. So I was stuck with no way to even try to burn a regular pkg rom and a broken clockwork (1.8.1.7 "works" but with errors).
TLDR: Black screen after "press camera button to update" on all recoveries except clockwork 1.8.1.7 on 02 1.6 4399.
Solution:
Installed clockwork formatted rooted 4399
Installed older recovery rom I found
I can provide links to these later. I don't have them on me at the moment.
If anyone has any idea how to solve FOTA name mismatch, or even wtf it means, let me know.
WOuld be great if u could tell the forum what u did
You may not be alone
r00tcause said:
Solved my own problem after hours of trial and error - no thanks to anyone here.
Click to expand...
Click to collapse
The Streak community seems to be pretty small at this time. Until we have a bigger user base we are all kind of breaking new ground. People might not have had the same experiences as others, such as yourself, so maybe you could share your story and help someone in the future.
drgopoos said:
WOuld be great if u could tell the forum what u did
You may not be alone
Click to expand...
Click to collapse
I was busy raging at the time.
I am *still* stuck on o2's OS (but 1.6 which works fine instead of the seriously bugged 2.1, which worked "ok" at first and got so buggy that it wouldn't allow me to answer incoming calls) but at least my recovery is no longer broken.
I can't swap back to ATT though due to a "FOTA name mismatch", whatever the hell that is.
The black screen recovery error seems to be caused by the ROM itself. Certain recoveries simply do not work on certain builds. It seems as though pretty much all of them failed with the build I had. However, I found an older recovery (smaller than the rest at 2.7mb) and used that along with a rooted ZIP format (clockwork) version of 4399.
It was really just about finding the right files and the right combination.
I hope I can upgrade to the ATT froyo when it gets here without issue. For now, I am staying with what works.
Download the attached recovery, flash it and you should be able to update any official rom.
crash6 said:
Download the attached recovery, flash it and you should be able to update any official rom.
Click to expand...
Click to collapse
**I looked through my recovery roms and I had already tried THAT EXACT ROM, so perhaps stop making assumptions, eh?**
The only recovery that worked was the 2.7mb one. I tried many others. They all resulted in a blank/black screen after selection.
The files I used to fix the issue are linked below.
The first is a zip/clockwork version of O2's 4399 build which clockwork can burn. The second is the stock 4399 recovery (2.7mb).
4399-update-streak-stock-rooted-signed-clockwork.zip - 80.1 Mb
recovery.stock4399.img - 2.7 Mb
*This fixed the black screen on all recovery roms except clockwork 1.8.1.7 issue. It won't do a thing for FOTA mismatch.

Unable to upgrade the streak.

I've an O2 streak, Firmware 1.6 build 3883 the baseband ends in -EU, I'm an O2 UK customer oem version ends in 21
After much researching I decided to upgrade to 2.1 so downloaded the O2 upgrade (update-6941-21.pkg) it seems this is the best build.
Copied file to sd card, renamed to update.pkg , double checked the md5 sum was correct then powered off the phone. I'm using Linux to copy files to the sdcard.
Held down both volume keys while powering on, selected second option (update), screen went black but a light could be seen behind it.
At this stage I'm not sure what to expect, the phone doesn't appear to do anything. None of the instructions tell you how long to wait, I expected 10 to 15 minutes max, after an hour and no change I reluctantly pulled the battery, the phone booted straight up into the old operating system (phew).
Tried an official 1.6 rom 4399 build, exactly the same result.
Is my phone being treat as if it has a custom rom is one idea that I'm considering, anyone had a similar experience, anyone offer any suggestions ?.
It's not as simple as just putting the .img file on your SD card. You have to flash a stock recovery. There's a sticky called "Complete Guide to Flashing Your Streak" or something close, that will hold all your answers.
*edit*
Here:
http://forum.xda-developers.com/showthread.php?t=776883
Personally I wouldn't even bother with 2.1
Goto the guide N upgrade to dj_Steve's 2.2 if I follow the guide it's quite straight forward N there is always plenty of help here if u get stuck
DJ_Steve has done a amazing job N made the streak what it should have been. I love BBC iplayer on it..although I now keep going over my T-Mobile broadband allowance LOL
Sent from my Dell Streak using XDA App
Charles: said:
It's not as simple as just putting the .img file on your SD card. You have to flash a stock recovery. There's a sticky called "Complete Guide to Flashing Your Streak" or something close, that will hold all your answers.
*edit*
Here:
http://forum.xda-developers.com/showthread.php?t=776883
Click to expand...
Click to collapse
Thanks for the reply.
It's not apparent to a newbie that to upgrade from a stock rom to another stock rom that you need to flash a stock recovery, at least it wasn't to me (being thick ?).
Maybe it's just a little piece of knowledge that people who've done this before take for granted and it never crosses their mind that newcomers would think otherwise.
Before you replied I managed to upgrade by doing as you said, I flashed the stock recovery with fastboot, put update.pkg on the sd card, held my breath and lo and behold I saw a screen that allowed me to continue (I'm going to try and take a photo of this for other newcomers benefit as in all the posts I read nothing indicated what you should see when upgrading).
I tried upgrading from build 8443 to 2.1 but ended up stuck at the Dell logo, (this was an early build that many people said was better than the last 2.1 release).
Tried upgrading again (different version) and finally managed to get 2.1 on the Streak.
Now for 2.2
Thanks for your help in any case, much appreciated.

[Q] Cannot boot into Recovery

Hey all. I just got a new G Tablet and am trying to install CM7 I was following the instructions to the letter from (Since I an't post links, just google this) Cyanogenmod G Tablet Wiki Full
I got through the 'Installing ClockworkMod Recovery' part and everything appeared to finish successfully.
After rebooting the device, I tried to boot into Recovery to install CM7 and the device just freezes on the ViewSonic splash screen. The screen says 'Recovery key detected Booting recovery kernel image', but it just sits there.
I am able to boot the device into the stock OS, but I can no longer get into recovery.
What can I do?
Tap UI Version: 1,2-4349
Kernel Version: 2,6,32,9-00001-g0e0c333-dirty
Build number: FRF91
Thank you in advanced for your help. Please let me know if there is any other information you need about my device.
Andrew
The key to your post is
Tap UI Version: 1,2-4349
Click to expand...
Click to collapse
You're on the 1.2 bootloader, and CWM .8 will not work on it. There is a versio nthat WILL work, but I, unfortunately don't know the exact link to provide for you. I'll attempt to look it up and get back to you, though.
basically, your G-Tablet, was at some point, updated with the most recent OTA update provided by viewsonic. The update was pulled 24 hours after it was released. You're not lost with 1.2...you have many options. You can either stay on 1.2 and flash any of the many 1.2 roms...some are listed in the development section, others can be found on "another" forum.
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Download
clockworkmod v3.0.2.8 (1.2 branch / NIA rev5) Link: http://www.mediafire...2flqn8b10ebcq44
md5sum: ac4d728d74a6b608cce588d2649e79f3
(updated on 5/15/2011)
clockworkmod v3.0.2.8 (1.2 branch rev2) Link: http://www.mediafire...x61q8jlu2dx8i9u
md5sum: 48c0c40175ab38cebc1199f9d3be8a7d
(updated on 5/05/2011)
THIS REV2 VERSION HAS BEEN TESTED MORE, but nandroid restores are not working properly. Rev5 corrects that, but I need more testers to confirm stability, please!
Many thanks to bekit and rothnic, for their work with clockworkmod!! Their documentation is what assisted me to get this functioning.
NOTE ON CWM: Do not use the Android GUI tool to wipe user data, or else cwm will get stuck in a reboot loop! If this occurs, there are two ways to fix this:
1- ADB required
In clockworkmod, go to mounts and storage and mount /system. Then, run this on your local PC:
adb shell
cd /system/bin
./fixrecovery.sh
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
2- nvflash required
Using the 4349 nvflash image, run this:
nvflash --bl bootloader.bin --download 9 part9.img
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
Click to expand...
Click to collapse
TJEvans (is it ok if I call you TJ for short?) thank you very much for your help, I appreciate it very much. I'm sorry if confuse some terms here as I try to address your posts inline below, but I would definitely still consider myself a novice at this process of installing custom roms.
TJEvans said:
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
Click to expand...
Click to collapse
This is a brand new G Tablet. I litteraly got in the mail today from Tiger Direct. I'm wondering if the Clockworkmod I tried to install is responsible for the custom kernel.
TJEvans said:
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
Click to expand...
Click to collapse
I don't necessarly need CM7, but that is what I have on my Nook Color, and I really like it.
The main question I have is that right now, I cannot get into clockwork or stock Recovery at all. I do have adb working, so I would think my next steps will require me to use adb.
At the moment since I can't get to recovery I seem to be stuck. Is there a process somewhere I can get recovery working again using adb?
OK...let's try something. It looks like you may actually be in stock recovery, but there's nothing for it to recover.
do you know of a way to get a file and a folder onto your internal SD?
if so, let's edit the instructions to be able to flash to 3588 stock...
What you need:
1. A stock 3588 image renamed to 'update.zip' (http://tapntap.http.internapcdn.net/...-3588-user.zip)
2. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
Click to expand...
Click to collapse
if yo ucan get those on the SD, then when you reboot, the stock recovery will run and install stock 3588 1.1 based rom and recovery, then you can install your CWM .8.
I have never used NVFlash or ADB, or APX...I have no experience with them. I'm just here helping people that have compatibility issues between 1.1 and 1.2 bootloaders.
After all, the key to fixing problems, is to first find out what the problem is...
I wish I could help more, but I've seen more and more people softbrick their g-tabs by using NVFlash than anything else. I'm not ready to go messing around with my own root files, yet.
If you can get that file, and that folder onto your SD, then stock recovery will automatically recognize it and run it...
I may have just really screwed things up. I ran 'adb reboot recovery' and I gets to the Splash screen with 'Booting recovery kernel image' and gets stuck. Now, I can't get into the device at all.
Also, none of the links in your posts seem to work for me.
try them from the original post, then:
http://forum.xda-developers.com/show....php?t=1039000
sorry, like I said, I'm not a techy...just a guy that doesn't like to see people suffer...
TJEvans said:
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Click to expand...
Click to collapse
It's far from being taboo since it's the honeycomb bootloader... their recovery was blue for a reason...
maybe they pulled those OTA update because they had not licensed honeycomb anyhow, 1.2 is perfectly good to install as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Ok, I was able to get the device working again using NVFlash. (http forum,xda-developers,com/showthread,php?t=861950 replace commas with periods).
Now, I have the following:
Tap UI:1,1-3588
Kernel is still: 2,6,32,9-00001-g0e0c333-dirty
I don't know anything about this kernel, or how I got it, other than maybe it came with my first errant clockwork install.
Can you give me some pointers on how I should proceed? (I would still like to get to CM7 at some point, but I don't know if I should get a different kernel or go back to the stock kernel as well)
GREAT NEWS....glad you god it running so far.
OK, that may be the stock kernel...the numbers looked familiar to me, and I've never seen the stock kernel on that report...so, I may be mistaken.
in any case, you are now back on stock 3588 1.1 bootloader...
Now, you should be able to install the CWM .8 that you tried before, and flash CM7 from there...basically, follow the guide you followed before. but this time, it should work fine, since you are on the right bootloader.
Just remember, research ANY new roms you want to try to make sure what bootloader they are on.
to P00r:
as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Click to expand...
Click to collapse
see, I didn't even know that...
The thing I'm seeing, is that Clemysn posted the BOS infromation here, and tried to emphasize that it's a 1.2 Rom...The 1.1 rom's though, do not indicate that they are 1.1 Roms. when 1.1 was all that existed, it made no difference, but now that there is another option, they should at least make sure to add "PLEASE BE SURE YOU ARE USING A 1.1 BASED BOOTLOADER BEFORE FLASHING THIS ROM!!!"
As you can see from Imarikinrat's post, he bought a supposedly factory G-Tablet with 4349 prepackaged on it...now, granted, you and I both know that it's more than likely a refurbished one, as I can't see Viewsonic intentionally releasing product with a bootloader and firmware that was pulled from their updater...
in any case. Roebeet kinda predicted that this would happen a bit. Since most moderators on XDA downplayed the impact of 1.2, it's gone fairly ignored. Think about Imaricanrat's post for a second. Had he not posted his system information there is no way that we would have known that it was a bootloader conflict. It would have been assumed that he was on 1.1 bootlaoder with a "brand new" g-tablet (seriously, man, I'd check that thing with a magnifying glass to make sure that there are no scratches or anything that would indicate that it was anythign other than BRAND NEW)
anyway...had he not posted that he was on 1.2, then who knows what advice he would have been given.
Well, now I'm back to my original problem. I cannot get into Recovery. When I start holding Power and Vol+, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
I have tried putting the recovery folder and update.zip in the internal memory, and on an sd card to no avail. Any other suggestions?
that most certainly sounds like stock recovery to me...
I'm at a loss...it worked fine for me when I flashed to 4349 from stock 3588...just ran and installed, then I ended up on 4349 stock...
you're following the CM7 install guide? Or are you trying to install CWM at this point? I never installed CWM myself, as mine came with it on it.
I'm trying to install clockworkmod so that I can install CM7. Is that the right way to do it? I know there was a stock recovery gui that I cannot get into now.
as long as the recovery folder is on the SDcard, it will automatically attempt to run it...
picture it this way...remember back in the day of windows 3.1 In some cases, if you inserted a floppy disk with a boot file on it, it would check there first, then boot from internal memory...
So, the recovery folder is telling it to run the file in it, which unpacks and installs the update.zip.
once again, though, I never installed CWM myself, but from what you're saying, it should be working.
what happens if you remove the folder and file (after running it), and attempt to go into recovery again?
When I remove the file, folder, and SD card and try to get into recovery, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
hmm...the box with the arrow and progress bar indicates that it's trying ot run something from recovery...weird..
ANYONE ELSE???
I'm not experienced enough to help...anyone else know enough about flashing CWM from stock, or flashing CM7, that can help out, please chime in.
thanks.
and sorry Imarican...I tried, but once again, no techie here.
No worries man, thanks for your help. Have a good night.
Update: Ok, I think somehow this whole process messed up the 'Recovery Partition' on my G Tablet for whatever reason. When I performed the NVFlash back to stock, it managed to 'fix' the majority of the device, allowing me to boot normally into Tap UI:1,1-3588. However that flash did not fix my Recovery Partition.
With all of that in mind, I found instructions on XDA to install 'clockworkmod via nvflash' (Since I still cannot post links, just google that and it should be the first link, also it's XDA thread 1058649).
After following those steps, I am now able to boot into Recovery which is now Clockwork Mod Recovery, and hopefully *crosses fingers* be able to flash CM7.
Given that I will probably never go back to stock anything on this device, does anyone know where I can download the 'Stock Recovery' for the G Tablet?
so is the point of this article Tiger direct sell used products as new?
so is the point of this article Tiger direct sell used products as new?
Click to expand...
Click to collapse
unconfirmed...what we know is that he had 1.2 4349 out of the box, stock firmware. There are a few possibilities. This could be a Tiger Direct return that was repackaged and sold as new. It could also be a direct from VS return that was repackaged as new, OR, VS actually sent a stock of G-Tablets to Tiger Direct that were packaged with the 4349 firmware on it.
Either way, people need to be careful when flashing roms and such. XDA has not, so far, made it clear which roms, kernels, and CWM versions are good on which bootloader. Some have been asking that devs start exiting posts to indicate which bootloader is needed for each mod, to attempt to avoid confusion.
We must also realize that new G-Tablets are being bought every day, and not every owner is knowledgable of the issues of the recent past, with VS, NVidea, 1.1, 1.2, etc. Most people probably, reasonably, assume that they can open it, root it, and start flashing whatever they want, not even aware that there is a difference.

[Q] Can anyone explain the builds to me please?

I have been searching all night and can not find what i am looking for.
Can some one explain why the dell streak 5 I have is at version #347 15274 but i see that latest retail version as # 351 15609.
My question is what are the differences between the two? I also see a new build from hong kong version #354 15881.
I already have a rooted phone but i have never upgraded the version before. Is it even worth it?
I guess i am just confused.
Actually there is a lot of info at the XDA Streak Wiki.
It appears that 347 is one of the ROMs that TheManii does not have files for. You should contact him about sharing your ROM with him, so it can be posted to the Wiki.
AFAIK 351 is just bug fixes. I am running 351 and have found it to be very stable.
marvin02 said:
Actually there is a lot of info at the XDA Streak Wiki.
It appears that 347 is one of the ROMs that TheManii does not have files for. You should contact him about sharing your ROM with him, so it can be posted to the Wiki.
AFAIK 351 is just bug fixes. I am running 351 and have found it to be very stable.
Click to expand...
Click to collapse
Thanks for your quick reply, Would you recommend the upgrade? Also which method would you recommend for doing this.
NotoriousHaze said:
Thanks for your quick reply, Would you recommend the upgrade? Also which method would you recommend for doing this.
Click to expand...
Click to collapse
I have never used 347 so I can not make any comparison. I do know that 351 runs very well for me. The reports that I see for 351 are better bluetooth and wifi connectivity.
I would try downloading the 351 .pkg file directly to your phone. When the DL is complete open your notification bar and tap on the completed download and it should install. Using this method preserves your apps and settings. You should be connected to WiFi.
Please note that on some phones (probably depends on what apps you are using) you may see issues and have to do a factory reset after the upgrade which will mean setting up your phone again, so back everything up.
You must have the stock recovery for 347 on your phone for this to work. If you still have install-recovery.sh on your phone (never renamed or deleted it) your phone will still have the stock recovery on it. See this info about the recovery image.
If the upgrade does not install rename the file to upgrade.zip and make sure it is in the root of your SD card and install it from recovery.
Read this flashing guide.
Please contact TheManii before upgrading to see if you can get the 347 files to him.
I already have a nandroid of 347, what i dont have is a pkg which i would not expect him to have.
TheManii said:
I already have a nandroid of 347, what i dont have is a pkg which i would not expect him to have.
Click to expand...
Click to collapse
OK - did not know that.

[Q] rom manager not recognizing fascinate

This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water

Categories

Resources