Develop Bugs

10/26 System Update?

I'm running Marshmallow 6.0 through the Bad Boyz v.2 Rom and I just got a 2.2 MB system update... Has anyone else recieved this update, any clue what this is?

I just had it pop up for me a few minutes ago. I'm rooted so I can't flash it yet because I'm not near aPC.

I received it also, not sure what it is

artjef said:
I received it also, not sure what it is
Click to expand...
Click to collapse
I'm afraid... hold me.

It fixed the netflix video freezing issue.

fasthair said:
I just had it pop up for me a few minutes ago. I'm rooted so I can't flash it yet because I'm not near aPC.
Click to expand...
Click to collapse
I've just had this too. Can I ask how you flash an update like this on a rooted device? I usually wait for the full image and then just flash that.

I got it too just now. it's 10/27/2015 1:27 AM

I installed the 6.0 image last week as explained in a post, with TWRP and the modified kernel. How do I install this update now?

Magister54 said:
I installed the 6.0 image last week as explained in a post, with TWRP and the modified kernel. How do I install this update now?
Click to expand...
Click to collapse
the update is 2.2 megs. The original MM6 image was manually installed on my device when it came out and this update just got installed normally as usual. Maybe you should get the stock MM6 image from google and let things work by themselves. I don't see why i would change anything on my nexus 7 2013 with a fresh original MM6 installed .....
Cold this morning in Québec hey ?

zigonneux said:
the update is 2.2 megs. The original MM6 image was previously installed manually when it came out and this update just got installed normally as usual. The device told me that an update was available and if i wanted to install it.... that's it that's all. Maybe you should wipe and flash the stock MM6 image from google and let things work by themselves. I don't see why i would change anything on my nexus 7 2013 with a fresh stock MM6 installed .....
Cold this morning in Québec hey ?
Click to expand...
Click to collapse
Problem is it reboots in TWRP, I cannot install it manually from here, it fails :-/
And yes it was -4°C this morning

Magister54 said:
I installed the 6.0 image last week as explained in a post, with TWRP and the modified kernel. How do I install this update now?
Click to expand...
Click to collapse
Magister54 said:
Problem is it reboots in TWRP, I cannot install it manually from here, it fails :-/
Click to expand...
Click to collapse
You need stock recovery to install the update. I'm not sure about the modified kernel, I flashed the stock boot.img just to be safe.
After sideloading the update (or I guess you can just update it normally if your device has automatically downloaded the update) and rebooting, I re-flashed TWRP and then used it to install the modified kernel and SuperSU. Everything is peachy now.

you can use " Nexus tool rootkit " to wipe and reinstall the original stuff. As the man said up here, you need a stock recovery to install the update... if you re-install this modified kernel, you might have the same problem at the next update.

does anyone have a flashable zip for this update? I really don't wanna reload just to install this update....

airberger said:
You need stock recovery to install the update. I'm not sure about the modified kernel, I flashed the stock boot.img just to be safe.
After sideloading the update (or I guess you can just update it normally if your device has automatically downloaded the update) and rebooting, I re-flashed TWRP and then used it to install the modified kernel and SuperSU. Everything is peachy now.
Click to expand...
Click to collapse
Just wondering if the version and or the build numbers changed?
Thanks

^As it says on the factory image page, it's still 6.0.0. MRA58U.
quazimodem said:
does anyone have a flashable zip for this update? I really don't wanna reload just to install this update....
Click to expand...
Click to collapse
You don't need to.
Download the system image and fastboot flash boot.img and system.img.
That's is. Doesn't wipe anything. Takes two minutes.

airberger said:
You need stock recovery to install the update. I'm not sure about the modified kernel, I flashed the stock boot.img just to be safe.
After sideloading the update (or I guess you can just update it normally if your device has automatically downloaded the update) and rebooting, I re-flashed TWRP and then used it to install the modified kernel and SuperSU. Everything is peachy now.
Click to expand...
Click to collapse
I rebooted in bootloader, flashboot recovery and boot from official image, but recovery boots in the dead android robot :-/. I reflashed TWRP and rooted kernel to get back on feet.

yosmokinman said:
^As it says on the factory image page, it's still 6.0.0. MRA58U.
Click to expand...
Click to collapse
Thanks... I should have looked there first.

Is it somehow possible to flash the OTA on a rooted MM 6.0 with still stock recovery on it? I never flash but temperary boot TWRP to flash things. Would hate to reflash firmware for every OTA.
Thanks.

You can download the whole archive of MRA58U, extract system.img, reboot in bootloader and use flashboot to flash system.img (and boot.img if you do not need the rooted kernel)

bad modified boot image?
Hi there,
I am upgrading to MRA58U, factory image upgrade just works fine (skipped wiping as usual), but the modified boot image (from razor-mra58u-boot.zip) won't load.
Code:
> fastboot flash bootloader boot.img
sending 'bootloader' (7448 KB)...
OKAY [ 0.239s]
writing 'bootloader'...
FAILED (remote: Signature mismatched!!!)
The very same procedure worked fine for mra58k.
What am I doing wrong?

Unable to update Recovery to update ROM

I haven't updated my phone in around a year so I'm trying to update to either Android 5 or 6. Whenever I try to update the ROM to anything newer than 4, I get an error with the rom binaries. I read somewhere that this has to do with the Recovery being outdated which makes since as I'm on TWRP 2.8.0. However, I tried to update to TWRP 3.0.0 and then 2.8.4 and both times my phone got stuck in the Recovery boot process. I also read somewhere that this might be due to an outdated firmware. After more reading, I'm confused on how to update the firmware or what I should do to remedy these other problems. I tried to use RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2 to update my phone off of a guide I found, but it failed. Any help or suggestions would be really appreciated.
I have the ATT m8 and I'm running Android 4.4.4 with CyanogenMod 11-20150106-Nightly-m8 and TWRP 2.8.0. Heres the results from running adb getvar all on my phone
i.imgur.com/QPSAEAY.png

I noticed at some point my phone had radio invalid and basically every peripheral had stopped working; no reception, wifi, bluetooth, or camera. I tried oem lock command then to unlock it with the binary downloaded from htcdev. At that point everything besides the external sd card decided to become unmountable and now only the bootloader and TWRP works. Soooooo......... any help would be appreciated
edit: So I flashed stock recovery and did a factory reset This fixed this particular problem so my phone is at least working. then reinstalled TWRP. Unfortunately, I was only able to install 2.8.0 because of the problem described above so I'm back to square one

tjm46 said:
I also read somewhere that this might be due to an outdated firmware. After more reading, I'm confused on how to update the firmware or what I should do to remedy these other problems. I tried to use RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2 to update my phone
Click to expand...
Click to collapse
This is the same firmware as the hboot number in your photo would indicate.
Relock the bootloader and run the Lollipop 4.28.502 RUU as linked in my AT&T M8 Index thread here: http://forum.xda-developers.com/showthread.php?t=2751432
Then unlock the bootloader again, wipe cache and try to install TWRP 3.0.0.0

redpoint73 said:
This is the same firmware as the hboot number in your photo would indicate.
Relock the bootloader and run the Lollipop 4.28.502 RUU as linked in my AT&T M8 Index thread here: http://forum.xda-developers.com/showthread.php?t=2751432
Then unlock the bootloader again, wipe cache and try to install TWRP 3.0.0.0
Click to expand...
Click to collapse
Thanks, this fixed it. I don't know how many different articles and stuff I read, but I must have missed locking the boot loader.

tjm46 said:
Thanks, this fixed it. I don't know how many different articles and stuff I read, but I must have missed locking the boot loader.
Click to expand...
Click to collapse
You're very welcome.
So you were able to unlock the bootloader again, update to TWRP 3.0.0.0, and flash a current ROM?

Yeah, flashed TWRP 3.0 then the latest cyanogenmod nightly. Everything works great

tjm46 said:
Yeah, flashed TWRP 3.0 then the latest cyanogenmod nightly. Everything works great
Click to expand...
Click to collapse
Nice work.

How to get back to stock?

My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?

MM MaD said:
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
Click to expand...
Click to collapse
You can do either but ensure two things for avoiding a possible bootloop. One is the TWRP and the other is wiping all except internal storage before flashing the ROM.
You should have the modified TWRP 3.0.2-23.
Wipe, flash ROM and flash TWRP before booting as the existing TWRP is likely to be overwritten by the stock recovery. Speaking from experience!
Though I was going from 3.2.7 to 3.2.8, TWRP was overwritten which I found only after booting and when I tried to get back into recovery.

Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks

jfodra said:
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
Click to expand...
Click to collapse
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)

lekronop said:
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
Click to expand...
Click to collapse
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.

jfodra said:
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
Click to expand...
Click to collapse
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.

lekronop said:
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
Click to expand...
Click to collapse
Oh okay. Thanks a lot for the clarifications.

jfodra said:
Oh okay. Thanks a lot for the clarifications.
Click to expand...
Click to collapse
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems

lekronop said:
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
Click to expand...
Click to collapse
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?

jfodra said:
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
Click to expand...
Click to collapse
Yes it does.. That's the reason I unlock the bootloader as soon as I get a new device

i was on freedom os . i am back on stock oxygen os but i have 2 issues.
1) when i got an update to 3.2.7 it showed in german that there is an update even though the language i chose was english
2) The boot animation shows the freedom os splash screen and then the boots into stock. Ihave got the boot animation of stock os but need instructions on how to flash the zip.
Can someone throw light on the above 2 issues?

Updating Oxygen OS 3.1.2 on stock recovery bricks device

Hi,
I've been running Oxygen OS 3.2.8, rooted, with TWRP fine for a bit. I had downgraded from Oxygen OS Community Beta 9, by using the Full Unbrick Tool (detailed here: http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700) to downgrade to 3.1.2, and then I upgraded to 3.2.8 using the official OTA file, and using the USB ADB sideload in the stock OOS recovery. I did go though the motions of setting up 3.1.2 before updating to confirm that it works.
However after updating to 3.2..8, the phone bricks itself again, and when I boot I get the OnePlus logo for about half a second, and then a black screen with the LED being white. I even tried updating OOS using the OTA updater in Android, and it boots into the recovery, apparently does the update but then bricks itself again!
I can boot into Fastboot fine, but I can't boot into the recovery.
I have noticed that when I boot, because my bootloader is unlocked, I get the screen about the bootloader being unlocked, blah blah blah, but the link to learn more says "g.co/placeholder". After I attempt to update to 3.3.8, I get the proper link, indicating that the firmware has updated in some way.
If I install TWRP straight after using the unbrick tool, I can boot into it fine, and then install CM13 just fine, and it boots. However the fingerprint reader doesn't work, and I assume this is a firmware issue.

Correct, it's a firmware issue. With CM13 you have to use older firmware (from 3.2.4 or older, if I remember correctly).
Sesrch XDA for a thread with firmwares and flash that, done
Sent from my OnePlus 3 using Tapatalk

Explorer23 said:
Correct, it's a firmware issue. With CM13 you have to use older firmware (from 3.2.4 or older, if I remember correctly).
Sesrch XDA for a thread with firmwares and flash that, done
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
I've got a 3.2.4 firmware file, what's the best way of flashing it?
I did attempt to flash this with stock TWRP, but it appeared to brick the device again.
Additionally, when I boot into fastboot mode it doesn't show me the bootloader version.
Someone did suggest using the commands:
Code:
Fastboot erase modemst1​​​
fastboot erase modemst2
after flashing OOS, would this help at all?

Stock TWRP should work with that ... But you may try modified 3.0.2.1-28 by eng.stk, nothing to lose (it works with ALL ROMs and firmwares to date).
Dunno about that other suggestion, I think that's more related to IMEI problems, but I'm not 100% sure.
Sent from my OnePlus 3 using Tapatalk

I think I'm going to book a session with OmePlus and see if they can unbrick it properly, or just return it to O2 where I bought the phone.
I still find it perplexing that updating to 3.2.8 from 3.1.2 using the Android OTA updater bricks the phone!

Issues with lastest OTA update

Hi,
I use a RMX2063 since last month, rooted with the TWRP method I found in this forum since day 0. I tried to install the lastest OTA update, that was released last week (RMX2063 _11_A.22), but I have issues to keep magisk working.
Either I do a clean install or a dirty flash, I enter into a bootloop every time I flash lastest magisk version (20.4). Otherwise, the phone works OK if I reflash the OTA and use it without rooting.
Any solutions to that, so I don´t have to downgrade the phone?

Jpigas said:
Hi,
I use a RMX2063 since last month, rooted with the TWRP method I found in this forum since day 0. I tried to install the lastest OTA update, that was released last week (RMX2063 _11_A.22), but I have issues to keep magisk working.
Either I do a clean install or a dirty flash, I enter into a bootloop every time I flash lastest magisk version (20.4). Otherwise, the phone works OK if I reflash the OTA and use it without rooting.
Any solutions to that, so I don´t have to downgrade the phone?
Click to expand...
Click to collapse
It doesn't work. In order for me to get root afterwards is to flash the latest for rmx2061, extract the boot.img, modify it with magisk and flash the modified boot.img afterwards

mepadiernos said:
It doesn't work. In order for me to get root afterwards is to flash the latest for rmx2061, extract the boot.img, modify it with magisk and flash the modified boot.img afterwards
Click to expand...
Click to collapse
First of all, thx for the quick response.
I think I already tried that, you mean flashing the modified boot.img via TWRP? (install -> install image -> "boot")?
After that I had another bootloop ("system image is destroyed" realme message)

Jpigas said:
First of all, thx for the quick response.
I think I already tried that, you mean flashing the modified boot.img via TWRP? (install -> install image -> "boot")?
After that I had another bootloop ("system image is destroyed" realme message)
Click to expand...
Click to collapse
I was actually referring to flashing via fastboot.
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse

mepadiernos said:
I was actually referring to flashing via fastboot.
Click to expand...
Click to collapse
The phone enters bootloop anyway (system destroyed), but thank you anyway @mepadiernos. Any other idea?

Jpigas said:
The phone enters bootloop anyway (system destroyed), but thank you anyway @mepadiernos. Any other idea?
Click to expand...
Click to collapse
Hmmm, I do remember that the twrp provided here for the Realme 6 Pro breaks encryption after I upgraded to .27 so I had to flash the .20 for rmx2061 via stock recovery. I had to put the ozip in the microsd. I believe that will factory reset the phone. When it does I went through the process of setting up my phone sans root. I installed magisk manager and proceeded to patch the extracted boot image from the ozip, the update for the rmx2061, and flashing via fastboot. So, I have root but no twrp.

mepadiernos said:
Hmmm, I do remember that the twrp provided here for the Realme 6 Pro breaks encryption after I upgraded to .27 so I had to flash the .20 for rmx2061 via stock recovery. I had to put the ozip in the microsd. I believe that will factory reset the phone. When it does I went through the process of setting up my phone sans root. I installed magisk manager and proceeded to patch the extracted boot image from the ozip, the update for the rmx2061, and flashing via fastboot. So, I have root but no twrp.
Click to expand...
Click to collapse
It doesn´t worked for me, buy, anyway, I´m planning to downgrade due to the very high power consumption. Nowadays the phone struggles to reach 3-4h screen on, versus the 6h I managed to reach on previous version. What do you guys think about it?