Hey, so I'm fairly new to the whole rooting and customizing Android, so please forgive me if I come accross "ignorant" or generally childish. I bought a galaxy note 3 the other day and researched what rooting did. After getting convince that rooting was "awesome," I actually managed to root. I also played with some Xposed modules because they were fairly simple and cool. After more research, I found out that Verizon had a locked bootloader which prevented me from using any other roms? I also read that verizon/att users can use safestrap but i couldn't exactly find some specifics for it. So whats the disadvantages of safestrap? Do specific roms have to be used?
Another concern, I'd like to get a faster rom than stock touchwiz, but i'd also like to find a rom that can use ART runtime as well as maintaining a nice multi window feature. I tried XHaloFloatingWindow and another xposed module, and I can't say I was pleased with them compared to the touchwiz one. I'd also like to maintain S-pen features? Does anybody know of any roms that may come close to fitting most of these topics?
Final, completely random question, The lg g3 has this lockscreen widget where when it rains out, drops of water will cover/slide down the entire lock screen on top of your notifications. I thought this was awesome, but wasn't sure if it was possible to get on a note 3.
Anyways, Hope to get some simple answers
ATalkingRock said:
Hey, so I'm fairly new to the whole rooting and customizing Android, so please forgive me if I come accross "ignorant" or generally childish. I bought a galaxy note 3 the other day and researched what rooting did. After getting convince that rooting was "awesome," I actually managed to root. I also played with some Xposed modules because they were fairly simple and cool. After more research, I found out that Verizon had a locked bootloader which prevented me from using any other roms? I also read that verizon/att users can use safestrap but i couldn't exactly find some specifics for it. So whats the disadvantages of safestrap? Do specific roms have to be used?
Click to expand...
Click to collapse
Safestrap is as close to a custom recovery as we'll get, right now. Due to our bootloader, stock based rom are all we can use. However, we are not stuck with one rom. Check in the dev threads for roms compatible with your device. Also check the dev and general threads for more info on rooting, safestrap, and how to flash roms.
Another concern, I'd like to get a faster rom than stock touchwiz, but i'd also like to find a rom that can use ART runtime as well as maintaining a nice multi window feature. I tried XHaloFloatingWindow and another xposed module, and I can't say I was pleased with them compared to the touchwiz one. I'd also like to maintain S-pen features? Does anybody know of any roms that may come close to fitting most of these topics?
Click to expand...
Click to collapse
Art not available for us. Only stock based. See my recommendation above for other roms. There are a few with some pretty cool features and add-ons!
Final, completely random question, The lg g3 has this lockscreen widget where when it rains out, drops of water will cover/slide down the entire lock screen on top of your notifications. I thought this was awesome, but wasn't sure if it was possible to get on a note 3.
Anyways, Hope to get some simple answers
Click to expand...
Click to collapse
Not sure about this one...
Not sure about your specific questions, as I don't use multiwindow or the other features you listed. But I thought I would point out, what method of root did you use? Make sure of what system your running at this point. beans or kitkat? You will have to select a rom based on that. Or vice versa, re-root if you find a rom that you prefer thats running different android version. Either one will run safestrap obviously, since there are roms for each. You will find pros and cons to each. The con that I'm currently experiencing on kitkat that has me thinking about going back is I can't seem to find a modem that will get me decent reception so I'm assuming at this point that its kitkat thats causing it. Just something more for you to research. Being new to it, you've got ALOT of material to read about. But if you've already rooted, sounds like you've got a decent idea of the process. For me, tutorial videos were a life saver
LeftyGR said:
Safestrap is as close to a custom recovery as we'll get, right now. Due to our bootloader, stock based rom are all we can use. However, we are not stuck with one rom. Check in the dev threads for roms compatible with your device. Also check the dev and general threads for more info on rooting, safestrap, and how to flash roms.
Art not available for us. Only stock based. See my recommendation above for other roms. There are a few with some pretty cool features and add-ons!
Not sure about this one...
Click to expand...
Click to collapse
Alright so perhaps you can help me with just a few more concerns. I researched roms and such. I successfully downloaded safestrap, made a backup of my stock rom and put it on mycomputer. I also made a backup with titanium backup before that and it is also on the computer. I am looking at hyperdrive or jasminerom for the note 3. On there, it explains normal directions to install, but then it says to flash with odin, but when I read something about a tutorial how to install cutom roms on a website "Galaxynote3root" (I can't post the URL yet, says i'll be spamming) , it explained nothing of odin. What is odin? is it mandatory? Does my phone have it by default? hm.... Also i have a build number of NC4, does that build not work with NC2? sorry for inconvenience or annoying noobish questions. Thanks if you respond
So being on Kitkat, did you use the beans method that installed a rom with root basically built in already? And by saying you downloaded safestrap, is it successfully installed? When you boot the phone, do you get the safestrap bootup screen allowing to go into recovery?
If you've already gotten that far, your pretty well set to install either of those roms.
LeftyGR said:
Safestrap is as close to a custom recovery as we'll get, right now. Due to our bootloader, stock based rom are all we can use. However, we are not stuck with one rom. Check in the dev threads for roms compatible with your device. Also check the dev and general threads for more info on rooting, safestrap, and how to flash roms.
Art not available for us. Only stock based. See my recommendation above for other roms. There are a few with some pretty cool features and add-ons!
Not sure about this one...
Click to expand...
Click to collapse
scott_65 said:
So being on Kitkat, did you use the beans method that installed a rom with root basically built in already? And by saying you downloaded safestrap, is it successfully installed? When you boot the phone, do you get the safestrap bootup screen allowing to go into recovery?
If you've already gotten that far, your pretty well set to install either of those roms.
Click to expand...
Click to collapse
Well i rooted my phone via towelroot. I got safestrap hooked up and installed, so in other words when i reboot, yes it does have the splash screen. I am on kitkat as well. but do i need to install some sort of odin or something? sorry
I think as long as the rom's op says it's based on nc2 or nc4, you should be good. You should not need to worry about odin, since you're already on kk.
Since you're new, I'd suggest not touching the stock slot. It gives you a fall back if something goes wrong. Make sure you understand using safestrap, and start trying some stuff out.
---------- Post added 30th July 2014 at 12:00 AM ---------- Previous post was 29th July 2014 at 11:58 PM ----------
scott_65 said:
So being on Kitkat, did you use the beans method that installed a rom with root basically built in already? And by saying you downloaded safestrap, is it successfully installed? When you boot the phone, do you get the safestrap bootup screen allowing to go into recovery?
If you've already gotten that far, your pretty well set to install either of those roms.
Click to expand...
Click to collapse
Sounds like he rooted the nc4 with towelroot, cuz he started on nc4. And sounds like ss is working for him, if he's made a backup.
LeftyGR said:
I think as long as the rom's op says it's based on nc2 or nc4, you should be good. You should not need to worry about odin, since you're already on kk.
Since you're new, I'd suggest not touching the stock slot. It gives you a fall back if something goes wrong. Make sure you understand using safestrap, and start trying some stuff out.
Click to expand...
Click to collapse
Okay thanks, that boosts my confidence a bit! I'm just afraid of bricking my phone, as any noobie should be.
ATalkingRock said:
Okay thanks, that boosts my confidence a bit! I'm just afraid of bricking my phone, as any noobie should be.
Click to expand...
Click to collapse
Good man.
If you find something that you don't know or understand, search that thread for an answer. Then ask if you don't find an answer. And always try to give any other details you think might help.
As long as you remember search is your friend first...then ask...you will almost always find people to help you out!
LeftyGR said:
Good man.
If you find something that you don't know or understand, search that thread for an answer. Then ask if you don't find an answer. And always try to give any other details you think might help.
As long as you remember search is your friend first...then ask...you will almost always find people to help you out!
Click to expand...
Click to collapse
alright alright I'm very sorry for this final question as I actually have tried to search for this but only got comparisons between titanium backup and safestrap. So, if I were to make a titanium backup right now, after the fact that i made a safestrap backup or installation, will that effect anything? I'm really really sorry if these questions are beyond beginner, I just like to play it safe.
ATalkingRock said:
alright alright I'm very sorry for this final question as I actually have tried to search for this but only got comparisons between titanium backup and safestrap. So, if I were to make a titanium backup right now, after the fact that i made a safestrap backup or installation, will that effect anything? I'm really really sorry if these questions are beyond beginner, I just like to play it safe.
Click to expand...
Click to collapse
Nope. Tibu backs up specific apps and it's associated data and stores it on sd. When you open tibu, it gets it's info from files it stores on sd. Recovery backs up your entire rom environment, but doesn't actually touch sd card user space.
This is why tibu is so helpful. Everything pops up that you had backed up, even on a new rom.
I'm not familiar with the towelroot method. Only the old Kingo for jb, or the beans method for kk. Sounds like your good to go for any KK roms, and Lefty seems familiar, good deal. Not sure how old you are or how far back your computer knowledge goes, so this may do you no good. Odin doesn't go on your phone, it goes on your computer. I always think of it as the old school DOS, or like now when you boot to command prompt if windows isn't working. Its like a back door when your phone operating system isn't working, or if you need to make changes to part of the system that would otherwise need to be running to make those changes FROM the phone. Its flashes the changes TO the phone from your computer instead.
I'm rambling. Its too early. Anyhow, glad your getting things moving along. You can try roms in various rom slots, but you may have issues. I had some roms work well, others not well at all. The ones that have problems, they seem to work better in the stock slot. So you have to wipe the stock slot and flash it there. No big deal, just don't goof up, flash it all at once. If you pause, take a potty break and the battery dies, whatever, don't forget, you have no operating system at that point. Thats when Odin would come into play
LeftyGR said:
Nope. Tibu backs up specific apps and it's associated data and stores it on sd. When you open tibu, it gets it's info from files it stores on sd. Recovery backs up your entire rom environment, but doesn't actually touch sd card user space.
This is why tibu is so helpful. Everything pops up that you had backed up, even on a new rom.
Click to expand...
Click to collapse
Alright so quick update. I successfully installed both roms into slots 1 and 2 respectively. Everything went okay, I rebooted system, but the screen just stayed black. They aren't loading, i still can go back to stock rom. But uhm any idea as to why this is occuring? Could it be the NC4/NC2 build things?
In the hyperdrive rom for the note 3, it says it will work with verizon and also states that after the initial reboot after flashing the rom, there will be a 10 minute wait until it actually boots up. I'd say i've waited 15 minutes and nothing has shown up. So I'm assuming something went wrong. Perhaps i should try to reflash it?
EDIT: I read the directions further ahead and managed to flash a file via odin for the first time, now im getting a rom's boot animation which is good. I hope this'll work !
Edit 2: I successfully installed it and booted it up, everything went okay, I restored my titanium backup and then titanium prompted me to restart. I restarted, and now its bootlooping android.process.acore or something like that is crashing everything =/
ATalkingRock said:
Alright so quick update. I successfully installed both roms into slots 1 and 2 respectively. Everything went okay, I rebooted system, but the screen just stayed black. They aren't loading, i still can go back to stock rom. But uhm any idea as to why this is occuring? Could it be the NC4/NC2 build things?
In the hyperdrive rom for the note 3, it says it will work with verizon and also states that after the initial reboot after flashing the rom, there will be a 10 minute wait until it actually boots up. I'd say i've waited 15 minutes and nothing has shown up. So I'm assuming something went wrong. Perhaps i should try to reflash it?
EDIT: I read the directions further ahead and managed to flash a file via odin for the first time, now im getting a rom's boot animation which is good. I hope this'll work !
Edit 2: I successfully installed it and booted it up, everything went okay, I restored my titanium backup and then titanium prompted me to restart. I restarted, and now its bootlooping android.process.acore or something like that is crashing everything =/
Click to expand...
Click to collapse
uh oh now my stock rom is bootlooping as well. i in trouble
ATalkingRock said:
uh oh now my stock rom is bootlooping as well. i in trouble
Click to expand...
Click to collapse
What did you flash in odin?
LeftyGR said:
What did you flash in odin?
Click to expand...
Click to collapse
In JasmineRom's instructions it says to flash a file called unified_KK_Firmware_RE.tar.md5. After flashing it, it booted up to the new rom.But seemingly once i restarted after titanium backup restored everything it crashed. I then cleared all the cache and data through a factory reset in the safestrap settings and it started up normally. Am I not going to be able to restore my things through titanium? I would send you a link to the odin flash file, but I can't until I have a certain number of posts
ATalkingRock said:
In JasmineRom's instructions it says to flash a file called unified_KK_Firmware_RE.tar.md5. After flashing it, it booted up to the new rom.But seemingly once i restarted after titanium backup restored everything it crashed. I then cleared all the cache and data through a factory reset in the safestrap settings and it started up normally. Am I not going to be able to restore my things through titanium? I would send you a link to the odin flash file, but I can't until I have a certain number of posts
Click to expand...
Click to collapse
No need. I know what you're saying. So flashing that file shouldn't have been really necessary, given you're already on nc4. But it doesn't hurt and should not have caused what you described. So you have roms in stock, slot 1, and slot 2? Which ones bootloop?
For tibu, I would uninstall, reboot, reinstall. Somehow it didn't like you doing that.
LeftyGR said:
No need. I know what you're saying. So flashing that file shouldn't have been really necessary, given you're already on nc4. But it doesn't hurt and should not have caused what you described. So you have roms in stock, slot 1, and slot 2? Which ones bootloop?
For tibu, I would uninstall, reboot, reinstall. Somehow it didn't like you doing that.
Click to expand...
Click to collapse
Alright so as we speak right now, I have slot 1 with jasminerom and stock which should be the untouched stock rom of course. I have a backup through safestrap of that. I will uninstall titaniumbackup and reinstall and see if that works?
edit: sorry I feel as though I'm being unclear as I can hardly comprehend my own messages. Before, both slot 1 and stock were bootlooping. This bootloop came after titanium backup promted me to restart. But when i cleared the cache through the factory reset, the slot1 rom started to work agin (jasminerom), I haven't tried stock rom to see if it works yet. I'm currently on jasminerom about to re-restore my apps through titanium backup like you said.
LeftyGR said:
No need. I know what you're saying. So flashing that file shouldn't have been really necessary, given you're already on nc4. But it doesn't hurt and should not have caused what you described. So you have roms in stock, slot 1, and slot 2? Which ones bootloop?
For tibu, I would uninstall, reboot, reinstall. Somehow it didn't like you doing that.
Click to expand...
Click to collapse
alright i finished re-restoring through titanium backup. Once it finished it provided a notification saying "batch complete, 66 elements failed" Right now all my apps are here and everything is seeming to work. Should I restart to see if it bootloops again?
ATalkingRock said:
alright i finished re-restoring through titanium backup. Once it finished it provided a notification saying "batch complete, 66 elements failed" Right now all my apps are here and everything is seeming to work. Should I restart to see if it bootloops again?
Click to expand...
Click to collapse
You should be ok. How many apps did you try to restore, if 66 failed?
Related
OK, congratulate me!! Thanks. I did it on the first try, no issue or hiccups what-so-ever.
Now for the info. I'm not sure that anyone will be interested, but I'm guessing other people in my position at least might be.
I'm very experienced with computers, but not working directly with rooting/unlocking devices. But I would say anyone who reads up a bit and can follow directions properly could pull it off pretty easily.
So I run 2.2.2, and I used superoneclick 1.6.3.
After opening superoneclick, I switched it from psneuter to rageagainsthecage. I had no idea if I was supposed to do this, but I read all about rageagainstthecage, and never heard of psneuter.
I had my phone connected to my PC, and I left my SD in the phone, but I unmounted it in settings. I have used ADB before, so I knew the drivers were installed and working, and I hit the button root.
After reading this site, http://forum.xda-developers.com/showthread.php?t=803682, I started with debugging off, and turned it on as it said. I then turned it off, but didn't get a chance to turn it back on and off and on, so I just turned it back on (debugging) when it got to "Waiting for device" for the second time.
That was it! It asked to test and see if root was in fact accomplished, and it was. I then installed setCPU (which is basically the only reason I wanted to do this) and as far as I can tell it seems to be working fine.
I have been reading a lot about this for the past few days, but the actual procedure only took a couple of minutes. Keeping in mind, of course, that I already had ADB and drivers working.
Nothing was wiped off my phone, which surprisingly was hard to confirm on the web. I did read somewhere that only unlocking wipes data, but still, you never know.
I hope this helps anyone else who is new and unsure of the process, and I'd be happy to answer any other specific questions based on what I have learned of the last week or so. I know that people hesitate to ask questions in case they have already been asked lots of times, but are buried and hard to find (because that's the position I was in ).
Thanks for posting your "rooting" experience. I'm sure there are people that will find it helpful.
I think when I did mine, it was something along the lines of:
fastboot-oem-unlock
fastboot flash recovery <whatever>
reboot into recovery and flash rom
Other than the ability to install custom ROM's I've yet to see a huge deal in rooting my phone. Anyone care to tell me what I can do with a rooted N1 that is a must have? So far I tried to change some fonts, which didn't work, and discovered that I have to install a custom ROM to change the color of the notification bar, and I can't make the default Google music and news widgets slightly transparent. So educate me, what's the huge deal with rooting, aside from a custom ROM?
Set cpu of course like being said. I remember the first time I rooted my phone was universal androot it was a breeze. Then I lost root and use super one click to gain out back. Root really easy as well
Sent from my Nexus One using XDA App
- Backup application, like MyBackup, can backup your app data(including game save...) if your device is rooted.
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..
Built in trackball colors, call blocker, hide frequently called list in the favorites tab, remove unnecessary apps, tmobile wifi calling, notification bar power toggles, trackball wake and unlock, quiet hours, themes, etc., etc., etc. Just off the top of my head. Oh, and Gingerbread!!!
Sent from my Nexus One using Tapatalk
Some apps want to bypass the home screen "5 second rule" like widget locker, you need root. I setup a widget to reboot (nice!).
brettbellaire said:
...I did read somewhere that only unlocking wipes data, but still, you never know.
Click to expand...
Click to collapse
Unlocking the Bootloader wipes data, rooting does not. This is probably what you read.
offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7? Yes you can. Often if the ROM is the next version in a series, you can flash without wiping data or cache, but some ROMs require you to do this first.
2/ Can I always restore backups, nomatter what rom I come from or to? A Nandroid backup can be reinstalled from any ROM, or even just from Recovery if there is no ROM.
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away? Yes. Either restore your stock ROM Nandroid backup or a passimg.zip.
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse
offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
2. Nandroids can be reinstalled anytime. However, a nandroid does not contain your HBOOT and Radio. So if you updated those to use a specific ROM, they would stay in place with the nandroid restore.
3. When GB does finally make it out to our specific device, there is no way you would get an OTA before the ROM devs here had you up and running.
***Also note, the 1-click root tools may or may not work right away with the OTA 2.3. So to anyone that rooted using those tools and unrooted to hurry up and get an OTA, you may be stuck on stock until it gets fixed.
Know-Fear said:
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
Click to expand...
Click to collapse
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
Another question would be if you just flash a new kernal do you lose any/all data?
brettbellaire said:
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
The only thing you'd lose is the old rom
Another question would be if you just flash a new kernal do you lose any/all data?
Click to expand...
Click to collapse
Nope
Sent from my Nexus One using XDA App
kmiloco49 said:
Nope
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Interesting... Thanks!
@ brettbellaire
I've rooted before, and lost root when ota's came. I've rooted again using superoneclick, and am contemplating cm7. But I feel very cautious about flashing a different rom, I'd cry if I bricked my phone. However, I'm probably going to do it during the next week (unless gingerbread ota arrives).
Andy
Sent from my Nexus One using XDA App
Hmmm, I have been anxious for GB too.... but I'm not sure it's worth it. I don't think it's such a big update. I don't think there's too much of a danger of brinking these days.
I have been contemplating doing what I have to to overclock, see what kind of a difference that makes...
bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
I am a newbie to root. Can Titanium Backup restore the paid apps? because some apps require online verification with Google at the first time of use.
Also, Z4root does not work on my N1. I want to use superoneclick but where can I find the driver for my win7? thanks
unroot
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks
zmalach said:
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks
Click to expand...
Click to collapse
If you see the padlock, you've got an unlocked boot-loader. This can't be re-locked.
Sent from my Nexus One using XDA App
I have a Canadian S4 and rooted using the twrp method and then installed the vigin google play edition rom. Everything worked fine at first when I installed it but i was fiddling around after in twrp and thought i should format the internal storage and start completely fresh and now if I install any rom including my original backup the device will boot up into the system fine for the first time but if the device resets after that it just hangs on the galaxy S4 logo and i have to reboot into recovery and flash again. Any ideas on how i could fix this? Thanks!!!
Try this, in twrp go into advanced wipe and wipe dalvik cache, cache, system, data and android secure. Then flash your nandroid.
I don't have a nandroid I have a twrp backup
Jaygrippa said:
I don't have a nandroid I have a twrp backup
Click to expand...
Click to collapse
That is a nandroid.
Dont use TWRP for the S4
From what I have experience and I believe others have as well, if you used TWRP to format where you had to type yes, you are pretty much screwed trying to get things working properly again. Maybe it is certain phones, sd cards, roms, who knows, but after I typed yes in TWRP to format everything, I could flash a rom but couldnt restart and things were buggy. I had to use odin to flash back to stock, re-root and flash the rom again. Now everything is 190% considering my battery life went from 6 hours to 28 with medium usage.
I have always loved TWRP on my other phones, but for the S4, its more frustration and using with caution than its worth.
Another word of caution, use windows to fix your phone. Im on linux and its too much of a pain in the ass to use odin/heimdall to go back to stock for newbs. On windows I went to stock and rooted again in no time.
Good luck!
jd1639 said:
That is a nandroid.
Click to expand...
Click to collapse
After doing that stuff in twrp should I flash right back to my backup of stock touch wiz or straight into the ROM of my choosing? Whenever I would have to reflash I would have to format he internal memory or it wouldn't work
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
You might have to. I had the same problem today where if the phone rebooted I would just get a black screen. I ended up using Odin with the stock rom, reinstalling twrp and then restoring my backup. I'm pretty sure it was a rom I flashed that caused the initial problem and only Odin would clear things up.
Start Over
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
ericchaffey said:
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
Click to expand...
Click to collapse
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Now the only problem is i have to find a Fido ROM
Jaygrippa said:
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Click to expand...
Click to collapse
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
ericchaffey said:
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
Click to expand...
Click to collapse
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Jaygrippa said:
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Click to expand...
Click to collapse
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
jd1639 said:
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
Click to expand...
Click to collapse
ya even they dont have a specific "Fido" firmware...
Anyone know if I can just use the Rogers ROM its pretty much the same company
Jaygrippa said:
Anyone know if I can just use the Rogers ROM its pretty much the same company
Click to expand...
Click to collapse
It'll work. It'll just put their bloatware on and the boot animation will be theirs
Reflashed
Ok so i reflashed to the stock rom using odin and bam it works again, im just wondering what is a good way now too root, and install the same rom i had
This will have everything you need http://forum.xda-developers.com/showthread.php?p=42320391
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Jaygrippa said:
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Click to expand...
Click to collapse
Glad to here it. Have fun.
This is the first time I've ever rooted an Android device. The process has been fraught with uncertainty and misinformation from around the internet. I'd like to describe what I have come to understand is the current preferred method, and ask a few questions to hopefully get my S5 where I want it to be.
I don't want to do anything to crazy (yet, anyway). I just want to remove some bloat and get the notification panel as close to vanilla Android as possible.
So far, I have ran towelroot, which was incredibly simple.
I installed SuperSU from the Play Store. During installation, it got stuck at "Disabling KNOX...". I have since learned that this is common and a reboot usually fixes it. However, I have also learned that I probably don't want to disable KNOX yet anyway, since I am not going to flash a custom ROM until there is one that is known to be stable and is able to create the vanilla Android experience that I want. Some people said that I should have installed SuperSU from chainfire's page instead of the Play Store, but I think that was old information.
Edit: I'm editing these steps as I go along:
1. Install busybox and the Safestrap APK
2. Use Safestrap to set up a new ROM slot and use that slot from now on (consider the italics a strikethrough)
^Even though the instruction video on the Safestrap page said this, apparently that's not what most people do. They use Safestrap to make a nandroid backup, and then use only one slot, the stock ROM slot, to experiment or flash a new ROM.
3. Install Titanium Backup
Edit: I also had to install SD KitKat Fixer and then reboot afterward to allow TB to write to the SD card...
4. Use Titanium Backup to backup all apps and data to SD card
5. Use Titanium to freeze processes that I carefully choose
Edit: I froze everything from the list here.
6. Install Xposed framework
7. Find the modules to customize Android how I want
Does that sound right? Any tips/advice?
ergalthema said:
So far, I have ran towelroot, which was incredibly simple.
Click to expand...
Click to collapse
By doing this, you are rooted.
Even if you are not going to flash a custom rom, you can and probably should disable KNOX. Doing so will not trip the counter.
Install busybox and the Safestrap APK - This is indeed necessary if you want to install another ROM to customize. The whole point of safestrap is to flash ROMs and is not related to rooting itself. The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state.
Use Safestrap to set up a new ROM slot and use that slot from now on - This is fine if you want to switch between ROMs. I know some people like to do this, but I am not one of them.
Install Titanium Backup - absolutely
Use Titanium to freeze processes that I carefully choose - correct and there are threads with lists of APKs to freeze. You will also want to make sure you freeze SDM so that it doesn't prompt for security updates.
Use Titanium as a backup? (not sure about this) - this is to backup your apps, texts, things like that but NOT your ROM
Install Xposed framework
Find the modules to customize Android how I want
jcollier said:
Install busybox and the Safestrap APK - This is indeed necessary if you want to install another ROM to customize. The whole point of safestrap is to flash ROMs and is not related to rooting itself. The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state.
Use Safestrap to set up a new ROM slot and use that slot from now on - This is fine if you want to switch between ROMs. I know some people like to do this, but I am not one of them.
Click to expand...
Click to collapse
The first step in installing Xposed in this thread is to do a nandroid backup. I'm not totally sure what that is, but someone in another thread said implied that Safestrap essentially does the same thing. That is why I was planning to use Safestrap.
ergalthema said:
The first step in installing Xposed in this thread is to do a nandroid backup. I'm not totally sure what that is, but someone in another thread said implied that Safestrap essentially does the same thing. That is why I was planning to use Safestrap.
Click to expand...
Click to collapse
That is what I meant by this: "The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state."
A nandroid is a backup image of your system so that you can restore it if you screw something up. Safestrap isn't "essentially" doing the same thing, it is doing exactly that thing. Safestrap is a way to make a custom recovery work on our phone without an unlocked bootloader.
Good advice up to here, but you might want to hold off on using Exposed. As I understand it, Exposed lets you tinker with the existing stock ROM. I don't think I would want to do that, and I have rooted and ROM flashed several Android devices over the years. But its up to you.
With your being new to rooting, I'll offer this advice:
Titanium Backup (a.k.a. "TIBU") is a good way to back up all your apps. Here are some suggestions in using it:
--Buy the PRO version. It has more features, is not very expensive, and helps support a really cool app that is very handy.
--Set the Preferences/Backup folder to your REAL external SD Card. It will default to internal storage (also called "sd card"....don't get me started lol) which is IMO totally useless. If you lose internal storage due to corruption or whatever, you would lose all your backups. Having them on the REAL SD card you can also archive them to your PC.
--Set your Max Backup History to some number larger than the default "1". I use 7. Why? Well, have you ever seen the developer of one of your favorite apps suddenly screw it completely up in some update? Or, worse yet, sell out to some other vendor who now made it a PAY SUBSCRIPTION app?? I have. By keeping multiple backups you can roll back in time to previous versions that you know WORKED when those things happen. I have several apps I will never update, especially on the Store, for various reasons. (TIBU used to be able to disconnect the link to the Store so apps didn't try to update, but Google broke their ability to do that).
--When you do make TIBU backups, select "app and system data" which is IMO incorrectly worded and causes confusion. It should read "app and APP data". Because that is what it really does. Backs up the data IN your system that is associated ONLY with the APP. NOT any "system files". When you restore a backup, restore "app and system data" and you not only get the app installed, you get all your data it created, as well as all your customized settings restored! It is a real time saver. And you can "usually" even do this with a new device, using the TIBU backup folder on an SD card you had in some previous Android device. I've done it many times.
Safestrap installs a custom version of TWRP recovery. From that you can make the aforementioned "nandroid" backups of your complete system. (You won't see the word "nandroid" in TWRP while you are doing this. It just calls them backups). Couple of caveats with TWRP (and the Safestrap version):
--The date/time stamp used in both TWRP and its alternative, Clockworkmod Recovery (CW) will always be wrong. I've read (in short) there is no way for them to fix it. BUT........you most certainly CAN edit the backup file name to be whatever you like while setting it up to make the backup. So I recommend deleting the portion of the name that is the screwed up date it will generate, and putting in a date you can read, like my preferred format of 2014-07-10-1727 which is today at 5:27 PM, or whatever format you like.
--By default, TWRP recovery uses (in the Advanced settings) an inane "power saving" feature of the display, which will maddeningly keep turning it off and making you think the phone died while it is in the middle of making your backup. A - ALWAYS keep your phone on the charger when working in Recovery!! Don't even start unless it has at least 40% charge. B- Turn OFF the inane "power saving feature" and get some peace of mind. The screen will stay lit forever, until you reboot system when you are done.
--By default, TWRP will be set to use INTERNAL STORAGE as the place to keep your nandroids. Again, I consider that a very bad idea. Use a REAL External SD card and keep them there. And make regular backups to your PC of the SD card. I've seen a great many SD cards suddenly fail without warning. Your device will pop up and tell you the SD card is corrupt, and you need to format it. Usually, there is no way to recover the lost data on the card when that happens.
--On my Galaxy S5, making a nandroid of the stock OS via Safestrap took up over 4GB! That is almost 4 x what I normally see making a nandroid of a custom ROM on some previous device. So make sure you have plenty of room on whatever SD card you choose to use.
jcollier said:
Even if you are not going to flash a custom rom, you can and probably should disable KNOX. Doing so will not trip the counter.
Click to expand...
Click to collapse
I didn't know it wouldn't trip the counter. I'm curious why I should disable it though.
I followed the video exactly and when I get to the point of the first Restore (around 9:00), it says "Restore Complete - Failed". There is a button to Reboot System. When I tap that, the phone won't turn on. I have to pull the batter to get it back on. I guess I'll be uninstalling Safestrap. If I "Uninstall Recovery" from the stock ROM slot, will the space be freed up again and the phone be returned to the same state as before I tried using Safestrap?
ergalthema said:
I followed the video exactly and when I get to the point of the first Restore (around 9:00), it says "Restore Complete - Failed". There is a button to Reboot System. When I tap that, the phone won't turn on. I have to pull the batter to get it back on. I guess I'll be uninstalling Safestrap. If I "Uninstall Recovery" from the stock ROM slot, will the space be freed up again and the phone be returned to the same state as before I tried using Safestrap?
Click to expand...
Click to collapse
May I ask what it is that you are restoring? Have you already made a (nandroid) backup? That's what the restore function is made to restore. If you tried to use Restore on some other kind of file, then it would try to overwrite your ROM (OS) with it, and make the phone unusable. If that happens, I think your only fix would be to Odin back to stock and start over from scratch. I believe there is a link to do that in the thread telling how to root the S5.
Zoandroid said:
May I ask what it is that you are restoring? Have you already made a (nandroid) backup?
Click to expand...
Click to collapse
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.
ergalthema said:
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.
Click to expand...
Click to collapse
Oh, OK. Since there aren't any ROMs available yet, I did not pursue that aspect of Safestrap. So you have stepped outside my range of experience with it. Hopefully someone else can help you.
If you get to a point in your endeavors where you find a solution to apply ad-blocking to the S5, please let me know in a PM. I've had no luck so far. It appears this will be yet another issue that will only be solved with some creative developer work. Google has done something in KitKat to block not only apps like Ad-Aware and Adblock Plus from working, they also seem to have some kind of snooper utility that, if you try to search online with the S5 for ad blocking, will pop up a browser page saying Google "cannot access" the page! Pages which my PCs can see easily. Crafty little PITAs for sure! I thought it might just be Chrome doing this, so when I tried to get Firefox from the Store, I was stuck in an endless downloading loop. I had to kill that and restore a copy from TIBU. They are doing everything they can think of to lock down a smartphone and spoon feed us only what THEY want us to see. Including copious advertisements.
There was a time when Android meant "freedom". I guess that time has passed. Now it is time for someone else with very deep pockets to re-kindle a hassle-free smartphone OS. It is a shame. Android has so much potential.
ergalthema said:
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.
Click to expand...
Click to collapse
Why flash the stock ROM in a newly created ROM slot? You should only create a ROM slot if you decide to run a custom ROM. If not, you can use safestrap to create the backup (nandroid) and save it to your SD card so you always have a "safe" restore point essentially. I run a custom ROM in my stock slot. And for the record... There are several ROMs in the development section which are quite stable. Also, you can check out the Safestrap thread there as well. If you read through the thread you'll have a better understanding of how it works and what bugs there are right now.
The thing that I find great about XDA is that folks will always try to help each other out. Good luck!
Sent from my SM-G900V using XDA Premium 4 mobile app
Do we have a thread where folks are reporting having tried various versions of the available ROMs for the Verizon S5, and can make a simple statement about what works and what doesn't? I think that would be a really good idea. Without something like that, the only way to really know which ones are trouble free is to slog through and read each and every post on every ROM thread, most of which will usually be outdated information anyway.
Maybe it could be done as a Poll so it doesn't grow into something just as long to read as the above.
Zoandroid said:
Do we have a thread where folks are reporting having tried various versions of the available ROMs for the Verizon S5, and can make a simple statement about what works and what doesn't? I think that would be a really good idea. Without something like that, the only way to really know which ones are trouble free is to slog through and read each and every post on every ROM thread, most of which will usually be outdated information anyway.
Maybe it could be done as a Poll so it doesn't grow into something just as long to read as the above.
Click to expand...
Click to collapse
That would be great - especially for the people who aren't on this site all day and don't know what is good and current.
shoresteve626 said:
Why flash the stock ROM in a newly created ROM slot? You should only create a ROM slot if you decide to run a custom ROM. If not, you can use safestrap to create the backup (nandroid) and save it to your SD card so you always have a "safe" restore point essentially. I run a custom ROM in my stock slot. And for the record... There are several ROMs in the development section which are quite stable.
Click to expand...
Click to collapse
I'm realizing that's probably what most people do. In the instructional video posted on the main Safestrap OP, it instructed to keep the original stock slot intact, and use a new slot for experimenting with another ROM. I would love to know a stable ROM that gives the most vanilla Android.
Hello- I am wondering if you can help me, yestyerday I had to reinstall the stock firmware for my note 3 on NC4 (thanks to Beantown's 106) after having great difficulty with the Biggins Rom ("unfortunately messagres has stopped, along with contacts and occasional android has stopped), I was unable to use the phone obviously let alone be able to explore this really cool rom. While trying to reset the phone, remove sache, dalvik, data etc. it did get to a point where the phone was stuck on the red Verizon Splash screen all the while Safestrap was still intact and by the end of the night after finding the stock firmware I was able to restore the phone to factory. The only issiue that I think would have caused these is finding and checking the boxes already set in 'root explorer' as opposed to what all the other apps are set to or possibly partitioning the new sd card but I doubt would cause an issue. I installed the rom the night before last and tried to fix the issue yesterday but was unable to which took most of last night to fix before I got it back up and running with the stock firmware. I would like to know how to get this rom back on without issues. Any advice would be great.
tjmethod said:
Hello- I am wondering if you can help me, yestyerday I had to reinstall the stock firmware for my note 3 on NC4 (thanks to Beantown's 106) after having great difficulty with the Biggins Rom ("unfortunately messagres has stopped, along with contacts and occasional android has stopped), I was unable to use the phone obviously let alone be able to explore this really cool rom. While trying to reset the phone, remove sache, dalvik, data etc. it did get to a point where the phone was stuck on the red Verizon Splash screen all the while Safestrap was still intact and by the end of the night after finding the stock firmware I was able to restore the phone to factory. The only issiue that I think would have caused these is finding and checking the boxes already set in 'root explorer' as opposed to what all the other apps are set to or possibly partitioning the new sd card but I doubt would cause an issue. I installed the rom the night before last and tried to fix the issue yesterday but was unable to which took most of last night to fix before I got it back up and running with the stock firmware. I would like to know how to get this rom back on without issues. Any advice would be great.
Click to expand...
Click to collapse
What firmware are you on? Were you OTA KK or MJE? (I know you said NC4, but was it OTA or did you use beans' .tar file?)
shaggy_kobain said:
What firmware are you on? Were you OTA KK or MJE? (I know you said NC4, but was it OTA or did you use beans' .tar file?)
Click to expand...
Click to collapse
Hi no OTA, I am on the KK NC4, which is how it came- it's an insurance replacement that I just received last week.
tjmethod said:
Hi no OTA, I am on the KK NC4, which is how it came- it's an insurance replacement that I just received last week.
Click to expand...
Click to collapse
Ok, so what they did was sent you a replacement with the KK OTA already on it.
Coming from NC4
1. Root with TowelRoot HERE[URL="https://towelroot.com/"]
[/URL]2. Install Busy Box from Play Store -Open App and Install
3. Install SuperSU- Open App and Install
4. Install SafeStrap 3.75 B04 HERE -Open App and Install
5. Reboot into SafeStrap, Wipe (Factory Reset) Stock Slot
6. Install BigginsRom
7. Reboot into Download Mode FROM WITHIN SAFESTRAP
8. Odin (AP slot) Updated NC2 Firmware for NC4 OTA users HERE
9. Reboot
----DONE----
**SOME USERS HAVE HAD TO DL SUPERSU AND FLASH THE ZIP AFTER FLASHING THEIR ROM***
Only IF you run into any issues after running SuperSU after installing in Step #3.
tjmethod said:
Hi no OTA, I am on the KK NC4, which is how it came- it's an insurance replacement that I just received last week.
Click to expand...
Click to collapse
To properly run most KK roms you need to flash the NC2 kernel. Instructions and download can be found here. You will only need to flash the kernel. If you are following the step by step instructions you can substitute any supported rom for the stock rom.
shaggy_kobain said:
Ok, so what they did was sent you a replacement with the KK OTA already on it.
Coming from NC4
1. Root with TowelRoot HERE[URL="https://towelroot.com/"]
[/URL]2. Install Busy Box from Play Store -Open App and Install
3. Install SuperSU- Open App and Install
4. Install SafeStrap 3.75 B04 HERE -Open App and Install
5. Reboot into SafeStrap, Wipe (Factory Reset) Stock Slot
6. Install BigginsRom
7. Reboot into Download Mode FROM WITHIN SAFESTRAP
8. Odin (AP slot) Updated NC2 Firmware for NC4 OTA users http://www.androidfilehost.com/?fid=235016813585512618. Reboot
----DONE----
**SOME USERS HAVE HAD TO DL SUPERSU AND FLASH THE ZIP AFTER FLASHING THEIR ROM***
Only IF you run into any issues after running SuperSU after installing in Step #3.
Click to expand...
Click to collapse
Thank you for the instructions- I will give it a go, but first verizon instructed me to take the phone to best buy to see if there's a problem with data since it somehow ate up 96% of my 2 gbs yesterday while I had problems- of course I didn't tell them I was rooted- dofood you know if there's a way to tell if the nc4 was an OTA or it was installed that way or does it even matter?
Thanks again
tjmethod said:
Thank you for the instructions- I will give it a go, but first verizon instructed me to take the phone to best buy to see if there's a problem with data since it somehow ate up 96% of my 2 gbs yesterday while I had problems- of course I didn't tell them I was rooted- dofood you know if there's a way to tell if the nc4 was an OTA or it was installed that way or does it even matter?
Thanks again
Click to expand...
Click to collapse
It doesn't matter since you can use TowelRoot to get root access. :good:
kinstre11 said:
To properly run most KK roms you need to flash the NC2 kernel. Instructions and download can be found here. You will only need to flash the kernel. If you are following the step by step instructions you can substitute any supported rom for the stock rom.
Click to expand...
Click to collapse
Hi thanks for the info- how would you suggest I save the stock rom if I need to go back to it or do I need to reinstall the firmware like I did last night?
tjmethod said:
Hi thanks for the info- how would you suggest I save the stock rom if I need to go back to it or do I need to reinstall the firmware like I did last night?
Click to expand...
Click to collapse
If you are already rooted you don't need to change anything with you rom. Just flash the NC2 kernel found in the link from my previous post using Odin. The kernel is not the bootloader img, You are already on the NC4 bootloader and can not go back, but flashing the NC2 kernel will leave you with the so-called Unified firmware (NC2/NC4). This is what is needed for most KK roms.
kinstre11 said:
If you are already rooted you don't need to change anything with you rom. Just flash the NC2 kernel found in the link from my previous post using Odin. The kernel is not the bootloader img, You are already on the NC4 bootloader and can not go back, but flashing the NC2 kernel will leave you with the so-called Unified firmware (NC2/NC4). This is what is needed for most KK roms.
Click to expand...
Click to collapse
Ok but is there a way to save the stock rom? when I root again and have any issue and need to go back to stock or I will need to DL the firmware again since I will have had the unified firmware on. Also since I like the stock rom besides the Samsung lag, I saw a rom that is based on stock but I think alot better from what I read and is deodexed, do you know what that means?
Thanks you!
tjmethod said:
Ok but is there a way to save the stock rom? when I root again and have any issue and need to go back to stock or I will need to DL the firmware again since I will have had the unified firmware on. Also since I like the stock rom besides the Samsung lag, I saw a rom that is based on stock but I think alot better from what I read and is deodexed, do you know what that means?
Thanks you!
Click to expand...
Click to collapse
Assuming you have Safestrap installed as it is the only way to flash a custom rom on retail Note 3, all you need to do is boot into Safestrap and make a backup. It will be stored on your external SD card and if you want to revert back to it simply wipe the stock rom slot in Safestrap then restore your backup. As you are on NC4 you won't be able to use a rom slot in Safestrap other than the stock slot, and you always want to wipe system, dalvik, cache, and data before installing any new rom.
Odex/Deodex is how the system stores and reads apps. Standard out of the box is usually (perhaps always) odex. This method breaks the apps into 2 parts. It allows for faster loading and searching of the system. Deodex keeps the apps as one entity. This means that the initial loading of the system will take longer but in the end we get easier customization/tweaking. Xposed framework needs a Deodex rom to run (I believe). I'm fairly sure most developers that make custom roms deodex their roms. (My understanding of Odex/Deodex may be flawed but this is a basic explanation, for more info you can always Google, or search these forums).
kinstre11 said:
Assuming you have Safestrap installed as it is the only way to flash a custom rom on retail Note 3, all you need to do is boot into Safestrap and make a backup. It will be stored on your external SD card and if you want to revert back to it simply wipe the stock rom slot in Safestrap then restore your backup. As you are on NC4 you won't be able to use a rom slot in Safestrap other than the stock slot, and you always want to wipe system, dalvik, cache, and data before installing any new rom.
Odex/Deodex is how the system stores and reads apps. Standard out of the box is usually (perhaps always) odex. This method breaks the apps into 2 parts. It allows for faster loading and searching of the system. Deodex keeps the apps as one entity. This means that the initial loading of the system will take longer but in the end we get easier customization/tweaking. Xposed framework needs a Deodex rom to run (I believe). I'm fairly sure most developers that make custom roms deodex their roms. (My understanding of Odex/Deodex may be flawed but this is a basic explanation, for more info you can always Google, or search these forums).
Click to expand...
Click to collapse
Hi thanks and yes I'll be googling more before doing. Do you have any idea while the phone was stuck on the verizon splash screen yet SS still worked, why the phone was sucking up huge amounts of data while on the Higgins Rom while it had issues and while trying to reinstall stock firmware?
Thanks again! I can't seem to find the "Thanks" button?
tjmethod said:
Hi thanks and yes I'll be googling more before doing. Do you have any idea while the phone was stuck on the verizon splash screen yet SS still worked, why the phone was sucking up huge amounts of data while on the Higgins Rom while it had issues and while trying to reinstall stock firmware?
Thanks again! I can't seem to find the "Thanks" button?
Click to expand...
Click to collapse
The splash screen freeze could have been caused by the rom not being compatible with the NC4 kernel combined with possibly wiping system via safestrap. Safestrap is not wiped when you wipe the system it remains installed separately (this is what allows us to wipe and install.
The data drain may also be linked to the incompatibility, however I would be unable to answer that as I have never experienced such an issue nor have I read about it on any forums.
Once you are set up with the proper firmware, I would suggest doing a factory reset before flashing any further roms. You may need to reroot and reinstall busybox and safestrap afterwards but it will reset any residual system alterations that may be left from the previous biggins problem.
tjmethod said:
Ok but is there a way to save the stock rom? when I root again and have any issue and need to go back to stock or I will need to DL the firmware again since I will have had the unified firmware on. Also since I like the stock rom besides the Samsung lag, I saw a rom that is based on stock but I think alot better from what I read and is deodexed, do you know what that means?
Thanks you!
Click to expand...
Click to collapse
I made a full backup of my stock nc4 rom before I flashed biggins rom and flashed nc2 kernel. I restored my stock rom to see if it would run on the nc2 kernel and it froze at the red Verizon splash screen. The nc4 kernel will need to be reflashed after going back to stock. However, biggins rom is basically perfect so I have no real intentions on going back anytime soon.
kinstre11 said:
To properly run most KK roms you need to flash the NC2 kernel. Instructions and download can be found here. You will only need to flash the kernel. If you are following the step by step instructions you can substitute any supported rom for the stock rom.
Click to expand...
Click to collapse
Thanks or that important point, I'm back up and running with the unified firmware on Biggins- very cool but the battery seems to lack a bit.
shaggy_kobain said:
It doesn't matter since you can use TowelRoot to get root access. :good:
Click to expand...
Click to collapse
hi thanks alot for all your guidance- I'm finnaly back on with biggins but the batterry seems a little less in performance than stock. Any idea as to how to improve this or know of a rom that is has better battery stats? I reall like the Biggins though
tjmethod said:
hi thanks alot for all your guidance- I'm finnaly back on with biggins but the batterry seems a little less in performance than stock. Any idea as to how to improve this or know of a rom that is has better battery stats? I reall like the Biggins though
Click to expand...
Click to collapse
First, you are welcome. Second, did you flash in Stock Slot or a ROM Slot?
Generally, performance on any ROM for battery life is measured after the ROM has time to "settle". It was about 48 hours after I flashed Biggins that I noticed my battery life increase significantly. I can't say that for other ROMS, as I have only been on Biggins, but it seems to be the general consensus all in all.
I do know that if you flashed on a ROM Slot, that for some reason battery consumption is drastic. Again, some have reported otherwise, but in general that seems a culprit to some.
However you flashed the ROM, 3 things will help
1) Let the ROM settle. After 48 hours if you see that the battery is still suckus, then switch to alternate (Stock Slot or whichever)
2) Check your Wakelocks. There is an app in the playstore that you can dl that will measure what is running in the background and then you can shut it down using Greenify
3) Always Greenify
Greenify is a lifesaver to some, and added with a ROM that already has ridiculous battery life (that was meant in a good way ) then you can push about 2 days on one full charge.
Hopefully this helps, if not, then you know where to find me :good:
shaggy_kobain said:
First, you are welcome. Second, did you flash in Stock Slot or a ROM Slot?
Generally, performance on any ROM for battery life is measured after the ROM has time to "settle". It was about 48 hours after I flashed Biggins that I noticed my battery life increase significantly. I can't say that for other ROMS, as I have only been on Biggins, but it seems to be the general consensus all in all.
I do know that if you flashed on a ROM Slot, that for some reason battery consumption is drastic. Again, some have reported otherwise, but in general that seems a culprit to some.
However you flashed the ROM, 3 things will help
1) Let the ROM settle. After 48 hours if you see that the battery is still suckus, then switch to alternate (Stock Slot or whichever)
2) Check your Wakelocks. There is an app in the playstore that you can dl that will measure what is running in the background and then you can shut it down using Greenify
3) Always Greenify
Greenify is a lifesaver to some, and added with a ROM that already has ridiculous battery life (that was meant in a good way ) then you can push about 2 days on one full charge.
Hopefully this helps, if not, then you know where to find me :good:
Click to expand...
Click to collapse
Great I'm at the 48 hr. mark so maybe I'll see some improvement- I will check out Geenify, I recently heard about and am using Clean Master- have you checked it out?... seems like a good utility widget. Yes I did the stock slot since I was told before installing Baja which actually had really good battewry performace but I just wasnt crazy about the rom.
I dont see a thanks button?
tjmethod said:
Great I'm at the 48 hr. mark so maybe I'll see some improvement- I will check out Geenify, I recently heard about and am using Clean Master- have you checked it out?... seems like a good utility widget. Yes I did the stock slot since I was told before installing Baja which actually had really good battewry performace but I just wasnt crazy about the rom.
I dont see a thanks button?
Click to expand...
Click to collapse
Great, you should see some improvement soon enough :good: Yes I have heard about CM, I use it on a regular basis
If you are using Tapatalk, it'll be a "thumbs up" at the top. If not, then I dunno lol.... no worries, i'm sure you'll find it eventually :laugh:.
shaggy_kobain said:
Great, you should see some improvement soon enough :good: Yes I have heard about CM, I use it on a regular basis
If you are using Tapatalk, it'll be a "thumbs up" at the top. If not, then I dunno lol.... no worries, i'm sure you'll find it eventually :laugh:.
Click to expand...
Click to collapse
I dl'd in on the phone but haven't used it yet- I'm going to dl in here too ( wifi note 2014 10.1)- ya so last night roughly 8 or soon after I had 38% the night before 15% around same time so its getting better battery. The other day I saw carbon rom, have you seen that? you can minimize apps like pages on windows while running multiples but one sight said our note 3 isnt compatable yet a couple other carriers versions are. Another site said it is but I can't find it- it seems like the rom of all roms…
Quick Sanity Check here. I mainly just want to confirm that I have all my ducks in a row before I pull the trigger on installing my first ROM on my 3 mo old S5. I have flashed ROMS in the past on other devices, but it has been 3 years or so, and then it was on the first day I got said device. I have been using my S5 for a few months now, and I don't want to lose any of my accumulated data. So here goes.
Running Stock 4.4.4 on G900V
I am Rooted via Towelroot, and I have installed Safestrap recovery. I also completed a Nandroid backup.
I completed a Titanium backup of all my apps and system settings just now.
I plan to flash the MOAR Rom to stock slot via Safestrap, and upon completion, do a restore from Titanium.
My hope is that by doing that, I will wind up with a custom ROM, but with all my contacts, sms messages, Apps and app settings, which is actually the entire point of this post.
Am I right in assuming that if I follow those steps, I should be good?
Your advice/confirmation/response will be appreciated!! Thanks!
Wow.. 40 views and no one knows the answer to my query? I just need a quick yes if my hunch is true, or if I'm off, just a no and a few small words or correction. Thanks will be given!
musiclover7 said:
Wow.. 40 views and no one knows the answer to my query? I just need a quick yes if my hunch is true, or if I'm off, just a no and a few small words or correction. Thanks will be given!
Click to expand...
Click to collapse
Make sure to backup call log, and the sms in titanium as well. The easiest way to keep everything the same app and data wise is to wipe all partitions besides micro sd and data, and then flash do a slightly dirty flash. Thats what I did, and it worked just fine. Just make sure to back up, and after you flash, make sure to odin the oa8 kernel as well. Also make sure to flash the kernel before first boot. Btw my phone took a while to boot up, so dont be too worried if it takes longer than 5 minutes. Mine took like 10-15 minutes, and has been rock solid since. Hope this helps!
Thorkle said:
Make sure to backup call log, and the sms in titanium as well. The easiest way to keep everything the same app and data wise is to wipe all partitions besides micro sd and data, and then flash do a slightly dirty flash. Thats what I did, and it worked just fine. Just make sure to back up, and after you flash, make sure to odin the oa8 kernel as well. Also make sure to flash the kernel before first boot. Btw my phone took a while to boot up, so dont be too worried if it takes longer than 5 minutes. Mine took like 10-15 minutes, and has been rock solid since. Hope this helps!
Click to expand...
Click to collapse
Thanks Thorkle! Are you sure I only need to flash OA8 Kernel? When I look at JKRuse's instructions here:
http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-t3024731
It mentions that it is important to flash the entire firmware, not just the kernel...
"6. flash VZW_BOA8_RETAIL_FIRMWARE_ONLY.tar.md5 Make sure it is the retail firmware and not just the kernel"
Of course, the link that is provided to said firmware does not work, and I have not been able to find a working one on the net so far. Anyone who has a link to that firmware, please share...
I got it installed and working. I am loving this new ROM!
musiclover7 said:
I got it installed and working. I am loving this new ROM!
Click to expand...
Click to collapse
Several people that have restored data, even in TIBU have run into problems. The suggested method is a full wipe and clean install. With that being said I resorted some data with TIBU and never had any issues.
jrv331 said:
Several people that have restored data, even in TIBU have run into problems. The suggested method is a full wipe and clean install. With that being said I resorted some data with TIBU and never had any issues.
Click to expand...
Click to collapse
So far it seems to be working very well for me. I only restored data from about 10-15 apps, none of which were red in TIBU. Messages, Contacts, email, etc.
So far, my phone feels much smoother than it did on 4.4.4. Battery life is good as well. I fell asleep with 55% last night, and about an hour after waking up this morning, I noticed I was at 51%. That is a marked improvement. Here is hoping that sentiment holds.
musiclover7 said:
Of course, the link that is provided to said firmware does not work, and I have not been able to find a working one on the net so far. Anyone who has a link to that firmware, please share...
Click to expand...
Click to collapse
if you look at the URL for the firmware, then look at the other URLs to download files in that post it will give you the clue to fix the firmware link to make it work. TIP: add a t to the end.