Develop Bugs

Bought an FRP locked phone, need a serial number

I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4

Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals

iBowToAndroid said:
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
Click to expand...
Click to collapse
I have a similar issue, could this be fixed with a Z3X Box?

you could try this method . . .
https://www.youtube.com/watch?v=ggRhkme9FC0
if for any reason didn't work try this one
https://www.youtube.com/watch?v=KRUp09bXnDA

JeffB81 said:
I have a similar issue, could this be fixed with a Z3X Box?
Click to expand...
Click to collapse
Yes it can be, do you have one?

discomaniac said:
Yes it can be, do you have one?
Click to expand...
Click to collapse
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you

JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
You took off FRP lock with software?

JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
Confirm?

vazersecurity said:
Confirm?
Click to expand...
Click to collapse
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock

crazynapkinman said:
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
Click to expand...
Click to collapse
Incorrect. FRP is held in a partition that is not touched during a firmware flash

vazersecurity said:
Confirm?
Click to expand...
Click to collapse
iBowToAndroid said:
Incorrect. FRP is held in a partition that is not touched during a firmware flash
Click to expand...
Click to collapse
Then what about this Cl3? Are there steps after flashing the firmware?

crazynapkinman said:
Then what about this Cl3? Are there steps after flashing the firmware?
Click to expand...
Click to collapse
Flashing firmware can't fix an FRP lock - period.
If you want to know what that poster meant by his message, I suggest you ask him directly

Samsung phones can be frp unlocked by flashing firmware
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.

Bullshipcaptcha said:
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Click to expand...
Click to collapse
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.

That doesn't matter when the phone no longer has a persistent partition.
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.

Bullshipcaptcha said:
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Click to expand...
Click to collapse
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like system, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.

Your going to need to go against the grain her a moment . Business or no business
iBowToAndroid said:
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like tem, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Click to expand...
Click to collapse
I'm telling you. I'm not debating the facts. Im telling you what I did. Kinda like I did today with a Moto e4 play. I bypassed frp with flashing stock rom through Odin and then custom rom on the Samsung J7. Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked . I don't have a business in the phones field but I am a business man and sittin on 12 frp locked phones gets tire some. Thant goodness for broken digitizers and displays or I'd still have a bunch more of them. I wont dipute that you know what your doing because likely you do more so than I; we can can probably be certain. I'm just going to tell you the 100 percent fact. Upset wife as my motivating factor I successfully unlocked and rooted a j7 by flashing stock rom into it with Odin then custom reccovery then root then custom rom. The custom recovery I used by accident was for a different brand Jay 7 so mysecond time around I tried the "right" recovery and bricked it. Then again and again and again until Knox was tripped and that's when finally I took bl,ap cp, csc and flashed them in dl mode successfully from there I had Rob from simple cell unlock ( Thanks Rob your the best) remotely unlock the jay7 from T-Mobile after which I flashed the "wrong" proper twrp file giving me the ability to install custom note 8 dna rom into the system. Took two tries, first try I flashed no encrypt no verity but it custom rom frp locked. So second time I made sure I install the developer tools package with OEM unlock switch not able to be turned off then no encrypt no verity. It was a very long process since especially since it was only my second successful full root. Then vallet. Man becomes praised by wife. Man feels empowered man tears apart more phones makes mess, MAN HAPPY! WIFE HAPPY! LOL okay sorry about that part.
---------- Post added at 04:18 PM ---------- Previous post was at 04:06 PM ----------
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
None the less each developer has a different approach that being said you frp unlocking phones? I have a Samsung s8 Moto e5 five LGs one zte n835 a couple of alcatels and a few more I couple reassemble real quick If I knew some one who had the abilitby to unlock especially if said amazing developer was teaching El padawan young Como. Yo tango mucho programs, apps and software. Just need the knowledge.

Bullshipcaptcha said:
Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked
Click to expand...
Click to collapse
Thinking you can flash TWRP on a locked bootloader device shows me exactly what your knowledge level is when it comes to all of this. Future discussion would be futile, and no more responses from me will be had. I do wish you luck with your devices though

How frustrating you are.
Your business need some schooling it sounds like. Your business can't be doing good. Go ahead and Google the Moto e4 unlock method. You will see. You have to try before you say it won't work.

discomaniac said:
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Click to expand...
Click to collapse
I just removed the frp lock on my s6 using a combination firmware (found here-https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=7410) which completely erased all partions and allowed me to access the settings menu to enable the OEM unlock setting. They are two different firmware there. I used the second one and it worked like a charm. Hope this helps

Constant crashing

Hi all,
My phone keeps crashing and rebooting. Every time it comes back, it needs to resign on to wifi (retype in WPA), downloads a file calle "how-to" (which I can't find), and have to resign into Google. By the time it accomplishes all this, it crashes and restarts the whole shabang again. Tried recovery mode and clearing, no difference.

It might be worth mentioning it boots into extreme power saving mode too.

Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?

redpoint73 said:
Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?
Click to expand...
Click to collapse
It is stock. Tried to root it but it didn't take. Don't know which version as it is stuck in a loop currently. It seems to me this is a hardware problem though.

carljames0603 said:
It is stock. Tried to root it but it didn't take.
Click to expand...
Click to collapse
Need more details on that. How did you try to root, what exact steps did you perform, where did you get stuck and why, etc.
Always provide as many details as possible when asking for help and answering our questions.
carljames0603 said:
Don't know which version as it is stuck in a loop currently.
Click to expand...
Click to collapse
If its stuck in a loop (rebooting) then simply hold volume down, and don't let go. The next time it reboots, it will go to bootloader (then you can let go of vol down).
From there, tell us what OS number it says on the bootloader screen, near the top.
carljames0603 said:
It seems to me this is a hardware problem though.
Click to expand...
Click to collapse
What makes you think that? You haven't provided any details or evidence that would support the statement.
Its possible its a hardware issue. But based on what little you've said, its perfectly possible its a software issue. So be optimistic, unless you have specific evidence to think otherwise.

When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process. Pain in the ass.
The OS is 3.28.605.4

carljames0603 said:
When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process.
Click to expand...
Click to collapse
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?

redpoint73 said:
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?
Click to expand...
Click to collapse
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked, and it stays there until I push it to reboot.

carljames0603 said:
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked.
Click to expand...
Click to collapse
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
carljames0603 said:
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Click to expand...
Click to collapse
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.

redpoint73 said:
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.
Click to expand...
Click to collapse
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.

carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
did you read the post you quoted ?
redpoint73 said clearly what you need and where to find
you used a different RUU and it will not accepted by your device ( in red above )

carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app.
Click to expand...
Click to collapse
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
carljames0603 said:
(RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).

redpoint73 said:
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).
Click to expand...
Click to collapse
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.

carljames0603 said:
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.
Click to expand...
Click to collapse
That's unfortunate, as your issue is probably completely fixable. All you need to do is follow the instructions already provided. Myself and others have taken our time, at no benefit to ourselves, in order to try to help you and others.
Any critique given by me was not mean to insult or attack, and if you read my post there is nothing in there that constitutes a personal attack or flaming (I even said "please") - while you on the other hand can't claim such a statement to be true. A constructive criticism of your posts is not the same as attacking a person (which you did). The intent was for us to obtain the proper information so that we can better understand what you did, in order to help; and hopefully to improve the quality of your subsequent posts (but that didn't happen).
You can try to learn from your mistakes and expand your knowledge; or you can complain and continue to be ignorant. Your choice.

I have found a working temp root method for 5.1.1

I found a bootloader unlock method for the Verizon variant of this phone, however after trying it on my phone I was able to get temp root on my AT&T Note 4. I have not tried to unlock the bootloader yet, but I will keep you guys posted.
Here is the link: galaxynote4root/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/2/ (add .com infront of the first root , I can't post links yet)
(Make sure that on step 9 and up to change the file name in the command to n4-2 instead of n4-fix)
(Download everything except the Verizon stuff)
Final edit: This method only works for root, the bootloader can't be unlocked for AT&T because there was never a developer edition released for it.
Note: The root is extremely buggy and unstable, so it is not that usable. Hopefully someone else can make a root better for this device.

How did the temp root go? Doesn't it reboot after a while and then lose the root?

boofman said:
How did the temp root go? Doesn't it reboot after a while and then lose the root?
Click to expand...
Click to collapse
It is very unstable and slow but it works, I'm probably going to install a different rom if I can unlock the bootloader.

bobshmo said:
It is very unstable and slow but it works, I'm probably going to install a different rom if I can unlock the bootloader.
Click to expand...
Click to collapse
Great going buddy!
How long has it been running with root? Does it survive a reboot?
I do hope you can unlock the bootloader, so we csn install custom ROMs and Kernels!

boofman said:
Great going buddy!
How long has it been running with root? Does it survive a reboot?
I do hope you can unlock the bootloader, so we csn install custom ROMs and Kernels!
Click to expand...
Click to collapse
It does not survive a reboot, however root although it slows the phone down seems to be working fine. I'm still trying to unlock the bootloader.

Nice to see someone take the bold risk. I hope you find success. I think everyone blew this off because this method was for Verizon and it tricks the phone to make it recognized as a Devloper model who come bootloader unlocked. AT&T does not have developer model devices so chances are this method will not unlock 910A bootloaders.

Wish you luck! There's a bounty thread here somewhere..
I saw on the other thread you temp bricked your phone attempting a bootloader unlock..hope you do unlock it without bricking your phone..

Problem with my note 4 please helppp !!
Can I update to an higher version than this ?
Android version 5.0.1
Build number : DONGCHAO.A916
Baseband version : N910FXXU1BOC4
Model SM-N910F

eypohraj said:
Can I update to an higher version than this ?
Android version 5.0.1
Build number : DONGCHAO.A916
Baseband version : N910FXXU1BOC4
Model SM-N910F
Click to expand...
Click to collapse
you are in the wrong thread
Your variant for the Note 4 is the international variant
This thread is for the AT&T Samsung Galaxy Note 4
---------- Post added at 05:39 PM ---------- Previous post was at 05:33 PM ----------
This temp-root doesn't let us access the system partition
This type of root has been recognized by this community for several months and we dismissed as worthless because DM-Verity removes the root after every reboot and I am surprised you guys haven't gotten a brick yet because, on Android 5.1.1, Samsung added a security method where if anyone roots with Kingroot/KingORoot and reboot, you get a message saying that the kernel isn't from AT&T before fully booting up

boofman said:
Wish you luck! There's a bounty thread here somewhere..
I saw on the other thread you temp bricked your phone attempting a bootloader unlock..hope you do unlock it without bricking your phone..
Click to expand...
Click to collapse
I unbricked it, bootloader can't be unlocked though, also I realized that kingoroot works on 5.1.1. It might be due to the file that I pushed for temp root, so now I have temp root on my phone that isn't that unstable.

Thanks for attempting to root though. We might have to look into other exploits to get a stable one. Or maybe there isnt one and its the end of the road on our journey to find it.

Update on how kingroot workin now?

AlexanderDAB said:
you are in the wrong thread
Your variant for the Note 4 is the international variant
This thread is for the AT&T Samsung Galaxy Note 4
---------- Post added at 05:39 PM ---------- Previous post was at 05:33 PM ----------
This temp-root doesn't let us access the system partition
This type of root has been recognized by this community for several months and we dismissed as worthless because DM-Verity removes the root after every reboot and I am surprised you guys haven't gotten a brick yet because, on Android 5.1.1, Samsung added a security method where if anyone roots with Kingroot/KingORoot and reboot, you get a message saying that the kernel isn't from AT&T before fully booting up
Click to expand...
Click to collapse
But the thing is that when i check through the phone info app it shows that i own a n910a variant. So confused

eypohraj said:
But the thing is that when i check through the phone info app it shows that i own a n910a variant. So confused
Click to expand...
Click to collapse
ok, so first of all
Go into Download mode. How to get there?
Turn off your phone entirely, and then when it has been fully turned off, hold down the power button, home button, and volume down button all at once until you get a warning screen. Press the volume down button and it should give you all the information about the phone without the system being all jacked up
Its should say if you have SM-N910F (International Variant) or SM-N910A (AT&T Variant)

Will my H812 have less problems on lollipop?

This phone was given to me with marshmellow and im having the issue of not being able to update google play service among other things. the other issues im having might be the effect of the google play service. i just wanted to know if its worth attempting the downgrade on lollipop

shatheone said:
This phone was given to me with marshmellow and im having the issue of not being able to update google play service among other things. the other issues im having might be the effect of the google play service. i just wanted to know if its worth attempting the downgrade on lollipop
Click to expand...
Click to collapse
Depending on the underlying issue, you may still encounter the Play Services issue on Lollipop as you have on Marshmallow.
First, see if you can work the issue out on your current system.
- Delete cache and Data on Play Services.
- reset app preferences and reset default apps in the menu in the Apps folder in Settings.
- delete your Google account and re-install it.
- use LGUP-NEW to reinstall your Marshmallow rom (H81220). Check out this site for some H812 stock roms:
https://lg-firmwares.com/lg-h812-firmwares/
scroll down to the firmwares list and install the correct stock kdz - carrier and version
You can downgrade to Lollipop (H81210) using LGUP-NEW - frankly I haven't noticed a lot of difference between them but does have the current advantage of being rootable. Some members report better battery life but you will lose some security updates.

sdembiske said:
Depending on the underlying issue, you may still encounter the Play Services issue on Lollipop as you have on Marshmallow.
First, see if you can work the issue out on your current system.
- Delete cache and Data on Play Services.
- reset app preferences and reset default apps in the menu in the Apps folder in Settings.
- delete your Google account and re-install it.
- use LGUP-NEW to reinstall your Marshmallow rom (H81220). Check out this site for some H812 stock roms:
https://lg-firmwares.com/lg-h812-firmwares/
scroll down to the firmwares list and install the correct stock kdz - carrier and version
You can downgrade to Lollipop (H81210) using LGUP-NEW - frankly I haven't noticed a lot of difference between them but does have the current advantage of being rootable. Some members report better battery life but you will lose some security updates.
Click to expand...
Click to collapse
thanks for the reply, i actually did all of those things, including a factory reset. i will try to reinstall using lg up, maybe something in the stock image got corrupted? i learned that even if my phone boot loops, it wont be repaired as the serial number is out of range. so i might hold on to it until theres a good custom available

shatheone said:
thanks for the reply, i actually did all of those things, including a factory reset. i will try to reinstall using lg up, maybe something in the stock image got corrupted? i learned that even if my phone boot loops, it wont be repaired as the serial number is out of range. so i might hold on to it until theres a good custom available
Click to expand...
Click to collapse
Yes, very possible that something got corrupted. Definitely try a re-install of your stock kdz with LGUP-NEW.
If you haven't checked out steadfasterX's bootloader unlock thread, you will have to in order to install any custom rom with some assurance of success:
https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288
You might as well get started now as it won't be long before he publishes. You will have to install his SALT program and create a backup before proceeding to unlock your bootloader preparatory to installing any custom rom:
https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864

sdembiske said:
Yes, very possible that something got corrupted. Definitely try a re-install of your stock kdz with LGUP-NEW.
If you haven't checked out steadfasterX's bootloader unlock thread, you will have to in order to install any custom rom with some assurance of success:
https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288
You might as well get started now as it won't be long before he publishes. You will have to install his SALT program and create a backup before proceeding to unlock your bootloader preparatory to installing any custom rom:
https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864
Click to expand...
Click to collapse
i couldnt get LG up to recognize my phone even after taking out the battery, so ill have to find another usb cable and try that. i see two different kdzs for my software version so ill have to research the correct one. and im not planning one unlocking the bootloader until theres a better way. id sell it before risking a brick

shatheone said:
i couldnt get LG up to recognize my phone even after taking out the battery, so ill have to find another usb cable and try that. i see two different kdzs for my software version so ill have to research the correct one. and im not planning one unlocking the bootloader until theres a better way. id sell it before risking a brick
Click to expand...
Click to collapse
IF, you'd actually read steadfasterX's thread and in particular his latest update (last page on the thread, currently) ... you would realize there had already been a proof of a successful unlock of an H812. I suspect your phone has been screwed up by somebody who didn't know what they were doing in the first place. No one has done more work in this area and had more successes than steadfasterX - good luck for waiting for a better way or getting much trying to sell it - check ebay and see the prices - LOL.

sdembiske said:
IF, you'd actually read steadfasterX's thread and in particular his latest update (last page on the thread, currently) ... you would realize there had already been a proof of a successful unlock of an H812. I suspect your phone has been screwed up by somebody who didn't know what they were doing in the first place. No one has done more work in this area and had more successes than steadfasterX - good luck for waiting for a better way or getting much trying to sell it - check ebay and see the prices - LOL.
Click to expand...
Click to collapse
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so

shatheone said:
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
Click to expand...
Click to collapse
The risk of bricking your phone has been minimized with steadfasterX's process - he has had a couple of successful unlocks of an H812 now and when he publishes it for the public, the risk will be minimized as much as it can be in any unlock case.
With respect to your phone not being recognized by LGUP-NEW. Make sure you have installed the LGMobileDriver_WHQL_Ver_4.2.0 available for download from the US LG site - the Windows driver will give you problems.

sdembiske said:
The risk of bricking your phone has been minimized with steadfasterX's process - he has had a couple of successful unlocks of an H812 now and when he publishes it for the public, the risk will be minimized as much as it can be in any unlock case.
With respect to your phone not being recognized by LGUP-NEW. Make sure you have installed the LGMobileDriver_WHQL_Ver_4.2.0 available for download from the US LG site - the Windows driver will give you problems.
Click to expand...
Click to collapse
well i wouldnt care doing it if there was more rom support, i dont see a point in unlocking at this point. if im missing a benefit of unlocking right now, enlighten me. and thats the driver i already have installed

shatheone said:
well i wouldnt care doing it if there was more rom support, i dont see a point in unlocking at this point. if im missing a benefit of unlocking right now, enlighten me. and thats the driver i already have installed
Click to expand...
Click to collapse
One benefit might be fixing your screwed up phone. Still didn't read the OP I guess as you were advised to in steadfasterX's bootloader unlock thread. Here's an idea ... before making summary judgements with little or no knowledge, perhaps you should check with the member that is sited in the "proof" for the H812 and post your questions there for the Roms he has tried. My understanding was that he was on Lineage for Nougat - the most popular downloaded custom rom for .... are you ready ... the H815/H811 - here's an idea ... why don't you check out ALL the roms that are for the H815/H811 in the Android Development section ... hmm ... really?

sdembiske said:
One benefit might be fixing your screwed up phone. Still didn't read the OP I guess as you were advised to in steadfasterX's bootloader unlock thread. Here's an idea ... before making summary judgements with little or no knowledge, perhaps you should check with the member that is sited in the "proof" for the H812 and post your questions there for the Roms he has tried. My understanding was that he was on Lineage for Nougat - the most popular downloaded custom rom for .... are you ready ... the H815/H811 - here's an idea ... why don't you check out ALL the roms that are for the H815/H811 in the Android Development section ... hmm ... really?
Click to expand...
Click to collapse
if you took 10 seconds, you would see i actually posed in that thread. and all they did was direct me to the OP which says nothing about lineageos working for h812, or that the h815/ or h811 roms work for this variant. all it says is that i can flash nougat based roms. so the thread isnt too helpful, im not sure why you think it is.

shatheone said:
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
Click to expand...
Click to collapse
Hey man, i'm agreeing with you for most of this...
I'm also not going to risk anything until 10 H812 users have successfully unlocked bootloader and flashed a custom rom (one thats intended for h815 or h811) with steadfasterx's method. Maybe you can flash H815 custom roms once the bootloader is unlocked... but just to be safe, let's flash other stock carrier firmwares in the meantime...... in the end no matter what anyone says, its your phone at risk...
Member TheLatios381 and I were asking same question here:https://forum.xda-developers.com/g4...10-q2-2017-t3567402/post75742903#post75742903 because no answer to our question on steadfasterx's thread...

How to root Samsung Galaxy a50 us model

I want to root my a50 soon. Is anyone have us model can root?

From what I understand this phone is very new. Not to mention that it's if you are on a U variant like I am sad there is no root because the bootloader is locked I believe. I was trying to confirm with an expert or someone who knows more than me. My variant is "SM-A505U1"

I just bought this model of phone.
I found this url.
http://androidbiits.com/root-samsung-galaxy-a50-sm-a505u1-easily/
All the steps are not clear to me though yet.
My phone has no oem or boot loader unlock options in the settings.
It also has knox which may complicate things.

donharter said:
I just bought this model of phone.
I found this url.
http://androidbiits.com/root-samsung-galaxy-a50-sm-a505u1-easily/
All the steps are not clear to me though yet.
My phone has no oem or boot loader unlock options in the settings.
It also has knox which may complicate things.
Click to expand...
Click to collapse
My phone was bought unlocked. The device is not a/b and it is system-as-root
Found this bit of information on the forums here:
"
jzy88 Cmon Meow • a year ago
Lol or simply download CSC file from a region different from your country e.g if in US download and flash an european CSC file via odin."
The snapdragon chip is locked only in the US per that post. I seem to remember something about a major security issue found in those chips.
---------- Post added at 05:12 PM ---------- Previous post was at 04:56 PM ----------
donharter said:
My phone was bought unlocked. The device is not a/b and it is system-as-root
Found this bit of information on the forums here:
"
jzy88 Cmon Meow • a year ago
Lol or simply download CSC file from a region different from your country e.g if in US download and flash an european CSC file via odin."
The snapdragon chip is locked only in the US per that post. I seem to remember something about a major security issue found in those chips.
Click to expand...
Click to collapse
I found this url on changing the csc,but it erases the config.
Maybe there is another method that does not do that such as the one mentioned above.
https://www.**********.com/how-to-change-csc-in-samsung-galaxy-phones/

Has anyone successfully flashed any combination firmware? I found this at halabtech, haven't tried to flash it. I thought I seen a bootloader unlock & root for ASH6 firmware I don't think it lets you downgrade though once you have the latest ASK1 firmware. I tried installing this one as well "https://support.halabtech.com/index.php?a=downloads&b=file&id=206734" the only part it failed on was on the boot.img.lz4 everything else flashed successfully. I hope this helps get a start to troubleshooting.
(ASH6 FIRMWARE) haven't tested yet. for A505U1 variant only!
https://support.halabtech.com/index.php?a=downloads&b=file&id=165842

Correction it seems that this is not a snapdragon chip.
I was able to look at the CSC by booting into safe mode and dialing the special number which includes the IMEI #.
They seemed to be all cscs in the US which is why they called it a "US version"
There are files that could be changed with the csc in them , but I don't know what the effect that would have. (maybe bad)
It seems that in the US version there is no OEM unlock option to change in the developer settings.
Also I have not found source code yet for this particular model. (SM-A505U1)

I tried all the root apk out there like kingo-root etc. None of them would root it.

It seems that to change the CSC, you need root access or an unlocked bootloader.
So that method will not work. It seems that unless samsung releases an upgrade that allows you to unlock the bootloader then we will have to wait. That is until
a new exploit is found, and released say via kingo-root etc.

I'm really dying waiting for opportunity to root this phone and make this phone runs so smooth

Here is one URl that provides a schematic for a related phone.
https://www.mobilerdx.com/2020/01/d...0-a505f-service-manual-schematic-diagram.html
Is the boot loader stored inside the processor chip or on another one?

donharter said:
I just bought this model of phone.
I found this url.
http://androidbiits.com/root-samsung-galaxy-a50-sm-a505u1-easily/
All the steps are not clear to me though yet.
My phone has no oem or boot loader unlock options in the settings.
It also has knox which may complicate things.
Click to expand...
Click to collapse
It's just a click bait article.
If you read it carefully, they're assuming there is already a BL unlock for the A505U variants, which doesn't exist at the moment.

I just got notification of an upgrade. I was hoping that the new version would have the oem unlock feature.
I had automatic upgrade turned off nad automatic download on. I was looking at the message, and it automatically scheduled the upgrade without my permission. So I ran the upgrade. It did not add the oem_unlock feature. Maybe next time. Hint! Hint!

donharter said:
I just got notification of an upgrade. I was hoping that the new version would have the oem unlock feature.
I had automatic upgrade turned off nad automatic download on. I was looking at the message, and it automatically scheduled the upgrade without my permission. So I ran the upgrade. It did not add the oem_unlock feature. Maybe next time. Hint! Hint!
Click to expand...
Click to collapse
I got notice of an upgrade today. I had it set to autodownload. It said that after the upgrade was applied that I could not downgrade. Also it said the I had only 3 chances. Last time it upgraded without my permission. So I turned of the autodownload in the settings.
If I knew the new version would enable an unlocking feature, then I, of course, would upgrade.

I found a trick to the no Unlock OEM option that worked so well I didnt believe it the first time. But my bootloader is unlocked and remains unlocked.

It seems that if you specify automatic download it will upgrade it even if you turn that off.
This latest upgrade still does not have the oem unlock feature. I made sure that my automatic download is turned off.
Automatic download also means automatic install. It seems to download the upgrade into a region of the file system which only root can read.
---------- Post added at 04:01 PM ---------- Previous post was at 03:34 PM ----------
juniorD said:
I found a trick to the no Unlock OEM option that worked so well I didnt believe it the first time. But my bootloader is unlocked and remains unlocked.
Click to expand...
Click to collapse
That method did not work for me. I tried it again and it did not work.
"Samsung allows unlocking the bootloader on the international versions of their phones. But on the Samsung Galaxy S8, Samsung Galaxy S9, and Samsung Galaxy Note 8, the ‘OEM unlocking’ option only becomes available after 7 days of activating the device and adding a Samsung or Google account to the device. If you would rather not wait 7 days or if even after 7 days the button is still missing, XDA Senior Member altai1963 has posted instructions about how to fix the missing ‘OEM unlock’ button on "
Perhaps it requires a samsung account. I do not have one on my phone. Incidentally I noticed that all my contacts had been uploaded to google. I would never have knowingly done that. I had to export my contacts to a file, delete all my contacts making sure then that google was not being used, and then import my contacts from the file that I had saved them to. I was worried that I would lose all my contacts, but fortunately that did not happen. It would probably be good to verify that the file exists and notate it location using a file system browser.

donharter said:
It seems that if you specify automatic download it will upgrade it even if you turn that off.
This latest upgrade still does not have the oem unlock feature. I made sure that my automatic download is turned off.
Automatic download also means automatic install. It seems to download the upgrade into a region of the file system which only root can read.
---------- Post added at 04:01 PM ---------- Previous post was at 03:34 PM ----------
That method did not work for me. I tried it again and it did not work.
"Samsung allows unlocking the bootloader on the international versions of their phones. But on the Samsung Galaxy S8, Samsung Galaxy S9, and Samsung Galaxy Note 8, the ‘OEM unlocking’ option only becomes available after 7 days of activating the device and adding a Samsung or Google account to the device. If you would rather not wait 7 days or if even after 7 days the button is still missing, XDA Senior Member altai1963 has posted instructions about how to fix the missing ‘OEM unlock’ button on "
Perhaps it requires a samsung account. I do not have one on my phone. Incidentally I noticed that all my contacts had been uploaded to google. I would never have knowingly done that. I had to export my contacts to a file, delete all my contacts making sure then that google was not being used, and then import my contacts from the file that I had saved them to. I was worried that I would lose all my contacts, but fortunately that did not happen. It would probably be good to verify that the file exists and notate it location using a file system browser.
Click to expand...
Click to collapse
USA variants are not unlockable... Simple

elliwigy said:
USA variants are not unlockable... Simple
Click to expand...
Click to collapse
juniord says that he unlocked his.
Unless I am misunderstanding what you wrote.
If you are saying that it can be unlocked, how do you recommend that it be done?
---------- Post added at 06:05 PM ---------- Previous post was at 05:46 PM ----------
donharter said:
juniord says that he unlocked his.
Unless I am misunderstanding what you wrote.
If you are saying that it can be unlocked, how do you recommend that it be done?
Click to expand...
Click to collapse
I added my samsung account, and tried it. It did not work. I had google and samsung logins provisioned in the phone.
So I guess that I am back waiting for the next exploit which might be a while if bonuses are paid for finding them.

donharter said:
juniord says that he unlocked his.
Unless I am misunderstanding what you wrote.
If you are saying that it can be unlocked, how do you recommend that it be done?
---------- Post added at 06:05 PM ---------- Previous post was at 05:46 PM ----------
I added my samsung account, and tried it. It did not work. I had google and samsung logins provisioned in the phone.
So I guess that I am back waiting for the next exploit which might be a while if bonuses are paid for finding them.
Click to expand...
Click to collapse
He's either bsing you or trolling or has a different variant.. the "trick" they use has been around a while now but only works on models that are actually unlockable.. the USA variants are NOT unlockable from the start so any tricks will not work.. simple as that.. this has been discussed for years and everywhere on xda as well as many discussions about this specific model.. if u want bl unlock purchase an unlockable variant..
Ppl seem to get confused cuz some devices in USA are exynos models so they think they can bl unlock them but this is not the case.. just bcuz a device is exynos doesn't make it unlockable.
Sent from my GM1925 using Tapatalk

elliwigy said:
He's either bsing you or trolling or has a different variant.. the "trick" they use has been around a while now but only works on models that are actually unlockable.. the USA variants are NOT unlockable from the start so any tricks will not work.. simple as that.. this has been discussed for years and everywhere on xda as well as many discussions about this specific model.. if u want bl unlock purchase an unlockable variant..
Sent from my GM1925 using Tapatalk
Click to expand...
Click to collapse
I did some research before I bought it. I also bought it because I could use it on multiple carriers.
The rooted ones that I saw must have been nonUS versions. What a waste of money. I only bought it because I wanted to root it and put a custom rom on it. I did not want to wait for a linux phone and truly 5g phones are coming out now.

samsung A50 security issue
https://www.inputmag.com/tech/googl...anges-to-the-android-kernel-on-the-galaxy-a50