Related
first of all please look around , all your answers are available here in the forums,
make sure you have a computer ready to help you with fastboot,
my recovery kept getting wiped out but it was easy enough to push it via fastboot,
This thread has the best source for your manual ICS update for nexus S i9023.
http://forum.xda-developers.com/showthread.php?t=1398186
1. take a updated backup of the GB rom, then take a separate backup via titanium backup just to be safe. also backup all your required data(call logs / SMS)
2. into the recovery, make sure to wipe every thing including the dalvic cahche, chache, battery stats.
3. reboot once then install the update.zip(assuming you named the downloaded ICS rom into update.zip)
4.keep rebooting after every install of the update.zip then recovery then superuser.
5. install the super user file thats available here on the forums(2.3.6 or something). it works for time being. then when you have acess to the app market, remember to manually update it to 3.07(updated for ICS).
6. When you are done you have a fully working Rooted Nexus ICS.
7. i9023 users remember to actually get the i9023 version when it is released... because Just because this version works for US doesn't mean that it will give the best experience.
*.those complaining about poor battery life remember it takes a few 0-100 charging cycles to get a better estimate. and you need the estimate from zero. meaning you should have wiped the battery stats.
*. also most of the applications are working for ICS but don't expect them to work just because they were working on GB. they have not been updated for ICS. I know the web browsers keep crashing (i tested the ICS web browser, Dolhin HD and Mini, Opera Mobile and Mini).
*. softwares like data enabler and juice defender or 2x battery have been rendered SOMEWHAT irrelevant, because you can disable the background data quiet efficiently from the ICS Ui itself.
This is a rooting guide where you can also find the links for the CWM recovery and super user 2.3.6. trust me that it works.
http://forum.xda-developers.com/showthread.php?t=895545
PS: I am no mobile or any kind of software developer, I am just a guy who has spend last 3-4 days scouring the forums for any kind of help, and then played with my Nexus S 9023..
first of all please look around , all your answers are available here in the forums,
make sure you have a computer ready to help you with fastboot,
my recovery kept getting wiped out but it was easy enough to push it via fastboot,
This thread has the best source for your manual ICS update for nexus S i9023.
http://forum.xda-developers.com/showthread.php?t=1398186
1. take a updated backup of the GB rom, then take a separate backup via titanium backup just to be safe. also backup all your required data(call logs / SMS)
2. into the recovery, make sure to wipe every thing including the dalvic cahche, chache, battery stats.
3. reboot once then install the update.zip(assuming you named the downloaded ICS rom into update.zip)
4.keep rebooting after every install of the update.zip then recovery then superuser.
5. install the super user file thats available here on the forums(2.3.6 or something). it works for time being. then when you have acess to the app market, remember to manually update it to 3.07(updated for ICS).
6. When you are done you have a fully working Rooted Nexus ICS.
7. i9023 users remember to actually get the i9023 version when it is released... because Just because this version works for US doesn't mean that it will give the best experience.
*.those complaining about poor battery life remember it takes a few 0-100 charging cycles to get a better estimate. and you need the estimate from zero. meaning you should have wiped the battery stats.
*. also most of the applications are working for ICS but don't expect them to work just because they were working on GB. they have not been updated for ICS. I know the web browsers keep crashing (i tested the ICS web browser, Dolhin HD and Mini, Opera Mobile and Mini).
*. softwares like data enabler and juice defender or 2x battery have been rendered SOMEWHAT irrelevant, because you can disable the background data quiet efficiently from the ICS Ui itself.
This is a rooting guide where you can also find the links for the CWM recovery and super user 2.3.6. trust me that it works.
http://forum.xda-developers.com/showthread.php?t=895545
PS: I am no mobile or any kind of software developer, I am just a guy who has spend last 3-4 days scouring the forums for any kind of help, and then played with my Nexus S 9023..
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
System + data + cache wipe, use core gapps 2-26. If you encounter issues, then again install rom after full wipe, but don't install gapps immediately. Reboot, and delete unwanted system apps to free up space, and then flash gapps and wipe cache
No easy way to backport safestrap (replacement for boot menu)
Sent from my MB526 using Tapatalk
johnaddams83 said:
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
Click to expand...
Click to collapse
do not use standard gapps..system partition not big enough to store standard gapps..install core gapps
Don't ask why I stayed so long on 4.2.2, did PhD and the phone was running nicely and hat no time to update, root again etc. pp. Now that the PhD is finished I wonder if it is worth at all to invest the time to update to higher version. It looks like 5.0 was the last update supported by sony. I don't have a custom ROM, just rooted original Sony firmware with flashtool.
In general I don't see a personal benefit to buy a new phone. Keeping the Z and updating to the best Version or custom ROM running smoothly on the old hardware and which can be rooted is my choice.
Which version and ROM do you suggest?
Thank you for your time and advise
It depends on what you need.
If all you need is a durable battery, then better stay on 4.2.2, but you know...as time goes by, most application will stop their support for jellybean.
If you want more performance, then 5.1.1 is the choice, but not battery friendly. STAMINA mode is present to help saves some battery.
For the best updated OS version, go for LineageOS 14.1. It's based on nougat 7.1.2.
Many thanks, as far as I remember I can do a image with CWM of current system and can give LineageOS a try! I saw now that some modern apps need at least jellybean 4.4 to be installable. Battery shouldn't be a problem, I rather want the camera to work nicely also under a customROM, actually I think the original Sony camera app is quite good and this one I would loose. All other Sony apps I never noticed really. For all the other possible customROM I don't really have the time to study them, camera would be most important. I guess recovering most of the apps from jellybean 4.2.2 to Lineage via Titanium Backup will work so I can check this fast?
Thanks in advance!
You can also try to use RR Oreo if you like the latest Android.
https://forum.xda-developers.com/xperia-z/development/rom-resurrection-remix-o-6-0-0-t3747588
Here what I think about it:
https://mastodon.social/@ahmd_amsyr/99954433452073565
Hmm, I installed lineage 14.1 zip via ROM Manager and it was succesful, but then I also wanted to add directly after this the optional lineage root. The phone was already rooted and unlocked and when pressing the option, the screen went immediatley black. When pressing power button the lamp is short igniting green/red and screen stays black. Installed the newest flashtool and flashtool drivers, but when trying to root or flash the xperia z again via flashtool, it always says in the flashtool log, the driver is too old under Win 7 and Win 10 on 2 PCs. I installed pc companion and additionallly the flashtool drivers.
Do I have to install distinct versions of flashtool and drivers? Flashtool is version 0.9.24...?
I could manage to get it in boot loop now, showing sony logo. But with same flashtool it's not possible to flash ftf in flash or fast boot mode, because it is constantly rebooting. What to do now?
https://forum.xda-developers.com/xperia-z/development/kernel-ub-t3198491
this does not work
https://forum.xda-developers.com/xperia-z/general/disaster-recovery-getting-z1-zu-z-zl-to-t2229250
also doesn't help
Still would like to install lineage.zip again. But how do I get the device booting normally and is the rom manager stil alive? If not I can also flash directly via flashtool a .ftf?
Nevermind, I could repair it, now on 5.1.1 stock.
as someone asked per pm:
I'm also not sure what changed it. I went then to very old flashtool version on my old notebook, probably over 5 years old when I flashed my xperia neo smartphone. With this it worked. Flashtool version is one point. My bootloader was unlocked. The flashing of lineage 7.1.1 also worked, I then made the error to root also via Lineage package directly after flashing the rom, then I was in Boot loop. It's best to start flashing, let flashtool compile the zip, this takes some minutes, progress shown in flashtool, and then you connect via usb smartphone, especially when in boot loop. But start with different flash tool version and post your error messages in the thread i posted. I stil have the old xda tabs in my browser history that helped me to install ics on neo and lollipop on xperia z (and it is really fast again after complete reinstall) no need for new phone
I flashed to LineageOS 7.1.2 and I do not regret it. I have the (almost) latest version on Android. I can manage the apps permissions and it all works great.
Last few days I tried to use custom ROM. Volte doesn't work. I've given up on that issue now. Now problem is Miui pro.
After flashing it keeps showing boot logo ( I waited for more than 30 minutes) but the older version (7... Something) flashes without any problem.
How long should I wait to complete it's booting process( more than an hour??!!!!!)
P.s- device encryption is enabled [ but I don't think it's causing the problem cuz older version is doing fine]
http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks ?
Also check this post for more information.
Link:- https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Thanks.
Im running Miui 9.2 global stable 9.2.2.0
Can i do dirty install? I dont wanna lose apps data
Im using stock miui global stable 9.2.2. Android 6.0
If i wanna install miui id, do i need to wipe all , as in format my handset. Or is it ok to just wipe system, cache dv? I dont wanna lose my apps data
@Trovies hi,
Just do titanium or swiftbackup search the apk in google, and u can do dirty flash but i will not recommend it.
Note :- download the premium version of the swiftbackup from the internet.
Thanks
Flash lazyflasher.zip
Sagar_zac said:
http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks
Click to expand...
Click to collapse
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Vinayakn73 said:
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Click to expand...
Click to collapse
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. ?For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache
Sagar_zac said:
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache
Click to expand...
Click to collapse
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??
Vinayakn73 said:
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??
Click to expand...
Click to collapse
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process
Sagar_zac said:
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process
Click to expand...
Click to collapse
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english
Vinayakn73 said:
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english
Click to expand...
Click to collapse
Ya i know modules can be a pain in the ass only one suggestion when ever after flashing a module if its stuck in the bootloop then just use magisk Uninstaller then again install Magisk or use magisk for recovery to remove the particular module which is causing boot loop also use root youtube valence and use universal installer it will not cause bootloop. Also use minimal module only what you need. Ok then. Also do as u discreet i am fine in this rom. And its great. ?
See my modules
I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.
Sagar_zac said:
I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.
Click to expand...
Click to collapse
yup there is no doubt this is best custom miui rom out there. But this bootloop and boot time driving me nuts. I wonder why all this problems are popping up though the rom is based on official firmware and I've never faced such problem with official roms. I will give it a try again after two days. I just hope that time it will go smooth.
I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.
I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...
I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.
I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.