Develop Bugs

[Q] Bricked my phone. I need help!

I got a new white T-Mobile GS3 last night, to replace a blue one i had that was having bluetooth problems. Once I rooted the new one I restored a nandroid I had made before returning the first one. For several hours the phone worked just fine, until it froze up, leaving my only choice to pull the battery. When I started it up again, it just looped from the Samsung logo to the Galaxy S III logo. I tried to restore the nandroid again, but it said something about incorrect MD5 sums. When that didn't work I tried flashing back to stock through ODIN. It says everything passes, but when it reboots it just continues to loop through the two screens.
Any help would be very much appreciated.

I would recommend you flash the stock boot and recovery > re-root. Though as a general I wouldn't flash a backup, even if from a similar device, ans things of your nature can happen.

I tried to flash the stock boot and recovery through ODIN, but it still wouldn't boot up. Is there a better way I can flash stock?

Did you try clearing all data and formatting system from recovery?
Sent from my SGH-T999 using XDA Premium HD app

daijizai said:
Did you try clearing all data and formatting system from recovery?
Sent from my SGH-T999 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah. Gave that a try.

deecampp said:
I tried to flash the stock boot and recovery through ODIN, but it still wouldn't boot up. Is there a better way I can flash stock?
Click to expand...
Click to collapse
You shouldnt of recovered your old nandroid on a different device, maybe the data partition but not the full nandroid.
Was this theStock Odin tar you flashed?
http://forum.xda-developers.com/showthread.php?t=1737855

Yes, that was the file I flashed

Any other suggestions? I'm really screwed. I can't even use my old phone because of this micro sim card.

Have you tried reflashing the stock Odin tar again?
Sent from my Samsung Galaxy SIII using Tapatalk

Yeah. I've reflashed (as well as downloaded fresh copies), several times. Same results.

delete

What's wrong with my phone

Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.

are you clearing /cache and dalvik-cache before you reboot to the custom rom?

mrmako777 said:
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
Click to expand...
Click to collapse
If you mean clearing those after the install (in recovery completes) then no. Basically after the install I just reboot. Obviously clear and reset everything before I install though.

hd2Raz said:
Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
Click to expand...
Click to collapse
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2

horr1blek1tten said:
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?

Try TWRP 2.2.1.1

hd2Raz said:
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Click to expand...
Click to collapse
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2

horr1blek1tten said:
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I use TWRP and have no problems.
Do a Factory reset, wipe cache, wipe dalvik cache, fix permissions.
If that doesn't work, flash stock and reroot and try again.

I use touch recovery 5.8.4.7 and flashed it with adb. I've flashed almost everything. Cyanogenmod and every other ROM. NEVER had a problem with an instalation. Or even lost IMEI. I think people specifically aren't reading over OP's and figuring out what's safest for their devices and end up with these kind of results. Just my input.
Sent from my SGH-T999 using xda premium

Use mskips tool for our phones. It does everything you can image and then some. I have been using his tools since the HD2 and no issues to date.

The odd string of numbers that flashes upon boot in the status bar sounds like it's just identifying your external sd card. Totally normal.

OK so nothing worked. TWRP did the same thing. Tried diff ROM, same thing. I flashed back to 100% stock, unrooted ROM. Wiped the phone in the standard Android recovery. Then I rooted again, installed TWRP and flashed my ROM of choice and voila. Everything works. Problem solved. Thanks all for the inputs.

Nandroid Restore Help

I'm new to Samsung Android phones, and new to the E4GT, so I need a little help.
I always flash the zip for the EL26 CWM5 recovery like instructed, soooo, here is my issue.
I'm running AOSP and thought I would try CM10 JB, soooo, I flashed into EL26, performed a full nandroid to my Ext SD. I flashed JB and gave it a shot. For issues known to all, I wanted to switch back
So, I went into recovery, flashed the EL26 recovery and rebooted recovery, I then restore the nandroid backup I just made, rebooted, went to the Samsung screen (with the yellow !). After some time, about 20-30 seconds, it goes to a black screen indefinately until I pull the battery.
Any ideas? I have yet to get a nandroid to work on this device. Had no issues at all on my 3D. I'm sure I'm doing something wrong.
TIA,
Tee Jay

You need to flash the AOSP kernel. Well first can you boot into recovery or download mode
Sent from my SPH-D710 using XDA

g_ding84 said:
You need to flash the AOSP kernel. Well first can you boot into recovery or download mode
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Yeah I can get into recovery fine, so I flashed an AOSP kernel and then my wifi didn't work.

Is it not connecting?
Sent from my SPH-D710 using XDA

g_ding84 said:
Is it not connecting?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Nope, won't even turn on. But if I do a full clean flash of the exact ROM, it works fine.

I'm by far no expert but I'd say the kernel is being replaced by the gb recovery kernel when you flash back for your safe recovery.I personally keep a couple various recoveries so I can nandroid backup on the kernel native to the Rom and then the backup will contain the proper kernel.I think I got that right.so....nandroid b4 recovery has been my habit.

Had this issue before, minus the yellow triangle....anytime you're on an aosp rom and do a nand via el26, the nand stores the last kernel used (which is GB el26). After you restore, wipe cache and dalvik and then flash an aosp kernel, probly one from chris41g. Reboot and should he good to go.
Sent from my SPH-D710 using xda app-developers app

dante32278 said:
Had this issue before, minus the yellow triangle....anytime you're on an aosp rom and do a nand via el26, the nand stores the last kernel used (which is GB el26). After you restore, wipe cache and dalvik and then flash an aosp kernel, probly one from chris41g. Reboot and should he good to go.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Right, I tried that with my AOKP backup, I was able to boot. But then my WiFi wasn't working because of something to do with the Kernel I'm assuming

Phone won't boot into recovery?

Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium

eggydrums said:
Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.

EtherealRemnant said:
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
Click to expand...
Click to collapse
With the goo app, I can boot directly into recovery, but my issue is that I get to the Recovery's splash screen, it hangs there for a second and immediately reboots back to system. I'm thinking to get the stock recovery back and try again I'm really not sure what the Hecks going on
Sent from my Nexus 7 using xda premium

Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium

eggydrums said:
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I would highly recommend putting TWRP back on there. The CWM was more for testing... people have reported issues using CWM with certain ROMs. Glad you were able to get CWM on though.

Nothing wrong with CWM.

Aerowinder said:
Nothing wrong with CWM.
Click to expand...
Click to collapse
There are a number of ROMs that do not support CWM so that statement is false. FreeGS3 loses update functionality, for example.
Also, there have been complaints in the case of CWM touch of it being too easy to wipe your entire device.
Not to mention there is no Goo Manager functionality without TWRP as well.
Lots of benefits of TWRP versus CWM. I used CWM for years then had to switch to a modified TWRP for my MAXX and was more than happy when I found out the SGS3 used TWRP as well (although I wish we had the ROM slots like the MAXX though - that was actually cool)

The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.

Aerowinder said:
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Click to expand...
Click to collapse
Don't get me wrong, I've used CWM on many devices for years and even have a premium license for ROM Manager but I've seen a number of ROMs explicitly say not to use CWM, FreeGS3 was just the first that came to mind. I don't flash often because quite frankly, I have no problems with Wicked v8 and see no reason to switch to anything else.
And I am neither careless nor illiterate but I have accidentally borked things using CWM before in the past (it was a modified CWM Touch recovery) and I was not happy.
I think most of the complaints about CWM these days though come from CWM Touch, not regular CWM. Sorry TWRP has issues for you.

OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium

eggydrums said:
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.

EtherealRemnant said:
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
Click to expand...
Click to collapse
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium

eggydrums said:
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.

EtherealRemnant said:
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
Click to expand...
Click to collapse
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium

eggydrums said:
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Did you fix permissions?

EtherealRemnant said:
Did you fix permissions?
Click to expand...
Click to collapse
I tried while I was in twrp, it failed, something about a an error "failed to chmod data/data/ email.apk" (not exactly like that)
Sent from my Nexus 7 using xda premium

No Recovery?

So, I'm having this strange issue where I can't boot into Recovery Mode.
I've been a flashaholic for a little over a year now, but I've never had this problem.
I wanted to get off of Philz because it wasn't wiping my phone correctly while flashing new roms, so I decided to go back to good 'ol TWRP.
I downloaded Goomamager and tried to install, no luck.
So I hopped on my laptop to flash via ODIN, still a no go.
Only after that, it doesn't boot into Recovery at all.
I tried to use ROM Manager to install CWM, because at this point I'm willing to use anything, still a no go.
Anyone got any ideas?
I can get into Download Mode, but no Recovery is sticking.
I try to boot into Recovery, but the device just reboots itself.
Any help is appreciated, thanks.
Sent from my SM-N900T using XDA Premium 4 mobile app

devynbf said:
So, I'm having this strange issue where I can't boot into Recovery Mode.
I've been a flashaholic for a little over a year now, but I've never had this problem.
I wanted to get off of Philz because it wasn't wiping my phone correctly while flashing new roms, so I decided to go back to good 'ol TWRP.
I downloaded Goomamager and tried to install, no luck.
So I hopped on my laptop to flash via ODIN, still a no go.
Only after that, it doesn't boot into Recovery at all.
I tried to use ROM Manager to install CWM, because at this point I'm willing to use anything, still a no go.
Anyone got any ideas?
I can get into Download Mode, but no Recovery is sticking.
I try to boot into Recovery, but the device just reboots itself.
Any help is appreciated, thanks.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Depends on the android version. Also go back to stock with Odin and start all over. Make sure you using right recovery ? As far as philz cwm not wiping properly. Not to sure about that one. A wipe is a generic thing. What do you mean not wiping the right way?
TWEAKED 2.0 ELEMENT V3.0 NOTE 3

BACARDILIMON said:
Depends on the android version. Also go back to stock with Odin and start all over. Make sure you using right recovery ? As far as philz cwm not wiping properly. Not to sure about that one. A wipe is a generic thing. What do you mean not wiping the right way?
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
Click to expand...
Click to collapse
Alright, I was gonna do that tomorrow on my day off, since the device seems to function properly mostly.
With Philz, I mean that I would Factory Reset, Wipe Data and "Wipe for new ROM", but when I would flash the new ROM, it would still have everything I had before on the device's SD memory, (which to me, is not a clean flash).
I am on Temasek's 4.4 CM11 v50.
I've been using this ROM for a long time and I've never had this problem in the past.
Sent from my SM-N900T using XDA Premium 4 mobile app

devynbf said:
Alright, I was gonna do that tomorrow on my day off, since the device seems to function properly mostly.
With Philz, I mean that I would Factory Reset, Wipe Data and "Wipe for new ROM", but when I would flash the new ROM, it would still have everything I had before on the device's SD memory, (which to me, is not a clean flash).
I am on Temasek's 4.4 CM11 v50.
I've been using this ROM for a long time and I've never had this problem in the past.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I am not familiar with asop so I don't know what to say. But best bet is Odin back then flash twrp as you would like
TWEAKED 2.0 ELEMENT V3.0 NOTE 3

just connect fastboot
fastboot flash recovery (recoveryname).img

Hi man,i also have a sm n900t and im having this problem to,tried with every kind of recovery but no1 made it possible to boot into recovery,did you find an answer?