Develop Bugs

A Warning About Rooted Stock! BACKUP YOUR DATA

I used the internarional toolkit v1.0 to root my phone the day after T-Mobile released it, and had minor stability issues frequently; if an app locked up, a battery pull was required to fix it, sometime "system" would request superuser access 8-10 times in a row before the phone would reboot itself, stuff like that. I wrote it off as something that I would worry about when I had more time to switch to a new ROM. Boy, do I regret waiting.
My phone locked up, like normal, and I performed a battery pull. When I replaced it and booted the device, I was greeted by a holo-style popup saying "Android is updating" or something to that effect. It would then load my lockscreen and respond for about 10 seconds before completely freezing again.
A full wipe fixed this, so I took this opportunity to switch to a different ROM. I lost my SMS' and all app data aside from the few Titanium backups I had. I don't know if the OS just borked itself, or if it somehow tried to download an OTA update, or what.
But if you experience these issues, or used the original international version of the toolkit with options 4-3-1, then you might want to switch to a custom ROM before it's too late.
Heeeeeed my waaaaarrrrnnniiiiinnnngggg...
EDIT: I guess I wasn't terribly clear due to my wording and being tired. Yes, I know doing a full wipe and flashing a ROM will cause me to lose my data. I was just saying that due to the fact that the only way to fix the device was a full wipe, I lost my data. All I'm saying really is to watch out for these issues or else you'll be in the same boat I was with no backups to restore from.

I don't understand. If you switch your ROM you're going to lose previous data unless you back it up. You do a backup before anything.
Sent from my SGH-T889 using Tapatalk 2

AllanJH said:
A full wipe fixed this, so I took this opportunity to switch to a different ROM. I lost my SMS' and all app data..
Click to expand...
Click to collapse
Confused too - of course you're going to lose your data after a full wipe.
Sent from my SGH-T889 using Tapatalk 2

EmceeGeek said:
I don't understand. If you switch your ROM you're going to lose previous data unless you back it up. You do a backup before anything.
Click to expand...
Click to collapse
decalex said:
Confused too - of course you're going to lose your data after a full wipe.
Click to expand...
Click to collapse
I added a clarification to my first post. All I was saying was that if anyone else is having issues similar to mine, back up your data before it's too late, like it was for me.

No problems here. I rooted my SGN2 with v1.0.0 and just de-bloated all tmobile apps with Titanium since first day release and never had an issue. Of course, some apps don't work with the SGN2, but it just tries to start and then after a few seconds it comes back, but this probably has more to do with the apps. This also happens with custom roms too.
I'm now just using rooted stock debloated tmobile rom. Seems to run the best without any issues.

might be off topic but i noticed when i tried to go back to factory with odin it flashed the rom and i lost root but it did not erase data at all. is this normal when using odin? or do i need the PIT file to go 100% stock?

I rooted threw odin. Whats the difference threw toolkits?
Sent from my SGH-T889 using xda premium

whats with all of these 'warning" threads lately? is this user error or a legitimate fault of the device because at this point im ready to swap this out for a gs3.

fix-this! said:
whats with all of these 'warning" threads lately? is this user error or a legitimate fault of the device because at this point im ready to swap this out for a gs3.
Click to expand...
Click to collapse
Its people taking an isolated incident blowing it out of proportion the phones fine I rooted that way and have had no issues disregard this loons rant
Sent from my SGH-T889 using xda app-developers app

fix-this! said:
whats with all of these 'warning" threads lately? is this user error or a legitimate fault of the device because at this point im ready to swap this out for a gs3.
Click to expand...
Click to collapse
You must not know the gs3 is where all this came from
Sent from my SGH-T889 using Xparent Blue Tapatalk 2

deeznutz1977 said:
You must not know the gs3 is where all this came from
Sent from my SGH-T889 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I had a gs3 on verizon and never had any issues after i backed up my efs with terminal manager. Flashed tons of roms too including aosp.

fix-this! said:
I had a gs3 on verizon and never had any issues after i backed up my efs with terminal manager. Flashed tons of roms too including aosp.
Click to expand...
Click to collapse
Efs is the only thing that worry me with Galaxy Note 2. Several methods of backing up. But seems that it is unclear if any method is really backing up efs within Galaxy Note 2. There seems to be differences between GS3 efs and GN2 efs.
No real solid clear evidence or clarification which and if any efs backup method actually backs up Galaxy Note 2 efs. And no real solid clarification on how to restore Galaxy Note 2 efs. And no solid clear evidence or clarification that if the Galaxy Note 2 efs restore method actually restores the efs correctly.

Won't boot past HTC screen

So the last few times I've flashed some roms I've noticed the phone would get hung up on the clear cache and wipe option in CWM. Eventually it would (maybe 5 mins) do it's thing and be fine. As of today, no bueno. All I can do is go into CWM. It won't do anything without locking up after that point. If I just do a regular reboot, it's stuck on the HTC screen. Now I get the attached error messages in CWM.
UPDATE- It's currently acting like it is restoring one of my backups, they usually take an hour.

aviris said:
So the last few times I've flashed some roms I've noticed the phone would get hung up on the clear cache and wipe option in CWM. Eventually it would (maybe 5 mins) do it's thing and be fine. As of today, no bueno. All I can do is go into CWM. It won't do anything without locking up after that point. If I just do a regular reboot, it's stuck on the HTC screen. Now I get the attached error messages in CWM.
UPDATE- It's currently acting like it is restoring one of my backups, they usually take an hour.
Click to expand...
Click to collapse
If it takes an hour to restore a back up you should maybe look at TWRP...5-7 minutes tops. I'm not sure it's always like that with CWM, but it maybe be something for you to check out.
Sent from my HTC6500LVW using Tapatalk

Twrp is definitley much faster at backing up and restoring. I would try reflashing cwm or flash twrp and see if that solves the issue.

Happen to have a link? I'm a creature of habit and really hate changing things but CWM has really not been doing well lately.

aviris said:
Happen to have a link? I'm a creature of habit and really hate changing things but CWM has really not been doing well lately.
Click to expand...
Click to collapse
Someone else posted about the same issue as yours in the cwm thread...
Try this..
http://forum.xda-developers.com/showthread.php?t=2416431
Sent from my Nexus 7 using Tapatalk

AT&T Samsung Galaxy Note II Won't Boot Into Recovery

Ok so over the last couple of days I tried getting a little too flash happy and thought I completely ruined my device. I could get into download mode, but not into recovery. I've tried flashing the files in Odin listed here http://forum.xda-developers.com/showthread.php?t=2584533 and usually that works. This time it didn't and at first I didn't get too bothered/noided because I thought I may have done something wrong. Fast forward to now and I was able to get recovery back on my phone and reinstall CleanROM Ace 5.0 which is a personal fave of mine. I got it to work using the instructions and files found here http://forum.xda-developers.com/showthread.php?t=2573576 and I used a very old version of Odin to do this. The one I used was Odin3 v1.85 but I also have v3.07 and 3.09.
Now I will walk you through what I did that caused this dilemma, aka doing the absolute most :silly:
It started out as me wanting to test out 2 different ROMS (eZKAT Beta found here http://forum.xda-developers.com/showthread.php?t=2747733 and Ditto Note 3 found here http://forum.xda-developers.com/showthread.php?t=2541860). My smart @$$ (sarcasm of course) didn't do a full wipe internally when flashing between the two. Reason being, I honestly just started doing that and never ran into an issue until now because of not doing it. I recently got an S5 and my 32gb sd card is in that phone and I found an 8gb sd card in an old G1 I had. So because I had ROM files and TitaniumBackup files on the sd card, I was using internal storage to house the two test ROM's. Bad idea I now know. I'm so thankful my Note II is now just a backup along with my iPhone 4S but still, it's nice to be able to experiment with a test android phone and know your primary is fully functional. Plus, all the apps I bought and things I got used to using that are strictly for rooted devices...anyway back on topic.
I flashed eZKAT and got that fully booted, even installed xposed framework and wanam both worked. That ROM is not on hold but development is currently. I'm fine with that, what was put out for us to use does work. eZdubzitmk4 does great work, and has responded to PM's from me seeking assistance in the past. So since I'm somewhat familiar with his work, I didn't think twice about trying it out. My curiosity kicked in and I thought ok, let's try a different Note 3 ROM because I've successfully flashed and used Sky Note Air (both editions) in the past and seanzscreams is another developer who does great work. I'm not saying nor implying no one else does, I'm just shouting out two developers.
Something went wrong between me switching from eZKAT to Ditto Note 3 and the only thing I can recall not doing that likely enhanced my issue was not wiping internally. I tried to flash CWM and Philz Recovery as suggested here http://forum.xda-developers.com/showthread.php?t=2541860&page=429 and I thought that would fix the issue. What actually happened was after flashing in Odin, the phone would attempt to boot into recovery and all I'd see was a navigation bar at the bottom with 4 arrows but no text and the screen would immediately fade to black and reboot. I could not get into recovery at all. I saw the Samsung Galaxy Note II splash screen repeatedly. I left it off the charger all day, and it repeated that same process the entire time. I tried using KIES and KIES3 but neither worked. I almost got something to work in KIES3 but right before the end, it failed and my phone said unsupported version in red text. I did a few Google searches at work which did help point me in the right direction.
I tried flashing stuff in the PDA slot as well as the Bootloader slot, but it didn't matter everything was the same result. My thought process was try it and see, all that can go wrong is it not boot into download mode . I prayed on it last night then did another Google search tonight when I got home from work, after attempting all that stuff again. This time I did a search for note 2 will not boot into recovery and I found this http://forum.xda-developers.com/showthread.php?t=2573576. TWRP was successfully flashed and I was able to flash CleanROM Ace 5.0 again now I'm happy ...but also EXTREMELY hesitant to flash anything else at this point. I'm just glad I no longer have a $371 paper weight ($321 for the phone and $50 for the AT&T flap cover case with attached back). I did state that if and when I fixed my phone I would create a thread about what I did and what worked for me. Hopefully this can be of use to someone else, because I know I'm not the only who has faced this issue. I also was all over Google with generic searches because all I knew was what was happening, not the technical/official name for what it was if that makes sense .
Here's a video showing what I'm describing.

I always use cwm. Just been more stable for me.
Not exactly sure what happened here tho.. Never seen that before.
I'm glad you're up and running again. I honestly would just wait for the dn3 update to flash a kit kat rom
Sent from my NoteII

I prefer CWM myself as well. I've been using it since my HTC Inspire 4G. After I got my Note II to boot and flashed CleanROM, I transferred a backup I had made in the past onto my sd card. I read before that there's an issue with TWRP and/or Philz Touch when trying to restore a CWM backup. To avoid further issues, I installed CWM from the play store, reflashed CWM Touch. Then I deleted the text from the md5 file in root explorer text editor, rebooted into recovery cleared everything then restored the backup. No issues since.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app

eZdubzitmk4 said:
I always use cwm. Just been more stable for me.
Not exactly sure what happened here tho.. Never seen that before.
I'm glad you're up and running again. I honestly would just wait for the dn3 update to flash a kit kat rom
Sent from my NoteII
Click to expand...
Click to collapse
I added a video to the thread so people can see what I'm describing.

Assassyn said:
I added a video to the thread so people can see what I'm describing.
Click to expand...
Click to collapse
Happened to me before. Since I didn't have a rom installed I couldn't boot to android so I had to use Odin..Flash twrp. Let it boot into recovery. Then pull battery and go back into download mode and use odin again to flash cwm then cwm worked fine and didn't just restart.
Since you can boot into android you can actually just download Recovery Tools from playstore to install twrp then cwm. I recommend the odin way tho
Sent from my NoteII

Will definitely look into it!
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app

I had the same issue but my phone won't even boot up...can't get into recovery or download mode...changed batteries and still no go.

allaidback said:
I had the same issue but my phone won't even boot up...can't get into recovery or download mode...changed batteries and still no go.
Click to expand...
Click to collapse
Are these new batteries?

one was new...I tried 2 others. Took to sprint and they are replacing the phone. This will be my 3rd note 4.

allaidback said:
one was new...I tried 2 others. Took to sprint and they are replacing the phone. This will be my 3rd note 4.
Click to expand...
Click to collapse
Wow, sorry you've had such trouble. Have you had any issues since your replacement? I recently shattered the screen on my S5 trying an at home wifi/bluetooth fix that actually did work but I pressed too hard on the device so my Note II is now my primary again. Holding off for a Note 5 unless I can get a 128 gb micro sd card, then I'll get a Note 4.

Anyone restored a back up using TWRP?

In past devices I've owned lately (can remember which cuz there's been A LOT) I've noticed that at times, when i restore a back up i suddenly have bugs that weren't there b4. I'm not saying it's common but i HAVE seen it. I wanna try installing some mods my phone but b4 i do I'm gonna create a back up. Im just hoping that if i do have too restore a back up that it's not gonna suddenly create problems. My set up is dam near perfect right now. So I'm just putting some feelers out here: has anyone restored a back up using TWRP? And if so, was everything running perfectly afterwards?
Thanks.

Never had an issue.
Sent from my LG-D851 using Tapatalk

If I restore a backup I usually do a factory reset first and foremost everything, that way its restoring to a clean space.
Sent from my LG-D851

Just did it today. No problems at all.

I have noticed stuff like google play services needing to be updated even though it was just updated and smart cards stop working. Never anything major though and it only happens every now and then.

Skizzy034 said:
If I restore a backup I usually do a factory reset first and foremost everything, that way its restoring to a clean space.
Sent from my LG-D851
Click to expand...
Click to collapse
Yeah, i do too. I think it was a while back on the note 3 that even when wiping fully you'd still get issues. Just glad to see others aren't having problems with this device. Thanks.

pathtologos said:
Yeah, i do too. I think it was a while back on the note 3 that even when wiping fully you'd still get issues. Just glad to see others aren't having problems with this device. Thanks.
Click to expand...
Click to collapse
That's because TWRP was horribly broken on the Note 3 for a long time. It wasn't restoring SELinux contexts properly so you'd wind up with a non-functional device (e.g. every app FC'd on launch, device would bootloop, etc.). It was also corrupting exFAT-formatted SD cards due to a buggy FUSE implementation. (I helped bigbiff troubleshoot and fix all of it over the past year.)
I had to restore contexts manually via adb after a TWRP restore before rebooting into Android. They only fixed that in the 2.7.1.0 release IIRC.

I haven't had a single problem. Restores perfectly. I do wipe like 3 times first though.

Constant Rebooting

So my friends Boss' son tried to be all "l33t h4x3r" and mess with his S6(sm-g920p). First he ruined his EFS section of the phone, the Baseband is Unknown, no IMEI number, Software Version is Unknown, and his radio wasn't working. I think he then tried to do some crazy **** in ODIN, "No Clue he doesn't remember". Well i've never ran into a constant reboot issue with any Android phones i've owned. I've had bootloops but this is throwing me for a loop. I've tried:
Loading TWRP wiping everything and trying a Custom ROM
Using Odin to Recover back to Stock
Honestly im not sure whats up anymore or if his phone is even fixable at this time.
Link to Probs: http5://youtu.be/QVLgYF_7tGU

Hi, you certainly have a challenge there. It sounds like you need to restore both the partitions and the stock OS.
If the phone is a 32 GB model, please see the whole thread at http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325
There is a PIT file linked at post 16, instructions for using it at post 22. Also a link for the latest stock TAR file.
Again, this would be for 32 GB model, but you want to flash first the PIT and then the TAR.

I think I may have done that already too but I'll look again once in home and see if maybe I did it in the wrong order. Thanks for the quick reply friend. ?

Well i did as instructed but Baseband is still unknown and it is still rebooting over and over :/

jbowman21 said:
Well i did as instructed but Baseband is still unknown and it is still rebooting over and over :/
Click to expand...
Click to collapse
If he messed up the efs partition, like it's empty, without a backup. I'm pretty sure the phone is done.
Sent from my SM-G900P using Tapatalk

elesbb said:
If he messed up the efs partition, like it's empty, without a backup. I'm pretty sure the phone is done.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I recommend he brings it to Sprint, after they "diagnose" it and declear its broken they should be able to replace it. Just make sure its as close to stock as possible that way it does not seem rooted.

1619415 said:
I recommend he brings it to Sprint, after they "diagnose" it and declear its broken they should be able to replace it. Just make sure its as close to stock as possible that way it does not seem rooted.
Click to expand...
Click to collapse
That is about the only option left. There are other options to restore the efs (pretty much rebuild it from scratch) but that is not something an every day user can do. I had an efs issue on my S4. I was tinkering with things I shouldn't have, forget exactly what I was doing, it was on T-Mobile so I think I was trying to remove the data cap (was on prepaid). Was pretty much in the same boat as OP but was able to completely from scratch rebuild the stuff that belongs in the efs directory. Some stuff I never restored but didn't seem to affect the device.

elesbb said:
That is about the only option left. There are other options to restore the efs (pretty much rebuild it from scratch) but that is not something an every day user can do. I had an efs issue on my S4. I was tinkering with things I shouldn't have, forget exactly what I was doing, it was on T-Mobile so I think I was trying to remove the data cap (was on prepaid). Was pretty much in the same boat as OP but was able to completely from scratch rebuild the stuff that belongs in the efs directory. Some stuff I never restored but didn't seem to affect the device.
Click to expand...
Click to collapse
Huh, if you remember, write a guide that way you can help people.

1619415 said:
Huh, if you remember, write a guide that way you can help people.
Click to expand...
Click to collapse
This was many many years ago. What saved me was the fact that Notepad++ keeps a copy of the file you have open even when you close the program. I just had to remember what things needed to be reverted back and the edits undone. I guess I didn't really rebuild it from scratch lol.

elesbb said:
This was many many years ago. What saved me was the fact that Notepad++ keeps a copy of the file you have open even when you close the program. I just had to remember what things needed to be reverted back and the edits undone. I guess I didn't really rebuild it from scratch lol.
Click to expand...
Click to collapse
Lol

1619415 said:
Lol
Click to expand...
Click to collapse
Yeah sadly I have no idea how the efs is populated. The second instance I get a new phone, dd is done on the efs partition and created into a .img file.

jbowman21 said:
So my friends Boss' son tried to be all "l33t h4x3r" and mess with his S6(sm-g920p). First he ruined his EFS section of the phone, the Baseband is Unknown, no IMEI number, Software Version is Unknown, and his radio wasn't working. I think he then tried to do some crazy **** in ODIN, "No Clue he doesn't remember". Well i've never ran into a constant reboot issue with any Android phones i've owned. I've had bootloops but this is throwing me for a loop. I've tried:
Loading TWRP wiping everything and trying a Custom ROM
Using Odin to Recover back to Stock
Honestly im not sure whats up anymore or if his phone is even fixable at this time.
Link to Probs: http5://youtu.be/QVLgYF_7tGU
Click to expand...
Click to collapse
Koop's firmware didn't work with my phone either. This version of it fixed mine for some reason. Try flashing it to yours
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip

Now i got same issue i accidently restored efs and ah man ive tried every thing it reboots after 2 or 3 mins no matter what rom back up i have and i have efs and radio with all my back ups ive restored it also no luck. Guess im going to the sprint store tomorrow even after i flashed stock 6.0.1 i can get to about half way through wifi setup before it reboots no matter what 2-3 minutes phone reboots unless in twrp

Still no luck becareful and dont try to restore efs i suppose in twrp. Your phone may never stop rebooting ive flashed 2 different 6.0.1 builds one was the revo other was from sammobil both @koop1955 has them PB6 6.0.1 odin doesnt fix this.

YOYOYO
Well wtf or omg it completely died left it for a day. Now its working so far it hasnt rebooted in 30 mins LOL but dude sucks going to a phone with kitkat after using marshmallow and one of the fastest phones made for awhile. I did pull the sim card out and try it in a old boost maybe that reset something idk its working though.My problems were Rebooting constantly after 2-3 mins no matter what rom i had even stock.
---------- Post added at 12:31 PM ---------- Previous post was at 12:11 PM ----------
Saafir said:
Backed up my EFS before ever even rooting. Stuck that bad boy in Dropbox for safety. *pats self on back*
Last one of these topics I seen, end result was JTAG.
Click to expand...
Click to collapse
BEcareful if u restore that efs. i backed up too but once in twrp. Now all i did was check restore efs by accident just tried restoring a renegade rom system,boot, and data. Tell you what i wont be rushing through crap and am fine with stock for awhile. Probably will still take the replacement when it comes its white the black one i got is too blue.

Saafir said:
I've got a raw partition backup as well as one through TWRP. If you check md5/sha hashes for data integrity, and only install software instances specific to your device, aside from manually monkeyin around
Hey needless to say im researching full partition backups did you use a app by wanam partitions back up and restore? Or just simple adb commands. Last used adb on a moto e 2nd with success on unlocking. Once i got a new harddrive haven't needed it.
Click to expand...
Click to collapse

Theres similar issues happening on sprint note 5s as well and has a couple threads currently speaking about this problem. Strange strange. It happened to me after updating to mm and then rooting.

Well i did try the note rom right before and when i did hit restore efs it after wiping system data boot from moar MM rom phone rebooted for days then after few resets and odin flashes i let it die then a day later it worked.

Correct but have always preferred the 925p roms.

Well i helped another with the rebooting issue on any rom.
He tried everything then but let it die after battery died plug it in and bingo his worked to
IF CONSTANT REBOOTING.
LET THE BATTERY COMPLETLY DRAIN.
AFTER FLASHING STOCK.