Database Develop

Updating to MMB29K 6.01 Causing Bootloop from MRA58X 6.0.0

I tried 6 ways to sunday to update to 6.01 on a shamu nexus 6 to no avail :crying
I am unlocked, no encryption, rooted on MRA58X 6.0.0. When I try to upgrade it just bootloops.
I am fastbooting new MMB29K 6.01 bootloader.img, new radio.img, new system.img, new unencrypted boot.img, and flashing in TWRP SuperSu v2.61 prior to first reboot.
Can someone tell me what is up???? I want to stay encrypted
Thanks, Mark

There is another thread that talks about a particular flashing order. I wonder if that is your problem?
Sent from my Nexus 6 using XDA Free mobile app

Deckard_9732 said:
I tried 6 ways to sunday to update to 6.01 on a shamu nexus 6 to no avail :crying
I am unlocked, no encryption, rooted on MRA58X 6.0.0. When I try to upgrade it just bootloops.
I am fastbooting new MMB29K 6.01 bootloader.img, new radio.img, new system.img, new unencrypted boot.img, and flashing in TWRP SuperSu v2.61 prior to first reboot.
Can someone tell me what is up???? I want to stay encrypted
Thanks, Mark
Click to expand...
Click to collapse
These contradict each other, no?
Out of curiosity, what are you coming from, 6.0? Were you running any ROM of any sort?
Last question...when TWRP is about to reboot and it asks if you want it to install root, you're choosing 'No' right? 2.61 is the system-less root, and if TWRP is trying to flash it's version it'll cause problems.
I know some of these may seem simple and 'duh' moments, but I just spent the past 60 minutes trying to find out why I couldn't update only the radio......it was the radio for the N5, so we've all been there

I'm coming from MRA58X 6.0.0 and no custom rom. I do have the hells core kernal v11 ... and no I select 'No' when rebooting from TWRP to install SuperSu. Shamu Nexus 6 works great with MRA58X 6.0.0 unencrypted and rooted with hells core v11 kernal and SuperSu v2.52. I dont know how to upgrade to 6.0.1 and stay encrypted? hells core has v12 kernal 6.0.1.

Deckard_9732 said:
I'm coming from MRA58X 6.0.0 and no custom rom. I do have the hells core kernal v11 ... and no I select 'No' when rebooting from TWRP to install SuperSu. Shamu Nexus 6 works great with MRA58X 6.0.0 unencrypted and rooted with hells core v11 kernal and SuperSu v2.52. I dont know how to upgrade to 6.0.1 and stay encrypted? hells core has v12 kernal 6.0.1.
Click to expand...
Click to collapse
I haven't been modding my N6 much at all, but I do remember reading something about when using custom kernels. I cannot remember exactly what it was, but there was an issue when you would use a custom kernel then trying to go back to stock.
Did you flash the new custom kernel before you ran into the bootloop? If so, I'd try booting it up bone stock and see if you can get it going that way. Then make one mod at a time and see what's causing the issue.

hayzooos said:
I haven't been modding my N6 much at all, but I do remember reading something about when using custom kernels. I cannot remember exactly what it was, but there was an issue when you would use a custom kernel then trying to go back to stock.
Did you flash the new custom kernel before you ran into the bootloop? If so, I'd try booting it up bone stock and see if you can get it going that way. Then make one mod at a time and see what's causing the issue.
Click to expand...
Click to collapse
That would force encrypt it again.
But the way is to back to stock as much as possible. No root, no custom kernel, factory reset. The only thing needed is a modified stock boot.img with the fstab changed to encryptable.

Any outstanding reason to take the April update?

I updated my N6 when I got it a few weeks ago, then unlocked loader, installed TWRP and rooted with NRT.
I am pretty darn happy with the way everything works as it is right now.
Yesterday, my phone downloaded the April update and prompted me to install it.
As I understand, you must flash factory and unroot to take the updates.
That said, is there any overwhelming reason to go through all that for (what seems) a minor update?
I am tempted to just wait for N to be finalized and flash the new image once available and "keep on keeping on."
A lot of you are worlds more experienced than I am and I am interested in your opinions.
Should I or shouldn't I?
TIA.

There are security updates... If you want them or not is up to you.
What I and many others do (rooted, TWRP, custom kernel) is to use the latest factory image and update by flashing individual parts of it through fastboot. In the update from march to april (MMB29V to MOB30D) I only flashed boot.img, radio.img and system.img. The rest was untouched or I didn't want to update it (i.e. custom recovery).
Check out this thread: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Follow that to set up your workspace and follow method 2 when flashing. Only flash the parts you want, but always leave out userdata.img unless you want to wipe your data. Also skip the factory reset in the end...
You will need to reroot when done, but that is just a matter of booting into TWRP (and that you should do anyway) and flashing the SuperSU zip.

nunjabusiness said:
... I am interested in your opinions...
Click to expand...
Click to collapse
There is a thread of Danvdh. He makes a Stock lite ROM after every update incl. root access.
Now you have TWRP you could monthly download and flash the new lite ROM.

NLBeev said:
There is a thread of Danvdh. He makes a Stock lite ROM after every update incl. root access.
Now you have TWRP you could monthly download and flash the new lite ROM.
Click to expand...
Click to collapse
Interesting idea. I am encrypted too, does that matter?

NLBeev said:
There is a thread of Danvdh. He makes a Stock lite ROM after every update incl. root access.
Now you have TWRP you could monthly download and flash the new lite ROM.
Click to expand...
Click to collapse
i am using Danvdh's Stock Lite ROM MMB29X. he has not updated to MOB30D. now say if i wanted MOB30D can i do the below steps?
flashing individual parts of it through fastboot
flashed boot.img, radio.img and system.img.

No reason at all.....its like saying you have some pirated version on Windows 10 and you would have to reinstall windows 8.1 to take a 19kb security patch. We have been running these OS with intentional security breaches (root) for many years..... Y start to worry about it now?
Additionally there will probably never again be a feature released that would necessitate such drastic measures. IMO.....sall incremental anymore.

so your opinion is to just roll with Danvdh's updates as they come?

iluvatrix said:
i am using Danvdh's Stock Lite ROM MMB29X. he has not updated to MOB30D. now say if i wanted MOB30D can i do the below steps?
flashing individual parts of it through fastboot
flashed boot.img, radio.img and system.img.
Click to expand...
Click to collapse
There only a few changes (bootloader, modem).
Better wait for the May update of Danvdh.
I think you can flash the new boot, radio and system. But that includes the bloatware that Danvdh will remove.

OxygenOS 4.1.6(7.1.1) OTA for OnePlus 3 (GDrive mirror)

"Hi all,
OxygenOS 4.1.5 was withdrawn, we are pushing out the incremental roll-out of OxygenOS 4.1.6 (7.1.1) OTA for OnePlus 3 and 3T instead.
Here are some highlights
New additions:
• Added system push notifications for important information from OnePlus
Updates:
• Updated network settings for select carriers
• Updated OnePlus Community app to v1.8
• Updated Android Security Patch level to 1st May 2017
• Modified WiFi no internet indication icon
Bug fixes:
• Fixed storage issue present on 3rd party filemanagers
• Fixed VoLTE issue on certain Jio SIM cards
• Fixed connection issue on Android Auto
Optimizations:
• Battery
• Proximity sensor
• Camera low light focus
• Expanded screenshot
Other changes:
• Enhanced system stability
For those who were on previous versions for OnePlus 3 and 3T, we appreciate your active feedback and attempts to reach out to us. With your help, we have been able to better optimize and improve several key areas. Thank you for your patience and as always, we look forward to hearing your continued feedback in the bug reporting forum here: https://forums.oneplus.net/feedback/.
As always, this OTA will be incremental. The OTA will reach a small percentage of users today, and we'll begin a broader rollout in a few days.
Your feedback is appreciated. We may not always be able to respond to every comment in the forums, but please be assured that we take your comments and feedback seriously. Hope you enjoy!
Please make sure to fill out our user survey here: https://goo.gl/forms/Pvr6KisTvbFoqZkl1
Never Settle.
****Special thanks to @ Stephan Mävers for helping out with rom validation."
https://forums.oneplus.net/threads/oxygenos-4-1-6-7-1-1-ota-for-oneplus-3-and-3t.547283/
Full ROM: https://drive.google.com/open?id=0B8wU-_ssGUuoSGJqUVYzYWlEUlk
MD5: 3db32c320ebce696e9b058a31e77e9a8

So quick, just now got someone OTA adn informed at OP forum and uploaded in xda. Great effort @piats

[email protected] said:
So quick, just now got someone OTA adn informed at OP forum and uploaded in xda. Great effort @piats
Click to expand...
Click to collapse
Hehe, time to give something back for this community :good::highfive:
Edit: remember to backup everything before flashing. I dirty flashed this ROM over stock OOS 4.1.5 via bluespark recovery v35 and it didn't boot back to system. So I booted back to recovery and somehow twrp asked password to decrypt data partition. I was decrypted before. So I installed stock recovery. Wiped everything and flashed this ROM via stock recovery. Everyhthing works now.

Can I flash this zip using TWRP?

DouglasDuZZ said:
Can I flash this zip using TWRP?
Click to expand...
Click to collapse
Well you can try but remeber to backup everything before flashing. See my previous post.
I would recommend stock recovery for now.

I would really like to know the reasons behind these withdrawns, but thats just me. Thanks for the mirror.

batt002 said:
I would really like to know the reasons behind these withdrawns, but thats just me. Thanks for the mirror.
Click to expand...
Click to collapse
Because there was an issue they missed through QC. OTAs are always incremental/staged just in case something like this happens. This way only small number of devices are affected

bhake said:
Because there was an issue they missed through QC. OTAs are always incremental/staged just in case something like this happens. This way only small number of devices are affected
Click to expand...
Click to collapse
Yes I'm interested in that issue that was missed, but we'll never know

I instaled new Twrp blu spark 3.1.1.37 by eng stk.
Full wipe, clean flash the rom, full zip. Recovery ok. No need to reflash recovery..
All apps work for me. Root, everything.

piats said:
Hehe, time to give something back for this community :good::highfive:
Edit: remember to backup everything before flashing. I dirty flashed this ROM over stock OOS 4.1.5 via bluespark recovery v35 and it didn't boot back to system. So I booted back to recovery and somehow twrp asked password to decrypt data partition. I was decrypted before. So I installed stock recovery. Wiped everything and flashed this ROM via stock recovery. Everyhthing works now.
Click to expand...
Click to collapse
I dirty flashed full zip from encrypted 4.1.5 with TWRP 3.0.4-1 and everything went fine.

I am on OOS 4.1.5 . rooted with magisk and twrp recovery. I thought magisk would help hide root and update using OTAs. I did hide the oneplus update process in magisk hide and updates prompted a 45 mb download.(with root it would say go download the full zip). I downloaded the OTA . but as expected flashing it via twrp failed. is there any way to just do OTA update with root and twrp ? I did see some threads where people went to stock recovery and installed it. is that a simple procedure ?

I just updated to oxygen os 4.1.6 and I am unable to root my device, i was able to root on previous versions using the same supersu file but now it does not work, if anyone has a solution please help me out.

Olal said:
I just updated to oxygen os 4.1.6 and I am unable to root my device, i was able to root on previous versions using the same supersu file but now it does not work, if anyone has a solution please help me out.
Click to expand...
Click to collapse
Hi, try latest supersu 2.82 or magisk
Sent from my OnePlus3 using XDA Labs

Rooting options for the S10 family

I need to get something straight, as I didn't quite get it. So the options for someone who'd like to root his S10 are 3:
1) Rooting with Topjohnwu method: This will get you root on the stock rom, but will keep the default recovery which is pretty much useless if one wanted to flash a custom rom.
2) Rooting with a prepatched version of TWRP and then, if desired, flash any custom rom (compatible with the TWRP version installed). This method is said to be less stable that the previous one.
3) Install TWRP after rooting with john wu method and then using it to flash custom rom.
First of all, is all this correct?
If so, then one has to choose between rooting safely, but keeping his phone stock, or rooting and then installing twrp and then flash whatever he desires.
Hopefully, somebody will be so kind to clarify this that is an unusually complicated situation about rooting this phone! I already regret passing my perfectly rooted S9 to my son
Thanks for whatever help you'll be willing to provide.
Cheers

I would say you summoned it up nicely.
The advantage of stock Magisk root is you can e.g. use Substratum, Magisk modules and update monthly security releases by yourself but, of course, no Custom ROMs.
The advantage of TWRP Magisk root is clearly the Custom ROM possibility but here you cannot update the monthly security releases by yourself and are dependent on the ROM creator to release the security updates.
I had been using Topjohnwu Magisk root on stock rom since released mainly to use Substratum/ some Magisk Modules and did the AP-patching everytime the monthly security was released.
However, doing the November security AP-patching something went wrong and I ended in boot-loop. So thought, as I had to reflash anyway I would try TWRP/ Custom ROM - I went with yash92Duster's lightrom / geiti94's magisk TWRP both which I find very stable.

Norup58 said:
I would say you summoned it up nicely.
The advantage of stock Magisk root is you can e.g. use Substratum, Magisk modules and update monthly security releases by yourself but, of course, no Custom ROMs.
The advantage of TWRP Magisk root is clearly the Custom ROM possibility but here you cannot update the monthly security releases by yourself and are dependent on the ROM creator to release the security updates.
I had been using Topjohnwu Magisk root on stock rom since released mainly to use Substratum/ some Magisk Modules and did the AP-patching everytime the monthly security was released.
However, doing the November security AP-patching something went wrong and I ended in boot-loop. So thought, as I had to reflash anyway I would try TWRP/ Custom ROM - I went with yash92Duster's lightrom / geiti94's magisk TWRP both which I find very stable.
Click to expand...
Click to collapse
One more doubt, if I may ask : once rooted the safe way, if I wanted to install twrp I would need to find the build that is compatible with the already patched firmware on my phone? And then only the roms that are exactly for the same build?
This is the most complicated rooting process that I have ever faced. And I've been rooting my phones and tablets since a very long time
Thanks

Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched

Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched
Hey all, I just updated my wife's P4 to Magisk 20.4 as of yesterday and have had no issues so far on the new version (nor on my P4XL). Here are the stock and recently newly updated Magisk patched (v20.4) boot images. I couldn't direct install the update on either of the phones via Magisk Manager, so I figured I would share these images.
Stock March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757144
Magisk Patched (v20.4) March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757143
Remember, these are ONLY for those on QQ2A.200305.003 firmware already. Don't flash if you don't know what you're doing.

Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.

Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.

falawefulwaffle said:
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Click to expand...
Click to collapse
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
Spookymyo said:
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
Click to expand...
Click to collapse
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.

i5lee8bit said:
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
Click to expand...
Click to collapse
Thanks for the reply. I ended up getting it to work using the "payload_dumper-win64" method i found in another thread to extract the boot.img from the payload.bin file. Turns out the OTA file was online from google.
To updatePixel 4 xl with "coral-ota-qq2a.200305.003-3b25765d" MAach update OTA software:
- uninstalled Magisk
-updated software
-reinstalled magisk
-patched the boot img from payload.bin
-pushed modified boot to device
-Done
Everything seems to be working well. I got to use python for the first time, so that was kind of fun. I was a flashing machine back around the galaxy s4.

I got root working. Spent so much time trying different things and all I had to do was factory reset my phone. There must have been some file or module interfering with the process. Once I reset my phone the root process went without error. ?*