Related
I accidentally flashed a ROM for the Galaxy S II SGH-I777 instead of for the Sykrocket. Now my power button won't work at all. I'm afraid I may have completely hosed it. Anyone here who has a lot more knowledge than me have any suggestions on what I could possibly do to get my phone to at least turn on enough to flash a skyrocket rom?
It's done for. Flashing an i777 rom screws up the partitions and the ONLY. and I repeat, ONLY way to get it working again is to send it and get it JTAG'ed. Search. You'll find plenty. This is a recurring issue with users here, sadly. Just saw a topic yesterday about this.
Try download mode, or a usb jig to get into download. Basically your phone is bricked. If the jig does not work. You will want to consider a jtag service. Thank you, bye bye now.
I did the same thing in January, pretty dumb on my part. Totally bricked.
Wow
Android 4.0.4 AOKP
It gets better and better that's 2 in two days ha
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
The explosion of ignorance lately has been amusing, discouraging, intriguing, and worrisome all at the same time.
I did it in January, not yesterday, and yes,it was pretty stupid in hindsight. I had done lots of ROM installs on my old Captivate, for some reason I didn't pay close enough attention to the ROM I was flashing on the Skyrocket and used the wrong one. I'm sure there are lots of people on here who have done the same thing but haven't admitted it.
LOLOLOLOL .. owned.
Why u know reads model numers?? So many trashed phones, what a shame.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
This is the case of someone who buys a Ferrari that only ends up wrecking it. Same thing.
Android 4.0.4 AOKP
Read read read. If you think your sure check again. Double check. Triple check. That's not something you want to learn from.....
Android 4.0.4 AOKP
Schools out for alot of kids who want to be hip and flash romz 2 theyre fonz
I hard bricked 2 weeks ago when i tried to flash a non-skyrocket recovery while riding a rom flashing high
If its been less than 1 year and it cant be turned on go to an at&t store that is certified for warranty replacements play stupid and tell them you plugged it in to a computer to charge and it just blacked out they replaced minw immediately
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
I agree with you. At this point I'd be happy with some sort of update from Samsung/T-Mobile. Even if they just said "we're still working on it" and gave no ETA at least we'd know they hadn't forgotten about it.
If the Blaze Q whatever the hell they've decided to call it launches here in a few weeks with ICS and we still don't get the software I will be ticked.
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Sent from my Samsung Galaxy S Blaze.
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Sent from my SGH-T769 using xda app-developers app
dr4stic said:
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
Click to expand...
Click to collapse
I completely agree with you. To be honest, I am already pissed off that they still havent released it. When I got this phone, T-Mobile promised I was going to get an ICS update in July. Yeah, so much for that. At the very least they could acknowledge our presence and let us know that they havent forgotten about us
Chitown021 said:
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Click to expand...
Click to collapse
The problem is the kernel and libraries specific to our hardware. We have to have a working kernel and libraries before the rest of the rom can come.
I'm not sure why people thought the Blaze Q would've been a good thing for us because unless the hardware was identically similar (which no one had any proof that it was), the releases for that phone would've been useless for ours. The fact that it's now coming with a 720p display (I would've stayed with my Blaze 4G if it had that), and a keyboard tells me that there will be PLENTY different between the phones.
Hardware-wise, the T769 (Blaze) is EXTREMELY similar to the T989 (T-Mo SGS2). How similar you ask? In the original kernel configuration file for the T769, the options are set to build it as a T769 AND T989. There are a few ifdefs that exist purely to stop little snippets of the T989 code from taking effect.
I worked on my own time to try and hack together a kernel from the released sources for the T989 for ICS. Porting specific code from the T769 sources to try to come up with something that worked. Here's the problem: it was stressful and thankless, and at the end of it all I had a kernel that would compile and not boot. No one collected anything to help me attempt this and I was getting tired of having a non-functioning phone that pissed me off. So I ordered me a Galaxy Nexus. I received 2 in a row with screen issues and ended up returning them. I figured I would return to my efforts with the blaze, but at that point I was used to the big phone with a beautiful 720p resolution... so I shelled out the money for a GS3.
I have thought of returning and making a second attempt to port the kernel, and have actually started setting up to do just that. I think I made some mistakes my first time around, so the second time might actually work. But it is A PAIN.
chjema said:
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Click to expand...
Click to collapse
You're right, it isn't... but it's the last time I saw this community bug an outside source for something, aside from buying a couple of guys a phone
Yeah, a 720p screen would have been nice... thanks for the detailed explanation.
I still find it comical that my old HD2 is on the verge of having a fully functional JB rom but my brand new Blaze is still stuck on GB.
Honestly if I could've afforded it I would have probably gone the Nexus or S3 route but given my limited funds and needing to cover two phones (wife needed an upgrade) I thought this was the best value ($30 upgrade cost at Target).
Sent from my Samsung Galaxy S Blaze.
Yes lets please do this.
T-Mobile hasn't updated their page for a month now, and that was for the Gingerbread update they released when they could have been making headway on ICS. I can't find out how to submit any new pages, but I can see two requests for an update that were a couple months old (click on the link, then read on the right side in section "Incoming Links") source = http://support.t-mobile.com/docs/DOC-4182
I went to Samsung's page about ICS updates, and rated it "very dissatisfied," informing them they should have supplied target Year and Quarter (i.e. 2012 Q3) at the minimum, but preferably a specific month. source = http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00046726&fm_seq=49755
Let's continue to put pressure on these assholes, or they will sweep us under the bus while they pursue development of the Samsung Galaxy Supernova 4G Touchwiz Xtra 4.1.
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Dr4stic
If you need want help, testing, anything.let me know of beer more than happy to help.. we need to get ics to this phone
Sent from my SGH-T769 using xda app-developers app
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Click to expand...
Click to collapse
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
I'll be the first to admit I've become a bit jaded because of my experiences with T-Mobile / Samsung and the Samsung Vibrant.
I heard promises about updates to that phone - they even set dates and pushed them back and back and back and finally... nothing.
If anything I think the release of the Blaze Q is a strike against us because our phones are now the "out dated" version of the Blaze and why put development hours into an "old" device.
I'm happy that I have a fully functional phone as it is now (the Vibrant never really had a fully working GPS). An update would be nice but I wouldn't lose any sleep over it because honestly, you may just be setting yourself up for a lot of sleepless nights.
Oh, and on the Vibrant Forum they started a twitter campaign #NeverAgain demanding the promised upgrade or they would never use T-mobile or Samsung again. No one listened.
I know this all sounds cynical but I've seen this show before.
Edit to add: If memory serves correctly this was also the case with the Behold on T-mobile.
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
L7ChrisL7 said:
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
Click to expand...
Click to collapse
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem.
Click to expand...
Click to collapse
What happens when more "cool new apps" are released to the market that require Android 4.0 API's or better? Chrome immediately comes to mind, and there are others with many more on the way. What happens 4 months from now when you are only 6 months into your 2 year contract and you're wondering why you can't realistically run things on your phone that has 1 gig of ram and a dual-core 1.5ghz cpu?
And honestly, btw... I had a myTouch 4G running CM7 that felt miles faster than my blaze. The samsung crapware is not only bloated, but breaks the system in a number of places. You can see this in the fact that you can't have a scrollable wallpaper, or that the system doesn't understand all the loop points in ringtones that work properly in other phones. I can't tell you how frustrated I get by an unlock and/or answer mechanism that can't track my fingers in real time like something as simple as CM7 does.
And don't get me started on the underutilisation of the video hardware.
AwesomeTurtle said:
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
Click to expand...
Click to collapse
No, this phone was released with a promise. When it was released, ICS had been out for 6 months or more, and I'm sure the OEMs had access to the system and API's well before the official release. By the time ICS is released for our phones (IF it is released for our phones), JB will have been out for several months.
This is a matter of support and broken promises. I am NOT just whining. I was sold a phone with a promise of ICS and it has NOT been delivered, and at this point the time has gone beyond reasonable.
If we don't make noise now, it WILL be forgotten and you're going to end up with a phone outdated well before it's time.
dr4stic said:
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
Click to expand...
Click to collapse
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
L7ChrisL7 said:
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
Click to expand...
Click to collapse
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
dr4stic said:
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
Click to expand...
Click to collapse
Well cant you decompile a kernel? or maybe if i get the source of both devices i can use the code to compile a new kernel... hmmm all stuff to try. but compiling a kernel takes a while i think ill update my PC first haha. Im not necessarily worried about the other drivers not working, i just want to make progress, or at least help us make a push in the right direction. Im sorry if im being too optimistic or noobish, i just want to learn what people have and havent tried, so i dont waste my time on what has already been done.
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
here's a thread we can vent at!
spartanerik said:
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
Click to expand...
Click to collapse
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
anactoraaron said:
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
Click to expand...
Click to collapse
http://support.t-mobile.com/people/tmo_erica
Try sending an email to [email protected] and ask (nicely) about a status update on the ICS update for our phone! I just sent one, and hopefully if we send enough we can get some traction
Damn...my third Android device and a completely new dev community. Just wanted to drop by and say hi and I am looking forward to these next few months(we know new phones come out all the time) with you guys.
Welcome! Some of the best advice I can give is back up your IMEI before you start flashing roms, Synergy has a nice backup built into their rom install that's pretty nice.
Sent from my Galaxy S III
Clienterror said:
Welcome! Some of the best advice I can give is back up your IMEI before you start flashing roms, Synergy has a nice backup built into their rom install that's pretty nice.
Sent from my Galaxy S III
Click to expand...
Click to collapse
+1 on the IMEI backup
LosEquisMan said:
+1 on the IMEI backup
Click to expand...
Click to collapse
What is this IMEI backup you speak of? Lol. I'm getting a galaxy s 3 today. Never owned a Samsung, android anyways. Always had HTC for rooting
Welcome! You will be extremely happy with the phone itself, and the amount of developer it is receiving now that the bootloader is unlocked.
As usual, make sure you back everything up before flashing ROMS and enjoy!
I do have one question, I have rooted my SG3, but left the bootloader unlocked. Should I worry about my IMEI getting corrupted?
bluedegeon said:
What is this IMEI backup you speak of? Lol. I'm getting a galaxy s 3 today. Never owned a Samsung, android anyways. Always had HTC for rooting
Click to expand...
Click to collapse
It's when you back up the cell information I think. If it gets erased you won't be able to connect to anything at all.
SubaruCop said:
I do have one question, I have rooted my SG3, but left the bootloader unlocked. Should I worry about my IMEI getting corrupted?
Click to expand...
Click to collapse
I read its best to do it period. People flashing aosp have been losing it more commonly. Unless I'm reading old threads.
Synergized GS3
I still have to get used to this phone...this is going to sound weird...but using it makes me feel as if I'm in a foreign place
Sent from my SCH-I535 using xda app-developers app
I am also getting my S3 either tomorrow or Friday. Just couldn't take the GNEX anymore.
Looking forward to the new community although the GNEX community has been one of the best I have seen so far with the least amount of trolls and fights.
People using great phone have to be great
Never mind it was a joke. And congrats on your SIII.
Sent from my Galaxy Nexus using xda app-developers app
My phone arrived yesterday at 2:30
2:40 activated
2:50 Rooted and Unlocked
2:55 TWRP installed and stock backed up
3:10 Paranoid 2.0 and JB gapps installed
3:15 KT Kernal installed
3:30 Best Android experience I've had yet (including Thunderbolt, Gnex, and N7)
SubliminalME said:
My phone arrived yesterday at 2:30
2:40 activated
2:50 Rooted and Unlocked
2:55 TWRP installed and stock backed up
3:10 Paranoid 2.0 and JB gapps installed
3:15 KT Kernal installed
3:30 Best Android experience I've had yet (including Thunderbolt, Gnex, and N7)
Click to expand...
Click to collapse
That's almost exactly what I did with mine yesterday....I say almost because I received mine about an hour later
Sent from my SCH-I535 using xda premium
I just received mine today and ws thinking to run it stock for a few days to make sure it runs good and this way I cannot blame anything on rooting it.
I remember with the SGS2 on Sprint, after we rooted it it caused a lot of radio issues. Samsung eventually fixed that.
Very hard to hold out though. I do want to run stock Rom rooted as I think it has a lot of cool features. I have been running Jelly Bean on my GNEX for a while now and the 2 things I really liked was Google Now and the new notifications.
I see running CM10 might cause IMEI issues but we can back that up in terminal emulator I see. Once we have that backed up is there anything else one needs to worry about or that is really the only issue that can make our device useless.......
I assume if we stay with TW roms there are no issues with the IMEI? If the IMEI gets messed up, will you know from your data just not working?
I hate getting a device after it has been out a little while! I like to to be there from the beginning and learn with everyone else. Now I feel like I have so much catching up to do!!!
I appreciate everyone's input and help and boy this phone eats my Nexus for lunch, dinner and breakfast!
Im not rooting quite yet...there arent any official ROMs for Jellybean yet...not only that, there are a few things I actually like in Touchwiz surprisingly enough, and yet a few things I dont. I had to replace the launcher(folder system is stupid). I also had to replace the keyboard with the stock Android 4.0 keyboard and the sounds on this phone really annoy me. Anyway, so I guess I am holding out for a good port(or maybe even VZW build) of Touchwiz with JellyBean.
Just a note to you guys with new S3s:
Back your IMEI up!
Seriously. Just do it.
Flashing ANYTHING, be it a TouchWiz ROM or a kernel (even a stock one!) have been reported as having at least one case of IMEI loss.
Just please do it.
From what I understand, with a proper IMEI backup and the right tools (and maybe an LTE SIM reprovisioning) you can restore a device with non-functional CDMA/LTE data/calling.
I flew too close to the sun! I'm an amateur just living off of the greatness that makes this site popular, but I've been fortunate over the years. It finally caught up with me. I have put many, many ROMs on my Nexus 7, Droid X and SG3 without any problems. I think I became over confident in my abilities. When I first started I would read through the whole process and research before leaping but this time I must have missed a step.
The steps to death of a phone
1. Had Pure Google AOSP on my phone for months with no problems (loved it)
2. Thought I had worked a a trade for a Galaxy Note II, so I put the newest Samsung Version back on the phone
3. Trade didn't work out, so I was just going to keep it and try a few other ROMs
4. Used my same 'ol procedures for trying to FLASH, didn't work because of the new Samsung Version
5. Played around awhile got in put CleanRom 6, but the cellphone would not not connect(Stuck in roaming) crap happens
6. Took it back to stock. dialed *2767*3855# everything worked fine
7. Decided to try a few other ROMs
8. This time I during flashing I the phone posted some message from Samsung saying the phone had a improper OS, contact Samsung. (can't remember exact message) This is were I probably screwed up. I got a little lazy and was playing around with my Note 10.1 while things were loading on my SG3. I had a few problems getting back to CWM. Finally, and I'm not sure how, I got back into recovery.
9. Loaded crDroid, got a little confused on which modem to pick, I think I picked XXELLA, everything else seemed straight forward.
10. Package seemed to install
11. On final reboot, the phone went off and never came back... No CWM, No Download mode, Won't charge, zero response to Odin
Oh well, crap happens! I knew it was always a risk. I will send it to MobileTechVideos and see if he can help me out.
EDIT: Oh, I just wanted to say to everyone, I love this site and the people on it.... I could never say that in the "Developer" section because I didn't have enough post. I don't know what drives you people but keep it up! And please don't take my screw up as a negative against any ROM. This is surely my fault for getting lazy. Works for thousands but fails for me? That is me not the package. Will I stop? NO! I'm getting ready to put something on my Nexus 7 as I type this.
SECOND EDIT: I think BattsNotlncld found the problem in two minutes. I don't think there is a crDroid package for SCH-1535. I was on another webpage looking for packages and ran across crDroid.
Easy to see where you messed up. I've never heard of crDroid or XXELLA but a quick google search brought me to the Galaxy S III I9300 forum (aka International version). Flashing a ROM made for the International version will surely give you a hard brick.
Go to www.mobiletechvideos.com
They are the best at fixing bricked phones. I bricked my SGS2 and they had it back to me good as new in 10 days.
BattsNotIncld said:
Easy to see where you messed up. I've never heard of crDroid or XXELLA but a quick google search brought me to the Galaxy S III I9300 forum (aka International version). Flashing a ROM made for the International version will surely give you a hard brick.
Click to expand...
Click to collapse
Yeap, it looks like in my hast to download packages, I slipped into the I9300 world and left my SCH-1535 world. I just recreated my download chain and I clicked on a external link from another webpage to get to the crDroid download. Stupid hurts. I should have stopped when I saw the modem question, but I didn't.
damn this is tough to see. sorry to read about this.
after a mistake like this you will be more careful, bricked an HTC Droid Eris (my first smartphone) and also loaded a leaked firmware, which, stopped us from getting root, which came about a week after that new leaked firmware (lesson learned).
hope to see you back in action soon
thanks
Thanks for taking the time to post your follies! As a novice, I will remember your tale and read everything to the point of understanding before flashing anything.
I've been a long time user of the site & just signed up a few days ago lol I've seen this many times.
Yeah, international versions will brick your phone. That's why it's extremely hard to port an international rom
Good luck man! But like bigtom said, mobiletechvideos can fix almost anything.
Cooter007 said:
I flew too close to the sun! I'm an amateur just living off of the greatness that makes this site popular, but I've been fortunate over the years. It finally caught up with me. I have put many, many ROMs on my Nexus 7, Droid X and SG3 without any problems. I think I became over confident in my abilities. When I first started I would read through the whole process and research before leaping but this time I must have missed a step.
The steps to death of a phone
1. Had Pure Google AOSP on my phone for months with no problems (loved it)
2. Thought I had worked a a trade for a Galaxy Note II, so I put the newest Samsung Version back on the phone
3. Trade didn't work out, so I was just going to keep it and try a few other ROMs
4. Used my same 'ol procedures for trying to FLASH, didn't work because of the new Samsung Version
5. Played around awhile got in put CleanRom 6, but the cellphone would not not connect(Stuck in roaming) crap happens
6. Took it back to stock. dialed *2767*3855# everything worked fine
7. Decided to try a few other ROMs
8. This time I during flashing I the phone posted some message from Samsung saying the phone had a improper OS, contact Samsung. (can't remember exact message) This is were I probably screwed up. I got a little lazy and was playing around with my Note 10.1 while things were loading on my SG3. I had a few problems getting back to CWM. Finally, and I'm not sure how, I got back into recovery.
9. Loaded crDroid, got a little confused on which modem to pick, I think I picked XXELLA, everything else seemed straight forward.
10. Package seemed to install
11. On final reboot, the phone went off and never came back... No CWM, No Download mode, Won't charge, zero response to Odin
Oh well, crap happens! I knew it was always a risk. I will send it to MobileTechVideos and see if he can help me out.
EDIT: Oh, I just wanted to say to everyone, I love this site and the people on it.... I could never say that in the "Developer" section because I didn't have enough post. I don't know what drives you people but keep it up! And please don't take my screw up as a negative against any ROM. This is surely my fault for getting lazy. Works for thousands but fails for me? That is me not the package. Will I stop? NO! I'm getting ready to put something on my Nexus 7 as I type this.
SECOND EDIT: I think BattsNotlncld found the problem in two minutes. I don't think there is a crDroid package for SCH-1535. I was on another webpage looking for packages and ran across crDroid.
Click to expand...
Click to collapse
It's very refreshing to see a user take responsibility and not whine and complain for their mistake. I commend you for that.
With that being said it sucks to see this happen to you. I have never heard of mobiletechvideos.com before this thread but did some looking and it's impressive what they promise. (damn good reviews to back it up too) Looks like it's $60 or so plus shipping to get it up and running again, sounds like a good deal to me.
Good luck, let us know what you do!
cubfan80 said:
It's very refreshing to see a user take responsibility and not whine and complain for their mistake. I commend you for that.
With that being said it sucks to see this happen to you. I have never heard of mobiletechvideos.com before this thread but did some looking and it's impressive what they promise. (damn good reviews to back it up too) Looks like it's $60 or so plus shipping to get it up and running again, sounds like a good deal to me.
Good luck, let us know what you do!
Click to expand...
Click to collapse
I bricked my SG3 just before Christmas and had it back from mobiletechvideos.com before New Years Eve. Pretty good for standard shipping and holiday season!
Mailing it off tomorrow! I bought a Note 2 until my SG3 gets fixed. I had to do something, because I don't have a home phone and my wife travels frequently. It is extremely hard to time an airport pickup without a cellphone. I love my SG3 but I really like the Note 2. I will be selling one in a few weeks. Which one? ....... we will see!
Cooter007 said:
Mailing it off tomorrow! I bought a Note 2 until my SG3 gets fixed. I had to do something, because I don't have a home phone and my wife travels frequently. It is extremely hard to time an airport pickup without a cellphone. I love my SG3 but I really like the Note 2. I will be selling one in a few weeks. Which one? ....... we will see!
Click to expand...
Click to collapse
Some of the best lessons are the ones learned the hard way... but still sucks!
When I got my S3, coming from a HTC Incredible, the biggest concern I had was how big the phone was.... now I would totally consider the Note2. Post which way you decide!
---------- Post added at 02:13 PM ---------- Previous post was at 02:12 PM ----------
[/COLOR]
Cooter007 said:
Mailing it off tomorrow! I bought a Note 2 until my SG3 gets fixed. I had to do something, because I don't have a home phone and my wife travels frequently. It is extremely hard to time an airport pickup without a cellphone. I love my SG3 but I really like the Note 2. I will be selling one in a few weeks. Which one? ....... we will see!
Click to expand...
Click to collapse
You have any updates??
I feel your pain....hard bricked mine on Apr. 1, shipped it off to MTV on Apr. 3, and just found out today it'll be shipped back this week, so.... $95 lesson learned lol
Hey guys, I'm not sure if this is where I'm supposed to post about this so here I go.
I've got an Arc S, rooted, unlocked bootloader. Problem is, I wanna upgrade to 4.2 at least, since I'm on 4.0.4 (4.1.B.0.587) but NOT A SINGLE TUTORIAL OR ANYTHING ELSE HELPED WHEN TRYING TO UPGRADE.
I've been on over 20 sites, tried over 10 how-to's, I already bricked the phone a couple of times, so I'm getting tired of this ****.
The other times I upgraded (from GB to ICS, it took a while, since ICS had just come out, so there were no auto-tools for rooting/etc), it worked beautifully, especially with the XDA how-to's, was just awesome. But now, I can't even get to the recovery mode. The only time I managed to was with the latest X-Parts, but that bricked my phone when I launched the ROM install (CM 10.1, if I recall), this time tho, it can't even install the recovery.
So I'm pretty much outta options, or I wouldn't be bothering you guys with this. I'm pretty sure it's either a failure on SE's part, but every god damned time I tried to boot into recovery mode I get into this useless "safe mode".
I'm far from being a Linux/Unix noob, but god damned, Android's more of a joke than a real distro.
I get that manufacturers and especially carriers **** Android in every way they can, so they should be skinned alive for making this harder on us, in their retarded quest for -illusionary- control over their customers, but this is getting ridiculous.
Please guys, any help would be appreciated.
Anyone?