Database Users

5.1 OTA failed

I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?

Claghorn said:
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Click to expand...
Click to collapse
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.

madbat99 said:
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
Click to expand...
Click to collapse
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.

Claghorn said:
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Click to expand...
Click to collapse
Since lollipop it is very sensitive to anything different or missing in system. Just flash the 5.1 factory image with the ~w removed from the flash-all.bat file so it doesn't wipe data. Or use wugs to flash stock 5.1 image with "no wipe" enabled. Or like I said in previous you can always flash a clean system image of 5.0.2 then take ota. Either way will update you without wiping data.

Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !

neo5468 said:
... I don't get it why people bother with OTA all the time ...
Click to expand...
Click to collapse
I'm not really bothering with it - it just showed up and started bothering me .

1.Backup everything.
2.Flash 5.1 with nexus root toolkit.
3.Restore all the data.
4.Change your build in NRT to android 5.1
5.Root it and flash TWRP/CWM if you want.
6.?????
7.Profit! duh

neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root.
Click to expand...
Click to collapse
... or wait for a week until someone will release a rooted 5.1 update

sensboston said:
... or wait for a week until someone will release a rooted 5.1 update
Click to expand...
Click to collapse
Why would you wait a week, we already waited too long for offical 5.1 to come out for our tablet. It is 5minutes of work, works 100% and also fasboot is the safest way to flash. Also you download the image straight from developers.google.com so there is no bs. I much rather flash that. But to each his own.

There is already a recovery flashable "stock rooted 5.1" thanks to scrosler (cleanrom Dev).
5.1 rooted ROM

neo5468 said:
Why would you wait a week
Click to expand...
Click to collapse
Agree, week is too long. A few days - better words And "one click" solution is much better in case of possible mistakes during flashing separate partitions, rooting etc...

neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
Click to expand...
Click to collapse
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?

beall49 said:
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
Click to expand...
Click to collapse
Custom recovery is fine. There is also a new boot loader to flash as well I think. You can also run the flash all batch file in the factory image and just remove the -w from it so it doesn't wipe data. But what you posted is also correct, but flash the boot loader too. If your rusty at it just use wugs toolkit, it will run the commands for you.

Solid, removing the -w was what I was forgetting. I knew there was something else.
Thanks!

Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL

nlinecomputers said:
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
Click to expand...
Click to collapse
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.

madbat99 said:
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
Click to expand...
Click to collapse
No big deal really. I don't keep important data on it. It's mostly used for Kindle and games. Easy to fix.

XT1575 Need advice - Relock bootloader, failure

Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Sent from my Portable

PassatSport15 said:
Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Click to expand...
Click to collapse
A few problems here... First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old, it's the original MM firmware from Moto's website (the one on Moto's site is very old and dated incorrectly). We don't have the 18-16 image yet, so you cannot relock or even effectively fix this.
Also, you used a tool to flash, so when pieces failed to flash, you didn't even know it... And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
When you relock a Moto device, you don't just enter "fastboot oem lock" like a Nexus device, there is a process where you start with "fastboot oem lock begin" then flash a complete, signed factory image, wipe, and end with "fastboot oem lock" in one process.
Many parts to this process went wrong... Right now you are just kind of stuck.
BTW, relocking the bootloader has no effective gains except security... You will still be able to see in a glance it was unlocked from the bootloader screen or a fastboot command and the unlocked bootloader warning screen will still be there (you have to flash a custom logo to make it go away).

Did you make a backup of your stock ROM with TWRP prior to rooting? Restoring the backup with TWRP along with stock recovery is usually going to be the simplest and easiest way to go back to full stock.
As acejavelin stated, there really is no benefit to relocking the bootloader except from a security standpoint. As long as the stock ROM and recovery are restored to preroot condition with no system mods, you can take OTAs regardless of bootloader status.

acejavelin said:
First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old
Click to expand...
Click to collapse
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
acejavelin said:
And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
Click to expand...
Click to collapse
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Sent from my Portable

PassatSport15 said:
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Click to expand...
Click to collapse
I think 18-12 is the latest we have so far, but trying to flash it would not help... Your best bet at this point is either custom ROM or wait until we can get the image for 18-16. The problem here is Moto's don't support downgrading, it can be done but it often leaves you in a mixed state.
You could try flashing the latest version we have available manually (don't use a tool) and it might be close enough to able to OTA from there. You have some though, rumor has it initial surveys for an upgrade on the Pure just went out to MFN users this week, assuming it is the Nougat upgrade trial then once it starts you have 4-6 weeks barring any problems they encounter before public release. Assuming of course that history repeats itself and Lenovo follows the same path as Moto has previously.
So basically I'm saying have patience... We don't know when (or really if) we will get the current firmware image, sometimes it's quick and sometimes it takes months.

Update on my xt1575, that I could not take an OTA, it gave me an error - unsuccessful.
My original software was MPHS24.49-18-16, December update, latest software.
Well, I went ahead unlocked the bootloader, installed TWRP, then rooted....
Days later I had decided to unroot, so I would be able to take the OTA.
While I unrooted my device, it was successful, but could not take the updates at all.
Now I reflashed again, in this order below.
Autoflash Script with MPHS24.49-18-8.
Reboot the phone, checked if it was unrooted (No root)
Now I went to software update, and the phone did it's upgrade, like last time. Did the update, device rebooted and it was SUCCESSFUL!
I am finally back to the original software MPHS24.49-18-16
Which was December 2016 update.
Sent from my Portable

BootLoop after installing twrp and SuperSU

Bit of background.
CID: BS_US001
MID: 2PS650000
Original verizon phone that i sent to sunshine for S-off and to unlock from Verizon. Ever since receiving it, almost a year ago, I've never been able to install a custom recovery I gave up on it for months and yesterday tried again. Finally managed to get TWRP. Then I tried to install SuperSU and bootloop. There's always been an issue getting OTAs. The OTA would download, install, and during boot, would give an error or go into bootloop. So, the plan was to finally get a recovery, root it, see about getting the latest OTA etc. Obviously that didn't work out. I feel like there's an issue with the boot sector and has always been. At this point, I just want to wipe and start over but I feel if I don't get this boot sector fixed the phone will never work properly. Any ideas? An RUU will update the OS and maybe fix the bootloop for now, but it won't deal with the OTA or issues with the boot sector that seem to be ever-present. Could use some advice.
I'm also a bit confused about something. This is originally a verizon phone but has been unlocked. When looking for RUUs from HTC should i be looking for the verizon versions or unlocked version?

vijn said:
Bit of background.
CID: BS_US001
MID: 2PS650000
Original verizon phone that i sent to sunshine for S-off and to unlock from Verizon. Ever since receiving it, almost a year ago, I've never been able to install a custom recovery I gave up on it for months and yesterday tried again. Finally managed to get TWRP. Then I tried to install SuperSU and bootloop. There's always been an issue getting OTAs. The OTA would download, install, and during boot, would give an error or go into bootloop. So, the plan was to finally get a recovery, root it, see about getting the latest OTA etc. Obviously that didn't work out. I feel like there's an issue with the boot sector and has always been. At this point, I just want to wipe and start over but I feel if I don't get this boot sector fixed the phone will never work properly. Any ideas? An RUU will update the OS and maybe fix the bootloop for now, but it won't deal with the OTA or issues with the boot sector that seem to be ever-present. Could use some advice.
I'm also a bit confused about something. This is originally a verizon phone but has been unlocked. When looking for RUUs from HTC should i be looking for the verizon versions or unlocked version?
Click to expand...
Click to collapse
You can't take OTAs as long as you have twrp installed or have a modified system partition, which you got after attempting to install SuperSU.
An RUU would restore all partition to a stock state, not just the OS. That's what I would do to get a clean slate, make a stock backup and then root it. Remember that the ruu will wipe your phone so backup your files. You won't find Verizon RUUs on HTC's website, but you can download them from the stock thread here.
Also make sure to fully read the instructions and FAQ posts in the twrp thread, and do the same in the root thread.
Edit: Re-read your post. Since yours is converted to U.S Unlocked, you indeed have to download the latest ruu from HTC's website. Forget about the Verizon ruu.

Tarima said:
You can't take OTAs as long as you have twrp installed or have a modified system partition, which you got after attempting to install SuperSU.
An RUU would restore all partition to a stock state, not just the OS. That's what I would do to get a clean slate, make a stock backup and then root it. Remember that the ruu will wipe your phone so backup your files. You won't find Verizon RUUs on HTC's website, but you can download them from the stock thread here.
Also make sure to fully read the instructions and FAQ posts in the twrp thread, and do the same in the root thread.
Edit: Re-read your post. Since yours is converted to U.S Unlocked, you indeed have to download the latest ruu from HTC's website. Forget about the Verizon ruu.
Click to expand...
Click to collapse
Sorry about the late reply. I was traveling. First off, thanks for your response. I guess my only remaining question then is what RUU do i go for? Unlocked developer? I'm just worried there might be a clash with my CID/MID. It's happened before on a previous phone. At this point, all i really want is to get stock back, make sure it's carrier unlocked, update to Oreo, and then, if I'm feeling lucky, root it, though I might just pass on that. So, would you say unlocked developer RUU is my best bet?
Again, thanks for your help.

vijn said:
Sorry about the late reply. I was traveling. First off, thanks for your response. I guess my only remaining question then is what RUU do i go for? Unlocked developer? I'm just worried there might be a clash with my CID/MID. It's happened before on a previous phone. At this point, all i really want is to get stock back, make sure it's carrier unlocked, update to Oreo, and then, if I'm feeling lucky, root it, though I might just pass on that. So, would you say unlocked developer RUU is my best bet?
Again, thanks for your help.
Click to expand...
Click to collapse
If it's an originally verizon phone which was converted to US Unlocked, then use the latest ruu for unlocked on HTC's website. It won't cause you to lose your carrier-unlocked status. It will take you to latest Nougat version. From there, take the OTA update

Tarima said:
If it's an originally verizon phone which was converted to US Unlocked, then use the latest ruu for unlocked on HTC's website. It won't cause you to lose your carrier-unlocked status. It will take you to latest Nougat version. From there, take the OTA update
Click to expand...
Click to collapse
Well, it worked. I'm currently on Oreo which is awesome. So first off, thank you very much. Not sure why it didn't work last year, but water/bridge etc.
This brings me to one more question. I want to get rid of some bloatware but would rather not do a full root. I've heard Magisk will give me the benefits of root without the security headaches that prevent things like Google Pay from working. You familiar with that? I also need 2 apps that require root. Never worked with Magisk but I have rooted a bunch of times and honestly, I kinda don't feel like doing it again, especially if I can maybe get the best of both worlds with Magisk. I just don't know enough about it. Figured maybe you might.

vijn said:
Well, it worked. I'm currently on Oreo which is awesome. So first off, thank you very much. Not sure why it didn't work last year, but water/bridge etc.
This brings me to one more question. I want to get rid of some bloatware but would rather not do a full root. I've heard Magisk will give me the benefits of root without the security headaches that prevent things like Google Pay from working. You familiar with that? I also need 2 apps that require root. Never worked with Magisk but I have rooted a bunch of times and honestly, I kinda don't feel like doing it again, especially if I can maybe get the best of both worlds with Magisk. I just don't know enough about it. Figured maybe you might.
Click to expand...
Click to collapse
I use Magisk myself. I prefer it to flashing the classic supersu for root.
Install latest twrp (make sure its the latest twrp for the 10), then flash Magisk. Then install Magisk manager app. As simple as that.
Read the instructions here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

You rock man. Thanks for all the help.

vijn said:
You rock man. Thanks for all the help.
Click to expand...
Click to collapse
No worries, glad it worked.

Shortcut to being rooted on N910VVRU2CQI2

Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE

I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks

My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839

RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.

Thanks doc. Is that a folder that gets overwritten when you flash a new room?

This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?

lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works

RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.

does this require the developer version? btw how do i backup

I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.

RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.

kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.

Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.

In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.

Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.

Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.

Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?

lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.

kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.

Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.

Mi A1 Downgrade from Pie to Oreo questions

EDIT 2: ISSUE SOLVED. Go to the bottom of this comment for how to get it done right. Credits to @rizkyxculture and @orma1
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
EDIT 2: Sorry for necroing this thread, but just to clear things up a bit, from my own experience, and include and clarify what @orma1 said below in this thread so you don't have to scroll down. Before all this, make sure you have SYSTEM WIDE ADB AND FASTBOOT INSTALLED for simplicity's sake.
All credits go to @orma1 and @rizkyxculture for your amazing efforts into this <3. None of it is mine, so thank them in their respective comments/threads if you wish to.
1. REMOVE ALL PASSWORDS AND FINGERPRINTS BEFORE PROCEEDING WHILE IN PIE, and do CLEAN DATA WIPE (do not choose the relock bootloader in Mi Flash Tool).
2. Do everything in that guide sent, and at the end, where rizky mentions flashing November update after the TWRP restore, don't do it. Instead, re-flash the March update. Thanks @orma1 for your comment. If your phone just straight up boots like mine did, without bootlooping, just power it off and go to fastboot again. Link to guide: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624.
3. Once your phone boots normally, go to developer options, and uncheck the automatic system updates to prevent it from going to pie automatically later on. in the future. Install GCam at this stage if you wish (follow manual installation guide on XDA). Link: https://forum.xda-developers.com/showpost.php?p=75541654&postcount=98
4. After you've installed GCam (which is why you're probably doing all this in the first place, or not, regardless), chances are you still want to keep your warranty (and for security reasons) and therefore you should relock your bootloader, else the servicemen are just going to see that BIG warning at your phone's boot, and are likely revoke any warranty straight up. To do this, simply go back to fastboot and type the command below in Command Prompt and WHILE FIRMLY PRESSING AND HOLDING THE VOLUME DOWN BUTTON (or copy paste the line below WHILE FIRMLY PRESSING AND HOLDING THE VOLUME DOWN BUTTON):
fastboot oem lock
Once it says okay, type the following command:
fastboot reboot
Done. Now reboot, go to system update, and download and install the November update. Enjoy your still in warranty Mi A1 with Oreo and/or GCam (just make sure you uninstall the apk when giving it to the service center should you ever need to service it). Also, the power down button press prevents the auto data wipe function from activating. Have fun.
Also I have verified this works even on the April 2019 update. Just don't update any further, else I can't be sure.

Nafis-ul-Islam said:
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
Anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
Click to expand...
Click to collapse
If you can't find documentation of anyone else successfully downgrading from Pie to Oreo with this specific device, then no one knows what is or isn't safe. In this case, you'll be taking a shot in the dark.
If you "can" find documentation of someone successfully downgrading, just do what they did.
Other than that, you'll have to blaze your own new trail.
Sent from my LGL84VL using Tapatalk

Droidriven said:
If you can't find documentation of anyone else successfully downgrading from Pie to Oreo with this specific device, then no one knows what is or isn't safe. In this case, you'll be taking a shot in the dark.
If you "can" find documentation of someone successfully downgrading, just do what they did.
Other than that, you'll have to blaze your own new trail.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Guess I'll just stick to pie and bite the sand and live with it till someone gets a solid, working method...
As a second thought, if I make a backup of everything (system, boot, etc. etc.) in TWRP and then carry out the flashing process, will reflashing those backups restore my device in case of a brick?

Nafis-ul-Islam said:
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
Anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
Click to expand...
Click to collapse
Just flashing oreo from pie should cause IMEI loss.
I used the method from here: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
although I had to do his method a little differently.
also make sure if you can to backup your data as you can lose it in the process.
first of all, after oreo march update flash, my phone did boot but with no IMEI.
second of all, flashing November update after restoring IMEI caused bootloop, instead you need to flash march update again. afterwards your phone should boot with the correct IMEI (you can double check with the one on your phone's box) . worked for me with two Mi A1s.
after all of this I was able to update to 8.1 November update via system update in the settings.
and lastly I made sure to disable automatic system update from developer settings.
Good luck!

Wanted to post same question.
As you described, there is method for downgrade but you are restoring someone else EFS partition, for that i am skeptical too.
Should we just downgrade as usual to Oreo using Mi Flash Tool? Or that thread is the only way of downgrading to Oreo?
Will i backup my IMEI if i backup EFS partition trought TWRP (Running Lineage OS 16.0)

Meme :D said:
Wanted to post same question.
As you described, there is method for downgrade but you are restoring someone else EFS partition, for that i am skeptical too.
Should we just downgrade as usual to Oreo using Mi Flash Tool? Or that thread is the only way of downgrading to Oreo?
Will i backup my IMEI if i backup EFS partition trought TWRP (Running Lineage OS 16.0)
Click to expand...
Click to collapse
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.

orma1 said:
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
Click to expand...
Click to collapse
Thanks, will see about all this.

orma1 said:
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
Click to expand...
Click to collapse
Sorry for my delayed response firstly, I'm currently in the countryside and the network here is *God awful*. I'll definitely check this out when I get back home this Saturday hopefully. How did you back up though? Did you boot temporarily to TWRP in fastboot and then backup everything to an external storage?

Nafis-ul-Islam said:
Sorry for my delayed response firstly, I'm currently in the countryside and the network here is *God awful*. I'll definitely check this out when I get back home this Saturday hopefully. How did you back up though? Did you boot temporarily to TWRP in fastboot and then backup everything to an external storage?
Click to expand...
Click to collapse
I used the backup from this thread
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
It's a backup of someone else's efs and boot patiotions. At first I thought too that restoring someone else's backup should result in me getting his IMEI.
But after trying to restore through this backup My IMEI changed from 0 to the one on my phone's original box meaning I got my own IMEI. the method there worked perfectly for me and now I am rocking 8.1 Oreo November update with Magisk and TWRP. the only thing is that following step 10 in the tutorial there resulted in a bootloop for me. Instead I followed the suggestion of one of the comments saying that instead of flashing November update after restoring IMEI you need to flash the same March update you flashed before. this time my phone booted with IMEI and I updated to 8.1 November through OTA.

Did you downgraded succesfully?

Meme :D said:
Did you downgraded succesfully?
Click to expand...
Click to collapse
I was able to downgrade successfully following this guide: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
In step 10 you need to flash oreo march update again and not November update as mentioned as flashing November update caused me bootloop.
afterwards you can update to November update via System update in the settings.
besides this I followed the tutorial exactly and was able to downgrade two Mi A1s.

I have successfully downgraded my Mi A1 with this thread
"Tutorial Downgrade 9.0 to 8.1 No EDL, No IMEI Problem & No Signal Problem"
Also im a 14 Yr old nearly 15 on April 20.

I was afraid too, now I'm on Nougat )
Just follow this tutorial : https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Before doing anything, boot TWRP and create a full backup of your system, after that transfer it to your PC. Probably you don't need it but better safe than sorry.
After you will flash March firmware, your phone will boot but you will not have signal, it's okay. Thing is, you don't lose the IMEI, it's still there, but somehow you lose the signal. Boot TWRP again, create a backup of your boot and EFS, you will see TWRP folder in your phone, go there and you will see a backup. Remove your backup files and replace them with the one from the guide, then you can restore them without issues (you will see a modem error, ignore it). Restart and let it boot a bit, then go to bootloader again, flash March firmware again (don't flash the November one! ignore that from the guide) and the signal will be back. If you do this, I doubt you will lose your IMEI somehow. I never lost mine, it's the same from the box.
Good luck! Make sure you go in developer settings after and disable automatic updates or you will be back to Pie. I rooted my phone so it can't update.

Just flashed it now, and it's working perfectly as orma1 described. I can't thank you enough <3

Nafis-ul-Islam said:
Just flashed it now, and it's working perfectly as orma1 described. I can't thank you enough <3
Click to expand...
Click to collapse
I'm happy to help
but all the credit goes to rizkyxculture for finding this method and ibooth2004 for correcting us to flash March update again instead of the November one.

so glad i read this and got the courage to go back, now downloading november ota, pie on this device is so bad, and cant even use gcam.

Marcos OC said:
so glad i read this and got the courage to go back, now downloading november ota, pie on this device is so bad, and cant even use gcam.
Click to expand...
Click to collapse
I agree the system's performance on pie is horrible and also the mic volume is low which is very annoying.