Develop Bugs

Never never an Lg again

I like lg's hardware. I had optimus 3d and now have optimus g. Both has great hardware.
I have flashed custom roms since windows mobile days, so i should have a little experience..!
But you can never be sure to flash safely especially with Lg. You can loose your imei, baseband...etc
And now i have kernel crash on my loved optimus g... A demogod kernel crash. I can boot in cwm but cant restore system. It restore boot and then system restoring fails. I can also boot in android and after a few seconds it crashes. So it doesnt stay long enough to be fx recognized by pc to save it. Pc doesnt recognize it even in download mode. I will also try with another pc.
You dont have such problems with htc or samsung. The problems with these phones arent so complicated like lg.
SO NEVER AN LG AGAIN...

What about side loading rom? Phones with external sd cards are great in such moments.
Sent from my LG-E975 using XDA Premium 4 mobile app

nchc said:
What about side loading rom? Phones with external sd cards are great in such moments.
Sent from my LG-E975 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I need to try it on another pc, as i said my pc cant see the phone. But it doesnt chage the truth about such problems with Lg.

yup, why not when you mess up the phone and cant do any thing about it, lets rock the blame game..
lu6200 to su640 to lte2 to optimus g to optimus g pro.... never had any issues and never will buy anything else.

You can't blame LG for a mishandeling YOU made.
I had HTC's and Samsung in the past, they all present a "bricking" potential if you start to fool around with Kernel, custom rom, etc.
Now, you should try to restore it back to stock to see if it fixes your issues.

t1mman said:
You can't blame LG for a mishandeling YOU made.
I had HTC's and Samsung in the past, they all present a "bricking" potential if you start to fool around with Kernel, custom rom, etc.
Now, you should try to restore it back to stock to see if it fixes your issues.
Click to expand...
Click to collapse
You should read my post again...
Yes i will try stock rom but i think i have read somewhere that some still has it even after stock rom...

niyazidk said:
You should read my post again...
Yes i will try stock rom but i think i have read somewhere that some still has it even after stock rom...
Click to expand...
Click to collapse
Yes, I've read your post: You've flashed a custom rom and now get a kernel error.
Go back to stock in download mode using KDZ updater and you should be ok.
Follow this guide to the letter:
http://forum.xda-developers.com/showthread.php?t=2010624
And, as I already told, LG can't be blame for anything other than running stock. Even if you only root the device and crash it, you can't blame em for this.

t1mman said:
Yes, I've read your post: You've flashed a custom rom and now get a kernel error.
Go back to stock in download mode using KDZ updater and you should be ok.
Follow this guide to the letter:
http://forum.xda-developers.com/showthread.php?t=2010624
And, as I already told, LG can't be blame for anything other than running stock. Even if you only root the device and crash it, you can't blame em for this.
Click to expand...
Click to collapse
It was stock rom. I have only rooted and unlocked it, then i wiped it in cwm, nothing else...

niyazidk said:
It was stock rom. I have only rooted and unlocked it, then i wiped it in cwm, nothing else...
Click to expand...
Click to collapse
Rooted and unlocked with a custom bootloader is not stock. You can have a lot of issue with the wrong bootloader. I once did!
Get it back to stock with the KDZ, you'll know if it's a software issue and if it's related to the custom/unlocking/rooting.

Wrong post sorrry.

nch26 said:
Man with all respect you even know if LG will update this phone.
Click to expand...
Click to collapse
What are you saying, is this a question? Who are you replying to?
This topic is not about update, it's about a bugus kernel. Don't mix things up please!

Finally... I figured it out. I have used the old KDZ updater and after tons of try, i did it. But again as i said no more LG... Maybe we should stick with a phone that has a sd slot. : )
A sum of what i did
1- find a stock rom from http://lg-phone-firmware.com/index.php?id_mod=20
2-Get old KDZ updater i have uploded and remove zip from the name
3-In KDZ updater choose 3GQCT and i think it was cs emergency, i am not sure and choose your kdz file and finally launch software update
4-Connect your phone in download mode to pc. KDZ updater has kicked the phone out of download mode and couldnt find the phone. Just try again and connect phone again while it extracts kdz file. You could also try different usb ports as i did.
Thats all.

niyazidk said:
Finally... I figured it out. I have used the old KDZ updater and after tons of try, i did it. But again as i said no more LG... Maybe we should stick with a phone that has a sd slot. : )
A sum of what i did
1- find a stock rom from http://lg-phone-firmware.com/index.php?id_mod=20
2-Get old KDZ updater i have uploded and remove zip from the name
3-In KDZ updater choose 3GQCT and i think it was cs emergency, i am not sure and choose your kdz file and finally launch software update
4-Connect your phone in download mode to pc. KDZ updater has kicked the phone out of download mode and couldnt find the phone. Just try again and connect phone again while it extracts kdz file. You could also try different usb ports as i did.
Thats all.
Click to expand...
Click to collapse
That's pretty much what the link I've posted said to do!
Anyway, good to know you're ok now.
If you want to unlock, use this:
Root:
http://forum.xda-developers.com/showthread.php?p=38886073#post38886073
To unlock after, install Project FreeGee from google play
Then CWM/TWRP from FreeGee

t1mman said:
That's pretty much what the link I've posted said to do!
Anyway, good to know you're ok now.
If you want to unlock, use this:
Root:
http://forum.xda-developers.com/showthread.php?p=38886073#post38886073
To unlock after, install Project FreeGee from google play
Then CWM/TWRP from FreeGee
Click to expand...
Click to collapse
That was what i did last time. But i think my problem was cwm. Because i wiped device in cwm and i had that problem. I have choosen cwm instead of twrp because it was preffered. What do you think? Should i choose twrp or cwm? Do you have experience with them?

niyazidk said:
That was what i did last time. But i think my problem was cwm. Because i wiped device in cwm and i had that problem. I have choosen cwm instead of twrp because it was preffered. What do you think? Should i choose twrp or cwm? Do you have experience with them?
Click to expand...
Click to collapse
CWM has issues with the latest Cyanogen, TWRP is apparently required so I installed the latter. I've been running "stock rom" for a month tought, I can't realy tell about Custom roms.

t1mman said:
CWM has issues with the latest Cyanogen, TWRP is apparently required so I installed the latter. I've been running "stock rom" for a month tought, I can't realy tell about Custom roms.
Click to expand...
Click to collapse
Ok so i try also twrp...
Thank you for your time.

niyazidk said:
I like lg's hardware. I had optimus 3d and now have optimus g. Both has great hardware.
I have flashed custom roms since windows mobile days, so i should have a little experience..!
But you can never be sure to flash safely especially with Lg. You can loose your imei, baseband...etc
And now i have kernel crash on my loved optimus g... A demogod kernel crash. I can boot in cwm but cant restore system. It restore boot and then system restoring fails. I can also boot in android and after a few seconds it crashes. So it doesnt stay long enough to be fx recognized by pc to save it. Pc doesnt recognize it even in download mode. I will also try with another pc.
You dont have such problems with htc or samsung. The problems with these phones arent so complicated like lg.
SO NEVER AN LG AGAIN...
Click to expand...
Click to collapse
Can't blame on lg. I see a ip***e fired, my s2 baseband fu***d, all companies made there best. Maybe it's about damaged/dropped phone.

aren't threads/guides on rooting, flashing custom roms/kernels had warned you about a potential bricked device? sometimes it pays to understand/accept what we read.

Dont blame our root or unlocking methods. One day after unlock and root, my battery drain in 4 hours. I even cant flash custom android 4.2.2 ROM.Even twrp doesnt work, appears a black screen. One day i uninstalled NFC apk. And thats it. Everything go back to normal. I dont know why Android 4.2 ROMS dont work on my device in that time, but the battery problem was NFC.
Just sharing an experience.

atifsh said:
yup, why not when you mess up the phone and cant do any thing about it, lets rock the blame game..
lu6200 to su640 to lte2 to optimus g to optimus g pro.... never had any issues and never will buy anything else.
Click to expand...
Click to collapse
Truly. Nitro to LTE2 to OG Pro to G2 :victory: :highfive:

*Help* I unrooted on a rom and now I can't root my phone.

Device: LG G3
Rom: [AOSP EXTENDED V3.0] [LG G3 - D855] [OFFICIAL] [NOUGAT R9] [by MARCHETTO96]
Hey again,
So i'm running this rom right and I was reinstalling my apps onto my phone and one app I need to log into but it noticed it was running root (Snapchat). So I followed someones advice on here on XDA to fully unroot the device and I did that I fully unrooted the app from the phone and then here comes the worst part that I realized this will kick me out of recovery and i wont be able to get back in because I need to get on to recovery to re install superSU back on. So im stranded on nougat 7.1 and dont have access to root at all except for root access on developer settings but that doesn't nothing at all I re installed the app on play store but its telling me the phone is unrooted of course.
Anyone can help me out here. It would be greatly appreciated .
P.S I did get snapchat working after that method kinda did work/backfire at the same time.

Do you have nandroid backup? If yes, flash that. It will be all well.
Other hard method is to downgrade to KitKat and then root and then TWRP. ?

I do not have a back up for this ROM but I have other back ups on my phone that still works. I can't do it as well cause I neeed root to l get it to work.

HunterTubeHD said:
I do not have a back up for this ROM but I have other back ups on my phone that still works. I can't do it as well cause I neeed root to l get it to work.
Click to expand...
Click to collapse
Backups don't need root. They need TWRP to be flashed.

Jahanzaibawan said:
Backups don't need root. They need TWRP to be flashed.
Click to expand...
Click to collapse
Yeah thats the only thing I can't get access to TWRP. When I fully unrooted It would not let me in my recovery at all just bootloops until i take the battery out then it reboots to the system fine.

Just going to ask a hopefully obvious question that I know doesn't help but I'm intrigued... Why didn't you just unroot using the supersu app?

pffcouk said:
Just going to ask a hopefully obvious question that I know doesn't help but I'm intrigued... Why didn't you just unroot using the supersu app?
Click to expand...
Click to collapse
I did do that....now my main problem is I don't have root anymore and I can't get access to my recovery and plus I'm running an Nougat rom so I need to find a way to re-root my phone again to get it all back.

The supersu app doesn't delete the recovery on your phone so something had to have gone wrong. Either way the best bet for you I would imagine anyway would be to follow a guide to install recovery - it's been that long since I had to do it I can't be of much help but I'm willing to look into the easiest options for you if you want. There will be a way, pretty much guaranteed

pffcouk said:
The supersu app doesn't delete the recovery on your phone so something had to have gone wrong. Either way the best bet for you I would imagine anyway would be to follow a guide to install recovery - it's been that long since I had to do it I can't be of much help but I'm willing to look into the easiest options for you if you want. There will be a way, pretty much guaranteed
Click to expand...
Click to collapse
I know that my recovery is still there but It wont allow me on there for some reason. But im thinking that If I factory reset the phone it would PROBABLY fix the problem but theres one risk that it could probably happen and im guessing that it will go straight into a bootloop. If you want to help me It would be great

I'll research for you mate!

Did you modify your ro.product.model in build.prop file and when supersu app asks if you want to flash stock recovery you pressed yes?
For example if you have enabled google assistant by changing your ro.product.model to pixel or pixel xl and after that unrooted and pressed yes to restore stock recovery (to get OTA to work), supersu flashes pixel recovery and thats why you can't get to recovey again.
There are ways to get your phone back to factory clean and start over.

Okay I have spent a whole day figuring out this problem but i finally managed to fix it.
So I went onto download mode
opened up LG Flash Tool 2014
Flashed an LG KDZ File managed to work after the 2nd time
10 or 15 mins later it finally worked
LG started to boot up and started loading in the apps
THEN
I rooted the phone again using this forum: https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268
Then I finally got back onto the glorious TWRP rom.
I re-installed the ASOP rom again.

I'd Like to thank Juhkimo, Jahanzaibawan and pffcouk for helping me out. You guys got my phone back to what it was before so thanks a ton

HunterTubeHD said:
I'd Like to thank Juhkimo, Jahanzaibawan and pffcouk for helping me out. You guys got my phone back to what it was before so thanks a ton
Click to expand...
Click to collapse
Really good to hear that :highfive:

Having trouble with the service.

My problem started some months ago, when a friend tried to root my phone, he told me that he rooted it but every app that checks for root told me that it wasn't rooted and i couldn't use apps that needed root also, the downside to all this is that i couldn't use apps that do not allow root, like the banking app, or Pokemon Go, but i used the phone like that for some months until last week when i decided to try and fix it. I thought that if i flash a stock firmware everything should be fine and the phone should be as new. On the phone, it says that the model is SM-N910F(behind the battery), in the settings it also said SM-N910F, so i tried flashing a rom for this model at first and it kept failing with me not knowing why. After trying different thing and googleing some time, i finally noticed that in "Fast Download", it says that the phone's model is SM-N910P, so i started searching about this, i didn;t understand why there were 2 different models on my phone, then i found out about searching my IMEI on imei.info, so i tried it and here it was SM-N910C, i had no idea what all this meant, but at this time i already got stuck into bootloop. Eventually, i found this thread: https://forum.xda-developers.com/note-4/help/help-sm-n910f-sm-n910p-bootloader-t3299285 and did what cam_bob22 said, it worked, i finally flashed the firmware on my phone and it worked, i could use the bank app, pokemon go, everything was fine except the fact that i couldn't select or change my mobile operator, when going to mobile networks, the mobile operators options was greyed out and couldn't be pressed(i want to mention that i did have service and that data worked but the internet would work only in roaming and i couldn't get 4G). So i tried updating the software from 5.1.1 to 6.0.1 like it was said in the instructions and hopping that this update would fix the issue, but unfortunately for me after the update i somehow lost service completely, the signal sign was in the shape of a triangle with no bars, and the mobile operators setting was exactly as before.
So far i tried going back to 5.1.1 but besides the Hands Free activation that i can't make to go away, i still can't use the mobile operators setting and my data only works with roaming activated and doesn't get 4g. One thing that i forgot to mention is that the IMEI with the 5.1.1 firmware was of a samasung Galaxy S5 not a note 4, i checked it on imei.info.
I was wondering if there is any way for me to go back to the OS i had before my friend tried to root my phone, when it said in the settings that it was SM-N910F and everything worked as it should have.
Thank you for reading and i really hope someone can help me.

@robert11arad
There is no way to go back unless he made a backup. Which is why you should always do this before you flash anything.
I'm not sure if this will help but you could try flashing a international custom Rom after you have correct firmware. But if your phone is a Sprint version, you'll have to use a special data fix and kernel.
What firmware did you end up using to flash? Was it Sprint? If so, and you use gsm service, try flashing my Gsm stock Rom for Sprint phones. It's in post 2.
https://forum.xda-developers.com/no...t/05-15-17-debloated-deodexed-rooted-t3607029
You'll first need to be on current marshmallow firmware. So flash firmware with Odin first, then install Twrp with Odin. Then install Rom with Twrp.

aaron74 said:
@robert11arad
There is no way to go back unless he made a backup. Which is why you should always do this before you flash anything.
I'm not sure if this will help but you could try flashing a international custom Rom after you have correct firmware. But if your phone is a Sprint version, you'll have to use a special data fix and kernel.
What firmware did you end up using to flash? Was it Sprint? If so, and you use gsm service, try flashing my Gsm stock Rom for Sprint phones. It's in post 2.
https://forum.xda-developers.com/no...t/05-15-17-debloated-deodexed-rooted-t3607029
You'll first need to be on current marshmallow firmware. So flash firmware with Odin first, then install Twrp with Odin. Then install Rom with Twrp.
Click to expand...
Click to collapse
Thank you for the reply, i wanted to say that with the Sprint firmware i used, after doing all the updates it unlocked the mobile operators option, but it couldn't find any.

robert11arad said:
Thank you for the reply, i wanted to say that with the Sprint firmware i used, after doing all the updates it unlocked the mobile operators option, but it couldn't find any.
Click to expand...
Click to collapse
Oh ok. So do you have service?

aaron74 said:
Oh ok. So do you have service?
Click to expand...
Click to collapse
No, the network operators is unlocked but there's still no service, when i try scanning for an operator it just stops with no message, and nothing happens.
I forgot to mention this, but before all this happened, I made a back-up of the phone with smart switch, is it possible to get back to how it was using that? And another thing is that when using the backup, it only restores music and photos, no contacts, no apps.(From what i've noticed so far)

robert11arad said:
No, the network operators is unlocked but there's still no service, when i try scanning for an operator it just stops with no message, and nothing happens.
I forgot to mention this, but before all this happened, I made a back-up of the phone with smart switch, is it possible to get back to how it was using that? And another thing is that when using the backup, it only restores music and photos, no contacts, no apps.(From what i've noticed so far)
Click to expand...
Click to collapse
You would have needed a system backup with twrp.
What country you in? What network you on? What firmware you on?

aaron74 said:
You would have needed a system backup with twrp.
What country you in? What network you on? What firmware you on?
Click to expand...
Click to collapse
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5

robert11arad said:
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5
Click to expand...
Click to collapse
Ok. About the best advice i can give is, because your on pure Sprint Rom, something is messing up with csc or something.
All i can suggest, is maybe try updating to QC1 with Odin and then try flashing my gsm Rom. Which is essentially just a tmobile rom.
And if that don't give you the function you you need. Then maybe try an international Rom.
It's hard to say what the last person did to the phone.

robert11arad said:
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5
Click to expand...
Click to collapse
Also. You stated your phone first showed as a 910f. So maybe flashing a international F rom, will provide the correct csc settings for your phone to work. Only problem your gonna have, is because it's Sprint hardware, you'll have to pair the Rom with a kernel that'll work and some lib files for data.
I can help you by putting together some files to flash. But the main question would be, Do you want a stock note 4 Rom?
Also before any of this happened, do you know what firmware you were on? Marshmallow? Lollipop?

aaron74 said:
Also. You stated your phone first showed as a 910f. So maybe flashing a international F rom, will provide the correct csc settings for your phone to work. Only problem your gonna have, is because it's Sprint hardware, you'll have to pair the Rom with a kernel that'll work and some lib files for data.
I can help you by putting together some files to flash. But the main question would be, Do you want a stock note 4 Rom?
Also before any of this happened, do you know what firmware you were on? Marshmallow? Lollipop?
Click to expand...
Click to collapse
I would really appreciate if you helped me put the files together cause i have no idea how any of this works, i'm new. But i wanted to ask, is there any chance for thia to brick my phone?
When it had sm-n910f on it i couldn't update it after 5.1.1, when i pressed update it wouldn't do anything.
And yes, if possible i would like it to be a stock firmware, but if it is not possible i don't mind using something else as long as it works properly.
Thank you for all your help, i don't know what i would do otherwise.

robert11arad said:
I would really appreciate if you helped me put the files together cause i have no idea how any of this works, i'm new. But i wanted to ask, is there any chance for thia to brick my phone?
When it had sm-n910f on it i couldn't update it after 5.1.1, when i pressed update it wouldn't do anything.
And yes, if possible i would like it to be a stock firmware, but if it is not possible i don't mind using something else as long as it works properly.
Thank you for all your help, i don't know what i would do otherwise.
Click to expand...
Click to collapse
Well, first, let me state,about bricking device. I have to state that it's not impossible to brick. But after hundreds of flashes never had problem. These devices are hard to brick. What hard bricks a device is messing with boot loader and partitions that shouldn't be messed with, like trying to unlock lte bands. But just flashing roms is fine unless you flash a Rom not for your phone and it over writes wrong partition.
All snap Dragon note 4s have the same layout so all you need is correct kernel, csc, and some ril lib files to get data working.
Now, mine main worry is that the phone is still unlocked,because I don't know what possible changes were made to it.
But with all that being said,I'll move on. With another post.
---------- Post added at 05:52 PM ---------- Previous post was at 05:13 PM ----------
@robert11arad
Before we go too deep into this and upgrade and stuff. I'd like to just test a custom Rom on your phone and see what works.
So what firmware are you on right now?
5.01, 5.1.1, or 6.0.1?
I'm gonna take a guess and move on. You last stated you were on OG5 which it's 5.1.1. So if that's true, let's try the following.
First I'm gonna assume you already used Odin to flash that firmware. So now we need to flash Twrp. So download this on pc https://eu.dl.twrp.me/trlte/twrp-3.1.1-0-trlte.img.tar
1 . Put phone in download mode. Open Odin and plug in phone.
2. In Odin options make sure everything is unticked except Reset Flash Counter.
3. Now click on AP and select the Twrp file.
4. Flash it. Let it flash until it states it's completed. Once done. Unplug phone. Pull out battery. Put back in and boot to recovery by holding power+home+vol.up
5. Now you should have Twrp. Just reboot phone so we can continue to next post.

PM sent

@robert11arad
Ok, here you go. If your where we left off, you should be on stock QC1 and have Twrp installed.
Just download this file, boot into recovery, and install. This file will delete dalvick/cache, so phone will take a few minutes to boot up.
I actually recommend before flashing, you do a factory reset in recovery then install.
Anyhow here you go. Let me know if it fixes what your looking for. If not, my only others option is to install a custom n910f Rom. I'll gladly walk you through if need be. But try this first.

aaron74 said:
@robert11arad
Ok, here you go. If your where we left off, you should be on stock QC1 and have Twrp installed.
Just download this file, boot into recovery, and install. This file will delete dalvick/cache, so phone will take a few minutes to boot up.
I actually recommend before flashing, you do a factory reset in recovery then install.
Anyhow here you go. Let me know if it fixes what your looking for. If not, my only others option is to install a custom n910f Rom. I'll gladly walk you through if need be. But try this first.
Click to expand...
Click to collapse
Alright so i just tried it and when starting my phone, i can't even set it up because i keep getting a message that com.android.phone has stopped. After about half an hour of trying to start it, i finally managed to get to setting and to app manager, there i looked for com.android.phone and it was nowhere to be found. Apart from this i noticed a N with some signal bars where my phone signal should've been and i didn;t get the hands free activation anymore, but that's all...

robert11arad said:
Alright so i just tried it and when starting my phone, i can't even set it up because i keep getting a message that com.android.phone has stopped. After about half an hour of trying to start it, i finally managed to get to setting and to app manager, there i looked for com.android.phone and it was nowhere to be found. Apart from this i noticed a N with some signal bars where my phone signal should've been and i didn;t get the hands free activation anymore, but that's all...
Click to expand...
Click to collapse
Ok. I must have forgot something in csc. Sorry. I'll get back with you.

N910P - Please Help - Tried to root and failed No Bootloader found?

I'm really hoping someone can bail me out here before I...
I have made a mess of my new (to me) Note 4. I bought it as an Unlocked GSM. It arrived booting with a Sprint screen. I have Safelink BYOP service. When I switched from my Note2 to Note4, yesterday, an ATnT sim card was used to activate it with Tracfone. Everything seemed to work EXCEPT for MMS - I could not send nor receive pictures. I read -what I thought was- clear instructions here on the forum, I started downloading and attempting to root my phone, hoping that would solve the problem, since tech support had no answers.
I followed the instructions in this post - https://forum.xda-developers.com/note-4-sprint/help/rooting-sprint-note-4-pj1-t3495306 . Now the phone will only boot to download mode, or I can use the up volume button to get to the program to install, restore, etc. I have tried several times - with a couple of different .tar files. This last attempt - I tried to restore it - that also failed. My old eyes can not really see the tiny text but I did see in Odin3 that 1) No MDS found 2) Systemless mode Boot img support required 3) Boot Image Patcher Failed. When I attempt to install the SuperSU, from the thread, it gives me similar errors 1) NO MDS file found 2) (under Boot Image patcher it says FAILURE / Abort after extracting Ramdisk.
If anyone could help me out, I would be most grateful.

JadenEllis said:
I'm really hoping someone can bail me out here before I...
Click to expand...
Click to collapse
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!

Once you get phone back on stock. I'll show how to root!

Thank You
Thank you so much for the reply. I have downloaded the files you put in my post. I will attempt to do these things now, but I have a question. I stayed up fighting with the phone all night. I probably did some things I shouldn't have? I realized that I was getting stupid and quit, but I did (maybe) put some other stuff on the phone that night. Should I use the Clean or wipe function in TWRP before I do anything else???
Yes, I can boot to downloader or to TWRP. The phone (on its own) is now stuck trying to load with the Note 4 splash screen - but I can boot to either with the vol +/- buttons.

SamFirm did not work. It said Unable to fetch... please check data or enter manually.
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

First - THANK YOU all for the assistance.
Yesterday, none of the suggestions were working, but I kept at it. I was finally able to install the most current Stock tar that I could find. This phone had updated to the most current version available for the phone - it had Marshmallow 6.01. NOW, the red and yellow tamper errors appear to be gone from the Note4 splash screen - BUT, it boots to Sprint Activation so it won't fully load to OS. I read a post about removing the Sprint Hands Free Activation, but it gives two ways of doing so. 1 requires having a rooted phone (I am assuming it is not rooted now?) and the other uses ADN Connect, and I am not sure what that is.
I'm not really sure what to do from here? Any assistance appreciated. Can I start from step 1 of the original post to install SuperSU now?
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

Well, the sun is about to come up - again - but I think I got it! This has been a learning experience to say the least. I wasn't really planning a crash course in Android, but thank you to all who responded. And to :Samep too!

I think I get it
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.

JadenEllis said:
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
Click to expand...
Click to collapse
Sorry bud. I'm so busy. Haven't been online since i message you. Glad you got it.

Rookie messed up..
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.

meBn360 said:
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
Click to expand...
Click to collapse
Sorry I don't get on here much lately. Just seen your post.
Without knowing exactly what you did. I'd say you lost your unlock. If you had an unlocked sprint phone. And tried nougat. I believe i remember that upgrading to nougat was messing up people's EFS partition. And that's where the unlock happens. Did you make a backup?
I always tell everyone, the most important thing you can do is have a full working backup of every partition.
Hope that sheds some light

[GUIDE] How to correct a wrong shown build number from settings menu

Yesterday i was upgrading my phone from B368 to B369, and wronging by impatience, i decided to shut down while my phone was apparently blocked on the NAG screen (your phone has been unlocked and can't be trusted screen at startup); in truth, it wasn't blocked but it was just applying updates during reboot and he was tooking some more time than usual... The result? My model number changed from BLN-L21 to generic_a15, and so apps like camera was keeping crashing and became not usable.
After had restored a TWRP backup made before updating, and so on B368 build, i ended up with BLN-L21C432B369 as build number, but without having the latest security patch and latest improvements. In poor words, the B369 build was shown even if i was on B368 at all, and so system update wasn't detecting any other updates since that i was apparently on the latest build.
[DISCLAIMER: don't point your finger on me if you end up with your phone exploding, emitting toxic spores or radiations, please. I'm just putting this simple guide here as a way to possibly solve your issue, but i can't know if it'll works on EVERY different model, variant or kind of issue; in mine case it worked like a charm, but BE CAREFUL. I'm not responsable for anything]
What i did for fix this issue was very, very simple, much simpler than what i thought to face; i just started combing here and there in the various root folders thanks to a root explorer (i used MiX, for example) containing the various local.prop and build.prop files scattered around the system folders, until i found the right one to tweak with. The path to follow is very simple: you just need to browse to
Code:
root/version/special cust/BLN-L21/hw/eu/prop/local.prop
(note that the path will obviously change if you own a BLN-L22, a BLL-L22, ecc. but the road will be always the same - you'll find other folders name after special cust, BLL-L22 other than BLN-L21, china instead of eu for example, but often it's always straight to the last folder that finally contains the local.prop file)
and once there, with the help of a text editor, correct all the errors that you'll find mismatching with your actual build number. The voices that i had to correct are circled in orange in the picture that i attached here below, (note: the picture shows voices already fixed) and there was four of them to adjust;
Code:
ro.build.display.id=BLN-L21C432[B][COLOR="Red"]B369[/COLOR][/B]
ro.build.version.incremental=C432[B][COLOR="red"]B369[/COLOR][/B]
ro.build.description=BLN-L21 -user 7.0 HONORBLN-L21 C432[B][COLOR="red"]B369[/COLOR][/B] release-keys
ro.build.fingerprint=HONOR/BLN-L21/HWBLN-H:7.0/HONORBLN-L21/C432[B][COLOR="red"]B369[/COLOR][/B]:user/release-keys
since that in this case i was on B368 other than B369, as shown by phone info in settings menu, i just tried to modify that number with an 8 instead of a 9, gave the phone a reboot and... It's done!
**Method Update!**
 @BakedOnSomeSour pointed out a way to definitely correct the build number, permanently and safer than my method!
To do this, flash the version.img matching your firmware build, an image that you can extract from the UPDATE.APP of each update.zip package through TWRP (flash the file as image of course, by selecting the dedicated option in TWRP menu). In this way, the build number will be definitely fixed!
Thanks to BakedOnSomeSour for finding a faster and more efficient method.​
Be aware, and backup before doing this or everything you're dubious about.
Cheers

nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.

shashank1320 said:
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
Click to expand...
Click to collapse
Thanks mate. I discovered how to do by myself while trying to get rid of this error, and so i thought to share with others who could face this in future.

nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15

sreekantt said:
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
Click to expand...
Click to collapse
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.

RedSkull23 said:
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
Click to expand...
Click to collapse
yeah same with me - don't wanna delay other things as of now... :highfive:

I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?

BakedOnSomeSour said:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
Click to expand...
Click to collapse
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)

RedSkull23 said:
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
Click to expand...
Click to collapse
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.

BakedOnSomeSour said:
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
Click to expand...
Click to collapse
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.

RedSkull23 said:
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
Click to expand...
Click to collapse
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.

BakedOnSomeSour said:
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
Click to expand...
Click to collapse
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?

RedSkull23 said:
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
Click to expand...
Click to collapse
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.

BakedOnSomeSour said:
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
Click to expand...
Click to collapse
Yeah got that, thanks. I'll write here a feedback as i'll be able to do this

@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited

RedSkull23 said:
@BakedOnSomeSour
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Click to expand...
Click to collapse
New mess with Huawei every day. They keep stopping us and we keep trying them

RedSkull23 said:
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
Click to expand...
Click to collapse
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help

shashank1320 said:
New mess with Huawei every day. They keep stopping us and we keep trying them
Click to expand...
Click to collapse
What a bore is this, man?! :laugh: never admitting a loose against them!
BakedOnSomeSour said:
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
Click to expand...
Click to collapse
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)

RedSkull23 said:
What a bore is this, man?! :laugh: never admitting a loose against them!
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
Click to expand...
Click to collapse
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:

shashank1320 said:
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
Click to expand...
Click to collapse
Thanks pal, wish you the same i can say that until I'll have an Honor device, that will be almost at day order