Hi guys, I bought an A5 with less than 15 days everything was ok but I wanted to root to release more RAM I passed a BL file that gave an error, but changed the KNOX counter until it was ok. The problem was that the ROM looked strange with two drum menus. I thought I will pass the stock rom until then it was but after that I do not have IMEI anymore. Does the serial number only appear that can do or need the same BOX?
find misc partition failed
Odin error BL
Help !!!!
I'm not sure what you did but it sounds like you downgraded the rest of the firmware without the bootloader part. If so, that's the cause why you're not having a valid IMEI.
Try flash the latest firmware for your country/carrier.
I understand, but when I try to pass the BL file the error below does not know why.
Nand write start fail on odin
tys0n said:
I'm not sure what you did but it sounds like you downgraded the rest of the firmware without the bootloader part. If so, that's the cause why you're not having a valid IMEI.
Try flash the latest firmware for your country/carrier.
Click to expand...
Click to collapse
I understand, but when I try to pass the BL file the error below does not know why.
Nand write start fail on odin
tys0n said:
I'm not sure what you did but it sounds like you downgraded the rest of the firmware without the bootloader part. If so, that's the cause why you're not having a valid IMEI.
Try flash the latest firmware for your country/carrier.
Click to expand...
Click to collapse
he was already with that damn security patch
Related
Hi guys.
So i have an Note 3 with HongKong firmware that i want to flash new international/europe firmware as it is not working on europe sim card(i think it will solve the problem...).
The firmware that is installed on it is N9005ZHUENB5 so i thought aha then this is the Hong Kong 16GB version that have flashing problem. But then i found out that the phone is 32 GB and not 16 so it can not be the Hong Kong 16 GB version but it has for some reason the Hongkong firmware on it.
The IMEI number under the batteri is matching the IMEI nr android is showing, but the serial number is not matching.
The weird part is phone INFO app shows this:
SN under batteri: Made in Vietnam
SN andorid show: Made in CHINA
Even weirder:
imei.info is giving me N900 Galaxy Note 3 as Model????
This has made me being carefull falshing it and i am asking you guys to advice me before i start flashing any new firmware. I have rooted and done EFS and pit file backup in case i screw it up.
What do you guys think, will it be safe for me to just download a europe firmware and flash it with odin?
Download and run Phone Info from Play store and post screenshots .
This is the info from Phone info app(attached)
This is not a new phone is it as i see warranty void Knox 0x1 .
Looks like a previous owner has flash a rom .
Thanks for feedback JJEgan.
I have rooted the phone so maybe therefore? The phone has android 4.4.2, however i believe this should not have anything to do with what i want to do. I can flash 4.4.2 or flash 5.0 via odin, but just want advice before i do that.
Thanks
The_Kurd said:
Thanks for feedback JJEgan.
I have rooted the phone so maybe therefore? The phone has android 4.4.2, however i believe this should not have anything to do with what i want to do. I can flash 4.4.2 or flash 5.0 via odin, but just want advice before i do that.
Thanks
Click to expand...
Click to collapse
Well at least you're 32GB - not sure why only HK phones seem to have a 16GB model. You're right to be cautious - there seems to be partition differences also, but if you search for a EU version of the PIT file for v5 Android you will be prepared in case the Odin flash fails. I'd also get SuperSU zip file on your extSDCard and an Odin flash version of TWRP or CWM - untick the Reboot option, flash the firmware you want, (Wait for it to finish completely - it will sit for a while then let you know it is done) then Reset, untick the Reboot again, then flash the Recovery. Reboot phone into Recovery and flash the SuperSU file and restart.
All being well you should boot into the stock firmware and do the set up. Then you can flash whatever ROM you want in Recovery.
If it DOESN'T work, Search for how to fix, and if you can't find what you need, ASK, don't just go playing...
Thanks @Journyman16
Result:
Tried to flash with lolipop stock firmware and my backed up pit file( from andoird 4.4.2))--->Fail/brick with Volume size is too big 4620288 < 4718592 and invalid ext4 image error(Odin setting Auto-reboot and F. reset used)
Tried to flash with lolipop stock firmware and with pit file CSB_signed_HLTE_EUR_OPEN_32G_0805 --->Fail/brick with Volume size is too big 4620288 < 4718592 and invalid ext4 image error(Odin setting Auto-reboot and F. reset used)
Tried to flash with stock HK kitkat 4.4.2 firmware without PIT file---> Success and i am back to stock firmware but that did not solve my call/SIM and wrong serial number
Maybee i should donwload an europe 4.4.2 firmware and try flash with that?
The_Kurd said:
Thanks @Journyman16
Result:
Tried to flash with lolipop stock firmware and my backed up pit file( from andoird 4.4.2))--->Fail/brick with Volume size is too big 4620288 < 4718592 and invalid ext4 image error(Odin setting Auto-reboot and F. reset used)
Tried to flash with lolipop stock firmware and with pit file CSB_signed_HLTE_EUR_OPEN_32G_0805 --->Fail/brick with Volume size is too big 4620288 < 4718592 and invalid ext4 image error(Odin setting Auto-reboot and F. reset used)
Tried to flash with stock HK kitkat 4.4.2 firmware without PIT file---> Success and i am back to stock firmware but that did not solve my call/SIM and wrong serial number
Maybee i should donwload an europe 4.4.2 firmware and try flash with that?
Click to expand...
Click to collapse
I think when you use a PIT for such things you need to tick the re-partition box - if you're going to try it, read up on it. I haven't done it since I had an S3. Mess up the PIT process and it's a bit of work to get the phone working again.
I'm puzzled about the serial number thing - even if the main board was changed, that wouldn't explain it because the IMEI would also change AFAIK. I wonder if the wrong S/No might be the reason you have the SIM/Call issue?
You could now try a factory reset. See if it changes anything. Other than that, research about EFS repair/restore.
You DID have a backup before all this... right?
Fingers-crossed
Journyman16 said:
I think when you use a PIT for such things you need to tick the re-partition box - if you're going to try it, read up on it. I haven't done it since I had an S3. Mess up the PIT process and it's a bit of work to get the phone working again.
I'm puzzled about the serial number thing - even if the main board was changed, that wouldn't explain it because the IMEI would also change AFAIK. I wonder if the wrong S/No might be the reason you have the SIM/Call issue?
You could now try a factory reset. See if it changes anything. Other than that, research about EFS repair/restore.
You DID have a backup before all this... right?
Click to expand...
Click to collapse
Ok guys:
I have one bad news and one good news
The good news: I managed to flash with Poland firmware after advice from @FeralFire(really appreciated, thanks) following his guide here: http://forum.xda-developers.com/showthread.php?t=2613374&page=13 I believe i can now flash any firmware as it is now international pit and firmware
The bad news: I can still not call/sms only data is working, and the serial number is stil diffrent then the one under the batteri. The IMEI is correct though. So i have now ruled out that it was something with HongKong firmware as it seems like this problem is not related to which firmware is in use. I have also tried with Region lock away app but no luck
I do have backup of my EFS and pit file, but the problem is this phone has had difrent serial number from begining so no help from EFS backup i believe?
I will try to digg some more in to EFS repaire threads here on xda and see what i can find, but any threads you guys advice or other tips i can try?
Again thank you for helping me out here: )
Dont remember the solution ( probably efs) look on S2 forum as their where a number of wrong serial posts that may give you a clue .
Hi,
I want to downgrade my SM-A310F to earlier Android versions, but Odin blocks this with the Error: "SW REV. CHECK FAIL. DEVICE: 3. BINARY: 2."
So apparently I can only install firmware files which come with the same Bootloader I'm currently on (so 3) and not earlier versions. For me it's Android 7 and the latest update of 6.0.1 which where made for this bootloader. But I want to downgrade to earlier versions of Android (please don't ask why, I know that these don't have the latest security patches etc. pp.).
So my first idea was I should downgrade the bootloader first so it matches the firmware I want to install. I extracted the recovery.img out of the firmware file, packed it in a .tar file and flashed it successfully through Odin. But unfortunately I get the same error in Odin like above when trying to flash the firmware again, so the bootloader maybe didn't downgrade?!
What can I do to downgrade my bootloader?
I want to install a stock Android ROM, so Custom ROMs are not an option. I heard I can install a Custom Bootloader, like TWRP, which allows installing every firmware?!
But does that trip my KNOX counter? My KNOX is still 0, so if there's an option to downgrade to earlier ROMs without tripping KNOX I'd be glad to hear it.
So I found the answer myself.
Apparently it is not possible to simply downgrade the Bootloader. I didn't fully dig into this, but to simply flash some image with Odin won't do the trick at least.
What works however is to downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's the trick? One downloads the firmware file (.tar) which one wants to downgrade to and opens it with an archiver application (7zip). One extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends on .bin (e.g. sboot.bin etc.). This .tar file can be flashed like any other firmware file via Odin and it should run through it without any problems.
I can not confirm that the downgrade works for every firmware version, but at least I could downgrade from Android 7 Nougat to 6.0.1 Marshmellow while the first one comes with the SW Rev 3 bootloader and the latter with SW Rev 2 bootloader. Again, I don't know how far into the past this works, e.g. if you can downgrade from 7 to 5.1.1 with this method.
Another option is always a Custom ROM (like this one for 5.1.1 for example) which doesn't check the Bootloader version.
I don't know if this method trips KNOX since I had tripped it already before figuring this out (very well could be, since you're not flashing a signed firmware file anymore...).
mcpossity said:
So I found the answer myself.
Apparently it is not possible to simply downgrade the Bootloader. I didn't fully dig into this, but to simply flash some image with Odin won't do the trick at least.
What works however is to downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's the trick? One downloads the firmware file (.tar) which one wants to downgrade to and opens it with an archiver application (7zip). One extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends on .bin (e.g. sboot.bin etc.). This .tar file can be flashed like any other firmware file via Odin and it should run through it without any problems.
I can not confirm that the downgrade works for every firmware version, but at least I could downgrade from Android 7 Nougat to 6.0.1 Marshmellow while the first one comes with the SW Rev 3 bootloader and the latter with SW Rev 2 bootloader. Again, I don't know how far into the past this works, e.g. if you can downgrade from 7 to 5.1.1 with this method.
Another option is always a Custom ROM (like this one for 5.1.1 for example) which doesn't check the Bootloader version.
I don't know if this method trips KNOX since I had tripped it already before figuring this out (very well could be, since you're not flashing a signed firmware file anymore...).
Click to expand...
Click to collapse
https://forum.xda-developers.com/samsung-a-series/general/rom-t3614602
So I found the answer myself.
Apparently it is not possible to simply downgrade the Bootloader. I didn't fully dig into this, but to simply flash some image with Odin won't do the trick at least.
What works however is to downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's the trick?
mcpossity said:
One downloads the firmware file (.tar) which one wants to downgrade to and opens it with an archiver application (7zip). One extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends on .bin (e.g. sboot.bin etc.). This .tar file can be flashed like any other firmware file via Odin and it should run through it without any problems.
Click to expand...
Click to collapse
Hi there mcpossity.
Can you please be more specific on this trick part? Please share the steps you followed.
Regards
With a S7 Edge
Hello,
My phone has updated on the last version of Android 8.0.0 Oreo (01.12.2020), with the last version of Bootloader (7th). I want to downgrade my device to Android 6.0.1, but all version for this OS have BLv1, so I am in the same situation than you (but one gen. later). Can I downgrade my phone, with the same methode ? If so, can you explain this in detail or give me a custom OS ? Thanks in advance.
I tried with this methode and this doesn't work : Odin has shut down when I have started the process. What was wrong ?
Downgrade using old versions of LineageOS?
Hi, I've got the same problem: I installed LineageOS 17.1 (Andoroid 10) which upgraded my Bootloader to 5. Now I need to go back to stock ROM but cannot do so because the error says: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 5, BINARY 1.
Is it possible to install an early Lineage OS that downgrades the Bootloader and then install stock ROM? Where would I find the BL version of LineageOS?
Thanks
PS: In my case Galaxy S8
galaxynoobie said:
Hi, I've got the same problem: I installed LineageOS 17.1 (Andoroid 10) which upgraded my Bootloader to 5. Now I need to go back to stock ROM but cannot do so because the error says: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 5, BINARY 1.
Is it possible to install an early Lineage OS that downgrades the Bootloader and then install stock ROM? Where would I find the BL version of LineageOS?
Thanks
PS: In my case Galaxy S8
Click to expand...
Click to collapse
story is not completely same but my device is note 9 exynos and i did march patch BL is 5 and android 10 & 9 is sucks so need 8.1 but can't go back need serious help
Hey I'm Sam said:
story is not completely same but my device is note 9 exynos and i did march patch BL is 5 and android 10 & 9 is sucks so need 8.1 but can't go back need serious help
Click to expand...
Click to collapse
have you ever rosolved this ?
i have s9 note, want disperatly to downgrade to oreo for call recording. I feel cheated from samsung, what a waste of money....
Nemonavicusrino said:
have you ever rosolved this ?
i have s9 note, want disperatly to downgrade to oreo for call recording. I feel cheated from samsung, what a waste of money....
Click to expand...
Click to collapse
in the same boat as you, cube acr does record but the recording quality is very poor and the recording does not work when you are using Bluetooth headphones
Need help with recording
bilaliz said:
in the same boat as you, cube acr does record but the recording quality is very poor and the recording does not work when you are using Bluetooth headphones
Click to expand...
Click to collapse
Find something here, but i am not sure what i need, seem promising. I feel so cheated by this companies that put this restrictions on OUR HARDWARE. I do not understand, why something i pay today, dont work as espected tomorow, for SECURITY REASON. I want to asume risk and i do not know who is the owner. Me or samsung or google ?
https://forum.xda-developers.com/galaxy-note-9/help/enabling-native-call-recorder-csc-t3962224/page2
Espect day when phones is replaced by personal computer model. I want this OS on this hardware, with this app for calling and ...voila. I am at rage now : a 1000+ euro hardware canot record WHAT I SPEAK AND WHAT IS SPEAKED TO ME? if i put call on speaker and 10 person hear what is the diference...
Please help !
GuestD1009 said:
So I found the answer myself.
Apparently it is not possible to simply downgrade the Bootloader. I didn't fully dig into this, but to simply flash some image with Odin won't do the trick at least.
What works however is to downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's the trick? One downloads the firmware file (.tar) which one wants to downgrade to and opens it with an archiver application (7zip). One extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends on .bin (e.g. sboot.bin etc.). This .tar file can be flashed like any other firmware file via Odin and it should run through it without any problems.
I can not confirm that the downgrade works for every firmware version, but at least I could downgrade from Android 7 Nougat to 6.0.1 Marshmellow while the first one comes with the SW Rev 3 bootloader and the latter with SW Rev 2 bootloader. Again, I don't know how far into the past this works, e.g. if you can downgrade from 7 to 5.1.1 with this method.
Another option is always a Custom ROM (like this one for 5.1.1 for example) which doesn't check the Bootloader version.
I don't know if this method trips KNOX since I had tripped it already before figuring this out (very well could be, since you're not flashing a signed firmware file anymore...).
Click to expand...
Click to collapse
you sure this method works? i want to downgrade from 9 to 8. I am desperate now. But i don't know if it'll work. I've read thousands of words and all say it won't work.
S10 downgrade bootloader
I'm also in the same boat, Galaxy S10 (Exynos). Android 10 doesn't support PPTP VPN hotspot, and now my bootloader has been upgraded to U4. So yeah..
this seems helpful. are there anyone tried this on a s10 exynos?
ya not alone with an Samsung.....i'm on Sony Xperia 1 and after the update to Android 10 i have couple issuse with Soft restart out of nowhere everyday ones or more
dowangrade to Pie wasn't the problem but with Pie i went into an Gyroscope error....display isn't turning anymore i tried everything to get the sensor working but nothing helped
after updating to Android 10 Sensor running well
PlayJ004 said:
With a S7 Edge
Hello,
My phone has updated on the last version of Android 8.0.0 Oreo (01.12.2020), with the last version of Bootloader (7th). I want to downgrade my device to Android 6.0.1, but all version for this OS have BLv1, so I am in the same situation than you (but one gen. later). Can I downgrade my phone, with the same methode ? If so, can you explain this in detail or give me a custom OS ? Thanks in advance.
I tried with this methode and this doesn't work : Odin has shut down when I have started the process. What was wrong ?
Click to expand...
Click to collapse
same here
Me now with sm-p615 (tablet)
GuestD1009 said:
So I found the answer myself.
Apparently it is not possible to simply downgrade the Bootloader. I didn't fully dig into this, but to simply flash some image with Odin won't do the trick at least.
What works however is to downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's the trick? One downloads the firmware file (.tar) which one wants to downgrade to and opens it with an archiver application (7zip). One extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends on .bin (e.g. sboot.bin etc.). This .tar file can be flashed like any other firmware file via Odin and it should run through it without any problems.
I can not confirm that the downgrade works for every firmware version, but at least I could downgrade from Android 7 Nougat to 6.0.1 Marshmellow while the first one comes with the SW Rev 3 bootloader and the latter with SW Rev 2 bootloader. Again, I don't know how far into the past this works, e.g. if you can downgrade from 7 to 5.1.1 with this method.
Another option is always a Custom ROM (like this one for 5.1.1 for example) which doesn't check the Bootloader version.
I don't know if this method trips KNOX since I had tripped it already before figuring this out (very well could be, since you're not flashing a signed firmware file anymore...).
Click to expand...
Click to collapse
How on earth did you do that??
Which archive are you talking about when you say you unpack all the files and repack them without every .bin file?
I'm guessing the BL archive because that's the only one with a lot .bin files in it.
So I tried the BL_xxxx.tar.md archive and repacked it. But Odin would always get stuck at "file analysis..."
Also did you flash the modified BL first and then the AP, CP and CSC or did you flash it all at once?
I've got the same problem here. I want to downgrade my Galaxy S7 from Android 8.0 to Androud 7.0 but am unable to do so, to the point where I'm considering buying a completely new device just to have Android 7.0 again.
There is a way but...only Samsung's engineer are able to hack / trick this.
It is require special file to flashing in device then Sofware protection will be removed
Ask an Samsung Mobile Engineer if you have relatives.
Hello,
Today I tried to flash KING OF NOUGAT v13 but my phone got stacked on Samsung Logo(+30min). I was forced to restart it(Power+Volume Up) and flash the recovery that made before flashing. To my surprise when the phone boot there was no connection(only Wi-FI). As far as I can see IMEI, Bluetooth and Mac address are unavailable. I tried different backup(I have two on SD card) but the problem was the same.
When I created the backup I made a full backup including EFC, but for some reason, it's not working.
I also tried this article , and put those commands in the terminal but no result.
I know there is an option to fix it if I flash the stock rom . But i would like to know if there is another options
there is sticky thread with info how to get imei back, so just read and follow
yaro666 said:
there is sticky thread with info how to get imei back, so just read and follow
Click to expand...
Click to collapse
Actually, the problem was the the Bl and Cp, After I flashed the latest everything workout
Can you please share the link to the latest BL and CP ...i am facing the same issue after flashing the leaked oreo update...and i cant flash older BL verrsions anymore,and i cant use any sim either....
download the newest rom and extract it yourself, easy as unpacking
yaro666 said:
download the newest rom and extract it yourself, easy as unpacking
Click to expand...
Click to collapse
I tried but it still shows this error
SW REV check fail device 2 binary 1
it flashed without any bl other ap cp and csc but gives error while flashing the BL file....did u flash the nougat BL file,or any other one ?
Sariful Alam Fahad said:
I tried but it still shows this error
SW REV check fail device 2 binary 1
it flashed without any bl other ap cp and csc but gives error while flashing the BL file....did u flash the nougat BL file,or any other one ?
Click to expand...
Click to collapse
same here i downloaded the latest version i could find and i cant flash the bootloader and flashing CP doesnt fix anything
I'm facing huge problem..... I can't downgrade January security patch..... and when I trying to flash old stock Rom bootloader (BL) prevents flashing...
Actually I want old security patch because I'm able to patch network certificate with old security patch.....
But after updating patch network and root not supported..... so always showing Emergency call.....
So please help me how to full flash old stock Rom with boot loader file....
Sorry for bad English....
S7 edge G935FD
Current Rom and baseband G935FXXU2DRAG
Country INS
It cant be done after jan 2018 update ?
Thanks Mr. Saurabh for your reply.
But is it possible to root and patch network on this latest update?
bhanu1758 said:
I'm facing huge problem..... I can't downgrade January security patch..... and when I trying to flash old stock Rom bootloader (BL) prevents flashing...
Actually I want old security patch because I'm able to patch network certificate with old security patch.....
But after updating patch network and root not supported..... so always showing Emergency call.....
So please help me how to full flash old stock Rom with boot loader file....
Sorry for bad English....
S7 edge G935FD
Current Rom and baseband G935FXXU2DRAG
Country INS
Click to expand...
Click to collapse
Extract tar file with 7zip then delete sboot.bin and cm.bin and re compress all remaining files in .tar with same 7 zip and flash with this method you can even go back to marshmallow or any firmware.
I did it. But when I'm flashing by your method Baseband shows unknown and both IMEI gone (invisible)...
I need Infos an Help to. I want to Downgrade G935F from 7.0 to 6.0 and try much.
Nothing works.
I flash AP Factory binary
COMBINATION_FA60_G935FXXU2ARA1 this works an then
if i flash 6.0 with Odin get errors and odin dont flash.
Somebody can help me?
Or i read somethink like goes help with teamviewer.
Im ready to donate for usefull Help.
I read somethink like i use the false files. But what files are the right?
In This time i see in Recovery:
7.0/NRD90M/G935FXXU1DQB3
SoftEagle said:
I need Infos an Help to. I want to Downgrade G935F from 7.0 to 6.0 and try much.
Nothing works.
I flash AP Factory binary
COMBINATION_FA60_G935FXXU2ARA1 this works an then
if i flash 6.0 with Odin get errors and odin dont flash.
Somebody can help me?
Or i read somethink like goes help with teamviewer.
Im ready to donate for usefull Help.
I read somethink like i use the false files. But what files are the right?
In This time i see in Recovery:
7.0/NRD90M/G935FXXU1DQB3
Click to expand...
Click to collapse
Downgrade G935F from 7.0 to 6.0
BL_G935FXXS2DRA9_CL12365438_QB16535159_REV00_user_low_ship.tar.md5
AP_G935FXXS1BPLO_CL9519568_QB11927977_REV00_user_low_ship.tar.md5
CSC_OLB_G935FOLB1CPK5_CL9519568_QB11505811_REV00_user_low_ship.tar.md5
CP_G935FXXU2ARA1_ENG_modem_BoxWares.tar.md5
install 4 files will start installation which will be interrupted after the first reboot because the phone will start in recovery now restart the phone and quickly press three buttons to enter the download mode then install the file:
CF-PBH6-Auto-Root-hero2lte-hero2ltexx-smg935f
the phone will stop at the samsung logo do not worry about it just wait after about 2 minutes there will be restart and after the reboot the normal installation will start. works 100%
I'm sorry for my english..
I have the same problem, manage to solve it?
Hi, I have a S8 that is currently flashed with firmware version G950FXXU3CRGB (July). For research purposes I would like to flash this firmware back to G950FXXU1CRD7 (April). Is this possible? Odin keeps giving failed messaged on either sboot.img or boot.img. I tried building a new AP package which only includes system.img, but this one also fails...
Is it at all possible, or is the bootloader/Download-mode preventing me from downgrading?
thereof said:
Hi, I have a S8 that is currently flashed with firmware version G950FXXU3CRGB (July). For research purposes I would like to flash this firmware back to G950FXXU1CRD7 (April). Is this possible? Odin keeps giving failed messaged on either sboot.img or boot.img. I tried building a new AP package which only includes system.img, but this one also fails...
Is it at all possible, or is the bootloader/Download-mode preventing me from downgrading?
Click to expand...
Click to collapse
You cannot downgrade firmware with a lower bootloader version than what is installed on your phone ie: your current bl is ver 3 and your trying to flash bl ver 1
spawnlives said:
You cannot downgrade firmware with a lower bootloader version than what is installed on your phone ie: your current bl is ver 3 and your trying to flash bl ver 1
Click to expand...
Click to collapse
That's what I expected... I'm guessing this also goes for the system image itself? I don't really care about the bootloader, but I would like the system image to be as close as possible to that of April (especially `init`, `vold`, `blkid` and `zygote`). Otherwise I'm just going to search for a non-updated second hand phone.
thereof said:
That's what I expected... I'm guessing this also goes for the system image itself? I don't really care about the bootloader, but I would like the system image to be as close as possible to that of April (especially `init`, `vold`, `blkid` and `zygote`). Otherwise I'm just going to search for a non-updated second hand phone.
Click to expand...
Click to collapse
This is one of the many reasons why I'm still on nougat ( ver 1 bl )- the inability to downgrade. I would also say going the other way holds true too upgrading the firmware without the upgrading the bootloader version would also cause issues.
I've also heard that doing a complete nandroid backup then upgrading then trying to restore does not work either.