Database Info

[Q] Darn boot problems, MIUI on Samsung Infuse

Forgive the title, I need it to make it interesting to get some views. Now that's said, let me get to it.
I recently tried to flash MIUI onto my Samsung Infuse. I had Infused ROM v.2.2.3. I must have messed up because now I'm having trouble getting my phone to start. When I power on, it briefly shows the Samsung logo (for about 3 sec); then for split second an alternate screen flashes on my screen just before my phone shuts off. Now, I've tried to load CWM(red version) with the 2/3 button technique; however, I haven't been able to get into that GUI.
I have been able to get into the Download screen, for Odin. But, I was hoping there might be some sort of way to solve this problem without resetting my phone to stock.
Questions
1. Can I utilize the Download screen to re-implement or re-flash my ROMs on my phone; without loosing data
2. Is there a way that I can force my way into the CWM GUI?
3 If none of the above are possible, where can I get information Odin for the Infuse; and where can I download the program?
Thank you for reading, and thanks for the help in advance!
Joaquin

I wasn't going to reply to your thread but you caught me in a good mood. head over to the dev forum and you will find everything you need to get your phone back. That's all I'm goin to give you. the more you search and experiment the more you will learn

Already found somethings that are helping...
I didn't post for as a resource, just thought that if someone knew where to look they'd point me in the right place.
For anyone who might need a nudge; this link will direct you to complete recovery http://forum.xda-developers.com/showthread.php?t=1092021

Did you follow the directions exactly as it says? Did you ever get into blue cwm and flash miui a second time?
Sent from my SGH-I997

I wouldn't recommend MIUI to anyone who isn't atleast a little experienced in flashing ROMs, and are sure won't panic if they find their system soft bricked.

went to http://galnetmiui.co.uk/landing/weekly-builds/ downloaded infuse rom using miui build 112230 wiped data,cache,dalvik applied installed galnet miui rebooted does not load stays on samsung logo wiped data,cache,dalvik reinstalled galnet does not work, used blue cwm, returned phone to stock froyo, using odin reinstalled galnet using green cwm, still doesnt work, dont know what im doing wrong, please help, do i need to install gb bootloaders?
Sent from my SGH-I997 using xda premium

[Q] Phone boots very slow! Huge problem!

My problem is when I turn on the phone, the Google logo stays stuck and after unknown minutes boots in with the software animation, but very slow! First a little history of my upgrades with this phone.
My friend bought me Nexus S T-mobile version for US 6 mounts ago, and the phone was with Gingerbread 2.3.4. After reading many post from here, I decided to upgrade because I can't upgraded 2.3.6 OTA. After many hours I finally upgraded it to 2.3.6.
Then ICS came out, and again, I upgraded to 4.0.3. Then, a few weeks ago, I got the 4.0.4 OTA notification. Happily I taped yes. And then before two days ago, my phone just died. I don't know how.
I have 115 installed application, no music inside, no ROOT - just pure stock. I was in my college room and I left my phone on the desk right in front of me and after few minutes when I looked at the phone, the Google logo was there. I didn't give the phone to anyone to picks or anything. When I get home, I turn the phone on and still the Google logo just was there doing nothing and like I said before, after unknown minutes the phone boots in with very slow animation of the ICS software. I decided to install Clockwork Mod recovery 5.0.2.0 and root the phone. After reading many tutorials I installed CWM recovery successfully. Then I tried to downgrade to 2.3.4 and successfully I did that to.
Now after doing all this things to this phone, after so many hours in pain, the phone is nothing like one week ago. The booting is very slow, the animation is veryyy slow, and I don't know what to do anymore... I think this is hardware problem.
Please help me solving this problem, I really expect someone here to know what is the problem and will help me in anyway. I'm desperate, and I don't know what to write here to tell you how desperate and sad I am...
Thank you in advance.
p.s. sorry for any grammar mistakes.

http://forum.xda-developers.com/showthread.php?t=1572307&highlight=factory+images

yeah, definitely flash the factory images, you'll have to reflash cwm after though

Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!

muldy said:
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
Click to expand...
Click to collapse
not if youre a crackflasher(flash stuff often). i see my boot animation 5+ times daily, if not much more

Yeah.. I forgot that...
When I had the Htc Magic, I used to flash it a LOT
I like Stock, the auto-updates...

dewaffelhaus8 said:
yeah, definitely flash the factory images, you'll have to reflash cwm after though
Click to expand...
Click to collapse
I flash with the official images from here and I reflashed cwm.
muldy said:
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
Click to expand...
Click to collapse
I don't reboot that often, my phone itself reboots... I need to fix that problem, the slow booting, restarting, slow software... I need to know is it a hardware problem or software, because I did everything related to software problems...

Totally bricked!!

Hi guys,
Well it just happened the unwanted.
After an unsuccessful upgrade to 20E I'm left with a bricked phone.
My phone is an European version (p920). I've tried all procedure described on this forum about how to get him back to live but all ended into a failure. The bin methode gave a partial "success" but at the end it made things worst cause it messed up my baseband and now it doesn't have a GSM network and there's no IMEI.
Well I tell you how all these happend.
A couple a days ago I was having 21A installed which I ended up rooting it in order to try some custom roms. I have tried a couple of them but at the end I was having some troubles with my wifi connection so I decided to revert back to 21A or just install another once using the kdz update method.
It was while upgrading to 21D that I got a connection fault and I had to detach and attach the phone. First I though it would be a cable though I changed it and I started all over with the provided cable from LG but always with the same results. As a result the phone didn't power up. I founded later that it powers up only when the wall charger is attached.
After many tries and after reading how to solve this issue I gave it a try trough flashtool with a bin file of 20E I downloaded here in the forum. I tried several times but after 95 seconds the upgrade just fail, well it never really got further. I also tried to flash a GB baseband and I remember once it got up untill 75 seconds of progress and the I got and ERROR. I remember the same happened when the first leaked GB rom came out and you had to flash the baseband separately using these method.
I can't get the phone into recovery mode. I ran out of button combination don't work. I read that some other people were having the same issue and they haven't found a fix yet.
Sorry for the large story but I wanted to be clear with it.
Can someone point me out how to solve this or just come with some ideas.
I really thank you in advance
Lucio

Have you tried this method?
http://forum.xda-developers.com/showthread.php?t=1186460
It worked for me for about 3 different types of bricking, even though it's very tricky and frustrating to get it to enter emergency mode correctly. However, when it does, it feels like a better way to flash a rom in my opinion. I prefer this method when installing a new rom.

Using V20E in mine right now.
Works just fine.
download this
http://forum.xda-developers.com/attachment.php?attachmentid=887870&d=1328537753
if your phone doesnt start put it in download mode like Trekfan422991 does in here
and then just watch this video i have uploaded the procedure here

xbsall said:
Using V20E in mine right now.
Works just fine.
download this
http://forum.xda-developers.com/attachment.php?attachmentid=887870&d=1328537753
if your phone doesnt start put it in download mode like Trekfan422991 does in here
and then just watch this video i have uploaded the procedure here
Click to expand...
Click to collapse
HI XBALL,
Thanks for the links man. I was using old driver and that was causing the constantly connection failure. I download the new USB driver trough the LG Updater app ( Recovery Phone) and installed them. I disabled the LG Android USB moden and started the upgrade procedure with a full success.
I've crazy for about three days. Now time for a bier.
Thanks

[Q] Bizarre Sound Issue with New Phone??

Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!

Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..

lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...

sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable

vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.

sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.

econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.

Boot into recovery and factory reset from there. That should clear up the boot loop issue.

theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:

A black window box come out after flashing my SGS3 GT-I9300

After flashing my SGS3 GT-I9300 with a few custom rom, now I'm using Smart Phone Revolution 2.5. Suddenly this box came out and won't dissapear even after a few restarts. But whenever I open any app, it disappears and when I close that app, it appears again. I really need help. I've tried flashing with official stock 4.1.2 firmware, any other custom but it's still there. The internet and call function is working as usual, only this box is the problem. Help me guys!
View attachment 2431463
p/s: I'm a noob.

Azmil2307 said:
After flashing my SGS3 GT-I9300 with a few custom rom, now I'm using Smart Phone Revolution 2.5. Suddenly this box came out and won't dissapear even after a few restarts. But whenever I open any app, it disappears and when I close that app, it appears again. I really need help. I've tried flashing with official stock 4.1.2 firmware, any other custom but it's still there. The internet and call function is working as usual, only this box is the problem. Help me guys!
View attachment 2431463
p/s: I'm a noob.
Click to expand...
Click to collapse
IDK it looks as if your phone was in some kind of "servicing mode", or something. Weird stuff I've never seen, as I'm quite a noob just like you. Still I've never been in any kind of pain to flash my phone, and outside of ROM-related glitches, never had any problem.
What I know for sure you should do is to give folks here more details about :
How you first rooted it
What recovery you're using
The exact procedure you've followed to flash Smart Phone Revolution
The exact procedure you've followed to try and resolve the problem.
Did you try to unroot the phone completely, or just flashed stock firmware after factory wipe?
Any other thing or incident you think could be related?
Then sit tight, and wait until someone with experience stops by to help. Good luck!