The phone has been working great on Android 4.1.2 as I describe in the thread ( Optimizing [Rom][I605VRAMC3][4.1.2])
Found Here: http://forum.xda-developers.com/note-2-verizon/help/rom-optimizing-t2817294
EXCEPT NOW, every time I boot the phone, I get a message that says All the APPS are upgrading automatically . I think the problem is related to me Using Titanium Backup to Freeze SDM 1.0 . The reason I froze SDM 1.0 was to stop the Nag from Verizon for a firmware update .
Anyone know what I need to freeze to stop the auto upgrading on every boot? It really slows down the boot time.
Thanks in advance
You probably did this already, but double check to make sure Play Store is not set to Auto Update apps. Can. be found in Play Store. settings. I don't believe that freezing SDM would play a role here, but I've been wrong before.
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
You probably did this already, but double check to make sure Play Store is not set to Auto Update apps. Can. be found in Play Store. settings. I don't believe that freezing SDM would play a role here, but I've been wrong before.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks , Play Store was set to auto update so I changed it , I just tried your suggestion and I rebooted . I'm still getting the same message while booting: Android is updating.............................................................................
doctor-cool said:
Thanks , Play Store was set to auto update so I changed it , I just tried your suggestion and I rebooted . I'm still getting the same message while booting: Android is updating.............................................................................
Click to expand...
Click to collapse
Hmmmm.... It's probably still working on updating apps that it started working on previous to disabling the auto update.
This might work..... Toggle off your wifi and data, then try going to phone Settings, Application manager, All Apps... then force close the Play Store and wipe the app data. Then open the Play Store again and it should go straight to settings area. Set it to " Do not Auto Update apps " and then back out of Play Store, turn wifi/data back on, and go back into Play Store and sign into the app again/change any other settings back to how you like them . I hope that will stop the auto update.
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
Hmmmm.... It's probably still working on updating apps that it started working on previous to disabling the auto update.
This might work..... Toggle off your wifi and data, then try going to phone Settings, Application manager, All Apps... then force close the Play Store and wipe the app data. Then open the Play Store again and it should go straight to settings area. Set it to " Do not Auto Update apps " and then back out of Play Store, turn wifi/data back on, and go back into Play Store and sign into the app again/change any other settings back to how you like them . I hope that will stop the auto update.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
doctor-cool said:
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
Click to expand...
Click to collapse
For a test,
I cleared data and disabled the Play Store, Turned off data and wifi . REBOOTED I'm still getting the same message while booting: Android is updating.......................................... ...................................
Now I'm thinking the problem is due to me flashing Gapps.
I flashed (HDPI / MDPI / TINY: gapps-jb-20121011-signed.zip) for Android 4.1.1 – 4.1.2 – Jelly Bean, from http://www.teamandroid.COM/gapps/
I probably shouldn't have flashed it on top of the official stock 4.1.2 Verizon ROM. I probably have two version of Gapps on my phone competing with each other. The quickest thing would probable be to re-flash to the OEM [Rom][I605VRAMC3][4.1.2]
doctor-cool said:
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
Click to expand...
Click to collapse
Ok.... I just realized that this has nothing to do with the Play Store App or updating your apps.... Your actual phone system is optimizing at boot screen.... like this pic, right?
Sent from my SCH-I605 using XDA Premium 4 mobile app
I'm not in any way a developer or expert.... this stuff is just a hobby for me...so please understand these are just my thoughts to hopefully help and not make things worse for you. With that said, I suspect you have an app or script (or something) that is doing something like wiping the Dalvik cache with each reboot, which is triggering your phone to run through the optimization process each time you boot. I am pretty confident this has nothing to do with SDM being frozen. I'm not sure about gapps with stock. Why do you need that if your running stock?
Sent from my SCH-I605 using XDA Premium 4 mobile app
Anyhow, What ROM do you recommend ? I'm using my phone to do Wave Accounting and Pay Pal transactions so I cant have down time.
doctor-cool said:
Anyhow, What ROM do you recommend ? I'm using my phone to do Wave Accounting and Pay Pal transactions so I cant have down time.
Click to expand...
Click to collapse
Sorry for being off base with my initial thought on your above post... It's been a long week at work and I'm tired.... so that's my excuse...
I hope you get it sorted out with what's causing your phone to upgrade/optimize apps at each reboot. I did a Google search just now and apparently, this is common issue asked on XDA. I found several comments from people saying they think something causes the Dalvik/Cache to get wiped on reboot. I also read where someone reported that flashing Gapps did the same thing to them. If you're going to flash a new ROM, that should take care of the problem when you wipe things for the new flash.
On the XDA forums, it's generally frowned upon to ask for ROM recommendations. But for me personally, I have decided to settle (for now) on Beanstown106's JellyBeans ROM Build 22 which is based off of 4.1.2. I think this was the last 4.1.2 based Rom (for our SCH-I605's) that he did for his JellyBeans ROM before he moved on to developing for 4.3 MJ9, so I think a lot of the bugs were worked out of it.
I love the ROM and I've tried out several others. I always end up coming back to it because it's really stable and (pretty much) everything works. And with Xposed Modules and his built in options, I can tweak everything to how I like it.
You can still grab his older JellyBeans ROM build 22 by going to the current Alliance Rom Thread here: ( http://forum.xda-developers.com/showthread.php?t=2032447 ), and then going to the "Downloads" area right above the thread title. The ROM Filename is: note2_JellyBeans_B22.zip.
There's tons of great ROM's for our phone and there's so many talented developers..... so I truly think you have to read through the threads on each of the ROM's to make a decision for your personal needs... but I know that JellyBeans Build 22 is very stable if that's what you're wanting. If you decide to try out JellyBeans Build 22, let me know if you need help with instructions for flashing it. I saved the install instructions for future reference when I flashed it the first time last year, but I don't see those old install instructions any place now that he's moved on to developing for the updated 4.3 build.
mattnmag said:
Sorry for being off base with my initial thought on your above post... It's been a long week at work and I'm tired.... so that's my excuse...
I hope you get it sorted out with what's causing your phone to upgrade/optimize apps at each reboot. I did a Google search just now and apparently, this is common issue asked on XDA. I found several comments from people saying they think something causes the Dalvik/Cache to get wiped on reboot. I also read where someone reported that flashing Gapps did the same thing to them. If you're going to flash a new ROM, that should take care of the problem when you wipe things for the new flash.
On the XDA forums, it's generally frowned upon to ask for ROM recommendations. But for me personally, I have decided to settle (for now) on Beanstown106's JellyBeans ROM Build 22 which is based off of 4.1.2. I think this was the last 4.1.2 based Rom (for our SCH-I605's) that he did for his JellyBeans ROM before he moved on to developing for 4.3 MJ9, so I think a lot of the bugs were worked out of it.
I love the ROM and I've tried out several others. I always end up coming back to it because it's really stable and (pretty much) everything works. And with Xposed Modules and his built in options, I can tweak everything to how I like it.
You can still grab his older JellyBeans ROM build 22 by going to the current Alliance Rom Thread here: ( http://forum.xda-developers.com/showthread.php?t=2032447 ), and then going to the "Downloads" area right above the thread title. The ROM Filename is: note2_JellyBeans_B22.zip.
There's tons of great ROM's for our phone and there's so many talented developers..... so I truly think you have to read through the threads on each of the ROM's to make a decision for your personal needs... but I know that JellyBeans Build 22 is very stable if that's what your wanting. If you decide to try out JellyBeans Build 22, let me know if you need instructions for flashing it. I saved the install instructions for future reference when I flashed the first time last year, but I don't see those old install instructions any place now that he's moved on to developing for the updated 4.3 build.
Click to expand...
Click to collapse
Thanks and right on time, After I did my return to stock I thought I needed to wipe both caches' and the system to be able to do a Titanium backup.
I lost my operating system and Odin didn't recognize my phone, I was looking for a 4.1.2 zip file at the time I found your post. THANKS!
I'm downloading now
doctor-cool said:
Thanks and right on time, After I did my return to stock I thought I needed to wipe both caches' and the system to be able to do a Titanium backup.
I lost my operating system and Odin didn't recognize my phone, I was looking for a 4.1.2 zip file at the time I found your post. THANKS!
I'm downloading now
Click to expand...
Click to collapse
When you say you returned to stock, I'm hoping you didn't ODIN flash a full stock version of 4.1.2, because that would have relocked your bootloader and removed the custom recovery and root. If you were able to use Advance wiping features, you must still have some sort of custom recovery on your phone.
Hopefully, you do so you can flash a zipped ROM back onto it. If you've still got an unlocked bootloader and have a custom recovery, you may want to try to flash this root/modified version of "stock" 4.1.2:
( http://forum.xda-developers.com/showthread.php?t=2261478 ). It was also made by Beanstown106 and the thread still has instructions.
Also, you may do some Google searching to find tips on how to get your computer/ODIN to recognize your phone in download mode again... the most common tips I've seen are to try to uninstall and reinstall the Samsung drivers on your computer...and to try different USB cables and different USB ports on the computer.
I'm exhausted and I'm going to bed, but here are the original install instructions posted by Beanstown106 for JellyBeans ROM Build 22 if needed.
------------------------
"(INSTRUCTIONS) YOU MUST BE UNLOCKED
Step 1-
Make sure u are unlocked
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom (flash it in your custom recovery)
Step 4-
Reboot and Enjoy!"
-------------------------------------
Hope that helps. (Also, if Beanstown's stuff helps you... I'd encourage you hitting the thanks button for all his hard work )
mattnmag said:
When you say you returned to stock, I'm hoping you didn't ODIN flash a full stock version of 4.1.2, because that would have relocked your bootloader and removed the custom recovery and root. If you were able to use Advance wiping features, you must still have some sort of custom recovery on your phone.
Hopefully, you do so you can flash a zipped ROM back onto it. If you've still got an unlocked bootloader and have a custom recovery, you may want to try to flash this root/modified version of "stock" 4.1.2:
( http://forum.xda-developers.com/showthread.php?t=2261478 ). It was also made by Beanstown106 and the thread still has instructions.
Also, you may do some Google searching to find tips on how to get your computer/ODIN to recognize your phone in download mode again... the most common tips I've seen are to try to uninstall and reinstall the Samsung drivers on your computer...and to try different USB cables and different USB ports on the computer.
I'm exhausted and I'm going to bed, but here are the original install instructions posted by Beanstown106 for JellyBeans ROM Build 22 if needed.
------------------------
"(INSTRUCTIONS) YOU MUST BE UNLOCKED
Step 1-
Make sure u are unlocked
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom (flash it in your custom recovery)
Step 4-
Reboot and Enjoy!"
-------------------------------------
Hope that helps. (Also, if Beanstown's stuff helps you... I'd encourage you hitting the thanks button for all his hard work )
Click to expand...
Click to collapse
Thanks I used JellyBeans ROM build 22 just to have a system so that I could get to Odin. Then I did flash the full stock version of 4.1.2 then I used the Casual method to unlocked the boot-loader and reinstall WIN recovery and root. As explained here http://forum.xda-developers.com/note-2-verizon/help/rom-optimizing-t2817294. ( I ran into some driver issues between Casual and Odin but they were resolved)
Actually I have three Samsung i605's.
I have one that has got all the Verizon OTA updates, never tampered with it's on 4,4,2.
I have the one we have been talking about I have restored it to the fully stock version of 4.1.2 with Root.
And the last one I am experimenting with DN3 (Ditto Note 3) for fun and knowledge.
doctor-cool,
That's great. Glad you got it fixed.
And that's pretty cool to have extra devices to work with. Must be nice.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Related
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
I've been struggling with this for about a week and I am not able to figure this one out. I hope someone here can give me a hand.
I've unlocked my phone using HTCDEV and rooted using TWRP 2.4.3 gaining root and recovery access. All seemed to work well but every GOOGLE app crashes now on start up. I can't go to the market as it crashes "Unfortunately Google play store has stopped". It does this with all Gapps.
I've flashed the GAPPS through recovery since I can't access Play.Google. and it made no difference. I can't log in to Google accounts as soon as try it gives me "google account manager has stopped".
I've tried to RUU back to rom 3.16. but RUU fails to update the phone although the restoral screen shows the scrolling dots indicating it is updating, but it goes on forever. the bootloader shows "TAMPERED" "Unlocked" and this came after using FASTBOOT OEM LOCK command in an attempt to reflash the unit. I have tried to flash to other roms like CM10 but it only gets to the point of the spinning logo and just sits there and spins, etc. Other roms get stuck as well in the first boot up logo of the rom or give a black screen. I can use TWRP to restore the backup each time so the phone works seemingly ok except for anything with Gapps.
I assumed I can't not flash JB roms without S-off and I tried to use Dirty Racun to obtain S-off but I get errors with each step so gave up on that for now. I've resolved myself to sticking with the stock rooted rom but I can't do much without Google Voice which is my text and phone account.
Can anyone shed some light on this for me? I've searched the forums here and elsewhere for dozens of hours and have not been able to find a solution for this or any help that might help me "stumble" into a solution. I don't mind flashing another rom if I could get one to take hold just so I can get this unit working.
I think the TWRP recovery or a old verion of Superuser might have caused this glitch. I did the rooting and recovery using this guide here htcevohacks.com/htc-evo-4g-lte-root/how-to-root-htc-evo-4g-lte-unlock-bootloadertwrp-recovery and the provided TWRP would not accept any input so I replaced it with 2.4.3.0 and recovery then recovery seemed to work and backup/restore but still can't flash any roms successfully. I didn't notice Superuser v0.87 here as being old (my goof) and didn't get a more recent version until after the flashing was done. LIke I said, where I'm left at now is everything seems to work but anything having to do with Gapps just crashes on start.
Any help please?
Couple things you could do if you wanted a new rom. First go to the q&a section there is a sticky titled don't panic it will let you know to fast boot the bootimg for being son or find a rom that has son kernel installer for sense mean bean does
Sent from my EVO using Tapatalk 2
I had this issue today when I flashed viper 4g ROM before doing my s off. I tried every approach and what I ended up doing is a factory reset, cache wipe, D. cache wipe, Android secure wipe, sd ext. wipe (I always do the wipe 3x in a row on each) then I reinstalled my viper rom (comes with the latest google apps) and off I go. Solved all my google sign in related issues. You could also try to locate a downloadable version of goomanager which will automatically check for the latest version of gapps that is compatible with your rom and download it. Doesn't need to have a google playstore link to work either.
Sent from my EVO using xda premium
thicklizard said:
Couple things you could do if you wanted a new rom. First go to the q&a section there is a sticky titled don't panic it will let you know to fast boot the bootimg for being son or find a rom that has son kernel installer for sense mean bean does
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thicklizard, Thanks, I'll check this out now. Are you saying the rom Mean Bean is a ROM and might take hold flashing it with my s-on situation? Is MeanBean an xda developers rom? I've always had good luck with just about everything from XDA, so would love to try it. My hope is a new rom would solve whatever "hell" my phone is stuck in. Thanks! I'll see if I can find it.
dominicsdad said:
I had this issue today when I flashed viper 4g ROM before doing my s off. I tried every approach and what I ended up doing is a factory reset, cache wipe, D. cache wipe, Android secure wipe, sd ext. wipe (I always do the wipe 3x in a row on each) then I reinstalled my viper rom (comes with the latest google apps) and off I go. Solved all my google sign in related issues. You could also try to locate a downloadable version of goomanager which will automatically check for the latest version of gapps that is compatible with your rom and download it. Doesn't need to have a google playstore link to work either.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
dominicsdad, I'm going to check out what was suggested about Mean Bean but I did try several JP type GB apps, etc. None of them would restore the function. THis has been so frustrating. I'm a guy that can folllow the posts and the guides I read, etc., but not having the core understanding or depth shows it's ugly face for a non-connected guy like me. WHy did you do an SD wipe? That's where I keep my backups which have been the only thing that has let me get back from a few botched rom attempts. I will try the goo manager if I can find a flashable version since I'm locked out otherwise with any kind of app install. I was surprised to see the EVO LTE didn't have a file manager as I was going to try and just install google voice which would at least allow me to use the phone.
THanks!
billaggie said:
Thicklizard, Thanks, I'll check this out now. Are you saying the rom Mean Bean is a ROM and might take hold flashing it with my s-on situation? Is MeanBean an xda developers rom? I've always had good luck with just about everything from XDA, so would love to try it. My hope is a new rom would solve whatever "hell" my phone is stuck in. Thanks! I'll see if I can find it.
Click to expand...
Click to collapse
Thicklizard,
Update, I installed Mean Bean and solved my problem. It gave me a scare thinking it would backfire with the 2 duplicate rom installs it requires but I had to put some faith in something working and it worked. Thank you for getting me on the right track!!!!!! Bill
Hello.
I know that you are all incredibly busy and I sincerely hope that this does not inconvenience anyone.
Yesterday, I was following this very helpful guide for my Samsung Fascinate, (http://forum.xda-developers.com/showthread.php?t=1238070), and I encountered a big problem.
On Section 4, Step 18 ("Once the rom finishes installing reboot."), I did not get the option to immediately reboot. With this Jelly Bean rom, Super Nexus (http://forum.xda-developers.com/showthread.php?t=2238075), I immediately found myself in Team Win Recovery 2.5.0.0.
After initially failing to install Super Nexus via this new Recovery software, I found out that I must have both the "Inject TWRP after Install" and the "Zip file signature verification" options disabled before it will succeed.
However, even after doing this, I noticed that the phone would not restart into the Super Nexus ROM properly. For some reason, it went right back to Team Win Recovery Project 2.5.0.0. Powering off the phone, removing the battery, and then putting it back in and starting the phone again allowed me to access the Rom properly. Afterward, I was able to install the GAPPS file which was provided by the Super Nexus thread (http://forum.xda-developers.com/showthread.php?t=2238075), but rebooting the phone via the power menu did not send me back into Clockwork Mod. Again, I was directed to TWRP and had to install it through there. Frankly, it seems this is all I can access now and Clockwork Mod is simply gone forever. This isn't really a problem I guess, but it is rather strange.
Besides this, my only real functional problem is that Google Search is unworkable. I get the infamous "Unfortunately Google Search has stopped" error message, but everything else seems to run fine. (It is certainly much faster than the Stock Gingerbread ROM.)
My question then is simply this: Why is this ROM so very different from all the others? The guide linked above (http://forum.xda-developers.com/showthread.php?t=1238070) seems to work for 99% of all users....
Why was I so different? Did I do something obviously wrong that anyone can think of? I tried to follow the steps slowly and accurately but I'm still left with a broken Google Search and tons of confusion.
Have you updated the Google Search app using the Play Store? Updating usually fixes any issue I have with it
Sent from my SCH-I500 using Tapatalk 4
SimplyShane said:
Hello.
I know that you are all incredibly busy and I sincerely hope that this does not inconvenience anyone.
Yesterday, I was following this very helpful guide for my Samsung Fascinate, (http://forum.xda-developers.com/showthread.php?t=1238070), and I encountered a big problem.
On Section 4, Step 18 ("Once the rom finishes installing reboot."), I did not get the option to immediately reboot. With this Jelly Bean rom, Super Nexus (http://forum.xda-developers.com/showthread.php?t=2238075), I immediately found myself in Team Win Recovery 2.5.0.0.
After initially failing to install Super Nexus via this new Recovery software, I found out that I must have both the "Inject TWRP after Install" and the "Zip file signature verification" options disabled before it will succeed.
However, even after doing this, I noticed that the phone would not restart into the Super Nexus ROM properly. For some reason, it went right back to Team Win Recovery Project 2.5.0.0. Powering off the phone, removing the battery, and then putting it back in and starting the phone again allowed me to access the Rom properly. Afterward, I was able to install the GAPPS file which was provided by the Super Nexus thread (http://forum.xda-developers.com/showthread.php?t=2238075), but rebooting the phone via the power menu did not send me back into Clockwork Mod. Again, I was directed to TWRP and had to install it through there. Frankly, it seems this is all I can access now and Clockwork Mod is simply gone forever. This isn't really a problem I guess, but it is rather strange.
Besides this, my only real functional problem is that Google Search is unworkable. I get the infamous "Unfortunately Google Search has stopped" error message, but everything else seems to run fine. (It is certainly much faster than the Stock Gingerbread ROM.)
My question then is simply this: Why is this ROM so very different from all the others? The guide linked above (http://forum.xda-developers.com/showthread.php?t=1238070) seems to work for 99% of all users....
Why was I so different? Did I do something obviously wrong that anyone can think of? I tried to follow the steps slowly and accurately but I'm still left with a broken Google Search and tons of confusion.
Click to expand...
Click to collapse
Twrp should be the recovery that is included with this ROM.
If you want a cwm recovery,, look at my thread in the general section.
Unjustdev said inject doesn't work.
For Google search:
I would try wiping dalvik cache and fixing permissions from recovery.
skepticmisfit said:
Have you updated the Google Search app using the Play Store? Updating usually fixes any issue I have with it
Sent from my SCH-I500 using Tapatalk 4
Click to expand...
Click to collapse
This did indeed fix the issue. :laugh:
Now, why it was there to begin with...I don't know. The Super Nexus thread makes no mention of this...
SimplyShane said:
This did indeed fix the issue. :laugh:
Now, why it was there to begin with...I don't know. The Super Nexus thread makes no mention of this...
Click to expand...
Click to collapse
I think Google just automatically updates for most people since they may have other devices running JB or they ran other ROMs. Starting with 4.1, Google automatically backs up every app you install, and when you set up a new device, it'll restore all the apps you had installed previously and it usually updates apps as well.
I take that back, you have to update all system apps manually. But I think most people know to do that.
Sent from my SCH-I500 using Tapatalk 4
skepticmisfit said:
I think Google just automatically updates for most people since they may have other devices running JB or they ran other ROMs. Starting with 4.1, Google automatically backs up every app you install, and when you set up a new device, it'll restore all the apps you had installed previously and it usually updates apps as well.
I take that back, you have to update all system apps manually. But I think most people know to do that.
Sent from my SCH-I500 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the info.
I don't know what happened. Or why it won't work.
When Safestrap was originally finished, I installed Hyperdrive without a problem. An update came, I downloaded and installed. It made it so I couldn't use HotSpot anymore. So, I figured it was the Rom, and I installed Jellybean Rom. I didn't like it. I tried to install the original Hyperdrive I had, and once its installed and reboots, the lights come on for one second and shut off. Downloaded the newest Hyperdrive, same issue.
The instructions say wait for 10 minutes. I did, and longer. (Range usually 20-40 minutes)
Last night I wanted to try again, (downloaded newest hyperdrive. I have sloooooow internet. Took 5 hours to finish). So, I tried installing today following the instructions, same issue. It installs and says everything is fine, reboot, safestrap pops up, loads normally through that, and the lights are on after like it starts with Stock, lights shut off, phone stops working.
When this happens, the phone does not respond to anything. Power does nothing. I waited 45 minutes the 3rd time trying to reboot after install. The phone will not turn on, respond, or anything unless I pop the battery out and put it back in. I can get back into Safestrap that way.
I really want to use Hyperdrive, but it just won't reboot for my phone.
I do have the Verizon i545 version, ME7, Safestrap, Rooted, and newest Hyperdrive Rom. Used the Safestrap Kernel, but the phone locks up.
I've tried default settings, different Rom settings, (2gb and 3gb), removing almost everything from install, adding what I want, adding what I like, etc. No combination of settings will let me phone boot into Hyperdrive.
Any thoughts?
Are you completely removing then re-creating the slot when trying all these flashes?
Are you flashing the ME7 kernel module.zip ?
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Have you tried to re-download the module? Preferably on the computer then transfer to your ExtSDCard with the ROM.
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
While you were trying to install did you notice if zip signature was checked if so uncheck when you install and uncheck when you install module other than that don't know what else to say. When i first started i found that to be my problem.
The zip signatures were not checked. : /
Sent from my SCH-I545 using xda app-developers app
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Excessumcarcer said:
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Click to expand...
Click to collapse
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
!Led*Eyes! said:
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
Click to expand...
Click to collapse
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
!Led*Eyes! said:
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
Click to expand...
Click to collapse
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Excessumcarcer said:
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Click to expand...
Click to collapse
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
!Led*Eyes! said:
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
Click to expand...
Click to collapse
Well...nothing has worked.
Update for everyone, I was using the older SS, 3.60.
I killed everything, put the original Verizon ME7 Rom on the phone, re-rooted, put 3.62 SS on, (Done like it), installed the HDrls10, Installed the module, (both successful), restarted, exact same thing. Right after Safestrap Enabled pops up, the phone goes dark and the battery needs to be removed and put back in for it to turn on again.
So, I tried something crazy and for whatever reason it worked as far as HD is concerned...but...I went outside of the instructions.
I have the HD rls9 Final. I installed it through SS, used the modded Kernel, (non SS), and restarted. It popped right up in about 45 seconds. (Wasnt working before I reset everything and started over)
I tried HD rls10 Final that way, and nothing.
I will be redownloading it tonight to make sure it isn't the download. (I have slow internet, itll take all night likely.) : /
If anyone is looking to actually uninstall SS (which you need to do to roll back a version) you need to use the commands hashcode has provided. Using Terminal Emulator on the stock side will accomplish that. Read up on hashcode's SS OP.
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Excessumcarcer said:
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Click to expand...
Click to collapse
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
lazer9 said:
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
Click to expand...
Click to collapse
I just double checked the MD5. It matches the download. How frustrating. Double checked the build, double checked the MD5, double checked install procedure, etc. It flat doesn't work on my phone, and there is no logical reason to it. I tried from a fresh build twice now, doing the rooting and SS install from stock everything.
It locks up right after SS, still.
Electronics hate me, it has been determined before. This is just further proof.
: /
So, I've done pretty much everything feasible. Guess Ill have to stick with an older HD or different rom. : (
Also, hotspot doesn't work HD 9 for me, (nor Jellybeans). I installed the module when I did the rom, but there is no hotspot for one. And two, when I download and use FoxFi, which I paid for to use on the Stock Rom before SS, it will try to turn it on and then it freezes and crashes.
All I want is a non-Verizon Rom with working Hotspot!!!! AHHHHH!!!! Looks like that aint happening.
Well played Verizon...well played. Perahps I should get an international phone and go to another company. Expensive, but tempting.
So, the final verdict for those following -
Hyperdrive 10 - Does not work on my i545 no matter what I tried.
Hyperdrive 9 - Works but the hotspot is glitched and froze no matter what I tried.
Jellybean - Works the same as HD 9
Synergy - Works. Everything on it works, hotspot, install, etc.
Not sure why the others did not work. But, for whatever reason Synergy works flawlessly for my i545. Installed and downloaded the same ways as the others, yet it worked.
: /
I was planning on trying a few others first, but Synergy claims to block Samsung from logging information from my phone. I realize this doesn't stop every company from doing it, but its the thought that counts. lol. So, Im trying this Rom out now. It's no hyperdrive, but it works.
After a BUNCH of tries I finally got it to work!!
I have a Verizon i545 with ME7. I basically started as if I'd never installed HD 9.1 in the first place.
Here's what I did.
1. Double check that your device is rooted. I used Root Checker Basic. I actually re-rooted my device just to be sure (I venture to guess it might have been unnecessary) and it worked.
2. I used a 4GB SD formatted to ex-fat and put the HD RLS10 AND the ME7 modules .zip file on it (Both on the SD)
3. I then booted into recovery.
4. Make a new ROM slot.
5. Name it whatever you like.
6. When you go to flash HD, hit the add zip button and select the ME7 modules.zip
7. When HD gets done flashing UNCHECK the "Reboot" box up top and then hit the reboot tab at the bottom right.
8. It will automatically flash the ME7 modules next. When it says 'Successful', then reboot.
9. Give it a few seconds and hopefully it will work for you as well. Good luck.
Latest installable version for Me7?
What is the latest installable version of HD for verizon locked Me7 bootloader, i currently have rls10.0 installed and ive tried 10.1, 10.2, and now 12 and none of them boot up.
help guys i know you can
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
help guys i know you can
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You will need to give a little more information to get some help.
Please include:
model of your phone
modem/baseband currently on your phone (settings, general,about phone)
firmware version (same location)
recovery installed (if you're currently rooted) or recovery attempting to use
root method being used
flashing steps taken
ROM or ROMs flashed
I know its a long list but it will go a long way towards getting the help you need.
Good luck
Note 3 sm900p lean kernel now I flashed Cm 11
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Note 3 sm900p lean kernel now I flashed Cm 11
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What exactly is your question? I don't actually see what you were trying to do and what went wrong.
One of the biggest problems that people have when trying to flash a 4.4.4-based ROM is that their bootloader is still based on NC5, not NH7. If you want to flash anything newer, you'll have to update your phone to NH7 before flashing a 4.4.4 ROM.
I put together this post when helping another person out on another thread. I think it'll work as a step-by-step guide for you:
I'll explain how to install a custom ROM and some common things to think about/check prior to installing anything:
Installing a Custom ROM
Step 1 - Gather Information
First off, you need to know what version of Android your phone currently is running. This is easily done by looking in the Settings Menu -> General -> About Device.
The Main things we are looking at on this screen are Software Version, Model Number, Android Version, and Baseband Version. I'll explain these (to the best of my knowledge) below:
Software Version:
This is the "type" of Android that you're running. Rather than quoting the entire name, we typically only refer to the last 3 characters (MJ4, NAB, NC5, etc.). Stock Note 3 devices will (most-likely) be running one of 3 different versions of TouchWiz (TW):
MJ4 - This is the last Jellybean version of TW for the Sprint Note 3NAB - This is the first KitKat TW version for the Sprint Note 3NC5 - This is the second KitKat TW version for the Sprint Note 3NH7 - This is the latest KitKat TW version for the Sprint Note 3
The reason that we are concerned with the Software Version is that between the MJ4 and NAB versions, there were major changes. So if you're running MJ4, you will have to do additional steps before flashing a custom ROM based on a newer version. And if you're on NAB or NC5, you will not be able to go back to MJ4, so beware what you're flashing.
For the most part, if you're on NH7, you can flash either a NH7 or NC5 custom ROM, but just read the ROM's FAQ to see if there are any issues with doing so.
Model Number:
Most people don't worry about this, but I always do when looking at a new ROM. The Sprint Note 3 is different from the Verizon Note 3, which is also different from the International Note 3. It's always best to double-check that the ROM you're trying to install is truly meant for your device. This simple check will prevent a LOT of potential issues you'll get when installing a ROM.
Android Version:
This is just an additional check to the Software Version. Always best to know.
Baseband Version:
The Baseband is, unless I'm mistaken, the "kernal" for the phone's cellular and 4G radios. Sometimes upgrading (or downgrading) the Baseband can help with signal strength and reception. Some users have noted that they got better reception on older Baseband versions. I haven't personally looked into it and the reports from other users seem somewhat anecdotal, but it's good to know which Baseband you're on.
The Baseband is independent from the ROM version, so you can run an older Baseband (MJ4 or NAB) on a newer ROM (NC5), and vice-versa.
The last bit of information you need to know is the Bootloader Version. The way to find this information is to reboot your device. When you see the text on the screen, you should look for the Bootloader Version. It'll be a long string of characters, but you're only looking for the last 3 (MJ4, NAB, or NC5).
Once you have all the above information, you should be ready to start the fun process of preparing your phone to flash your first ROM.
Step 2 - Backup your Media
First thing: Backup all of your media to your computer. If there's pictures/music/videos/recordings you don't want to lose, back them up. It's just good practice. Don't lose all your cat pictures because you flashed something and it somehow erased your internal storage. I tend to keep everything of importance on the External Storage, but there are times where even external storage can be wiped, so it's best to back up everything to a PC.
Step 3 - Upgrade your Phone to the latest Stock ROM (NH7)
This only is a MUST applies if you're running an older version and want to install a NH7 ROM. Most continually-developed ROMs are either NC5 or NH7 now, so the first things first: Update your phone to NH7.
Go over to micmar's thread and download the One-Click File. It will remove Root, but don't worry, because when you install a new ROM, it will automatically include root access.
Follow the instructions in his thread and your phone will now be fully upgraded.
At this point, your "About Device" should show the following:
Software Version: N900PVPUCNH7
Android Version: 4.4.4
Baseband Version: N900PVPUCNH7
Reboot your phone and let it sit for a minute so it can get it's bearings.
Step 4 - Install a Custom Recovery
So far, we've been flashing everything in ODIN. Now, we're going to use ODIN one last time to flash a custom recovery, so that you can flash custom ROMs without the need of a computer.
The most-commonly used Custom Recovery is TWRP (XDA Link). You'll want to use the latest version, 2.8.0.
Flash this in ODIN. You should use the "PDA" or the "AP" Slot.
Reboot your phone to make sure it works correctly.
Step 5 - Make a Nandroid Backup of your device
If you don't know what a Nandroid backup is, don't worry. It's basically just taking your phone as is and making a backup of it. In case you make a mistake or flash a bad download of a ROM, this allows you to restore your system. I always keep my backups on the External Storage (microSD Card), so in case I have to wipe my internal storage, it's not a big deal. You can also copy the files over to your PC, just to be more paranoind about your nandroid backups (rhyming is fun!).
You do this by restarting into Recovery (power down device, hold down home button and volume up while powering on phone).
Once in TWRP, go to "backup." Make sure the storage selected is "external storage." This screen will have various options of what to backup. I typically choose everything except external storage. Typically, backups range from 1-2 Gigs.
For me, backups typically take 5-10 minutes to do. In my opinion, this is totally worth it, since I can always restore a backup with no issues.
Step 6 - Install a Custom ROM
Once you choose your custom ROM from the Development Section, follow the instructions on the original post to install it. I'll give a general outline of what I do whenever installing a new ROM, but sometimes a custom ROM will have specific instructions, so you want to make sure to read the posts carefully.
Generic Instructions for Installing a ROM:
Download ROM and check the md5
Internet being spotty in my area, I always check the md5 to make sure that the file downloaded correctly. You can check the md5 using this windows program or using a file explorer on your phone like ES File Explorer. I always copy the ROM zip file to my external SDcard.
Reboot to Recovery
Wipe Data, System, Cache, and Dalvik Cache
This is called a "Clean Wipe," meaning it will wipe out your installed Apps and the data associated with them. Some people will claim that "Dirty Flashing" (i.e. not wiping the above) is OK, but I've seen too many apps Force Closing (FC-ing) when dirty flashing. Also, if you dirty-flash and encounter an issue with a ROM, the first piece of advice is to do a clean install. Might as well do that initially and hopefully not run into any issues.
Install the Custom ROM
Pretty straight-forward on how to do this... just click "Install" and then browse to the place your copied the ROM zip file.
Reboot your phone and run through the typical initial start-up information (google account, etc).
Once you get your phone set up the way you like (apps, accounts, wifi passwords, etc), I'd make another Nandroid backup, just so you have one where it's setup with everything you need. This will make any issues less painful, since you'd restore a backup that's already setup.
Step 7 - Further Considerations
If you ever want to try a new ROM, all you have to do is repeat step 6. Beware, though, people easily become flashaholics when they first figure this stuff out.
If you were paying attention to my "Generic Instructions" when installing a ROM, you'd notice that every time you do a Clean Install of a ROM, you lose all your apps... All of your Angry Birds 3-Star levels are gone!
Well, there are ways to get prevent losing that data... One is by "Dirty Flashing" (Not wiping the "system" or "data" partitions before flashing a ROM in TWRP). This is common practice among users here on XDA, but is typically frowned upon by ROM devs. I've noticed that a good number of issues on ROM threads stem from people Dirty Flashing. It typically causes more problems than it solves.
The other way of backup up and restoring app data (prior to wiping) is by using Titanium Backup. I could write up a long post on how to use Titanium Backup (TiBu), but the main things to remember are the following:
White line items are fine to be restored (both Data and Apps).
Restoring Yellow line items is typically OK (Data only).
Restoring system apps or data (red line items in TiBu) is typically a bad idea.
I've been using TiBu for the past 2-3 years and it's typically worked like a charm. Sometimes, when there's a major Android Update (like from JellyBean to KitKat), it can become broken, but the Developer is really responsive and gets it to work within a few weeks. If you upgrade to PRO, you can schedule automatic app backups (I backup all my user apps every night at 3am). You can also restore apps/data from Nandroid Backups (which is great if you do a Nandroid backup but had forgotten to update your TiBu backups).
In Summary
Whew, that was a lot to write... I'm a Structural Engineer, not a Software Engineer, so I don't know the technical side of things like bootloaders or basebands, but hopefully none of the information I provided was false.
Anyways, let me know if you have any problems with the install. I appreciate any feedback!
Click to expand...
Click to collapse
I hope this helps, but please, in the future, write out your question clearly and provide as much information as possible, that way we can help you quickly and efficiently.
Cheers!
-Topher
OK I noticed that thanks again I finally found a 4.4.4 Cm Rom working awesome very little glitch but can deal with I have no way to update without pc
Sent from my SM-N900P using XDA Premium 4 mobile app
Why does titanium backup not save from deletion says no external backup detected
Sent from my SM-N900P using XDA Premium 4 mobile app
No data sorry
Sent from my SM-N900P using XDA Premium 4 mobile app
Running pac man rom Cm no data
Sent from my SM-N900P using XDA Premium 4 mobile app
Thanks
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Running pac man rom Cm no data
Click to expand...
Click to collapse
Ok, you haven't fully answered the questions myself and @jdelano asked you. If you cannot answer these questions, we will be unable to help you.
Phone Model: Note 3 sm900p
Phone Modem/Baseband: Unanswered
Firmware version: Unanswered
Recovery installed: Unanswered
Root Method: Unanswered
Flashing Steps: Unanswered
ROM flashed: CM11, pac man rom (no build number/date given, please provide a link to the thread you flashed from)
Are you a Sprint Customer, or have you flashed your phone to another carrier?
What is the issue you're having: No data when on CM 4.4.4 ROMs.
I am in the process of downloading/installing the PacMan ROM in this thread. The file I will be flashing is the pac_hltespr__20141110-124721.zip and the Gapps modular package from this thread, filename: pa_gapps-modular-full-4.4.4-20141121-signed.zip.
EDIT: By following the steps in my previous post, I was able to install the PacMan ROM with Gapps and all worked well. I had data, root access, and was able to wifi tether... Please answer the questions I asked before, especially what version is your baseband, as I suspect that's the main issue that you have.
Nc5
Sent from my SM-N900P using XDA Premium 4 mobile app
Y'all packing works great little glitchy phone turns on an off but all good all Cm roms I end up with no data I have Phil's recovery beast kernal average gapps had to update su binary any time I flash cm and it changes my recovery sometimes I cannot format SD card or I will loose all files I have no PC even if I use drop box titanium doesn't work the way it use to can save apps from deleting with confirmation so what's a stable cm Rom or slim rom and gapps or do you have knew updated tw rom rooted I have update my boot loader so
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Nc5
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Phone Model: Note 3 sm900p
Phone Modem/Baseband: NC5
Firmware version: Unanswered
Recovery installed: Unanswered
Root Method: Unanswered
Flashing Steps: Unanswered
ROM flashed: CM11, pac man rom (no build number/date given, please provide a link to the thread you flashed from)
Are you a Sprint Customer, or have you flashed your phone to another carrier?
What is the issue you're having: No data when on CM 4.4.4 ROMs.
Click to expand...
Click to collapse
As I stated in my first reply to you, the issue is that your phone is still on the NC5 bootloader. In order for 4.4.4 ROMs to play nicely on your phone, you'll need to update it to NH7. This is also stated in my previous post. You need to follow those instructions to the letter (particularly Step 3) in order to update it. You must use a computer to flash the update file, as Mobile ODIN is not able to update the bootloader. You need to get access to a computer (work, library, friend who owes you $20, someone at Starbucks).
Until you follow those steps, I doubt any 4.4.4 ROM will work correctly on your device.
Exposed frame work not compatible with roms only tw anyone have zip for NH7 u date with root
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Exposed frame work not compatible with roms only tw anyone have zip for NH7 u date with root
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is the first you've mentioned XPosed Framework... What exactly are you trying to do with it?
I don't know where you've gotten your information from, but I know for a fact that XPosed is compatible with all 4.4.4 AOSP ROMs as well as all TW ROMs. XPosed is NOT compatible with 5.0+ Roms. I'm currently using it on my "daily-driver" ROM, which is based on 4.4.4 AOSP.
R1000 said:
Y'all packing works great little glitchy phone turns on an off but all good all Cm roms I end up with no data I have Phil's recovery beast kernal average gapps had to update su binary any time I flash cm and it changes my recovery sometimes I cannot format SD card or I will loose all files I have no PC even if I use drop box titanium doesn't work the way it use to can save apps from deleting with confirmation so what's a stable cm Rom or slim rom and gapps or do you have knew updated tw rom rooted I have update my boot loader so
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, lets get you to a known platform with your phone so you can use 4.4.4 TW or AOSP ROMs.
#1. Load latest stock firmware and software
[Stock ROM] Odin flashable N900PSPTDNH7Follow the instructions EXACTLY
Now make sure you boot stock NH7, let it get data and update your profile and PRL by doing:
go to Settings -> General -> System Update, then select Update PRL (wait for it to do its thing), then Update Profile (again wait for it.)
Now we know you're on the most current stock software available and we've updated your profile and PRL (preferred roaming list)
#2. Root stock NH7 acquired in step #1
Go here Download philz_touch_6.48.4-hlte.tar.md5 (save it in the same folder you have Odin in from Step #1)Go Download SuperSU-v2.37.zipCopy the zip to your phone's sd cardUse Odin to put philz_touch_6.48.4-hlte.tar.md5 on your phone (same basic steps you used to Odin NH7) - Make sure you UNCHECK rebootOnce odin is finished and you see PASSED on the screen, unplug your phone from your computer then press Volume UP + HOME + POWER and hold all 3 until the phone reboots and you see blue words "Recovery Booting ..." at the top of the screen - Philz recovery will startnow select install zip -> choose zip from /sdcard -> scroll all the way to the bottom and select the SuperSU-v2.37.zip file -> select Yesonce finished press back until you get to the main recovery menu and select Reboot to System
#3. Update SuperSU binaries
Once your rebooted, Open Apps drawer, open SuperSU, say no to disable knox, it will ask about updating binaries, select yes, select normal, wait until it says its finished.Now you are Rooted Stock NH7You can now flash any 4.4.4 TW-NH7 or AOSP hltespr ROM - make sure to follow each Post #1 instructions on the ROM you choose and of course backup before flashing anything new
I hope this gets you to where you want to be, good luck.
Theres a lot of patience being displayed here. One should never start messing with their phone unless they have even the slightest clue what they are doing from the start
piaa_nissan said:
Theres a lot of patience being displayed here. One should never start messing with their phone unless they have even the slightest clue what they are doing from the start
Click to expand...
Click to collapse
The amount of patience I am seeing is mind blowing! To the OP...Just some words of advice. I have been a member of XDA for alot of years now and I can tell you that you will get a tremendous amount of help from this community. My only suggestions would be,when looking for help:
1) Be very clear as to the question you are asking.
2) If someone is willing to help you, Give them all of the information that they are asking you for.
3) Punctuation goes a very long way when someone is trying to understand what you are asking. Try using a period to avoid run on sentences.
Please do not take this as anything other then what I have learned over the years to get the best and quickest help!
I hope these guys are able to help you with your issues! :fingers-crossed: