Develop Bugs

Wrong build fingerprint when flashing ota

I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please

ImjuzCY said:
I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please
Click to expand...
Click to collapse
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358

jj14 said:
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358
Click to expand...
Click to collapse
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be

ImjuzCY said:
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be
Click to expand...
Click to collapse
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this

jj14 said:
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this
Click to expand...
Click to collapse
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now

I tried everything and still get wrong build fingerprint when trying to flash the 5.0
ImjuzCY said:
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now
Click to expand...
Click to collapse
Hello!
Really want to flash the OTA without a total wipe.
First flashed it from TWRP 2.8.1.0 and got the wrong build finger print says I have Flo:4.3/JSS15Q/779366 and it expects KTU84P/1227136
Then using WugFresh 1.9.4 flashed stock recovery so I could sideload then encountered the whole adb disappearing in recovery - eventually solved that and finally managed to adb sideload saw my screen saying it was installing the update using the stock recovery - YAY! It was short lived as the stock recovery screen told me the exact same thing that TWRP had told me.
I looked at my build.prop and it says my ro.build.fingerprint=google/razor/flo:4.4.4/KTU84P/1227136. user/release-keys
Can someone enlighten me? I've wasted so much time on this I would love some keen insight - PLEASE!!
Thanks for any and all help!
Edbogue

Google changed the way OTAs work in 5.0. You will usually not be able to flash a OTA if your OS is modified. Means no custom recovery or root. You will have to flash your tab back to stock kitkat.
Before it would patch individual file blocks, now it patches the whole system partition as a blob. Read more http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/

Workaround that helped me upgrade
Following the steps below seems to have done the trick for me. My issue was that Android 5.0 updates the system partition all in one go now, rather than each file separately. Following those steps will unroot your device but will allow you to install the OTA updates.
So follow these steps to refresh your current Android version (e.g 4.4.4) then use OTA or adb sideload to update to, for example, 5.0.
This will not wipe user data or the cache.
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
I would post my source, but as I only just joined to say what helped me, I'm not allowed to post links I'll just say Google "flashing-a-stock-android-image-without-wiping-user-data" and (as of 19/11/2014) it's the top result.

Please continue here: http://forum.xda-developers.com/nexus-4/help/android-5-0-0-to-5-0-1-update-t2972371#post57515317

Finally finally!!! A fix!
Raingram said:
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
.
Click to expand...
Click to collapse
Thank you Raingram! This worked perfectly!

Updating Using Factory Images And Fastboot Mode

Hi all,
Within the last month I successfully unlocked my 5x, rooted it, installed a custom recovery and have kept it on stock ROM with a custom kernel (ElementalX) and some minor tweaks (AdAway, Viper4Android). So far, so great.
However, when I was locked and unrooted, I used to use ADB and the sideload OTA function to update to the newest builds, usually within 3-5 days after the binaries first drop.
Now, with the desire to remain on an updated stock ROM, keep root, custom recovery, and the minor tweaks noted above, I wanted some confirmation from the great minds here as I navigate Heisenberg's thread and use fastboot on my own for the first time.
What I've done so far: Download and extract the binaries from my current build (MHC19Q) as well as today's new build (MTC19T).
Compared them and see there is a new radio that I'll have to flash.
I want to keep my custom recovery (TWRP) and boot image (ElementalX kernel), so I believe I leave those untouched.
So, my process here is:
1. Boot into bootloader mode. Open a command prompt and confirm via fastboot devices that my device is connected/recognized through USB.
2. Enter "fastboot flash radio {insert radio.img here}"
3. Enter fastboot reboot-bootloader
4. Enter "fastboot erase cache"
5. Enter "fastboot flash cache {insert cache.img here}", repeat step 3
6. Enter "fastboot flash system {insert system.img here}, repeat step 3
7. Enter "fastboot flash vendor {insert vendor.img here}
My 2 questions are - will this process above succeed in updating my security/build and leave my recovery and kernel untouched? And will I keep root and modifications, or have to reflash TWRP, SuperSU, AdAway, Viper4Android, etc.?
Thanks for the patience, all. Once I do this once or twice, I'm sure it'll become old hat!

Moonboots said:
Hi all,
Within the last month I successfully unlocked my 5x, rooted it, installed a custom recovery and have kept it on stock ROM with a custom kernel (ElementalX) and some minor tweaks (AdAway, Viper4Android). So far, so great.
However, when I was locked and unrooted, I used to use ADB and the sideload OTA function to update to the newest builds, usually within 3-5 days after the binaries first drop.
Now, with the desire to remain on an updated stock ROM, keep root, custom recovery, and the minor tweaks noted above, I wanted some confirmation from the great minds here as I navigate Heisenberg's thread and use fastboot on my own for the first time.
What I've done so far: Download and extract the binaries from my current build (MHC19Q) as well as today's new build (MTC19T).
Compared them and see there is a new radio that I'll have to flash.
I want to keep my custom recovery (TWRP) and boot image (ElementalX kernel), so I believe I leave those untouched.
So, my process here is:
1. Boot into bootloader mode. Open a command prompt and confirm via fastboot devices that my device is connected/recognized through USB.
2. Enter "fastboot flash radio {insert radio.img here}"
3. Enter fastboot reboot-bootloader
4. Enter "fastboot erase cache"
5. Enter "fastboot flash cache {insert cache.img here}", repeat step 3
6. Enter "fastboot flash system {insert system.img here}, repeat step 3
7. Enter "fastboot flash vendor {insert vendor.img here}
My 2 questions are - will this process above succeed in updating my security/build and leave my recovery and kernel untouched? And will I keep root and modifications, or have to reflash TWRP, SuperSU, AdAway, Viper4Android, etc.?
Thanks for the patience, all. Once I do this once or twice, I'm sure it'll become old hat!
Click to expand...
Click to collapse
Yes, that will keep your recovery untouched, however you might want to wait until flar2 and/or other kernel devs confirm there are no changes to the kernel before you upgrade your system. More often than not, there are improvements to the kernel source.
About Adaway, Viper4Android, etc... I'm almost sure you will have to reflash those, as they are part of the system.
I am myself waiting for confirmation about the kernel stuff, but in the meantime will flash bootloader and radio.

redsmith said:
Yes, that will keep your recovery untouched, however you might want to wait until flar2 and/or other kernel devs confirm there are no changes to the kernel before you upgrade your system. More often than not, there are improvements to the kernel source.
About Adaway, Viper4Android, etc... I'm almost sure you will have to reflash those, as they are part of the system.
I am myself waiting for confirmation about the kernel stuff, but in the meantime will flash bootloader and radio.
Click to expand...
Click to collapse
Excellent, thank you for the quick reply. I'll put a subscription on the ElementalX Kernel thread and keep an eye out before making any changes.
Also, if I'm reading the updates correctly, the bootloader remains unchanged at version bhz10m. In your experience, are there changes under the hood there that don't appear in the version number, or is there no need to flash the "new" bootloader, as it's identical?

I would like to have a sort of ota to install just the updated files that leaves my system mod untouched. But I think there is no way to keep everything...

redsmith said:
Yes, that will keep your recovery untouched, however you might want to wait until flar2 and/or other kernel devs confirm there are no changes to the kernel before you upgrade your system. More often than not, there are improvements to the kernel source.
About Adaway, Viper4Android, etc... I'm almost sure you will have to reflash those, as they are part of the system.
I am myself waiting for confirmation about the kernel stuff, but in the meantime will flash bootloader and radio.
Click to expand...
Click to collapse
To be a little bit more specific, you have to flash again whatever you have flashed so far.
Adaway is an app, you don't have to flash it nor reinstall.
Same for xposed, you have to flash over the framework, but your installed modules will remain and work once you have reflashed xposed for instance.

exploreresp said:
To be a little bit more specific, you have to flash again whatever you have flashed so far.
Adaway is an app, you don't have to flash it nor reinstall.
Same for xposed, you have to flash over the framework, but your installed modules will remain and work once you have reflashed xposed for instance.
Click to expand...
Click to collapse
Thank you for the clarification. I've been keeping an eye on the ElementalX thread and it appears everything works with the newest build without a need for an update to the kernel.
With that being said, do I need to flash the new boot.img and recovery.img, then re-flash TWRP and ElementalX, or can I just not push the new binaries for boot and recovery, and just do radio, system, and vendor?

Moonboots said:
Thank you for the clarification. I've been keeping an eye on the ElementalX thread and it appears everything works with the newest build without a need for an update to the kernel.
With that being said, do I need to flash the new boot.img and recovery.img, then re-flash TWRP and ElementalX, or can I just not push the new binaries for boot and recovery, and just do radio, system, and vendor?
Click to expand...
Click to collapse
Don't think it'll hurt to try
I already avoided to flash the recovery img last month but it still got patched and had to flash TWRP again so I'm not sure...
Anyway, don't think this May update is worth all the trouble... Only security updates that haven't even been reported by users. Unless you're really worried about smtg, this won't bring you anything.

exploreresp said:
Don't think it'll hurt to try
I already avoided to flash the recovery img last month but it still got patched and had to flash TWRP again so I'm not sure...
Anyway, don't think this May update is worth all the trouble... Only security updates that haven't even been reported by users. Unless you're really worried about smtg, this won't bring you anything.
Click to expand...
Click to collapse
Confirming here for the group and anyone that hasn't used fastboot before - totally easy and worked like a charm. I know you mentioned there wasn't much to the May update but I still wanted to do it as an academic exercise for myself so I know how to do it in the future.
I flashed the new radio.img, vendor.img and system.img. Bootloader stayed the same. Recovery held at TWRP and the kernel (boot.img) patched over ElementalX on first boot. I flashed SuperSU, ElementalX and the Viper4Android drivers and everything was back up and running, fully updated. The whole thing took about 15 min.
Thanks for the help and encouragement, all.

Unofficial TWRP based on v4.88B - WiFi working, Magisk Rootable

*IT IS FOR UNLOCKED BOOTLOADERS ONLY*
Voila ..
Alas TWRP is working on Nokia 8 NB1 based on v4.88B kernel. Wifi and Magisk root both are working on my mobile. Please and report if it is working for you as well.
Download:
https://mega.nz/#!nRgVWKqB!fWx4zO1f19Shs_I8Thkw4ycsZMMMmSYP24cK0MHIBlM
Flash:
adb reboot bootloader
fastboot flash boot_a TWRP_NB1_boot_v2.img
fastboot reboot
Click to expand...
Click to collapse
If working well, also flash boot_a partition as well.
Then following below thread to root it using MagiskManager
https://forum.xda-developers.com/nokia-8/development/pre-rooted-boot-image-nokia-nb1-v4-88b-t3798063
Check Following Post for Update:
https://forum.xda-developers.com/showpost.php?p=77307135&postcount=74
WARNING: Don't change boot slot using TWRP . I am not responsible if you brick your phone.

Many thanks!
Does this mean if you have this IMG, you can flash after any other (even older) IMGs without verify check?
With fastboot and OST LA from here?
That would be a fantastic news!!! :good:

Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.

head66 said:
Many thanks!
Does this mean if you have this IMG, you can flash after any other (even older) IMGs without verify check?
With fastboot and OST LA from here?
That would be a fantastic news!!! :good:
Click to expand...
Click to collapse
Didn't checked by flashing it. But, logically yes. Though system partition is still encrypted. That may cause an issue. But for custom ROM developers - it can be a start. Provided - your bootloader is unlocked.

KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
Hey,
maybe that can help u.
Fastboot need Admin permissions on windows open a CMD as Admininstator.
On Linux just login into user root.

WORKING
Image is working! Thanks a lot!
Magisk is also working after patch. (With WiFi)

KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
Did you checked if USB debugging is on in the developer settings?
Powered by View 10

KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
I have it problem on Windows 10 too. If you want very strong, download any Linux-based LiveCD, flash it on USB and load. After this install adb and fastboot from LineageOS site (delete space after "https://" https:// wiki.lineageos.org/devices/bacon/build) and run commands.
P.S.: I am sorry for my bad English, but I hope help you

Wow, you are a genius! So glad to see twrp on our Nokia 8 xD but with encrypted /system. Does it mean nandroid backup is not possible at the moment? Also, with your magisk patched kernel, can i flash over or do i need to first flash twrp then reroot with your method?

corpsegrinder62 said:
Wow, you are a genius! So glad to see twrp on our Nokia 8 xD but with encrypted /system. Does it mean nandroid backup is not possible at the moment? Also, with your magisk patched kernel, can i flash over or do i need to first flash twrp then reroot with your method?
Click to expand...
Click to collapse
Flash TWRP img, then re-root using Magisk method provided in the URL.
Created another version of TWRP. Now /data is browsable, but showing garbled file names So, nanodroid is still unachievable. Don't have a backup phone, so could not take the risk of loosing my data, else could have un-encrypt ICE filesystem encryption and could have build a stock based ROM without encrypted partition.

bidhata said:
Flash TWRP img, then re-root using Magisk method provided in the URL.
Created another version of TWRP. Now /data is browsable, but showing garbled file names So, nanodroid is still unachievable. Don't have a backup phone, so could not take the risk of loosing my data, else could have un-encrypt ICE filesystem encryption and could have build a stock based ROM without encrypted partition.
Click to expand...
Click to collapse
Thanks bro. You are making tremindous progress on this phone though. Hopefully you inspire other devs to jump the train on our N8

Does this work with a locked bootloader? And if so do I just follow the steps here? Or do I need OST LA?

thank you so much for your time and effort. Much appreciated. Can the stock recovery be backed up and restored Later? Is it advised to flash it on TA 1012 Nokia 8 unlocked? How can we revert to the original state? Does OEM Unlock help in this case? Is it an image of the whole OS like previous mod attempts?

iKillua said:
Does this work with a locked bootloader? And if so do I just follow the steps here? Or do I need OST LA?
Click to expand...
Click to collapse
You need an unlocked bootloader. Else fastboot not let you overwrite /boot partition. No OST LA required.

trandafirmd said:
thank you so much for your time and effort. Much appreciated. Can the stock recovery be backed up and restored Later? Is it advised to flash it on TA 1012 Nokia 8 unlocked? How can we revert to the original state? Does OEM Unlock help in this case? Is it an image of the whole OS like previous mod attempts?
Click to expand...
Click to collapse
There is no different partition for recovery. So, just flashing the original boot partition ( boot.img ) will be enough to restore. OEM unlocked is required to decrypt the /data partition. This one is just the boot.img modification.

bidhata said:
There is no different partition for recovery. So, just flashing the original boot partition ( boot.img ) will be enough to restore. OEM unlocked is required to decrypt the /data partition. This one is just the boot.img modification.
Click to expand...
Click to collapse
Is this img suitable for restore https://mega.nz/#!yYwUWKwC!5wb2EkDhFKE2QIhI5tW0SE_uqkn2UL2uEPkTM01G5Mg?0 I can't see any 1012 img's How can I backup the boot.img from my phone?
Thank you.

trandafirmd said:
Is this img suitable for restore https://mega.nz/#!yYwUWKwC!5wb2EkDhFKE2QIhI5tW0SE_uqkn2UL2uEPkTM01G5Mg?0 I can't see any 1012 img's How can I backup the boot.img from my phone?
Thank you.
Click to expand...
Click to collapse
It is the same image for TA 1004 / TA-1012 . Taken from v4.88B update.

I realized that after the download finished. I apologize for jumping the gun. Since I'll have to unlock my bootloader, is there a way to do a full system backup through adb or otherwise? Most likely, I have a locked bootloader and before I can figure out a way to unlock it, I will have to backup as much data as possible since unlocking it will most likely wipe all my data and do a factory reset.

You can not make a backup unfortunately.

could you and other people making useless threads put it in the thread title and OP so that 99.9% of nokia 8 owners that dont have a way of unlocking the bootloader dont waste our time by having the salt rubbed in, thanks

Hard Bricked MOTO G5S XT1799-2 :(( HELP!

So it finally happened.
After trying to flash stock firmware on my phone via fastboot it went black dead and won't even start It was a strange story. I wanted to root to access camera2.api, once I got there, I wanted a better switching between camera 1 and 2 and found ROOT enabler app. That somehow disabled my cameras altogether. I did factory reset only to soft brick my phone. Then I tried to flash another rom. I thought maybe getting OREO will help. Oreo disabled NFC and selfie camera. Then I did the fatal mistake of trying to downgrade flashing back to nougat = HARD BRICK.
Could anybody help me please or am I doomed for good?
Thanks
Six

sixtheninth said:
So it finally happened.
After trying to flash stock firmware on my phone via fastboot it went black dead and won't even start It was a strange story. I wanted to root to access camera2.api, once I got there, I wanted a better switching between camera 1 and 2 and found ROOT enabler app. That somehow disabled my cameras altogether. I did factory reset only to soft brick my phone. Then I tried to flash another rom. I thought maybe getting OREO will help. Oreo disabled NFC and selfie camera. Then I did the fatal mistake of trying to downgrade flashing back to nougat = HARD BRICK.
Could anybody help me please or am I doomed for good?
Thanks
Six
Click to expand...
Click to collapse
use the sdcard booting method with existing img file
if the phone boot from sdcard
reboot the phone in bootloader(fastboot) and flash again the oreo rom with fastboot comands!

vaserbanix said:
use the sdcard booting method with existing img file
if the phone boot from sdcard
reboot the phone in bootloader(fastboot) and flash again the oreo rom with fastboot comands!
Click to expand...
Click to collapse
Thanks I was about to do that, but will the XT1795 file work on my device? Plus I don't want to go to OREO as it disables various functions for my phone. I want to roll back and flash the stock nougat rom so I can use nfc and selfie camera. Can't I just do that somehow?
Cheers
Six

sixtheninth said:
Thanks I was about to do that, but will the XT1795 file work on my device? Plus I don't want to go to OREO as it disables various functions for my phone. I want to roll back and flash the stock nougat rom so I can use nfc and selfie camera. Can't I just do that somehow?
Cheers
Six
Click to expand...
Click to collapse
you cant downgrade the bootloader!
you have to put back the oreo
you can try after oreo to install boot.img and all
system-sparsechunk files from nougat rom(your stock rom)
if it work, youre saved
if not, you have to wait for a full compatible oreo for youre phone model.
also you can try after oreo, a custom rom(cm14.1)
Sent from my Moto G5s using Tapatalk

vaserbanix said:
you cant downgrade the bootloader!
you have to put back the oreo
you can try after oreo to install boot.img and all
system-sparsechunk files from nougat rom(your stock rom)
if it work, youre saved
if not, you have to wait for a full compatible oreo for youre phone model.
also you can try after oreo, a custom rom(cm14.1)
Sent from my Moto G5s using Tapatalk
Click to expand...
Click to collapse
Oh, I kind of thought that the process of unbricking totally format all data, so I would be able to start from scratch. Each time I tried to install any other custom rom for normal montana, after flashing the phone would boot back into recovery mode. I tried Lineage 14.1, ViperOs and Ressurrection Rmx and AOKP. Always the same result. I guess that even if I'd manage to flash them I'd lose the XT1799-2 extra functions as I did with this Oreo. But anyway, you are saying that I can use bootloader 7 to install nougat over Oreo? If so would confirm exact procedure?
I would boot into fastboot and then which of these commands I will leave out?
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Because this is exactly what I did to hard brick my phone, so if there is a method to do the same without bricking it I'd be grateful thousand times I somehow doubt that Xt1799-2 will ever get its own custom rom or oreo update.
Cheers
M>

sixtheninth said:
Oh, I kind of thought that the process of unbricking totally format all data, so I would be able to start from scratch. Each time I tried to install any other custom rom for normal montana, after flashing the phone would boot back into recovery mode. I tried Lineage 14.1, ViperOs and Ressurrection Rmx and AOKP. Always the same result. I guess that even if I'd manage to flash them I'd lose the XT1799-2 extra functions as I did with this Oreo. But anyway, you are saying that I can use bootloader 7 to install nougat over Oreo? If so would confirm exact procedure?
I would boot into fastboot and then which of these commands I will leave out?
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Because this is exactly what I did to hard brick my phone, so if there is a method to do the same without bricking it I'd be grateful thousand times I somehow doubt that Xt1799-2 will ever get its own custom rom or oreo update.
Cheers
M>
Click to expand...
Click to collapse
after you flash full oreo, use only this lines from nougat:
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot reboot
Sent from my Moto G5s using Tapatalk

Unfortunately I did the same with my phone (I installed the 8.0, first I had done without bootloader, but forgot to take the gpt, I was not able to downgrade without losing the imei, which I could not recover in any way, so I decided to install the 8.0 complete and see if it worked at least the chip) but it did not happen hardbrick the screen went black but I still hear the sound of the phone calling and I can put it in fastboot mode even without appearing anything on the screen, some method to recover? I did not even try to downgrade because I know I can make it worse :,(

I am currently in a midst transferring img to SD card, but my Rufus 3.3 does not allow me to choose GPT only MBR. Also I had no idea how to check out the current bootloader version in fastboot. So what it actually mean when you lose IMEI? Can you still use the phone?

sixtheninth said:
I am currently in a midst transferring img to SD card, but my Rufus 3.3 does not allow me to choose GPT only MBR. Also I had no idea how to check out the current bootloader version in fastboot. So what it actually mean when you lose IMEI? Can you still use the phone?
Click to expand...
Click to collapse
Check with the command
Code:
fastboot getvar all [/ CODE]
and search for "version-bootloader" is the version of your bootloader
If the IMEI is null your sim card does not connect, it is a smatphone without sim card
You can use the phone but it will be out of cellular network until you repair your imei
My bootloader is BC.12 and my phone got the black screen but it did not brickou but unfortunately can not use anything because the screen simply does not work and I can not outdate otherwise I can brick it
I'll wait to see if the Chinese oreo is out, and maybe the bootloader version is bigger and save me from this problem (but I learned a lesson never flash the gpt and bootloader from another phone even though they are similar).

jvfigueredo said:
Check with the command
Code:
fastboot getvar all [/ CODE]
and search for "version-bootloader" is the version of your bootloader
If the IMEI is null your sim card does not connect, it is a smatphone without sim card
You can use the phone but it will be out of cellular network until you repair your imei
My bootloader is BC.12 and my phone got the black screen but it did not brickou but unfortunately can not use anything because the screen simply does not work and I can not outdate otherwise I can brick it
I'll wait to see if the Chinese oreo is out, and maybe the bootloader version is bigger and save me from this problem (but I learned a lesson never flash the gpt and bootloader from another phone even though they are similar).[/QUOTE]
Shiit, ok so if I have BC12 I can only flash it with OREO that'd leave me without nfc and front camera. What happened to your screen?
Click to expand...
Click to collapse

sixtheninth said:
Shiit, ok so if I have BC12 I can only flash it with OREO that'd leave me without nfc and front camera. What happened to your screen?
Click to expand...
Click to collapse
You will have to flash the full oreo and then try to flash the stock without the gpt and bootloader, if you lucky it all worked (when I tried to do this my IMEI was null, I tried to repair it and I did not succeed).
Finally the screen, I do not know what happened, but it stopped working after I flashed the OREO stock rom with bootloader, I do not know why but it seems that it did not recognize the screen of my phone or something, because before I flashed it was working normal

I used Win 10 and Rufus on XT-1799-2 using XT-1794 and 95 files, both holding power button for over 1min but screen remained black (

vaserbanix said:
you cant downgrade the bootloader!
you have to put back the oreo
you can try after oreo to install boot.img and all
system-sparsechunk files from nougat rom(your stock rom)
if it work, youre saved
if not, you have to wait for a full compatible oreo for youre phone model.
also you can try after oreo, a custom rom(cm14.1)
Sent from my Moto G5s using Tapatalk
Click to expand...
Click to collapse
The results so far are underwhelming. I did the operation in Linux following your guidelines at https://forum.xda-developers.com/sho...14&postcount=1 .
Dowloaded both .img XT1794 and 95, checked the MD5 and flashed them on my sd card.
Neither of them worked. Light was flashing at various intervals, but even after two minutes of holding the power button screen remained pitch black.
I have even downloaded mmcblk0 for XT1799-2 from here https://cloud.mail.ru/public/vEq7/A...id 7.1.1, ZUI 3.1.68-74 ST (China AliCustom)/
but the results are the same.
Do you think I will need a special Oreo mmcblk0.img or is the damage permanent?
Thanks

jvfigueredo said:
You will have to flash the full oreo and then try to flash the stock without the gpt and bootloader, if you lucky it all worked (when I tried to do this my IMEI was null, I tried to repair it and I did not succeed).
Finally the screen, I do not know what happened, but it stopped working after I flashed the OREO stock rom with bootloader, I do not know why but it seems that it did not recognize the screen of my phone or something, because before I flashed it was working normal
Click to expand...
Click to collapse
So how did you manage to get it loaded in to a bootloader if you hard bricked the same way as I did? I cannot use any of the mmcblk0 images because they are all having lower versions of bootloader apparently.
OPP28.65-37 was the ROM I flashed before my foolish downgrade attempt. Which might have Bootloader ver. 12.

sixtheninth said:
So how did you manage to get it loaded in to a bootloader if you hard bricked the same way as I did? I cannot use any of the mmcblk0 images because they are all having lower versions of bootloader apparently.
OPP28.65-37 was the ROM I flashed before my foolish downgrade attempt. Which might have Bootloader ver. 12.
Click to expand...
Click to collapse
I don't downgrade my bootloader, i just install oreo and the screen don't turn on, but it play sounds(hello moto) and can enter on fastboot mode. Sorry i don't help you on this

jvfigueredo said:
I don't downgrade my bootloader, i just install oreo and the screen don't turn on, but it play sounds(hello moto) and can enter on fastboot mode. Sorry i don't help you on this
Click to expand...
Click to collapse
aha, do you remember what version of OREO did you install?

sixtheninth said:
aha, do you remember what version of OREO did you install?
Click to expand...
Click to collapse
I install OPP28.65-37-2 and OPP28.65-37 and my screen don't turn on

jvfigueredo said:
I install OPP28.65-37-2 and OPP28.65-37 and my screen don't turn on
Click to expand...
Click to collapse
oh ****, so we are on the same path there - I also did OPP28.65-37. Do you know what bootloader versions they both had? It seems we will booth need this Oreo blankflash (mmcblk0). If you know somebody who flashed working Oreo on G5S, you can ask them to follow a guide here on XDA and create mmcblk0 for us via TWRP. That seems to be the only solution as far as I know.

sixtheninth said:
oh ****, so we are on the same path there - I also did OPP28.65-37. Do you know what bootloader versions they both had? It seems we will booth need this Oreo blankflash (mmcblk0). If you know somebody who flashed working Oreo on G5S, you can ask them to follow a guide here on XDA and create mmcblk0 for us via TWRP. That seems to be the only solution as far as I know.
Click to expand...
Click to collapse
it's BC.12, I'm sorry I do not know anyone, and I can not do that for you because I do not have a microSD card and my screen does not work either. Kkkkkkkkkkkk damn time I invented to upgrade, I continued in 7.1.1 everything was working, except the front camera that did not I recognized the 16mp (only 4mp) but that was the least: /

jvfigueredo said:
it's BC.12, I'm sorry I do not know anyone, and I can not do that for you because I do not have a microSD card and my screen does not work either. Kkkkkkkkkkkk damn time I invented to upgrade, I continued in 7.1.1 everything was working, except the front camera that did not I recognized the 16mp (only 4mp) but that was the least: /
Click to expand...
Click to collapse
I know your pain man. But there is a guide on how to make that happen and I am sure sooner or later, someone will take on the challenge to unbrick them all ) The whole purpose of this forum is to solve problems, so let's keep hunting for that blankflash, there is quite a number of people who flashed Oreos with BL 12 on their G5S!

Phone unrooted itself

This has happened to me before, I think -- I restarted, and my phone unrooted itself. What's that about, again? How do I stop it?

My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.

ctfrommn said:
My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.
Click to expand...
Click to collapse
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?

DanHakimi said:
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?
Click to expand...
Click to collapse
You can just go flash the patched boot again.

ctfrommn said:
You can just go flash the patched boot again.
Click to expand...
Click to collapse
Welp... I did that, and now my phone is stuck booting, it won't go past the G screen.

I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.

Bob nesta said:
I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.
Click to expand...
Click to collapse
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.

DanHakimi said:
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.
Click to expand...
Click to collapse
I only mentioned flashing a custom kernel since your patched boot.img messed you up so I threw that out there because sometimes it's a way to get out of a boot problem. (I'm not trying to plug other peoples' kernels/work or anything like that.)
But you got things up and running, so...carry on