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.
Hi,
I'm having this issue where I get a pop-up window saying "Android is upgrading..." and "Starting applications..." every time I reboot the phone. It's not the same as when I wipe the dalvik cache where it states "Optimizing applications # through #" for about a minute or two on reboot. What I'm seeing is about 1 to 3 seconds.
I did a complete factory reset, re-flashed the ICS RUU as well as the ROM. It was fine in the beginning and for quite a while after I reinstalled my apps but it eventually came back.
I tried uninstalling apps a few at a time and it didn't change anything until I got down to the last four and then it went away. So, I then tried restoring from nandroid backup and just removing those four apps but it didn't work that time. The issue was unaffected.
I realize that the symptoms point to one or more of my apps but I was wondering if there is some kind of diagnostic logger that I can use to record whats happening during reboot that might offer some hints as to which one(s). One possible indirect culprit might be Superuser. I've had a permanent issue with updating the SU binary. When I do, I lose the ability to add new root apps. I keep root for existing root apps, but SU won't detect any requests from new apps. Therefore, I simply don't update the binary and I have no problems with new apps.
Any suggestions or recommendations would be greatly appreciated.
Thanks.
RuLEoF2 said:
Hi,
I'm having this issue where I get a pop-up window saying "Android is upgrading..." and "Starting applications..." every time I reboot the phone. It's not the same as when I wipe the dalvik cache where it states "Optimizing applications # through #" for about a minute or two on reboot. What I'm seeing is about 1 to 3 seconds.
I did a complete factory reset, re-flashed the ICS RUU as well as the ROM. It was fine in the beginning and for quite a while after I reinstalled my apps but it eventually came back.
I tried uninstalling apps a few at a time and it didn't change anything until I got down to the last four and then it went away. So, I then tried restoring from nandroid backup and just removing those four apps but it didn't work that time. The issue was unaffected.
I realize that the symptoms point to one or more of my apps but I was wondering if there is some kind of diagnostic logger that I can use to record whats happening during reboot that might offer some hints as to which one(s). One possible indirect culprit might be Superuser. I've had a permanent issue with updating the SU binary. When I do, I lose the ability to add new root apps. I keep root for existing root apps, but SU won't detect any requests from new apps. Therefore, I simply don't update the binary and I have no problems with new apps.
Any suggestions or recommendations would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
1.) How did you root the rez? some are very picky 2.) are you using Titanium backup to restore system apps or using an app like kernel tuner?
I used the ICS RUU installation guide on TeamBAMF which walks you through using the HTC bootloader unlocker, flashing a recovery and a custom ROM. Later on, I used the S-OFF tool from JuopunutBear and flashed RezROM Ex 3.4.
I do use TBU but not to restore system apps or any data in general. I understood a long time ago that restoring data can lead to trouble so I rarely do it. I occasionally use TBU to restore user apps (no data) but have gotten into the habit of using the market links to get the app directly from the market.
RuLEoF2 said:
I used the ICS RUU installation guide on TeamBAMF which walks you through using the HTC bootloader unlocker, flashing a recovery and a custom ROM. Later on, I used the S-OFF tool from JuopunutBear and flashed RezROM Ex 3.4.
I do use TBU but not to restore system apps or any data in general. I understood a long time ago that restoring data can lead to trouble so I rarely do it. I occasionally use TBU to restore user apps (no data) but have gotten into the habit of using the market links to get the app directly from the market.
Click to expand...
Click to collapse
what recovery are you using? Amon ra 3.1.6 has the su and superuser installer built in and ive never had issues....id also suggest after actually running an RUU.exe and not an OTA (ph98img file) to do the amon ra method and a pure clean flash...should fix your issue
Ok. I'll try your suggestion to help solve the Superuser problem, but what do you think about getting rid of the "upgrading" messages? Is there a way to record what the system is doing during reboot?
RuLEoF2 said:
Ok. I'll try your suggestion to help solve the Superuser problem, but what do you think about getting rid of the "upgrading" messages? Is there a way to record what the system is doing during reboot?
Click to expand...
Click to collapse
if you are familliar with adb you can pull a logcat....to be honest though this does sound like either a bad or unclean flash of a rom or the whole rom itself
REV3NT3CH said:
if you are familliar with adb you can pull a logcat....to be honest though this does sound like either a bad or unclean flash of a rom or the whole rom itself
Click to expand...
Click to collapse
You are correct that the re-flash will solve the problem, but only temporarily. If this was a first time occurrence, I agree that a pure clean re-flash is the best approach but I've already done that numerous times, well over a dozen in the past year or so.
Only a couple weeks ago I did a complete wipe of everything (factory reset, data, cache, dalvik cache, boot, system, rotate settings AND battery stats) and then re-flashed the RUU four (4) times back-to-back. The TeamBAMF guide says to flash it twice so I doubled it to be sure. I then flashed the ROM twice. That solved the "Updating" problem as it always has. However, once I finished re-installing my most frequently used apps, the problem came back.
It hasn't been consistent. It doesn't always come back. Doing the wipe and re-flash works about 50% of the time. I'll go months without it showing up again and then all of the sudden, there it is. It doesn't seem to correlate to the installation of any one particular app. I've tried installing only a few at a time and watching it but when it does come back, it never occurs until after I've installed my most basic line-up.
If there is any one activity that it seems to follow it is after I've had another issue (usually tinkering with a root app or mod and didn't like the way it turned out) and performed a wipe and nandroid restore. It doesn't come back every time, but it's on that initial reboot when I usually first notice it. In those cases, it's always hard to say whether the root app or mod caused the problem or did the wipe and restore do it.
RuLEoF2 said:
You are correct that the re-flash will solve the problem, but only temporarily. If this was a first time occurrence, I agree that a pure clean re-flash is the best approach but I've already done that numerous times, well over a dozen in the past year or so.
Only a couple weeks ago I did a complete wipe of everything (factory reset, data, cache, dalvik cache, boot, system, rotate settings AND battery stats) and then re-flashed the RUU four (4) times back-to-back. The TeamBAMF guide says to flash it twice so I doubled it to be sure. I then flashed the ROM twice. That solved the "Updating" problem as it always has. However, once I finished re-installing my most frequently used apps, the problem came back.
It hasn't been consistent. It doesn't always come back. Doing the wipe and re-flash works about 50% of the time. I'll go months without it showing up again and then all of the sudden, there it is. It doesn't seem to correlate to the installation of any one particular app. I've tried installing only a few at a time and watching it but when it does come back, it never occurs until after I've installed my most basic line-up.
If there is any one activity that it seems to follow it is after I've had another issue (usually tinkering with a root app or mod and didn't like the way it turned out) and performed a wipe and nandroid restore. It doesn't come back every time, but it's on that initial reboot when I usually first notice it. In those cases, it's always hard to say whether the root app or mod caused the problem or did the wipe and restore do it.
Click to expand...
Click to collapse
which leads me to believe its a rom issue for that specific rom...ive never used that one so i cant verify thats what it for sure is....but having to flash the same rom twice for it to work seems like what can cause it in the first place because it already obviously clearly has some bugs...also flashing an RUU (which is a windows .exe based program...many people confuse this with an OTA ph98img file) is actually partitioning, wiping, and re installing the pure factory OS, HBOOT, and Recovery... which no recovery can do....which shouldnt be done directly before a rom install...a full thorough wipe in a custom recovery and then the install of the actual rom you are trying to obtain is how it should be done...to be honest though with how buggy this rom sounds id just suggest going to a new rom....which i have good suggestions for sense based ones
REV3NT3CH said:
which leads me to believe its a rom issue for that specific rom...ive never used that one so i cant verify thats what it for sure is....but having to flash the same rom twice for it to work seems like what can cause it in the first place because it already obviously clearly has some bugs...also flashing an RUU (which is a windows .exe based program...many people confuse this with an OTA ph98img file) is actually partitioning, wiping, and re installing the pure factory OS, HBOOT, and Recovery... which no recovery can do....which shouldnt be done directly before a rom install...a full thorough wipe in a custom recovery and then the install of the actual rom you are trying to obtain is how it should be done...to be honest though with how buggy this rom sounds id just suggest going to a new rom....which i have good suggestions for sense based ones
Click to expand...
Click to collapse
Well, if you wouldn't mind offering some of your ROM suggestions and perhaps a sound RUU download source I'll give it a go and see what happens. I'm sure the initial results will be positive, it's the long-term that will be the real test.
One more piece of potentially useful information. I've converted one market app from user to system and froze, uninstalled or converted several user apps that were installed as system apps by the ROM. I read in one thread where someone had the same issue and a responder theorized that it could be from converting a user app to system. The responder followed saying the issue could be a symptom of the converted app not having corresponding "odex" files. I'm only a modest tinkerer and certainly not a developer so I'm not sure what that means or how important that is. However, I tried reversing the three conversions that I did and the issue persisted.
RuLEoF2 said:
Well, if you wouldn't mind offering some of your ROM suggestions and perhaps a sound RUU download source I'll give it a go and see what happens. I'm sure the initial results will be positive, it's the long-term that will be the real test.
One more piece of potentially useful information. I've converted one market app from user to system and froze, uninstalled or converted several user apps that were installed as system apps by the ROM. I read in one thread where someone had the same issue and a responder theorized that it could be from converting a user app to system. The responder followed saying the issue could be a symptom of the converted app not having corresponding "odex" files. I'm only a modest tinkerer and certainly not a developer so I'm not sure what that means or how important that is. However, I tried reversing the three conversions that I did and the issue persisted.
Click to expand...
Click to collapse
if youve already used an ruu once you dont need to do it everytime you flash a rom....and depending on the rom certain recoveries wont work for them...good example amon ra will not work for JB or higher....if staying on ICS or sense based roms stick with amon ra only....im guessing your looking for a good Sense based rom correct?.....as for converting apps...i highly suggest against it on sense rom and can cause issues with the rom...on aosp its fine but sense just doesnt like some of them
REV3NT3CH said:
if youve already used an ruu once you dont need to do it everytime you flash a rom....and depending on the rom certain recoveries wont work for them...good example amon ra will not work for JB or higher....if staying on ICS or sense based roms stick with amon ra only....im guessing your looking for a good Sense based rom correct?.....as for converting apps...i highly suggest against it on sense rom and can cause issues with the rom...on aosp its fine but sense just doesnt like some of them
Click to expand...
Click to collapse
My mistake, but I should have been more specific. I've only re-flashed the RUU three... maybe four times since I've owned the phone and only as a last resort to fix a problem that a wipe and/or ROM re-flash alone wasn't correcting.
As for recovery, I've only used Amon Ra on my Rezound. It's what was recommended in the Team BAMF guide and I've stuck with it. I do prefer a sense-based ROM and ICS works fine for me right now. The HTC Incredible was my first smart phone and I rooted that within a month of getting it. I tried a few ROMs but eventually settled on Skyraider which I really liked. RezROM is the only comperable ROM that I've come accross for the Rezound, but if you have recommendations, I'll give them a try.
Here's what I've done so far. The ICS RUU linked in the Team BAMF guide was an internal flash through the bootloader. To eliminate that as a possible cause, I found a couple .exe versions to run from my PC.
On the first run, I immediately flashed RezROM and used Amon Ra to install Superuser and SU as you suggested. I updated Superuser and then installed a few basic root apps: Titanium Backup, Root Explorer, QuickBoot, Busy Box, Root Checker and Root Validator. There were no issues until I starting using those root apps. I was periodically rebooting and it wasn't until I updated Busybox and ran TBU and Root Explorer that the "Android is upgrading..." message came back. Worse than before, it was doing the "Optomizing apps # through ##" part where before it was just the "upgrading" message. I uninstalled all of them one-by-one but whatever happened was perminant because it didn't go away so I did a full wipe and used the second ICS RUU .exe. On the second run I stayed stock. Again, I used Amon Ra to install Superuser and SU. I updated Superuser and then installed those same basic root apps. So far, no issues.
With these results, it's pretty evident that the problem is ROM related, but not necessarily a bug as much as a compatibility discrepancy. This issue has never been this persistent until the last few months and within that time, there has been several updates for TBU, Root Explorer and Busybox. I agree that switching to a different ROM may be the ultimate solution, but unless there is one that is a RezROM comparable, I'm not ready to write it off just yet. If there's a way to pin point which app is the cause, I might be able to find a workaround or persuade the developer to come up with a fix, I'd much rather try that first.
But again, I'm certainly interested in trying out any ROM suggestions you might have to offer in the meantime.
In the process of trying to nail down this problem, I've discovered that it appears to have something to do with the relationship between superuser and RezROM.
Since I first flashed RezROM, I haven't been able to update superuser or the binary in any way. In addition to downloading from the market, I've tried re-installing superuser with Amon Ra, flashing it from the sdcard in recovery and from adb. No matter how I do it, I either lose root or it shuts down superuser's ability to detect requests from new root apps. I tried to find a solution but had no success so I just decided to ignore it as long as it didn't effect functionality. I've had root app issues here and there but always chalked it up to a bug with that particular app and either found a fix or ditched the app altogether.
I've been able to isolate superuser as the cause of the "upgrading" message issue with several full wipes, RezROM and RUU re-flashes. In my last three attempts to narrow it down, I did completely sterile RUU and RezROM flashes and used Root Explorer and Root Checker as test apps. In each attempt, I lost root and the "upgrading" messages returned as soon as I updated superuser or the binary. I tried doing the same with the stock ROM and with one of the BAMF ROMs and these problems don't occur with either of them.
So, with the "Android is upgrading" message popping up repeatedly, having new stability problems with previously dependable apps and increasing system bugs, it's apparent that the consequences of having such a severely outdated superuser has finally caught up with me. It definitely looks like RezROM is the problem and unless there are some options that I might try to fix it myself, it's up to the developer. I've contacted them but I'm not optimistic that they'll be willing to put any time into coming up with a fix since the Rezound is so "dated".
I had this popup on every boot on my Evo 3D with the stock ICS Sense 3.6 ROM, I still have it on my Rezound with a custom ICS Sense 4.1 ROM. I just assumed it's standard behaviour from Android, why would you think it's an issue if it doesn't cause any problems?
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
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:
Hello.
I was able to fix the random reboots i had with flashing prerooted zip via TWRP, this apply also on the new 26.1.A.3.111, only tested on E2306.
1. Must backup your data. You are gonna wipe it
2. Use flashtool and downgrade to a rootkitXperia rootable firmware. I used 26.1.A.1.112 but other rootable should be the same. (wipe data may not be necesary in this step but i did it just in case)
3. When flashing done, root the device with rootkit, and install TWRP
4. Use xperifirm to download the 3.111 FW then create the prerooted with its system.ext4 and kernel.elf
5. Flash the zip via TWRP, wipe dalvik, then start the phone and check that you have superuser, and go about phone to make sure everything went well and your in 3.111 with its kernel also.
6. Use flashtool again to flash 26.1.A.3.111 but you this time you must EXCLUDE SYSTEM and KERNEL to keep the root, in other words your gonna flash everything but kernel and system so be sure you ticked them, also should wipe data so you can start fresh and avoid possible incompatible things.
7. Let the phone starts, mine took around 10 - 15 min. You should now be in 26.1.A.3.111 with root and no random reboots. So far im using it since 12 days and no reboots nor system hangs, ive updated all apps via playstore, and even downloaded several 500Mb+ games and its working really fine
Click to expand...
Click to collapse
Sorry for this guide that isnt noob friendly, im doing it quite hurry because im too busy with work but i wanted to share what worked for me with everyone. If this works for you too and someone wants to do a better noob friendly guide with links and such go ahead it is ok.
[NOTE]Random reboots seems to happen when there are diferent modem versions. Special thanks to @sergioslk who discovered this.
Of course, all credits to the respective developers who worked really hard on this tools for us. Thanks devs.
Hey, thanks. I had 26.1.A.2.167 rooted, so I just installed 3.111 with data wipe through prerooted zip on top of 2.167, and then reflashed everything except for kernel and system (also data wipe here) like you wrote in your post. So far so good - almost 30h without reboot, which is far better than before.
Hm, didn't work for me also with 3.111 I reflashed (using stock 3.111 from xperifirm) excluded kern and system but it is still randomly rebooting when installing gapps.
fpghost84 said:
Hm, didn't work for me also with 3.111 I reflashed (using stock 3.111 from xperifirm) excluded kern and system but it is still randomly rebooting when installing gapps.
Click to expand...
Click to collapse
Did you first flashed via TWRP the prerooted zip you created with system.ext4 and kernel.elf extracted from 3.111 FW? did you wiped data after completing flash? which version of FW you had just before flash 3.111?
Yeah, I did as you say. My phone orig had 2.167, but it upgraded itself recently to 3.111, then I downgraded to 1.128 to root, before using the prerooted TWRP zip (with system.ext4 and kernel.elf extracted from 3.111 ftf) to upgrade back to 3.111.
EDIT: I think something went wrong when I created the ftf bundle from the files downloaded from xperifirm. I repeated the whole process and now I'm not seeing the random reboots (at least for an hour with quite a few apps installed and updated) ....So yeah in summary many thanks for this ...It would be nice if it was mentioned on the main how to thread.
thewailer said:
Hello.
I was able to fix the random reboots i had with flashing prerooted zip via TWRP, this apply also on the new 26.1.A.3.111, only tested on E2306.
Click to expand...
Click to collapse
Thanks so much for posting this. I had thought of doing this myself but quickly ruled it out because I thought it was a dumb idea (no offense) and wouldn't work, but after hearing of your success I thought I'd give it a try anyways and I've been powering through a ton of app installs/updates and haven't had a single reboot so far. It sounds to me like this is the key.
I'll post an edit after a few days to let you guys know how it holds to my personal test of time.
Thanks again!
Update:
Well, it's been nearly a week now and I've yet to experience a random reboot. This is definitely the fix we've all been waiting for! I hope this knowledge can be spread to all who have been plagued with this issue!
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
sergioslk said:
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
Click to expand...
Click to collapse
Hey @sergioslk,
Thanks so much for your contribution. I found your post about this problem but it was kind of hard to read whereas the original poster here went into a bit more detail. Sometimes that's all people need, is a little more information. I'm sure you've made other contributions to the community that have been extremely valuable.
To reitterate, this is definitely the fix to the problem we've all been facing when it comes to using the pre-rooted zip to get root on the latest version. I had suspected this to be the problem awhile ago but couldn't really figure out how to fix it.
Thanks everyone for all your hard work!
sergioslk said:
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
Click to expand...
Click to collapse
Oh dude many thanks for this contribution, i havent readed your post before, but now i can say theres a know reason why the random reboots occurs. Im not an expert in android, i just tried this as a last hope, ive tried everithing, no google account, no wifi, no moibile data, no sdcard, deleting all bloatware, untouching bloatware, a lot of wipes..... and this last one for some reason worked but i wasnt sure why untill now. Thanks again!