Help!!! I forgot to unlock bl - Verizon Samsung Galaxy S III

I just tried to flash Jellywiz for the first time. I forgot to unlock the bootloader prior to flashing the rom. I know.........So Stupid.
Anyway. I've tried the odin trick but my phone just has the yellow triangle with the message that the system software in not authorized by VZE. I can't boot into recovery to restore my backup. Odin doesn't seem to work. I'm trying to follow the instructions http://forum.xda-developers.com/showthread.php?t=1840030 But I'm not getting the "PASS" message.
Please help... I'm freaking out.

Are you booting into download mode before connecting to Odin?

Oh, no I wasn't. I'm now going through the Odin process in Download mode. Thanks for the tip. Hope this works

dbow32 said:
Oh, no I wasn't. I'm now going through the Odin process in Download mode. Thanks for the tip. Hope this works
Click to expand...
Click to collapse
folks...i will say it again, you dont need to use puremotives guide to recover in this situation. just flash a stock rom in odin and be done. there is no need to flash bootchains...use section 6 of my guide, then if that does not work use puremotives guide. not trying to take anything away from pures great writeup, but its intended for devices that are actually soft bricked. i only recomend flashing bootchains if absolutely necessary because if anything fails during the flash, you get a hardbrick....then its jtag time!

droidstyle said:
folks...i will say it again, you dont need to use puremotives guide to recover in this situation. just flash a stock rom in odin and be done. there is no need to flash bootchains...use section 6 of my guide, then if that does not work use puremotives guide. not trying to take anything away from pures great writeup, but its intended for devices that are actually soft bricked. i only recomend flashing bootchains if absolutely necessary because if anything fails during the flash, you get a hardbrick....then its jtag time!
Click to expand...
Click to collapse
Ok, I'll try that. Thanks for every ones help. I'll let you guys know if it works.

I'm up and running. Thank you all so much... especially droidstyle for the tutorial. I tried looking for a "Donate" button on the tutorial but couldn't find one. I'll keep looking and send some cash your way. Again, thank you VERY much.
Dave

dbow32 said:
I'm up and running. Thank you all so much... especially droidstyle for the tutorial. I tried looking for a "Donate" button on the tutorial but couldn't find one. I'll keep looking and send some cash your way. Again, thank you VERY much.
Dave
Click to expand...
Click to collapse
donate link up! i never really thought to put up a link, but actually there have been quite a few folks wanting to make a donations...thx and glad your back up and running!

Droidstyle what are boot chains? I came from sprint and never saw them before and a Google search doesn't give an answer. Could u please shed some light on it for me. Thanks bro
Sent from my SCH-I535 using xda premium

musclehead84 said:
Droidstyle what are boot chains? I came from sprint and never saw them before and a Google search doesn't give an answer. Could u please shed some light on it for me. Thanks bro
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
bootchains are the order of operations for the boot process(aka bootloader). some folks have had thier devices emmc internal memory get corrupted during a cwm session causing the system permissions to read only. since no data can be written on boot, your device is stuck in a bootloop. reflashing the bootchain followed by the stock rom restores the proper boot sequence and read/write permissions allowing the device to boot. the kicker is you want to make sure nothing goes wrong when flashing a bootchain or its brick city. hopefully this makes sense lol

droidstyle said:
bootchains are the order of operations for the boot process(aka bootloader). some folks have had thier devices emmc internal memory get corrupted during a cwm session causing the system permissions to read only. since no data can be written on boot, your device is stuck in a bootloop. reflashing the bootchain followed by the stock rom restores the proper boot sequence and read/write permissions allowing the device to boot. the kicker is you want to make sure nothing goes wrong when flashing a bootchain or its brick city. hopefully this makes sense lol
Click to expand...
Click to collapse
Yes it does. Thank you so much. I have never seen these used before so it was new to me. Thanks again.
Sent from my SCH-I535 using xda premium

I wonder how many times droidsytles howto has saved people, im sure its in the thousands, thanxs droidstyle! I known it saved me a couple times
Sent from my SCH-I535 using xda app-developers app

Related

[Q] Noob needs a little help

Ok so I just got me a New samsung showcase. It came with 2.2 installed build number sch-i500.ee25. Ok so i find out about rooting and all this so i start researching all about it. Here is where i am. I rooted with SuperOneClick. Worked fine. I installed ROM manager to get the clockworkmod but it did not work so I used Odin to install clockworkmod. That worked fine. So at this point I decided i need to backup the stock ROM. I try this using ROM manager but no go. it reboots into clockworkmod and gives me the sd card not mounted stuff. So I read and read and read but i can't seam to find a solution to this problem. I know there other people that have had this problem. I have read through the step by step guides and i really see nothing on this. Anyone have any type of solution.
Running on stock 2.2 rom manager doesnt work. You will need to go into cwm by turning off phone, holding power,vol up and down at same time. after samsung blinks 2nd time let go of buttons and you will boot into recovery.
Thank you. I thought I tried that before but I guess i did something wrong. Worked that time. Now if my memory is correct from reading that will not back up two things. The kernel and something else. How do I back up the kernel? Or am I just not thinking correctly cause I have not had enough sleep.
Samsung Galaxy S with Cellular South
I had to have Kies Mini open and running on my computer to root my phone
First, Welcome!
Second, Download and familiarize yourself with a program called Odin. This phone is hard to brick. From nearly every situation you can flash back to stock with Odin.
Third, Showcase files are not common. Send me a PM and ill give you my email address. I can better help over email.
studdyhalllooser said:
This phone is hard to brick. From nearly every situation you can flash back to stock with Odin.
Click to expand...
Click to collapse
Not true; that's what we call a false sense of security.
add144 said:
Not true; that's what we call a false sense of security.
Click to expand...
Click to collapse
that is true. ive seen phones get restored that have been flashed with roms for other phones and wont even get past the samsung logo. he said nearly, I'm sure you can come up with some weird far out situation but don't try and scare the newbies off this early.
Sent from my MIUI SCH-i500
sageDieu said:
don't try and scare the newbies off this early.
Click to expand...
Click to collapse
What will scare newbies off is when they start flashing crazy **** for another phone in the Phone box in ODIN or something and can't fix it by just ODIN'ing like you guys are suggesting.
add144 said:
What will scare newbies off is when they start flashing crazy **** for another phone in the Phone box in ODIN or something and can't fix it by just ODIN'ing like you guys are suggesting.
Click to expand...
Click to collapse
It's ok he's the only one still here so he'll have to help them.
Sent from my SCH-I500 using XDA App
You say that but the fact that you said it means I'm not the only one.
Ooooohhhh someone's getting technicallllllllll
add144 said:
Ooooohhhh someone's getting technicallllllllll
Click to expand...
Click to collapse
dang right
Sent from my MIUI SCH-i500
Same phone
I have the exact same phone as you. I just rooted my phone for the first time yesterday and I am having trouble installing CWM. Can you explain to me how you used Odin to flash CWM. And after you flash CWM, is it possible to revert back to stock recovery? If so how?

From bricked to fixed.

I was caught in a boot loop and tried to re flash, when in my haste I forgot that Odin will recheck partition when loading .Pit files (pretty lame feature)
Still it was my fault for clicking start in haste.
**phone was partitioned, and would not go into download mode, it was stuck in a screen that said "Firmware update error, please restore in Kies", but it wouldn't connect to kies**
I sent my phone to XDA member Connexion2005
http://forum.xda-developers.com/member.php?u=1602851
I haven't got it in my hands yet, but he just told me it was fixed, I can't wait to get it back and leave it the hell alone (until someone makes CM7 or better work on it)
anyhow, this is out there so if you do what I did (DON'T) there's a solution. Set me back $50 plus shipping to TX from NYC but still, I didn't have to get a whole new phone.
for 50 bucks im sure k0nane would have made an uberfixit tar :/
shabbypenguin said:
for 50 bucks im sure k0nane would have made an uberfixit tar :/
Click to expand...
Click to collapse
Absolutely.
shabbypenguin said:
for 50 bucks im sure k0nane would have made an uberfixit tar :/
Click to expand...
Click to collapse
Please elaborate. Not finding much info on this "uberfixit", but it sounds like it's some method of re-creating the stock filesystem that's flashable in odin?
I was putting this out there, because I'm not the only one that this will happen to.
yea it happens when you repartition, an uberfixit requires a complete dump of the phone and quite a bit of time, but will completely fix what you described
the problem with repartitioning is that it wipes the phone clean and then starts to reinstall everything, problem is neither one of teh tars has the full dump (we do it for the sake of saving actual bricks)
knowing someone who can jtag is great we have had a few epic 4g touches that crashed and burned and were saved via jtag.
shabbypenguin said:
yea it happens when you repartition, an uberfixit requires a complete dump of the phone and quite a bit of time, but will completely fix what you described
the problem with repartitioning is that it wipes the phone clean and then starts to reinstall everything, problem is neither one of teh tars has the full dump (we do it for the sake of saving actual bricks)
knowing someone who can jtag is great we have had a few epic 4g touches that crashed and burned and were saved via jtag.
Click to expand...
Click to collapse
You may not remember, but I did go onto your IRC and spoke with you regarding this issue.
oh sorry, the irc channel we have is for a bunch of devices currently we house blaze 4g, attain 4g, conenct 4g, lucid and optimus m+ owners. so i probably thought you were an attain owner since we have had a good number of attain owners repartition as well :/
shabbypenguin said:
oh sorry, the irc channel we have is for a bunch of devices currently we house blaze 4g, attain 4g, conenct 4g, lucid and optimus m+ owners. so i probably thought you were an attain owner since we have had a good number of attain owners repartition as well :/
Click to expand...
Click to collapse
it's all good, bottom line is I f'd up my device, but now its fixed.
um...yeah...
So i did the exact same thing as you... Been trying to find anyone who can help me out. Is there anyway I can fix it myself? I haven't found a single place in my whole state that can fix the problem. If at all possible, I'd like to avoid sending it out for repair.
So how do I get this uberfixit?
I stupidly re-partitioned using Odin, also: I did not realize that Odin re-checked the check box -even after unchecking- when a new pda file was loaded. My bad. Totally though it was bricked until i was able to flash this stock gingerbread rom, but now kies says that my Blaze S does not qualify for upgrades... Did the re-partitioning do this?
I can no longer get to the recovery screen, although if I restart my blaze while connected to a pc via usb, it does allow the "re-install OS?" page to display, and I can get to recover from there: But absolutely no more access to the recovery "menu" which allows me to wipe cache/restore to factory/etc.
Just Odin cwm back then flash away
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Thanks for the quick reply; I will try that right now: My fingers are crossed.
2vivid said:
Just Odin cwm back then flash away
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
thomassino said:
Thanks for the quick reply; I will try that right now: My fingers are crossed.
Click to expand...
Click to collapse
It's just a soft brick, I have done that at least 10 times.
Will you make this?
k0nane said:
Absolutely.
Click to expand...
Click to collapse
Hi, k0nane I too have bricked my phone due to not unchecking re-partition. Now no matter what I do the phone displays the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. It is frustrating. I will certainly pay you if you make a fix for this that I can flash in odin! I don't care if it wipes my phone completely as I was trying to flash a new rom anyways. Please reply I'm desperate to get this thing working again.
runboyrun said:
Hi, k0nane I too have bricked my phone due to not unchecking re-partition. Now no matter what I do the phone displays the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. It is frustrating. I will certainly pay you if you make a fix for this that I can flash in odin! I don't care if it wipes my phone completely as I was trying to flash a new rom anyways. Please reply I'm desperate to get this thing working again.
Click to expand...
Click to collapse
That's a soft brick.
No need to pay anyone lol just pull the battery and go back to download mode (for Odin) again and revert back to stock. A quick search through 'bricked' type threads would have netted this info :thumbup:
Sent from my SGH-T769 using xda app-developers app

Anybody sitting at home looking to make a few extra dollars?

Verizon GS3 was running the new ota 4.1. Tempted to root and now its Bricked. It will only boot to the yellow triangle telling me to take it back to Verizon. I have tried to use Odin the flash back to stock and it will not for the life of me. If someone is home and willing to call me and walk me through this I will gladly fork over some cash.
Sent from my Nexus 4 using xda app-developers app
Can you describe your process trying to Odin back to stock?
Phush said:
Can you describe your process trying to Odin back to stock?
Click to expand...
Click to collapse
I followed these instructions and got to the PASS screen but phone is still only booting to the yellow triangle telling me to go to Verizon Store.
http://www.theandroidsoul.com/restore-verizon-galaxy-s3-samsung-pre-rooted-rom/
rswheaton said:
I followed these instructions and got to the PASS screen but phone is still only booting to the yellow triangle telling me to go to Verizon Store.
http://www.theandroidsoul.com/restore-verizon-galaxy-s3-samsung-pre-rooted-rom/
Click to expand...
Click to collapse
Currently downloading 1.2GB worth of files and going to try this next...
http://www.youtube.com/watch?v=HyuJ8ii3M4o
Don't stress.. Lol just put the phone back into download mode (home+power up+ power)... redo whatever you wanted in odin.. Don't worry, I think we all have had panic moments...
rswheaton said:
Currently downloading 1.2GB worth of files and going to try this next...
http://www.youtube.com/watch?v=HyuJ8ii3M4o
Click to expand...
Click to collapse
I have been there and done that
Most likely you, while installing a custom recovery or custom ROM, forgot to unlock your boot loader.
For future reference you can unlock he boot loader using this app
https://play.google.com/store/apps/details?id=com.mmmeff.ez.unlock
I hate to say it but I doubt his method is going to fix your phone in this situation.. I have been in this situation and you need to follow the soft brick method here
http://forum.xda-developers.com/showthread.php?t=1840030
90% sure your binary count has been tripped as well and you will need to reset that as well if you ever plan to ship to Verizon.
Binary count number can be viewed in download mode by the way.
Flash count can be reset useing this app.
After you unsoft bricked.
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Let me know how everything goes. Feel free to pm me.
Hit that thanks if I pointed you in the right direction.
sent from that young galaxy on clean ROM!
FIXED!!!!
rswheaton said:
Currently downloading 1.2GB worth of files and going to try this next...
http://www.youtube.com/watch?v=HyuJ8ii3M4o
Click to expand...
Click to collapse
If anyone runs into the same issue follow these instructions! The file is HUGE so it will take a while to download but it worked like a champ!
http://www.youtube.com/watch?v=HyuJ8ii3M4o
rswheaton said:
If anyone runs into the same issue follow these instructions! The file is HUGE so it will take a while to download but it worked like a champ!
http://www.youtube.com/watch?v=HyuJ8ii3M4o
Click to expand...
Click to collapse
You mean when since not everyone will take the time to do some research before they embark on this journey called rooting.
hope you get it fixed man.
but just for future reference, (sorry if was already said, didn't read the thread)
a brick is just that, the phone is worthless, cannot charge, no lights, no nothing you cannot get it to turn on or do anything.

HELP with Soft Brick

So I have an old Infuse that my kids use and it went crazy the other day. Not sure what happened. Long story short I keep getting a boot loop at the ATT screen. This phone is not rooted and I'm not sure if it was on Froyo or GB. I've flashed every return from brick I can find on XDA. I'm using Odin and I'm pretty familiar with flashing/rooting etc. Can't figure this one out. The only thing I can think is the boot loaders are not the correct ones? Not sure, I keep seeing GTG's ultimate unbrick but all the links I get to it don't work. this is the only thing I haven't tried. Any help would be appreciated.
Edit to add: After I flash in Odin it goes to reboot then does the open update, verifying update, installing update, successfully installed update package.
Copying media files it says failed to mount/sdcard, can't mount /sdcard your storage not prepared yet please use UI menu for format and reboot. ??? I think that's the problem. How do I fix??
Just search in the stickies for bootloaders. That will solve your problems
Sent from my SGH-I997 using xda app-developers app
COfatboy said:
So I have an old Infuse that my kids use and it went crazy the other day. Not sure what happened. Long story short I keep getting a boot loop at the ATT screen. This phone is not rooted and I'm not sure if it was on Froyo or GB. I've flashed every return from brick I can find on XDA. I'm using Odin and I'm pretty familiar with flashing/rooting etc. Can't figure this one out. The only thing I can think is the boot loaders are not the correct ones? Not sure, I keep seeing GTG's ultimate unbrick but all the links I get to it don't work. this is the only thing I haven't tried. Any help would be appreciated.
Edit to add: After I flash in Odin it goes to reboot then does the open update, verifying update, installing update, successfully installed update package.
Copying media files it says failed to mount/sdcard, can't mount /sdcard your storage not prepared yet please use UI menu for format and reboot. ??? I think that's the problem. How do I fix??
Click to expand...
Click to collapse
If you'd like to try GTG's Ultimate Unbrick, you can find a working download here:
http://forum.xda-developers.com/showpost.php?p=22404446&postcount=391
Tried everything and no go. Not sure where to go from here. Sure seems like a hardware issue.
COfatboy said:
Tried everything and no go. Not sure where to go from here. Sure seems like a hardware issue.
Click to expand...
Click to collapse
You mentioned it's boot-looping at the Samsung logo - perhaps there's an issue with the power button.
Here's a couple of threads that may be helpful:
http://forum.xda-developers.com/showthread.php?t=2107558
http://forum.xda-developers.com/showthread.php?t=1996709
prairied0gg said:
You mentioned it's boot-looping at the Samsung logo - perhaps there's an issue with the power button.
Here's a couple of threads that may be helpful:
http://forum.xda-developers.com/showthread.php?t=2107558
http://forum.xda-developers.com/showthread.php?t=1996709
Click to expand...
Click to collapse
It goes past the Samsung logo screen then to the ATT Rethink Possible screen then keeps looping on that screen over and over. It charges normally also.
COfatboy said:
It goes past the Samsung logo screen then to the ATT Rethink Possible screen then keeps looping on that screen over and over. It charges normally also.
Click to expand...
Click to collapse
I would try flashing just a kernel (not the whole unbrick package). I have been in a similar situation and after trying everything imaginable that's what ended up fixing it for me.
Sent from my SGH-I997 using Tapatalk 2
prairied0gg said:
I would try flashing just a kernel (not the whole unbrick package). I have been in a similar situation and after trying everything imaginable that's what ended up fixing it for me.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Tried that earlier I thought, tried again just to make sure. Still no go. I appreciate all your help! :good: I'm gonna give up for tonight anyways.
COfatboy said:
Tried that earlier I thought, tried again just to make sure. Still no go. I appreciate all your help! :good: I'm gonna give up for tonight anyways.
Click to expand...
Click to collapse
This happened to me earlier. What I did was-
1 Went to full stock using heimdal one click, After completetion, U may stuck in bootloop in at&t as you said
2 Flash efs.zip found in the link below using odin. put efs.zip in odin and untouch any other setting and flash, (Ur imei may be previously corrupted so u got bootloop). This doesnot do any harm. So flash with confidence. If ur device doesnot show up in odin after u flash with heimdal one click , reinstal drivers with kies mini
Link for download http://forum.xda-developers.com/showthread.php?t=1729838
3 Now u'll be out of AT&T bootloop if ur imei was previously corrupted.
I was in similar situation. And this solved my proble.
Hit me thanks if I helped you :good:
Thanks for all the advise. Still not working. Tried everything above and much more. Different things I do give different results but pretty much the same in end. Either sticks in recovery or boot loops one way or another. Really don't see how this could be related to software but you never know I guess.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] Tried to root phone, now won't boot

tried to root my Skyrocket, tried to put on latest cm10.1 nightly, got system 7 error, someone said to format. Did so, now it won't go past the samsung screen. Can someone help me fix my newb-ness?
Noobs have no business messing with nightlies.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Noobs have no business messing with nightlies.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
thanks for stoppin' by
lookslikescreech said:
thanks for stoppin' by
Click to expand...
Click to collapse
Np, enjoy the skyrocket!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
lookslikescreech said:
tried to root my Skyrocket, tried to put on latest cm10.1 nightly, got system 7 error, someone said to format. Did so, now it won't go past the samsung screen. Can someone help me fix my newb-ness?
Click to expand...
Click to collapse
Start at the beginning. When you rooted your phone what ROM/build were you on? Stock? What Recovery are you running? Did you make a backup? In my experience, you usually get a system 7 error when the download is bad, (did you check the MD5?) or if you're trying to flash a ROM that doesn't match your current system (IE: trying to flash a JB ROM when you're currently on ICS.)
The more info we have, the better we can help you.
Fall of Enosis said:
Start at the beginning. When you rooted your phone what ROM/build were you on? Stock? What Recovery are you running? Did you make a backup? In my experience, you usually get a system 7 error when the download is bad, (did you check the MD5?) or if you're trying to flash a ROM that doesn't match your current system (IE: trying to flash a JB ROM when you're currently on ICS.)
The more info we have, the better we can help you.
Click to expand...
Click to collapse
Uh status 7 is assert protection so its a mismatch usually in device info typically model numbers, and has nothing to do with bad downloads.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Fall of Enosis said:
Start at the beginning. When you rooted your phone what ROM/build were you on? Stock? What Recovery are you running? Did you make a backup? In my experience, you usually get a system 7 error when the download is bad, (did you check the MD5?) or if you're trying to flash a ROM that doesn't match your current system (IE: trying to flash a JB ROM when you're currently on ICS.)
The more info we have, the better we can help you.
Click to expand...
Click to collapse
Thanks for helping
I had a stock rom on it and found a youtube video referencing the how to guide in this forum, walked everything through step by step but didn't do the twrp thing, only odin . Tried it, didn't work. Didn't checkthe MD5 as it wasnt referenced in the video (have since seen it in the thread).
I'm gonna try and flash a stock rom with odin if I can and start over and ignore the youtube video.
At the moment Odin is the only program on my computer that talks to my phone so I'm hoping that works, just gotta find how to do it...
lookslikescreech said:
Thanks for helping
I had a stock rom on it and found a youtube video referencing the how to guide in this forum, walked everything through step by step but didn't do the twrp thing, only odin . Tried it, didn't work. Didn't checkthe MD5 as it wasnt referenced in the video (have since seen it in the thread).
I'm gonna try and flash a stock rom with odin if I can and start over and ignore the youtube video.
At the moment Odin is the only program on my computer that talks to my phone so I'm hoping that works, just gotta find how to do it...
Click to expand...
Click to collapse
Yeah, stay stock until you have a clue on what you're doing.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
lookslikescreech said:
Thanks for helping
I had a stock rom on it and found a youtube video referencing the how to guide in this forum, walked everything through step by step but didn't do the twrp thing, only odin . Tried it, didn't work. Didn't checkthe MD5 as it wasnt referenced in the video (have since seen it in the thread).
I'm gonna try and flash a stock rom with odin if I can and start over and ignore the youtube video.
At the moment Odin is the only program on my computer that talks to my phone so I'm hoping that works, just gotta find how to do it...
Click to expand...
Click to collapse
In this section (q&a), read through "the ultimate newb guide" by vincom.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
btm fdr said:
In this section (q&a), read through "the ultimate newb guide" by vincom.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
thanks, on it now. Just need to get it back to stock with Odin then I'll try again when I understand what I'm doing more.
Anyone feeling charitable and want to tell me how to flash the stock rom with Odin? I'd appreciate it.
lookslikescreech said:
thanks, on it now. Just need to get it back to stock with Odin then I'll try again when I understand what I'm doing more.
Anyone feeling charitable and want to tell me how to flash the stock rom with Odin? I'd appreciate it.
Click to expand...
Click to collapse
It's in the guide bro
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Best of luck mate, reply here if you have any issues. And for pete's sake, next time, instead of watching a YouTube video, read read read and re-read the forums. Once that's done, read them again. Only then, start flashing.
Fall of Enosis said:
Best of luck mate, reply here if you have any issues. And for pete's sake, next time, instead of watching a YouTube video, read read read and re-read the forums. Once that's done, read them again. Only then, start flashing.
Click to expand...
Click to collapse
hahaha thanks
Now it says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Far out, I can't win tonight!
lookslikescreech said:
hahaha thanks
Now it says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Far out, I can't win tonight!
Click to expand...
Click to collapse
Bro, you're going to end up with a paperweight. That guide is step by step. Read it, read it again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
lookslikescreech said:
hahaha thanks
Now it says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Far out, I can't win tonight!
Click to expand...
Click to collapse
That's an alternate form of DL mode. Odin a stock ROM from that screen. Read the Noobs Guide. Odin is finicky so pay attention to the guide. Then read it again. Once you've read and comprehend it all spin in a circle saying "I deserve this" three times and Odin will grant your wish. lol
hechoen said:
That's an alternate form of DL mode. Odin a stock ROM from that screen. Read the Noobs Guide. Odin is finicky so pay attention to the guide. Then read it again. Once you've read and comprehend it all spin in a circle saying "I deserve this" three times and Odin will grant your wish. lol
Click to expand...
Click to collapse
hahaha thanks
Got it working, used TWRP to flash the latest RC CM 10.1
Got it all going now after a minor heart attack and a few more grey hairs. Just gotta figure out why the wifi isn't working at all now. Can't get it to turn on.
Your original 'system error 7' problem was most likely caused by trying to flash a newer ROM with an older version of CWM or TWRP. Glad you got the phone up, can't help you with the wifi problem, sorry. Although, what modem did you flash, if any? System Settings -> About phone -> Baseband version?
Tom
rpr69 said:
Your original 'system error 7' problem was most likely caused by trying to flash a newer ROM with an older version of CWM or TWRP. Glad you got the phone up, can't help you with the wifi problem, sorry. Although, what modem did you flash, if any? System Settings -> About phone -> Baseband version?
Tom
Click to expand...
Click to collapse
I flashed the UXUMA7 radio, didnt really do much, it worked before.
Still can't figure out the Wifi though :-/ just straight up won't turn on.
If you are on a newer CM 10.1 , the only supported radio is UCMC1, UXUMA7 is really old. That may be why wifi is not working.
UXUMA7 and UCMC1 are very similar. First one is the Rogers and second is att's release which is usually late by a month or so after rogers. Bottom line both will work.
Have your radiofile.zip, cm10.1.zip, and gapps from 20130301 all on your SD card.
Do you have a back up, nandroid? If not do it now.
Go to recovery and Clean up well:
Go to mounts and format data, system, cach twice or three times. Go to advanced and clean dalvik cache. Don't reboot
Now installing in this order:
- radio
-cm10.1
-gapps
Now reboot your phone.
Wait until it is finished and leave it untouched for 10 minutes to settle down and do its thing.
Then turn it off back on and enjoy.
Your noob status will start to fade if you do a clean install :thumbup:
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Categories

Resources