Related
Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.
No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...
dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.
dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.
Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!
*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!
Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67
I got a serious issue here. When I turn on my phone, it freezes on the black background/white text "Samsung" screen, and won't load the OS and will stay like that until I pull out the battery. I researched on this site how to fix this issue found out about the 3 button combo (Vol +, Vol -, Power), tried it on my phone, and it didn't work.
I'm panicking now since it seems like I seriously bricked my phone. Did I?? Are there any other solutions??
If it helps, here are details how I ran into this issue:
I tried to install Cyanogen mod using ROM Manager, and it rebooted my phone into what I think is the recovery mode. However, I kept getting this "E: signature verification failed" error which I learned later is what Google implemented with Froyo to prevent people from installing custom roms. I did some research, and I found this xda thread on how to fix it: http://forum.xda-developers.com/showthread.php?p=12321787#post12321787
According to "kisfit2000," I needed to download this file called 3e_recovery_installer.zip and run the install.bat file. I did it and ran into the error:
Installing modified recovery
rm failed for /system/bin/recovery, No such file or directory
failed to copy 'C:\User\HomeDesktop\xxx\xxx' to '/system/bin/recovery': No space left on device'
Unable to chmod /system/bin/recovery: No such file or directory
Click to expand...
Click to collapse
At that point, I gave up and restarted my phone. And that's when the problem began...
Have you looked at this thread? It is a guide on bringing a semi briced epic back from the brink. As long as you can get into download mode and have your pc recognize your phone in odin you should be fine.
http://forum.xda-developers.com/showthread.php?t=1052813
Edit: I just read the op again and see you are trying the three finger method for a vibrant. The three finger boot to recovery method on an epic it to hold vol-, camera, and power at the same time.
THANK YOU SO MUCH! That was extremely helpful. I tried using the Vol-, camera, and power button like you suggested and it didn't work, but your referral to the other thread did. My phone boots up normally now. Phew.
On another note, is there a newbie guide for flashing custom ROMS for Epic4G? I realized my phone started having issues because I was following the wrong guides for other Samsung Galaxy phones, like Vibrant.
Sweet, glad to hear it. Just check some of the stickies in the epic 4g android development section. You should have cwm 3.1.0.1 to start flashing easily, or the acs 1.0.0.5 recovery is pretty much the same thing, but a bit cleaner and more reliable. Read the op of whatever rom you are installing to be sure of the cleanest way to install that particular rom. There isn't really a master list of everything available, but I would start with some froyo roms as gingerbread roms are still fairly unstable on the epic untill official source drops.
Edit: I'll update this post over the next few minutes with some decent places to start.
Here is a one click root and recovery thread
http://forum.xda-developers.com/showthread.php?t=1076967
Here is a guide to flashing different modems. Follow the link in the op to qbkings how to videos, he does an awesome job on those. They my be the most helpful thing to find for a new user.
http://forum.xda-developers.com/showthread.php?t=1123103
Here is a link direct to qbkings how to page. I haven't checked it in a while, but just skimmed it and is definitely the most complete new user guide out there.
http://forum.xda-developers.com/showthread.php?t=1009997
Sent from my SPH-D700 using xda premium
As long as you have a sign of life it is not bricked...sponged maybe. As for guides, there are a few in the tops of each of the forums in the "stickies". Here is one made by qbking77 with a ton of youtube videos and links on how to do most everything on your epic:
http://forum.xda-developers.com/showthread.php?t=1009997
Thanks for the helpful links! I took a look at them and wish I saw these earlier.
Btw, if I wanted to change from one from to another, do I just have to go back into ClockworkMod and just wipe the data/cache, then install the mod? Is there anything else I need to do?
Again, thanks for the help!
jdawg101 said:
Thanks for the helpful links! I took a look at them and wish I saw these earlier.
Btw, if I wanted to change from one from to another, do I just have to go back into ClockworkMod and just wipe the data/cache, then install the mod? Is there anything else I need to do?
Again, thanks for the help!
Click to expand...
Click to collapse
You should have no problem with clearing cache and Dalvik cache then flashing another theme. Some apps may be themed in one and not the other so you may get stuck with a themed app or two from a previous theme. You should be able to reflash your ROM if you ever want a clean start again.
Sent from my SPH-D700 using XDA App
I would get in the habit of making nandroids weekly or even fewer between and store them on a pc or dropbox. You can use rom manager to give your backups custom names to help keep track of what each one is if you want to try different roms and such. You should use titanium backup or my backup root to backup data and apps. It comes in handy for quickly restoring those hard to find apps when jumping around roms. The acs recovery is nice as it has a pre rom wipe and pre theme wipe to simlify things. Mainly just keep reading or ask here before doing anything you are unsure of.
Sent from my SPH-D700 using xda premium
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!
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|
Alright, so I am having this weird issue. I thought I found the fix for it several times, however, NO dice.
I've researched for a few hours now, I just don't know if I have over looked it or what. If it has been answered, I apologize.
I looked at the modified recoveries thread for newer s3 devices, but it doesn't seem to fit my area of error.
The Details:
I've been really curious to try some 4.3 roms. Of course, they are for D2SPR. I get them to flash correctly, after a full wipe. The issue happens right after I set everything up in the phone, and reboot. When I reboot I get hung at the splash screen. I have tried to reflash the rom muliple times only to fall flat on the splash screen again. Now, I don't have an SD Card in the phone, except, I left a TW rom in a folder. I use twrp, forgot to mention that. I rewiped the phone and installed that touchwiz rom, and still it wouldn't allow me to get past splash into that tw rom.
So the only way that I could think of to get out of this hole was to flash the rooted LJ7 tar file I have through ODIN. After getting the S3 into download mode, Odin successfully push LJ7 into my phone. Now again, I had an issue getting it to boot. I read somewhere that when this happens, I need to check the Erase NAND option in Odin. So I tried that out and forced LJ7 back on. After successfully flashing, it boots but gets stuck on the boot animation; the fix to that is booting into stock recovery and wiping once more. Then you are able to get into the OS.
I let the phone sit and take the OTAs till I get from LJ7 to MD4 so I re-root the phone using Odin and Chain Fire's root method. Now I am able to flash the recovery (TWRP) using OpenScript through Goo Manager.
I've only tried flashing Illusion and Carbon's 4.3 rom. The second time I used Carbon's rom. Same results. So I have no Idea what the heck is going on. Can anyone explain this to me better or point me into the direction that I need to go?
Thanks much!
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
bbrita said:
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Click to expand...
Click to collapse
Well, it's good to know that I'm not the only one, however, it's horrible that it's happening to others. I appreciate you spreading the info!
edfunkycold said:
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
Click to expand...
Click to collapse
When I go to set up, I just install about 15 apps, I don't restore. I just download them fresh. I had a habit of doing that and it just stuck. I don't restore anything with Titanium or and root backup/restore app. Could one of those apps not be updated then that causes the partitions to get locked up, or just corrupt /data in general? If that's whats happening.
I just find it extremely odd that I (maybe others), can't wipe, and then re flash another rom; actually I can, it just gets stuck at the splash and never goes forward, that is what had me confused most. If I had an sd card, and formatted data itself, would that fly?
thanks Ed i have tried this after the first 2 tries . i dont have any problems installing 4.3 its just after rebooting it gets stuck. Like you said there are always bugs Im fine with using other roms for now. Hopefully when an official 4.3 drops problems will go away