Related
Hi guys, have a few questions...
For starters, I have a Samsung Galaxy S4 / AT&T
Running Android 4.4.2 Rooted with Towel Root
Connected on Straight Talk
~NC1
SafeStrap 3.72 (TWRP v2.7.0.0) Installed.
Im new to all this ROM/Modules and Rooting stuff.
Last time i fully customized stuff was on my Motorola RZR ages ago
making my keypad/ LED light blink with calls, and replacing the Cingular Logo
with a Pirate/2 Swords Logo. hah... good times.
I mean there was jail-breaking and whatnot but...that's easy stuff.
Any who, Im a quick learner so on to the subject.
My original idea was to FULLY customize this phone and install ROMS/other OS, thats
what im all about, customization. Sadly, i realized im on a NC1 which its Boot loader is
locked if im understanding correctly preventing me from installing other? ROMS?
However if i understood correctly, we still can install certain ROMS? Whats the difference?
Is there any ROM i can install that is clean? no bloatware? but with everything I need?
Whats the best, fastest and best looking ROM i can get? or they dont look different because the
boot loader thing? Or they can only be Samsung/AT&T roms? This stuff can be confusing. lol
Module wise, why do i need them? why arent they included in the actual ROM?
Also, is there any App/or way for me to know what causes my phone to randomly crash/reboot?
A few months ago I was at the GYM and my phone randomly shut off. It didnt want to turn back on.
After a while it turned back on, then it would randomly reboot. That eventually went away.
Last night, i was with some friends in a bar and my phone just turned off again. Didnt wanna turn
on...then the same reboot thing happened again.
Today, is working fine. I thought maybe it was an overheat issue but, i wasnt doing anything on my
phone and on top of that im using a CPU tempt program installed through xPosed and according to the
readings it wasnt hot, as it was in the 50-55c (or is that too hot?) Im at home now and its reading
36c but i dont have its case on (if that makes any difference)
There are 3 kind of "ROM"s :
1- Official ones. made by samsung. flashable via odin exclusively. not rooted
2- A bit modified (maybe more than a bit) Official ones, modified by people, flashable via odin or recovery (1), usually already rooted
3- Completely rewritten ROMS, almost made from scratch (Cyanogenmod, MIUI for exemple...), installable via recovery. already rooted
Now, your phone can be in two states : Rooted or not rooted.
From factory, your phone is not rooted (you can compare it to jailbreak)
with root, you become a "super user", which means you have rights on almost every single aspect of your phone, and you give authorisations to apps so they can act on system files (for exemple, they can get hidden informations, they can automatically install apps etc... infinite possibilites there are.)
As for the best rom there is, is like asking what is the best music ever, it depends on the user, you have to try by yourself to find the one that satisfies you the most.
For random reboots, i personally think that it is comparable to windows Blue Screen of Deaths. you maybe messed up something while installing something. your phone can't handle the bug, so it restart or shut down itself. so the safest way to get rid of this problem is to factory reset your phone (via the recovery)
if you are looking for stableness, don't opt for completely remade ROMS, they are usually experimental. but personally i use MIUI and i didn't have any problem and i love this ROM.
Hope i answered every question.
Thanks a lot for the reply.
I understand a bit better now...
That MIUI looks interesting... Reminded me of DreamPassport for my Sega Dreamcast, hah...
I'm guessing I cant install that one huh? Lol
well since you already have a custom recovery you can... just download a miui rom (one for your phone version (be carefull about the model) ) then put it on the root of your sd card, go to the custom recovery and flash zip from sdcard and choose it... but i advice you to factory reset your phone first in order to fix your reboot problem.
also, make sure you have installed the right android version before installing the equivalent miui version (for exemple if you want to install miui that requires 4.2, install an official 4.2 rom first) via odin.
Gotcha. Thanks.
One last question....
If I want my phone with the original OS it came with. But with all the bloatware removed...
which rom would be the best? , since I want the stock experience but no bloatware.
Also...
I noticed when you click to see how much ram is being used, it says
800/1.77GB
Isnt my phone suppose to have 2GB? Can I do something to get that back? is it cause the bloatware?
I appreciate the help.
Raging Tiger said:
Gotcha. Thanks.
One last question....
If I want my phone with the original OS it came with. But with all the bloatware removed...
which rom would be the best? , since I want the stock experience but no bloatware.
Also...
I noticed when you click to see how much ram is being used, it says
800/1.77GB
Isnt my phone suppose to have 2GB? Can I do something to get that back? is it cause the bloatware?
I appreciate the help.
Click to expand...
Click to collapse
I don't think the above information is correct.
From what I know the AT&T has a locked bootloader. So you can run custom roms, just not all of them. I think only custom roms that match the version you are using.
You could better read in the section for the AT&T (this section is for a different model).
http://forum.xda-developers.com/galaxy-s4-att
Hello guys,
Here is a long story, interesting to read maybe for some.
I had android 4.3.2 on my Note 3 N9005, for 2 and a half years now. I rooted the phone as soon as it came out. Had many applications which ran smoothly on it, schreenshots/screenrecorders, xposed installer with a lot of mods.. etc.. everything worked fine. Until the last few months, where suddenly "some application" stopped working. I began to have that message, more and more often, and on different applications. I thought, it was time to run a factory reset. BUT I remembered that I ran into some applications on Play Store, which couldn't be installed, since I had an old android version.
So, now, I thought, maybe it was time to try a custom rom. So I installed LiquidSmooth, (android 5.1.1). Nice jump, I must say, many things different, than 4.3.2. Some problems though, the sound was with interference, and some apps just froze. Some games I was playing, just froze.
Then I thought I try another ROM. Found a page with best ROMs, for 5.1.1 and saw that LiquidSmooth only had like 4.8% of the votes, while Nightly had like 40% of the votes and was much more stable (well, according to that site). So I thought I change. BUT, then I saw, that I could actually update to 6.0.1 with Ressurection Remix. So I thought, wow, lemme try that !
So I did. I installed Ressurection Remix, and I must admit, it looks damn good. Even bought the swift dark theme, and it is beautifull. It is candy for the eye. God damn, almost like the 3D cube I played with in Linux a few years back. But some of my games, still freeze. - And as you can guess, I do not like that.. I also got the message on boot: Kernel is not seandroid enforcing.. and I know it's normal, but still I do not like it. (I want everything to be perfect). And with some games, not being able to run, I got tired of RR.
So now, I was thinking, what if I could switch back to 4.3.2? I should have run maybe a factory reset on 4.3.2 instead of trying ROMs, at least my stuff was working. So I thought I get the original stock firmware, and just flash it with ODIN. So, it should be good.
Now I know that on a lot of threads here on the site, people mention that you can't downgrade android. Well, at least not from 6.0.1 to 4.3.2. Because ODIN is not working in 6.0.1 and other stuff.
BUT, I think this: I have a backup, with CWM, for 4.3.2, which I know works, (since I used it a few times).
So, what if I run that backup and get my phone back to 4.3.2.? (again, some ppl here on site, that they accidentally downgraded from 4.4 to 4.3, then they could't upgrade back to 4.4).
So my question is: I use CWM to restore the 4.3.2 backup, THEN in the phone with ODIN I run the original full stock firmware?
Then later, I could unlock bootloader and root my phone again if I want to try something. Would this be possible?
A second question, which I have is: Before I upgraded to lolipop and marshmallow, i ran of course a factory reset, reset cache and dalvik from CWM. But still, now, where I am on 6.0.1 I still saw some folders of some programs I had on 4.3.2. How is that possible? The programs are not in the menu, but the folders are on phones memory. Shouldn't they have been deleted on those 3 resets from CWM? (factory, cache and dalvik?). This is also a reason, for why I would want to return to original stock firmware. Cos I could root my phone right away again, and then upgrade to some rom, so those programs do not come along, and I would have a clean rom. Or with other words, the phones "user" memory, /storage/emulated/sdcard0 - could I just delete it all? I mean the operating system is on root, this directory /storage/emulated/sdcard0 is usually what the user installs on the phone, am I right?
And last question, cos I am greedy for answers. The samsung pen, is of course not working, and I miss it. Any app to install or flash to get the pen alive again?
Thank for your time ro read this Hope u can help ))
Please somebody help. I am also interested.
Wao, boy it was a real long story. And I read it all.
LordTicut said:
Hello guys,
Here is a long story, interesting to read maybe for some.
I had android 4.3.2 on my Note 3 N9005, for 2 and a half years now. I rooted the phone as soon as it came out. Had many applications which ran smoothly on it, schreenshots/screenrecorders, xposed installer with a lot of mods.. etc.. everything worked fine. Until the last few months, where suddenly "some application" stopped working. I began to have that message, more and more often, and on different applications. I thought, it was time to run a factory reset. BUT I remembered that I ran into some applications on Play Store, which couldn't be installed, since I had an old android version.
So, now, I thought, maybe it was time to try a custom rom. So I installed LiquidSmooth, (android 5.1.1). Nice jump, I must say, many things different, than 4.3.2. Some problems though, the sound was with interference, and some apps just froze. Some games I was playing, just froze.
Then I thought I try another ROM. Found a page with best ROMs, for 5.1.1 and saw that LiquidSmooth only had like 4.8% of the votes, while Nightly had like 40% of the votes and was much more stable (well, according to that site). So I thought I change. BUT, then I saw, that I could actually update to 6.0.1 with Ressurection Remix. So I thought, wow, lemme try that !
So I did. I installed Ressurection Remix, and I must admit, it looks damn good. Even bought the swift dark theme, and it is beautifull. It is candy for the eye. God damn, almost like the 3D cube I played with in Linux a few years back. But some of my games, still freeze. - And as you can guess, I do not like that.. I also got the message on boot: Kernel is not seandroid enforcing.. and I know it's normal, but still I do not like it. (I want everything to be perfect). And with some games, not being able to run, I got tired of RR.
So now, I was thinking, what if I could switch back to 4.3.2? I should have run maybe a factory reset on 4.3.2 instead of trying ROMs, at least my stuff was working. So I thought I get the original stock firmware, and just flash it with ODIN. So, it should be good.
Now I know that on a lot of threads here on the site, people mention that you can't downgrade android. Well, at least not from 6.0.1 to 4.3.2. Because ODIN is not working in 6.0.1 and other stuff.
BUT, I think this: I have a backup, with CWM, for 4.3.2, which I know works, (since I used it a few times).
So, what if I run that backup and get my phone back to 4.3.2.? (again, some ppl here on site, that they accidentally downgraded from 4.4 to 4.3, then they could't upgrade back to 4.4).
So my question is: I use CWM to restore the 4.3.2 backup, THEN in the phone with ODIN I run the original full stock firmware?
Then later, I could unlock bootloader and root my phone again if I want to try something. Would this be possible?
A second question, which I have is: Before I upgraded to lolipop and marshmallow, i ran of course a factory reset, reset cache and dalvik from CWM. But still, now, where I am on 6.0.1 I still saw some folders of some programs I had on 4.3.2. How is that possible? The programs are not in the menu, but the folders are on phones memory. Shouldn't they have been deleted on those 3 resets from CWM? (factory, cache and dalvik?). This is also a reason, for why I would want to return to original stock firmware. Cos I could root my phone right away again, and then upgrade to some rom, so those programs do not come along, and I would have a clean rom. Or with other words, the phones "user" memory, /storage/emulated/sdcard0 - could I just delete it all? I mean the operating system is on root, this directory /storage/emulated/sdcard0 is usually what the user installs on the phone, am I right?
And last question, cos I am greedy for answers. The samsung pen, is of course not working, and I miss it. Any app to install or flash to get the pen alive again?
Thank for your time ro read this Hope u can help ))
Click to expand...
Click to collapse
Hi friend.
I think you asking: I installed Android MM and It's possible to downgrade 4.3 via Odin tar.md5 flash installation?
I answer: Yes, i think i like you (or you like me). I love use all rom as possible as quickly, but i tired from "system" process not respond and sound quality issue.
I say you ITS POSSIBLE. because i flash via odin anytime (my stock firmware .tar.md5). Even from android mm to 4.3, lollipop > kitkat, v5.1.1 port rom > v5.0.
You can try, first time i'm newbie on XDA, there said something like bootloader. I now said, its necessary (important), just not too for Flashing Stock ROM.
I hope this little helps to you...
Good luck, i'm now Android MM!
Now i searching for backing knox to 0x0.
Via CWM not ODIN
Thanks dalisoft for answering.
My question was actually if I could restore my backup I made with ClockWorkMod a few years ago.
dalisoft said:
Hi friend.
I think you asking: I installed Android MM and It's possible to downgrade 4.3 via Odin tar.md5 flash installation?
I answer: Yes, i think i like you (or you like me). I love use all rom as possible as quickly, but i tired from "system" process not respond and sound quality issue.
I say you ITS POSSIBLE. because i flash via odin anytime (my stock firmware .tar.md5). Even from android mm to 4.3, lollipop > kitkat, v5.1.1 port rom > v5.0.
You can try, first time i'm newbie on XDA, there said something like bootloader. I now said, its necessary (important), just not too for Flashing Stock ROM.
I hope this little helps to you...
Good luck, i'm now Android MM!
Now i searching for backing knox to 0x0.
Click to expand...
Click to collapse
LordTicut said:
Thanks dalisoft for answering.
My question was actually if I could restore my backup I made with ClockWorkMod a few years ago.
Click to expand...
Click to collapse
Yes, you can restore nandroid backup if you have CWM.
But, remember, before restoring you should to do some steps:
1. Wipe data/factory reset
2. Wipe cache
3. Advanced > Wipe dalvik cache
4. Mounts > Format /system
5. Mounts > Format /data
Allright, thanks Dalisoft.
Do you know by the way, if CWM also takes a copy of EFS? I mean EFS is a system directory, so is it included in the nandroidbackup by CWM, right? So if I restore that backup, I will have my EFS exactly as it was, just after I rooted my phone. (not because something is wrong with it, but in case sometyhing is altered, it will be back to normal, right?).
I mean, there are 2 partitions on the phone, the ROM and the recovery. And CWM does an exact image of the ROM partition, so I would assume that the EFS folder is there too. But I am not sure, that's why I am asking.
Guess I am happy and lucky I made a backup with CWM right after root..
CWM also takes a copy of EFS?
Answer = NO .
http://forum.xda-developers.com/showthread.php?t=2698639
http://forum.xda-developers.com/showthread.php?t=2481255
JJEgan said:
CWM also takes a copy of EFS?
Answer = NO .
http://forum.xda-developers.com/showthread.php?t=2698639
http://forum.xda-developers.com/showthread.php?t=2481255
Click to expand...
Click to collapse
JJEgan
You are right, I posted this thread in the wrong forum. I am deeply sorry for that. I just wanted quickly an answer. It won't happen again. ( I saw in the meantime it has been moved, so I guess everything is good)
Cheers !
As of yesterday my phone stopped booting certain roms! Im rooted with all the latest twrp, vendor, bootloader, etc. I never encountered this problem and Ive been rooted since day one. I have several custom roms on my phone and only "Resurrection Rom" seems to boot without any problem all the other (Purenexus, benzorom, chroma, exdous) Roms get past the google screen and stay stuck in the boot up screen.. Am I missing something?? Ive checked everything I could. Ive downgraded twrp. Im stump any insight on this would be greatly appreciated..
Info
big nu said:
As of yesterday my phone stopped booting certain roms! Im rooted with all the latest twrp, vendor, bootloader, etc. I never encountered this problem and Ive been rooted since day one. I have several custom roms on my phone and only "Resurrection Rom" seems to boot without any problem all the other (Purenexus, benzorom, chroma, exdous) Roms get past the google screen and stay stuck in the boot up screen.. Am I missing something?? Ive checked everything I could. Ive downgraded twrp. Im stump any insight on this would be greatly appreciated..
Click to expand...
Click to collapse
check Kernel compatibility if you update internal rom
- reinstall kernel
:good:
big nu said:
As of yesterday my phone stopped booting certain roms! Im rooted with all the latest twrp, vendor, bootloader, etc. I never encountered this problem and Ive been rooted since day one. I have several custom roms on my phone and only "Resurrection Rom" seems to boot without any problem all the other (Purenexus, benzorom, chroma, exdous) Roms get past the google screen and stay stuck in the boot up screen.. Am I missing something?? Ive checked everything I could. Ive downgraded twrp. Im stump any insight on this would be greatly appreciated..
Click to expand...
Click to collapse
Same with me dude
https://tapatalk.com/shareLink?url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php?t=3357580&share_tid=3357580&share_fid=3793&share_type=t
Here's my thread... I have tried everything even going back to stock MHC19Q and starting fresh... RIP 6P
MoistPicklez said:
Same with me dude
https://tapatalk.com/shareLink?url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php?t=3357580&share_tid=3357580&share_fid=3793&share_type=t
Here's my thread... I have tried everything even going back to stock MHC19Q and starting fresh... RIP 6P
Click to expand...
Click to collapse
Never figured anything out? I think im having this same issue with my 6p i tried flashing pure nexus, xTraFactory, and Stock+ but for me it just bootloops and once out of 20 attemps pure nexus will get to the colored logo then freeze and reboot. I long deleted Ressurrection Remix because it was my daily driver and already had a backup made. That went to sh*t though when my backup bootlooped as well so now i have a 6p i can only boot into recovery and bootloader. My laptop with fastboot installed needs a new charger so i use my moms computer to put zips on my phone but i really doubt she will let me install anything on it at all :/. I dont want to flash the factory image and bootloop still though when i get a charger. Ill see if I can boot back into rros fresh.
Coeur Brisé said:
Never figured anything out? I think im having this same issue with my 6p i tried flashing pure nexus, xTraFactory, and Stock+ but for me it just bootloops and once out of 20 attemps pure nexus will get to the colored logo then freeze and reboot. I long deleted Ressurrection Remix because it was my daily driver and already had a backup made. That went to sh*t though when my backup bootlooped as well so now i have a 6p i can only boot into recovery and bootloader. My laptop with fastboot installed needs a new charger so i use my moms computer to put zips on my phone but i really doubt she will let me install anything on it at all :/. I dont want to flash the factory image and bootloop still though when i get a charger. Ill see if I can boot back into rros fresh.
Click to expand...
Click to collapse
Well this is quite an old post to awaken but to be short and Frank I had to send my device in to have the motherboard replaced because the 6p still has hardware issues whether it's Huawei's (prolly spelled wrong.) fault or Google's, regardless I just got the motherboard replaced and sold the device immediately because I didn't want to have another paper weight in my hands I now have an essential phone and it is dare I say the most comfortable phone I've ever had. That being said I hope you can Rectify your issues here but you'll have to go through either Huawei or Google, and get one of the two to help you out with a replacement.
This kind of happened to me too. I just updated TWRP and all flash are fine now. Hope this will help someone
MoistPicklez said:
Well this is quite an old post to awaken but to be short and Frank I had to send my device in to have the motherboard replaced because the 6p still has hardware issues whether it's Huawei's (prolly spelled wrong.) fault or Google's, regardless I just got the motherboard replaced and sold the device immediately because I didn't want to have another paper weight in my hands I now have an essential phone and it is dare I say the most comfortable phone I've ever had. That being said I hope you can Rectify your issues here but you'll have to go through either Huawei or Google, and get one of the two to help you out with a replacement.
Click to expand...
Click to collapse
Solved it today it was because I tried restoring an old backup with an old version of twrp that has a fatal bug when you restore an EFS. I was truly relieved
Hi, I need the ROM for this phone, more specifically, the boot.img file, as the current kernel is for the older, Indian revision of the On5, and my revision, the USA version SM-G550T1, seems not to have any copies of its firmware floating around. I'm running an OS for the SM-G550FY, which has no audio or camera support. Even if the version isn't an exact match, if you bought this phone in the USA, new, in 2016, your boot.img will probably work. I need this kernel guys. Please, if someone has an On5 in the USA, can I please get a copy of your boot.img and possibly system.img? I really care about the boot.img.
Thanks guys
-Subsentient
Firstly, did you try the updated ones at these locations:
http://www.theandroidsoul.com/galaxy-on5-stock-firmware-2-86761/
http://firmwarefile.com/samsung-sm-g550fy
Secondly, why exactly do you need the boot.img, what problem do you think it'll solve? Is there any specific issue with your current ROM that you are trying to solve?
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Subsentient said:
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Click to expand...
Click to collapse
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
prahladyeri said:
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Subsentient said:
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Click to expand...
Click to collapse
There you are! I just cannot emphasize enough that why don't you guys backup your existing ROMs before flashing a new one? It hardly takes five minutes with CWM/TWRP recovery.
In any case, what happens when you flash the Indian ROM (5.1.1)? I guess that could be your only option.
Otherwise, you can put a request on the CyanogenMod thread for your particular Samsung model.
For future reference, perform device backups and all the research before flashing a custom ROM, not after the fact.
EDIT
If you can contact Samsung support, see if you can manage to get a stock ROM from them that you can flash using ODIN or something.
I contacted them already, they basically told me to go **** myself. The missing ROM is a result of bad parameters I accidentally put in to Heimdall/ODIN flasher. I wanted to back up, but ironically, my first attempt at installing TWRP is what destroyed my ROM.
I've downloaded the kernel source code from Samsung and I'll try compiling it myself. If I create a working boot.img, I'll post it here.
prahladyeri said:
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
boot.img is where the kernel is stored. I know, I decompressed it.
Subsentient said:
boot.img is where the kernel is stored. I know, I decompressed it.
Click to expand...
Click to collapse
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
prahladyeri said:
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
Click to expand...
Click to collapse
The kernel on this device does not have loadable module support. It's entirely monolithic. And, I'm having one hell of a time building a kernel this thing is willing to boot.
I really would love just to get a ROM from someone else's SM-G550T or SM-G550T1.
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
bandtab said:
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
Click to expand...
Click to collapse
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Subsentient said:
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Click to expand...
Click to collapse
thank you!
however, i can't install twrp to my recovery partition anymore because i got FRP locked, and i can't go into my settings to disable it now. so i think my only option really is via odin. i'll see what i can do with this though, thank you very much. i did have twrp on there before but after i got frp locked i can't go into recovery mode at all.
I've been losing my mind trying to make this work.
I think if I installed the stock recovery.img it may work, but I can't find it in the files you sent. Would you or anyone else be able to make a copy of it for me? I would be eternally indebted to whoever could.
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
holydude92 said:
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
Click to expand...
Click to collapse
unfortunately smart switch is incompatible with this model phone for the time being.
I got four of these from T-Mobile when we switched from Verizon ($120 for 4 lines). Three of our Verizon phones worked well on T-Mobile (after a few APN tweaks), but my dad's old Galaxy S3 barely worked at all, and when it did, only got Edge for data. So I set one of the On5 phones up for him.
Everything was going great. I put the TWRP recovery on it, rooted it, froze all the bloatware, and backed up/restored his apps from the old S3. However, he wanted me to see if I could restore all his SMS/MMS. I tried restoring that, and the stock Messaging app started FC'ing. I installed Textra, which worked (and saw the old messages), but he never received new texts (even though he could send). So I tried removing Messaging and Textra, as well as the SMS cache (which seemed to be in "Dialer Storage (Phone SMS/MMS). I removed it, but now I'm getting an error every five seconds about "com.android.phone" and can't seem to get rid of it. I tried to restore the dialer storage backup again, but it just seems to sit forever without installing.
I've looked far and wide for a stock ROM... hoping I could just put this mess behind me, but I'm surprised to find it is nowhere to be found.
My other alternative would be to fix the com.android.phone error, but nothing seems to fix it.
Which cynogenmod or any custom os suits for Samsung Galaxy on 5.......please tell me guys.....I am bored with this official os
I was really hoping to come back to this forum and finally see stock ODIN files for this phone. I really, really want to get rid of the MetroPCS ROM I used to fix it.
Has anyone been able to find it?
Looking for any help or at least clues about what is wrong.
I was on ArrowOS 10, updated OTA to latest build two days ago, all was fine. Tonight it suddenly rebooted and when I unlock it, the desktop says the OS is loading, but it hangs, and then eventually reboots, bootlooping.
I had a working Nandroid backup, so I restored that from TWRP. Still cannot get the OS loaded. Wiped everything, even internal storage, backup still had same issue.
Then I tried reinstalling an older build of the ROM that I knew worked for me and I get stuck on the "Just a sec" after choosing a language. Eventually it reboots and hangs on the "Just a sec" before rebooting again. Wiped everything again and I tried another build of the same ROM, same problem. More wiping, tried Pixel Experience, same problem.
I'm thinking something is corrupted but I don't get any specific error messages so I'm not sure what to do. I repaired the data partition in TWRP, thinking that was the issue, but still cannot get any ROMs to load.
Any guidance is greatly appreciated as the phone is useless in this state. Thank goodness I have all my data backed up, but I really hope the phone is salvageable. Thank you.
twasbrillig12 said:
Looking for any help or at least clues about what is wrong.
I was on ArrowOS 10, updated OTA to latest build two days ago, all was fine. Tonight it suddenly rebooted and when I unlock it, the desktop says the OS is loading, but it hangs, and then eventually reboots, bootlooping.
I had a working Nandroid backup, so I restored that from TWRP. Still cannot get the OS loaded. Wiped everything, even internal storage, backup still had same issue.
Then I tried reinstalling an older build of the ROM that I knew worked for me and I get stuck on the "Just a sec" after choosing a language. Eventually it reboots and hangs on the "Just a sec" before rebooting again. Wiped everything again and I tried another build of the same ROM, same problem. More wiping, tried Pixel Experience, same problem.
I'm thinking something is corrupted but I don't get any specific error messages so I'm not sure what to do. I repaired the data partition in TWRP, thinking that was the issue, but still cannot get any ROMs to load.
Any guidance is greatly appreciated as the phone is useless in this state. Thank goodness I have all my data backed up, but I really hope the phone is salvageable. Thank you.
Click to expand...
Click to collapse
Sounds not so good. I would try to fastboot flash the latest signed Motorola firmware.
Here's a link where you can find it and how to do it:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Sounds not so good. I would try to fastboot flash the latest signed Motorola firmware.
Here's a link where you can find it and how to do it:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thank you! That fixed it. Any idea what happened? Could it have been from the OTA update two days prior? I'd like to prevent it from happening again if possible.
twasbrillig12 said:
Thank you! That fixed it. Any idea what happened? Could it have been from the OTA update two days prior? I'd like to prevent it from happening again if possible.
Click to expand...
Click to collapse
First of all good to hear you've got everything up and working again. Difficult to say what caused the problem, best would be to give these informations to the ROM maintainer/developer because he knows best what is changed in his custom ROM/OTA compared to the original stock firmware.
I would think it has been the OTA update that caused the trouble, OTA's are problematic for manufacturers and even more for custom ROMs with a smaller userbase and less employees.
My advice would be to avoid OTA updates if possible, often it's better to (dirty) flash the whole ROM by hand if available.
But the exact reason is not easy to find out, as said check the ROMs thread or PM the maintainer.
If you're in a situation like you've been it's always a good idea to flash original stock firmware, it brings the device to the most stable and recommended state.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
First of all good to hear you've got everything up and working again. Difficult to say what caused the problem, best would be to give these informations to the ROM maintainer/developer because he knows best what is changed in his custom ROM/OTA compared to the original stock firmware.
I would think it has been the OTA update that caused the trouble, OTA's are problematic for manufacturers and even more for custom ROMs with a smaller userbase and less employees.
My advice would be to avoid OTA updates if possible, often it's better to (dirty) flash the whole ROM by hand if available.
But the exact reason is not easy to find out, as said check the ROMs thread or PM the maintainer.
If you're in a situation like you've been it's always a good idea to flash original stock firmware, it brings the device to the most stable and recommended state.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Okay, I was planning on dirty flashing the next update anyway. I usually do since OTA's often don't work for me, but this last one seemed like it was. I'm definitely notifying the developer. Thanks again!