Develop Bugs

Verizon Unlock/Root Survey

I thought I'd put together a basic survey to possibly help others with their Unlocking/rooting questions.
Please only answer if you have successfully completed the steps and have your bootloader unlocked and phone rooted based on information provided by THIS thread. If you don't currently own a Verizon Retail Note 4, respectfully, PLEASE DO NOT post a reply. Thank you.
If you reply, it is assumed that you have completed the process and have successfully turned your Retail Phone into a Developer Phone. If you are still "tinkering" with your phone after the conversion process, feel free to reply and update your reply as needed, to help others.
Before you began:
Your Android Version?
Your build number?
Did you Odin or Flash to get the above Build Number?
What version of KingRoot did you use to Temp Root your phone?
After Converting to Developer Mode/Rooting (Some questions - If Applicable):
SINCE converting, what Android Version/Build Number have you upgraded from/to? Was the upgrade via OTA or Odin?
What confirmed working root apps are you running (other than Root Checker)?
What have you installed onto your phone that requires an unlocked bootloader that are confirmed to be working?
Has this process changed (made better or worse) how your phone reads extended batteries? State which external batteries you have tested, since the root process was made available this week.

Here's my experience.
STARTED WITH:
Your Android Version? 5.0.1
Your build number? BOG5 Safe Upgrade
DOWNGRADED TO (Because I thought I had to which might've been a mistake)
Your Android Version? 4.4.4
Your build number? ANJ5
Flashed via Odin 3.10.7
Results: After starting the HOWTO Guide on converting from Retail to Developer Mode, I got stuck on THIS step, which gave me an error message
Code:
./samsung_unlock_n4-2
Later, I was told that others had reported issues trying to convert from KK. I then took the Safe Upgrade to BP1. Be sure that you are installing the RETAIL version of the ROM, not the Developer Version. You are not there, yet.
Once you are on BP1, download eMMC Brickbug Check from the Play Store. Verify that your CID begins with 15 followed by a bunch of random numbers. Then, follow the steps on the HOWTO Guide on converting your Retail phone to Developer.
After you do this:
Boot to Download Mode (VOLUME DOWN+HOME+POWER) and flash TWRP 2.8.5 recovery via Odin
If you haven't, already, get your MicroSD card, plug it into your computer and load SuperUser and the kernel (see this reply) onto it. Put it back into your phone
Boot to TWRP recovery (VOLUME UP+HOME+POWER)
Install the two files you just loaded
I this point in time, you SHOULD have BPA, Developer Mode AND root.
With that said........
Your Android Version? 5.0.1
Your build number? BP1
Flashed via Odin 3.10.7
What version of KingRoot did you use to Temp Root your phone? KingRoot 4.8.5
Rather than answer my own questions, I'll just state what so far does work that I've tried:
I've installed CM13 via TWRP. I currently do not have root, but that's about to change.

Before you began:
4.4.4
ANJ5
Don't remember
4.8.5
After rooting:
(If applicable) Have you taken an OTA or Flashed via Odin to a more updated build number? If so, what build number?
Upgrade to 5.0.1 N910VVRU2BOG5_StockRestore.tar.md5 using Odin.
Followed directions to unlock Developer mode.
Flashed N910VVRU2BPA1_StockRestore.tar.md5 to get 5.1.1 through Odin.
Reflashed TWRP and rebooted.
copied MultiSystem-Kernel_LP-5.1.1.zip, BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip, and xposed-v75-sdk21-arm-arter97-snapdragon.zip to phone and flashed them through TWRP. Wiped cache and Davlik cache. Rebooted.
(If applicable) What confirmed working root apps are you running (other than Root Checker)?
Titanium Backup, SD Maid, Xposed Framework, TWRP Manager, Call Recorder, BusyBox Free.
(If applicable) What have you installed onto your phone that requires an unlocked bootloader that are confirmed to be working?
You couldn't install TWRP without an unlocked bootloader, so...
(If applicable) Has this process changed (made better or worse) how your phone reads extended batteries? State which external batteries you have tested, since the root process was made available this week.
Haven't tested yet, but I think the MultiSystem-Kernel_LP-5.1.1.zip and screen auto brightness settings are draining battery less. Too soon to tell.

Bootloader upgrade questions

Hi,
I was reading the threads about upgrading / unlocking the bootloaders.
After spending almost half day rooting and rerooting, I have a few questions.
Right now I am on BPA1, rooted, stock. In order to install an Marshmallow ROM, it looks like I have to upgrade the bootloader, to minimum CPD1. Here it gets confusing. I already changed the CID to developer and the bootloader is unlocked. If I try to upgrade:
1. Can I flash just the bootloader (and eventually the modem) and not the entire stock firmware?
2. Will I lose root? If yes, I have to reroot, but the rooting tools are kind on unreliable, spent a lot of time already, no guarantee they will work again...In order to push the files for bootloader unlock, root is required. Is there a way to keep root? Flashing the stock firmware seems to lock the bootloader and eliminate root, so every time something needs to be upgraded, we have to go through the same process?
3. At this point, it looks that there are so many updates: CPD, CPF, CPG, CPJ, that I need a CPR if I have to repeat the process 4 times! Some roms don't require the latest update, but if it installed, will it work? E.g. the rom requires CPF and I upgrade to CPJ, what happens?
Thanks!

razvu said:
Hi,
I was reading the threads about upgrading / unlocking the bootloaders.
After spending almost half day rooting and rerooting, I have a few questions.
Right now I am on BPA1, rooted, stock. In order to install an Marshmallow ROM, it looks like I have to upgrade the bootloader, to minimum CPD1. Here it gets confusing. I already changed the CID to developer and the bootloader is unlocked. If I try to upgrade:
1. Can I flash just the bootloader (and eventually the modem) and not the entire stock firmware?
2. Will I lose root? If yes, I have to reroot, but the rooting tools are kind on unreliable, spent a lot of time already, no guarantee they will work again...In order to push the files for bootloader unlock, root is required. Is there a way to keep root? Flashing the stock firmware seems to lock the bootloader and eliminate root, so every time something needs to be upgraded, we have to go through the same process?
3. At this point, it looks that there are so many updates: CPD, CPF, CPG, CPJ, that I need a CPR if I have to repeat the process 4 times! Some roms don't require the latest update, but if it installed, will it work? E.g. the rom requires CPF and I upgrade to CPJ, what happens?
Thanks!
Click to expand...
Click to collapse
Yeah it definitely gets a little confusing, but I might be able to clear up a few of your questions. The bootloader you want to upgrade to is the cpd1 version, after that the only things that change when you upgrade to pf3, pg2, and pj1 are the kernels and modems. Right now I'm using the latest pj1 firmware and my bootloader has never changed from cpd1 and flashed between the different versions several times and for unlocking the bootloader on 6.0 you do have to repeat the process you did for lp, unfortunately.

kevintm78 said:
Yeah it definitely gets a little confusing, but I might be able to clear up a few of your questions. The bootloader you want to upgrade to is the cpd1 version, after that the only things that change when you upgrade to pf3, pg2, and pj1 are the kernels and modems. Right now I'm using the latest pj1 firmware and my bootloader has never changed from cpd1 and flashed between the different versions several times and for unlocking the bootloader on 6.0 you do have to repeat the process you did for lp, unfortunately.
Click to expand...
Click to collapse
OK, so what file do I need to download and flash? I have to unloack the CPD1 bootloader and reroot? Which app? Kingroot or Kingoroot?
Once this is updated, how can I upgrade the modems and kernels, can I flash them individually?
Thanks!

razvu said:
OK, so what file do I need to download and flash? I have to unloack the CPD1 bootloader and reroot? Which app? Kingroot or Kingoroot?
Once this is updated, how can I upgrade the modems and kernels, can I flash them individually?
Thanks!
Click to expand...
Click to collapse
These are excellent questions that I'm sure a lot of members are thinking, but just haven't formally asked.
I have a Developer Device that I got directly from a Samsung 2 years ago. When hsbadr put out CM 14.1, I was still on Android 5.1.1. It seemed like a daunting task to do all that was required to get to CM 14.1, but I went ahead with it. I decided that it just made more sense to have my device CID changed to the one that everyone else was on, so I went through all the motions. Yes, the root thing was very touchy. But it really wasn't all that bad.
I'm now on bootloader CPD1, and just today upgraded the baseband by odin flashing the partial firmware for CPJ2 baseband.
Can't wait for hsbadr's next build!!!!

Ok, so in conclusion, which file needs to be flashed to upgrade to CPD1? Is it a stock tar, or the bootloader can be flashed just by itself? After flashing I'm gonna lose root again and have to start over before changing the CID?
You mentioned that you have a developer edition. I have one developer and one retail. My developer is still on an older Jasmine, but it needs to sent for repair. I'm trying to get the retail one done, so I can use it in the meantime. Then, the plan is to get the same thing done on the developer edition. I was hoping that would be easier, as the bootloader is unlocked, but apparently that's not the case.
Sent from my SM-N910V using XDA Free mobile app

Nobody can recommend the right file to flash?
Sent from my SM-N910V using XDA Free mobile app

I am also looking for advice on how to upgrade the bootloader. I am on BPA1 currently but everything I find keeps upgrading everything but the bootloader.
Thanks in advance for any help you can provide.

Advice on updating new VS986

Hi all - I received a brand new VS986 today with 5.1 installed (VS98611A specifically). I followed the UsU procedure to unlock the bootloader and installed Magisk.
Basically I'd like to either remove some of the bloatware on 5.1 / Lollipop or upgrade to 6 / Marshmallow. If I choose to upgrade, is there a recommended ROM to flash that won't undo the UsU I already performed? Can I use my existing SALT flash drive to manually disable / remove unwanted apps in download mode?
I had a custom ROM on my previous phone (Galaxy S5) but I think I'll stick with a vanilla ROM this time, at least for now, unless there's a highly recommended M/N/O custom ROM that doesn't have any glaring issues, and will be an easy upgrade path from my current Lollipop installation.
Thanks for any advice here.

After further research, it appears I did a no-no and applied UsU to a Lollipop bootloader. Now that that's done, is flashing a stock Nougat ROM (e.g. as described here) safe to do? Or should I go through the procedure listed in #20 of the FAQ from steadfasterX and try to flash elements from a MM .ndz file first? If so, I downloaded a VS98626A kdz file - should that work to pull the necessary MM boot files from?
Sorry for the newbie-ish questions, I'm just trying to avoid bricking my new phone.

Reverting from custom ROM to stock causes bootloops

Hi guys,
I have a problem I need some advice for. A year ago, I purchased my Amami for the purpose of GPS-navigation on my bicycle. It always worked fine and I was able to charge it with my dynohub without any issues. The charging is giving me a headache now though, and all troubleshooting points at the phone being the problem.
Now, a couple months ago I decided to ditch 4.4 and go for a custom ROM (I've tried Oreo and Pie) which worked fine, but the phone doesn't charge as well as it used to on my bike. I'd like to go back to stock to see if that's what is causing the issue and used the Xperia Flashtool to revert to a stock image, but the ones that used to work on the phone now give me bootloops after I've flashed TWRP and ResurrectionRemix and Lineage OS.
Is there anything I need to know before I flash a stock firmware with the tool? Any input would be appreciated.

Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.

jho55 said:
Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.
Click to expand...
Click to collapse
My bootloader is unlocked, I have TWRP installed and am currently running Lineage OS (Android 8). It doesn't matter if I flash Sony's original Kitkat or Lollipop; both will have bootloops. No offense, but I'm not sure you understood my original post: I'd like to go back to an old stock ROM, because 4.4 is the one that I'm sure have me no trouble with charging on my bike.

Proper BL relock:
https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907
If you use twrp in fotakernel partition maybe necassary to write back original fotakernel.sin (inside stock.ftf) before relock with flashtool. Remember! After relock with flastool the new BL unlock key here: DEVICESERIAL \ unlock.txt

Warranty problem: Flashing to stock Nougat from a custom Pie rom

Hi folks,
I searched the forum and did not find a suitable thread that answered my question.
My Moto G5 has a charging problem and I want to give it back for a repair - it still has warranty.
I have read that flashing a custom rom does not necessarily invalidate the warranty, but to ensure that Motorola will repair the phone I would like to flash a stock (nougat) rom.
Is it possible without the risk of losing IMEI or other stuff?
Or do you recommend to send it back to Motorola with the custom rom installed?
Thank you VERY MUCH in advance!!!
Kind regards
Wolf

They will be able to see you have unlocked the bootloader regardless of whether you re-lock it
Just download the latest stock firmware and flash it via fastboot
If your base firmware is already oreo you can skip flashing gpt and bootloader to avoid risking hard brick
Don't downgrade your base firmware eg if it's oreo don't flash nougat (base firmware is stock firmware not custom rom)
I would flash it back to stock rom so at least they can't blame custom rom

Thanks!! I'm not sure, if it was delivered with Android 7 or 8. But I can flash 8 in any case, because its no downgrade?
And a last question: can I flash it also with TWRP? It's installed anyways...

moped2000 said:
Thanks!! I'm not sure, if it was delivered with Android 7 or 8. But I can flash 8 in any case, because its no downgrade?
And a last question: can I flash it also with TWRP? It's installed anyways...
Click to expand...
Click to collapse
Yes flash android 8 - note if it was never updated to android 8 you will also have to flash gpt and bootloader as well the rest of the firmware
You will need to flash the firmware via fastboot
Flashing via twrp is just like flashing a custom rom with no modifications & you will still have twrp installed and not stock recovery & still have a modified system partition etc

Thanks! Android 8 was definitely installed, only possibly not as stock firmware, but only as custom rom.
But I guess it's okay if I just flash all the files to make sure?

Motorola says, I have lost my warranty because I have opened the bootloader. They won't even fix it for money ****.

moped2000 said:
Motorola says, I have lost my warranty because I have opened the bootloader. They won't even fix it for money ****.
Click to expand...
Click to collapse
Depends what country you are in
In America or Europe you can argue and would most likely win in court that if your issue is totally unrelated to the unlocking of the bootloader they must repair it
Eg if the camera doesn't work because of a faulty component they must fix it
However if the camera stop working because you unlocked the bootloader & did some modifications causing it to no longer work then you're not covered
This would be the same for boot issues - If your phone no longer boots and you have unlocked the bootloader they can claim you have done a modification that now stops it booting
The general rule is if you unlock the bootloader than software/firmware booting issues are not covered but hardware faults unrelated to a bootloader unlock are
Again it varies depending on your country but the above is true for USA & the majority of Europe (EU)