Related
So I flashed the Deodexed version of the new stock 3.70 ROM this weekend and it re-booted with no problem. I played with it for a few minutes, and then went back into Recovery using CWM and flashed the Radio/WiMax combo and it flashed unusually quick. The on screen message then prompted me to Re-boot to complete initialization or something to that effect. So then I re-boot and it takes a second for the screen to shut off like usual and then where it normally brings up my splash screen it brings up the little cigarette looking box with the arrow pointing towards the Android guy standing outside the box and the RED TRIANGLE image. I didn't panic and did a battery pull as I have had this happen once before. I put the battery back in and try to power on and the same image pops up. I did a battery pull again and tried to turn on the device in Hboot mode and then something bad happened, the same image popped up again. FML. I have waited 24 hours and attempted to go back into HBoot and the same thing happens over and over. I downloaded both the ROM and the radio/wimax file from my phone, but I did notice the Radio/Max file downloaded unusually quick ( Bad download maybe???) and I also performed a NANDROID back up but without being able to access my HBOOT, it's pretty much useless to me. Needless to say, I am currently the owner of a $500 dollar paper weight ( A very nice one might I add). I do have insurance and can make a claim if need be. But I would really like to avoid having to pay the deductible if at all possible. I have used these forums religiously and am now hoping that some kind soul might be able to save me from the depths of BRICKED EVO HELL. Any links to a guide or input on correcting the problem would be greatly and absolutely appreciated. Or if you just want to be brutally honest and tell me my EVO is doomed from now until eternity I would appreciate it also... Thanks for reading if you made it this far and I anxiously await any and all responses
Well hopefully u didnt screw up the phone by pulling the battery put that sign with the arrow pointing down is just writting the new radio down on the phone just let it set for awhile takes a good 5 min the most
Have you tried to boot up the phone without the SD card?
Edit:
Sorry for the short response but I said that because I believe that the CWM recovery is stored on the SD card or at least part of it. Maybe that'll work. If not I'll try and think of something else.
WOW... SMH
Words can not express how much of an idiot I feel like right now. I have never flashed a radio and did not realize that image was indicating writing of the radio. If I just bricked my phone because my dumb ass didn't do it right... I have flashed countless times and always made sure to feel comfortable before doing so and now this happens. My phone is in my car and im here at work. Do you think I should just power on the device and let it sit there at that image or what? I hope pulling the battery in the middle of instillation didn't brick it forever. Damn, I am so pissed at my self its not even funny
Try that. If that doesn't work maybe you can have someone upload the files you need to place on your SD card for CWM. You can pop out your SD card and place it into a reader/laptop and delete the ClockWork folder and replace with the new files.
Hopefully someone with more knowledge can lend their expertise but that's just some things I would try if I were in your situation.
My guess is that you can turn it on but it probably won't do anything because you popped the battery out mid cycle instead of waiting. Hopefully it picks up from where the installation left off but I doubt it.
::: By doing that you'll delete your backup so I'd recommend placing that file somewhere on your computer :::
Pimp. I had the same thing happen to me, I flash the newest 3.70 update and it change everything and I could not go back to my old nandroid so, all I did was flash the sprint lovers with the 3.30 update. It cames with evrythign you need. I hope that this helps you. Put this on the root of the sd card and than press the - volume button and the power button, the phone will look for the pcm36img.zip.and update.
http://www.megaupload.com/?d=D454VSVN
whooo...(huge sigh of relief sound)
So pretty sure I just took a smoke break and went and got my phone. Turned it on, let it sit there for about three minutes, it went through two boot loops ( I was biting my nails ) and then it finally booted up into the new stock ROM ( Thank god ). Thanks for everyone's responses as I had no idea that image was indicating a process on the phone and I thought it was an error message. But you live and you learn, I will try to delete this thread so it doesn't take up any more space. Or maybe leave it up in case someone has a similar problem.. Either way, whatever the moderators want is fine by me... Thanks again a million...
You very likly screwed up your RSA keys for 4g. That happened to me when I pulled the bat as it was writing the radio.
Only way to get those back is via nandroid restore (and hope you have amanra 1.8)
DAMN
You are correct my friend. Everything is fully functional but 4G and I dont use Amon RA, im a ClockWork man. It keeps saying scanning, connecting to sprint, and where it normally says obtaining IP address it just starts saying scanning again. It does this over and over until I turn 4G off. Should I just re-flash the radio/wimax .zip or what? Any links to a guide would be greatly appreciated. So looks like my phone isn't bricked but 4G is broken, so goes the life of a MODDER... SMH
Through adb shell check /data/misc/wimax and do an ls there.
If it is creating a file called 0016......tree.xml, basically a number other than your wimax MAC address (located under battery on sticker) then you have the same problem I did.
There is a thread on XDA that allows you to verify your wimac MAC.
http://forum.xda-developers.com/showthread.php?t=715525
Basically, I deleted the *.tree.xml files that were in my /data/misc/wimax
I did the fastboot process and corrected my wimax MAC.
After I did that, and I verified that it was correct by rebooting phone and turning on 4g. This created a new file in /data/misc/wimax that was my actual MAC address.
It was still stuck scanning. Looking at logcat I saw that the RSA keys were invalid.
Luckily I had a backup of a past rom where 4g was working. Amonra 1.8 includes the wimax partition and gets your RSA keys. I don't know if clocks does that.
I restored that backup, booted up and 4g would connect and work.
out of the blue, my phone began to reboot , and turn off and reboot again.
in the forum ive found a lot of fixes but nothing that helps me!
when im trying to go to recovery it goes to the white screen and loops again,
and by the way it reads in green letters pc36100img no found.
help please!!!
thanks
have u tried dropping the 100 and naming it "pc36img" instead of "pc36100img"? i believe thats what it should be named. What rom were u running when this happened?
haha sorry about that
i was running cm7 nightly build 8
also ive tried putting the pc36img.zip on the sd card but nothing, it doesnt read it !!
It has to be all caps as in PC36IMG.zip, and then boot into the boot loader.
im sorry im an idiot, yeah i put the PC36IMG (all caps)on the sd card, it updates but same problem, i even pulled out the battery to brick it! but dammit the same problem!! urgh!!
chinoapple said:
im sorry im an idiot, yeah i put the PC36IMG (all caps)on the sd card, it updates but same problem, i even pulled out the battery to brick it! but dammit the same problem!! urgh!!
Click to expand...
Click to collapse
You're not the first person I've seen that happen to recently on certain nightlies. Unfortunately, in all of the other cases I saw, they weren't able to recovery. RUU didn't work, PC36IMG didn't work, formatting the sd card didn't work, it just looped at the splash screen every time. PC36IMG flashes even appeared to be successful, but it would never get past the looping splash screen. I'm not sure if anyone ever came up with a fix, but when I was following the thread, one dude threw the phone out the window of his car and told sprint he lost it. The other guy went through insurance and shelled out the $100 to get a new replacement. I hope you have better luck. I would try flashing PC36IMG again, or setting hte phone in fastboot mode, and running an RUU. If that doesn't work, I don't think there is too much else to try, that I'm aware of at least. Here is a link to all of the RUU's and PC36IMG's. http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
Yeah cm7 seems to do that to some peoples phones, including mine. I found no solution, as far as I could tell ur only option is a new phone.
Sent from my PC36100 using XDA App
So my phone fudge up and I had to buy another one, I really want to root again and reflash roms. Anyone recommends a good gingerbread rom. That doesn't screw up after 3 weeks
Sent from my PC36100 using XDA App
Well I would say CM7, cuz i have never had any issues.
Altternatives:
King's Ultra [gingerbread edition]
MIUI [gingerbread edition]
Evervolv
Salvage Mod
I just saw this in here for the first time today, but I am seeing it alot!!!
Just glad I went back to sense a few weeks ago....
Hey guys, let me begin for apologizing if this is in the wrong place. I've been trying to read as much as I possibly can regarding these problems, and I'm stressed, and tired.
That out of the way, allow me to attempt to explain...
My Epic 4g seems to be "bricked" but only in the "soft way" (I've seen this term used before, and it seems to fit.)
It will still boot into Clockwork 2.5~ but no further, if I try to boot it farther, it will hang at the Samsung Screen and play the music.
Before anyone flames me, please, try to remember what it is like to have no idea what the hell is what after something weird happens.
I am running OSX Snowleopard, and have gotten Heimdall to run, but it will not recognize my epic when I put it into download mode. I feel like I am out of options, but I do have one more idea, and I wanted to run this past all of you ...
Since I cannot get my Heimdall to find my epic when I put it into download mode, would it be feasible for me to get a microsd reader (I found one at walgreens for 20 bucks), put an update.zip on it of like a stock eclair or froyo ( I hardly even care which version now, I just would like a working phone...) and run the update from sd via the still working clockwork recovery??
If this would work, it would rock, but I haven't seen any mention of it anywhere. I don't see why it would work, but then again I am not a wizard.
Any suggestions? Comments? Reassurance or Guidance?
If anyone could point me towards the best update.zip to try and push via the microsd reader, I would be eternally grateful. Or in general, if you have a better idea, I'd love to hear it...
Thank you so much in advance, to anyone willing to give me a shot or lend a hand...
blueoxide said:
Hey guys, let me begin for apologizing if this is in the wrong place. I've been trying to read as much as I possibly can regarding these problems, and I'm stressed, and tired.
That out of the way, allow me to attempt to explain...
My Epic 4g seems to be "bricked" but only in the "soft way" (I've seen this term used before, and it seems to fit.)
It will still boot into Clockwork 2.5~ but no further, if I try to boot it farther, it will hang at the Samsung Screen and play the music.
Before anyone flames me, please, try to remember what it is like to have no idea what the hell is what after something weird happens.
[snipp].
Click to expand...
Click to collapse
I have NEVER tried this but it sounds like its worth a shot...i would try CM7 just to get something booting (and its a small file to DL).
But you should definitely "find" a copy of windows (google it *cough cough*) and use bootcamp (search in spotlight) to partition your hard drive and install it and have a mac with osx and windows lol i have xp but you can try newer...
its pretty easy (instructions are detailed) and you will never have to worry about "soft bricks" because you have odin
Yeah, I've toyed with the idea of bootcamping again, it's just such a damn pain, and so many of the "findable" windows on google are infected with godknows what. By CM7 do you mean cyanogen mod 7? I've never used cyanogen mod, if you could point me in a good direction I'd appreciate it.
Also, thank you for the civil reply... I have noticed a degree of distast for those who really don't know thier **** on many fourms, but I figure, everyone is starting at some point....
So should I look for a update.zip for CM7 and attempt to push it? Are there other considerations I should take into account? I really see no reason the microsd reader wouldn't work, and given that my phone is rooted and has clockwork operational on it (god willing it's as workable as it seems)....
blueoxide said:
Yeah, I've toyed with the idea of bootcamping again, it's just such a damn pain, and so many of the "findable" windows on google are infected with godknows what. By CM7 do you mean cyanogen mod 7? I've never used cyanogen mod, if you could point me in a good direction I'd appreciate it.
Also, thank you for the civil reply... I have noticed a degree of distast for those who really don't know thier **** on many fourms, but I figure, everyone is starting at some point....
So should I look for a update.zip for CM7 and attempt to push it? Are there other considerations I should take into account? I really see no reason the microsd reader wouldn't work, and given that my phone is rooted and has clockwork operational on it (god willing it's as workable as it seems)....
Click to expand...
Click to collapse
Your welcome, and HERE is CM7 (cyanogen mod 7). This is just to see if your phone still works (seems to me like it will) and after that you can root with clockwork 3.0.0.6 (if you want ext4). Be sure to have an EXT4 compatible rom when u boot into CWM. You will need to flash it after it converts your filesystem.
If you dont mind having a "dead" phone i suggest trying bootcamp...some files dont have "god knows what" and you will be able to odin EC05 prerooted. ALOT easier lol by dead i mean get no calls and sms, etc..
Just download file, put on sd card and flash...should work. I hope it works for you!
I'm going to give this a shot -- Got nothing to loose either way, and I've heard sweet things about cyanogen anyway. I'm trying to see all this as a learning experience. I was a bit freaked to try custom roms before, but at this point, why the hell not, right?
One question: what is this EXT4 business? I've seen it popping up, and I think I missed the boat. What would you suggest for a EXT4 compatible rom to use? ( Are you on an epic, by the way?)
blueoxide said:
I'm going to give this a shot -- Got nothing to loose either way, and I've heard sweet things about cyanogen anyway. I'm trying to see all this as a learning experience. I was a bit freaked to try custom roms before, but at this point, why the hell not, right?
One question: what is this EXT4 business? I've seen it popping up, and I think I missed the boat. What would you suggest for a EXT4 compatible rom to use? ( Are you on an epic, by the way?)
Click to expand...
Click to collapse
Lmao yea i have an epic. And ext4 is just a faster filesystem than RFS which is stock. Also most roms have journaling off which means you
cant just pull your battery and stuff like that because you will have corrupt data (most likely). Journaling enabled (like in stock with RFS)
will simply keep a journal of what the system does and in case of an improper shutdown (battery pull or phone falls and batt. pops out or
batt. drain to 0) when it turns on it will "recover" from where it left off. The only bad thing about this is that it writes to the nand (i
think) ALOT...maybe more than RFS but really it would kill your phone in 3-4 years and you probably wont keep it that long anyway lol
I usually run bonsai but you have to sign up to their forum for the download...i dont think im allowed to post a link. but ive heard Syndicate
rom frozen is also VERY good. And quick. But in short, if you want a speedy epic, choose EXT4 lol
Also you can try MIUI 1.3.5 rom..Its really cool. Sort of like best of iphone and android in one. Im actually one of the guys trying to port it now...
but im not a dev lol
Good luck!! and trust me, custom roms are fun. Especially when you become a flash-a-holic lol
Yeah, I get the feeling it's pretty addicting. I'm going to start by flashing CM7, as you said, just to make sure the thing isn't an expensive paperweight. Next I am either going to try Syndicate or try out the froyo stock w/out bloatware....Since I had it rooted months before the OTA happend, I'd been stuck on eclair. I may just be happy with a working phone, but as this point, i've tasted blood.
blueoxide said:
Yeah, I get the feeling it's pretty addicting. I'm going to start by flashing CM7, as you said, just to make sure the thing isn't an expensive paperweight. Next I am either going to try Syndicate or try out the froyo stock w/out bloatware....Since I had it rooted months before the OTA happend, I'd been stuck on eclair. I may just be happy with a working phone, but as this point, i've tasted blood.
Click to expand...
Click to collapse
Lol it happens to everyone xD
And let me know if it works...if not you will have to try the bootcamp way
Will do...
Thanks again for your help! I truly appreciate it!
As long as you're rooted with a working ClockWorkMod and can manually access your sd card, you can flash anything to your phone. You may want to make sure you format Data, Cache, And Dalvik Cache 3 times before flashing a rom though. Also, you may want to upgrade to ClockWorkMod 3. I have it referenced in my signature. It will need to be booted into first, while it converts to ext4, then a suitable rom like Syndicate Rom Frozen will have to be flashed.
Have you tried to fix it with an update.zip? My assumption is that this would not work for a number of reasons.
Your questions are not new, and have been asked more than once in their own threads as well as general question threads. GOOGLE search your question with "XDA" in the search bar. It's your friend, and it will answer your questions.
Just to recap:
1. CWM 2.5 or 3
2. Flash suitable rom
3. Shutdown properly, no reboot or battery pull!
4. Boot into CWM
5. Backup, and then immediately restore! This will re-engage Journaling and prevent future data corruption
6. Use Google! The more questions that are asked repeatedly, the more threads people will have to dig through to find answers.
Thank you for your reply, I appreciate it.
I have been using google extensively, and it's just that many times I would get conflicting or not quite as clear as I was hoping answers, but yes I understand what you are trying to point out here. Syndicate seems like my best best, and as such I am going to need to get to CWM 3. I went to the thread, I am assuming I should use the new version (EB13) as opposed to the the DK28, correct? Since Syndicate is an EC05, I should go for the newer one?
Excuse me for my ignorance, again, we all start somewhere...
Thanks!
blueoxide said:
Thank you for your reply, I appreciate it.
I have been using google extensively, and it's just that many times I would get conflicting or not quite as clear as I was hoping answers, but yes I understand what you are trying to point out here. Syndicate seems like my best best, and as such I am going to need to get to CWM 3. I went to the thread, I am assuming I should use the new version (EB13) as opposed to the the DK28, correct? Since Syndicate is an EC05, I should go for the newer one?
Excuse me for my ignorance, again, we all start somewhere...
Thanks!
Click to expand...
Click to collapse
I can also recommend Bonsai and Midnight as fantastic roms. I use them all, but Syndicate is my current. Syndicate EB13 is the one you want. EC05 didn't change the firmware, it only modified the modem. I've tested EB13 as well as EC05 with Syndicate, switching back and forth, with no visible problems. If your phone is on EB13 or EC05, then Syndicate Frozen 1.1 should work nicely, it's linked in my signature.
Yeah, unfortunatly it was stuck on DK18 for a varitety of reasons.... I hope that doesn't change anything...
blueoxide said:
Yeah, unfortunatly it was stuck on DK18 for a varitety of reasons.... I hope that doesn't change anything...
Click to expand...
Click to collapse
If you're able to use Odin on your computer, just use my CWM Odin link. You'll find EB13 pre-rooted with CWM 3 and you can flash that straight from the computer. Just be sure you have a Rom on your SD card first so it's ready to install from the recovery menu.
Odin is not a possibility right now, however, I just got CM7 to boot. And although it seems to have no service (or it could be because airplane mode toggles on and off faster than I can blink) it seems to be at least functional in a baseline way. I'm going to try to use one of the CWM backups I saved on my computer to see if that works... Thanks for your help!
blueoxide said:
Odin is not a possibility right now, however, I just got CM7 to boot. And although it seems to have no service (or it could be because airplane mode toggles on and off faster than I can blink) it seems to be at least functional in a baseline way. I'm going to try to use one of the CWM backups I saved on my computer to see if that works... Thanks for your help!
Click to expand...
Click to collapse
Good luck to you! Hopefully you read the following:
What does NOT work in CM7 for Epic::
GPS
Camera
Multimedia Messaging
Bluetooth In-Call (Hands-Free Profile)
WiMax 4G (This is absolute LAST priority, DON'T ASK ABOUT IT)
I don't develop personally, but I make it a habit to try and understand what's going on, and as such I rearrange and personalize ROMs to my liking, and subsequently carefully test them to maximize performance and battery. I like to share my understanding and insight to help alleviate the task from developers who already do so much work in an effort to pay them back!
Yes, I am aware of the current limitations of this incarnation of CM7, it seems as though right now, cell coverage radio is going a bit insane (toggle rapidly airplane mode) with my setup. I am currenly looking into how to get CW3 on it.
Hey I managed to gain access to a windows laptop, installed odin on it, and attempted to reflash with what I imagine are the stock files, but it's failed twice...
Which files should I be using? My phone WAS on DK18, but all i'm looking for now is to get it working in a stock way, then I can venture out again....
Any help?
Edit: Odin said it failed, but it seems like some stuff took, it will boot to the samsung screen, do the sprint yellow boxy thing with music, go to the glowing S, it'll pulsate for a while, then it goes to a black screen sat for a good while., Now when I reboot, it hangs at the first samsung screen again..
Does it look like I just used the wrong files, or was it a usb issue?
I'm a bit perplexed...
I'm a noob as well. You need to watch qbking77 on you tube. He goes through the exact steps and exactly what files to use if using odin in one of his videos. The links are all there as well. I have hade my epic a week and have done about everything in his videos to help me understand what I am doing.
Sent from my SPH-D700 using Tapatalk
http://m.youtube.com/#/profile?user=qbking77&v=YQ2g6J1JgjU&view=videos
That is a link to the video.
Sent from my SPH-D700 using Tapatalk
Hi everybody!
I figure we should have a thread dedicated to telling horror stories about flashes gone wrong. Whether it's because of power failures, bad USB cables, poorly labeled packages, or pure user error, we've all had that moment of worry: "Did I just turn my device into a paperweight?"
It's my hope that, by sharing these stories, we can help each other realize that we're all human, we all make mistakes, and most mistakes can be recovered from. Don't be afraid to share your stories; we can't learn from each other's mistakes if nobody talks about them!
_____________________________________________
My first story is from my Telus SGS3 (I747M, you'll see why that matters in a moment) and is definitely a user-error kind of story.
I've been playing around with CM10 and its derivatives for the past month or two (got my SGS3 on release day and it wasn't running Samsung software 3 hours later) and I'm not new to Android, having run XDAndroid on my HTC Diamond, and bouncing between CM7 and CM9 on my Milestone. The first thing I did when I got my SGS3 was a full block device backup using DD from the command line, which is the only reason I don't have a paperweight today.
I decided to try out Paranoid Android over a week ago and I've been loving it, so I haven't been flashing much lately. But, when I got back from vacation and saw that CM10 had gone into nightly builds, I couldn't resist the temptation to try a clean install. I've got folders on my SD card for ROMs, GApps, kernels, recoveries, and anything else flashable just to make my life easier. Apparently at some point I downloaded an AT&T (I747, no M) modem, stuck it in a "/modems/" folder with the rest of my flashables, but realized that it wouldn't work on my device, so I never used it. I then promptly forgot that I had put it on the SD card, and it had a fairly cryptic filename. Away I went, flashing CM10, GApps, a nice bootscreen, and... the modem.
Dammit. :crying:
At this point, I was running the newest CM10 build, but with a borked modem. I thought I had fallen victim to the IMEI bug that's been going around, but then I remembered something about that modem file not being usable on a Telus device... And had no idea how to get back to a working state. I already knew that none of my nandroid backups would have the modem in them, and the only "stock" flashables I could find were rooted kernels and a nearly-700MB "stock" package that wouldn't download any faster than 10 kb/s. I couldn't wait 20 hours for a download, I wanted my phone now! I tried using Odin with a few of the TAR packages I found, but that only made my situation worse to the point of failing to boot entirely, even restoring a nandroid wasn't helping anymore.
I started digging through the forums in the hope that someone had ripped the Telus modem into a CWM flashable zip, but had no luck. I tried both the Rogers and Bell modems with the same results. That's when I remembered that I had done a block backup, but I had no idea which block device was the modem, and my phone wouldn't even boot up to let me MTP the files over. I was left with CWM recovery as my only option, and had to ADB push 2.5 GB of .img files to the SD card, and DD them one at a time through the ADB shell.
Somehow, it all worked out, and I was back to running Stock Touchwiz with root, and was then able to restore a nandroid from yesterday and amazingly enough Paranoid Android booted up, happy as ever, and in came my emails and text messages. I know I'm lucky that my IMEI didn't get lost in that mess, but it just goes to show that there's no such thing as a backup being "too extensive". You never know when "mmcblk0p99" needs to be replaced with a known working copy.
I do believe im going to flash a stock/rooted ROM and then do a dd backup.
What options do you set for your backups?
Sent from my SGH-I747M using xda premium
I did as follows:
Code:
cd /dev/block/
ls
(get the list of mmcblk devices from here)
dd if=/dev/block/mmcblk0p1 of=/sdcard/dd/blk0p1 bs=4096
...
dd if=/dev/block/mmcblk0p99 of=/sdcard/dd/blk0p99 bs=4096
Obviously you shouldn't have 99 partitions... but you get the idea. I ran each line manually.
Then just move the /dd/ folder off your /sdcard/ and onto some safe storage.
I bought my device off someone from Craigslist 2 nights ago. Went home with device working great. Decided to update from ICS to JB, downloaded everything on the ol gaming machine, go to update using Kies, then BAM! Hung update, bricks phone immediately. Woo....great experience after dropping $400 on phone lol. Contacted Samsung support who told me my update wouldn't work until I registered? I told him it bricked my phone and it wasn't being picked up by computer anymore and I wanted to go back to ICS, he apparently thought waiting 24 hours would fix driver issues. Found JB official rom and learned about Odin. Worked at it until 2-ish am, never worked, woke up, did ICS instead same method, worked immediately, then update worked.
Moral of story? Don't trust Samsung apparently, go with 3rd party everything....
Can we share from other devices? Because I've had a serious one with my nitro HD lol.
Sent from my SGH-I747 using xda premium
After having my phone on stock rooted touch wiz since day one I was tempted to go jellybean... So months later I'd say Octoberish I finally said f**k it I'm going aokp... So I ran the task and k toonsen romantic for a while until they started porting the t mobile jelly bean stock tw rom... It made me miss tw and it's awesome camera app... So I flashed it after a week or so upon its release... First thing I noticed was the phone would get txts and phone calls rarely (keep in mind I'm in an lte area) and it became un bare able after about an hour. So I reverted back to my aokp nandroid and just figured I'd call it a day... But when I restored my nandroid my service was still messed up.. So after a bit of gooogling I checked my phone status to find my imei to be 0!!! I was beyond upset... So I tried re flashing stock in Odin and everything else I could find (unfortunately the imei restorer wasn't existent yet) and it came to the point where I left it stock and went to the att repair center down the road... The guy didn't know what was wrong with it and I just played dumb... After about 30 mins he came to the conclusion that my sim card slot was broken and I got a new phone...
After getting this one back home I instantly rooted it again
I've been staying away from those ported tmobile roms ever since
Sent from my SAMSUNG-SGH-I747
[/COLOR]
rani9990 said:
Can we share from other devices? Because I've had a serious one with my nitro HD lol.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I dont see why not. All stories are interesting lol
Sent from my SAMSUNG-SGH-I747 using xda premium
No bad flashes .... Yet?
Sent from my Nexus 7 using xda app-developers app
Alright then,
It was my first day with the LG Nitro HD. My first smartphone (don't comment xD) and I was prepared to root and flash the living crap out of it. Done with rooting, now to install CWM. Simple enough, right? WRONG. This was the one time where google was not my friend. I followed a horribly misleading guide, and ended up with a paperweight. Turns out I flashed the recovery image to the secondary bootloader partition, thereby bricking my phone completely and utterly, irreparably. Had to ship it off to LG, and they fixed it, no questions asked. Thank God for that...
I had an HTC Touch Pro on Sprint. You had to flash a stock ROM before flashing a new custom ROM or the phone would stop working properly after almost exactly an hour. The file system would become completely messed up but the OS would keep running from RAM. It would fail to reboot after that. It was such a pain that I updated my phone every ~3-4 months.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
This one actually just happened this weekend.
So I finally got bored of having stock ICS on my i747 (Rogers), and since I loved cm 7/9 on my SGS2, I figured I'd go with the latest (15 dec) CM10 nightly.
downloaded to phone, rebooted in recovery, wiped data and cache, and installed the new firmware.
booted up and I've got no (or inconsistant) cell service. Figure it's a bug that hasn't been fixed, so no biggie, I backed up a week ago, so I decided to revert back to stock for the time being.
go through the process, and discover I still only have EDGE data.... WTF?
So I do some reading *AFTER the fact, hur dur...* and discover the IMEI wipe issue, and surprise surprise, I didn't do an NV backup, since I didn't know it'd get wiped.
Spent a couple hours keeping the phone / computer away from the 13 month old while I replace the IMEI NV data.... Still stuck on EDGE.... at least my IMEI is showing up though.
Nick
Odin back to stock worked for me when that happened to me.... YMMV.
Sent from my SGH-I747 using xda premium
The night I got my phone, I rooted via odin and when it booted, I'd get a framework FC every 90 seconds or so. It took me almost two hours to get cwm recovery on my phone to flash AOKP. Not a brick, but since I hadn't even activated it, yet....not happy.
Sent from my SGH-I747 using xda app-developers app
Each Phone an Adventure
I can completely relate to all of you. Though I'm new as a member (thought I already had an account but apparently I didn't), I've been using the forum for a long time. I have rooted four phones to date, each with its' own disaster story and happy ending. My latest was the AT&T S3. While not a disaster entirely, the no flash counter guide ended up not working out for me. So I paved my own trail so to speak and I found all the root dependencies (Recovery, ROM, the works) by myself. The entire process took me about a day. I also used TriangleAway which threatened explosions if anything went wrong and thankfully nothing did. I'm glad I never had to send a phone back, I've always been very cautious about any type of flashing and always read the forum before doing it.
When I was on the captivate, I really wanted JB so I thought I could grab the Nexus S JB ROM cause the devices were so close to each other. Flashed it via Odin. Good God was that a mistake. I couldn't get back to download mode using the button combo since the button mapping was all switched up. I had this one cable that would give me bad connection, so I jiggled that around in the port for 35 minutes trying to get download mode. Finally, I got it and flashed the stock package. Learned my lesson, will never flash something from a different phone or anything that won't work 100%.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
goobs408 said:
When I was on the captivate, I really wanted JB so I thought I could grab the Nexus S JB ROM cause the devices were so close to each other. Flashed it via Odin. Good God was that a mistake. I couldn't get back to download mode using the button combo since the button mapping was all switched up. I had this one cable that would give me bad connection, so I jiggled that around in the port for 35 minutes trying to get download mode. Finally, I got it and flashed the stock package. Learned my lesson, will never flash something from a different phone or anything that won't work 100%.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
The thing about the Captivate was, no matter what ROM you flashed, the jig ALWAYS worked. It saved my ass quite a few times, until that is, the memory in the phone decided to die. I could flash through Odin as much as I wanted and it would pass everytime, but never go past the boot animation.
Dave the Knave said:
The thing about the Captivate was, no matter what ROM you flashed, the jig ALWAYS worked. It saved my ass quite a few times, until that is, the memory in the phone decided to die. I could flash through Odin as much as I wanted and it would pass everytime, but never go past the boot animation.
Click to expand...
Click to collapse
Flash stock GB with forgot name of kernel baked in. After that in cwm recovery partition external SD card.. then reflash in Odin then install whatever ROM u want
Sent from my SGH-I747 using xda premium
Trying to use Kies to flash anything. That's always a bad story for me
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Don't attempt to explain to a friend of little flashing knowledge how to root their phone. He hard bricked my phone. Odin is easy if you read but he turned it into rocket science and yeah.. Had to wait for another phone
Sent from my SGH-I747 using xda app-developers app
Well let me begin by saying I have a Galaxy Nexus and have been flashing roms, etc like it's going outta style. It's very simple to me and I am no newb. So with this logic in mind, I got a brand new GS3 the other day and proceeded to do the same. First, it took my a while to realize there are so many variants of our phone, then when I did a search I saw that there was a i9305 that is LTE....you already know where this is going. I figured that was the correct variant, spent like an hour trying to install a recovery because of the auto wipe feature and thus increasing the flash counter to 10+ (wtf!). Finally I download a rom, flash it. Freezes half way through (knew that wasn't good) and when I pull the battery, BAM, bricked phone.
After some more reading, not only did I find out the correct way of flashing to not increase the counter but also that the Canadian versions are the i747! Luckily it happened a day after I got it and I switched it out for a new one. Moral of the story: If you are flash happy and think all phones are like the Nexus, that's your biggest mistake! lol
Hey Folks, I need your help. I've got an ATT GS3. I've got intermediate skills with root/ROM activity, but have gotten in over my head.
After many months of bouncing around AOSP ROMs I decided to go back to TW based b/c I have had rebooting issues ever since CM went to 4.3.
I went from Carbon to Hyperdrive. It never would finish "activating" so I moved to Dandroid. It seemed fine. I restored from TB and got things setup. Everything seemed fine. I left it on the charger and after a couple hours I went to get it and see it locked up at the 'Samsung Galaxy SIII' screen you see right after power on button. I figured the ROM had issue and would try something else.
TWRP seemed to still work until I noticed that it could not mount any internal memeory, though it could mount/navigate the ext SD card. On the chance TWRP was messed up I tried a flashable recovery replacement from TWRP to CWM. The flash seemed to think it was good, but a recovery reboot still showed wonky TWRP. Next I tried to ODIN back to original OEM FW. Odin stopped with 'Fail (write)'.
I'm not sure what to do here as it seems the internal memory is just not there. I've searched for similar condition w/o luck. It is so strange that it was working fine for about 12hr on Dandroid and then just gone.
Anyone have an ideas?
Always a good idea to save anything u want to keep from the internal storage and wipe it also when going from aosp based roms back to tw...
After chasing this for many more hours it seems I'm screwed. My best assessment of the situation is that I've got "sudden death", which is a failure of the EMMC chip.
The fix can be done by these guys for about $150.
That's about all the phone is worth now so I guess I'm phone shopping for something new. Probably Note3 or Nexus 5. I've got my SIM in my old N1 and will slum until the Nexus5 announcement and make a decision then. It better be quick b/c the N1 is hard to swallow coming from GS3.
I've enjoyed the S3. Thanks to the devs for all the great ROMs.
[email protected] said:
After chasing this for many more hours it seems I'm screwed. My best assessment of the situation is that I've got "sudden death", which is a failure of the EMMC chip.
The fix can be done by these guys for about $150.
That's about all the phone is worth now so I guess I'm phone shopping for something new. Probably Note3 or Nexus 5. I've got my SIM in my old N1 and will slum until the Nexus5 announcement and make a decision then. It better be quick b/c the N1 is hard to swallow coming from GS3.
I've enjoyed the S3. Thanks to the devs for all the great ROMs.
Click to expand...
Click to collapse
I had the same problem tonight, but git it back. I flashed TWRP 2.6.1.0 d2att with Odin 3.06. Then from TWRP I flashed a stock rom.
Can you detail how to flash recovery with Odin?
EMMC failure. At best you'll be able to prolong the life a bit but you'll likely encounter issues no matter what. That's the most probable cause of your reboots, too.
[email protected] said:
Can you detail how to flash recovery with Odin?
Click to expand...
Click to collapse
Sure, Open Odin as Admin, load TWRP-2.6.1.0-d2att in PDA, uncheck everything except auto reboot, put your phone in Download mode, plug it in to PC, wait for com port to recognize, and start the flash. I really hope this gets your phone back.
Link to TWRP: http://techerrata.com/browse/twrp2/d2att
As i mentioned, get 2.6.1.0.tar, not img file.