Develop Bugs

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.

my phone crapping..." com.android.phone has stopped" - tried everything!

Background - I rooted and installed CWM recovery through Toolkit. Realized every time I "Factory Reset" in CWM recovery it would complete wipe my internal storage. Ok so I installed TWRP using the tookit. Then installed other roms and notice EVERY rom I've installed errors right after boot-up with "Unfortunately, the process com.android.phone has stopped". Upgrading to latest TWRP didn't fix it.
I've tried to wipe everything. Even tried format internal storage. Flash multiple roms again and still same error.
I'm thinking it was CWM "Factory Reset" wiping all my internal storage could of messed up my internals... maybe the file format? Something else I can try?
Phone is still usable, just every time it starts up - error shows up twice. It might pop up again once in a while when i'm using it.
BTW when I was "Factory Reset" in CWM it always made my phone "Activate with sprint" again... like it was a brand new phone.

Try odining back to stock then redo root and ROM flashing and see if that helps.
Sent from my SPH-L900 using Tapatalk 2

slick_rick said:
Try odining back to stock then redo root and ROM flashing and see if that helps.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Should I 1st flash stock recovery then odining back to stock ?

mxl180 said:
Should I 1st flash stock recovery then odining back to stock ?
Click to expand...
Click to collapse
no, if you ODIN back to the stock unrooted with the file from -viperboy-'s thread it will change your recovery as well.

t3project said:
no, if you ODIN back to the stock unrooted with the file from -viperboy-'s thread it will change your recovery as well.
Click to expand...
Click to collapse
holy crap. Ran Viper's ODIN instructions back to stock now. Error show up again.

mxl180 said:
holy crap. Ran Viper's ODIN instructions back to stock now. Error show up again.
Click to expand...
Click to collapse
Does this set the flash timer to ZERO so I can return to sprint?

mxl180 said:
Does this set the flash timer to ZERO so I can return to sprint?
Click to expand...
Click to collapse
No....but flash counter should not matter.
Sent from my SPH-L900 using xda app-developers app

00mred00 said:
No....but flash counter should not matter.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Well reverting back to CWM fixes the process error, but it also completely wipes the device in recovery. So every time I wipe it needs to "hands-free activate" w/ sprint and lose all my internal storage. Oh well, no process errors!

[Q] Don't Understand

Hi all. I'm going absolutely crazy over here. I have an i747 and I rooted it, no problem. The problem that I am having is that I'm currently running 4.1.2 and for the life of me, cannot figure out how to get it to 4.2. I've tried installing CM10, but every time I try and flash it in CWM, I get a E: Error in /emmc/cm10.zip (Status 7). I've tried installing other 4.2 ROMs like Paranoid Android etc, but get the same/similar error. I can flash other custom ROMs, like Alliance and such. I'm sure I'm over thinking this and just need a fresh set of eyes on the issue and a point in the right direction here. Your help is much appreciated.

What version of cwm are you running?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta

jon_yarbrough said:
Hi all. I'm going absolutely crazy over here. I have an i747 and I rooted it, no problem. The problem that I am having is that I'm currently running 4.1.2 and for the life of me, cannot figure out how to get it to 4.2. I've tried installing CM10, but every time I try and flash it in CWM, I get a E: Error in /emmc/cm10.zip (Status 7). I've tried installing other 4.2 ROMs like Paranoid Android etc, but get the same/similar error. I can flash other custom ROMs, like Alliance and such. I'm sure I'm over thinking this and just need a fresh set of eyes on the issue and a point in the right direction here. Your help is much appreciated.
Click to expand...
Click to collapse
Status 7 is an out of date recovery, so make sure that's updated.
Also the newest cm10 and aokp and Pac man need updated bootleggers. Check the cm10 thread for the links to the Odin files.
http://forum.xda-developers.com/showthread.php?p=41535366
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I'm running cwm 5.5.0.4
Sent from my SAMSUNG-SGH-I747 using xda premium

jon_yarbrough said:
I'm running cwm 5.5.0.4
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Read up on what the status 7 error means. Also, I would recommend switching from CWM to TWRP.

jon_yarbrough said:
I'm running cwm 5.5.0.4
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Cwm is up to 6.0.2.8
Just needs an update.
http://forum.xda-developers.com/showthread.php?p=38962585
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Cwm is actually sitting currently at 6.0.3.1. Here is the latest cwm flashable zip: http://forum.xda-developers.com/attachment.php?attachmentid=1888710&d=1366136727
Flash this in cwm, go to advanced, select reboot recovery. Once back in, make a new backup.
Before you flash a 4.2 rom from 4.1, wipe everything. Save everything you want to an sd card or your PC. Place your desired rom and gapps on a micro sd card. Wipe data, wipe cache and dalvik. Format /system and /data. Flash rom and gapps.

xBeerdroiDx said:
Cwm is actually sitting currently at 6.0.3.1. Here is the latest cwm flashable zip: http://forum.xda-developers.com/attachment.php?attachmentid=1888710&d=1366136727
Flash this in cwm, go to advanced, select reboot recovery. Once back in, make a new backup.
Before you flash a 4.2 rom from 4.1, wipe everything. Save everything you want to an sd card or your PC. Place your desired rom and gapps on a micro sd card. Wipe data, wipe cache and dalvik. Format /system and /data. Flash rom and gapps.
Click to expand...
Click to collapse
Lol I did the same thing last time.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

KorGuy123 said:
Lol I did the same thing last time.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hahaha. I thought that was you. Cheers, KorGuy!

Thanks all. I just went into ROM Manager and updated CWM to the current version of 6.0.3 and it worked like a freakin' charm. I will be sure to hit THANKS for you all. Thanks again.

xBeerdroiDx said:
Cwm is actually sitting currently at 6.0.3.1. Here is the latest cwm flashable zip: http://forum.xda-developers.com/attachment.php?attachmentid=1888710&d=1366136727
Flash this in cwm, go to advanced, select reboot recovery. Once back in, make a new backup.
Before you flash a 4.2 rom from 4.1, wipe everything. Save everything you want to an sd card or your PC. Place your desired rom and gapps on a micro sd card. Wipe data, wipe cache and dalvik. Format /system and /data. Flash rom and gapps.
Click to expand...
Click to collapse
It's actually 6.0.3.2 now, but you have to build it yourself to get it as the latest released version is still 6.0.3.1.
https://github.com/CyanogenMod/andr...mmit/6f8d24d326258f2293436c50caca1c50eccab329

klin1344 said:
It's actually 6.0.3.2 now, but you have to build it yourself to get it as the latest released version is still 6.0.3.1.
https://github.com/CyanogenMod/andr...mmit/6f8d24d326258f2293436c50caca1c50eccab329
Click to expand...
Click to collapse
:laugh:
It's not a release until it's released.
Cheers, klin

[Q] N7 bootlooping on custom rom?

Okay, so I bought the n7 v2, went home, unlocked the boot loader, and rooted it. I've tried to flash versions of vanir I built my self, the betas that are posted here on the forums, and I also tried carbon ROM. Every time I flash a ROM, my device bootloops, so I just hold power + vol down to get to boot loader mode so I can boot into recovery. Any fix for this? I've tried flashing a stock IMG and re rooting to. No luck.

Bump

frap129 said:
Bump
Click to expand...
Click to collapse
Did you even wipe, and perform a factory reset before flashing a ROM?
Sent from my Nexus 7 using xda app-developers app

TheMrcool212 said:
Did you even wipe, and perform a factory reset before flashing a ROM?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I wiped data, cache, and dalvik every single time.

Bump? Anyone?

try redownloading the rom and install, could of been a bad download
Sent from my Nexus 7 using xda app-developers app

shortyboy said:
try redownloading the rom and install, could of been a bad download
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
With four different ROMs, 2 transfered via adb and 2 from different download hosts, I doubt its a bad download.

frap129 said:
With four different ROMs, 2 transfered via adb and 2 from different download hosts, I doubt its a bad download.
Click to expand...
Click to collapse
you should've mentioned that in your original post. id try to reflash to complete stock and start all over. it seems like something you modified in the first rom you've flash isn't being removed from another flash,so going back to stock,you can be sure everything is working first.hope this helps

shortyboy said:
you should've mentioned that in your original post. id try to reflash to complete stock and start all over. it seems like something you modified in the first rom you've flash isn't being removed from another flash,so going back to stock,you can be sure everything is working first.hope this helps
Click to expand...
Click to collapse
I did mention that in the original post, as well as the fact that ive flashed stock a few times already.

Did you boot into the tablet after unlocking the bootloader but before rooting it? If not, try formatting data (not factory resetting) in recovery. I had the same experience and my sdcard never got populated with the default folders and files, remaining at 0MB. Apparently, symptoms of this problem include being unable to factory reset from recovery, being stuck on the splash screen, and having TWRP demand a password.

bananagranola said:
Did you boot into the tablet after unlocking the bootloader but before rooting it? If not, try formatting data (not factory resetting) in recovery. I had the same experience and my sdcard never got populated with the default folders and files, remaining at 0MB. Apparently, symptoms of this problem include being unable to factory reset from recovery, being stuck on the splash screen, and having TWRP demand a password.
Click to expand...
Click to collapse
I'll try that, maybe its because I restore my data after I wipe it that this happens. Another thing I've found is that after I flash and the restore my system partition that I backed up, su says that no subject binary was found, even though I've flashed it a million times. And some root apps don't work because it says no binary is found.

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?