yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] TBarb169:
So I loaded this rom today and almost immediately after I started receiving phantom text messages from 8737. I have received 4 of them in the first hour, and one about 4 hours later. Any ideas or is it a coincidence?:confused:

update, ok i found that it may have something to do with gosms, but i never had that issue on any previous roms (unnamed rom).
[Streak 5 Q&A, Help & Troubleshooting] bazzoon:
EDIT: My phone is now working. Read at end of OP Below for the trick. Credit goes to thomascw: http://xdaforums.com/showpost.php?p=21173699&postcount=69

My phone is going into a cycle that I am unable to get out of.

I followed instruction on how to fastboot flash recovery and update to whatever rom version.

My phone baseband is the 347 US stock rom. Here is the cycle my phone is getting into:

I have placed the update.pkg in the root of my sd card (At various times I tried various roms but always matched the region between recovery and rom)

I flash the recovery image using fastboot. Both my phone and my command prompt (I use linux) say OK and writing is done.

I do fastboot reboot and the phone reboots fine.

I hold the (vol+,vol-,pwr) keys to boot into recovery. When booted, it always show the correct recovery image that I just flashed. So seems OK!

I highlight the 2nd option which is the update from sd card. It goes fine and it finishes installation.

The phone boots but it gets stuck at the dell logo indefinitely. The phone is not responsive at this point and only removing battery is the option.

I replace the battery and let the phone boot but it shows me this message

Apparently the device is rewriting stock recovery into the recovery partition.

The phone reboots after finishing the copy into recovery mode again asking me to reset, update, ...etc.

This cycle always happen no matter what rom versions I choose. Well, stock roms only. I did not try modified ones.

I am unsure how to get out of the cycle as I tried every option, like reseting after flashing. I even flashed a backup copies of the 347 system and boot images. Always goes at the end to rewrite the stock recovery image (steps 7 and 8 above).

- SOLVED: last night, I flashed 360 as mentioned in steps 1-5 above. now, Instead of step 6 above, do these:

After streakmod recovery image flashed, fastboot reboot then vol+,vol-,pwr to go into recovery mode.

choose option 2 (upgrade from sd card) --- this will take you into another menu with more options.

Choose factory reset, wipe data, wipe cash,dalvik cash and all that.

Next get to advance option listed. From there, choose fix permissions (not sure if this is necessary but I did it anyway.)

From android back button, go back to previous menu.

Choose the reboot option.

Again hold vol+,vol-,pwr to go into recovery mode. Now choose factory reset (not sure if important, but did it anyways)

Phone will reboot into the rom you installed in step 5 above.

It worked from first time. I got encouraged and I even followed the steps again and I installed GB stock rom and also worked from first time. I am not sure I like the GB 407 rom over the 360 ROM, especially I get the annoying flashing lights every now and then because of the mismatch between the 407 region 14 and baseband region 00. But this is another issue.
[Streak 5 Q&A, Help & Troubleshooting] marvin02:
Did you at some point try a Gingerbread based ROM? I have seen others have issues reverting to Froyo after that.

If you can get to recovery, for the ROM you want to run:

Make sure the pkg file for your ROM is on the root of your SD Card and is named update.pkg

Flash the amss.mbn file, dsp1.mbn file and the recovery.img with fastboot.

use the command fastboot reboot to reboot your Streak and make sure that you go directly to recovery

Now select step 2 and do the update

Since there is no pkg, recovery, amss or dsp1 files for BB 347 you will need to use a different baseband (I use 351, 360 is the latest). Use 407 if you must have Gingerbread.

ROM and related file Downloads

Flashing Guide

My take on Streak modding

Edit: the above steps should work even if you have never tried installing a Gingerbread ROM.
[Streak 5 Q&A, Help & Troubleshooting] bazzoon:
Thank you.

I've done all the steps you mentioned, except the second point. I never tried them. At least I have some new steps to follow. To which partition shall I flash the *.mbn files? Where do I find these files for a specific rom?
[Streak 5 Q&A, Help & Troubleshooting] bazzoon:
OK. Found amss and dsp1 files that are bundled with recoverySM.img (custom one), can I use these files with any ROM or are they rom and/or regional specific? I am confused because I do not see these files in the wiki page with the stock roms.
[Streak 5 Q&A, Help & Troubleshooting] bazzoon:
OK guy forgive my ignorance. I found the corresponfing .mbn files under manii's directory provided by your links.

I am trying them now. Crossing fingers and will let you know how it goes.

Thank you.
[Streak 5 Q&A, Help & Troubleshooting] bazzoon:
Back to the cycle. I added flashing both amss.mbn and dsp1.mbn to the process, but got the same pattern. I used the 360 build downloaded from mirror2.streakdroid.com/manii/360 directory. After the flash, the device hangs on dell logo screen. I remove the battery and replace it. I turn it on, and let it boot but this time it reverts to the emergency stock recovery image 347.

I will try tomorrow to get custom GB roms and see if they work.
[Streak 5 Q&A, Help & Troubleshooting] _n0p_:
That's a well known issue with 347 firmware.

You should use streakflash tool to restore it to 305 lowlevel fw version, and continue from that point.

Very detailed article of using streakflash:

http://forums.whirlpool.net.au/archive/1557150
[Streak 5 Q&A, Help & Troubleshooting] apirec:
I'm experiencing exactly the same problem: I tried to update 347 to 360 and now I'm stuck at the boot logo :-(

I tried several stock images and yet no luck... Even the article mentioned above won't help me out ouf this misery.

Is there something else I could try?
[Streak 5 Q&A, Help & Troubleshooting] andy1weir@hotmail.co.uk:
ive also had this 4 or 5 times, so i replaced my inner sd with a 2gb sdhc ,think maybe the card was at fault
[Streak 5 Q&A, Help & Troubleshooting] thomascw:
Dikos found an answer some where

Flash stock 360 recovery

Reboot

Hold Volume buttons

Option 2 - Recovery mode

Install stock 360 rom.

Fastboot

Flash streakmod

Hold Volume buttons

Option 2 - Recovery mode

wipe cache partitions and dalvik cache

Reboot

Hold Volume buttons

Option 1 - Factory Reset

Worked for me,now using 407 olleh, was on 360 for an hour,the key appears to be flashing back to streakmod and wipe cache partitions and dalvik cache before factory reset

I think this should be stickied
[Streak 5 Q&A, Help & Troubleshooting] apirec:
Well, whatever a "dalvik cache" is, it even works without clearing it!

Unfortunately my baseband is still at 347. Is that the reason for my leds to flash about 9 times every minute?
[Streak 5 Q&A, Help & Troubleshooting] thomascw:
apirec, clear dalkic cache is under advanced options in steakmod recovery. The flashing is probably related to needing to flash the right amss and dsp1 mbn.
[Streak 5 Q&A, Help & Troubleshooting] Mohan Nade:
path to streakmod

Can anyone please confirm the link to latest streak mod.

Is it same as the link on

http://xdaforums.com/showthread.php?t=840326 for

recovery-v0.3.2.8-beta.zip

-Mohan
[Streak 5 Q&A, Help & Troubleshooting] apirec:
No, I did clear that cache, too (for the first time). But then I did the procedure again (without clearing that cache) to get the right baseband and to get rid of the flashy leds.

How would I flash the right amss and dsp1 mbn?

Yes, that's the correct link.

---------- Post added at 10:31 AM ---------- Previous post was at 10:02 AM ----------

Ok, found it myself: http://mirror2.streakdroid.com/manii/360/

But what are the other files for? Will it do any good, if I flash them, too?
[Streak 5 Q&A, Help & Troubleshooting] thomascw:
If you have flashed recovery and gone through update, as far as I know,all you need are the amss and dsp1. I've read that the update.pkg reflashes the baseband, not true on my phone. One of the multirecoveryflasher tools has a baseband flasher built in. I havent used it, but it I think it probably just flashes the above 2 files.
[Streak 5 Q&A, Help & Troubleshooting] bazzoon:
Thank you here again for pointing out the solution. I have updated my OP to reflect the solution to this problem.
[Verizon Droid Incredible 2] armchairbear:
I love using AOSP roms because they're blazing fast and smooth. No Sense rom that I've tried so far can match the speed. However, the camera on the AOSP rom takes very grainy pictures no matter what I try. Sense rom cameras take very good pics, so it must be a software issue.

I've already tried using a few different camera apps like camera360 and zoomfx. No dice. I've even tried the camera from MIUI rom. I guess there's something about the AOSP framework that affects the camera.

Is there a fix for this? I've searched and others have had this problem, but there wasn't a definite solution. Just thought I'd ask again here.
[Verizon Droid Incredible 2] knipp21:
Did you try messing with the settings of the miui cam
[Verizon Droid Incredible 2] ubuntunerd:
The camera on my miui takes amazing pictures I know this because my fiance is a graphic designer for ups and we have printed lots of pics from my miui phone and she always tells me you can have the best camera on the world but if you don't have a good printer you wont get the best quality pictures. It all depends on the output of the printer I'm not saying that you don't have a good printer I'm just saying I have seen the quality of the pics taking by my phone printed at her job and I most said they are amazing and they are huge I'm talking portrait size
[Verizon Droid Incredible 2] TheAtheistReverend:
My understanding is the MIUI camera can be installed on AOSP roms, though I have never been able myself. But this would be the best "fix" for the cruddy AOSP cams out there.
[Verizon Droid Incredible 2] Amphibliam:
Just saying, ROMs like Zeus and GingerBang Sense are just as fast as AOSP in my opinion.
[Verizon Droid Incredible 2] collinray:
I agree. For the most part during good light situations, I can get a decent picture using AOSP or MIUI, but if the lighting isn't 100% optimal the pictures don't really turn out that well. Over all the sense software/driver integration does give me better pictures as well. Especially when I view them in full screen on my computer. I've messed around with the settings too, but I just believe that there is optimization in sense because of HTC owning both the software & the drivers for the phone. As funny as it sounds, the better camera quality is the one thing that really keeps me coming back to Sense. I love the camera interface in MIUI, but after a bit, i always come back.
[Verizon Droid Incredible 2] APeaceofStrange:
I still feel aosp is faster than those, but i do agree the difference is not enough leave sense if you need the best camera performance or love the launcher and widgets combination which are awesome. I think many run aosp though because of the combination of mods/themes available and we feel special when we explain to others that we are running "pure" android.
[Verizon Droid Incredible 2] ubuntunerd:
I heard the same from others but I think I'm gonna try this theory for myself
[Verizon Droid Incredible 2] dirkdigles:
Bringing up this old thread.

I just did some quick testing with the AOSP camera (Aeroevan's CM7.2 kang). I'm using the MIUI camera, but have noticed the same effect no matter what camera app I use (default, CameraZOOM).

It appears that the grainy effect on the pictures is due to the ISO setting failing to adjust with changes in settings. I took a few pics with ISO set to Auto, 100, and 1250, and they all came out identical (same amount of grain, etc).

If the ISO was being adjusted correctly, the ISO 100 pic should have had significantly less noise (grain) than the ISO 1250 one.

As my best guess, it would appear that the AOSP rom's camera driver is incomplete / buggy, as changing the ISO in settings does not change the actual ISO of the camera/picture.

I also noticed that the ISO data is being reported incorrectly in the picture file details. The pic I took @ "ISO 1250" (according to camera settings) is reported as being "ISO-129" in the EXIF data.

I've uploaded a full size pic just for example:

Pic of Chicago

I would think that this picture, taken in broad daylight, should have nearly no noise whatsoever, yet it has quite a bit.

Any feedback on this? Or is this as good as it gets for this camera?

EDIT: Upon further investigation (viewing original resolution pics taken by the ADR6350 on Flickr), it seems that nearly everyone's pics, when viewed at full size, are rather grainy, no matter the light level. Perhaps this camera just isn't very good.

EDIT #2: Here's a pic of a similar scene from an iPhone 4 - there's just no comparison in terms of overall quality (not trying to bash the DINC2, I'm just a bit disappointed with what I'm seeing).

EDIT #3: A pic from an Incredible S. Little noise, even in low light. WTF
[Verizon Droid Incredible 2] jbarcus81:
I feel this is true for all AOSP .. the camera feels incomplete at best... It doesn't even focus properly when recording video.. if you start recording, don't get any closer or farther away!!! It won't focus.. Our phone has the capability to take wonderful pictures as long as you stick with Sense.. AOSP will ruin any chance of taking a decent picture with our hardware.. I've tested roms side-by-side and AOSP is at the bottom of the barrel in this category for me..
[Verizon Droid Incredible 2] TheAtheistReverend:
The Sense camera is significantly better that any AOSP camera in my opinion. I would love to have the time to shoot a photo with AOSP then NAND back to Sense and shoot the same photo to compare.

If no one else does this, I will as soon as I have a good opportunity. Pictures should be posted for comparinson.
[Verizon Droid Incredible 2] dirkdigles:
Please do! I'll try the same; I currently have TSM's vanilla installed in a bootmanager slot.

Update: I just booted into TSM Vanilla to give the camera a quick look. I took a few pics indoors, and changed the ISO for each one. It looks like it's having the same issue! Both pics I took (one @ ISO 100 and the other @ ISO 1250 per the camera settings) came out looking the same, and the EXIF info said they had the exact same ISO. :confused:

PS - I linked a couple other pics for comparison in my reply a few posts up. One from an IncS and the other from an ip4

Example 1, Phone = Incredible 2, Fully Enlarged

Example 2, Phone = Incredible 2, Fully Enlarged

These examples seem a bit less noisy ... it's obviously not as good as a dedicated digital camera, but a crapload better than what I'm getting now !!
[Verizon Droid Incredible 2] ericsdeadinside:
I love the vintage effects on sense 3.5 roms. I would have to spend 20 minutes in Photoshop to reproduce that.
[Verizon Droid Incredible 2] ericsdeadinside:
http://db.tt/ZxhpK8C2

Here's one I just took outside with camera 360 at 8mp on miui
[Verizon Droid Incredible 2] dirkdigles:
Not bad - do you have some sort of post-processing or color effects enabled? The colors in that pic are bizarre.
[Verizon Droid Incredible 2] ericsdeadinside:
Yeah that is on the Vintage setting.
[Verizon Droid Incredible 2] ericsdeadinside:
Here's one with no effects

http://db.tt/x5DUhdT4
[Verizon Droid Incredible 2] dirkdigles:
Looks pretty good. Definitely better than what I'm getting.

I just saved your pic file and looked at the properties - for some reason, your file reads as having horizontal & vertical resolution of 96dpi, whereas mine says 72dpi. I wonder if this has to do with the issue ??
[Verizon Droid Incredible 2] ericsdeadinside:
Are you using camera 360?
[Verizon Droid Incredible 2] dirkdigles:
For my pic I was using the MIUI cam (but I'm running CM7.2). Seems that CameraZOOMfx and the default android camera have the same result for me.

It's almost as if the camera is taking a picture at a lower resolution (like 4MP) and extrapolating (interpolating?) it out to the 8MP picture size (a possible explanation for the the 8MP pictures seeming a lot less sharp than they should be).
[Verizon Droid Incredible 2] ericsdeadinside:
Cool. 360 has a super high quality setting. That must make 96dpi.
[Verizon Droid Incredible 2] TheAtheistReverend:
Here's a few samples, all with the highest settings possible and the ROM and camera listed on the white sheet of paper in the photo. All photos were taken from the same location with the same level of lighting (pretty bright, but not sunlight). I also made sure the camera was resting on a flat surface to minimize user induced blur.

Stock Sense Camera

Stock Camera360

Stock Camera360 w/enhance

Stock CameraEffects

MIUI Camera

CM7 Camera

Which do you think has the best detail? Try to read which camera is being used on the paper, look at the little stones on the outside of the candle just to the right of the chair on the radiator.

You may notice the Stock Sense photo is the smallest file size and the Camera360 w/enhance is 3X bigger with the same dimensions.

The color disappoints me in all the photos except for the Camera360 w/enhance photo. They all look washed out. I think it's pretty bad.

Daylight photos aren't as bad with the washed out colors if I remember right.

Next is taking photos in broad daylight with the different cameras. Too bad I'm in Minnesota, land of 10000 clouds. It might be a while.
[Verizon Droid Incredible 2] ericsdeadinside:
I think the stock Miui cam is the best. Its grain is more uniform and colorless. Whereas the sense cam's grain is made up of various colors and is sort of distracting. That being said, it is a just a phone camera and no flash used.
[Verizon Droid Incredible 2] dirkdigles:
Excellent work - I looking forward to seeing the outdoor shots. It's interesting to see the stock sense camera isn't that much better than the CM7 one.
[Verizon Droid Incredible 2] jbarcus81:
Wow.. My beliefs are changing right in front of me!!!! Who knew?? They all look the same!! But I will say MIUI looks better!!! WHAT??!?!??
[Verizon Droid Incredible 2] ChrisDDD:
Great test, and it really does show that the differences are very minimal. I do some photography semi-professionally and a lot of graphic design/photoshop work professionally, and to me it looks like the Sense camera probably runs a slight despeckle filter on the photos - the same grain is there, it's just been softened a bit.
[Verizon Droid Incredible 2] Tarpit_Carnivore:
A lot of cell phone cameras do bad with indoor lighting. I'd be curious to see the same test but done outdoors. I always found the Inc2 to do way better outdoors than indoors.
[Verizon Droid Incredible 2] ChrisDDD:
Yup, low light is the bane of all digital cameras, and the smaller the sensor, the worse they handle it. I never expect much from a cell phone camera, so I never found it to be a major issue.
[Verizon Droid Incredible 2] TheAtheistReverend:
Finally had a chance to shoot with a couple roms during the day. All of these were set at the highest resolution and highest quality jpg compression available. Good for comparison?

Stock Sense Gingerbread Camera

Gingerbread Sense Camera360

CM7.2 Stock Camera

CM7.2 Camera360

Ecliptic Sense ICS Stock Camera

Ecliptic Sense ICS Camera360

UKB X Sense ICS Stock Camera

UKB X Sense ICS SCamera360

CodenameAndroid 2.0 (CM9 Kang) Stock Camera

LINKS FIXED!
[Verizon Droid Incredible 2] Tarpit_Carnivore:
Your links are erroring on Dropbox probably due to permissions.
[Verizon Droid Incredible 2] TheAtheistReverend:
Thanks, I thought I had made that folder public. Guess not. :silly:

FIXED!

I like looking at the far away house and its siding or fence to look for detail... Leaves move, so I don't look at the trees.
[Verizon Droid Incredible 2] Triscuit:
Now with all this info at hand for AOSP/AOKP ROMS do we have the ability to flash a new cam?
[Galaxy S I9000 Q&A, Help & Troubleshooting] envirojay:
I flashed my phone with onecosmic ICS 4.0.3 with the glitch
[Galaxy S I9000 Q&A, Help & Troubleshooting] TaLeNDiL:
I just flashed it today and no signal issues by my side. Which rom did you flashed ics from?
[Galaxy S I9000 Q&A, Help & Troubleshooting] mbc663:
Flash a different modem. See the sticky thread.
[Samsung Galaxy Nexus] kbrian:
Do i need to reset my battery stats? Or is it already accurate? Also if i do need to reset my battery stats how do i? (not rooted)
[HTC Flyer, EVO View 4G] globatron:
This procedure applies to both flyers and view

Required downloads

First download the Gingerbread RUU for your device from this thread.

If you don't have adb and fastboot on your PC

Get fastboot and adb tool for windows here

Get Fastboot and adb for linux here

I don't have a simple bundde for Mac, would welcome a link if anyone has one.

Download my universal misc_version and unzip to obtain the misc_version file.

Download tacoroot

Place both the misc_version and tacoroot.bin files in the same directory as adb

Procedure

Check the version number for your gingerbread RUU

In my example I am using this RUU: RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.08 9BU_3809.05.04.10_M_release_194964_signed.exe

The version is the part highlighted in red.

Boot your flyer up to android if it's not already on, with usb debugging enabled and connect it to the PC.

Run the following adb commands

adb push tacoroot.bin /data/local/
adb push misc_version /data/local/
adb shell chmod 755 /data/local/tacoroot.bin
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/tacoroot.bin --setup

At this point your device will reboot to recovery

Simultaneously press Volume Up, Volume Down and Power

Reboot your device

Run the following command

adb shell /data/local/tacoroot.bin --root

Your device will reboot, do not worry if it does not boot fully, it doesn't matter for this procedure, and it is a side effect of this root exploit.

Run the following command:

adb shell /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]

Note that the number in RED is the version number retrieved in step 1.

Reboot to fastboot:

adb reboot bootloader

Relock the bootloader:

fastboot oem lock

Go back to fastboot mode ( lock causes the device to reboot )

Run your RUU ( if on linux or mac, see other similar threads from me on how to RUU on those OSes )

Special Thanks

jcase for the tacoroot.
[HTC Flyer, EVO View 4G] paranoidpenguin:
s*** too late!!!! :rolleyes:

Yesterday I unlocked my Tab via HTC Unlock, hopefully I'll never need the warranty ...

But thanks for your detailed and very helpful instructions in this forum, don't know where I would be without you.
[HTC Flyer, EVO View 4G] Tutmanichtun:
I think there is a mistake, it should be:

adb shell /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]

But: it doesn't work. The device hangs in the boot process after flashing the RUU.
[HTC Flyer, EVO View 4G] globatron:
The typo correction is correct but that it doesn't work is not. I've done this multiple times with both my own and other peoples devices and it works just fine. Make sure you used a gingerbread RUU and the it flashed completely. AND that you not doing this on an S-OFF device.
[HTC Flyer, EVO View 4G] Tutmanichtun:
Thats the fault. My Flyer is S-OFF. Is there a possibility to get back to GB anyway?

Edit: Found a Solution. It cost me the whole day, but now it works.

The bad note: I don't know the Link with the solution. But it was in this Forum.

I got to it by Flashing a 3.2.1 ROM, and after that a 2.3.4 ROM via Goldcard-Method. (Via the SD-Card.)

During the process the Bootloader creates a message, that the installed hboot version isn't downgradeable or something like that. I hacked that into Google and it throws out a Thread in this Forum with the Solution.
[HTC Flyer, EVO View 4G] echaru:
Might be a little off topic, but the title:

[Pocedure]No HTC unlock HC-GB downgrade for official HC OTA

"[Pocedure]" is missing a letter r
[HTC Flyer, EVO View 4G] globatron:
Cool. someone who actually reads :D

Thanks echaru, fixed.