Hello friends, a friend hand me a messed up locked AT&T Skyrocket flashed with the GT-I9100 Firmware for unlocked reasons.
Did not go well because some keys are not working, and else..
Android 4.0.4
Baseband I9100xxlq6
Kernel 3.0.15-I9100xwlpo-cl913058
Build number IMM76D.XWLPO
Im trying to get it back to stock, to get everything working well. I tried installing CWM with Odin and got FAIL message.
Any recommendations on how to do it?
josuemolina2000 said:
Hello friends, a friend hand me a messed up locked AT&T Skyrocket flashed with the GT-I9100 Firmware for unlocked reasons.
Did not go well because some keys are not working, and else..
Android 4.0.4
Baseband I9100xxlq6
Kernel 3.0.15-I9100xwlpo-cl913058
Build number IMM76D.XWLPO
Im trying to get it back to stock, to get everything working well. I tried installing CWM with Odin and got FAIL message.
Any recommendations on how to do it?
Click to expand...
Click to collapse
im surprised it booted up at all, it shouldve of been hardbricked
read the sticky in my sig on returning to stock, read the whole op, espicially the troubleshooting sections.
if it doesnt work you would need a jtag repair, link in the 1stop sticky in my sig
edit: read this thread to see if it fits your situation, possible fix if returning to stock fails Odin Crashes at "Getting PIT for mapping
You are so lucky it booted! Christmas came late for you my friend. Hopefully you are able to successfully get it back to stock
-------------------------------------------------
Sent from my Skyrocket i727 with Chimera 3.0
-----------Nexus 7 running AOKP PUB-----------
My jaw dropped at this lmao. How is that even possible?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Your extremely lucky that your device booted up. Hopefully someone experienced on the forum will be able to correctly answer your question. Best of luck! :thumbup:
:S
Im not the responsible for doing that, my friend gave it to me like that, and Im trying to fix this.. I think they used a JTag computer or something. Im also impressed it boot. I have read a lot, but Odin doesnt seem to work. Im trying from CWM now.. Will i need to install new bootloaders or ill be fine with stock modem/kernel and FW?
Are you sure you're talking about a Skyrocket?
It sounds like you got an I777 in your hands, and Skyrocket is I727. Only I777 would even boot if flashed with I9100 build, Skyrocket would die. Triple-check it before you hard-brick the phone.
I agree with you.
OP
on the back battery cover is it smooth or is it textured.
Both will say galaxy s11
all of the above is true, you are lucky if it booted most people have HARD bricked from installing that
droid512 said:
I agree with you.
OP
on the back battery cover is it smooth or is it textured.
Both will say galaxy s11
all of the above is true, you are lucky if it booted most people have HARD bricked from installing that
Click to expand...
Click to collapse
Or you could pull the battery out and check the model. lol
lol there is always that
So true
Yeah, sorry mates, my friend told me that it was an skyrocket and I didnt even bother to check that, its not an skyrocket, is only a SGH-I777
So what should i try now?
First step.... Dont use anything found on this forum.
Im sure the 777 FORUM has restore stock instructions
Sent from my SAMSUNG-SGH-I727 using xda premium
Thanks!
Thank u people, is fixed now..
josuemolina2000 said:
Thank u people, is fixed now..
Click to expand...
Click to collapse
Wow, you are a saint for hanging out with a dunce like him... Not to mention, calling him a friend jk
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Related
Ok...
All I wanted to do was flash a custom rom on my Rogers I727R so I could get on my laptops adhoc network.
FoxHound_Otacon_V1_LP4_ICS_GSII_By_SnakeS.zip Seemed to be the right choice.
Rooted phone fine, but couldn't seem to get into cwg with the button combonation.
Heard of Rom Manager so ran that, it began flashing the new rom...
The linux text was in italian for some reason, and then I read errors regarding permissions?
Rebooted phone. MF Bricked.
Bought a usb jig, took about two weeks to arrive, followed the jig instructions, still cant get the phone to turn on.
Used a multimeter to check battery voltage, it's reading 3.665v, should be enough?
Any ideas? Besides having Rogers send it back to Samsung and wait 3 weeks, do I have any other options? Cheers.... ...
Nope but where did you get that rom is is a 727 or 989 rom
Sent from my SGH-T989 using Tapatalk 2
You flashed a ROM from a different phone. Its toasted.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yup u need jtag. Service. And also need to only flash i727 or t989 roms
*rubs eyes* f..I thought it said SG2...oh man...
What'll happen if Samsung gets ahold of it? Will they just send it back and say sol?
Sgs2 skyrocket very different then sgs2
rogers dont send your phone to samsung and make you wait 3 weeks, they send you a refurbished GS2 and a return box to put your broken phone and return it back to them. I've do this many times over the past 5 years ive been with them and they never made me wait for any repair
Man, I feel sorry for you. . However, it is not like it is "fried" or anything. A "repair" service is needed to reload the firmware etc.
EDIT: Yeah, try what polish_pat says. TELL THEM YOU TRIED AN OTA SOFTWARE UPDATE, and then the phone just died.
BUT, where the heck did you get the ROM from. Seriously, how could you even THINK of flashing something you had no clue about.
With all respect man, this is a thread all newbies should read. Even when I myself flash ANYTHING I am so tense, even after reading till I get a headache.
Contact adam outler on the forums here. Search for user "Adam Outler". PM him. He will ask you t mail your phone. He is a king in repairs. He has all kinds of hardware tools, and he won't gyp you with exorbitant prices.
Good luck !!
I thought I727r and I9100 were the same thing...argh..
I'll try rogers then on Tuesday and update.
If someone can someone point me to a good rom for I727r so I can get adhoc going when I get my phone back I'd really appreciate it, I really need wifi and adhoc is my only option where I'm located.
Got the rom from galaxys2root.com, didn't realize it wssnt for I727R.
3r4in1ac said:
I thought I727r and I9100 were the same thing...argh..
I'll try rogers then on Tuesday and update.
If someone can someone point me to a good rom for I727r so I can get adhoc going when I get my phone back I'd really appreciate it, I really need wifi and adhoc is my only option where I'm located.
Got the rom from galaxys2root.com, didn't realize it wssnt for I727R.
Click to expand...
Click to collapse
Does the USB jig get you into download by ANY chance? Just by fluke or something ! You said you used a jig.
In ht meantime also look for member Adam Outler and PM him. He always has thousand tricks up his sleeve.
Only if soft brick. You have a hard brick
I did the same thing, people keep saying Odin doesn't work for us Canadians, it does, use Odin on your PC, find stock Rogers ROM, flash that, should fix it, and more questions about how, pm me
Sent from my SGH-I727R using xda premium
Odin only works if he can actually get into download mode he flashed a Rom from a different phone and buggered up
Sent from my SGH-T989 using Tapatalk 2
denenatse said:
I did the same thing, people keep saying Odin doesn't work for us Canadians, it does, use Odin on your PC, find stock Rogers ROM, flash that, should fix it, and more questions about how, pm me
Sent from my SGH-I727R using xda premium
Click to expand...
Click to collapse
Who said Odin didn't work on the i727r? There's even a stock tar file for the i727r. Never heard that before, Sorry bruh but if the phone won't kick into download mode then she's toast
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Odin with i727r
Actually what I read here was:
"NOTE: Rogers users double check to make sure each thread you are reading is compatible with your S2 LTE (I727R) before taking action! As a general tip, the ICS leak Odin TAR files are incompatible with the Rogers S2 LTE."
Not the same thing as Odin not working on Rogers' phones.
Does the new ICS for the att version of the skyrocket have a safe kernal or is it still at risk of having the emmc corrupted?
Update: it seems the brick bug is in the stock ics 4.0.4 , use caution when wiping back to factory. Entropy512 has informed me that the att rom has the mmc_cap_erase command in a host file where rogers does not. I will update as soon as more info becomes available to me.
Wipe internal in the rom and let us know
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Intub8 said:
Does the new ICS for the att version of the skyrocket have a safe kernal or is it still at risk of having the emmc corrupted?
Click to expand...
Click to collapse
you gotta read more
Illnevertell said:
Wipe internal in the rom and let us know
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Lol no thanks.
vincom said:
you gotta read more
Click to expand...
Click to collapse
The answer is not in your sig. It may not be possible to tell until the source drops but maybe a dev has some insight.
Sent from my SAMSUNG-SGH-I727 using xda premium
Now that ics source has been released can anyone confirm the brick bug in Samsung's kernels have been fixed
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Mike on XDA said:
Now that ics source has been released can anyone confirm the brick bug in Samsung's kernels have been fixed
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Click to expand...
Click to collapse
.....I can say that just today I went from rooted/rom/kernal to gingerbread stock, kies ICS upgrade (ran for awhile/made nandroid), reflashed to custom everything again and recovered all apps in 1.5hrs. No probs so far. Have to say that samsung/kies did spend about 20+ minutes on the phone. Even rebooted once during...
wantowan2 said:
.....I can say that just today I went from rooted/rom/kernal to gingerbread stock, kies ICS upgrade (ran for awhile/made nandroid), reflashed to custom everything again and recovered all apps in 1.5hrs. No probs so far. Have to say that samsung/kies did spend about 20+ minutes on the phone. Even rebooted once during...
Click to expand...
Click to collapse
Not to be rude, but how does this apply to my question?
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Lmfao...
Samsung Galaxy s2 Nuclear Rocket - Embryo 3.2 [UCLE2 BASE]
iPhone 4S - Gave it away, not cool enough
iPhone 3GS - Went for a Swim
Dog - Custom Rom [Golden Retriever] [BEAR2 BASE]
Mike on XDA said:
Not to be rude, but how does this apply to my question?
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Click to expand...
Click to collapse
I guess the kies upgrade to ICS. The question was posed somewhere wondering if samsung has fixed there OS. I'm saying that I didn't get it from this site but as up to date as possible. just say'n I guess I didn't mention that I have the supposed domed chip and that I haven't ever had issues
wantowan2 said:
I guess the kies upgrade to ICS. The question was posed somewhere wondering if samsung has fixed there OS. I'm saying that I didn't get it from this site but as up to date as possible. just say'n
Click to expand...
Click to collapse
Wtf
Glad to hear u upgraded to ics without issue but this really doesn't apply to my question whatsoever. Your post was very confusing to top it all off
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Mike on XDA said:
Wtf
Glad to hear u upgraded to ics without issue but this really doesn't apply to my question whatsoever. Your post was very confusing to top it all off
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Click to expand...
Click to collapse
Was a little random. But I was in a car at the time. All I was trying to get across is that I couldn't have done that process with this brickbug being a prob.
wantowan2 said:
Was a little random. But I was in a car at the time. All I was trying to get across is that I couldn't have done that process with this brickbug being a prob.
Click to expand...
Click to collapse
You are incorrect as from what I understood from your original post you were on a rooted gb rom and flashed back to stock in order to update via kies. 1st off, gb kernels aren't an issue and 2nd, Odin is a safe work around the brick bug issue.
No where in here do u say that u went into the settings on ics and performed a factory reset. That will be the true test
Edit: I revisited your post and see youbdidnt specify gb vs ics but even if u were on ics and went back to stock this wouldn't be a problem through Odin
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Mike on XDA said:
You are incorrect as from what I understood from your original post you were on a rooted gb rom and flashed back to stock in order to update via kies. 1st off, gb kernels aren't an issue and 2nd, Odin is a safe work around the brick bug issue.
No where in here do u say that u went into the settings on ics and performed a factory reset. That will be the true test
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Click to expand...
Click to collapse
Nope. I was on Embryo 4.1-->GB(no root)-->then kies upgrade to ICS-->then flashed recovery--> then back to Embryo 4.1......
....for what it's worth. No offense dude.
wantowan2 said:
Nope. I was on Embryo 4.1-->GB(no root)-->then kies upgrade to ICS-->then flashed recovery--> then back to Embryo 4.1......
....for what it's worth. No offense dude.
Click to expand...
Click to collapse
??? What do u mean no offense?
I didn't read anything offensive. I was just trying to wrap my head around what u were talking about. I understand now. As I stated in my previous post though the gb kernels were not affected.
To anyone in "the know", I assume brick bug had been addressed and the kernels fixed but can anyone actually CONFIRM this? Thanks
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Mike on XDA said:
??? What do u mean no offense?
I didn't read anything offensive. I was just trying to wrap my head around what u were talking about. I understand now. As I stated in my previous post though the gb kernels were not affected.
To anyone in "the know", I assume brick bug had been addressed and the kernels fixed but can anyone actually CONFIRM this? Thanks
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
Click to expand...
Click to collapse
I will ask entropy512 to rip the source apart when he has time. He was the one to discover it originally.
Sent from my SAMSUNG-SGH-I727 using xda premium
Intub8 said:
I will ask entropy512 to rip the source apart when he has time. He was the one to discover it originally.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Good to hear. Thanks!
Sent from my Skyrocket i727 running Sky ICS
PS: If I was able to help you then hit thanks
For a one stop shop here is Vincom's thread http://forum.xda-developers.com/showthread.php?t=1652398
this a quote from this post http://forum.xda-developers.com/showpost.php?p=28731347&postcount=27
Originally Posted by mohan_kr
"First of all there are two aspects to the brick bug (apart from the app., that it just *reports* the suspect f/w):
1) The latest touch recovery (5.5.0.4) 4.3 I believe has been moved to ICS with the EMMC erase capability disabled. I don't know about others, since I don't use it..do the research..
2) Executing erase functions from the running kernel, e.g. the stock firmware that is what this zip has..if you look at the sources and *if* the kernel was built with that source, it is safe there too..standard disclaimer applies..since i am assuming it is built with the recently released code.
In general, the brick bug was specific to I believe certain leaks not on our device. And, if you are flashing a custom rom/kernel they all have a big disclaimer, that you can brick your device in many other ways. If you are so afraid, then you should *not* be flashing custom roms, since pretty much every custom rom/kernel will have that disclaimer..
-----
And as for the erasing photos and all. Flashing does *NOT* delete the contents of the internal or external sdcard (except for platform specific data). It will delete /system /data and /cache, read the pinned threads here on what that means (as the install instructions says, you will have to do that step anyways and make a nandroid backup).."
-----------------------------------------------------------------------------------
i'll leave it to you guys to decide what this means
vincom said:
this a quote from this post http://forum.xda-developers.com/showpost.php?p=28731347&postcount=27
Originally Posted by mohan_kr
"First of all there are two aspects to the brick bug (apart from the app., that it just *reports* the suspect f/w):
1) The latest touch recovery (5.5.0.4) 4.3 I believe has been moved to ICS with the EMMC erase capability disabled. I don't know about others, since I don't use it..do the research..
2) Executing erase functions from the running kernel, e.g. the stock firmware that is what this zip has..if you look at the sources and *if* the kernel was built with that source, it is safe there too..standard disclaimer applies..since i am assuming it is built with the recently released code.
In general, the brick bug was specific to I believe certain leaks not on our device. And, if you are flashing a custom rom/kernel they all have a big disclaimer, that you can brick your device in many other ways. If you are so afraid, then you should *not* be flashing custom roms, since pretty much every custom rom/kernel will have that disclaimer..
-----
And as for the erasing photos and all. Flashing does *NOT* delete the contents of the internal or external sdcard (except for platform specific data). It will delete /system /data and /cache, read the pinned threads here on what that means (as the install instructions says, you will have to do that step anyways and make a nandroid backup).."
-----------------------------------------------------------------------------------
i'll leave it to you guys to decide what this means
Click to expand...
Click to collapse
Thanks vin.
Sent from my SAMSUNG-SGH-I727 using xda premium
Do a grep for MMC_CAP_ERASE in drivers/mmc/host - Give me a list of each file it appears in.
Entropy512 said:
Do a grep for MMC_CAP_ERASE in drivers/mmc/host - Give me a list of each file it appears in.
Click to expand...
Click to collapse
Do I need to be rooted to do that entropy.
Sent from my SAMSUNG-SGH-I727 using xda premium
Hey guys.
Sorry for asking this, but Ive looked everywhere and tried 2 different kernels flashing with both heimdall 1.3.1 and 1.3.2, as well as odin 1.85, and I just cant seem to find the right kernel that will flash properly through either flash tool. All I want is to be able to put a new rom on this cappy I JUST picked up.
I have a motorola atrix and a samsung s2 skyrocket, and change roms like theyre underwear, lol. But with no official CWM that can be easily flashed through rom manager, Im having trouble figuring out how to get CWM on this thing. Im not a noob, troll, or whatever else people hate, lol. Its just that there arent any new threads in the cappy section about this, and all the instructions Ive found are at least a year old, and havent worked for me.
I just need to be pointed or guided in the right direction so I can start having fun with this bad boy!!
Thanks guys!!
See here...http://forum.xda-developers.com/showthread.php?p=33386328
Sent from my SGH-I897 using xda premium
ATRIXXIRTA said:
Hey guys.
Sorry for asking this, but Ive looked everywhere and tried 2 different kernels flashing with both heimdall 1.3.1 and 1.3.2, as well as odin 1.85, and I just cant seem to find the right kernel that will flash properly through either flash tool. All I want is to be able to put a new rom on this cappy I JUST picked up.
I have a motorola atrix and a samsung s2 skyrocket, and change roms like theyre underwear, lol. But with no official CWM that can be easily flashed through rom manager, Im having trouble figuring out how to get CWM on this thing. Im not a noob, troll, or whatever else people hate, lol. Its just that there arent any new threads in the cappy section about this, and all the instructions Ive found are at least a year old, and havent worked for me.
I just need to be pointed or guided in the right direction so I can start having fun with this bad boy!!
Thanks guys!!
Click to expand...
Click to collapse
I had problems too, i just figured everything out and this worked for me.
To do this successfully, you need to be running gingerbread on your cappy.
1.) go to goo.gl/4vmPj
2.) read EVERYTHING and make sure you understand it.
3.) Download the Odin and Kernel they provide. I suggest the kernel v.7.05 that it recommends too because other versions gave me problems this version worked the best for me.
4.) follow all the steps there, it will give you cwm recovery AND root.
5.) Now you can flash any rom from the captivate android development section like normal but this first time when going from stock to a custom rom, DO NOT wipe data/factory rest in cwm!!
6.) Enjoy :good: :laugh:
Appreciate the help fellas!
I followed your link anwarkhan and corn kernel worked perfect! Just complete my first backup of stock, so now its time to play!! lol
But my ACTUAL problem turned out to be odin not recognizing the device. I didnt realize it wasnt seeing it.
Turns out I just needed to update the samsung drivers on my computer. I thought I had done that through heimdall, but aparantly not.
Just went in and manually updated them and voila!
Thanks again guys
Yeah, Heimdall installs it's own drivers, and those specific drivers are only installed to the one usb port that u r connected to with ur phone at the time of the install.
Odin uses the drivers from samsung.
For another helpful thread on Connection Issues, etc. etc. ---- see this....http://forum.xda-developers.com/showthread.php?p=33227541
Sent from my SGH-I897 using xda premium
Awesome!! Thanks again!!
Quick question.
Why are you not supposed to do a factory reset when coming from stock?? Just a little curious.
Sent from my SGH-I896 using xda app-developers app
Not sure why that was posted. Because when flashing a Developer's Rom it will be a full wipe rom anyway, usually.
And ur apps and other stuff u should have backed up before flashing.
Sent from my SGH-I897 using xda premium
That's what i figured. Anyway, I'm happy to report that i am now running aocp 4.2 jb, rooted and recovery'd, lol. Thanks for the helpful hints fellas. Let the games begin!!!
Sent from my SGH-I897 using xda app-developers app
ATRIXXIRTA said:
Awesome!! Thanks again!!
Quick question.
Why are you not supposed to do a factory reset when coming from stock?? Just a little curious.
Sent from my SGH-I896 using xda app-developers app
Click to expand...
Click to collapse
No problem, I'm glad everything is now working for you. && you aren't supposed to do a factory reset when coming from stock because if you do, when you flash the rom and kernel and reboot, your cappy will directly boot into recovery and recovery only and wont boot into the rom. That's the problem I had a few days ago which took me a while to figure out.
Hello guys im really getting sick of the bloatware on Blaze and want to get rid of it and i also want to root my phone. But im literally terrified to do so cause i heard it could possibly brick and i seriously do not have the money to buy another phone and also this is my first time rooting. My blaze is currently running 4.0.4 ics with Baseband version T769UVMB1. It would be a great help if someone could shed some light on the possibilitiy of bricking or destroying my phone, also it would also be great if someone could give me a root guid that is compatible with my Blaze and its baseband version
Code:
chilife15 said:
Hello guys im really getting sick of the bloatware on Blaze and want to get rid of it and i also want to root my phone. But im literally terrified to do so cause i heard it could possibly brick and i seriously do not have the money to buy another phone and also this is my first time rooting. My blaze is currently running 4.0.4 ics with Baseband version T769UVMB1. It would be a great help if someone could shed some light on the possibilitiy of bricking or destroying my phone, also it would also be great if someone could give me a root guid that is compatible with my Blaze and its baseband version
Click to expand...
Click to collapse
anactoraaron said:
Kintaro1991 said:
Hello, I am new to this forum and just got my blaze 3 weeks ago. I know the phone is kind of old but I like it. Any way when I get a new phone the first thing I do is root it and get rid of the bloatware, but after 3 weeks searching and following 2 tuts from other sources I managed to softbrick my phone. All is good there and I managed to un-brick the phone both times. My question here, is there any tuts out there that can help me root my phone? I will post the specs below and hopefully someone can direct me to the right info.
Any help is greatly appreciated and If I missed sonething I apologise as I am in the U.S Army and usually very busy. Thanks guys!
T-mobile Samsung Galaxy S Blaze 4g
Current firmware: 4.0.4 (ICS I believe)-OTA updated accidently
The phone came pre-loaded with 4.0.3...I don't know why
Current baseband: T769UVMB1
Click to expand...
Click to collapse
First, you should never look at "other sources". XDA is the best and you should have started here
Second, wrong thread. Questions belong in the General section.
Third, if you look there is a [GUIDE][ICS]How to root stock just a few posts down.
Lastly, this phone has never been on 4.0.3 lol. There was a recent baseband update to UVMB1 but it is still 4.0.4 just as UVLH5 was 4.0.4.
Hope that helps
Click to expand...
Click to collapse
It seems they want us using the guide for UVLH5 although I followed it precisely (twice) and was unsuccessful.
you can disable bloatware apps with ics
you'd be able to permanently remove them with root
From what I've read on here, the Blaze is pretty hard to brick and if you do, fairly easy to fix. There's a thread on here by beastmode that lays out the exact process in rooting our phone running ICS. I'd never done it before, either, but followed the guide, Googled the info I didn't know, and it went seamlessly.
Sent from ParanoidAndroid Blaze using xda Premium
njstein said:
From what I've read on here, the Blaze is pretty hard to brick and if you do, fairly easy to fix. There's a thread on here by beastmode that lays out the exact process in rooting our phone running ICS. I'd never done it before, either, but followed the guide, Googled the info I didn't know, and it went seamlessly.
Sent from ParanoidAndroid Blaze using xda Premium
Click to expand...
Click to collapse
I believe the Beastmode thread you mentioned is the one I linked, and followed twice, unsuccessfully
It lays out instructions for rooting our ICS Blaze on firmware UVLH5. I (and the op) have firmware UVMB1. They are both ICS 4.0.4, I wouldn't think the process would be any different, and I don't know why it didn't work for me, but it didn't.
In that thread, there are a couple people using that version of ICS that rooted just fine. Odd it didn't work for you. Did you place the zip on your internal or external sd card?
Sent from ParanoidAndroid Blaze using xda Premium
njstein said:
In that thread, there are a couple people using that version of ICS that rooted just fine. Odd it didn't work for you. Did you place the zip on your internal or external sd card?
Sent from ParanoidAndroid Blaze using xda Premium
Click to expand...
Click to collapse
I tried a few more times today, and in combination with a separate root toolkit app, allowing "save root," I've gotten it settled.
So i bought this phone used, i assumed when i bought it that it was a galaxy s blaze 4g, thats the box it came in, now just today after having soft bricked it today i was looking into the warrenty on the phone and i come to find out that the fcc id number is for the wrong phone, so when i tryed to install cwm for the blaze though odin you can imagine what went wrong, i was on stock gingerbread, 2.3.6, now im not sure exactly how to unbrick it here, the threads seem old and google seems to keep taking me to the blaze threads
http://forum.xda-developers.com/showthread.php?t=1470716
Pull the battery and verify the model number before you go much further.
champ1919 said:
Pull the battery and verify the model number before you go much further.
Click to expand...
Click to collapse
I did, thats how i ended up here, its t959v
http://forum.xda-developers.com/showthread.php?t=1500427
Sent from my Xoom using xda app-developers app
If a mod sees this this thread can be closed, after some deep google searching i managed to find a stock gb 2.3.6 firmware for the phone and flashed it in via odin, i thanked everyone who posted trying to help though, thanks
Add [SOLVED] or something like that to the title
Sent from my Xoom using xda app-developers app