Database Users

Tl10 b120sp04

Hello guys,
My Mate 7's original version is B120SP04 (32gb/3gb RAM) and I upgraded to B324. Well, to be honest, the only reason why I like B324 is because it's Lollipop. It has better UI. But then again, just because it is newer doesn't mean it is better, right?
I experienced a lot of bugs on B324. I thought that if I downgraded back to B120SP04, cleared cache partition, and reformatted the phone the bugs would be fixed, or at least lessened. Unfortunately, it didn't.
Anyway, I'm thinking of downgrading to B120SP04 for good, or until Huawei fix the bugs.
So my question, what's after B120SP04? I mean can I still upgrade my phone to a firmware with better performance? I'm talking about KitKat.
Thank you!

markchong89 said:
Hello guys,
My Mate 7's original version is B120SP04 (32gb/3gb RAM) and I upgraded to B324. Well, to be honest, the only reason why I like B324 is because it's Lollipop. It has better UI. But then again, just because it is newer doesn't mean it is better, right?
I experienced a lot of bugs on B324. I thought that if I downgraded back to B120SP04, cleared cache partition, and reformatted the phone the bugs would be fixed, or at least lessened. Unfortunately, it didn't.
Anyway, I'm thinking of downgrading to B120SP04 for good, or until Huawei fix the bugs.
So my question, what's after B120SP04? I mean can I still upgrade my phone to a firmware with better performance? I'm talking about KitKat.
Thank you!
Click to expand...
Click to collapse
I actually didn't notice any bugs as of the moment, the camera app has more functionalities...
the way i upgraded is like this:
1 - i downloaded the file from website
2 - inserted a micro sd card, didnt remove the sim, made sure battery is at least 90%
3 - formatted the memory card
4 - pasted the "dLoad" folder containing the lollipop os in the root directory of micro sd card
5 - did upgrade using local upgrade in the settings
6 - waited for the upgrade to finish
7 - phone upgraded successfully, all my files were intact though but im experiencing lags
8 - i tried doing format through settings but failed
9 - did format using volume key + power
10 - format is successful and the phone ran smoothly and better
can you cite the bugs you've encountered?

19Excalibur19 said:
I actually didn't notice any bugs as of the moment, the camera app has more functionalities...
the way i upgraded is like this:
1 - i downloaded the file from website
2 - inserted a micro sd card, didnt remove the sim, made sure battery is at least 90%
3 - formatted the memory card
4 - pasted the "dLoad" folder containing the lollipop os in the root directory of micro sd card
5 - did upgrade using local upgrade in the settings
6 - waited for the upgrade to finish
7 - phone upgraded successfully, all my files were intact though but im experiencing lags
8 - i tried doing format through settings but failed
9 - did format using volume key + power
10 - format is successful and the phone ran smoothly and better
can you cite the bugs you've encountered?
Click to expand...
Click to collapse
Actually, this is the second time I upgraded to Lollipop. Before upgrading on my second try, I did step 9 first. Then steps 3-6.
Encountered bugs are:
1. 2 instances of Messaging app running. Let's say you opened the Messaging app once and you exited by pressing the back or home button. Then when you run it again by pressing the icon and pressed the square button, you will see 2 Messaging app on the screen, which should just be 1.
2. Smart screenshot doesn't work. Someone said I should knock harder, but it really doesn't work. It works on my first upgrade though.

markchong89 said:
Actually, this is the second time I upgraded to Lollipop. Before upgrading on my second try, I did step 9 first. Then steps 3-6.
Encountered bugs are:
1. 2 instances of Messaging app running. Let's say you opened the Messaging app once and you exited by pressing the back or home button. Then when you run it again by pressing the icon and pressed the square button, you will see 2 Messaging app on the screen, which should just be 1.
2. Smart screenshot doesn't work. Someone said I should knock harder, but it really doesn't work. It works on my first upgrade though.
Click to expand...
Click to collapse
I did upgrade from 125 and I still never found any bugs or error,ph running very smooth,for me I can say newest is the perfect one than the kk...I just reset 125 first then upgeade lollipop, I didnt even need to reset after upgrade...
Sent from my HUAWEI MT7-TL10 using XDA Free mobile app

markchong89 said:
Actually, this is the second time I upgraded to Lollipop. Before upgrading on my second try, I did step 9 first. Then steps 3-6.
Encountered bugs are:
1. 2 instances of Messaging app running. Let's say you opened the Messaging app once and you exited by pressing the back or home button. Then when you run it again by pressing the icon and pressed the square button, you will see 2 Messaging app on the screen, which should just be 1.
2. Smart screenshot doesn't work. Someone said I should knock harder, but it really doesn't work. It works on my first upgrade though.
Click to expand...
Click to collapse
the 2nd time you attempted upgrading to lollipop, did you went back to the sp04 version KitKat first? there are certain versions you need to use in order to have a smoother transition with the official lollipop release from Huawei. sp04 is one of them...

19Excalibur19 said:
the 2nd time you attempted upgrading to lollipop, did you went back to the sp04 version KitKat first? there are certain versions you need to use in order to have a smoother transition with the official lollipop release from Huawei. sp04 is one of them...
Click to expand...
Click to collapse
Yes, second time I attempted to upgrade to LP my phone was on B120SP04. On B120, I used the volume + power key reboot. I cleared cache partition and reformatted my phone. Put the B324 on my SD card and upgraded to LP.

markchong89 said:
Yes, second time I attempted to upgrade to LP my phone was on B120SP04. On B120, I used the volume + power key reboot. I cleared cache partition and reformatted my phone. Put the B324 on my SD card and upgraded to LP.
Click to expand...
Click to collapse
before you tried upgrading to lollipop the 2nd time, you're already running sp04... did you experience any problems with sp04?

19Excalibur19 said:
before you tried upgrading to lollipop the 2nd time, you're already running sp04... did you experience any problems with sp04?
Click to expand...
Click to collapse
No problems with B120. It was fast.
Sent from my HUAWEI MT7-TL10 using Tapatalk

markchong89 said:
Hello guys,
My Mate 7's original version is B120SP04 (32gb/3gb RAM) and I upgraded to B324. Well, to be honest, the only reason why I like B324 is because it's Lollipop. It has better UI. But then again, just because it is newer doesn't mean it is better, right?
I experienced a lot of bugs on B324. I thought that if I downgraded back to B120SP04, cleared cache partition, and reformatted the phone the bugs would be fixed, or at least lessened. Unfortunately, it didn't.
Anyway, I'm thinking of downgrading to B120SP04 for good, or until Huawei fix the bugs.
So my question, what's after B120SP04? I mean can I still upgrade my phone to a firmware with better performance? I'm talking about KitKat.
Thank you!
Click to expand...
Click to collapse
sorry about this but would you mind backing up your file system in cwm/twrp and upload them cause i fked up my phone it won;t boot into stock recovery it only boot loop can get it in fastboot mode and any custom recovery

Updating from 4.4.4 to latest (7.0/7.1) ?

Was given back my Nexus 7 tablet and was thinking about updating it. Currently rooted running on a 4.4.4 rom (purity). Is there any new basebands/modems that I need to flash/update before flashing a 7.0 rom? Would appreciate any pointers, thanks in advance!

You probably should first update your device to the latest factory image from Google (5.1.1 - LMY47V, including 4.23 - bootloader, etc.), then installing the latest TWRP 3.1.1 and you should be fine for a 7.x Nougat ROM.
Please be sure to select correct factory image (nakasi / nakasig) depending on your model and probably verify that the bootloader included within the factory image is a "good one" because there existed factory images from Google with a non working bootloader ... You probably might want to have a look here

AndDiSa said:
You probably should first update your device to the latest factory image from Google (5.1.1 - LMY47V, including 4.23 - bootloader, etc.), then installing the latest TWRP 3.1.1 and you should be fine for a 7.x Nougat ROM.
Please be sure to select correct factory image (nakasi / nakasig) depending on your model and probably verify that the bootloader included within the factory image is a "good one" because there existed factory images from Google with a non working bootloader ... You probably might want to have a look here
Click to expand...
Click to collapse
is the rom in your signature stable enough for me giving this tablet to my mom and for it to not feel slower than life?
right now im on 4.4 and its very very very laggy
i have an update to 5.1 but i have been there and it was Unusable...
do you have any rom recomendation so it performs nice with some not demanding games ? and browsing
mine its the WIFI ONLY version
tablet is so old that i dont know where to look for a good rom anymore..
thanks for the help
edit:
im updating to 5.1.1 latest so im am on latest bootloader and stuff (but as my tablet is not updating im doing a factory image install, then TWRP then this rom https://forum.xda-developers.com/nexus-7/development/rom-android-7-aosp-grouper-t3467514 )
so the steps to follow would be
install TWRP
boot into recovery
**Factory reset tablet (wipe DATA and cache)
**install OTA for groupr wifi only tablet
**reboot into recovery
**install GAPPS (bean something)
**wipe dalvik/cache _
**then reboot???

@gierso should be fine ... if you run into setup issues, skip the google account setup, switch on WiFi and then add a user account to your tablet

AndDiSa said:
@gierso should be fine ... if you run into setup issues, skip the google account setup, switch on WiFi and then add a user account to your tablet
Click to expand...
Click to collapse
nevermind tablet is not updateable .. usb port does not respond to PC ( i think is broken as it sounds as connected disconected many times) so i ended up giving up trying to make it connect ..
i might open it to try to solder the pins.. or to try to change the connector but for the time being i just formatted it and installed the sole game i need it for (it still charges but the data connection is never acomplished) ...
i will try to update my nexus 7 2013 with a similar rom (but ifrom the 2013 forum of course)

Experience : successful Resurrection Remix NEM-L51 - Meticulus's ROM v5.8.5-20171214

Hi all XDA's members and Meticulus's RR ROM contributors,
I would like to share my experience with Meticulus's RR ROM for Honor 5C.
First I tried Elite V6 with no success : bootloop, F2FS or EXT4 nothing to do ; the Elite V7 is available from Christmas but I see that there are bugs to fix for Hassan, so I gave up and restored a backup of my STOCK system.
The restore was not good as my camera and audio no longer worked...
Before I get back to the STOCK update NEM-L51C432B357, I decided to try Meticulus's RR. It was a very good idea as I now have a renamed Honor 5c to hi6250 (...) working with no bug up to now.
LTE OK, SMS OK, GPS OK, SDCARD OK, AUDIO OK, VIDEO OK, GAPPS OK, MTP OK, etc
Adaway OK, Afwall+ OK, Magisk v14 OK
+ Bonus : Evie Launcher working as it was not using with STOCK ROM (icon size issue) !
Many thanks to Meticulus and contributors for sharing this very good work.
---
To be more precise for Honor 5C owners :
DEVICE : HONOR 5C
ROM STOCK BUILD : NEM-L51C432B350
MODDED RECOVERY .. : TWRP-3.1.1-0-hi6250-v5.2.zip
ROM INSTALLED .... : RR-N-v5.8.5-20171214-hi6250-Meticulus.zip
GAPPS INSTALLED .. : open_gapps-arm64-7.1-pico-20171225.zip
---
Steps of my successful installation with SDCARD and no SIM CARD :
1- FASTBOOT the TWRP then reboot to the TWRP RECOVERY
2- Wipe all except external SDCARD
3- Install the ROM
4- Reboot to TWRP RECOVERY
5- Install the GAPPS
6- Reboot to system (RR)
7- During RR Android setup, when asked insert the SIM CARD.
It would perhaps also have been successful with the SIM CARD inserted from the beginning...
---
Questions/feature requests :
- On Resurrection Remix site, I have not found your great ROM why ?
- On XDA Dev, there is no thread "Resurrection Remix For The Honor 5C [METICULUS]" but a "[ROM][7.1.2] Resurrection Remix For The Honor 6x [METICULUS]" one, this is why I put my comments here and in the Elite thread for those like me unable to get Elite V6 or V7 working with their Honor 5C.
- One thing is really missing to me (not found in settings) : the scheduled start/stop that worked very well with the STOCK ROM.
Do you think that this useful feature could be added on a future version ?
- The double TAP for screen wake up, would be a great bonus feature (was not provided in the STOCK ROM).
- Not tested the OTG, I will tell it in this thread.
Thanks again.
---
Meticulus's replies :
1. It is unlikely that any device with a kirin processor will get "official support" for LineagOS and therefore Resurrection Remix. There just isn't enough source.
2. Just because there is no "Honor 5c" thread doesn't mean you should come here and confuse information. It makes the water muddy. There is nothing stopping you from creating a thread in the "Honor 5c General" and post your experienced there.
3. Scheduled device start and sleep is not something I will work on.
4. DoubleTap 2 Wake only works on some P9 Lite's. Other devices with different touchscreens simply do not have the hardware capability.
5. I'm glad you like the ROM but please re-post your experiences in the Honor 5c section. I intend to delete these posts...

Is working dual sim and volte
Is works dual sim and volte

Sim working fine??

What do you think solved the audio issue?
Reverting to Stock Rom backup could have helped somehow.
Renaming it maybe ? And how did you rename it? After installing this rom mine became hi6250.
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Now installed this ResurrectionRemix twrp and rom after seeing this thread.Audio still refuses to work .

thatwasmyfakeacc said:
What do you think solved the audio issue?
Click to expand...
Click to collapse
I had the same problem on my NEM-L51. The problem is (or at least i think it is), that the vendor partition is somehow corrupted.
Short explaination, the vendor partition holds some drivers which are not open source (therefore not in the android kernel) and also aren't shipped in the custom roms (because of copyright stuff). So you always need to have them, if the custom rom depends on them (and most/all of the honor 5c custom roms do so). That's also the reason why you always have to flash the custom rom over your emui5.x and if you screwed your whole system, you first need to flash a backup or get back to emui on a different way before you can flash a working custom rom again.
So that's the explaination part. I installed twrp on my device, took a complete backup, flashed aosp from meticulus, everything worked except of Audio/Videos. Flashed LineageOS from Hassan, everything worked except of audio/video playback. Flashed backup, everything worked except audio/video. WTF. I don't know why, but i believe that the backups made with TWRP were somehow not complete, because flashing all partitions (the backup was over all partitions, triple checked, made new backups from stock) didn't solve audio issues, not even on the stock backup. What I now did was getting back to stock with the dload method, and flashed again directly the lineageos from hassan, which then worked. I had a try before where i first accidentially flashed aosp again, and same problems occured again. Also the now stock backup again didn't work. That's why i think that the TWRP backups for Honor 5c NEM-L51 are somehow not right.
Tl;dr if you have audio/video playback issues, try to get back to stock (make sure those features work on your stock rom) and flash again. If it still doesn't work, custom rom is maybe not compatible with nem-l51 (only experienced that with meticulus roms, hassans work great).
thatwasmyfakeacc said:
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Click to expand...
Click to collapse
Try again with the dload method, maybe use another UPDATE.zip. I had to try it several times, device booted sometimes for ever, and suddenly it worked. No idea why, but maybe try it again.

Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones

stevedat said:
Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones
Click to expand...
Click to collapse
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.

thelous said:
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.
Click to expand...
Click to collapse
Rite, it's just for fun.

shankarjdhv125 said:
Is works dual sim and volte
Click to expand...
Click to collapse
Hi,
Dual SIM not tested, Volte I don't know if it works using my ISP (free.fr) and don't know how to check this.
An advice, don't update Magisk, I have done it on several rr (honor 5c, idol3 5.5), the result was bootloop.

[A501CG T00J Kitkat 4.4.2] Cannot Upgrade to Lollipop - Update Exits abruptly

My current firmware is ASUS_T00J_WW_user_2.22.40.54_20151120_16 running non-rooted Kitkat 4.4.2 and I've followed a few guides from the ASUS site in an attempt to update from Kitkat to Lollipop.
The guide had me download this file: UL-ASUS_T00F-WW-3.23.40.52-user.zip (but had to get it from androidhostfile though because I couldn't find the official one from ASUS, as they seem to be already removed) and followed the rest of the instructions (copy the file into phone's Internal Storage, disconnect USB, check notification area for update).
My phone does recognize the system update file and tapping the relevant notification starts the process, but it will only work for a few seconds and then abruptly exit and proceed to reboot normally. It will show this:
i.imgur.com/H41GeyE.jpg
and then disappear and reboot the phone (notice the progress bar). In short, updating fails.
Any ideas, suggestions how to solve this? Any help would greatly be appreciated. Thanks in advance.

(but had to get it from androidhostfile though because I couldn't find the official one from ASUS, as they seem to be already removed) - That is not True. The Official Download Link for you: https://dlcdnets.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-3.24.40.87-user.zip
If the link is not working, try opening it from here: https://www.asus.com/Phone/ZenFone-A501CG/HelpDesk_Download/
Update a reply after trying to install from the official source.
I think the problem is not in your phone, but with the update itself, because it is causing conflicts. Otherwise try Factory Reset.

@mrsiri it Worked... Thanks!
mrsiri said:
(but had to get it from androidhostfile though because I couldn't find the official one from ASUS, as they seem to be already removed) - That is not True. The Official Download Link for you: https://dlcdnets.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-3.24.40.87-user.zip
If the link is not working, try opening it from here: https://www.asus.com/Phone/ZenFone-A501CG/HelpDesk_Download/
Update a reply after trying to install from the official source.
I think the problem is not in your phone, but with the update itself, because it is causing conflicts. Otherwise try Factory Reset.
Click to expand...
Click to collapse
It Worked... Thanks!

Need help getting LineageOS to be stable (15.1 UNOFFICIAL, hltevzw, TWRP 3.3.0)

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.