Related
I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Gzerner said:
I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Click to expand...
Click to collapse
K. The reason you aren't getting to the old version of CWM is because you flashed Codename. Codename is an AOSP ROM which has been known to cause bricks when flashing with Rogue. Because if the bricks the developers opted to but include CWM of any kind in the kernel. What you need to do is find a replacement ROM and download it. Once you've downloaded it you need to flash the EL26 stock CWM (you can find it in the OP of the link below) then use it to flash your new ROM.
http://forum.xda-developers.com/showthread.php?p=295021
Well you're at it is suggest reading the How Not To Brick Your Phone thread in general.
Good luck!
Codename rom is an AOSP rom so your external SD storage will be under /emmc and not /sdcard/externalsd. That's why it wasn't showing up. Same thing with CM9 and AOKP, not because it doesn't work. Also I wouldn't recommend flashing anything ICS related from rogue recovery, js.
And recoveries changed because with our phones, the recovery is packed into the kernel itself so when you flashed Codename, the recovery changed to the stock recovery included with the roms kernel. Hope that clears it up lol.
Sent from my SPH-D710 using Tapatalk
If you want a fresh install, the best way is to Odin the el29 kernal. From there, get into your recovery and wipe and flash away.
Sent from my SPH-D710 using XDA
Hello everyone,
been creeping the forums for the past week...new to the android world but i find the idea of customizing your phone in your own unique way was a good enough reason to leave blackberry after using it for 7years. Anyways....onto my real problem here.
(I appolgize in advance if i mess up the terminology. hopefully you can understand me)
I use a phone on wind mobile (SGH-T999V) and from what i know it's been a safe assumption that if the T999 works then the t999v will most likely work.
I was on AOKP build 5 prior to flashing to the CM M2 ROM...used odin to install CWM_Touch 6.0.1.2.tar then did the steps in
http://forum.xda-developers.com/showthread.php?t=1946701
Edit : I forgot to mention...I can get the screen to go into recovery mode...however, when i press up on the volume key my phone will turn itself off.
and i plugged the phone in again and it decided to be read by my computer.
to install the ROM which worked successfully... however this is where I think i messed up or maybe it has nothing to do with it at all... But my MMS messages did not work so i tried to just play around with some settings and i searched the forums and tried the things that were posted but to no avail. One of the things i did try was to uncheck the privilege unknown applications button and to turn off developers option so USB debugging should be off...or it may have been on...not too sure.
Anyways, so i remembered that I haven't finished the last 2 steps from the "how to flash a rom" in the midst of reinstalling my programs using titanium backup. So i reboot into recovery mode(and this is where i messed up i think) and i wiped my factory data again so after noticing that i did that i went back and restarted the phone and filled in all the information on the welcome screen again. and went back into recovery.
did "wipe cache partition" 3 times AND dalvik cache once then proceeded to install from my sd card the "lk_aosp_jb_tmo-v1.6". After installing i rebooted the device again and i get to see the Samsung Galaxy S3 screen and my screen will go completely black. However, I know it's still on as the battery charging indicator is on and my two buttons around the home button are lit up constantly....out of curiosity i decided to call myself using a land line and the phone is still working (I hope this is good news and that i'm not bricked but teased in a sense i can't fix the screen).
I tried to plug my phone in and it didn't detect it so i reinstalled the drivers and it did detect the phone. I laoded the Samsung Galaxy S3 Toolkit V.2.3.0 in hopes of trying to recover via option 6 "backup and restore your phone" and was hoping to revive it by restoring the nandroid backup however when i typed in my folder the toolkit crashed on me...and now it can't detect my phone as when i try to install the drivers again - the MDA driver seems to fail everytime.
Sorry for the long message...I wanted to be detailed in a sense I don't have to keep giving people more details... your help would be appreciated...Thanks everyone!!
Where'd you get the lk_aosp_jb_tmo_1.6 file from? Never read about it. All you need to do is wipe completely from recovery (data, system, cache...) and install cyanogen and then gapps, reboot.
Sent from my SGH-T999 using xda premium
You can also just odin back to stock and start over from fresh. If you can still get into cwm then just do what he just stated above.
Sent from my SGH-T999 using xda app-developers app
Where'd you get the lk_aosp_jb_tmo_1.6 file from? Never read about it. All you need to do is wipe completely from recovery (data, system, cache...) and install cyanogen and then gapps, reboot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1845836
It was 1.6 as of yesterday when i downloaded it but it looks like it's 1.7 now. That was my original plan however when i boot into recovery i literally have roughly 1second to pick an option before my screen goes blank again. I tried to boot it a few times into recovery trying to "beat" the blank screen but that hasn't worked.
You can also just odin back to stock and start over from fresh. If you can still get into cwm then just do what he just stated above.
Click to expand...
Click to collapse
Yeah the problem is I can't get back into the cwm as my screen goes blank
I tried to find a link for the stock kernel but the 2-3 that i found all have 404.
Something tells me i just ran into bad luck with the kernel flash. or does it have to do with me doing a wipe/data reset again and perhaps not selecting the debugging options/trusting unknown apps checkbox before running it through again? I'm not sure...just grasping at straws here to why my phone is doing that.
Anyone else have more ideas?? Anything will help...Thanks again!!
Looking like an Odin is your option here. To flash a ROM/kernel, wipe data,system,cache... flash ROM then gapps(optional for which ever ROM you are on) and then kernel. Make sure you're flashing the proper kernel.
Sent from my SGH-T999 using xda premium
mt3g said:
Looking like an Odin is your option here. To flash a ROM/kernel, wipe data,system,cache... flash ROM then gapps(optional for which ever ROM you are on) and then kernel. Make sure you're flashing the proper kernel.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Okay - I'll try it tonight when i get home from work. Here's where my lack of knowledge/noob status comes into play. Thanks for the help.
Do i get into Odin via trying to start my phone in download mode? (I tried to hold the power button/down/home) but that's when i get that glimmer of hope before my screen turns blank again when it asks if i want to continue or reboot my phone.
Or do i try to get it running through Samsung Galaxy S3 Toolkit V.2.3 ?? (If that's the case can you tell me which option i should use to get to the appropriate screen? or should i just launch the odin executable file? (however I'm not sure how that would get anything accomplished if my phone doesn't enter download mode...or maybe it's in download mode when i press up on the volume key but the screen is actually blank? Or maybe i don't understand the process 100%)
But lets say hypothetically speaking I manage to get Odin working. Which proper kernel should i be using? I tried looking for the stock kernel but all the links i found 404'ed. Does anyone have one that works? I'm just kind of trying to get my phone working in general...even if it means going back to stock everything. Pointers Anyone?
Thanks!!
Edit: Forgot to mention the fact that I may not be in debugging mode as i tried to turn that off to see if that had anything to do with my inability to send out MMS msg's as i mentioned in my first post... so that might stop me from using Odin no?
Update
Ok well just an update in case it happens to someone else - I pretty much left the phone alone and didn't touch it for 16hrs. Came home from work and it decided to boot up recovery mode so i just wiped data/cache quicker than a little kid wanting to open Christmas presents on Christmas day when they wake up... Needless to say I didn't bother testing the lk 1.6 kernel so i'm not sure if it works with CM10 running a SGH-T999V (Wind Mobile) phone. I'm trying to think of what may have happened and I'm thinking MAYBE it's because i was charging my phone from 20% all the way to about 95 then decided to plug it into my computer ...so maybe an overheat issue?
Anyways. Thanks for everyone's attempt to help. Much appreciated!
Ok I rooted my note 2 Exactly as explained on this site. Worked perfect!! Then did the backup before i flashed the new ROM exactly how it was explained on here and the new PAC MAN ROM worked freaking amazing! I came to the android world after being a faithful iphone user since its launch and when they brought out the BS iphone 5 that was it for me. I knew it was time to switch, and Wow I wish I'd come sooner. The devs on here make owning an Android so much fun!! Cheesy yeah whatever but Im a tech nut so this is my new playground. Thank you all.
Now back to the problem. I wanted to install an overclock Kernal because I had it on the JEDI X ROM previous to the PAC MAN and when I set it at 1.8 the phone was fast and the battery did good enough for my work. However when I tried to install it after the PM ROM the phone will not load past the Samsung Galaxy Note2 load screen. It just goes blank. I've tried every single restore method I could find. It goes to the download mode and itll go into custom recovery mode just fine. But once i try the recovery options with any wipe possible it still only lights up for the Samsung Screen. When i plug the phone into my computer it doesnt show up in the list of removable drives like before however the Device Manager sees it just fine. Hopefully you guys can help. I will answer whatever I left out if I havent been complete enough. Yeah I'm an FNG so Ive got to learn a bit more yet! Thanks again.
Quick Update
ngclassicsgb said:
Ok I rooted my note 2 Exactly as explained on this site. Worked perfect!! Then did the backup before i flashed the new ROM exactly how it was explained on here and the new PAC MAN ROM worked freaking amazing! I came to the android world after being a faithful iphone user since its launch and when they brought out the BS iphone 5 that was it for me. I knew it was time to switch, and Wow I wish I'd come sooner. The devs on here make owning an Android so much fun!! Cheesy yeah whatever but Im a tech nut so this is my new playground. Thank you all.
Now back to the problem. I wanted to install an overclock Kernal because I had it on the JEDI X ROM previous to the PAC MAN and when I set it at 1.8 the phone was fast and the battery did good enough for my work. However when I tried to install it after the PM ROM the phone will not load past the Samsung Galaxy Note2 load screen. It just goes blank. I've tried every single restore method I could find. It goes to the download mode and itll go into custom recovery mode just fine. But once i try the recovery options with any wipe possible it still only lights up for the Samsung Screen. When i plug the phone into my computer it doesnt show up in the list of removable drives like before however the Device Manager sees it just fine. Hopefully you guys can help. I will answer whatever I left out if I havent been complete enough. Yeah I'm an FNG so Ive got to learn a bit more yet! Thanks again.
Click to expand...
Click to collapse
I tried to unroot/unbrick with ODIN. Once I hit start the Message Box in odin says MD5 Hash Value Invalid. Ideas please? Thanks again.
ngclassicsgb said:
I tried to unroot/unbrick with ODIN. Once I hit start the Message Box in odin says MD5 Hash Value Invalid. Ideas please? Thanks again.
Click to expand...
Click to collapse
after you installed your Back up rom files, did you do a wipe cache and etc?I think you have to do the wiping before you flash a rom? I don't remember, I did have a Xoom that kept bootlooping after flashing my back up, so I did a system wipe, factory wipe, etc and it started up.
I also See a option to Wipe Rom, maybe try that? then flash your Back-up Rom Files
You say you can get into recovery, try wiping cache and dalvik, doing a factory reset, then re flashing the rom and kernel.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
ngclassicsgb said:
Ok I rooted my note 2 Exactly as explained on this site. Worked perfect!! Then did the backup before i flashed the new ROM exactly how it was explained on here and the new PAC MAN ROM worked freaking amazing! I came to the android world after being a faithful iphone user since its launch and when they brought out the BS iphone 5 that was it for me. I knew it was time to switch, and Wow I wish I'd come sooner. The devs on here make owning an Android so much fun!! Cheesy yeah whatever but Im a tech nut so this is my new playground. Thank you all.
Now back to the problem. I wanted to install an overclock Kernal because I had it on the JEDI X ROM previous to the PAC MAN and when I set it at 1.8 the phone was fast and the battery did good enough for my work. However when I tried to install it after the PM ROM the phone will not load past the Samsung Galaxy Note2 load screen. It just goes blank. I've tried every single restore method I could find. It goes to the download mode and itll go into custom recovery mode just fine. But once i try the recovery options with any wipe possible it still only lights up for the Samsung Screen. When i plug the phone into my computer it doesnt show up in the list of removable drives like before however the Device Manager sees it just fine. Hopefully you guys can help. I will answer whatever I left out if I havent been complete enough. Yeah I'm an FNG so Ive got to learn a bit more yet! Thanks again.
Click to expand...
Click to collapse
Which kernel are you trying to run with PAC MAN rom? You can't use the same kernel as Jedi is stock based and Pac Man is aosp based. If you flashed the kernel you used on Jedi with the Pac Man rom the results would be what you are seeing. Soooo....try this, boot into recovery and wipe data/factory reset, wipe cache and dalvic cache and reflash Pac Man rom, just the rom and see if it works, if it does great, go find an aosp based kernel and try again. I am suggesting this because of what you said that I highlighted in red in the quote above.
The md5 hashcheck failure sounds like a bad download. If this doesn't work I would suggest looking at mr. robinson's " Root no tripping flash counter" thread and odin flash a stock rooted firmware with odin and start over. Here is mr. robinsons thread
Worst case you can odin stock firmware, root, recovery, restore backup. That may not identify the cause but should solve the problem if you can get to dl mode.
Sent from my GT-N7105 using xda premium
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Re: [Q] Any possible ways to unbrick a softbricked SHGI747
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:
MeatwadGetTheHunniesG said:
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:
Click to expand...
Click to collapse
No problem at all =) Its pretty hard to completely brick your device unless you flash something made for a different phone lol. As long as your phone can see any signs of life (even a faint vibration), let us know and we are more than happy to help!
Sent from my SGH-I747 using xda app-developers app
I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.
S.O.S. Phone is completely wiped only dowload mode and recovery work.
Okay so I think I kind of put myself in a sticky situation. I tried to flash a custom rom onto my phone but in the process deleted my modem file everything worked fine except for the fact that I couldnt make calls or text messages. Basically a $400 dollar multimedia device. At this point I just want to put my phone back to the way it was when I got it at the AT&T store. My phone model is SGH-i747 Galaxy S3 that came with JB 4.1.1 pre installed.
I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.
Click to expand...
Click to collapse
Out of curiosity, how did you finally manage to brick it?
Sent from my Nexus 7 using xda app-developers app
solution
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
There's another thread called stuck on boot screen with same issue. Had same issue with simular Rom had to boot in recovery and clear cache and user settings. And no longer an issue
Soft bricked...
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?
kinjo1023 said:
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?
Click to expand...
Click to collapse
I think I did someting like that too nd now I cant install any ROM and TWRP complains that I have no OS inside the phone.I tried modifying the assert-script file but it then eventually ends up at STATUS 6 and not status 7 again.Pls and Pls help us
You have to be on twrp 2.7.x to install any kk ROMs.
Sent from my SGH-I747 using Tapatalk
Hey guys,
So I desperately need some help here. I rooted my phone using the ODIN method, which worked fine. I put 2 ROMS on the internal memory in order to see which I liked best. I was only able to install one before my phone started heading downhill.
Basically after installing LiquidSmooth (the "stable" one) my phone started wigging out: not letting me access the external SD card (it didn't even see that I had one, and I popped it to reset it), not letting me even open a web browser, saying I had no connection via 3G (which is strange because it's a 4G phone, and it stated so before I installed LiquidSmooth) and just generally not letting me do anything.
Logically I figured I'd just replace the ROM with another, so I tried to install the "Pac-Man" d2tmo ROM... but LiquidSmooth was the only one starting up, no matter what I did (soft reboot, factory restore from keypad, UP vol + power + home, and even from inside the phone settings.) Nothing worked. I even tried to recover a backup I had made before I installed LiquidSmooth, but the menu just kept saying no data present (which is especially odd, since I even put the backup on my desktop, but I just can't get the phone to run it)
I figured, okay well maybe I'll just have to restore from the vol + pow + home screen. Bigger mistake. Now my phone won't boot at all, and I'm at a loss for words. I've rooted other phones with no issue before (I even had to recode a bit of a "one-click" program to root my ol' Galaxy S Vibrant) and now I just don't know what to do.
Here's what I need to know: If I can recover to factory (and if so, what other ROMs are good... I was mislead by everyone saying LiquidSmooth was great *grrr*), and if not, what exactly are my options to get this thing running at all.
Oh, and I was running Jellybean 4.1.1 and it got bumped to 4.2.2 when I installed LiquidSmooth, if that helps at all.
Thanks so much for any and all help.
OneIdiotInATree said:
Hey guys,
So I desperately need some help here. I rooted my phone using the ODIN method, which worked fine. I put 2 ROMS on the internal memory in order to see which I liked best. I was only able to install one before my phone started heading downhill.
Basically after installing LiquidSmooth (the "stable" one) my phone started wigging out: not letting me access the external SD card (it didn't even see that I had one, and I popped it to reset it), not letting me even open a web browser, saying I had no connection via 3G (which is strange because it's a 4G phone, and it stated so before I installed LiquidSmooth) and just generally not letting me do anything.
Logically I figured I'd just replace the ROM with another, so I tried to install the "Pac-Man" d2tmo ROM... but LiquidSmooth was the only one starting up, no matter what I did (soft reboot, factory restore from keypad, UP vol + power + home, and even from inside the phone settings.) Nothing worked. I even tried to recover a backup I had made before I installed LiquidSmooth, but the menu just kept saying no data present (which is especially odd, since I even put the backup on my desktop, but I just can't get the phone to run it)
I figured, okay well maybe I'll just have to restore from the vol + pow + home screen. Bigger mistake. Now my phone won't boot at all, and I'm at a loss for words. I've rooted other phones with no issue before (I even had to recode a bit of a "one-click" program to root my ol' Galaxy S Vibrant) and now I just don't know what to do.
Here's what I need to know: If I can recover to factory (and if so, what other ROMs are good... I was mislead by everyone saying LiquidSmooth was great *grrr*), and if not, what exactly are my options to get this thing running at all.
Oh, and I was running Jellybean 4.1.1 and it got bumped to 4.2.2 when I installed LiquidSmooth, if that helps at all.
Thanks so much for any and all help.
Click to expand...
Click to collapse
Did you flash the latest recovery? Did you wipe data when flashing to a 4.2.2 aosp ROM from 4.1.1 tw? You'll need to do that before and not dirty flashing. Have you done a battery pull? And then tried to enter recovery?
Sent from my SGH-T999 using xda app-developers app
monkeypaws said:
Did you flash the latest recovery? Did you wipe data when flashing to a 4.2.2 aosp ROM from 4.1.1 tw? You'll need to do that before and not dirty flashing. Have you done a battery pull? And then tried to enter recovery?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It auto-wiped to upgrade to 4.2.2, so if there is a way to downgrade it to get it to work, I'd love to know. At the moment all I can access is the Clockwork Mod boot list from the vol+pow+home route. Did a battery pull and entered recovery. Still nothing. If I try to boot without going through the vol+pow+home method, it just vibrates and then nothing.
Update recovery.
Wipe everything except sd cards.
Install rom.
Install Gapps.
Factory reset.
Done.
Aerowinder said:
Update recovery.
Wipe everything except sd cards.
Install rom.
Install Gapps.
Factory reset.
Done.
Click to expand...
Click to collapse
I formatted everything from that vol+pow+home menu.
Gapps? Is that something I should install from SD?
Sorry, I'm just a bit overwhelmed by something I thought would be easy...
OneIdiotInATree said:
I formatted everything from that vol+pow+home menu.
Gapps? Is that something I should install from SD?
Sorry, I'm just a bit overwhelmed by something I thought would be easy...
Click to expand...
Click to collapse
Gapps are Google apps that are required to flash after flashing an aosp ROM. They are usually included as a separate download in the first post of the wrong you are downloading. Make sure you download the right gapps. There shod be a setti ng in cwm to turn on USB connection when connected to comp. So you can load the gapps to your SD card. Then re wipe phone through recovery, reflash the rom , the in the same menu reflash gapps. Then reboot. It should then load properly . Otherwise. If you can access download mode, restore stock rom with Odin, reroot and try again from step one.
Sent from my SGH-T999 using xda app-developers app
If you fix your phone try using twrp instead of cwm thats what i had to do and DL the 2013 version of gapps. I have the latest pacman ROM and the only thing i had to do after install was clear data and cache for the rom control via apps-all-rom control. Well hope this helps.
Sent from my SGH-T999 using xda app-developers app
SamsungGui said:
If you fix your phone try using twrp instead of cwm thats what i had to do and DL the 2013 version of gapps. I have the latest pacman ROM and the only thing i had to do after install was clear data and cache for the rom control via apps-all-rom control. Well hope this helps.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Alright, I just installed both LiquidSmooth again followed by GApps, factory reset the phone, and restarted. Now the phone will not start up (even the vibration) or allow a shift into cwm. Why did this happen? Is there a way to reverse this since now I've lost the ability to even access the cwm?
At this point, I just want to restore to the original loadout, but I've been unable to do that too.
By the way, I do appreciate all the advice on this problem. I'm frazzled beyond belief and have a very expensive paperweight currently.
OneIdiotInATree said:
Alright, I just installed both LiquidSmooth again followed by GApps, factory reset the phone, and restarted. Now the phone will not start up (even the vibration) or allow a shift into cwm. Why did this happen? Is there a way to reverse this since now I've lost the ability to even access the cwm?
At this point, I just want to restore to the original loadout, but I've been unable to do that too.
By the way, I do appreciate all the advice on this problem. I'm frazzled beyond belief and have a very expensive paperweight currently.
Click to expand...
Click to collapse
Make sure you have the ROM of choice and compatible Google apps on your SD card.
Now do the following
1. Pull battery out of phone
2. Put battery into phone
3. Boot into recovery (volume +, home button, power button)
4. Wipe cache
5. Wipe dalvik cache
6. Wipe data/factory reset
7. Install ROM
8. Install gapps (Google apps)
9. Wipe cache
10. Wipe dalvik cache
11. Reboot phone
Once booted up and logged into Google account, go to play store, search for goo manager, download goo manager, open goo manager and press the menu button and install the open recovery script....now you'll have twrp (team win recovery project).
|When Emotion Goes Up, Logic Goes Down|
|Even If You Fall Face First You're Still Moving Forward|
707BeastMode707 said:
Make sure you have the ROM of choice and compatible Google apps on your SD card.
Now do the following
1. Pull battery out of phone
2. Put battery into phone
3. Boot into recovery (volume +, home button, power button)
4. Wipe cache
5. Wipe dalvik cache
6. Wipe data/factory reset
7. Install ROM
8. Install gapps (Google apps)
9. Wipe cache
10. Wipe dalvik cache
11. Reboot phone
Once booted up and logged into Google account, go to play store, search for goo manager, download goo manager, open goo manager and press the menu button and install the open recovery script....now you'll have twrp (team win recovery project).
|When Emotion Goes Up, Logic Goes Down|
|Even If You Fall Face First You're Still Moving Forward|
Click to expand...
Click to collapse
I finished most of these steps, but when I rebooted my phone after installing both LiquidSmooth and Gapps, it refused to start. Now I can neither turn it on or go back into recovery mode. The phone is just dead now. What would cause this? I've taken the battery (and everything else for that matter) out again and again, charged it for the last hour, and nothing has changed.
Okay follow this to get to stock and make sure it can at least do that. http://forum.xda-developers.com/showthread.php?t=2136921
Sent from my SGH-T999 using xda app-developers app
OneIdiotInATree said:
I finished most of these steps, but when I rebooted my phone after installing both LiquidSmooth and Gapps, it refused to start. Now I can neither turn it on or go back into recovery mode. The phone is just dead now. What would cause this? I've taken the battery (and everything else for that matter) out again and again, charged it for the last hour, and nothing has changed.
Click to expand...
Click to collapse
Are you sure you have a T-Mobile phone?
monkeypaws said:
Okay follow this to get to stock and make sure it can at least do that. http://forum.xda-developers.com/showthread.php?t=2136921
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the set of instructions, but I am unable to either start it (power button), put it in cwm (pwr+up+home) or download mode as mentioned (pwr+down+home). I don't get a vibration; I don't get anything. Is this totally bricked now? Since the device isn't on, I can't do anything with Odin or the SD card.
What country do you live in, and how did you acquire your phone? Looks like you maybe have the intl version.
I would say try to get into download mode with the physical bottons if that dint work try a jig u can get on ebay like 5 bucks they are always handy.if u can get in to dl mode odin a root66.tar then install recovery.if that dobt worj u prib install liquid rom but fir diff device abd hard brixk u f that case hope u have insurance ti replace they will never know u rooted ir have it jtaged
Its bricked, jtag repair only way .
Stop flashing in my opinion theres a huge issue with the t999 rom compatility and someone mentioned of tw roms being labeled as aosp.roms,I would root but stay away from flashing.until someone figures this out .Theres way to many brick topics lately i find to be oddly connected to the same causes .
Some will say bs but trust me theres something going on..even the most experienced flashers are bricking the t999 its to me the most easiest brickable device i ever delt with.
lojak29 said:
Its bricked, jtag repair only way .
Stop flashing in my opinion theres a huge issue with the t999 rom compatility and someone mentioned of tw roms being labeled as aosp.roms,I would root but stay away from flashing.until someone figures this out .Theres way to many brick topics lately i find to be oddly connected to the same causes .
Some will say bs but trust me theres something going on..even the most experienced flashers are bricking the t999 its to me the most easiest brickable device i ever delt with.
Click to expand...
Click to collapse
it honestly sounds like he has he international version not the US variant. so i think thats the mistake not the phone
lojak29 said:
Its bricked, jtag repair only way .
Stop flashing in my opinion theres a huge issue with the t999 rom compatility and someone mentioned of tw roms being labeled as aosp.roms,I would root but stay away from flashing.until someone figures this out .Theres way to many brick topics lately i find to be oddly connected to the same causes .
Some will say bs but trust me theres something going on..even the most experienced flashers are bricking the t999 its to me the most easiest brickable device i ever delt with.
Click to expand...
Click to collapse
99% of the bricking is user error...the reason for the increase in "bricked" topics is cause by the amount of users of the T999...its the most heavily used phone by a wide margin now.
Ive far from an expert but have been flashing since the G1 days and have experience with many phones...in my opinion the t999 is darn near unbrickable unless you didnt follow the directions or use a reputable developer when selecting a rom...
To the OP:
What is the actual model of your phone ? you came with an issue and have not really posted much about the specifics of your phone...
sounds like your phone is not partitioned correctly which probably happened by not following the correct directions
there is so much more info needed to diagnose your issue its silly...
Ive been using wicked roms from day one on the t999 and I dont remember seeing anyone hardbrick a phone yet and there are thousands of users using wicked roms...
---------- Post added at 10:58 AM ---------- Previous post was at 10:16 AM ----------
Also...was your phone charged when you last tried to flash something? long ago my phone died while flashing ( lessoned learned) ...
pull the battery for awhile...put it back in and try to charge it...
then try to odin back to stock after its charged...
Even if AOSP and TW ROMs were labelled wrong... what difference would it make ? Sure, it could be misleading and all but it's hardly going to brick a phone just give you something you might not have exactly wanted (if that's even actually happening).
I also wonder if this phone is actually an International version instead of the T-Mobile one.
OP, it looks like you need JTAG repair now. If you don't honestly know what exact model you have talk to the JTAG repair service people about it - since they can most likely JTAG either they can just tell you which phone you have once they've fixed it.
Pennycake said:
Even if AOSP and TW ROMs were labelled wrong... what difference would it make ? Sure, it could be misleading and all but it's hardly going to brick a phone just give you something you might not have exactly wanted (if that's even actually happening).
I also wonder if this phone is actually an International version instead of the T-Mobile one.
OP, it looks like you need JTAG repair now. If you don't honestly know what exact model you have talk to the JTAG repair service people about it - since they can most likely JTAG either they can just tell you which phone you have once they've fixed it.
Click to expand...
Click to collapse
OP just has to remove the battery cover and battery and bam! There's a label with Sammy's logo along with device model and other info about the phone.
|When Emotion Goes Up, Logic Goes Down|
|Even If You Fall Face First You're Still Moving Forward|