I have a Samsung Galaxy S III that I purchased on eBay. It have TWRP on it, and I know absolutely nothing about it except how to open it and get back to the phone. I'm looking for someone who can be patient enough to answer questions and give advice
Ok, to help you with this, in case you haven't fully understood TWRP yet.
It is a very powerful tool that has many features. It can create(backup button in TWRP) and restore(restore button in TWRP) backups(most important feature), it can save those backups to whatever storage location you choose, you have to find the option and select where you want the backup to be stored. You can also choose to backup other partitions along with the default partitions.
It can install(Install button in TWRP) various recovery flashable .zip files including ROMs, Kernels, Modems, newer recoveries, and various other mods/tweaks such as the Xposed framework. It can flash .img files also, provided those .img files are for your device.
It has the ability to wipe(format) the various partitions on the device to clear all data in the selected partition(s), these include the normal wipes when flashing ROMs and such, To do the normal wipes, select the Wipe option in TWRP, you'll see at the top it says Factory reset/wipe data, wipe cache partition and wipe dalvik/ART cache(newer ROM and recoveries use ART, dalvik is older stuff(swipe the slider to wipe). In addition to the normal wipes there are the advanced wipes(select Wipe option, then select Advanced Wipe), typically the advanced wipes are only used when doing a "clean install", it is used to wipe only the System partition and the Data partition to clear any junk that might cause issues with a new ROM you want to use, some ROMs even require a system wipe/clean install to use the ROM. You must be careful when using advanced wipes, if you wipe the wrong thing you'll be screwed. To be safe, only wipe System, Data, Cache, Dalvik/ART, and maybe internal storage(this erases everything you have on internal such as pictures, other media and other downloaded content). Also, when you wipe system partition it removes your OS completely and will have to be flashed with a ROM before rebooting, if you reboot without flashing you'll have nothing to boot to and in some cases it is difficult to revive the device.
It has a file manager that you can use to browse through the folders and files on your device while in recovery.
It can be used to connect the device to ADB where you can do all manner of things with the device. ADB can be used to boot the device to whatever mode you want, it can be used to push or pull files to and from the device, it can be used to capture logcats from the device that give technical live data of what the device is doing below all the layers of software to pinpoint bugs and issues. ADB is used to flash .img files to the device and even pull .imgs from the device using the dd command line, it has many, many things it can do, its all pretty advanced though.
There are other minor, rarely used features as well such as fix permissions, mount and unmount various partitions, etc. You can learn all of them by googling the various features to find descriptions of them.
If you have questions, just ask.
Where were you 4 months ago lol. I searched and begged and googled this with no answers. I didn't know anything about ROMs or kernals or recovery until this phone wanted to update. I followed the instructions and found myself in TWRP and thought my phone had been infected with a virus. That was around October 2015. It took me months more to find XDA, months more to figure out where to post a question, and months more to get information. I manged to flash the MOAR rom in July, but didn't see that it was from 2012, so the developer won't answer any questions I have. I couldn't figure out how to restore what I had before and subsequently deleted the files from my exSd.
My frustration is that I didn't get into this because I was interested in it or knew about the workings of operating systems and wanted to make my phone awesome. I thought I had to in order to make it work right. I was seduced by ideas of having an awesome phone when I read about custom ROMs while trying to find one. The problem is, I don't understand the power I have in order to use it.
Sorry to ramble. I do thank you for your information. I also welcome ( beg for) any help or suggestions about what works with what devices.
Thank you again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Where were you 4 months ago lol. I searched and begged and googled this with no answers. I didn't know anything about ROMs or kernals or recovery until this phone wanted to update. I followed the instructions and found myself in TWRP and thought my phone had been infected with a virus. That was around October 2015. It took me months more to find XDA, months more to figure out where to post a question, and months more to get information. I manged to flash the MOAR rom in July, but didn't see that it was from 2012, so the developer won't answer any questions I have. I couldn't figure out how to restore what I had before and subsequently deleted the files from my exSd.
My frustration is that I didn't get into this because I was interested in it or knew about the workings of operating systems and wanted to make my phone awesome. I thought I had to in order to make it work right. I was seduced by ideas of having an awesome phone when I read about custom ROMs while trying to find one. The problem is, I don't understand the power I have in order to use it.
Sorry to ramble. I do thank you for your information. I also welcome ( beg for) any help or suggestions about what works with what devices.
Thank you againView attachment 3891814
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
You should be able to flash any of the sprint S3(d2spr) ROMs, recoveries, kernels and mods for d2spr and of course the general mods that can be used by virtually any device such as the Xposed framework for ARMv7 devices. I have an S3 that uses the (d2vzw) stuff so I can help you a lot with your S3.
Actually all of the US variant S3(d2vzw, d2spr, d2att, d2usc, d2tmo, etc..)devices can use the d2lte ROMs, on top of that, the d2 devices can all flash each others ROMs without harming the device, they just won't have signal or buttons will be backwards and little things like that, the S3 ROMs can easily be converted from one device to another, the d2 devices are 95% the same.
You could easily flash the newest TWRP and then choose a d2spr lollipop or marshmallow ROM from the Sprint S3 forum as these are the most up to date and readily available ROMs, there's very little support for Kit Kat and older stuff.
And of course, you could always go back to full stock with no root or TWRP if you just want the device to work and would rather avoid all of this custom stuff and its complexities.
For that you just need to do a google search for:
"Return to stock (your model number)"
Or you can go to Sammobile .com or samsung-updates .com and use your model number to find the stock firmware for your device, download it then download the newest version of Odin and install it on PC then boot your phone to download mode(volume down+home+power, press up at the caution screen to enter download mode), connect to Odin, if you get a blue or yellow comm# box you're connected. Click the AP button then browse to your stock firmware .tar.md5 file, select it, back in Odin click start and it will flash the device and reboot into the restored stock firmware, sometimes it bootloops and you have to boot to stock recovery(volume up+home+power) then factory reset and wipe cache in stock recovery then reboot.
I can help you any direction you want to go, just say the word and I'll get you there. Do you want custom or stock? If you want custom, do you want Kit Kat(4.4.x) lollipop(5.x)or marshmallow(6.x), maybe even a Nougat(7.0) ROM?
Droidriven said:
You should be able to flash any of the sprint S3(d2spr) ROMs, recoveries, kernels and mods for d2spr and of course the general mods that can be used by virtually any device such as the Xposed framework for ARMv7 devices. I have an S3 that uses the (d2vzw) stuff so I can help you a lot with your S3.
Actually all of the US variant S3(d2vzw, d2spr, d2att, d2usc, d2tmo, etc..)devices can use the d2lte ROMs, on top of that, the d2 devices can all flash each others ROMs without harming the device, they just won't have signal or buttons will be backwards and little things like that, the S3 ROMs can easily be converted from one device to another, the d2 devices are 95% the same.
You could easily flash the newest TWRP and then choose a d2spr lollipop or marshmallow ROM from the Sprint S3 forum as these are the most up to date and readily available ROMs, there's very little support for Kit Kat and older stuff.
And of course, you could always go back to full stock with no root or TWRP if you just want the device to work and would rather avoid all of this custom stuff and its complexities.
For that you just need to do a google search for:
"Return to stock (your model number)"
Or you can go to Sammobile .com or samsung-updates .com and use your model number to find the stock firmware for your device, download it then download the newest version of Odin and install it on PC then boot your phone to download mode(volume down+home+power, press up at the caution screen to enter download mode), connect to Odin, if you get a blue or yellow comm# box you're connected. Click the AP button then browse to your stock firmware .tar.md5 file, select it, back in Odin click start and it will flash the device and reboot into the restored stock firmware, sometimes it bootloops and you have to boot to stock recovery(volume up+home+power) then factory reset and wipe cache in stock recovery then reboot.
I can help you any direction you want to go, just say the word and I'll get you there. Do you want custom or stock? If you want custom, do you want Kit Kat(4.4.x) lollipop(5.x)or marshmallow(6.x), maybe even a Nougat(7.0) ROM?
Click to expand...
Click to collapse
Wow, you are my hero! I don't know how to thank you enough.
First off, I promise I have put in lots of work on my own trying to find answers. Also, I may be underestimating my own understanding.
As far as ROMs, I haven't worked this hard to give up now! Not only do I want custom, I want to know what kernel does, what a governor does, what mods are. I think everyone else thought I wanted to be told what system to install while I only wanted to be educated so I could decide for myself. Basically, I'm asking for a teacher
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Where were you 4 months ago lol. I searched and begged and googled this with no answers. I didn't know anything about ROMs or kernals or recovery until this phone wanted to update. I followed the instructions and found myself in TWRP and thought my phone had been infected with a virus. That was around October 2015. It took me months more to find XDA, months more to figure out where to post a question, and months more to get information. I manged to flash the MOAR rom in July, but didn't see that it was from 2012, so the developer won't answer any questions I have. I couldn't figure out how to restore what I had before and subsequently deleted the files from my exSd.
My frustration is that I didn't get into this because I was interested in it or knew about the workings of operating systems and wanted to make my phone awesome. I thought I had to in order to make it work right. I was seduced by ideas of having an awesome phone when I read about custom ROMs while trying to find one. The problem is, I don't understand the power I have in order to use it.
Sorry to ramble. I do thank you for your information. I also welcome ( beg for) any help or suggestions about what works with what devices.
Thank you againView attachment 3891814
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
Here, may I suggest the ROM linked below?
http://forum.xda-developers.com/showthread.php?t=3033797
This is OctOS Marshmallow, OctOS is pretty much the most stable custom available, they don't try to cram it full of every feature they can, it isn't featureless, its just that their focus is stability and not the bells and whistles. I've used OctOS on my d2vzw S3 for 2 years without a single issue. In fact, I've liked the ROM so much I joined the OctOS team as a beta tester(kinda pointless because even the test builds are rock solid, takes the fun out of testing). I've even built a system for one of the developers on the team to use for developing ROMs. Anyway, that's all unimportant.
Try the ROM, I think you'll like it. It requires using the advanced wipes in recovery to wipe System and Data partitions before flashing the ROM to do a "clean install". I'll help you with that if you need it. I hope you enjoy.
---------- Post added at 11:12 AM ---------- Previous post was at 10:56 AM ----------
Mablemae said:
Wow, you are my hero! I don't know how to thank you enough.
First off, I promise I have put in lots of work on my own trying to find answers. Also, I may be underestimating my own understanding.
As far as ROMs, I haven't worked this hard to give up now! Not only do I want custom, I want to know what kernel does, what a governor does, what mods are. I think everyone else thought I wanted to be told what system to install while I only wanted to be educated so I could decide for myself. Basically, I'm asking for a teacher
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
Kernels are what integrate your hardware with your software, the kernel is what loads all the software that is installed and the kernel has to be made to work with your specific hardware.
Custom kernels can be used to do things like overclock your processor and your graphics processor to increase performance. Governors do just that, they govern how your processor responds to your usage, such as you can set it to run full speed at all times or you can set it to only respond with full speed when you need it. There are different governors and they each perform differently, it just depends on which ones were included in the kernel. I could explain it all but you wouldn't understand it until you've used it a while and gotten the feel for what they do. There are other things you can do with kernels but its pretty technical and you'll probably never use/need most of what it does. The OctOS ROM actually comes with its own Kraken kernel and the Kernel Auditor app built in. Other ROMs don't have their own kernel, they typically use the stock CM kernel. There are also other stand alone kernels for d2spr that you could use, you just have to verify which kernels work with which ROMs(kit kat kernel for kit Kat ROMs, lollipop kernel for lollipop, etc..., some kernels can be used with kit kat, lollipop and marshmallow, you just have to read about each kernel to see what they work with).
Mods are modifications, not all devices can use all mods, mods can be all kinds of things major and minor. A mod can be absolutely any part of a ROM that someone modifies for whatever reason. There isn't any one thing I can put my finger on and say "this is a mod" that would help you understand what they are. Just know that there are mods that only work on specific devices and mods that can be used by many or even all devices, you just have to know which are which.
By the way, I figured you'd stay with custom, everyone does when they get bitten by the android bug, lol.
Thank you. My dilemma in finding one is that I read where you need a certain firmware or modem. How do I know if I need it? I looked at the section in my phone that I sent the pic of. Where is the information I need, and how do I know if I can install something?
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Thank you. My dilemma in finding one is that I read where you need a certain firmware or modem. How do I know if I need it? I looked at the section in my phone that I sent the pic of. Where is the information I need, and how do I know if I can install something?
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't know of the d2spr devices requiring flashing a modem. Can you give me a link to see what you're talking about? If not I'll see if I can find what you're talking about. Or I might get in private chat with the d2spr guys on the OctOS team to see if they know.
You do know that there is a d2spr device and the d2spr refresh device, don't you? You can't use the d2spr refresh stuff, that's a different variant. I think it is the one with the certain modem because it is a tri band device I think.
Droidriven said:
I don't know of the d2spr devices requiring flashing a modem. Can you give me a link to see what you're talking about? If not I'll see if I can find what you're talking about. Or I might get in private chat with the d2spr guys on the OctOS team to see if they know.
You do know that there is a d2spr device and the d2spr refresh device, don't you? You can't use the d2spr refresh stuff, that's a different variant. I think it is the one with the certain modem because it is a tri band device I think.
Click to expand...
Click to collapse
I am going to try out the one you sent me the link for. If I think I want more bells and whistles, I'll let you know and see what else is available. I have no reason to look elsewhere. I'm just so thankful for your help. Do you have a link where I can send money to your team or an address where I can send a pie? Lol
Sent from my SPH-L710 using XDA-Developers mobile app
Droidriven said:
Here, may I suggest the ROM linked below?
http://forum.xda-developers.com/showthread.php?t=3033797
This is OctOS Marshmallow, OctOS is pretty much the most stable custom available, they don't try to cram it full of every feature they can, it isn't featureless, its just that their focus is stability and not the bells and whistles. I've used OctOS on my d2vzw S3 for 2 years without a single issue. In fact, I've liked the ROM so much I joined the OctOS team as a beta tester(kinda pointless because even the test builds are rock solid, takes the fun out of testing). I've even built a system for one of the developers on the team to use for developing ROMs. Anyway, that's all unimportant.
Try the ROM, I think you'll like it. It requires using the advanced wipes in recovery to wipe System and Data partitions before flashing the ROM to do a "clean install". I'll help you with that if you need it. I hope you enjoy.
---------- Post added at 11:12 AM ---------- Previous post was at 10:56 AM ----------
Kernels are what integrate your hardware with your software, the kernel is what loads all the software that is installed and the kernel has to be made to work with your specific hardware.
Custom kernels can be used to do things like overclock your processor and your graphics processor to increase performance. Governors do just that, they govern how your processor responds to your usage, such as you can set it to run full speed at all times or you can set it to only respond with full speed when you need it. There are different governors and they each perform differently, it just depends on which ones were included in the kernel. I could explain it all but you wouldn't understand it until you've used it a while and gotten the feel for what they do. There are other things you can do with kernels but its pretty technical and you'll probably never use/need most of what it does. The OctOS ROM actually comes with its own Kraken kernel and the Kernel Auditor app built in. Other ROMs don't have their own kernel, they typically use the stock CM kernel. There are also other stand alone kernels for d2spr that you could use, you just have to verify which kernels work with which ROMs(kit kat kernel for kit Kat ROMs, lollipop kernel for lollipop, etc..., some kernels can be used with kit kat, lollipop and marshmallow, you just have to read about each kernel to see what they work with).
Mods are modifications, not all devices can use all mods, mods can be all kinds of things major and minor. A mod can be absolutely any part of a ROM that someone modifies for whatever reason. There isn't any one thing I can put my finger on and say "this is a mod" that would help you understand what they are. Just know that there are mods that only work on specific devices and mods that can be used by many or even all devices, you just have to know which are which.
By the way, I figured you'd stay with custom, everyone does when they get bitten by the android bug, lol.
Click to expand...
Click to collapse
I just want to be sure I'm doing the right thing. I went to the link you sent and clicked the link for "stable", then "Samsung", then s3 lte, then sprint gs3. I assume that since you have my current phone information to know what I'm running, you gave me something that is compatible and doesn't need me to modify any of my current settings in order to install, but I'm just double checking. Also, how important is gapps if I use titanium to backup any apps I want to carry over? I've never downloaded gapps before a wipe
Sent from my SPH-L710 using XDA-Developers mobile app
Droidriven said:
Here, may I suggest the ROM linked below?
http://forum.xda-developers.com/showthread.php?t=3033797
This is OctOS Marshmallow, OctOS is pretty much the most stable custom available, they don't try to cram it full of every feature they can, it isn't featureless, its just that their focus is stability and not the bells and whistles. I've used OctOS on my d2vzw S3 for 2 years without a single issue. In fact, I've liked the ROM so much I joined the OctOS team as a beta tester(kinda pointless because even the test builds are rock solid, takes the fun out of testing). I've even built a system for one of the developers on the team to use for developing ROMs. Anyway, that's all unimportant.
Try the ROM, I think you'll like it. It requires using the advanced wipes in recovery to wipe System and Data partitions before flashing the ROM to do a "clean install". I'll help you with that if you need it. I hope you enjoy.
---------- Post added at 11:12 AM ---------- Previous post was at 10:56 AM ----------
Kernels are what integrate your hardware with your software, the kernel is what loads all the software that is installed and the kernel has to be made to work with your specific hardware.
Custom kernels can be used to do things like overclock your processor and your graphics processor to increase performance. Governors do just that, they govern how your processor responds to your usage, such as you can set it to run full speed at all times or you can set it to only respond with full speed when you need it. There are different governors and they each perform differently, it just depends on which ones were included in the kernel. I could explain it all but you wouldn't understand it until you've used it a while and gotten the feel for what they do. There are other things you can do with kernels but its pretty technical and you'll probably never use/need most of what it does. The OctOS ROM actually comes with its own Kraken kernel and the Kernel Auditor app built in. Other ROMs don't have their own kernel, they typically use the stock CM kernel. There are also other stand alone kernels for d2spr that you could use, you just have to verify which kernels work with which ROMs(kit kat kernel for kit Kat ROMs, lollipop kernel for lollipop, etc..., some kernels can be used with kit kat, lollipop and marshmallow, you just have to read about each kernel to see what they work with).
Mods are modifications, not all devices can use all mods, mods can be all kinds of things major and minor. A mod can be absolutely any part of a ROM that someone modifies for whatever reason. There isn't any one thing I can put my finger on and say "this is a mod" that would help you understand what they are. Just know that there are mods that only work on specific devices and mods that can be used by many or even all devices, you just have to know which are which.
By the way, I figured you'd stay with custom, everyone does when they get bitten by the android bug, lol.
Click to expand...
Click to collapse
Ok here goes. I'm about to do this. I will be back shortly with how it went either from this phone or my backup phone.
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Ok here goes. I'm about to do this. I will be back shortly with how it went either from this phone or my backup phone.
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
Tell me what you are flashing first and I'll verify it for you if you want.
Droidriven said:
Tell me what you are flashing first and I'll verify it for you if you want.
Click to expand...
Click to collapse
I flashed this and the screen flashed the whole time with the TWRP screen and the file images over it. I could see an "ok" option and pressed it. When I went to reboot, TWRP said there was no os installed, so I went back and wiped and reinstalled MOAR. Now I can't install titanium. I get some kind of error. Did I lose root?
Droidriven said:
Tell me what you are flashing first and I'll verify it for you if you want.
Click to expand...
Click to collapse
I didn't download the md5 file because I didn't see one
Mablemae said:
I didn't download the md5 file because I didn't see one
Click to expand...
Click to collapse
The file may have its own md5 sum attached to it instead of a separate md5.
As for the issue with Titanium Backup, you don't need root to install it but you do need root to restore the stuff you backed up in Titanium Backup.
When I asked about what you flashed, I was asking for links to what you used so I could go there to where you got it and see if its for your device or not and what might need to be done with it to make sure it comes out right, in other words, I'll check to see if requires the modem you spoke of.
If you think you lost root, download SuperSU.zip and flash that in recovery like you did the ROM and you should have root.
When I ask you questions I need the answer, not partial responses. If you don't give me the answers I need about exactly what you're using and what you're doing, it makes understanding any issues you might have a little harder to understand and troubleshoot. Work with me and I'll work with you.
Mablemae said:
I didn't download the md5 file because I didn't see one
Click to expand...
Click to collapse
That screenshot you gave me is not a ROM. That is a flashable zip to fix your APNs so you that your mobile data works.
This should be your ROM.
https://www.teamoctos.com/download/M_release/d2spr/OCT-M-R2-6.0.1-20160812-d2spr.zip
For the gapps you'll need, do a google search for:
Open Gapps
When you get to their page, select ARM(not ARMx64), then select 6.0, then select mini, pico or nano packages then download.
You have to flash the Gapps with your ROM, they are system apps, apps you install aren't system app, they're user apps, different animal. When flashing a ROM different than what you have you can't use Titanium Backup to back up system apps because they won't restore properly in your new ROM, especially when going from one android version to another.
Flash the Gapps and then only restore apps that you downloaded from Playstore.
The link I gave you was to the thread for your ROM, it should the info you need to know to flash it.
By the way, when you flashed and it said you had no OS, that's because of the advanced wipe when you wiped system partition in recovery, I told you that it removes your OS and that you'll have to flash the ROM AFTER doing the wipe, you can't flash and then do the wipe, that wipes what you flashed.
Droidriven said:
That screenshot you gave me is not a ROM. That is a flashable zip to fix your APNs so you that your mobile data works.
This should be your ROM.
https://www.teamoctos.com/download/M_release/d2spr/OCT-M-R2-6.0.1-20160812-d2spr.zip
For the gapps you'll need, do a google search for:
Open Gapps
When you get to their page, select ARM(not ARMx64), then select 6.0, then select mini, pico or nano packages then download.
You have to flash the Gapps with your ROM, they are system apps, apps you install aren't system app, they're user apps, different animal. When flashing a ROM different than what you have you can't use Titanium Backup to back up system apps because they won't restore properly in your new ROM, especially when going from one android version to another.
Flash the Gapps and then only restore apps that you downloaded from Playstore.
The link I gave you was to the thread for your ROM, it should the info you need to know to flash it.
By the way, when you flashed and it said you had no OS, that's because of the advanced wipe when you wiped system partition in recovery, I told you that it removes your OS and that you'll have to flash the ROM AFTER doing the wipe, you can't flash and then do the wipe, that wipes what you flashed.
Click to expand...
Click to collapse
Yes I wiped, then flashed. This is the path I took that got me to what I flashed
http://forum.xda-developers.com/showthread.php?t=3033797.
On the first page in the thread, I found a link that said it was stable and followed it for my phone.
I only backup user apps to titanium because I did read that system apps can cause problems when carried over to a different rom. Sorry about the lack of information.
Mablemae said:
Yes I wiped, then flashed. This is the path I took that got me to what I flashed
http://forum.xda-developers.com/showthread.php?t=3033797.
On the first page in the thread, I found a link that said it was stable and followed it for my phone.
I only backup user apps to titanium because I did read that system apps can cause problems when carried over to a different rom. Sorry about the lack of information.
Click to expand...
Click to collapse
OK, I'll check out some details and see what might have happened when you flashed. Doing the wipes a d then flashing ROM then Gapps should have worked with no issue, let me do some digging to see why it didn't.
Droidriven said:
OK, I'll check out some details and see what might have happened when you flashed. Doing the wipes a d then flashing ROM then Gapps should have worked with no issue, let me do some digging to see why it didn't.
Click to expand...
Click to collapse
Stop digging. The apps started downloading, but I'm going to try what you sent me tonight when I get off
Mablemae said:
Stop digging. The apps started downloading, but I'm going to try what you sent me tonight when I get off
Click to expand...
Click to collapse
Ok, I'm chatting with my OctOS colleagues, some of them have had d2spr, hopefully they remember whether there is anything special you need to do. I have helped others with d2spr but its been a year or more so I don't remember details.
Related
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
Hey guys,
I just got a few questions with this,
Will i lose my apps, theme and such when installing only a ROOT?
Also what do you guys prefer as ROOT method goes, Chainfire and Odin?
I've seen a ROOT BAT program a while ago that realy did everything for you, i just can't remember the name at the moment...
With that i would also like to ask what happens if i update my device? Will i still be able to update it when Samsung pushes a new update ?
Would i need a custom flash recovery? I used to have a phone wich i did it on, But as this is more of my expensiver phone i aint looking to realy risk it. and due all my apps info etc, has well over 150 apps.
Thanks everybody
Bump,
Sorry if nagging but i'm kinda in a rush, if anyone could help me a little?
I basicly know how you most likely root and stuff, just wanna be sure about a few things and what program/apk is best to get into the S3 at 4.3 firmware
Dr.Luigi said:
Hey guys,
I just got a few questions with this,
Will i lose my apps, theme and such when installing only a ROOT?
Click to expand...
Click to collapse
You might lose data.
Few things can be saved, because you have an official (so unrooted) device.
Also what do you guys prefer as ROOT method goes, Chainfire and Odin?
Click to expand...
Click to collapse
Odin is needed, Chainfire root is the most famous method.
I've seen a ROOT BAT program a while ago that realy did everything for you, i just can't remember the name at the moment...
Click to expand...
Click to collapse
Personally I did root with an automatized software, called Unlock Flash.
The better one is Framaroot, but I don't know how it works.
With that i would also like to ask what happens if i update my device? Will i still be able to update it when Samsung pushes a new update ?
Click to expand...
Click to collapse
You'll lost Samsung warranty (no more assistance support, excluded mine and use for software problems [emoji6]), update check and the access to some proprietary apps (You shouldn't be able to download/update from Galaxy Apps).
Normally when you root the device, a CWM custom recovery is included, otherwise you can simply flash via Odin the excellent Philz Recovery, so you'll be able to flash a new Samsung-based rom (ARHD, ArchiPort, Omega, Imperium... aborting the limited stock) or try the greatful AOSP roms (CyanogenMod, Omnirom, PacRom, etc.).
Also custom kernels (BOEFFLA, Googy Max, ArchiKernel and some others, I prevent to cite you outdated ones) and mods (everything!).
Would i need a custom flash recovery? I used to have a phone wich i did it on, But as this is more of my expensiver phone i aint looking to realy risk it. and due all my apps info etc, has well over 150 apps.
Thanks everybody
Click to expand...
Click to collapse
Highly recommended, as I said you need this to install a new rom and any other zip file.
For the rest... I haven't understood you.
Can you explain better last things?
Simone98RC said:
You might lose data.
Few things can be saved, because you have an official (so unrooted) device.
Odin is needed, Chainfire root is the most famous method.
Personally I did root with an automatized software, called Unlock Flash.
The better one is Framaroot, but I don't know how it works.
You'll lost Samsung warranty (no more assistance support, excluded mine and use for software problems [emoji6]), update check and the access to some proprietary apps (You shouldn't be able to download/update from Galaxy Apps).
Normally when you root the device, a CWM custom recovery is included, otherwise you can simply flash via Odin the excellent Philz Recovery, so you'll be able to flash a new Samsung-based rom (ARHD, ArchiPort, Omega, Imperium... aborting the limited stock) or try the greatful AOSP roms (CyanogenMod, Omnirom, PacRom, etc.).
Also custom kernels (BOEFFLA, Googy Max, ArchiKernel and some others, I prevent to cite you outdated ones) and mods (everything!).
Highly recommended, as I said you need this to install a new rom and any other zip file.
For the rest... I haven't understood you.
Can you explain better last things?
Click to expand...
Click to collapse
Well i would only be intrested in ROOT if i can keep all of my files, apps, widgets and such,
I would have done a new ROM if i wouldnt have had so many apps, it would take hours if not days to get everything back as it used to be would be a rather pain in the ***.
Thanks for your help!
Been a while when i unlocked my old device and rommed it undervoltaged it etc etc.
Dr.Luigi said:
Well i would only be intrested in ROOT if i can keep all of my files, apps, widgets and such,
I would have done a new ROM if i wouldnt have had so many apps, it would take hours if not days to get everything back as it used to be would be a rather pain in the ***.
Thanks for your help!
Been a while when i unlocked my old device and rommed it undervoltaged it etc etc.
Click to expand...
Click to collapse
My same problem: too many apps to be restored.
With MyBackupsPRO, the only working without root permissions, you can only keep some settings, contacts, SMS and MMS, then all your apps and games... but without any relative data.
Because as I said you're on an unrooted/official system.
I think you are using an external SD for documents and multimedia files, when you run the first start of your custom rom (highly recommend for the updates, instead the limited stock), be sure that the "Restore data from Google" option is checked.
A discrete help for you, better than nothing.
You have to think that when you did root, backups will be complete, via the greatful Titanium Backup or via recovery with Nandroid backup (my words should be useless if you already have experience with an old device).
Good hacking
As Samsung-based roms I suggest you Android Revolution HD 4.3 or ArchiPort to get the new and officially unsupported 4.4 system.
Pro:
-Compatibility with other Samsung devices;
-Much better camera stabilization than AOSP roms.
Con:
-Touchwiz is heavy for RAM memory and CPU performance;
-Many AOSP functions are completely removed or altered.
As AOSP rom I suggest you CyanogenMod 11, the M builds to have a more stable system, the nightlies for daily updates and less (but always enough) stability.
Pro:
-Latest updates daily/monthly available;
-Many features, AOSP and Cyanogen specific;
-Fully configurable, launcher can be completely replaced, at opposite of Samsung-based roms;
-Greater performance than Samsung-based roms.
Con:
-Some little bug;
-Poor compatibility with Samsung devices and proprietary apps.
As custom kernel, no better one than BOEFFLA: obviously OC and UV support, then lots of functions such "Touch to Wake", a great audio engine, zRAM support, a rich choice of governors and schedulers... it's available for Samsung and many AOSP roms.
Simone98RC said:
My same problem: too many apps to be restored.
With MyBackupsPRO, the only working without root permissions, you can only keep some settings, contacts, SMS and MMS, then all your apps and games... but without any relative data.
Because as I said you're on an unrooted/official system.
I think you are using an external SD for documents and multimedia files, when you run the first start of your custom rom (highly recommend for the updates, instead the limited stock), be sure that the "Restore data from Google" option is checked.
A discrete help for you, better than nothing.
You have to think that when you did root, backups will be complete, via the greatful Titanium Backup or via recovery with Nandroid backup (my words should be useless if you already have experience with an old device).
Good hacking
As Samsung-based roms I suggest you Android Revolution HD 4.3 or ArchiPort to get the new and officially unsupported 4.4 system.
Pro:
-Compatibility with other Samsung devices;
-Much better camera stabilization than AOSP roms.
Con:
-Touchwiz is heavy for RAM memory and CPU performance;
-Many AOSP functions are completely removed or altered.
As AOSP rom I suggest you CyanogenMod 11, the M builds to have a more stable system, the nightlies for daily updates and less (but always enough) stability.
Pro:
-Latest updates daily/monthly available;
-Many features, AOSP and Cyanogen specific;
-Fully configurable, launcher can be completely replaced, at opposite of Samsung-based roms;
-Greater performance than Samsung-based roms.
Con:
-Some little bug;
-Poor compatibility with Samsung devices and proprietary apps.
As custom kernel, no better one than BOEFFLA: obviously OC and UV support, then lots of functions such "Touch to Wake", a great audio engine, zRAM support, a rich choice of governors and schedulers... it's available for Samsung and many AOSP roms.
Click to expand...
Click to collapse
Thanks for the great help,
I aint realy sure yet realy,
But isnt there a way you can simple backup almost everything with the PC?
I thought that was faster, then root it and get those back up on the phone with the PC?
Youve made me thinking realy as my phone was getting slower, Samsung OS isnt that great quiet slow indeed,
I might just drop a few games i dont play realy, so i can get my faster phone back as it used to be.
I used to love tweaking my phone realy, till it broke due rain, was a quiet cheap phone 150e or so.
Do you mind giving your SKYPE or Steam? so i could ask you there, Its been 2 years when i did this, some are kinda floating around in my head but i just cant remember it all anymore.
http://forum.xda-developers.com/gal...msung-galaxy-s3-unified-toolkit-v8-0-t1979290
This is what i meant, Its simple and all in 1, just aint sure if its still up to date?
Via ADT Development Tool, you can do the "adb backup" command, but I think it will include the bootloader, so you'll restore the official and unrooted device state.
But I'm not sure, I never used to backup via PC.
Games are almost innocue, except for notification services who consume a bit of resources.
Can you tell me the heavier apps you're using?
According to your words, having too many apps you're not very satisfied about your performance... or I'm wrong?
Simone98RC said:
Via ADT Development Tool, you can do the "adb backup" command, but I think it will include the bootloader, so you'll restore the official and unrooted device state.
But I'm not sure, I never used to backup via PC.
Games are almost innocue, except for notification services who consume a bit of resources.
Can you tell me the heavier apps you're using?
According to your words, having too many apps you're not very satisfied about your performance... or I'm wrong?
Click to expand...
Click to collapse
Ye it used to be quiet a bit faster, Might be Samsung OS i forgot the name of the OS but anyhow, wizard or something,
Oh well, i will just do it i guess and i will see on the road what apps i need, the rest clearly seems that i dont need em if i never use em.
I'm guessing that the best would be Clockwork recovery and the SUroot? together with cyanogen ROM and buffalo.
As apps goes its basicly my home screen wich has quiet some widgets and such, all diffrent apps, in some folders like 100 apps etc.
Dr.Luigi said:
Ye it used to be quiet a bit faster, Might be Samsung OS i forgot the name of the OS but anyhow, wizard or something,
Oh well, i will just do it i guess and i will see on the road what apps i need, the rest clearly seems that i dont need em if i never use em.
I'm guessing that the best would be Clockwork recovery and the SUroot? together with cyanogen ROM and buffalo.
As apps goes its basicly my home screen wich has quiet some widgets and such, all diffrent apps, in some folders like 100 apps etc.
Click to expand...
Click to collapse
SuperSU is included in CF-Root and so is the most known, but Superuser (from Clockworkmod, the other Superuser is obsolete!) is a great open source alternative.
The best recovery is Philz, always based on CWM, but with extra and TWRP functions.
CyanogenMod yes, is the better choicr and also the easiest choice for root newbies.
Ps Buffalo is a kernel? If it's true, try BOEFFLA, is considered absolutely the best.
Simone98RC said:
SuperSU is included in CF-Root and so is the most known, but Superuser (from Clockworkmod, the other Superuser is obsolete!) is a great open source alternative.
The best recovery is Philz, always based on CWM, but with extra and TWRP functions.
CyanogenMod yes, is the better choicr and also the easiest choice for root newbies.
Ps Buffalo is a kernel? If it's true, try BOEFFLA, is considered absolutely the best.
Click to expand...
Click to collapse
Well i meant boeffla of course, Well i cant get it to work, What are the keys to get into TWRP recovery?
As in download mode it tells me its custom, but i cant get into it..
tryed quiet a few combis already
Dr.Luigi said:
Well i meant boeffla of course, Well i cant get it to work, What are the keys to get into TWRP recovery?
As in download mode it tells me its custom, but i cant get into it..
tryed quiet a few combis already
Click to expand...
Click to collapse
Edit:
Tryed again, i cant reboot if i did it would get the old recovery back, so in a push method it worked,
Now SuperSU, i might get a ROM but aint sure yet, Do kernels work on the stock rom aswell?
Dr.Luigi said:
Edit:
Tryed again, i cant reboot if i did it would get the old recovery back, so in a push method it worked,
Now SuperSU, i might get a ROM but aint sure yet, Do kernels work on the stock rom aswell?
Click to expand...
Click to collapse
Yes, BOEFFLA works also on stock rom (make sure to flash the correct zip file)... but I haven't understood your problem: can't reboot, old recovery back... what?
Simone98RC said:
Yes, BOEFFLA works also on stock rom (make sure to flash the correct zip file)... but I haven't understood your problem: can't reboot, old recovery back... what?
Click to expand...
Click to collapse
Ye nevermind that,
The problem is when i flashed my recovery, that when i reboot it switched automaticly back to the orginal stock recovery,
Only way to repair this was to not reboot, but goto the Philz recovery directly and reinstall the recovery program,
Also rooted it now,
So i can simple install Boefflo on my S3 international, With stock rom and ROOT, philz recovery?
If so that would be sweet ^^
As it should be more sufficient as far as battery goes, and a small overclock to like 1.6Ghz is reasonable ive heard,
1.8 is to high if i can believe those on some forums.
Since the last stable release you can overclock up to 1704 Mhz... and no more 1.5 Ghz step, I don't know the reason.
As I said, BOEFFLA works almost on every rom, but you habe to flash a different zip file for Samsung and AOSP roms.
Why can't you get a custom recovery? Are you sure to flash them reproducing properly the reported Odin guide (what to check in app, where to write file, etc.)?
It's a strange problem, rom "might" be cause by replacing the new recovery with the stock one, I think, but I'm not absolutely sure.
Simone98RC said:
Since the last stable release you can overclock up to 1704 Mhz... and no more 1.5 Ghz step, I don't know the reason.
As I said, BOEFFLA works almost on every rom, but you habe to flash a different zip file for Samsung and AOSP roms.
Why can't you get a custom recovery? Are you sure to flash them reproducing properly the reported Odin guide (what to check in app, where to write file, etc.)?
It's a strange problem, rom "might" be cause by replacing the new recovery with the stock one, I think, but I'm not absolutely sure.
Click to expand...
Click to collapse
Well like i said i've fixed that,
The standard way to flash doesnt work, As once i get booted in Samsung ROM, It fixes it, So you have to goto your Recovery immeaditly when youve flashed it, and flash it again in the custom recovery, and then it does work.
Well i will see, aint sure yet if i will do it the kernel and romming.
Thanks for the help
Dr.Luigi said:
Well like i said i've fixed that,
The standard way to flash doesnt work, As once i get booted in Samsung ROM, It fixes it, So you have to goto your Recovery immeaditly when youve flashed it, and flash it again in the custom recovery, and then it does work.
Well i will see, aint sure yet if i will do it the kernel and romming.
Thanks for the help
Click to expand...
Click to collapse
Here is also a great kernel. Check this out http://forum.xda-developers.com/gal...04-googy-max2-kernel-2-3-1-cm-camera-t2517875
I am in NO WAY affiliated with any of the ROM developers mentioned below nor am I a developer at all. I discovered this by trial and error and decided to share with the community. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE!!!!!!!!!!!!!!! Everything mentioned worked for me and me alone. I will NOT guarantee it will work for you. I cannot offer any support concerning why it will not work for you and NEITHER DOES THE DEVS AND THEIR VZW ROMs!!!! SO DO NOT CLOG THEIR THREADS WITH QUESTIONS ABOUT WHY THEIR ROM WON'T WORK WITH YOUR SPRINT NOTE 3!!!!!
THIS IS FOR 4.4.X ONLY!!! I am currently on NC5 baseband so I have no idea if it will work with NH7. It should, but again, I can only speak for me and my setup. SMS, MMS (with 3rd party app to send possibly) and GPS all work for me. Calls are working as well.
EDIT: Ok folks, I have decided to go ahead and post the how to anyway even though I have gotten no response from any of the devs of the Verizon ROMs mentioned below. I assume they are working on new projects and do not have time to mess with this discovery. They also do this for free and have lives to live just like the rest of us. If at any time they want me to remove this I will, purely out of respect for what they have done for all of us. With that in mind, THE DEVS HAVE NO TIME TO SUPPORT THIS SO PLEASE DO NOT CLOG UP THEIR THREADS WITH QUESTIONS RELATED TO THEIR VZW ROMS WORKING ON SPRINT DEVICES!
What you will need: A rooted N900P Note 3 device with a custom recovery installed. I am currently using the latest Philz Recovery so I cannot say for sure if using TWRP will cause this not to work on your device. I don't think it will matter, but to be safe I can only speak for Philz Recovery right now.
If you are on TWRP and want to switch to Philz (many have suggested doing so regardless if you try this or not) keep in mind Philz is not being updated now ( I think ) so the latest build for KitKat is 6.12.9 as far as I know and can be found HERE for the N900P. If you don't know how to change recoveries you probably shouldn't be trying this at all. Research it and you will find out how to do it. Or ask around. You will also need to use a 3rd party MMS app possibly to send MMS messages. On Eclipse it seems to work using the stock Messenger, but on Alliance I had to use Textra to send MMS.
Step 1: BACK UP YOUR CURRENT SETUP!!!! I cannot stress how important this is with ANY ROM flashing or file changing. I have been caught with my pants down before and it really sucks when you have to Odin back to stock because you did not do a Nandroid backup. That is the main purpose of having a custom recovery like Philz or TWRP or CWM is to completely back up your device. Most or all offer EFS backups as well. Also keep a copy of said backup on an external device in case you accidentally wipe your EXT card. Don't think it's not possible, I have done it on other devices because I thought I was cool and could wipe real fast and flash.
Step 2: Acquire the stock kernel for your build/baseband ( Mine is NC5 ) in a flashable .zip. The NCS stock kernel can be found HERE OR you can use Lean Kernel 3.10 ( which I am using) that can be found HERE. MAKE SURE YOU GRAB THE HTLESPR version!!!
Step 3: Download the Verizon Touchwiz ROM of your choice. I have successfully tested this on Eclipse and Alliance. Eclipse can be found HERE Make sure you use the correct build ( 4.4.X ) because it needs to match your baseband. In other words, if you are currently on 4.4.2 or 4.4.4 use the same ROM build that they offer. Eclipse 2.0.1 is what I am using. Alliance ROM is HERE Those are the only 2 I have tried thus far. Experiment if you dare, but the others should work as well ( in theory).
Step 4: Grab the flashable app APN Backup and Restore provided HERE THANKS TO FREEZA!!!! You will need this to get the Sprint APNs on your device. More on how do do this later.
Step 5: Take a deep breath. While still on your Sprint ROM, update your PRL and Profile for good measure because those options will not be in settings on the VZW ROMs. Relax, it will be ok.
Step 6: Boot into recovery, do a full wipe like you would any other time flashing a new ROM. Flash the ROM of choice, then flash the Sprint kernel of choice. If you do not get any errors, reboot system and wait...........and wait some more. It will take a few min for either ROM to boot. If you see the Eclipse or Alliance splash screen (boot animation) you are probably ok. Do not panic at the 3 min mark and shut down. Just let it do it's thing. You should eventually see the beginning setup screen. If after 8-10 min you still are seeing the animation it probably is in a bootloop. It may not work but you can simply power down and boot back into recovery and restore your backup, or try again flashing the kernel first, then ROM, then kernel again then boot into system and wait again. Just use some patience.
Step 7: If you made it to this step, congrats, you have booted a VZW ROM onto your Sprint Note 3. But we have more to do. After you set up wifi and gone through the setup menu you may see some Verizon related errors pop up. Just ignore them for now. Those apps can be frozen using TiBu after completely done as a cleanup measure. Boot back into recovery ( On Eclipse you will have to do this using vol up/home/power buttons because there is no 4 way reboot menu. This can be added with Xposed and Wanam later as well). Flash the APN Backup and Restore app ( this could also be done when you flashed the ROM I suppose) and reboot. which will put the APN backup & restore app into your /system/app directory and the SprintAPNxXML file onto your sdcard. Once done installing, boot back up and launch the application, Ignore the warning screen you get from first launch, then press menu and select "Disable ICS check." Once done, exit the app and load it again, then choose "Delete APNs" and select yes to the following prompt. Once done, go ahead and tap Restore APNs, and select the SprintAPNsXML from the prompt and select no to the duplicate check. IF THIS DOES NOT WORK THE FIRST TIME- Move the app from /system/app directory to /system/priv-app/ directory and change permissions to rwx/rwx/rwx and reboot. Then try to Delete APN, then try to Add APNs using the provided SprintAPNxXML file in the app. This will add Sprint APNs.
Step 8: Go into settings/more settings/Mobile Networks/Access Point Names and choose the appropriate one for your area. I chose APN2 LTE Internet n.ispsn. You should now have data icon showing. This worked for me, hopefully it worked for you. I have seen it switch between LTE and 3G so I know it is handing off correctly. Make sure Network Mode is CDMA/LTE/EVDO as well. I haven't tested on the road yet, but will tonight. But it has been working flawlessly for me on local towers.
Step 9: You will need to add Sprint apps you were using, including voicemail. Install Titanium Backup and freeze Verizon related apps if you want. Also you will notice in settings your phone will show to be a N900V instead of N900P due to the Verizon ROM. Don't panic.
Step 10: Profit! At this point you should be able to tinker with the ROMs according to what the threads offer. I know Eclipse has it's own app to customize some things. But Xposed will work as well. I have no idea if Hotspot works or any of that stuff, I do not use it. Alliance has a ton of customization settings and apps built in, including themes. Some minor tweaks haven't worked, but most have. Eclipse has actual AOSP functionality baked in. ENJOY!! I will try to answer as many questions as i can, but again, please DO NOT clog up the threads of those great ROMs with questions, the devs do not, as far as I know, support this method and will not be able to help you with your Sprint device.
EDIT: When you connect to your PC via USB for the first time you may have to toggle MTP on and off to get it to be recognized in Explorer. It will most likely say N900V when you get connected. Also on Alliance a couple of Verizon apps will try to install on your PC. You can cancel them.
Screenshots
MUCH THANKS!!!
Sprint side: Freeza for the APN Backup and Restore app as well as all you have done for the Sprint Note 3!! LMMT for the NC5 kernel thread! Phil3759 for Philz Recovery for the N900P
Verizon Side: Nitroglycerine33 for all he has done for the community. My first attempt at flashing was an Eclipse ROM. Cannot say enough about what he has done! Beanstown106 for the hard work on all the Verizon devices and now along with Team Alliance they continue to dominate!
Multiple Devices: Imoseyon for his great Lean Kernels!! I have run them on every device so far. They just get better and better.
All the devs on all the devices deserve a huge thanks from all of us! Without them none of this would be possible!!
this would be cool to know, and give us more choices at ROM flashing time
Is it me or is XDA running real slow today?? Even on Tapatalk.
Anyway, so far I have SMS, MMS and GPS working smooth. Really was simple. No need to decompile or change the ROM itself. As long as the bootloaders match (4.4.2 to 4.4.2 etc) it works. Thanks to an earlier post by Freeza dealing with APN restore everything works thus far. Really hope Nitro gives me the go ahead to create a thread or at least post a how to with links to his site. If you want real AOSP feel on a TW ROM, Eclipse is the way to go. I ran this all the time on my VZW Note 3.
Also will be trying the same with a couple of other VZW ROMs I once loved as well. Stay tuned. :good:
Looks like I will have to post the How To here anyway so I am testing another VZW ROM now (Alliance) and if all goes well I will add the directions to this thread in the OP.
All the way to Chicago and back with no data issues. Have a hard time believing nobody knew we could do this.
Real_JESRadio said:
All the way to Chicago and back with no data issues. Have a hard time believing nobody knew we could do this.
Click to expand...
Click to collapse
I had no clue! I knew the devices were very similar but figured if it were possible to use VZW ROMs across devices, I'd have started months ago! Thanks for the How To, I'll be giving it a shot this evening. Cheers! :beer:
Sent from my SM-G900P using XDA Free mobile app
sixshooterz said:
I had no clue! I knew the devices were very similar but figured if it were possible to use VZW ROMs across devices, I'd have started months ago! Thanks for the How To, I'll be giving it a shot this evening. Cheers! [emoji481]
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Cool. Hope it goes well. Must be the CDMA thing. At least it gives us more options. Eclipse is working so good I can't get away from it lol
Jasmine 2.4.1 works
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Hyperdrive RLS8
Vzw lte b4 on/off
are you able to get new LTE Bands (4 ,13) so that n900p can operate on verizon network on MVNO?
or are you able to VZW LTE B4 ON/OFF to enable band 4 on?
This sounds awesome! Thank you for posting! I will have to try this out this weekend.
Latest one I tried was vn Rom 7.2 and Norma beta 6 both good.
Sorry these 2 are not Verizon but are for 9005 and they do work.
Anyone flash T-Mobile roms on this phone?
twisteddroid said:
Anyone flash T-Mobile roms on this phone?
Click to expand...
Click to collapse
Ive flashed this rom selecting the tmobile version in aroma runs with no problems just no data and messaging
help guys i know you can
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
help guys i know you can
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You will need to give a little more information to get some help.
Please include:
model of your phone
modem/baseband currently on your phone (settings, general,about phone)
firmware version (same location)
recovery installed (if you're currently rooted) or recovery attempting to use
root method being used
flashing steps taken
ROM or ROMs flashed
I know its a long list but it will go a long way towards getting the help you need.
Good luck
Note 3 sm900p lean kernel now I flashed Cm 11
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Note 3 sm900p lean kernel now I flashed Cm 11
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What exactly is your question? I don't actually see what you were trying to do and what went wrong.
One of the biggest problems that people have when trying to flash a 4.4.4-based ROM is that their bootloader is still based on NC5, not NH7. If you want to flash anything newer, you'll have to update your phone to NH7 before flashing a 4.4.4 ROM.
I put together this post when helping another person out on another thread. I think it'll work as a step-by-step guide for you:
I'll explain how to install a custom ROM and some common things to think about/check prior to installing anything:
Installing a Custom ROM
Step 1 - Gather Information
First off, you need to know what version of Android your phone currently is running. This is easily done by looking in the Settings Menu -> General -> About Device.
The Main things we are looking at on this screen are Software Version, Model Number, Android Version, and Baseband Version. I'll explain these (to the best of my knowledge) below:
Software Version:
This is the "type" of Android that you're running. Rather than quoting the entire name, we typically only refer to the last 3 characters (MJ4, NAB, NC5, etc.). Stock Note 3 devices will (most-likely) be running one of 3 different versions of TouchWiz (TW):
MJ4 - This is the last Jellybean version of TW for the Sprint Note 3NAB - This is the first KitKat TW version for the Sprint Note 3NC5 - This is the second KitKat TW version for the Sprint Note 3NH7 - This is the latest KitKat TW version for the Sprint Note 3
The reason that we are concerned with the Software Version is that between the MJ4 and NAB versions, there were major changes. So if you're running MJ4, you will have to do additional steps before flashing a custom ROM based on a newer version. And if you're on NAB or NC5, you will not be able to go back to MJ4, so beware what you're flashing.
For the most part, if you're on NH7, you can flash either a NH7 or NC5 custom ROM, but just read the ROM's FAQ to see if there are any issues with doing so.
Model Number:
Most people don't worry about this, but I always do when looking at a new ROM. The Sprint Note 3 is different from the Verizon Note 3, which is also different from the International Note 3. It's always best to double-check that the ROM you're trying to install is truly meant for your device. This simple check will prevent a LOT of potential issues you'll get when installing a ROM.
Android Version:
This is just an additional check to the Software Version. Always best to know.
Baseband Version:
The Baseband is, unless I'm mistaken, the "kernal" for the phone's cellular and 4G radios. Sometimes upgrading (or downgrading) the Baseband can help with signal strength and reception. Some users have noted that they got better reception on older Baseband versions. I haven't personally looked into it and the reports from other users seem somewhat anecdotal, but it's good to know which Baseband you're on.
The Baseband is independent from the ROM version, so you can run an older Baseband (MJ4 or NAB) on a newer ROM (NC5), and vice-versa.
The last bit of information you need to know is the Bootloader Version. The way to find this information is to reboot your device. When you see the text on the screen, you should look for the Bootloader Version. It'll be a long string of characters, but you're only looking for the last 3 (MJ4, NAB, or NC5).
Once you have all the above information, you should be ready to start the fun process of preparing your phone to flash your first ROM.
Step 2 - Backup your Media
First thing: Backup all of your media to your computer. If there's pictures/music/videos/recordings you don't want to lose, back them up. It's just good practice. Don't lose all your cat pictures because you flashed something and it somehow erased your internal storage. I tend to keep everything of importance on the External Storage, but there are times where even external storage can be wiped, so it's best to back up everything to a PC.
Step 3 - Upgrade your Phone to the latest Stock ROM (NH7)
This only is a MUST applies if you're running an older version and want to install a NH7 ROM. Most continually-developed ROMs are either NC5 or NH7 now, so the first things first: Update your phone to NH7.
Go over to micmar's thread and download the One-Click File. It will remove Root, but don't worry, because when you install a new ROM, it will automatically include root access.
Follow the instructions in his thread and your phone will now be fully upgraded.
At this point, your "About Device" should show the following:
Software Version: N900PVPUCNH7
Android Version: 4.4.4
Baseband Version: N900PVPUCNH7
Reboot your phone and let it sit for a minute so it can get it's bearings.
Step 4 - Install a Custom Recovery
So far, we've been flashing everything in ODIN. Now, we're going to use ODIN one last time to flash a custom recovery, so that you can flash custom ROMs without the need of a computer.
The most-commonly used Custom Recovery is TWRP (XDA Link). You'll want to use the latest version, 2.8.0.
Flash this in ODIN. You should use the "PDA" or the "AP" Slot.
Reboot your phone to make sure it works correctly.
Step 5 - Make a Nandroid Backup of your device
If you don't know what a Nandroid backup is, don't worry. It's basically just taking your phone as is and making a backup of it. In case you make a mistake or flash a bad download of a ROM, this allows you to restore your system. I always keep my backups on the External Storage (microSD Card), so in case I have to wipe my internal storage, it's not a big deal. You can also copy the files over to your PC, just to be more paranoind about your nandroid backups (rhyming is fun!).
You do this by restarting into Recovery (power down device, hold down home button and volume up while powering on phone).
Once in TWRP, go to "backup." Make sure the storage selected is "external storage." This screen will have various options of what to backup. I typically choose everything except external storage. Typically, backups range from 1-2 Gigs.
For me, backups typically take 5-10 minutes to do. In my opinion, this is totally worth it, since I can always restore a backup with no issues.
Step 6 - Install a Custom ROM
Once you choose your custom ROM from the Development Section, follow the instructions on the original post to install it. I'll give a general outline of what I do whenever installing a new ROM, but sometimes a custom ROM will have specific instructions, so you want to make sure to read the posts carefully.
Generic Instructions for Installing a ROM:
Download ROM and check the md5
Internet being spotty in my area, I always check the md5 to make sure that the file downloaded correctly. You can check the md5 using this windows program or using a file explorer on your phone like ES File Explorer. I always copy the ROM zip file to my external SDcard.
Reboot to Recovery
Wipe Data, System, Cache, and Dalvik Cache
This is called a "Clean Wipe," meaning it will wipe out your installed Apps and the data associated with them. Some people will claim that "Dirty Flashing" (i.e. not wiping the above) is OK, but I've seen too many apps Force Closing (FC-ing) when dirty flashing. Also, if you dirty-flash and encounter an issue with a ROM, the first piece of advice is to do a clean install. Might as well do that initially and hopefully not run into any issues.
Install the Custom ROM
Pretty straight-forward on how to do this... just click "Install" and then browse to the place your copied the ROM zip file.
Reboot your phone and run through the typical initial start-up information (google account, etc).
Once you get your phone set up the way you like (apps, accounts, wifi passwords, etc), I'd make another Nandroid backup, just so you have one where it's setup with everything you need. This will make any issues less painful, since you'd restore a backup that's already setup.
Step 7 - Further Considerations
If you ever want to try a new ROM, all you have to do is repeat step 6. Beware, though, people easily become flashaholics when they first figure this stuff out.
If you were paying attention to my "Generic Instructions" when installing a ROM, you'd notice that every time you do a Clean Install of a ROM, you lose all your apps... All of your Angry Birds 3-Star levels are gone!
Well, there are ways to get prevent losing that data... One is by "Dirty Flashing" (Not wiping the "system" or "data" partitions before flashing a ROM in TWRP). This is common practice among users here on XDA, but is typically frowned upon by ROM devs. I've noticed that a good number of issues on ROM threads stem from people Dirty Flashing. It typically causes more problems than it solves.
The other way of backup up and restoring app data (prior to wiping) is by using Titanium Backup. I could write up a long post on how to use Titanium Backup (TiBu), but the main things to remember are the following:
White line items are fine to be restored (both Data and Apps).
Restoring Yellow line items is typically OK (Data only).
Restoring system apps or data (red line items in TiBu) is typically a bad idea.
I've been using TiBu for the past 2-3 years and it's typically worked like a charm. Sometimes, when there's a major Android Update (like from JellyBean to KitKat), it can become broken, but the Developer is really responsive and gets it to work within a few weeks. If you upgrade to PRO, you can schedule automatic app backups (I backup all my user apps every night at 3am). You can also restore apps/data from Nandroid Backups (which is great if you do a Nandroid backup but had forgotten to update your TiBu backups).
In Summary
Whew, that was a lot to write... I'm a Structural Engineer, not a Software Engineer, so I don't know the technical side of things like bootloaders or basebands, but hopefully none of the information I provided was false.
Anyways, let me know if you have any problems with the install. I appreciate any feedback!
Click to expand...
Click to collapse
I hope this helps, but please, in the future, write out your question clearly and provide as much information as possible, that way we can help you quickly and efficiently.
Cheers!
-Topher
OK I noticed that thanks again I finally found a 4.4.4 Cm Rom working awesome very little glitch but can deal with I have no way to update without pc
Sent from my SM-N900P using XDA Premium 4 mobile app
Why does titanium backup not save from deletion says no external backup detected
Sent from my SM-N900P using XDA Premium 4 mobile app
No data sorry
Sent from my SM-N900P using XDA Premium 4 mobile app
Running pac man rom Cm no data
Sent from my SM-N900P using XDA Premium 4 mobile app
Thanks
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Running pac man rom Cm no data
Click to expand...
Click to collapse
Ok, you haven't fully answered the questions myself and @jdelano asked you. If you cannot answer these questions, we will be unable to help you.
Phone Model: Note 3 sm900p
Phone Modem/Baseband: Unanswered
Firmware version: Unanswered
Recovery installed: Unanswered
Root Method: Unanswered
Flashing Steps: Unanswered
ROM flashed: CM11, pac man rom (no build number/date given, please provide a link to the thread you flashed from)
Are you a Sprint Customer, or have you flashed your phone to another carrier?
What is the issue you're having: No data when on CM 4.4.4 ROMs.
I am in the process of downloading/installing the PacMan ROM in this thread. The file I will be flashing is the pac_hltespr__20141110-124721.zip and the Gapps modular package from this thread, filename: pa_gapps-modular-full-4.4.4-20141121-signed.zip.
EDIT: By following the steps in my previous post, I was able to install the PacMan ROM with Gapps and all worked well. I had data, root access, and was able to wifi tether... Please answer the questions I asked before, especially what version is your baseband, as I suspect that's the main issue that you have.
Nc5
Sent from my SM-N900P using XDA Premium 4 mobile app
Y'all packing works great little glitchy phone turns on an off but all good all Cm roms I end up with no data I have Phil's recovery beast kernal average gapps had to update su binary any time I flash cm and it changes my recovery sometimes I cannot format SD card or I will loose all files I have no PC even if I use drop box titanium doesn't work the way it use to can save apps from deleting with confirmation so what's a stable cm Rom or slim rom and gapps or do you have knew updated tw rom rooted I have update my boot loader so
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Nc5
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Phone Model: Note 3 sm900p
Phone Modem/Baseband: NC5
Firmware version: Unanswered
Recovery installed: Unanswered
Root Method: Unanswered
Flashing Steps: Unanswered
ROM flashed: CM11, pac man rom (no build number/date given, please provide a link to the thread you flashed from)
Are you a Sprint Customer, or have you flashed your phone to another carrier?
What is the issue you're having: No data when on CM 4.4.4 ROMs.
Click to expand...
Click to collapse
As I stated in my first reply to you, the issue is that your phone is still on the NC5 bootloader. In order for 4.4.4 ROMs to play nicely on your phone, you'll need to update it to NH7. This is also stated in my previous post. You need to follow those instructions to the letter (particularly Step 3) in order to update it. You must use a computer to flash the update file, as Mobile ODIN is not able to update the bootloader. You need to get access to a computer (work, library, friend who owes you $20, someone at Starbucks).
Until you follow those steps, I doubt any 4.4.4 ROM will work correctly on your device.
Exposed frame work not compatible with roms only tw anyone have zip for NH7 u date with root
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Exposed frame work not compatible with roms only tw anyone have zip for NH7 u date with root
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is the first you've mentioned XPosed Framework... What exactly are you trying to do with it?
I don't know where you've gotten your information from, but I know for a fact that XPosed is compatible with all 4.4.4 AOSP ROMs as well as all TW ROMs. XPosed is NOT compatible with 5.0+ Roms. I'm currently using it on my "daily-driver" ROM, which is based on 4.4.4 AOSP.
R1000 said:
Y'all packing works great little glitchy phone turns on an off but all good all Cm roms I end up with no data I have Phil's recovery beast kernal average gapps had to update su binary any time I flash cm and it changes my recovery sometimes I cannot format SD card or I will loose all files I have no PC even if I use drop box titanium doesn't work the way it use to can save apps from deleting with confirmation so what's a stable cm Rom or slim rom and gapps or do you have knew updated tw rom rooted I have update my boot loader so
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, lets get you to a known platform with your phone so you can use 4.4.4 TW or AOSP ROMs.
#1. Load latest stock firmware and software
[Stock ROM] Odin flashable N900PSPTDNH7Follow the instructions EXACTLY
Now make sure you boot stock NH7, let it get data and update your profile and PRL by doing:
go to Settings -> General -> System Update, then select Update PRL (wait for it to do its thing), then Update Profile (again wait for it.)
Now we know you're on the most current stock software available and we've updated your profile and PRL (preferred roaming list)
#2. Root stock NH7 acquired in step #1
Go here Download philz_touch_6.48.4-hlte.tar.md5 (save it in the same folder you have Odin in from Step #1)Go Download SuperSU-v2.37.zipCopy the zip to your phone's sd cardUse Odin to put philz_touch_6.48.4-hlte.tar.md5 on your phone (same basic steps you used to Odin NH7) - Make sure you UNCHECK rebootOnce odin is finished and you see PASSED on the screen, unplug your phone from your computer then press Volume UP + HOME + POWER and hold all 3 until the phone reboots and you see blue words "Recovery Booting ..." at the top of the screen - Philz recovery will startnow select install zip -> choose zip from /sdcard -> scroll all the way to the bottom and select the SuperSU-v2.37.zip file -> select Yesonce finished press back until you get to the main recovery menu and select Reboot to System
#3. Update SuperSU binaries
Once your rebooted, Open Apps drawer, open SuperSU, say no to disable knox, it will ask about updating binaries, select yes, select normal, wait until it says its finished.Now you are Rooted Stock NH7You can now flash any 4.4.4 TW-NH7 or AOSP hltespr ROM - make sure to follow each Post #1 instructions on the ROM you choose and of course backup before flashing anything new
I hope this gets you to where you want to be, good luck.
Theres a lot of patience being displayed here. One should never start messing with their phone unless they have even the slightest clue what they are doing from the start
piaa_nissan said:
Theres a lot of patience being displayed here. One should never start messing with their phone unless they have even the slightest clue what they are doing from the start
Click to expand...
Click to collapse
The amount of patience I am seeing is mind blowing! To the OP...Just some words of advice. I have been a member of XDA for alot of years now and I can tell you that you will get a tremendous amount of help from this community. My only suggestions would be,when looking for help:
1) Be very clear as to the question you are asking.
2) If someone is willing to help you, Give them all of the information that they are asking you for.
3) Punctuation goes a very long way when someone is trying to understand what you are asking. Try using a period to avoid run on sentences.
Please do not take this as anything other then what I have learned over the years to get the best and quickest help!
I hope these guys are able to help you with your issues! :fingers-crossed:
Note: I am not affiliated to the Dev team of this ROM, just a Note 7 user who would like to share the ROM with everyone here. Hence, NO dev support will be provided.
Some elements of the UI/ROM options are in Chinese, but I will not be providing translations unless there is demand. Thank you for your understanding
A Chinese dev team has recently released an Oreo port for the Note 7, and hence I am sharing it here for everyone to enjoy.
The original Dev thread (in Chinese): Here
Once again, I am not affiliated to the Dev team, so don't direct any questions/bugs as I will not know how to solve them.
Most of the info listed below is translated from the original thread.
Aurora ROM for Note 7 Exynos 8890
Supported devices:
Note 7 N930F/FD
Unsupported devices:
Note 7 N930S/L/K
[*]ROM will fail to boot on these devices, as the kernel does not support these models yet.
ROM Information
Full Oreo 8.0 port based on the Note FE stock ROM
Stock UI, but with additional customization options
Multi-language support. A few elements may be in Chinese, but 90% of the UI will be in the chosen language.
Custom Aurora kernel for better battery life and stability
Pre-rooted, able to choose from SuperSU or Magisk on install
De-bloated
Full S-Pen support
Added Dolby Atmos audio effect
Advanced power menu - fast reboot, recovery, download mode, safe mode
Wallpapers and lock screen ported from the S9
No time limit/paywall, unlike the Soul ROM that has been floating around this forum
Device model changed to Samsung S8+ (SM-G9550)
Will not change or update the baseband
Things that are working:
Everything
except... (see below)
Things that are not working:
Iris scanner
Mobile data usage tracking (can be circumvented with 3rd party apps)
That's it
Bugs:
None known thus far
Screenshots:
Here
Installation guide:
1. Boot into TWRP recovery with home+volume up+power on while the device is off.
2. Do a full backup (optional, but always helpful in case something goes wrong)
3. Perform a full wipe (system, data, cache)
4. Flash the installer zip (download link below).
5. Follow the pictures in the album: How to install
6. The first boot may take 10-15 mins. Be patient.
7. Once the setup wizard pops up, change the language to English (or any language of your choice)
8. Reboot your device after configuring
9. Your Note 7 is ready for use
Special note: Do not update any system apps as the device model has been modified, and updating system apps may cause errors.
Download link:
http://www.mediafire.com/file/6sgn1b50lqsy2bz/Aurora_N930X_N935X_OREO_RG4_V1.0_2.zip/file
FAQ section (translated from the original dev thread)
Q: Google play services keeps stopping
A: Go to app permissions in settings and enable location access for Google play services.
Q: Unable to sync Google contacts
A: Go to app permissions -> Contacts, and enable all 3 settings for Google play services.
Note: The ROM comes with Google Play store installed but disabled by default. Refer to bomcoi1402's comment to see how to enable it.
Can you help me to install Google services? (Google play, Gmail, Maps, Google account manager, ...)
Thank somuch!
Update: I was installed. In Aurora app.
Hey guys, if you like using your device, DO NOT INSTALL this rom, it has a lot of chinese apps, and if you try to flash another rom your device would constantly be restarting itself.
I couldn't figure how to install google ?
After checking Aurora App setting WHAT?
Can you help me ?
I installed a gapps but Play services Stopped. @bomcoi1402
@IcyDevil_ can you translate FAQ section?
Edit: Thx for answers I will try again
10 cmt for upload picture
@ReTekno: do not install gApps. You can factory reset, then see pictures and do it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@KAL26: I was installed this rom from last week and everything okey now ^^~
KAL26 said:
Hey guys, if you like using your device, DO NOT INSTALL this rom, it has a lot of chinese apps, and if you try to flash another rom your device would constantly be restarting itself.
Click to expand...
Click to collapse
Are you sure we installed the same ROM? As far as I can see, the only Chinese app installed is the ROM settings, no others. Not quite sure about the flashing another ROM part, but have you done a full wipe before flashing? Dirty flashing may cause issues sometimes so it's not recommended to dirty flash.
ReTekno said:
I couldn't figure how to install google ?
After checking Aurora App setting WHAT?
Can you help me ?
I installed a gapps but Play services Stopped. @bomcoi1402
@IcyDevil_ can you translate FAQ section?
Click to expand...
Click to collapse
@ReTekno, have translated the FAQ section. Do take a look to see if it solves your issue.
Guys, how can I remove chinese text on the control panel ?
IcyDevil_ said:
Are you sure we installed the same ROM? As far as I can see, the only Chinese app installed is the ROM settings, no others. Not quite sure about the flashing another ROM part, but have you done a full wipe before flashing? Dirty flashing may cause issues sometimes so it's not recommended to dirty flash.
Click to expand...
Click to collapse
Yes i installed the same ROM, i did a full wipe and i still have random restarts. Thanks to this ROM i can't use my phone anymore. I'll see if i'll manage to get it working eventually.
You can try it.
Only one problem, this is don't push notification of Facebook, Messenger, Zalo.
I still don't know how to fix it.
ugur142015 said:
Guys, how can I remove chinese text on the control panel ?
Click to expand...
Click to collapse
I still don't know
KAL26 said:
Yes i installed the same ROM, i did a full wipe and i still have random restarts. Thanks to this ROM i can't use my phone anymore. I'll see if i'll manage to get it working eventually.
Click to expand...
Click to collapse
Same issue, but not with this rom (Note8 Port Full Note7/FE). Any solution!
Push notifications
[/COLOR]
bomcoi1402 said:
You can try it.
Only one problem, this is don't push notification of Facebook, Messenger, Zalo.
I still don't know how to fix it.
Click to expand...
Click to collapse
You can easily fix it by uninstalling the brevent app
Brevent prevents apps from running in background that is why when your screen is off you wont get any push notifications
vicioso3 said:
Same issue, but not with this rom (Note8 Port Full Note7/FE). Any solution!
Click to expand...
Click to collapse
Sadly i don't think there is a solution, I tried everything, factory reset, full wipe, re-root, nothing works, still getting random restarts, and the worse is happening whenever i try to update or install any apps, either from play store or from galaxy apps. Thanks to this crap, i now have an unusable brick of a note7.
KAL26 said:
Sadly i don't think there is a solution, I tried everything, factory reset, full wipe, re-root, nothing works, still getting random restarts, and the worse is happening whenever i try to update or install any apps, either from play store or from galaxy apps. Thanks to this crap, i now have an unusable brick of a note7.
Click to expand...
Click to collapse
And who asked you to do this? It looks a lot like a personal problem to me. I am running the other Chinese Oreo ROM for a long time with no problems. Tried this one too and it was good, but I just didn't want to fix all the Chinese again. I might try the Aurora kernel when I have the time.
I really suggest you study all the information available on this forum before you share nothing but frustrated rants. BTW, I can't see a way how you can brick this phone permanently. In the worst of all cases there is always Odin.
ulev said:
And who asked you to do this? It looks a lot like a personal problem to me. I am running the other Chinese Oreo ROM for a long time with no problems. Tried this one too and it was good, but I just didn't want to fix all the Chinese again. I might try the Aurora kernel when I have the time.
I really suggest you study all the information available on this forum before you share nothing but frustrated rants. BTW, I can't see a way how you can brick this phone permanently. In the worst of all cases there is always Odin.
Click to expand...
Click to collapse
What made you think i have a personal problem or that this simply is a frustrated rant? I simply told my experience in trying this ROM, and apparently i'm not the only one having issues with it. Due to all the chinese apps, and various other issues, i simply didn't like this ROM, and when i tried to flash another ROM, i got the problems i mentioned. I've been installing ROM's on my various phones for many years now, i'm not a noob when it comes to rooting, ROM's and other custom things you can do to and android device. I tried ODIN aswell, and still no changes, so i simply voiced my opinion. Next time try to be less frustrated yourself, and less judgy.
KAL26 said:
What made you think i have a personal problem or that this simply is a frustrated rant? I simply told my experience in trying this ROM, and apparently i'm not the only one having issues with it. Due to all the chinese apps, and various other issues, i simply didn't like this ROM, and when i tried to flash another ROM, i got the problems i mentioned. I've been installing ROM's on my various phones for many years now, i'm not a noob when it comes to rooting, ROM's and other custom things you can do to and android device. I tried ODIN aswell, and still no changes, so i simply voiced my opinion. Next time try to be less frustrated yourself, and less judgy.
Click to expand...
Click to collapse
Well, there is a long line of posts by you in this thread that are indicating that you should not have started using a device that has been withdrawn by the manufacturer.
BTW, I did not mean to say YOU have a problem (how would I know?). I simply wanted to say your problems should not be generalized as indicative of what can be done with this device.
I still don't see any reason why you can't flash back an older Android 7 version with Odin and have a flawless, Chinese free experience of this nice device until it dies. Again, the problems you are describing are related to your device or environment, not to the Note7 per se.
In fact, I would like to understand, how you initially overcame Samsung's blocking of the phone and how you proceeded since then. This would provide an indication what might have gone wrong. Your ranting does not.
And only so you understand, I am writing this on my Note7 with the Soul Vip11 Oreo ROM where I added my own mods to eliminate 99% of the Chinese crap and the pay wall. Once I 8did a TWRP backup and installed this ROM without any problem and played around with it for a while until I restored my old one,again no problem. There was no incentive for me to polish up this ROM and install all my apps again, would have been a total waste of time.
This should explain to you, that those Chinese ROMs might be a PITA, but they are also not intended for us Westerners. So if you can't handle them, simply don't go there.
ulev said:
Well, there is a long line of posts by you in this thread that are indicating that you should not have started using a device that has been withdrawn by the manufacturer.
BTW, I did not mean to say YOU have a problem (how would I know?). I simply wanted to say your problems should not be generalized as indicative of what can be done with this device.
I still don't see any reason why you can't flash back an older Android 7 version with Odin and have a flawless, Chinese free experience of this nice device until it dies. Again, the problems you are describing are related to your device or environment, not to the Note7 per se.
In fact, I would like to understand, how you initially overcame Samsung's blocking of the phone and how you proceeded since then. This would provide an indication what might have gone wrong. Your ranting does not.
And only so you understand, I am writing this on my Note7 with the Soul Vip11 Oreo ROM where I added my own mods to eliminate 99% of the Chinese crap and the pay wall. Once I 8did a TWRP backup and installed this ROM without any problem and played around with it for a while until I restored my old one,again no problem. There was no incentive for me to polish up this ROM and install all my apps again, would have been a total waste of time.
This should explain to you, that those Chinese ROMs might be a PITA, but they are also not intended for us Westerners. So if you can't handle them, simply don't go there.
Click to expand...
Click to collapse
Maybe you didn't understood what i wrote in my first post. What i said was that i installed this ROM, tried to use it, and due a lot of chinese apps, i couldn't get used to it, so i flashed the ROM i was using before, and that's when the problems began. Random restarts, device would freeze up. I did backup, full wipe, factory restore, re-did the entire root process, I even tried ODIN, without any luck. Before installing this ROM, my device worked flawlessly, It was rooted before installing this, with the Nougat Note FE ROM, no issues. So for me this ROM messed up my device in some way.
KAL26 said:
Maybe you didn't understood what i wrote in my first post. What i said was that i installed this ROM, tried to use it, and due a lot of chinese apps, i couldn't get used to it, so i flashed the ROM i was using before, and that's when the problems began. Random restarts, device would freeze up. I did backup, full wipe, factory restore, re-did the entire root process, I even tried ODIN, without any luck. Before installing this ROM, my device worked flawlessly, It was rooted before installing this, with the Nougat Note FE ROM, no issues. So for me this ROM messed up my device in some way.
Click to expand...
Click to collapse
All I can say: Do a TWRP backup first if you want to experiment. Has been said on XDA thousands of times. And READ the OP fully before you jump into it.
And if I had your problem, I am quite sure I would fix it silently myself. You may have to format (not wipe). Also, a remaining SAMSUNG function in the bootloader may try to keep you from going back to NOUGAT, so as a last option you might have to live with one of the Chinese OREO ROMs before you figure out what to do.
In any case, the real experts (besides the Chinese) have all moved on. Nobody around anymore who would help you. And I obviously don't like your style... :silly: