Database Develop

Why did you downgrade?

Okay, so after soak test version of lollipop rolled out, we have seen lots of Moto Es being hard bricked by people including me while they tried to downgrade back to KitKat. So, this question is for all those people who did that; I am asking this out of curiosity: Why did you downgrade from lollipop to Kitkat in the first place? What was your reason?
I tried to downgrade because Link2SD was not working on lollipop in the way it is supposed to work (mount scripts not working at all, hence 2nd partition not getting mounted automatically at boot thus loosing all apps linked to SD card after rebooting). This "linking" thing was the primary reason I decided to root my phone. I wanted loads of apps on my phone which is impossible to have without Link2SD or similar apps like Mount2SD (which don't work either because Moto E's lollipop simply wouldn't run any init.d scripts during boot thus breaking all such applications). I don't plan to upgrade to lollipop unless this problem is solved because Moto E is nothing without Link2SD with its mere 2.1 GB of internal free space it offers. It vanishes within a blink of an eye. I had 250+ apps on Moto E running smoothly on Kitkat 4.4.4 before it died.

Cannot remove system apps with a rooted S5

I have several problems. I am still on the stock ROM. I updated with Kies to Android 5.0. I then rooted the phone. I have not flashed a custom ROM yet. I have tried to remove system apps with my old favorite root app removers and they simply don't work. They say successful but the apps come right back. I have backed up my phone with the standard recovery apps, TWRP, Philz touch and ROM Manager. I carefully chose backup to the SD card but all of them also save the backup to the phone memory also. Those backups eat the phone memory and I cannot remove them. Removal fails. Files are write protected. I was able to remove the backups by using the factory reset. That is a real pain. I'm now afraid to use any recovery now. With only 16 GB of memory, I choose to use the SD card. Is Android 5.0 causing these problems? Am I stuck with the stock Android 5.0? Kies warned me that I can't go backwards. I had none of these problems with the Samsung S3 and S4 with custom ROMs. I might add that I used a no bloat program with the S5 and Android 5.0. It bricked my phone. It was quite difficult to get it working again with the stock Android ROM. I wish I not bought the S5 or updated to Android 5.0.
My phone is a G900F with Lollypop 5.0

3545alg said:
I have several problems. I am still on the stock ROM. I updated with Kies to Android 5.0. I then rooted the phone. I have not flashed a custom ROM yet. I have tried to remove system apps with my old favorite root app removers and they simply don't work. They say successful but the apps come right back. I have backed up my phone with the standard recovery apps, TWRP, Philz touch and ROM Manager. I carefully chose backup to the SD card but all of them also save the backup to the phone memory also. Those backups eat the phone memory and I cannot remove them. Removal fails. Files are write protected. I was able to remove the backups by using the factory reset. That is a real pain. I'm now afraid to use any recovery now. With only 16 GB of memory, I choose to use the SD card. Is Android 5.0 causing these problems? Am I stuck with the stock Android 5.0? Kies warned me that I can't go backwards. I had none of these problems with the Samsung S3 and S4 with custom ROMs. I might add that I used a no bloat program with the S5 and Android 5.0. It bricked my phone. It was quite difficult to get it working again with the stock Android ROM. I wish I not bought the S5 or updated to Android 5.0.
My phone is a G900F with Lollypop 5.0
Click to expand...
Click to collapse
You stated you have a G900F so you need to post in the international threads this is for G900A devices

OPOfreak said:
You stated you have a G900F so you need to post in the international threads this is for G900A devices
Click to expand...
Click to collapse
The thread title is; "AT&T Galaxy S5 Q&A, Help & Troubleshooting". I have an S5. I don't see an International thread.

3545alg said:
The thread title is; "AT&T Galaxy S5 Q&A, Help & Troubleshooting". I have an S5. I don't see an International thread.
Click to expand...
Click to collapse
That's right it's for the G900A
Go here
http://forum.xda-developers.com/showthread.php?t=2700073

OPOfreak said:
That's right it's for the G900A
Go here
http://forum.xda-developers.com/showthread.php?t=2700073
Click to expand...
Click to collapse
Moved.

[Q] Backup ROM and Root Device Assistance

Hello So I have a brand new, unlocked, Samsung Note 3 (SN-900A - AT&T variety) that I bought from Best Buy. In the next few days I'll be switching to T-Mobile (no comments on carrier switch please), but since the GSM phone is unlocked I can use it on T-Mobile's network
Here is the current status of my phone:
Used Odin to flash back to stock AT&T 4.4.2 ROM from installed NL1 4.4.4
Rooted device on 4.4.2 and then upgraded to rooted/stock AT&T ROM 4.4.4 using SuperSU, BusyBox, and SafeStrap as explained here, here, and here (did not update to Lollipop)
Used Root App VIP to manually disable AT&T bloatware now that I have the phone rooted on 4.4.4
So in its current form my phone is rooted on 4.4.4 and working pretty well. I'm happy thus far and don't want to get too greedy since it works.
However I have a few questions about how to backup my current ROM and about geeting some better understanding about the root and ROM process. I would be quite appreciative if someone could assist me with the answers please!
It appears the original Dev of Safestrap (the core app at the heart of rooting and upgrading the Note 3 in my process) has moved onto greener pastures. Since SafeStrap does not work on 4.4.4 (can't boot into recovery or do backups), what is the replacement tool/utility? Should I use Odin for everything? OdinMobile? CWM? TWRP? FlashFire? I've read a bunch of threads on the differences and I'm having a hard time making heads or tails of it all. The main thing I want to be able to do now is backup my current ROM like you could previously with Safestrap, and update to a new ROM if I so choose.
I never wanted the bloatware - do you think I flashed the wrong ROM? Should I have used a stock ASOP ROM if I didn't want bloatware or is this not possible on the 900A?
Ironically if I had to have bloatware I would have preferred to have T-Mobile's since I will be on their network. Could I have put a T-Mobile ROM image on an AT&T variant of the phone? (just curious)
I used a AT&T stock ROM apparently from those links I posted which propogated the bloatware to 4.4.4, however at least I'm rooted. I believe this was all done to not disturb the KNOX flag. I have a warranty from BestBuy I would like to keep (1 year), but I can't go to AT&T for warranty service (they are not my carrier) and I didn't buy the phone from T-mobile either, so is the warranty worth anything anyway?
I keep reading that the AT&T variant of Note 3 has a 'locked bootloader' and that's what's with going to all the trouble with SafeStarp was about. Essentially it loads an alternate image/ROM not disturbing the stock one so that the KNOX flag is never triggered. Is there a way to unlock the bootloader on this phone or should I even care?
I'm early enough in this process that if I went down the wrong path I could do something different. Any or all help/assistance is greatly appreciated!

atconway said:
Hello So I have a brand new, unlocked, Samsung Note 3 (SN-900A - AT&T variety) that I bought from Best Buy. In the next few days I'll be switching to T-Mobile (no comments on carrier switch please), but since the GSM phone is unlocked I can use it on T-Mobile's network
Here is the current status of my phone:
Used Odin to flash back to stock AT&T 4.4.2 ROM from installed NL1 4.4.4
Rooted device on 4.4.2 and then upgraded to rooted/stock AT&T ROM 4.4.4 using SuperSU, BusyBox, and SafeStrap as explained here, here, and here (did not update to Lollipop)
Used Root App VIP to manually disable AT&T bloatware now that I have the phone rooted on 4.4.4
So in its current form my phone is rooted on 4.4.4 and working pretty well. I'm happy thus far and don't want to get too greedy since it works.
However I have a few questions about how to backup my current ROM and about geeting some better understanding about the root and ROM process. I would be quite appreciative if someone could assist me with the answers please!
It appears the original Dev of Safestrap (the core app at the heart of rooting and upgrading the Note 3 in my process) has moved onto greener pastures. Since SafeStrap does not work on 4.4.4 (can't boot into recovery or do backups), what is the replacement tool/utility? Should I use Odin for everything? OdinMobile? CWM? TWRP? FlashFire? I've read a bunch of threads on the differences and I'm having a hard time making heads or tails of it all. The main thing I want to be able to do now is backup my current ROM like you could previously with Safestrap, and update to a new ROM if I so choose.
I never wanted the bloatware - do you think I flashed the wrong ROM? Should I have used a stock ASOP ROM if I didn't want bloatware or is this not possible on the 900A?
Ironically if I had to have bloatware I would have preferred to have T-Mobile's since I will be on their network. Could I have put a T-Mobile ROM image on an AT&T variant of the phone? (just curious)
I used a AT&T stock ROM apparently from those links I posted which propogated the bloatware to 4.4.4, however at least I'm rooted. I believe this was all done to not disturb the KNOX flag. I have a warranty from BestBuy I would like to keep (1 year), but I can't go to AT&T for warranty service (they are not my carrier) and I didn't buy the phone from T-mobile either, so is the warranty worth anything anyway?
I keep reading that the AT&T variant of Note 3 has a 'locked bootloader' and that's what's with going to all the trouble with SafeStarp was about. Essentially it loads an alternate image/ROM not disturbing the stock one so that the KNOX flag is never triggered. Is there a way to unlock the bootloader on this phone or should I even care?
I'm early enough in this process that if I went down the wrong path I could do something different. Any or all help/assistance is greatly appreciated!
Click to expand...
Click to collapse
When I'm on a 4.4.4 Rom, I use AT&T OC1,NL1,NJ5 SafeStrap Work Around http://forum.xda-developers.com/note-3-att/general/att-nj5-safestrap-t2957471 install the Kernel Flasher http://forum.xda-developers.com/note-3-att/development/nc2-flasher-app-unsafe-t2989141/ grant it Supersu and tap to reboot, it will boot to Safestrap and do your backup or whatever you are doing. Once done you MUST flash the kernel may it be the NL1 or OC1, but you must flash it with Safestrap. The NL1 kernel (SM-N900A_NL1_KERNEL_RecoveryFlashable.zip) is for NL1 and NJ5 Roms and the OC1 kernel (SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip) is only for OC1 Roms. I don't use Mobile Odin or FlashFire. Even though you are on T-Mobile the phone is AT&T which has a locked boot loader, so you can not use CWM or TWRP and you are stuck using only AT&T Roms. You can use Titanium Backup to remove any bloatware (Backup first saves on headache, case something goes wrong or you can freeze it). This is a T-Moible Rom that is ported for AT&T; T-Mobile Alliance Lollipop Rom on ATT Note 3 http://forum.xda-developers.com/note-3-att/general/t-mobile-alliance-rom-att-note-3-t3065127 and since you are on T-Mobile, you wouldn't have to "After the phone came up, I went to settings..general..applications...running .... and found every Tmobile app and cleared cache and disabled them. The real important one here is the Visual Voicemail. Otherwise it will keep on trying to contact Tmobile and then you will get text messages saying there is an error." It is a OC1 Rom (Lollipop) so you would need the SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip because you would flash this in Safestrap once you have used the Kernel Flasher to access Safestrap. [How-To] Update to N900A_NL1 - 4.4.4 and Keep Root (12-24-2014) http://forum.xda-developers.com/note-3-att/general/how-to-root-n900aucudnl1-4-4-4-12-24-t2983357 is just the plain AT&T Rom that's been rooted, that's why you got all that bloatware. I go right here for any Rom I wish to install, Android development for the AT&T Galaxy Note 3 http://forum.xda-developers.com/note-3-att/development Forgot to say, write down your APN settings, so you can still get data. T-Mobile Network: Samsung Galaxy Note 3 (N900) https://support.t-mobile.com/docs/DOC-11447 in case.

Rooted i747 said:
This is a T-Moible Rom that is ported for AT&T; T-Mobile Alliance Lollipop Rom on ATT Note 3 http://forum.xda-developers.com/note-3-att/general/t-mobile-alliance-rom-att-note-3-t3065127 and since you are on T-Mobile...
Click to expand...
Click to collapse
This had all been really helpful, thank you. I've read the post a bunch and followed all the steps. The NC2 flasher is awesome and works great!
However, I'm trying to make heads or tails though of the T-Mobile Alliance ROM version to use (reminder I want a T-Mobile ROM on my AT&T Note 3 since I'm on T-Mobile's network). The underlying link that has the T-Mobile Alliance ROM to actually download states that KNOX is removed and activated (0x1). However the link provided by you to the T-Mobile Alliance flashing instructions page has multiple replies saying KNOX remains undisturbed and is at 0x0 after completion. I'm probably asking the wrong questions, but is the process of using Safestrap regardless of the ROM I'm using prevent KNOX from being tripped? Or is it that the newest version of the Alliance ROM is what would trip KNOX (i.e. should I use an older version of the ROM that doesn't remove KNOX)?
I have everything backed up, downloaded and ready to flash and install. I just want to flash this T-Mobile Alliance ROM but not trip KNOX. Once I can get a clear understanding this I'm ready to move forward and complete it.

atconway said:
This had all been really helpful, thank you. I've read the post a bunch and followed all the steps. The NC2 flasher is awesome and works great!
However, I'm trying to make heads or tails though of the T-Mobile Alliance ROM version to use (reminder I want a T-Mobile ROM on my AT&T Note 3 since I'm on T-Mobile's network). The underlying link that has the T-Mobile Alliance ROM to actually download states that KNOX is removed and activated (0x1). However the link provided by you to the T-Mobile Alliance flashing instructions page has multiple replies saying KNOX remains undisturbed and is at 0x0 after completion. I'm probably asking the wrong questions, but is the process of using Safestrap regardless of the ROM I'm using prevent KNOX from being tripped? Or is it that the newest version of the Alliance ROM is what would trip KNOX (i.e. should I use an older version of the ROM that doesn't remove KNOX)?
I have everything backed up, downloaded and ready to flash and install. I just want to flash this T-Mobile Alliance ROM but not trip KNOX. Once I can get a clear understanding this I'm ready to move forward and complete it.
Click to expand...
Click to collapse
Safestrap will not stop Knox from tripping. If you are not sure, if you Knox will trip or not then I say don't flash it. I never flashed that Rom, so I can't say. The Roms I have used and my Knox still 0X0. Currently on FireKat Deodex NC2 KK V19N3/V19N4 http://forum.xda-developers.com/showthread.php?t=2786666 AllianceROM Lollipop v9.1 http://forum.xda-developers.com/showthread.php?t=2778933 Note 4 Port Evolution 3.0 http://forum.xda-developers.com/note-3-att/development/rom-note-4-port-evolution-1-0-t2982296 Note 4 Port Evolution 3.0 you will have to flash extra things in Safestrap to make it work right.

atconway said:
This had all been really helpful, thank you. I've read the post a bunch and followed all the steps. The NC2 flasher is awesome and works great!
However, I'm trying to make heads or tails though of the T-Mobile Alliance ROM version to use (reminder I want a T-Mobile ROM on my AT&T Note 3 since I'm on T-Mobile's network). The underlying link that has the T-Mobile Alliance ROM to actually download states that KNOX is removed and activated (0x1). However the link provided by you to the T-Mobile Alliance flashing instructions page has multiple replies saying KNOX remains undisturbed and is at 0x0 after completion. I'm probably asking the wrong questions, but is the process of using Safestrap regardless of the ROM I'm using prevent KNOX from being tripped? Or is it that the newest version of the Alliance ROM is what would trip KNOX (i.e. should I use an older version of the ROM that doesn't remove KNOX)?
I have everything backed up, downloaded and ready to flash and install. I just want to flash this T-Mobile Alliance ROM but not trip KNOX. Once I can get a clear understanding this I'm ready to move forward and complete it.
Click to expand...
Click to collapse
Got bored so I tried it. Did not trip Knox and I really didn't see a different from AllianceROM Lollipop v9.1 http://forum.xda-developers.com/showthread.php?t=2778933 Well, I don't care for it, so back to FireKat! :silly:

Thanks for trying it out and your assistance I did the same on my phone immediately after you did and got the same results. It works great and should be a viable option for those like me that have an AT&T phone, but want to load a T-Mobile based ROM.
I'll be curious if that Alliance ROM though stays up to date with the newer versions of Android (i.e. 5.0.2, etc.) It appears to be based on 5.0.0 from what I can tell. Only reason I ask is because my experience with 5.0 on my old S4 has been awful. Fells like I'm back on Android Gingerbread with 500mb of ROM. :S There are so many memory leaks on my S4 now it stinks. 4.4.4 was way better.
Good news is I haven't seen that same issue thus far with the Alliance ROM, so hopefully is worked out whatever shortcomings the OS had.

How to wipe a phone with corrupted storage

I've got a Sprint Galaxy Note 2 (SPH-L900) with storage issues. For a few months now, the internal storage will occasionally become corrupted to the point where it won't boot. I have to wipe, reformat, and reinstall to get it running again using TWRP. When it died today, I decided it was time to trade up to a newer model. However, when I try to reformat the internal storage as usual, TWRP claims that it can't access the internal storage at all. The regular partitions are all in the list of things on which I could operate, but they're all listed as being not present in the phone. Is there any way around this?
I'd like to sell the Note 2 for whatever I can get for it (with appropriate disclosure, of course), but I'm not about to let it go without convincing myself that my personal data has been completely overwritten. If TWRP can't see the internal storage, how can I reformat it? Might adb or some other computer-based solution have better luck? I've never run that before, except when flashing TWRP with Odin. The phone won't currently boot past the initial black & white "Samsung Galaxy Note II" screen, unless I'm booting into recovery.
FWIW, I've really enjoyed using the MoKee 6.0.1 ROM on this phone recently. It's a pity the phone died out from under it. It has several nerd-friendly features that my wife's stock S5 lacks, and which I'm sure my new Note 4 will also lack.

Pros and cons of rooting.

Going to flash back to stock image. Any compelling reason to root? I'm rooted now and really the only reason to root would be to restore my titan backups of a couple games. I like the thought of being able to get updates hassle free.
Thoughts?

Xposed, Ad blocking, tasked, TiBu, LED notifications and Layers are the main reasons I'll stay rooted. You have to weigh the pros and cons based on what you consider most important.
Sent from my Nexus 6 using Tapatalk

monkey3ddd said:
.... I like the thought of being able to get updates hassle free.
Thoughts?
Click to expand...
Click to collapse
When you have Twrp-recovery installed
A prerooted stock rom is a possibility.
- download latest version to internal memory.
- boot Twrp-recovery
- wipe system and caches
- flash rom (zip file)
- reboot.
http://forum.xda-developers.com/showthread.php?p=59561445/

ATM, my interest in rolling back to stock is insure that I can use us cellular towers in fi. I read that running pure nexus could mess with this ability. I have yet to see a usc tower show as my "network". Latest fi update said it included that..

I'm ocd about battery life so I root to run custom kernels and use dark themes to take advantage of the oled screen. and I can't used android pay because my small town bank can't be used with it so I'm not missing out on anything

pros= everything
cons=none
this question has been asked many many many many times...you need to make up your OWN mind on this..