Database Develop

Not a noob, but still confused.

I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.

Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.

mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
FWIW: I would recommend that you:
1) Unlock bootloader
2) Decide if you want uncrypted kernel, or not (since it wipes data, just like unlocking bootloader).
3) Fastboot flash TWRP recovery.
4) Download SuperSU .zip and flash it in recovery.
5) Now, when a new OTA comes out, they usually show up here > http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493
6) You can download your current factory image here > https://developers.google.com/android/nexus/images
7) Unzip your current factory image. Fastboot flash the system.img and that will unroot and restore the stock recovery.
8) Fastboot flash the stock boot.img if you have a custom kernel (or an unencrypted stock kernel).
9) Relax and wait for the OTA.

RW-1 said:
Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.
Click to expand...
Click to collapse
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!

mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.

mad_rulzzz said:
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!
Click to expand...
Click to collapse
What he just explained is what I said, unroot and take the OTA.... He listed how as well.

RW-1 said:
What he just explained is what I said, unroot and take the OTA.... He listed how as well.
Click to expand...
Click to collapse
Yup.

@rw_1 @cam30era thanks guys

I would do what gee2012 said.
From what I have seen the OTA and the images are released pretty close together.
Instead of flashing images to get back to stock and waiting for the OTA. and then re-rooting
Just download the image files from Google. Manually flash all the files EXCEPT user data if you want to keep your data.
Re-root.
You are now updated and don't have to wait for OTA.
Either way works so it depends on which you are happier with.

mad_rulzzz said:
@rw_1 @cam30era thanks guys
Click to expand...
Click to collapse
Welcome. And BTW: there's a button for that.

gee2012 said:
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.
Click to expand...
Click to collapse
Just to be sure I understood right:
If I don't care about app data or settings ( I have titanium backup),
1)I can just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
one last thing... Does Google upload factory images after each OTA happens?

cam30era said:
Welcome. And BTW: there's a button for that.
Click to expand...
Click to collapse
My BAd!!

mad_rulzzz said:
If I don't care about app data or settings ( I have titanium backup),
1)Can I just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
Does Google upload factory images after each OTA happens? i.e; If Nexus 6 receives an OTA to 5.2, will they upload the 5.2 factory image soon?
Click to expand...
Click to collapse
When you unlock the bootloader it will wipe the contents of your SD card. Make sure it is backed up on your PC.
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.

cam30era said:
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.
Click to expand...
Click to collapse
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.

mad_rulzzz said:
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.
Click to expand...
Click to collapse
Correct. M is intended for T-Mobile. My point, though, is that Google doesn't always, 100% of the time publish a factory image for every OTA.

[HOW TO] Return to stock

Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Motorola Z2 Force users! Your issues will be resolved!
Reasons for using this method:
If you haphazardly flashed a ROM, and now can't boot.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock.
You then can update.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:
Motorola Firmware Team for the zips

Great, So you've read why you might have borked your phone!
Now, let's get it fixed! Below is the link to the only flashall bat file I currently have. This is a simple process to do. There are some requirements though.
Requirements:
Correct drivers (ADB and fastboot is included in the utilities zip if you don't have minimal adb and fastboot installed, or don't have the SDK.)
Over 4GB of RAM.
How to fix your phone:
Download the Utilities zip
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
This process can take up to 10-15 minutes depending on USB connection and your PC
Disclaimer: I did not personally test the zips below besides the Sprint and T-Mobile ones. These are the official Firmware links from the Motorola Firmware Team. My only contribution is this thread and the utilities zip.
Disclaimer 2: it is never suggested to flash a zip not intended for your device/major patch version. If you're on Oreo, DO NOT FLASH NOUGAT. (I flashed T-Mobile to my Sprint phone for testing purposes and so I can tell you what it does. I lost all sim functionality and had to do some wonky stuff to get my phone back to working shape... Word of advise: don't do it.)
Disclaimer 3: if you have minimal adb and fastboot or the Android SDK, please be sure you update to the latest fastboot. The exe files included in the zip are for those who don't have a development environment set up.
Downloads:
Flash All Utilities
AT&T Oreo Flash All
Sprint Oreo Flash All
T-Mobile Flash All (Not official download link, but official files, See here)
USC (check version) Flash All
Verizon Flash All
NOTE: yes, it's in the Z2 play folder. Motorola Firmware Team did not make another folder for our device. Check the file name. It has "Nash" specifying the Z2 force. If you ask why it's in the Play folder, I will not respond.

If you have any other official links, I will add to second post and give proper credits to who found the zip. Only perm links like the AFH ones I posted.

Uzephi said:
First: The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA. This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
This zip will fix that and put you back to stock on the "August" security patch (September update). You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits: Motorola Firmware Team for the zips
Me for modifying the zip to fix oem.img issue on B partitions and turning the xml into a simple flash all.bat
Note: I am mobile and I will clean up the OP and second post when I get time @ home
Click to expand...
Click to collapse
I was going to add yours in but kinda got busy

Thanks for this! I flashed a modified boot.img for root to get my phone unlocked, and flashed the stock kernel back, but I couldn't update to the September patch. After flashing this, updates are working fine. A bit of a lifesaver!

full circle...
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!

esuormai said:
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
Click to expand...
Click to collapse
I don't take donations, just pay it forward! Thanks for the offer though.

NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE

WeUseLord- said:
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
Click to expand...
Click to collapse
Added in requirements, thank you for verifying that.

Uzephi said:
Added in requirements, thank you for verifying that.
Click to expand...
Click to collapse
Okay thanks OP

when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?

cooleoboom5 said:
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
Click to expand...
Click to collapse
That is a "permanent" flag that triggers when you flash something unsigned and not from Motorola. I.E. custom boot image for root. Reason it's in quotes is because we don't know how to return it back or if we even can.

moto z2 force
WeUseLord- said:
Okay thanks OP
Click to expand...
Click to collapse
where do you download the bat file from

irule1977 said:
where do you download the bat file from
Click to expand...
Click to collapse
It's in the zip

So Sprint Z2 can't get GSM unlocked by flashing ROMs from other carriers? Any idea how it can be unlocked?

How to get back to software status official in bootloader menu? I did managed to do it with T-Mobile version but cant get that from this one.

Uzephi said:
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Sprint Motorola Z2 force users! Your issues will be resolved!
First: Our phone differences
The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA.
This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
Reasons for using this method:
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock on the "August" security patch (September update).
You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:Motorola Firmware Team for the zips
Versions currently available:
NCXS26.122-59-8-6
NCX26.122-59-8
NCX26.122-51
Versions on OTA but no firmware files available:
NCXS26.122-59-8-9
Click to expand...
Click to collapse
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.

robdevil said:
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
Click to expand...
Click to collapse
I would only release something I can test. I don't have TMobile service, so I won't be releasing TMobile only firmware. There is a thread by joemossjr for TMobile flashall.

A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.

hackenggr said:
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
Click to expand...
Click to collapse
My Sprint model has the -03 identifier. You should be safe if the bootloader is unlocked. Needs that to flash this

51.1.A.11.51 changelog?

Does anyone who get it see a difference?
Could you provide the output of
Code:
fastboot getvar all
So we see, if the bootloader got updated and I can provide TWRP and XPeria AOSP.
Then the custom rom development can start.

Stock Android 8.0 September
(bootloader) version-bootloader:1310-7079_X_Boot_SDM845_LA1.0_O_60
Bootloader got an update and until Sunday I will upload a new Sony AOSP 8.1 build.
If it is bootable, I will release a new TWRP build.

Hmm, keep getting ”Could not install" from the India (IN) variant. Guess I'll try again tomorrow.
Anyone successfully install it and if so, with which region?

eelpout said:
Hmm, keep getting ”Could not install" from the India (IN) variant. Guess I'll try again tomorrow.
Anyone successfully install it and if so, with which region?
Click to expand...
Click to collapse
German H8266 on my H8296.

MartinX3 said:
German H8266 on my H8296.
Click to expand...
Click to collapse
Hello do you think I can possibly flash H8216 firmware to my H8276 just as you flash H8226 to your H8296?

nolihowell said:
Hello do you think I can possibly flash H8216 firmware to my H8276 just as you flash H8226 to your H8296?
Click to expand...
Click to collapse
You should flash H8266, because the H8276 is dualsim, too.
H8216 would work fine, but the second sim is dead.
The external sdcard maybe, too.

MartinX3 said:
German H8266 on my H8296.
Click to expand...
Click to collapse
OTA? Or did you flash it?
Maybe it's time for me to switch. ?

eelpout said:
OTA? Or did you flash it?
Maybe it's time for me to switch. ?
Click to expand...
Click to collapse
Xperifirm and its building new flasher
But it will be like a factory reset.
Buuut it will work like a charm. And you get your updates faster.
But aren't you from Canadia?
Maybe the Canadian software is optimized/calibrated for your mobile network technology. :silly:

Does this update just bring security updates?

dibdin said:
Does this update just bring security updates?
Click to expand...
Click to collapse
And some small fixes and improvements.

MartinX3 said:
Xperifirm and its building new flasher
But it will be like a factory reset.
Buuut it will work like a charm. And you get your updates faster.
But aren't you from Canadia?
Maybe the Canadian software is optimized/calibrated for your mobile network technology. :silly:
Click to expand...
Click to collapse
nah, U.S. but I grew up in Minnesota, which is close to Canada.
IN doesn't have problems with update speed, it's within hours of DE, but this is the second time the OTA has continuously failed. Though other times it's been fine.
OK, I see you're cheating and not getting it OTA.
Flashing another region's firmware though shouldn't require a full reset, as long as one removes the user data sin file from the folder.

dibdin said:
Does this update just bring security updates?
Click to expand...
Click to collapse
A new bootloader.
Which allows custom ROMs and twrp, which allows the DRM fix.

eelpout said:
nah, U.S. but I grew up in Minnesota, which is close to Canada.
IN doesn't have problems with update speed, it's within hours of DE, but this is the second time the OTA has continuously failed. Though other times it's been fine.
OK, I see you're cheating and not getting it OTA.
Flashing another region's firmware though shouldn't require a full reset, as long as one removes the user data sin file from the folder.
Click to expand...
Click to collapse
Since I switched to h8266 in April or May I install only OTA Delta updates.

MartinX3 said:
A new bootloader.
Which allows custom ROMs and twrp, which allows the DRM fix.
Click to expand...
Click to collapse
oh, hmmm. since it's a new bootloader, is it a risk to switch firmware regions?

eelpout said:
oh, hmmm. since it's a new bootloader, is it a risk to switch firmware regions?
Click to expand...
Click to collapse
Of course not.
It is an universal bootloader.

@MartinX3 Just flashed the *51 firmware and my BL version string is:
Code:
1310-7079_X_Boot_SDM845_LA1.0_O_60
I'm trying to boot AOSP Oreo, I just built today, but no success so far.
Have you got better luck booting aosp?

nasko_spasko said:
@MartinX3 Just flashed the *51 firmware and my BL version string is:
I'm trying to boot AOSP Oreo, I just built today, but no success so far.
Have you got better luck booting aosp?
Click to expand...
Click to collapse
Try my build in the twrp thread.
Someone told me, that he successfully booted the old aosp build.
So I made one with the newest sources.
A manual how to flash is there, too.
Maybe you need the OEM file from the last build.

MartinX3 said:
Try my build in the twrp thread.
Someone told me, that he successfully booted the old aosp build.
So I made one with the newest sources.
A manual how to flash is there, too.
Maybe you need the OEM file from the last build.
Click to expand...
Click to collapse
Ops! I apparently forgot to flash dtbo and vbmeta. Boots!!!

nasko_spasko said:
Ops! I apparently forgot to flash dtbo and vbmeta. Boots!!!
Click to expand...
Click to collapse
:laugh::silly:
Any errors, missing features?
How is the camera with the open camera app?
ADB? Usb? Touch? Sound?
The new 9.0 OEM image is compatible?

MartinX3 said:
:laugh::silly:
Any errors, missing features?
How is the camera with the open camera app?
ADB? Usb? Touch? Sound?
The new 9.0 OEM image is compatible?
Click to expand...
Click to collapse
Well the 8.1 is not much of a usable one, i'll try the 9.0 after the build is complete, the touchscreen is not working as expected, it's picked up as a touchpad the UI is navigated with mouse, it seems that the graphics acceleration is not working (gralloc?), brightness is not adjustable. RIL works(sort of), calls work (mic produces robotic sound), Data works. ADB is not working and Developer Options menu crashes the settings app, Sleep not working, device gets quite hot over time(PM?).
Sound works. Camera is not accessible(just gray screen with the navbar at the bottom) It's fast as hell, though... That works SDM845 (rock)

[HD1925]PSA: WARNING: Unlocking the bootloader or doing fastboot -w will KILL OTA!

ntzrmtthihu777 said:
The OnePlus 7t Pro 5g McLaren (at least the one from T-Mobile; I don't know about other versions) has a crucial issue
in how it handles factory resets/wiping userdata, and OTA updates.
The stock rom contains a file, `/data/reserver/reserve.img`, which is an ext4 image mounted at `/system/reserve/`.
It contains a number of OnePlus specific APKs and is not particularly required for a functioning phone (though I
believe it may have stuff which is preventing my fingerprint from working, but that is speculation), but this image
is updated by standard OTA updates. As there is no way to read this image without a rooted device, and there is
currently no way to root your device without unlocking your bootloader (which would nuke userdata), any 'master
reset' (as described here) or `fastboot -w` or `fastboot erase userdata` will kill your ability to take OTA updates.
[edit start]
Apparently the tmo method will not kill it. Only the unlocking bootloader or wiping via fastboot should.
[edit end]
The OTA updates given out are what are called `delta` updates, which are a record of changes to filesystems and
not whole filesystems in and of themselves. As such, any change to the expected filesystem images (system, vendor,
this reserve image, etc) will kill your ability to take OTA updates.
If you're having issues OTA updating, you can check if this is your problem by checking if this file still exists
(`adb shell ls /data/reserve/` should return reserve.img) or by grepping your logcat during update attempts,
checking for sha256 hash errors on the 'reserve' partition.
Click to expand...
Click to collapse
TL;DR: don't unlock or erase userdata on this image, or you'll never get another update until OnePlus fixes this.
https://forums.oneplus.com/threads/t-mobile-7t-pro-5g-usa-ota-10-0-19hd61cb.1172725/
https://www.reddit.com/r/tmobile/comments/eq4or6/security_disclosure_master_reset_procedure_on/

I sadly can confirm this. :crying:

Yes this is what it looks like. See attached.

Oh wow. Isn't that just lovely.

Can some one confirm it on hd1913 model?

sagiag said:
Can some one confirm it on hd1913 model?
Click to expand...
Click to collapse
No, I think you're good on those, as there is a full software package on the oneplus site you can use to restore.
the HD1925 models do not, so we're screwed until something gets fixed/figured out.

Thank you very much!

Finally,, I know why I can't update. Thanks.
Will TMobile tech fix this if you send them your phone?

La_anvil said:
Finally,, I know why I can't update. Thanks.
Will TMobile tech fix this if you send them your phone?
Click to expand...
Click to collapse
No idea personally. Someone has mentioned something to that effect in the telegram
chat.

Hopefully this means a MSM tool coming out faster. I'm tired of not being able to update at all.

CloseCoder said:
Hopefully this means a MSM tool coming out faster. I'm tired of not being able to update at all.
Click to expand...
Click to collapse
Hope so. honestly its just a case of bad design on OnePlus's part. What's the first thing the help desk going to tell
you to do if your phone isn't working? Exactly, wipe /data. And now no updates for you.

Just read on OnePlus forums someone called tmobile and their solution was to send out a new phone....

ntzrmtthihu777;8152337 Someone has mentioned something to that effect in the telegram
chat.[/QUOTE said:
What channel?
Click to expand...
Click to collapse

Android Police picked up the story:
https://twitter.com/AndroidPolice/status/1218982470822924289
https://www.androidpolice.com/2020/...laren-breaks-your-ability-to-install-updates/

T-Mobile get your act together and fix it! ??

ntzrmtthihu777 said:
Hope so. honestly its just a case of bad design on OnePlus's part. What's the first thing the help desk going to tell
you to do if your phone isn't working? Exactly, wipe /data. And now no updates for you.
Click to expand...
Click to collapse
Pretty sure that's on TMO not oneplus

For those who have a problem with OTA, what build number do you show on your phone ?

justthefacts said:
For those who have a problem with OTA, what build number do you show on your phone ?
Click to expand...
Click to collapse
10.0.16.HD61CB for me.

benny3 said:
Pretty sure that's on TMO not oneplus
Click to expand...
Click to collapse
Nah. its a bit of both. OnePlus was stupid for putting 'reserve.img' inside userdata,
but T-Mobile is even stupider for not implementing the fix non-TMO OnePlus
devices use, which is to switch to full OTA updates.

(Guide) How to dump your ROM Without PC

Hi guys, as We know, BS3 don't have stable global rom yet for chinese version. If have some good soul here, please follow this tutorial and upload your global rom stable for communnity.
The step is very easy, fallow this guide to unlock and flash twrp: https://forum.xda-developers.com/bl...ckshark-3-3-pro-3s-unlock-bootloader-t4141537
After unlock and flash twrp, make sure to logout your Mi Account.
Go to TWRP> backup > select all box (don't select data user and EFS) wait the proccess finish. After finish, go to PC plug the device, copy your twrp folder to your pc, compact it with winrar and upload it. Share with us.
With this way we can get legit global rom for BS3 (normal version).

are this rooms global version of black shark 3?
https://mifirm.net/model/kle.ttt
https://romprovider.com/xiaomi-flash-shark-3-firmware/

maverickgtm said:
are this rooms global version of black shark 3?
https://mifirm.net/model/kle.ttt
https://romprovider.com/xiaomi-flash-shark-3-firmware/
Click to expand...
Click to collapse
global but beta. won't receive ota update
---------- Post added at 03:23 AM ---------- Previous post was at 03:18 AM ----------
hehk1234 said:
Hi guys, as We know, BS3 don't have stable global rom yet for chinese version. If have some good soul here, please follow this tutorial and upload your global rom stable for communnity.
The step is very easy, fallow this guide to unlock and flash twrp: https://forum.xda-developers.com/bl...ckshark-3-3-pro-3s-unlock-bootloader-t4141537
After unlock and flash twrp, make sure to logout your Mi Account.
Go to TWRP> backup > select all box (don't select data user and EFS) wait the proccess finish. After finish, go to PC plug the device, copy your twrp folder to your pc, compact it with winrar and upload it. Share with us.
With this way we can get legit global rom for BS3 (normal version).
Click to expand...
Click to collapse
Maybe no one will do because they could be afraid of getting bricked or afraid of not receiving ota updates anymore. If only bs team will share it (and not sell), we won't have this problem. Now I hope they fail spectacularly on the next update or in JoyUI12 so they wont have a choice but to release full rom over ota. Imagine that.

the method is very easy ;-; , sad

I would love to dump my rom, but the thing is, this TWRP recovery won't guarantee the safety of my device. I just bought this and I check the link and the files that were put in there, I'm not sure if I should risk flashing a modified TWRP created by an unknown dev, I also would not risk flashing a Chinese TWRP recovery not knowing the compatibility of Global devices to CN ones. You're right, it is easy as point click and type commands, but the risk is high also and bricking the phone is too easy too. I hope Blackshark really opens up on devs like what Asus is doing on their ROG3. This would make their device a lot more famous, allowing developers collaborate with each other. If I can't figure out a safe way to root and install custom recovery at least in the next few months, I might sell this device, too bad this has serious hardware that can rival flagships but, it's a deal breaker for us not to have custom recovery backups and rooting too. Ecosystem is too restrictive. I dunno what these chinese folks were thinking when they made this device.

sushi_kun said:
I would love to dump my rom, but the thing is, this TWRP recovery won't guarantee the safety of my device. I just bought this and I check the link and the files that were put in there, I'm not sure if I should risk flashing a modified TWRP created by an unknown dev, I also would not risk flashing a Chinese TWRP recovery not knowing the compatibility of Global devices to CN ones. You're right, it is easy as point click and type commands, but the risk is high also and bricking the phone is too easy too. I hope Blackshark really opens up on devs like what Asus is doing on their ROG3. This would make their device a lot more famous, allowing developers collaborate with each other. If I can't figure out a safe way to root and install custom recovery at least in the next few months, I might sell this device, too bad this has serious hardware that can rival flagships but, it's a deal breaker for us not to have custom recovery backups and rooting too. Ecosystem is too restrictive. I dunno what these chinese folks were thinking when they made this device.
Click to expand...
Click to collapse
don't have error. If you would want revert back for stock recovery, just lock your bootloader again and it will revert back for original system.

hehk1234 said:
don't have error. If you would want revert back for stock recovery, just lock your bootloader again and it will revert back for original system.
Click to expand...
Click to collapse
Yours is a CN Model. Mine isn't, this is Global already. I haven't studied the phone differences yet so I can't comment too much, I'll have to check how to get stock images to revert to original system. There's no known downloadable image right?

sushi_kun said:
Yours is a CN Model. Mine isn't, this is Global already. I haven't studied the phone differences yet so I can't comment too much, I'll have to check how to get stock images to revert to original system. There's no known downloadable image right?
Click to expand...
Click to collapse
There's none. But you have it on your phone. And if you know how, maybe you can pull it.

sushi_kun said:
Yours is a CN Model. Mine isn't, this is Global already. I haven't studied the phone differences yet so I can't comment too much, I'll have to check how to get stock images to revert to original system. There's no known downloadable image right?
Click to expand...
Click to collapse
In short word, you need use this tool https://forum.xda-developers.com/an...ev-img-patch-tools-sdat2img-ota-zips-t3640308 and have pc with linux. For generate new system and vendor need use standard command from readme of tool, for boot need use this command ./ApplyPatch boot.img - (sha1 of new image) 100663296 (sha1 old image) boot.img.p

Hi I will do it today I got global bs3 and I will provide twrp system backup

Mr. Fros one said:
Hi I will do it today I got global bs3 and I will provide twrp system backup
Click to expand...
Click to collapse
Hello can you share the file thank you

It would be awesome

Mr. Fros one said:
Hi I will do it today I got global bs3 and I will provide twrp system backup
Click to expand...
Click to collapse
hi bro
do we have a good news here?