[Q] CyanogenMod messed up my Infuse?? - Samsung Infuse 4G

So I was curious about the CyanogenMod, and wanted it for my Infuse 4G. I downloaded the zip file and stored it onto my phone. I went into recovery mode (power button + volume down and up) and unzipped the file from there. It worked great for awhile, but this is the second time this has happened....It will randomly turn of, and seem to reboot when "Samsung" appears on the screen. It the goes to the next screen where "Cyanogen(mod)" appears, then it just loops and does the same thing repeatedly. I have no idea why it's doing this, but I need help!!!!! What can I do???

A little more detail may come in handy. Exactly which CyanogenMod ROM did you flash? What was the full procedure you followed? Also, why would you unzip the file when in recovery mode? ROMs aren't meant to be unzipped, they're flashed while in .zip format. I'd recommend reverting back to stock, with Heimdall, and starting over again. This time, don't unzip anything.
---------- Post added at 03:22 PM ---------- Previous post was at 03:17 PM ----------
If you want to go back to stock, all the downloads and instructions you need are in the first 2 posts of this thread:
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3

A few things could've caused this...over clocking (doubt it...our oc is pretty stable) under volting (very likely if he put it too low) and under clocking (also likely if it was put to low) or just bad luck
For a fix I suggest back to stock with any heimdall or Odin package
Sent from my HTC PH39100 using Tapatalk 2

OP, there is more than enough info around on just the Q/A thread on solving boot loops and lost recovery.
Spend a few hrs and through the Q/A sections to get your answer. It's all there...
gl
edit: imho, CM in itself doesn't messes with anyone's phone. It is simply an optional firmware created by many talented individuals and their countless hours of hard work. It one wants to use it, there is a mandatory due diligence on the end users part. Search and read before you ask. The OP's title is also misleading. The simple answer to the op's title is "NO"

Thread cleaned, I suggest some of you to relax and help out else, don't post

datrickett7 said:
So I was curious about the CyanogenMod, and wanted it for my Infuse 4G. I downloaded the zip file and stored it onto my phone. I went into recovery mode (power button + volume down and up) and unzipped the file from there. It worked great for awhile, but this is the second time this has happened....It will randomly turn of, and seem to reboot when "Samsung" appears on the screen. It the goes to the next screen where "Cyanogen(mod)" appears, then it just loops and does the same thing repeatedly. I have no idea why it's doing this, but I need help!!!!! What can I do???
Click to expand...
Click to collapse
Make sure you didn't dirty flash it and you wiped cache and delvik and did a restore just follow all the instructions. Also another thing to do is check the thread and see if theres anyone with a similar problem.

mg2195 said:
A few things could've caused this...over clocking (doubt it...our oc is pretty stable) under volting (very likely if he put it too low) and under clocking (also likely if it was put to low) or just bad luck
For a fix I suggest back to stock with any heimdall or Odin package
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the help, but I can't do that. I can't enter recovery mode at all. It makes it to the "cyanomod" screen, then loops from there. It will turn on to the Samsung screen, cyanogenmod screen, then turn off and back on again.

I'd say boot into download mode and flash stock using Odin and try to reflash cm again but make sure your following the instructions step by step
Sent from my Nexus S

That almost sounds like a stuck power button. Does it start IMMEDIATELY running if you remove the battery and reinstall it after 30 seconds?

I'm having the exact same problem. Is there any sure way of fixing this?

xavsteez said:
I'm having the exact same problem. Is there any sure way of fixing this?
Click to expand...
Click to collapse
I think you need to replace the power button hardware send it to http://mobiletechvideos.mybigcommerce.com/ their services is A+ and fast shipping, they fix my Infuse with same problem like that and they even restore my vibrant to life that was totally brick that doesn't turn on at all.

Related

[Q] G2x stuck at LG logo/cannot access recovery

Hey all
Before anyone mentions that i should be searching around more, i would like to say that i've been on multiple threads and they all state the same thing (use NVflash to flash CWM and then boot into CWM but the solution did not work for me past flashing CWM and then trying to access recovery after) and i wasn't able to find one that had a similar problem as mine.
I have CWM flashed through NVflash and was running CM7.1 RC1. I took a screenshot with the 'shootme' app and proceeded to look at the gallery to make sure it came out okay. The gallery crashed and i was sent to the home screen. I swiped to a different homescreen when my phone froze halfway through the transition to the next screen. No combination of buttons/long presses were able to get me out of it so i went ahead and did a battery pull. So my dilemma is that now i'm stuck at the LG boot logo with no blue status bar under it. It freezes there and will not do anything every time i boot up. volume down+power does not give me access to recovery nor does any other button combo get me past the LG boot logo.
Are there any other methods i might be able to use like ADB or what not to get myself out of this situation? or at least into recovery? Any comments or suggestions would be greatly appreciated as i've been searching for hours with little help and my eyes are starting to get strained.
hmmm.. I know it's a simple question, but I gotta ask.. are you holding the pwr and volume down button long enough? you have to keep holding it even after you see the LG screen.. Keep holding until you see the 2nd screen?
If so.. do the nvflash again? Edit: Not sure if I would do this without getting further guidance tho..
schmit said:
hmmm.. I know it's a simple question, but I gotta ask.. are you holding the pwr and volume down button long enough? you have to keep holding it even after you see the LG screen.. Keep holding until you see the 2nd screen?
Click to expand...
Click to collapse
This. I remember when I boot looped my phone I had the problem of letting go of the volume key too early, you need to hold down volume and power from a totally powered off phone until recovery actually starts and you see the green "android" logo of CWM.
Try re-flashing CWM, NVFlash CAN fail. There is literally nothing you can do within the OS that will prevent recovery from working. Either you did something wrong somewhere along the recovery process or you discovered an entirely new problem with the phone. I'm going to hazard a guess and say it's the former.
Thanks for the response guys. I wish that it was the case of not holding the buttons long enough. I have tried numerous times with the buttons held down for a long period of time. I even held the combo down for almost 5 minutes a few times.
Every time i try to boot up, it won't go past the LG boot screen so i would pull the battery out and go through flashing CWM through NVflash again. I'm sure I'm not missing anything because everything goes through and gets sent to the phone successfully.
I did happen to run into a thread that was closely similar to mine but his method was to just keep reflashing CWM and the stock recovery back and forth every time it failed until it turned on. I might have to try that if i cannot figure out this problem out soon. Not being able to use this phone is killing me! heh.
I just joined your club. Wow this sucks.
So apparently this is a whole new problem that's been found? Every other help thread seems to point to using NVflash or remaking the partitions due to a bad flash using an O2x based file instead of G2x.
But none of those solutions come close to doing anything. There has been some people with the same problem as me but aren't proactive at all enough to get someone's attention, so i'm guessing this problem is getting pushed to the side with people just going about getting their phones replaces/buying new ones.
I did happen to run into a thread on paulobrien/modaco's forum that had people using NVflash to get out of any sticky situation like this. It just reverts everything back to the stock factory settings but with root. We cannot use this though because he hasn't built it to be compatible with our LGP999's because everything was built for their UK LGP990's. Maybe that's a start to getting this solution fixed?
I hate to say this, bit you might have to call t mobile and get a replacement. Flash back to stock recovery and they won't know you messed with anything.
Sent from my Nexus 5g using XDA Ultimate App
Don't send back....you'll get same defacement a battery pull go into nvflah and go back stock then flash nv flash fix pArtitions
As I have mentioned before, NVflash does NOT give me access to my recovery let alone solve anything else. NVflash DOES work and does sucessfully send both CWM and the stock recovery but when I try to boot into either of them, let alone just power on normally, it simply DOES NOT go past the LG boot screen. it just hangs there doing nothing at all until I pull the battery out and do the same process over until it just hangs again.
while it is on/stuck at the LG screen, my computer does not recognize it so i cannot even try and run ADB commands. It does however, recognize it when I plug it in using the volume buttons held down when I use NVflash but there's nothing else I can do besides use NVflash obviously.
Jduhb said:
As I have mentioned before, NVflash does NOT give me access to my recovery let alone solve anything else. NVflash DOES work and does sucessfully send both CWM and the stock recovery but when I try to boot into either of them, let alone just power on normally, it simply DOES NOT go past the LG boot screen. it just hangs there doing nothing at all until I pull the battery out and do the same process over until it just hangs again.
while it is on/stuck at the LG screen, my computer does not recognize it so i cannot even try and run ADB commands. It does however, recognize it when I plug it in using the volume buttons held down when I use NVflash but there's nothing else I can do besides use NVflash obviously.
Click to expand...
Click to collapse
Did you ever find a solution to this issue? Because my phone is doing this...
I attempted to restore my phone back to the wrong backup that was from a galaxy sII (2.3.4 i think); needless to say, the restore failed. I then restarted my phone from CWM and it gets stuck at LG screen.
I have tried to NVflash back to stock; nothing. same thing reflashing back to CWM.
ideas?
have you tried this link out yet?
http://forum.xda-developers.com/showthread.php?t=1180331
same problem..... anybody find something to fix this yet?
From what I heard is that you need to remove the battery, then boot into recovery or something.
Sent from my G2X
Use smartflash for the p990 but only use the p999 ap.bin file which will put the rom and kernel back to stock p999.
Rom for recovery always fixes any soft brick back to stock 2.3.3 OTA. It's saved my phone multiple times from stuck on S/W screen to being stuck on lg logo or even the dreaded can't mount sdcard-cache errors in cwm.
Sent from my LG-P999 using xda premium
I used the following method when Clockworkmod became corrupted and was unable to mount my sd card. I had just wiped everything on my phone intending to install a new rom when the issue happened. I could not even get to the S/W upgrade screen. It saved my phone. Hope it works for you.
http://forum.xda-developers.com/showthread.php?p=17258229
jcbofkc said:
I used the following method when Clockworkmod became corrupted and was unable to mount my sd card. I had just wiped everything on my phone intending to install a new rom when the issue happened. I could not even get to the S/W upgrade screen. It saved my phone. Hope it works for you.
http://forum.xda-developers.com/showthread.php?p=17258229
Click to expand...
Click to collapse
omg thank you so much! It worked! Not only that but i was stuck on frodo 2.2.2 before which is why i was messing with my phone in the first place and now its on gingerbread. Awesome! thank you!!!!
sabotage99 said:
omg thank you so much! It worked! Not only that but i was stuck on frodo 2.2.2 before which is why i was messing with my phone in the first place and now its on gingerbread. Awesome! thank you!!!!
Click to expand...
Click to collapse
Glad for you that it worked.
Kwes1020 pointed me in the right direction last week. Be sure to give a thanks to ILUHA_89 who came up with the fix.
Amazing how people are soo lost without providing them link after link to other threads. They are soo lazy and can't follow simple directions, each time i get a new phone i go to that section on xda and soak up all the information as it usually is already there. It's just funny is all i guess.
d12unk13astard said:
Amazing how people are soo lost without providing them link after link to other threads. They are soo lazy and can't follow simple directions, each time i get a new phone i go to that section on xda and soak up all the information as it usually is already there. It's just funny is all i guess.
Click to expand...
Click to collapse
It's really not that big a deal. I was brand new to android once and asked all sorts of things.
I, like you, happen to read everything I can get my hands on. Some struggle going through all the info. I was here the day the forum opened, so I kind of remember where everything is.
Some are lazy and others just have no idea what the heck is going on and are intimidated by certain processes. I would rather help someone instead of listening to them ***** about their broken phone.

[Q] Sidekick 4G Bricked!!!!!!! odin dosent work

tried installing glorious overdose but I tried to wipe data, and it stayed there for about 10min so i pulled out the battery. i tried a second time but without wiping data (i didnt know WTH i was thinking) so it rebooted and was stuck at boot screen saying create new partition and system not avaliable (sumthing like that) so i decided to try odin so i can go back to stock firmware and it finished and now it stays at the bootscreen blinking i tried recovery im stuck.
before you odin, reinstall the phones drivers on your pc. connect the phone to the pc without the battery, hold the volume down button and the trackpad and reinsert the battery. when you odin, make sure only auto reboot is checked, and put the pit file in the pit slot and the tar file in the pda slot. if you use kies to update firmware, reinstall drivers again before updating.
You may need to check "Re-Partition" in Odin.
shouldnt need to repart, in fact it may be a bad idea. every time i odined and accidentally had repart checked, it screwed something up. most recently the stock messaging app didnt work after odin. i have since switched to go sms, but still made sure i had a clean firmware install. i would try odin without repartitioning first and see how that goes. if something is wrong, you can always odin again. the first time i tried to flash a rom i bricked because i flashed cwm through rom manager. the thread where i found the odin file said make sure only auto reboot is checked. besides, if the rom didnt flash correctly, then it didnt convert any partitions anyway.
ok i had the same problem for the first time i tried to install a custom rom, theres a way that you can fix it with out odin. follow this steps... i promise it will work.
1)boot into the red cwm voodoo lagfix recovery
2)wipe data/factory reset
3)wipe cache partion
4)after all the steps above are completed, go to apply sdcard:update.zip
the its going to take you to the regular cwm once there follow this steps...
1)install the custom you want to install, but make sure that it doesnt need special mounts and unmounts, so follow the instruction flash the rom and it should fix it
Heimdall worked perfectly when I bricked my phone.
Thank you!! ^ I was boutta cry when it was Rebooting .... Yea I guess I messed something up with odin
WolfV2 said:
Heimdall worked perfectly when I bricked my phone.
Click to expand...
Click to collapse
I tried the method above but ater reboot it stays on the T-Mobile Sidekick 4G boot screen and does nothing else. I'm hesitant and Flash Bootloader but what do you all think?
flashing bootloader in that package doesn't break it.
creid2352 said:
I tried the method above but ater reboot it stays on the T-Mobile Sidekick 4G boot screen and does nothing else. I'm hesitant and Flash Bootloader but what do you all think?
Click to expand...
Click to collapse
My advice is do whatever it takes, and besides, don't worry about breaking something that's already broken, if you know what I mean...
johnwazhere said:
Thank you!! ^ I was boutta cry when it was Rebooting .... Yea I guess I messed something up with odin
Click to expand...
Click to collapse
No problem, glad I could help
creid2352 said:
I tried the method above but ater reboot it stays on the T-Mobile Sidekick 4G boot screen and does nothing else. I'm hesitant and Flash Bootloader but what do you all think?
Click to expand...
Click to collapse
This is my current problem as well, except I have tried checking flash bootloader and have also tried Odin, but all to no avail. Can anyone help me? This is my situation:
I've had my sidekick for about a year now and have gone through the typical problems of a sidekick user. Then yesterday, my sidekick's alarm woke me as normal, but I was unable to turn it off because my touch screen wasn't working. So i battery pulled, restarted, and noticed that the screen stayed on the "T-Mobile Sidekick 4g SAMSUNG" start up screen and did not budge. I tried battery draining, more battery pulling, and nothing worked. So i did a lot of research on here and other websites and decided to use Odin. After initial problems of a newbie, I eventually figured it out and got it to RESET and PASS, but the subsequent reboot only caused my phone to be stuck in the same Sidekick start up screen it has been getting stuck in. Similarly, after many tries, Heimdall has done the same for me. Sorry if that was a long read (also, I hope its cool that i bumped this thread with my own problems), but is there anything else i can do? I'd really like to use my phone again..
I've been working for hours trying to figure out how to fix it, and I just don't know. The end result is always just the freezing at the t-mobile start up screen..Also, since i forgot to mention, I can only get into download mode with the volume down+trackball method because otherwise it would just go to the regular start up screen and freeze. I don't know if that means anything, but yeah.
Have you used heimdall yet? I bricked my SK4G the other day when flashing a rom and heimdall put it back to stock within 5 minutes of me bricking it.
Thank you for replying. Unfortunately yes, I did. With flash bootloader unchecked and checked. It says it disconnects after everything is done and it restarts, only to become frozen at the start screen again =/. I don't know if there is some silly detail that im missing that makes the flash rather than just restart, but all i can manage to make it do is restart.
Sigh. Guess im going phone shopping.
How did u get the phone in dl. Mode
Sent from my SGH-T839 using XDA
I had to plug the phone into my computer without the battery, hold volume and the track ball, then pop the battery in. Any other attempts would simply start it up/freeze it.
Ok did u have heimdall started first?
Sent from my SGH-T839 using XDA
And what rom did u last have?
Sent from my SGH-T839 using XDA
I'm not entirely sure if I had it started first, so I'll try it that way now. And the last ROM that I had? Honestly not really sure what that means =p, but i've never flashed one and I had the most recent sidekick update installed (though it is possible that I had done a factory reset at some point to fix an error).
---------- Post added at 01:04 PM ---------- Previous post was at 12:45 PM ----------
Just tried it. Without flashing bootloaders, it finishes and restarts to my frozen start up screen as normal. However, when i flash bootloaders, it gets to "uploading pit", but the upload fails and it reboots my phone. But this time, it reboots into download mode. A welcome change from my start up screen. Maybe there's hope.

ROM: Stock Rooted and Deodexed Android 2.3.6 UVLB7

This is a full stock ROM. Everything works.
Features:
Deodexed
Zipaligned
Rooted
Busybox installed
T-Mobile bloatwares removed
Carrier IQ removed
Credits:
erikmm & fbis251 (updater-script)
Samsung (stock ROM)
ChainsDD (superuser)
dsixda (Android Kitchen)
Installation:
ClockworkMod Recovery
Wipe Data/Factory Reset
Wipe Cache
Wipe Dalvik Cache
Install ROM
Reboot
Battery calibration:
Turn off phone
Fully charged
ClockworkMod Recovery
Wipe battery stat
Reboot
Discharge and recharge
DOWNLOAD ROM
Thanks for asking perms to use the script....
Also, did u remove carrier IQ from frameworks?
sent from my batcave
erikmm said:
Thanks for asking perms to use the script....
Also, did u remove carrier IQ from frameworks?
sent from my batcave
Click to expand...
Click to collapse
Yes. I did. See my screenshot.
I still have to learn a lot from you, erikmm. Thanks.
tthaz777 said:
Yes. I did. See my screenshot.
I still have to learn a lot from you, erikmm. Thanks.
Click to expand...
Click to collapse
Well by erasing the apk it can be shutdown as well so u recompiled without carrieriq? Awesome bro. Lol
And I was being sarcastic about rhe script lol just next time u gotta ask first bro
sent from my batcave
looks like because of u 2 and the many others on this, this fone will be a hot topic for later roms coming out... any updates erik?
badboy68 said:
looks like because of u 2 and the many others on this, this fone will be a hot topic for later roms coming out... any updates erik?
Click to expand...
Click to collapse
Not to kang on OPs thread but nah no updates yet since I dont have tthe phone but ill try some stuff this weekend
sent from my batcave
erikmm said:
Not to kang on OPs thread but nah no updates yet since I dont have tthe phone but ill try some stuff this weekend
sent from my batcave
Click to expand...
Click to collapse
Erikmm, can you please port Xperia S Music Player (Walkman) to our Galaxy S Blaze 4G? It would be very interesting.
I found the thread below
http://forum.xda-developers.com/showthread.php?t=1646138
tthaz777 said:
Erikmm, can you please port Xperia S Music Player (Walkman) to our Galaxy S Blaze 4G? It would be very interesting.
I found the thread below
http://forum.xda-developers.com/showthread.php?t=1646138
Click to expand...
Click to collapse
Lol I'm not used to going off topic on dev thread but ur OP so...yea ill give it a shot just again hard to do it blindly
sent from my batcave
erikmm said:
Lol I'm not used to going off topic on dev thread but ur OP so...yea ill give it a shot just again hard to do it blindly
sent from my batcave
Click to expand...
Click to collapse
I will be tester. Don't worry. Thanks.
tthaz777 said:
I will be tester. Don't worry. Thanks.
Click to expand...
Click to collapse
Lol well flyers00 is my tester that's not the issue...the issue is the difficulty lol
sent from my batcave
Loaded this up last night.....not one issue to report. I happen to like touch wiz (as well as everything else) I hope you keep this ROM going in a stock like direction. Maybe if your plan is to change launchers etc you could branch off. Anyway....well done I love my phone!
sorry but have to ask. how did you get cwm on phone? I cant get download screen. figured it was the 2.3.6 UVLB7 build causing it. just got phone 5 days ago. had G2x piece before.
Can you give me more details in regards to your question? Have you lost the ability to get into recovery? I had the G2X as well....CWM is flashed pretty much the same way as the LG (except without the NVIDIA tool)
Things are not far enough along to have a reboot option in the ROMS yet, try power tool or something like it, works fine for me.
---------- Post added at 03:44 AM ---------- Previous post was at 03:33 AM ----------
sk622 said:
Loaded this up last night.....not one issue to report. I happen to like touch wiz (as well as everything else) I hope you keep this ROM going in a stock like direction. Maybe if your plan is to change launchers etc you could branch off. Anyway....well done I love my phone!
Click to expand...
Click to collapse
I wanted to amend this after ongoing usage and say things are still running solid. I did notice a lower quality audio performance as compared to dknight. Not a major concern this early in the game by any means.
The audio capabilities on Android was and is the big reason I am here and not on I-tunes so i'm particularly sensitive to that area. I run completely uncompressed FLAC's (1411 kb bit rate) and have a 64gb SD card on my phone loaded to the hilt.
My work phone is a GNEX (with Black Ice and Axiom Morphr) streaming through Google Play so I have back up ...lol
robertguero said:
sorry but have to ask. how did you get cwm on phone? I cant get download screen. figured it was the 2.3.6 UVLB7 build causing it. just got phone 5 days ago. had G2x piece before.
Click to expand...
Click to collapse
You must install ClockworkMod Recovery before flashing a ROM. I'm currently using this ROM. I can still access ClockworkMod Recovery by holding volume up, volume down, and power button at the same time, then release after Samsung logo disappears. Don't flash ClockworkMod Recovery in ROM Manager. See the thread below to know how to flash it.
http://forum.xda-developers.com/showthread.php?t=1591622
http://forum.xda-developers.com/showpost.php?p=27360727&postcount=57
Sent from my SGH-T769 using xda premium
I have done all this to my G2x piece of crap so it not new to me. On my new phone the Samsung Galaxy S Blaze 4G SGH-T769. if I hold down the 3 buttons, vol up/dn and pwr, remove battery all that stuff I DO NOT get the "WaRNING" or download screen. It will only give me recovery screen after the Galaxy splash screen. I have tried every method available. I have tried every unlock I can find, oneclick and unlock and even Odin but it needs the download screen. It will not see phone till it totally boots. Was hoping you had something to install thru recovery screen to get to download screen. Have not tried ADB yet but have not read everything on how it works or what to do. Really have not found much info on ADB way to unlock.
So since everyone here is a lot more advanced than I am figured I would ask. Seems only a handfull of Blaze devices will not go into download mode.
1. Turn phone off and plug to pc
2.proceed to hold both volume and power button simultaneosly. Keep holding down until phone vibrates then let go of power button and continue holding volume buttons.
3. Let go of buttons as soon as u get to the next screen then press vol up to proceed to download mode.voila
P.s. I have the same baseband.
That should work for you, works for me all the time
If i helped in anyway hit the thank button
i just P.M you with a video on how to do it
Sent from the Darkside
no joy. this sux. tried every combo. exactly what you said. also tried removing battery... longer hold... shorter hold.. no sim or sd...throwing against wall while holding buttons. nothing works. all it does is continue to boot. :crying:
can there be a script or something written to do update from recover screen to make it boot to download mode? something..... or am I just stuck with jtag or adapter or whatever you call it.
What will adb do for me? can I root from it? will it help? I have not found instruct on what to do once in adb. found instruct on how to get to work but didnt see anything more. then again I did not fully look into it.:cyclops:
Hey but honestly THANKS FOR ALL HELP!!!. I did not want to bring to this thread but figured yall might know something special. Will understand if you tell me to post elsewhere.
2.3.6
base T769UVLB7
Kernel 2.6.35.11
GINGERBREAD.UVLB7
robertguero said:
no joy. this sux. tried every combo. exactly what you said. also tried removing battery... longer hold... shorter hold.. no sim or sd...throwing against wall while holding buttons. nothing works. all it does is continue to boot. :crying:
can there be a script or something written to do update from recover screen to make it boot to download mode? something..... or am I just stuck with jtag or adapter or whatever you call it.
What will adb do for me? can I root from it? will it help? I have not found instruct on what to do once in adb. found instruct on how to get to work but didnt see anything more. then again I did not fully look into it.:cyclops:
Hey but honestly THANKS FOR ALL HELP!!!. I did not want to bring to this thread but figured yall might know something special. Will understand if you tell me to post elsewhere.
Click to expand...
Click to collapse
Please follow these instructions and try again:
+ Download and install USB Driver for T-Mobile SGH-t769 Samsung Galaxy S Blaze 4G on your PC http://org.downloadcenter.samsung.com/downloadfile/ContentsFile.aspx?CDSite=US&CttFileID=5002142&CDCttType=SW&ModelType=null&ModelName=null&VPath=SW/201204/20120424041113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe
+ Download Odin 1.85 http://k0nane.info/rom/odin-185.zip
+ Download PIT http://shabbypenguin.com/k0/blaze.pit
+ Download Clockworkmod recovery TAR http://www.shabbypenguin.com/OUDstuff/Blaze4G/Clockworkmod-Blaze-4G.tar
+ Extract Odin-185.zip
+ Run Odin 1.85.exe and make sure that you check "auto-reboot", and uncheck all other options.
+ Click PDA and select the TAR you downloaded. Click PIT and select the PIT your downloaded. Uncheck repartition.
+ Connect your device to your PC
+ Remove the battery while holding down volume up and volume down buttons
+ Reinsert the battery and press volume up, volume down, and power button at the same time until your device has entered download mode.
Good luck
Sorry. Have tried and tried. Total time trying this exact method and others over the past 2 days about 4 hours. Will not go into download mode. Have all of the above installed and ready to go on the computer. Can get odin to connect if phone is totally booted up in working mode but that does nothing for odin. Same with superoneclick and unlock root. The last two are not configed for 2.3.6 on blaze 4g or something so they will not complete the root/unlock.
If I remove battery with usb plugged in it will vib about every 3 seconds. Once battery is put in it stops vibing but once you hold button it will vib one more time then "samsung" comes across screen goes away then blaze spash on screen and it continues to boot. Never see "warning" screen or download screen.
I have no issues getting into phone from pc or phone connecting to pc. Just no download mode.
As I said i did not want to take over your thread with this and I feel I have taken up to much of our time as it is. Thank you for your help. Hope someone has solution soon. Thanks again.
robertguero said:
If I remove battery with usb plugged in it will vib about every 3 seconds. Once battery is put in it stops vibing but once you hold button it will vib one more time then "samsung" comes across screen goes away then blaze spash on screen and it continues to boot.
Click to expand...
Click to collapse
Just tryin to cover all the bases here, but you should be holding both the volumes and the power button when you put the battery back in. Then be ready to release all to quick vol up when the dl screen shows up. You should also be connected via usb.
Hope this helps.

[Q] Stuck in bootloop on LiquidSmooth

A few details before I start
I am on Galaxy S3 i535 from Verizon, was running CleanROM 5.6 for a few hours after coming from Codename Android that I was using for a few days(I've been going crazy with trying roms lately.)
I flashed LiquidSmooth 2.0 with CWM (never have used odin)
On all of these flashes before i did so I wiped system/factory reset, wiped cache and dalvik cache, and formatted system, cache, and data.
I had just finished flashing Liquid Smooth about an hour ago and was installing a few things with titanium back up. everything up until this point was going fine, got all my apps instaIlled and ready to go, and I head into the settings and try to turn on a few things and edit some settings in the Liquidsmooth settings.
Now my phone is stuck in a bootloop and I'm not sure what to do. I have tried power/volume down, power/home/volume up, power/home/volume down, and nothing will get it to reboot. I dont know whether or not it is safe to take out the battery and start from there, so if that is the route I should take, please let me know.
I have no experience with odin, but I can most definitely look that up so I wont need help there. Just some help on whether or not I should take out the battery or do something else. I just don't want to brick it in any way if that is avoidable:fingers-crossed :fingers-crossed:
Thanks to whoever can help me!
Edit:
I used the search a little better this time and saw people say pull battery on similar cases, and I did that, and I'm still stuck in bootloop. (It seems like in most of the threads I found pulling the battery was a given so people didnt mention it, but I needed to know for sure.) So I am still in the bootloop and am just going to boot into download mode and go from there.
Alright I was able to odin to stock, and now im back to square one.
Not sure how to delete threads :S
Toastiesyay said:
A few details before I start
I am on Galaxy S3 i535 from Verizon, was running CleanROM 5.6 for a few hours after coming from Codename Android that I was using for a few days(I've been going crazy with trying roms lately.)
I flashed LiquidSmooth 2.0 with CWM (never have used odin)
On all of these flashes before i did so I wiped system/factory reset, wiped cache and dalvik cache, and formatted system, cache, and data.
I had just finished flashing Liquid Smooth about an hour ago and was installing a few things with titanium back up. everything up until this point was going fine, got all my apps instaIlled and ready to go, and I head into the settings and try to turn on a few things and edit some settings in the Liquidsmooth settings.
Now my phone is stuck in a bootloop and I'm not sure what to do. I have tried power/volume down, power/home/volume up, power/home/volume down, and nothing will get it to reboot. I dont know whether or not it is safe to take out the battery and start from there, so if that is the route I should take, please let me know.
I have no experience with odin, but I can most definitely look that up so I wont need help there. Just some help on whether or not I should take out the battery or do something else. I just don't want to brick it in any way if that is avoidable:fingers-crossed :fingers-crossed:
Thanks to whoever can help me!
Edit:
I used the search a little better this time and saw people say pull battery on similar cases, and I did that, and I'm still stuck in bootloop. (It seems like in most of the threads I found pulling the battery was a given so people didnt mention it, but I needed to know for sure.) So I am still in the bootloop and am just going to boot into download mode and go from there.
Alright I was able to odin to stock, and now im back to square one.
Not sure how to delete threads :S
Click to expand...
Click to collapse
ok i only read the first few lines but manually boot into cwm by either vol up or down and multi function and power at the same time and upload a rom like synergy i know it works and u should be good
WOW!
This I cant believe!
Toastiesyay said:
I have tried power/volume down, power/home/volume up, power/home/volume down, and nothing will get it to reboot.
Click to expand...
Click to collapse
wingtytn said:
ok i only read the first few lines but manually boot into cwm by either vol up or down and multi function and power at the same time and upload a rom like synergy i know it works and u should be good
Click to expand...
Click to collapse
Yeah, we noticed you only read the first few lines. :what:
If you are gonna try to help at least read the whole OP.
And to manually boot recovery its: Volume up+home+power.
Not
wingtytn said:
EITHER vol up or down and multi function and power at the same time
Click to expand...
Click to collapse
Sent from my SPH-L710 using xda premium
OP you are missing the point here. You have to take the battery out and put it back in before going to recovery. Once you have done that try vol-up/home/ power at the same time. Once samsung logog appears look at the top left if you see words release. it will boot to recovery. You can take it from there.

Ugh... Screwed up my phone using the Wallet Installer. Someone Help!

Sorry for posting this.
I was trying to get Google Wallet on my phone, and of course it backfired. I noticed in my "About Phone" it said "Galaxy Nexus." I remember trying to restore my build.prop thru the app before, but I tried it again, this time clicking on "Verizon" and SIII, and I pressed build.prop and my phone has been endlessly trying to bootloop. I haven't been able to get past the "Samsung Galaxy SIII" menu with Cid on it.
My biggest problem is I'm running a Mac. I know theres a whole Odin process, I haven't even looked at, unfortunately. Typically, this phone doesn't read Macs well.
I backed up multiple ROMs thru recovery. I tried getting to the boot menu, pressing vol up+power and vol down+ power to no avail. I know there are countless threads on this, but if anyone could do me the kindness to show me the right thread to read and what I should look at, I would GREATLY appreciate it. I've been flashing forever and this is the first time this has happened to me.
Thank you.
UPDATE!:
I'd delete this post entirely, but I don't see an option where I can. Thought I'd post how I figured it out at least so when someone else does this, they know what to do.
I figured out how to boot into recovery from power off. You press and hold VOLUME DOWN + HOME. Then you press power and let go when the S-Screen comes on.
I've heard all GS3 flashers soft brick at some point, and I'm dreading the day I have to use Odin...
for the future, as far as i understand theres almost no downside to keeping the build prop edited to nexus.
I had it that way for months at a time with no noticeable differences.
npro1464 said:
Sorry for posting this.
I was trying to get Google Wallet on my phone, and of course it backfired. I noticed in my "About Phone" it said "Galaxy Nexus." I remember trying to restore my build.prop thru the app before, but I tried it again, this time clicking on "Verizon" and SIII, and I pressed build.prop and my phone has been endlessly trying to bootloop. I haven't been able to get past the "Samsung Galaxy SIII" menu with Cid on it.
My biggest problem is I'm running a Mac. I know theres a whole Odin process, I haven't even looked at, unfortunately. Typically, this phone doesn't read Macs well.
I backed up multiple ROMs thru recovery. I tried getting to the boot menu, pressing vol up+power and vol down+ power to no avail. I know there are countless threads on this, but if anyone could do me the kindness to show me the right thread to read and what I should look at, I would GREATLY appreciate it. I've been flashing forever and this is the first time this has happened to me.
Thank you.
UPDATE!:
I'd delete this post entirely, but I don't see an option where I can. Thought I'd post how I figured it out at least so when someone else does this, they know what to do.
I figured out how to boot into recovery from power off. You press and hold VOLUME DOWN + HOME. Then you press power and let go when the S-Screen comes on.
I've heard all GS3 flashers soft brick at some point, and I'm dreading the day I have to use Odin...
Click to expand...
Click to collapse
I actually had this problem, to fix this issue you can always choose system restore only from advanced restore. It restores your build.Prop and keeps all of your data intact.
Just for future use in case you modify your system files again.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
ddurandSGS3 said:
for the future, as far as i understand theres almost no downside to keeping the build prop edited to nexus.
I had it that way for months at a time with no noticeable differences.
Click to expand...
Click to collapse
The only downside is if you install a recovery via goomanager or rom manager. It will flash the wrong recovery to your phone.
Will this actually brick the phone? Or keep it from booting into recovery?
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I actually had this problem, to fix this issue you can always choose system restore only from advanced restore. It restores your build.Prop and keeps all of your data intact.
Just for future use in case you modify your system files again.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
The only downside is if you install a recovery via goomanager or rom manager. It will flash the wrong recovery to your phone.
Will this actually brick the phone? Or keep it from booting into recovery?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
no clue about that. i had recovery installed before wallet installer was used.

Categories

Resources