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…
Related
I have CM installed on my Nexus 4, but it lags a lot and has a bunch of issues, so I want to go back to stock, but I forgot to make a stock recovery with CWM.
Can I just flash the stock ROM using CWM? If so can someone link me to the .zip file?
nmunro said:
I have CM installed on my Nexus 4, but it lags a lot and has a bunch of issues, so I want to go back to stock, but I forgot to make a stock recovery with CWM.
Can I just flash the stock ROM using CWM? If so can someone link me to the .zip file?
Click to expand...
Click to collapse
You forgot to mention which stock rom you need.
To make things simpler, I'll give you a couple of links to flash deodexed stock roms via recovery.
If you need the 4.2.1 stock rom, you can get it here:
http://forum.xda-developers.com/showthread.php?t=2019243
If you need 4.2.2 stock rom, you can get it here:
http://forum.xda-developers.com/showthread.php?t=2147281
All you need to do is download whichever version you need and copy it onto the phone's storage, boot to recovery mode and flash the .zip.
You don't need to wipe but to avoid unforeseen issues, you can just wipe system, cache and dalvik cache.
I advise you to try different custom roms and not stock..
scream4cheese said:
You forgot to mention which stock rom you need.
To make things simpler, I'll give you a couple of links to flash deodexed stock roms via recovery.
If you need the 4.2.1 stock rom, you can get it here:
http://forum.xda-developers.com/showthread.php?t=2019243
If you need 4.2.2 stock rom, you can get it here:
http://forum.xda-developers.com/showthread.php?t=2147281
All you need to do is download whichever version you need and copy it onto the phone's storage, boot to recovery mode and flash the .zip.
You don't need to wipe but to avoid unforeseen issues, you can just wipe system, cache and dalvik cache.
Click to expand...
Click to collapse
If I flash 4.2.1 will I be able to update using system update to 4.2.2? And it will still be rooted?
I am using the Cyaniogen-Nightly of 21. Feb.
I am happy with this ROM, but my battery drains 5% per hour. Is this normal?
Bluetooth is always visible, Exchange is syncing every 10min and data is on. But there is "no action" or wakeup during the day.
Would this be better with the original ROM?
So I restored to stock and I'm still having issues.
The problem in both stock and CM is that when on the lock screen, if you swipe left to right twice, the second swipe causes a short lag. Also occasionally the lock screen will just freeze.
Any help?
nmunro said:
So I restored to stock and I'm still having issues.
The problem in both stock and CM is that when on the lock screen, if you swipe left to right twice, the second swipe causes a short lag. Also occasionally the lock screen will just freeze.
Any help?
Click to expand...
Click to collapse
A little late...Did you figure it out nmunro? I too am trying to find the best, easiest method to go back to stock, but keep root.
Best and easiest can be subjective. IMHO, if your looking to go back to stock due to some HW issues you can't figure out, try pulling some logcats first and review. Or....
Flash the stock image from developers dot Google dot com. I think I've even seen a forum with instructions on how to do it (flashing everything from fastboot).
Sent from my Nexus 4 using Tapatalk 2
Hi All,
I am using PA Rom, but for some reason, the colors are not exact the same. But I'd like to know now if the Stock ROM also showing these wrong colors. Now I'd like to flash back to Stock, particularly Stock kernel.. How can i do that?
senthilrameshjv said:
Hi All,
I am using PA Rom, but for some reason, the colors are not exact the same. But I'd like to know now if the Stock ROM also showing these wrong colors. Now I'd like to flash back to Stock, particularly Stock kernel.. How can i do that?
Click to expand...
Click to collapse
Here is a tutorial http://forum.xda-developers.com/showthread.php?t=2010312.
Hi,
I flashed the Google 4.3 S4 Rom and used TWRP 2.5.0.2 and Goo with instructions I found on the boards.
- I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
So now the problems:
1) I originally installed it and it was constantly stuck on 'Samsung Galaxy S4' Screen, couldn't proceed barely got into recovery and reflashed; this worked and it booted google and i realized why this happened is because i accidentally erased my data.
2) The second time, I simply turned off my phone and turned it back on, again i was stuck on 'Samsung Galaxy S4' Screen, no way of doing anyhing except turnging off the phone and trying again and again to get to recovery, I then flashed to 4.3 again off the external.
3) I simply tried to open facebook and the phone booted and went on to the 'Samsung Galaxy S4' Screen and is stuck again! Even when I reboot through Team Win Recovery v2.5.0.2 to System I get the same boot loop.
I am super frustrated with this, what can I do and at this point I'm getting to the point where I would like some help to go back to stock. I would also like some input as to why this is happening if anyone has any suggestions or help it would be greatly appreciated.
Thank You.
notorious99 said:
Hi,
I flashed the Google 4.3 S4 Rom and used TWRP 2.5.0.2 and Goo with instructions I found on the boards.
- I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
So now the problems:
1) I originally installed it and it was constantly stuck on 'Samsung Galaxy S4' Screen, couldn't proceed barely got into recovery and reflashed; this worked and it booted google and i realized why this happened is because i accidentally erased my data.
2) The second time, I simply turned off my phone and turned it back on, again i was stuck on 'Samsung Galaxy S4' Screen, no way of doing anyhing except turnging off the phone and trying again and again to get to recovery, I then flashed to 4.3 again off the external.
3) I simply tried to open facebook and the phone booted and went on to the 'Samsung Galaxy S4' Screen and is stuck again! Even when I reboot through Team Win Recovery v2.5.0.2 to System I get the same boot loop.
I am super frustrated with this, what can I do and at this point I'm getting to the point where I would like some help to go back to stock. I would also like some input as to why this is happening if anyone has any suggestions or help it would be greatly appreciated.
Thank You.
Click to expand...
Click to collapse
Have you try using Odin to go back to stock?
shizs14 said:
Have you try using Odin to go back to stock?
Click to expand...
Click to collapse
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
notorious99 said:
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
Click to expand...
Click to collapse
Rule #1. Learn Odin before attempting anything on Samsung phones
notorious99 said:
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
Click to expand...
Click to collapse
You need to read these threads and make sure to read the threads linked in these threads that have to do with your phone...
http://forum.xda-developers.com/showthread.php?t=2301762
and
http://forum.xda-developers.com/showthread.php?t=2312444
You can use the forum's search function to help you find specific information. Good luck.
agreed, odin should be the first thing any noob should learn.
Scott, you da man...
scott14719 said:
You need to read these threads and make sure to read the threads linked in these threads that have to do with your phone...
http://forum.xda-developers.com/showthread.php?t=2301762
and
http://forum.xda-developers.com/showthread.php?t=2312444
You can use the forum's search function to help you find specific information. Good luck.
Click to expand...
Click to collapse
So I flashed a different rom (4.2.2 google) and I tested turning my phone off and then on again, and SAME issue, it boot loops at the S4 screen, what is the deal with that specifically? does anyone have any ideas?
notorious99 said:
So I flashed a different rom (4.2.2 google) and I tested turning my phone off and then on again, and SAME issue, it boot loops at the S4 screen, what is the deal with that specifically? does anyone have any ideas?
Click to expand...
Click to collapse
Which google rom 4.2.2? there are a few, meaning where did you get the rom?
Which kernel did you use?
you say you have this...both roms require a certain kernel. Depending on whose rom you flashed.
I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
TheAxman said:
Which google rom 4.2.2? there are a few, meaning where did you get the rom?
Which kernel did you use?
you say you have this...both roms require a certain kernel. Depending on whose rom you flashed.
I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
Click to expand...
Click to collapse
THE ROM
Google Edition 4.2.2 - v1.3 - http://d-h.st/Lm8
posted here: http://forum.xda-developers.com/showthread.php?t=2341376
MY KERNEL as it is on my phone currently is:
Baseband: 1337MVLUAMDJ
Kernel: 3.4.0-Google-Edition, [email protected]#1,
Build Number: JDQ39.1337
AND I'm using TWRP Custom
-----------------------------------------
notorious99 said:
THE ROM
Google Edition 4.2.2 - v1.3 - http://d-h.st/Lm8
posted here: http://forum.xda-developers.com/showthread.php?t=2341376
MY KERNEL as it is on my phone currently is:
Baseband: 1337MVLUAMDJ
Kernel: 3.4.0-Google-Edition, [email protected]#1,
Build Number: JDQ39.1337
AND I'm using TWRP Custom
-----------------------------------------
Click to expand...
Click to collapse
Ok, now we're cooking, thanks for the info...
I haven't tried that rom yet, I am going to d/l it and give it a shot. Be back shortly.
ODIN back to stock, and start over from there, and take care to flash/erase properly. backup user apps/data if you can (there are non-root options) and restore when you finish flashing 4.3 and are sure its stable.
Ok..back...I flashed this rom I booted with the kernel supplied in rom. Hmm..it is kernel related for sure. Have you posted the issue in that roms thread? May want to give that a shot.
I'm on canadian S4 aswell and I also flashed the 1.3 Google edition but flashed faux kernel. Works like a charm.
Sent from my SGH-I337 using Tapatalk 4 Beta
Thank you to all you guys. I successfully used odin to get back to stock. I still have no idea why I had so many problems but will try the Google Rom again when I feel more comfortable.
Thanks again!
notorious99 said:
Thank you to all you guys. I successfully used odin to get back to stock. I still have no idea why I had so many problems but will try the Google Rom again when I feel more comfortable.
Thanks again!
Click to expand...
Click to collapse
Proper wiping steps is key when changing ROM bases. Do a factory reset, wipe both caches, format /system, and if coming from TW, format the internal also.
Here is a post by TeamWin on wiping for Roms. Formatting Data is not part of "normal" wipe process. It wipes your internal sd.
http://teamw.in/whattowipe
These guys are far above me. But my preferred method is to "Wipe" System/Data/Both Caches. I actually do it twice. I know many say no need, but I do. I did this for many years on previous phones and never had issues. If on Nightlies or incremental updates did not wipe unless OP said to.
rugmankc said:
Here is a post by TeamWin on wiping fro Roms. Formatting Data is not part of "normal" wipe process. It wipes your internal sd.
http://teamw.in/whattowipe
These guys are far above me. But my preferred method is to "Wipe" System/Data/Both Caches. I actually do it twice. I know many say no need, but I do. I did this for many years on previous phones and never had issues. If on Nightlies or incremental updates did not wipe unless OP said to.
Click to expand...
Click to collapse
The internal wiping isn't necessary, but it does get rid of TW folders that you don't need if switching to AOSP.
I think you could delete them individually as opposed to formatting entire internal with other rom backups/kernels/gapps etc. I also have music/pics on internal too. Also, I like some will go back and forth btwn aosp and tw. So, I would want to keep them. I never did that, but read about some having issues after Formatting Data
All IMHO--
rugmankc said:
I think you could delete them individually as opposed to formatting entire internal with other rom backups/kernels/gapps etc. I also have music/pics on internal too. Also, I like some will go back and forth btwn aosp and tw. So, I would want to keep them. I never did that, but read about some having issues after Formatting Data
All IMHO--
Click to expand...
Click to collapse
You're right, it's an overkill. Just my OCD nature kicks in sometimes.
+1
I understand OCD hence my wiping twice--hey sometimes 3x
Monk has nothing on me, If you are familiar with that tv show--
I am OCD thru and thru--
I have a rooted Galaxy Note 3 (Verizon). I'm running Safestrap and made a backup of the stock ROM about two weeks ago.
...I had not tried any other ROMs, now I wish I had. Something went wrong with my stock ROM, long story short - it's just not workin' right and I want to restore it from the backup I've made.
I want to restore it to the stock ROM slot (not a new ROM slot).
The backup is on a Micro SD card, Safestrap sees the backup file. The 'Restore' button is not red (while I've got the stock ROM activated).
I haven't done anything yet. I'm hoping I can just hit restore and it'll restore the stock ROM slot to the backup I made a couple weeks ago.
...is it that simple? Is there anything I should or should not do?
Twisked said:
I have a rooted Galaxy Note 3 (Verizon). I'm running Safestrap and made a backup of the stock ROM about two weeks ago.
...I had not tried any other ROMs, now I wish I had. Something went wrong with my stock ROM, long story short - it's just not workin' right and I want to restore it from the backup I've made.
I want to restore it to the stock ROM slot (not a new ROM slot).
The backup is on a Micro SD card, Safestrap sees the backup file. The 'Restore' button is not red (while I've got the stock ROM activated).
I haven't done anything yet. I'm hoping I can just hit restore and it'll restore the stock ROM slot to the backup I made a couple weeks ago.
...is it that simple? Is there anything I should or should not do?
Click to expand...
Click to collapse
It is that simple, just hit restore, select the file, then swipe the restore button.
airmaxx23 said:
It is that simple, just hit restore, select the file, then swipe the restore button.
Click to expand...
Click to collapse
Just one more question, if for any reason the restore fails... will Safestrap be unaffected?
What I mean by that is, I have another ROM (Hyperdrive) up and running that I can choose with Safestrap. If for some reason the restoration of the Stock ROM (in the stock ROM slot) fails, Safestrap will keep on working and I can choose Hyperdrive.
...and then if I reboot, I can still choose to boot up into Recovery mode with Safestrap. Is that correct?
Twisked said:
Just one more question, if for any reason the restore fails... will Safestrap be unaffected?
What I mean by that is, I have another ROM (Hyperdrive) up and running that I can choose with Safestrap. If for some reason the restoration of the Stock ROM (in the stock ROM slot) fails, Safestrap will keep on working and I can choose Hyperdrive.
...and then if I reboot, I can still choose to boot up into Recovery mode with Safestrap. Is that correct?
Click to expand...
Click to collapse
If the restore fails you'll get a message saying that it failed, you can then just restore a different backup.
airmaxx23 said:
If the restore fails you'll get a message saying that it failed, you can then just restore a different backup.
Click to expand...
Click to collapse
I've only got the one backup file that I'd made.
If it does fail, could I download a stock ROM from somewhere to put into the Stock ROM slot?
I'm not sure how Safestrap works, in my thinking if I screw up (wipe out) the Stock ROM slot then I've deleted Safestrap too. I think that's where my biggest worries are coming into play here. I'm hoping my understand of that is wrong.
...thanks by the way for your replies :good:
EDIT: I found a site that has a rooted stock ROM for the Verizon Galaxy Note 3. Downloading it now to be safe.
Twisked said:
I've only got the one backup file that I'd made.
If it does fail, could I download a stock ROM from somewhere to put into the Stock ROM slot?
I'm not sure how Safestrap works, in my thinking if I screw up (wipe out) the Stock ROM slot then I've deleted Safestrap too. I think that's where my biggest worries are coming into play here. I'm hoping my understand of that is wrong.
...thanks by the way for your replies :good:
Click to expand...
Click to collapse
If for some odd reason your backup fails you could place one of the available ROMs on your sdcard and install it from there. In a worst case scenario you always have Odin and the .tar files to restore your phone.
airmaxx23 said:
If for some odd reason your backup fails you could place one of the available ROMs on your sdcard and install it from there. In a worst case scenario you always have Odin and the .tar files to restore your phone.
Click to expand...
Click to collapse
Hopefully last question (sorry, want to make sure I have my head wrapped around this)
You said if the restore fails I'll simply get a failed message. ...if that happens, could I choose to boot with the Hyperdrive ROM and restart the phone with no problems?
I guess what I'm trying to ask is, isn't Safestrap running from that Stock ROM slot? Or does it run independently of whatever ROMs are in the slots.
Twisked said:
Hopefully last question (sorry, want to make sure I have my head wrapped around this)
You said if the restore fails I'll simply get a failed message. ...if that happens, could I choose to boot with the Hyperdrive ROM and restart the phone with no problems?
I guess what I'm trying to ask is, isn't Safestrap running from that Stock ROM slot? Or does it run independently of whatever ROMs are in the slots.
Click to expand...
Click to collapse
If the restore fails it will not effect SafeStrap, you will just be able to boot up HyperDrive afterwards. The chances of it failing are extremely slim.
airmaxx23 said:
If the restore fails it will not effect SafeStrap, you will just be able to boot up HyperDrive afterwards. The chances of it failing are extremely slim.
Click to expand...
Click to collapse
Thank you so much for all your help! I'm probably going to wait 'til tomorrow evening to do this (need my phone runnin' smoothly from now 'til then for work).
...not sure which reply of yours to click 'THANKS' on. I guess the first one, but they were all helpful. :good:
Twisked said:
Thank you so much for all your help! I'm probably going to wait 'til tomorrow evening to do this (need my phone runnin' smoothly from now 'til then for work).
...not sure which reply of yours to click 'THANKS' on. I guess the first one, but they were all helpful. :good:
Click to expand...
Click to collapse
One more thing, more of a "heads up". During the restore if your screen turns off and pressing Power or Home doesn't turn it on just leave it and when the restore is done it will turn on or just reboot on it's own. Restores can take 5 minutes or more depending on how big of a backup file you have.
airmaxx23 said:
One more thing, more of a "heads up". During the restore if your screen turns off and pressing Power or Home doesn't turn it on just leave it and when the restore is done it will turn on or just reboot on it's own. Restores can take 5 minutes or more depending on how big of a backup file you have.
Click to expand...
Click to collapse
Thought you might like to know, my meeting for tomorrow was cancelled so I went ahead and tried the restoration. ...worked FLAWLESSLY!! Whew!! :laugh:
So my phone is back, everything is running PERFECTLY.
Which brings me to a new question (hopefully you might know). I'm on 4.3 and do not want to get the OTA update for 4.4 from Verizon. It will download automatically (640 MBs or so), and a notification will appear that can't be swiped away.
Is there something in Titanium Backup that I can freeze to prevent the OTA update? To stop that non-swipable notification from appearing?
Twisked said:
Thought you might like to know, my meeting for tomorrow was cancelled so I went ahead and tried the restoration. ...worked FLAWLESSLY!! Whew!! :laugh:
So my phone is back, everything is running PERFECTLY.
Which brings me to a new question (hopefully you might know). I'm on 4.3 and do not want to get the OTA update for 4.4 from Verizon. It will download automatically (640 MBs or so), and a notification will appear that can't be swiped away.
Is there something in Titanium Backup that I can freeze to prevent the OTA update? To stop that non-swipable notification from appearing?
Click to expand...
Click to collapse
Yes, you can follow THIS guide to remove the notification and prevent further OTA updates from showing up.
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?
Hi. My note 3 has Aryamod 8.1 flashed on it but i think there is a app causing this but i can't figure which one is causing it!
My phone runs normally but suddenly it totally blacks out and i need to do a battery pull out just to get it back on!
Here is the logcat after the issue happened and rebooted:
https://mega.nz/#!6VIwmTwC!1gz0eVIAZaPTqhNCgHFYFCLCBWz8ZrwduB5uN_Tj04s
been using the same ROM for more than an year!
joluke said:
Hi. My note 3 has Aryamod 8.1 flashed on it but i think there is a app causing this but i can't figure which one is causing it!
My phone runs normally but suddenly it totally blacks out and i need to do a battery pull out just to get it back on!
Here is the logcat after the issue happened and rebooted:
https://mega.nz/#!6VIwmTwC!1gz0eVIAZaPTqhNCgHFYFCLCBWz8ZrwduB5uN_Tj04s
Click to expand...
Click to collapse
I've been using AryaMod form v5.3. Did you flash the BL and CP before installation? Also did you flash stock before installing Arya if youre coming from other ROM?
nijom said:
I've been using AryaMod form v5.3. Did you flash the BL and CP before installation? Also did you flash stock before installing Arya if youre coming from other ROM?
Click to expand...
Click to collapse
Yes, did flash BL and CP but didn't flash the totally stock rom before installing Arya since i didn't had these issues in the past (before Audax 34)
The logs don't show anything?
Maybe tomorrow i'll download the stock rom, flash it, flash twrp on it and do a full wipe and test but i did a full wipe a week ago, and previously was in another rom where the same exact issue happened:
Audax 34!
Any ideas? I seriously doubt flashing the stock rom will solve it since i did a full wipe and i do never restore data from a previous rom... always configure everything from scratch
PS: Every single update to a rom, i always do a full wipe
joluke said:
Yes, did flash BL and CP but didn't flash the totally stock rom before installing Arya since i didn't had these issues in the past (before Audax 34)
The logs don't show anything?
Maybe tomorrow i'll download the stock rom, flash it, flash twrp on it and do a full wipe and test but i did a full wipe a week ago, and previously was in another rom where the same exact issue happened:
Audax 34!
Any ideas? I seriously doubt flashing the stock rom will solve it since i did a full wipe and i do never restore data from a previous rom... always configure everything from scratch
PS: Every single update to a rom, i always do a full wipe
Click to expand...
Click to collapse
I don't know to read log files
I used to follow whats in OP and have been successful in all installs. I came to Arya from CM11S, I flashed a stock 5.0 in between, just to install Arya over it
nijom said:
I don't know to read log files
I used to follow whats in OP and have been successful in all installs. I came to Arya from CM11S, I flashed a stock 5.0 in between, just to install Arya over it
Click to expand...
Click to collapse
I will try to flash the stock rom, though i suspect flashing persist, BL and CP it way more then enough to get the rom working properly!
If i continue to have this issue i will full wipe and install my apps, one by one and get some tests going so see if i find the culprit!
Anyway i'll be waiting for more help around here