So I am getting ready to make the move to root / custom rom on a ZVA. It seems there are some mixed thoughts on best route to root. What is the easiest method right now that works with that rev?
Also, I am thinking about going with Cyanogen. Could anyone give their 2 cents on that vs stock rom? Part of the reason for my decision is I am getting tired of the lag on my stock ROM even after I disabled all the bloat that I could. Does lag go away with CM?
Also... does the power on/off work the same? Call me crazy, but I would rather not have the double tap screen on function. I would like to be forced to use the button.
Any final pointers when it comes to the process?
Thanks.
Best way in my opinion is to revert back to zv4, then use Stump root, then bump, then add TWRP recovery. Some are having issues with the one clicks working with stock 5.0.1. I think this is the safest way, but you must be familiar with ODIN when messing with firmware flashing. Stock versus aftermarket roms are usually based on what you want. For me, I use WiFi calling all the time, so I can't use aftermarket roms, because WiFi calling only works on stock based roms. In my experience, battery is not that much better on either kind of rom. CM to me is too plain, I'd rather use Pacman, more feature packed.
sent from my LG G3
edufur said:
So I am getting ready to make the move to root / custom rom on a ZVA. It seems there are some mixed thoughts on best route to root. What is the easiest method right now that works with that rev?
Also, I am thinking about going with Cyanogen. Could anyone give their 2 cents on that vs stock rom? Part of the reason for my decision is I am getting tired of the lag on my stock ROM even after I disabled all the bloat that I could. Does lag go away with CM?
Also... does the power on/off work the same? Call me crazy, but I would rather not have the double tap screen on function. I would like to be forced to use the button.
Any final pointers when it comes to the process?
Thanks.
Click to expand...
Click to collapse
I just did this exact same thing and it was really easy.. I did this for root http://forum.xda-developers.com/showthread.php?t=
Then i just use the one click app here http://forum.xda-developers.com/showthread.php?t= to flash twrp and flashed CyanogenMod without needing to downgrade my phone at all.. BUT WHEN YOU USE THIS APP YOU WILL MOST LIKELY GET A SECURITY ERROR WHEN BOOTING BACK TO STOCK ROM SO MAKE SURE YOU HAVE CYANOGENMOD ALREADY DOWNLOADED TO YOUR EXTERNAL SD CARD AND FLASH IT AND IT WILL BOOT UP FINE
churchey360 said:
I just did this exact same thing and it was really easy.. I did this for root http://forum.xda-developers.com/showthread.php?t=
Then i just use the one click app here http://forum.xda-developers.com/showthread.php?t= to flash twrp and flashed CyanogenMod without needing to downgrade my phone at all.. BUT WHEN YOU USE THIS APP YOU WILL MOST LIKELY GET A SECURITY ERROR WHEN BOOTING BACK TO STOCK ROM SO MAKE SURE YOU HAVE CYANOGENMOD ALREADY DOWNLOADED TO YOUR EXTERNAL SD CARD AND FLASH IT AND IT WILL BOOT UP FINE
Click to expand...
Click to collapse
I was able to root with the root tool on ZVA. I had to do some manual stuff to make it fully work, but it did. I also loaded the TWRP and CM12.1. Everything is working great as far as the ROM goes. I am having issues though with the phone not being able to reboot without pulling the battery first. If I don't do that, it just goes blank and does not power up.
I'm with you I just recently rooted mine on ZVA and tried the one click scripts but none of them worked for me. I had to use the script for ZVA but enter it manually which was still pretty easy and worked first try. Now I'm trying to figure out how to go about a custom recovery so i can run Xposed and maybe a custom ROM. I'v been reading a lot and I haven't come across any proven method to do it on ZVA. Seems like you can do it with AutoRec but like churchey360 said you have to have a ROM on your phone already that you can boot into because the stock will bring up the security error and I'm not sure if Flashify still works for recovery.
Related
I am very new to flashing ROMs. I have Flashed the Route66 and also the t0ltevzw ROM as well. The trouble I am having is flashing the ClockworkMOD . I have tried also using the GN2 Toolkit with the stock ROM, and I have no luck in getting CWM onto the device. I have tried also flashing CWM from ODIN and I get errors.
When I turn on the phone and try to get to CWM, I get a message that a software not provided by Verizon...blah blah and I need to take phone into VZW. It fixes after I flash a ROM back to the device.
Can someone explain what I am doing wrong, or what step I am missing, or what proper ROM to use?
As stated, I already tried using the stock 4.1.1 ROM along with GNII Toolkit to flash CWM and SU and they fail everytime.
At present I have flashed the Route66 ROM back to my device and I have ROM Manager installed and I have already tried flashing CWN 6.0.2.6
Sounds like you are in the sameboat I was about a week ago, the fix to this is to unlock your bootloader first which can be done following some guides in the Development section, you'll want to start with flashing a stock ROM image to the phone through ODIN which you can get one through the "[ODIN][VRALJB] Restore to Stock" by imnuts in the Development section, this should make it so you can reaccess the phone again to atleast use it, then you'll want to look into the "How to Unlock Your Bootloader -New and Improved Super Easy-" thread from the Original Android Development form for Verizon Note II, this you will want to read everything through so you get it right the first time which it will unlock your bootloader so you are able to install customer ROMs which then I highly recommend Scotts Clean ROM.
Let me know if you have any questions on the process or if you are able to get back on your feet!
soulsk8r99 said:
Sounds like you are in the sameboat I was about a week ago, the fix to this is to unlock your bootloader first which can be done following some guides in the Development section, you'll want to start with flashing a stock ROM image to the phone through ODIN which you can get one through the "[ODIN][VRALJB] Restore to Stock" by imnuts in the Development section, this should make it so you can reaccess the phone again to atleast use it, then you'll want to look into the "How to Unlock Your Bootloader -New and Improved Super Easy-" thread from the Original Android Development form for Verizon Note II, this you will want to read everything through so you get it right the first time which it will unlock your bootloader so you are able to install customer ROMs which then I highly recommend Scotts Clean ROM.
Let me know if you have any questions on the process or if you are able to get back on your feet!
Click to expand...
Click to collapse
Thanks for the reply. I will look into your suggestion. Is thios suggested ROM really close to the original stock? I only ask because I prefer one that is as original as possible.
techiexp1969 said:
Thanks for the reply. I will look into your suggestion. Is thios suggested ROM really close to the original stock? I only ask because I prefer one that is as original as possible.
Click to expand...
Click to collapse
Yes, it is nearly identical to stock just with added features like the Hotspot is fully unlocked so you can tether for free and you can choose to add a new kernel to the phone so you will be able to overclock/underclock and undervolt it to either improve performance or make your battery last for ever. The install is easy since he incorporated a nice GUI to for the install which prompts you along the way for what stuff you want to have on the phone which you can make it as stock as you want with Touchwiz (orig Samsung interface) or bump up the customization with Nova launcher or Apex which personally I've used both an Nova is better thus far. There has been known issues with the GPS with the ROM however getting the GPS Status & ToolKit app from the Play Store then running the Download option fixes it to the extent of my testing.
And one other thing I just remembered which you may or may not run into is if you use Linux on your PC Odin generally is not going to work since there really are no Drivers for it on Linux so getting your hands on a WIndows system would be idea but a Virtual machine may work but I haven't tried that yet.
thanks
soulsk8r99 said:
Yes, it is nearly identical to stock just with added features like the Hotspot is fully unlocked so you can tether for free and you can choose to add a new kernel to the phone so you will be able to overclock/underclock and undervolt it to either improve performance or make your battery last for ever. The install is easy since he incorporated a nice GUI to for the install which prompts you along the way for what stuff you want to have on the phone which you can make it as stock as you want with Touchwiz (orig Samsung interface) or bump up the customization with Nova launcher or Apex which personally I've used both an Nova is better thus far. There has been known issues with the GPS with the ROM however getting the GPS Status & ToolKit app from the Play Store then running the Download option fixes it to the extent of my testing.
Click to expand...
Click to collapse
I wanted to come back and just say thanks for the help/suggestions. Tho I have flashed a couple roms, I was a bit shaky about unlocking the BL. But it went without a hitch and I did try the CleanROM. It is nice and fast. I I love having all the toggles and the All App Multiview. I only had a small issue recovering a backup. It sucks that not all roms support putting all your icons as they were. Anyways, thanks again and I liked the rom so much I donated because I know this stuff takes time.
I got the S4 back when it first came out, and messed around with some CM ROMs and other custom ROMs that worked fairly well. The big killers for me though were bluetooth audio not working, not being able to use headphone microphones, and the proximity sensor being all weird. So I reverted to stock but kept root, and eventually upgraded to MJ7 while keeping root. When I boot I still get the 'Samsung Custom' bootscreen.
I've never been happy with Touchwiz, and have all of the Samsung features turned off. The stock messaging app is really the thing that bugs the hell out of me, since it takes forever to get messages (sometimes up to an hour, while Handcent will get them right away), and I love my Nexus 7 experience. I'd really like to get as close to a 'Google' phone as possible, but I'm currently stuck on Verizon.
I've tried using GooManager to download the recovery managers again, but it's having problems with 404 errors downloading the scripts. I tried ROM Manager and it says it installs ClockworkMod (6.0.44 in fact), but it refuses to boot into recovery mode. Most of the tools I'm finding are not for MJ7, so I'm kind of hesitant to solutions that aren't for my current version. Since I can't make any backups without being able to boot into a proper recovery mode, that's another kind of notch against using most of the guides.
I don't mind the actual process of doing the work, I'm just not sure where to go from here. What are my options?
dragonmantank said:
I got the S4 back when it first came out, and messed around with some CM ROMs and other custom ROMs that worked fairly well. The big killers for me though were bluetooth audio not working, not being able to use headphone microphones, and the proximity sensor being all weird. So I reverted to stock but kept root, and eventually upgraded to MJ7 while keeping root. When I boot I still get the 'Samsung Custom' bootscreen.
I've never been happy with Touchwiz, and have all of the Samsung features turned off. The stock messaging app is really the thing that bugs the hell out of me, since it takes forever to get messages (sometimes up to an hour, while Handcent will get them right away), and I love my Nexus 7 experience. I'd really like to get as close to a 'Google' phone as possible, but I'm currently stuck on Verizon.
I've tried using GooManager to download the recovery managers again, but it's having problems with 404 errors downloading the scripts. I tried ROM Manager and it says it installs ClockworkMod (6.0.44 in fact), but it refuses to boot into recovery mode. Most of the tools I'm finding are not for MJ7, so I'm kind of hesitant to solutions that aren't for my current version. Since I can't make any backups without being able to boot into a proper recovery mode, that's another kind of notch against using most of the guides.
I don't mind the actual process of doing the work, I'm just not sure where to go from here. What are my options?
Click to expand...
Click to collapse
Well unfortunately for you you're on MJ7 which means your only options right now are rooting and Xposed. Other than that though, there's really nothing else you can do at the moment. If you were on ME7 or MI1 still you could at least run Safestrap, but even then you would be limited to Touchwiz based roms. Unless you're willing to go on the hunt for an MDK S4 you'll just have to deal with your limited options for now. Oh and before you ask, there is absolutely no way to revert back to earlier firmwares. Once you update, you're stuck.
Crawshayi said:
Well unfortunately for you you're on MJ7 which means your only options right now are rooting and Xposed. Other than that though, there's really nothing else you can do at the moment. If you were on ME7 or MI1 still you could at least run Safestrap, but even then you would be limited to Touchwiz based roms. Unless you're willing to go on the hunt for an MDK S4 you'll just have to deal with your limited options for now. Oh and before you ask, there is absolutely no way to revert back to earlier firmwares. Once you update, you're stuck.
Click to expand...
Click to collapse
Yeah, I know I couldn't revert the firmware to something earlier. Is it possible to revert to stock even? At this point I think I just want to revert it and sell this phone off and get something else. I don't care about KNOX status, just getting it back to stock so that whomever buys it won't keep getting security notifications.
dragonmantank said:
Yeah, I know I couldn't revert the firmware to something earlier. Is it possible to revert to stock even? At this point I think I just want to revert it and sell this phone off and get something else. I don't care about KNOX status, just getting it back to stock so that whomever buys it won't keep getting security notifications.
Click to expand...
Click to collapse
Yes I believe it's possible, I found this thread that gives you an Odin image to flash: http://forum.xda-developers.com/showthread.php?t=2507217
The security notification was actually fixed and supposedly an update was pushed out, but maybe yours didn't grab the update properly? I'm not sure, but that Odin image should get you back to factory stock. If I were you I would get an HTC One if you can live with not having a removable battery and sd card.
Awesome, thank you very much.
I'm re-flashing today take it back. I'll have a look at the HTC One, since it wasn't out when I got my S4. I know that (at the time) the S4 was the only Android phone I had found, with the One a close second but not available. I would really love a Google phone, but I get the feeling that will probably never happen on VZW.
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Bump in hopes of someone's experience or advice.
falkon114 said:
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Click to expand...
Click to collapse
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
*see below*
Jiggabitties said:
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
Click to expand...
Click to collapse
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
falkon114 said:
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
Click to expand...
Click to collapse
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Jiggabitties said:
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Click to expand...
Click to collapse
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
falkon114 said:
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
Click to expand...
Click to collapse
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Jiggabitties said:
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Click to expand...
Click to collapse
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
falkon114 said:
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
Click to expand...
Click to collapse
Glad I could help in any way. Bummer about your camera.
I've had my brand new SCH-I545 since thanks giving now. I've been trying to root and get a custom ROM on the phone ever since then and have gotten closer and closer but haven't been able to quite get everything to co-operate.
I may catch scorn for posting such a generic question on a flagship phone but I've been up all night for 2 weeks now trying to get this to work following numerous tutorials but with android everything seems to get outdated when there are so many software variables at hand that are constantly changing like firmwares and build numbers. I've included all the info since it all seems to be vital and have tried to seperate tasks by paragraph so you can skip over what you feel may be arbritrary. So if I could get an up to date breakdown on how I could succeed in my endevour I'd appreciate it greatly.
Out the box I have a 4.4.2 and NK1 build number. I was finally able to get root access through towel root after flashing back to NC5. However even after flashing NC5 through odin, about phone still says my baseband and build number end I545VRUFNK1 but towelroot no longer gives me the "phone not supported" message and I'm able to succesfully atain root access, confirmed by root checker. Is that normal?
So I have root now but want a custom ROM. VZW locks the bootloaders on new phones so I believe that means I can't use a custom recovery like CWM. I've tried and tried but it doesn't work, neither does the CWM Rom manager app. I've managed to get a custom recovery through installing BusyBox and Safestrap. (I had to go through several apk's to get Safestrap to work. Usually I would be able to enter TWRP recovery through it but the recovery won't respond to any of my touches. The power button still works to turn the screen on and off so it is not frozen but it won't respond when I swipe to unlock it. Even now that I have it working, if the screen locks I'm unable to unlock it even if TWRP is performing a task in the backround and clearly not frozen.
One time I was able to more or less successfully flash LiquidSmooth (LS-KK-v3.2-2014-10-04-jflte.zip). This was the closest I ever got to my goal as the ROM succesfully booted up and I was able to browse the home screen and change all the settings and it was a moment of joy until I went to settings and switched wifi on it just wouldn't. It either just wouldn't switch or would switch right back and grey itself out I don't remember exactly. My phone had no service either for calls, text or 4G. So everything worked internally it just couldnt comunicate with any signals coming from outside the phone. Why would this be? If I manage to boot LiquidSmooth again is there something I could download to make the wifi/service work? (I could download through USB or Odin.)
After this I tried to flash CM but the phone wouldnt even start after installation and would just bootloop so I had to flash back to stock to make it work again. Then I tried LiquidSmooth several more times but now I get stuck at the bootscreen for LiquidSmooth where it has the logo and the backround flashing. I've let the animation loop for several minutes multiple times before doing a battery pull.
Basically for 2 weeks I've been flashing NC5->rooting->flashing NK1 back->installing safestrap->installing a rom->soft bricking->flashing back to stock ROM and starting again
Is it possible if I keep doing this proccess that it will just work one time? It may sound silly but I kind of believe just because I've had varrying degrees of success following the exact same procedure.
And when I install a ROM in TWRP I go Wipe->(swipe factory reset)->Install->(select LS.zip and wait for it to say its succesfully installed)->Swipe one more time to wipe cache->Reboot after this the phone either fails to start up or loops the LiquidSmooth animation. As I said, one time it started succesfully.
Let me know what any of this information leads you to believe and if you may have a sollution in mind. Huge thanks to anyone that read this and will try to help me. I've had this phone 2 weeks now and would like to start actually using it.
unorthodocks said:
I've had my brand new SCH-I545 since thanks giving now. I've been trying to root and get a custom ROM on the phone ever since then and have gotten closer and closer but haven't been able to quite get everything to co-operate.
I may catch scorn for posting such a generic question on a flagship phone but I've been up all night for 2 weeks now trying to get this to work following numerous tutorials but with android everything seems to get outdated when there are so many software variables at hand that are constantly changing like firmwares and build numbers. I've included all the info since it all seems to be vital and have tried to seperate tasks by paragraph so you can skip over what you feel may be arbritrary. So if I could get an up to date breakdown on how I could succeed in my endevour I'd appreciate it greatly.
Out the box I have a 4.4.2 and NK1 build number. I was finally able to get root access through towel root after flashing back to NC5. However even after flashing NC5 through odin, about phone still says my baseband and build number end I545VRUFNK1 but towelroot no longer gives me the "phone not supported" message and I'm able to succesfully atain root access, confirmed by root checker. Is that normal?
So I have root now but want a custom ROM. VZW locks the bootloaders on new phones so I believe that means I can't use a custom recovery like CWM. I've tried and tried but it doesn't work, neither does the CWM Rom manager app. I've managed to get a custom recovery through installing BusyBox and Safestrap. (I had to go through several apk's to get Safestrap to work. Usually I would be able to enter TWRP recovery through it but the recovery won't respond to any of my touches. The power button still works to turn the screen on and off so it is not frozen but it won't respond when I swipe to unlock it. Even now that I have it working, if the screen locks I'm unable to unlock it even if TWRP is performing a task in the backround and clearly not frozen.
One time I was able to more or less successfully flash LiquidSmooth (LS-KK-v3.2-2014-10-04-jflte.zip). This was the closest I ever got to my goal as the ROM succesfully booted up and I was able to browse the home screen and change all the settings and it was a moment of joy until I went to settings and switched wifi on it just wouldn't. It either just wouldn't switch or would switch right back and grey itself out I don't remember exactly. My phone had no service either for calls, text or 4G. So everything worked internally it just couldnt comunicate with any signals coming from outside the phone. Why would this be? If I manage to boot LiquidSmooth again is there something I could download to make the wifi/service work? (I could download through USB or Odin.)
After this I tried to flash CM but the phone wouldnt even start after installation and would just bootloop so I had to flash back to stock to make it work again. Then I tried LiquidSmooth several more times but now I get stuck at the bootscreen for LiquidSmooth where it has the logo and the backround flashing. I've let the animation loop for several minutes multiple times before doing a battery pull.
Basically for 2 weeks I've been flashing NC5->rooting->flashing NK1 back->installing safestrap->installing a rom->soft bricking->flashing back to stock ROM and starting again
Is it possible if I keep doing this proccess that it will just work one time? It may sound silly but I kind of believe just because I've had varrying degrees of success following the exact same procedure.
And when I install a ROM in TWRP I go Wipe->(swipe factory reset)->Install->(select LS.zip and wait for it to say its succesfully installed)->Swipe one more time to wipe cache->Reboot after this the phone either fails to start up or loops the LiquidSmooth animation. As I said, one time it started succesfully.
Let me know what any of this information leads you to believe and if you may have a sollution in mind. Huge thanks to anyone that read this and will try to help me. I've had this phone 2 weeks now and would like to start actually using it.
Click to expand...
Click to collapse
The issue is that safestrap is incompatible with the roms you are trying to use. It can be only used with Touchwiz based roms(i.e. using the stock kernel). Try flashing hyperdrive rom. Also, Im not familiar if NK1 can use towelroot and safestrap well. My recommendation would be to
1. clean wipe to nc5
2. towel root
3. install safestrap
4. flash ONLY roms that say they were safestrap compatible.
5. Flash any patches, modems, etc.
Weeks? How about spending a few hours reading up on what you can and can't do with your phone.
Raymondlikesroot said:
The issue is that safestrap is incompatible with the roms you are trying to use. It can be only used with Touchwiz based roms(i.e. using the stock kernel). Try flashing hyperdrive rom.
Click to expand...
Click to collapse
Ok, thanks, I was going to try to flash hyperdrive but the ROM I found was 1.2GB and I didn't have that much space on my SD. I'll borrow an empty one and try it again. Is it not odd that LS did a full boot if it's not compatible with safestrap? And are there any other Touchwiz roms? I don't like Touchwiz and am trying to get as far from it as I can but if I could just delete the bloatware (which I can still only disable after towel root), get SD access and get rid of the battery restrictions.
unorthodocks said:
Ok, thanks, I was going to try to flash hyperdrive but the ROM I found was 1.2GB and I didn't have that much space on my SD. I'll borrow an empty one and try it again. Is it not odd that LS did a full boot if it's not compatible with safestrap? And are there any other Touchwiz roms? I don't like Touchwiz and am trying to get as far from it as I can but if I could just delete the bloatware (which I can still only disable after towel root), get SD access and get rid of the battery restrictions.
Click to expand...
Click to collapse
The reason that LS did a full boot is because certain aosp roms can function with a touchwiz kernel. However, the result is always buggy. There is s4 verizon general thread talking about this.
There are many other tw roms. Just go to andriod devlopment! On the top of my head, I can think of eclipse, hyperdrive, echoe, and empty galaxy.
Hi Note 3 gang. I just got those phone yesterday as a replacement for my dead Note 2, and I love it so far! Quick question though, which version of TWRP recovery is the right one? I've downloaded a few, and tried to install with the Official TWRP App but they all come back saying failed. I rooted last night with Odin and Chainfire autoroot, but forgot to do a recovery at the same time. I can go back and use that to install TWRP if it works better, but I'm still not certain which version to use. The phone is still running stock 5.0, but I'd like to check out some other roms.
Any help is appreciated! Thanks
Edit:
Also, if anybody knows of a flashable to get my notification toggles back I'd like to get my hands on it. I read a post saying how to enable the torch toggle with terminal commands, but when i pasted them, everything disappeared except Wifi calling lmao!
https://dl.twrp.me/hlte/
I suggest you install version 2.8.7.0 since anything higher will prevent custom roms to install that have an aroma installer. I'm not sure if it was ever fixed, going to be fixed, or what.
Thanks for the tip.. Is it possible to downgrade? I took a leap and installed 3.0.0-0, it works but if it's not compatible with customs I want to go back lol..
The:Dude said:
Thanks for the tip.. Is it possible to downgrade? I took a leap and installed 3.0.0-0, it works but if it's not compatible with customs I want to go back lol..
Click to expand...
Click to collapse
Yea you can go back and forth. Stay on it until you encounter a rom you can't install.