Hello,
Is there a way to dowgrade the bootloader of SM-G950F with stock fw G950FXXUCDUD1 to further flash a stock fw Android 8?
- flashing a downgraded bl with twrp?
- with "combination" fw?
- with a modified stock bl flashed with Odin?
...?
Thank you!
No. Samsung will not allow flashing of lower bootloader versions numbers.
Hello, thank you for your answer.
Even with a combination fw or directly flashing an older bootloader with twrp?
No.
Combination roms follow stock firmware regarding bootloader version ( can't downgrade). TWRP is a recovery image to replace stock, You can do more things in twrp over stock except downgrade stock firmware.
spawnlives said:
No.
Combination roms follow stock firmware regarding bootloader version ( can't downgrade). TWRP is a recovery image to replace stock, You can do more things in twrp over stock except downgrade stock firmware.
Click to expand...
Click to collapse
Ok, but what about this thread which seems to say it's doable with combination roms?
(Method) For everyone who wants to Downgrade Galaxy S8 to Oreo/Nougat
Hey guys! I recently read many Questions About downgrading the Galaxy S8 to 7.0/8.0 after we got the 5x Bootloader. Well many of you say NO but What many of you forgot is that there is a way to Downgrade your phone. I already had that Problem...
forum.xda-developers.com
I've seen many guides on how to downgrade stock firmware. Most of them revolve around editing stock firmware. None of them mention whether the bootloader version was actually downgraded. To me personally you are essentially trying to install a custom type rom using by using stock firmware.
spawnlives said:
I've seen many guides on how to downgrade stock firmware. Most of them revolve around editing stock firmware. None of them mention whether the bootloader version was actually downgraded. To me personally you are essentially trying to install a custom type rom using by using stock firmware.
Click to expand...
Click to collapse
I checked and you're right. The minimal configuration for flashing the bl is a tar with cm.bin and sboot.bin and this leads to the usual error "... check fail(cm) device : x binary : y" (whatever odin version used... patched or stock)
reverse engineering sboot and cm.bin and changing the binary release doesn't help because the code is signed and verified by the PBL from the ROM.
The only way to do it should be to connect to the exynos jtag / uart / ? and to reverse engineering the soc (!) modifying the way the PBL check the SBOOT.
Adam Outler a researcher did it on GalaxyS (1 or 2!) more than ten year ago... (https://forum.xda-developers.com/t/how-to-hack-hardware-binary-and-bend-it-to-your-will.1338073/)
So... I think is doable with a lot of talent and patience...
Anyway, thank you for your help!
Related
Hey guys, my question is there:
Its possible to downgrade from 4.4.2 to 4.2.2 ?
I have been reading alot of threads with similar question but i gives to many answer.
Im on a rooted 4.4.2 and i will just back to 4.2.2 because i will a !!completely!! Knox free rom and bootloader.
I dont care about the warrenty, my is run out.
I dont will not only a downgraded rom but also a downgraded bootloader.
When someone have trying a to downgrade from 4.4.2 to 4.2.2 please post here the result.
When a downgrade to 4.4.2 is not possible than which is the lowest firmware which i can flash?
Please try to keep the thread clear and give a usefull answer. Thank you guys
And please dont kill me for my english :good:
Once the bootloader has been upgraded to a Knox-enabled version, you cannot downgrade it. The ROM can be downgraded regardless of the bootloader, but running a Knox-free ROM with a Knox-enabled bootloader will result in a "Kernel is not SEAndroid Enforcing" message to appear on the splash screen every time the device is rebooted.
Okay too Bad...
A question more, i have been reading that a downgrade (Rom+Bootloader) is possible to 4.3, because there have the same Bootloader but just less aggressiv. Is that true?
When yes you can share a stock samsung rom 4.3 without knox?
Thank you for the answer
Sent from my GT-I9505 using XDA Free mobile app
You can downgrade with a custom 4.2.2 rom. You just need to look for one.
Okay that i understand but can i downgrade the Bootloader to 4.3? Because there is similar to our one.
Sent from my GT-I9505 using XDA Free mobile app
Can we use official ROM
Can we downgrade without using Custom ROM?
If we unpack Official tar ROM and remove the bootloader and modem of it and then repack it to tar.
Can that downgrade the Android version from 4.4.2 to 4.2.2?
Or it is not working?
Andro-Man said:
Can we downgrade without using Custom ROM?
If we unpack Official tar ROM and remove the bootloader and modem of it and then repack it to tar.
Can that downgrade the Android version from 4.4.2 to 4.2.2?
Or it is not working?
Click to expand...
Click to collapse
It's possible to downgrade to stock 4.2.2 but a custom kernel such as KT-SGS4 will probably be needed to get the WiFi working.
Simply reinstalling the 4.2.2 modem files using Odin should be sufficient to get the WiFi working. No need of a custom kernel. It is also possible to downgrade the ROM without going through the routine of unpacking and repacking the ROM. Simply flash it through Odin, although you'd need to flash the modem files a second time to get the radios fully functional, as previously mentioned. Just be aware that the bootloader will not change, so every time you boot the 4.2.2 ROM with the Knox-enabled bootloader you will get a message on the splash screen about the kernel not being in enforcing mode.
I have trying this:
I take a orginal XXUBMF8 4.2.2 delete inside the zip bootloader and some other files repack back to .tar
Flash it all fine but then the error, the software is not authorized and on the top secure fail: kernel.
I tried flash a custom 4.2.2 kernel through odin but the same result.
My DL Modus look so: https://dl.dropboxusercontent.com/u/93311676/DSC_0014.JPG
Now i get back to 4.4.2 GNG8
I currently have AT&T stock (I used to have a custom ROM then had to flash to stock ROM to be able to flash to another custom ROM--however, I accidentally flashed a newer version of the AT&T stock ROM which locked my bootloader and I could no longer flash to a custom ROM). I updated my AT&T stock ROM recently and now my back/menu buttons don't work, so I want to see if I can flash to a custom ROM now.
I don't remember the procedure to flash a custom ROM--do I first need to get root in order to unlock the bootloader to be able to flash ROMs (i.e. if I have root then I am guaranteed to be able to unlock bootloader in order to flash ROM)? Is the baseband version the only thing that determines whether I can unlock the bootloader and then be able to flash ROMs?
I currently have OK2 as broadband version and checked one of the stickied threads which said this:
" ROOT
OK2 -- No direct root method. Must Odin OC4 kernel, use Kingroot, then Odin OK2 kernel back."
Does that mean what I have to do is use Odin to get OC4 kernel, then use Kingroot, then Odin OK2 kernel and then I will be able to have root, which means I can then unlock my bootloader and be able to flash to ANY ROM (not just TouchWiz-based ROMs)? Is there anything else I need to consider or is this 100% foolproof? In the future, what should I be careful of in order to prevent getting my bootloader locked again--just that I don't flash a stock (AT&T) ROM that is known to lock back the bootloader?
Thank you all!
There's no way to unlock the bootloader if you have updated your device to the lastest firmware version. The only thing you can do is flash SafeStrap and use Stock Kernel Based ROMs which are compatible with Safestrap.
As regards to the procedure of rooting an OK2 firmware, I'm afraid I won't be able to help you.
Have a happy new year.
mindstormer said:
...however, I accidentally flashed a newer version of the AT&T stock ROM which locked my bootloader ...
Click to expand...
Click to collapse
I was just about to sit down and flash a stock ROM. Can you explain what you mean by this? Did you flash OK2 and it caused you a problem?
smock9 said:
I was just about to sit down and flash a stock ROM. Can you explain what you mean by this? Did you flash OK2 and it caused you a problem?
Click to expand...
Click to collapse
It was a while ago but I used to have I believe an MDL broadband version which meant I could flash any ROM available. I tried a different ROM, didn't like it, then decided to flash back to the stock ROM but accidentally flashed a newer version of it, which meant that my bootloader is now locked. With a locked bootloader, apparently I can only flash to a newer stock ROM (not other ROMs like Cyanogenmod) via Safestrap.
I think if you don't have the MDL broadband version you shouldn't worry about it anyway because it is locked and you will only be limited to flashing stock ROMs.
Slight correction
The previous entry is not entirely correct. Like the OP, I was originally on an unlocked bootloader on my i337. I'd purchased my i337 on the first day and eschewed OTA updates. I wanted to try a touchwiz based ROM, Hyperdrive, and in doing so I recall flashing the stock NB1 firmware. Every firmware beginning with NB1 has a locked bootloader and there has been no progress for more than a year in unlocking the bootloader again. This can limit you to either stock ROMs OR other touchwiz based ROMs like Hyperdrive. I love the Hyperdrive ROM (now on release 21) but its developer has moved on to a newer phone, so it's stuck at Android 4.4.2 and no one has picked up the project in many months. There are several other touchwiz based ROMs for the i337 version of the S4 which I have also tried but I prefer Hyperdrive's myriad customization, even without proper patching. I'll be moving on soon to the Nexus 6P as my daily driver, but would very much like to keep my S4 up to date with a custom ROM. Given the number of people that have been in this same situation, where a newer stock ROM from AT&T locked a previously unlocked bootloader, it's been surprising that the issues have not been overcome on a phone as popular as the Galaxy S4 was and continues to be. I've seen unlocked versions of the S4 selling for just under $400 in the last week of 2015.
Use the desktop version of Kingoroot to root and use Super su and update the binary. Don't forget to hit thanks if this helped.
The bootloader for the at&t s4 was never unlocked. The MDL bootloader had a flaw in it that allowed you to use LOKI which is a lock bypass, not a way to unlock the bootloader.
is it possible to downgrade lollipop stock rom to stock jellybean?or do i need to downgrade first to kitkat stock before downgrading to jellybean?i want to do this because i have apps that i used when im on jellybean which is not compatible with kitkat and lollipop.
Using Odin you should be able to downgrade directly to Android 4.3
You will have to do a factory reset in recovery.
I did my factory reset after downgrading the firmware, but guessing you could do it before the downgrade and then not have to worry about the auto-reboot in Odin.
Hi
I have a problem during flashing from 4.4.2 to 4.3. After start the process fails by aboot.mbn. If I remove the file aboot.mbn in the md5-package and start the process again, it works. The mobile flashs back to 4.3, but it hasn't sound and I can't record Video or Soundmemo. Please help! I don't what to do.
I'm looking forward.
Best wishes
Aboot.mbn is the bootloader. You cannot flash a 4.3 bootloader over a 4.4.2 bootloader.
audit13 said:
Aboot.mbn is the bootloader. You cannot flash a 4.3 bootloader over a 4.4.2 bootloader.
Click to expand...
Click to collapse
Is there any way to go around the bootloader? Would it help to flash lollipop 5.0.1 and then to flash back to jelly bean 4.3 or the lollipop has a bootloader locker too.
Thank's so much!!
There is no way to downgrade the bootloader to 4.3 once the phone has been flashed with 4.4.2 or newer. This applies to many Samsung phones including the s3, note 3, note 4, etc.
audit13 said:
There is no way to downgrade the bootloader to 4.3 once the phone has been flashed with 4.4.2 or newer. This applies to many Samsung phones including the s3, note 3, note 4, etc.
Click to expand...
Click to collapse
I flashed my S3 from 4.4.4 to 4.3 and tab 3 from 4.4.2 to 4.2.2 without any problems...why it doesn't works on S4?
Are you sure that the ROM you used to downgrade included a bootloader?
For the s3, it may be possible to go to a 4.3 bootloader as there was no bootloader after 4.4.2 but I'm not 100% sure. I have no idea about the tab.
audit13 said:
Are you sure that the ROM you used to downgrade included a bootloader?
For the s3, it may be possible to go to a 4.3 bootloader as there was no bootloader after 4.4.2 but I'm not 100% sure. I have no idea about the tab.
Click to expand...
Click to collapse
Hi,
yes, there were one. I've rolled my s4 back to 4.3 now, but I have no sound in it...What can I do?
I'm looking forward.
Best wishes.
You installed the 4.3 bootloader too? You may want to run Samsung Phone Info from the play store to confirm.
audit13 said:
You installed the 4.3 bootloader too? You may want to run Samsung Phone Info from the play store to confirm.
Click to expand...
Click to collapse
I'm not sure. I removed the file aboot.mbn and converted the md5 archive to tar archive and finaly flashed my s4. It works, but there's only no sound in thy system.
Dr Goodvibes said:
Using Odin you should be able to downgrade directly to Android 4.3
You will have to do a factory reset in recovery.
I did my factory reset after downgrading the firmware, but guessing you could do it before the downgrade and then not have to worry about the auto-reboot in Odin.
Click to expand...
Click to collapse
I'm not able to downgrade it from lollipop too. I haven't the option to unlock the oem in the developer options
The OEM unlock bootloader option is only useful where a phone has a locked bootloader. In the case of your s4, the bootloader is not locked and cannot be downgraded.
The aboot.mbn file is the bootloader and removing it means the phone is running a 4.3 ROM on a 4.4.2 bootloader. This is probably why not every works properly.
audit13 said:
The OEM unlock bootloader option is only useful where a phone has a locked bootloader. In the case of your s4, the bootloader is not locked and cannot be downgraded.
The aboot.mbn file is the bootloader and removing it means the phone is running a 4.3 ROM on a 4.4.2 bootloader. This is probably why not every works properly.
Click to expand...
Click to collapse
How can I solve this problem?
You can solve the sound problem by flashing a newer ROM.
You cannot downgrade the bootloader and trying to downgrade may brick the phone by damaging the bootloader.
audit13 said:
You can solve the sound problem by flashing a newer ROM.
You cannot downgrade the bootloader and trying to downgrade may brick the phone by damaging the bootloader.
Click to expand...
Click to collapse
Why it worked with tab 3 and s3? I saw many videos on youtube, there rolled guys the system back...Well, Ithink it's my fate to have the kitkat. I hate this system.
The s3 and Tab 3 are totally different items. Being able to downgrade a bootloader on one device does not automatically mean every bootloader in a company's product line can be downgraded.
Have you tried running a custom ROM on the phone? You may find those more palatable.
audit13 said:
The s3 and Tab 3 are totally different items. Being able to downgrade a bootloader on one device does not automatically mean every bootloader in a company's product line can be downgraded.
Have you tried running a custom ROM on the phone? You may find those more palatable.
Click to expand...
Click to collapse
Can I flash for example cyangenmod 12 and then flash android 4.3?
There is no way to run a completely stock 4.3 ROM, including the bootloader, on the s4 once it has been upgraded to 4.4.2 or 5.01.
audit13 said:
There is no way to run a completely stock 4.3 ROM, including the bootloader, on the s4 once it has been upgraded to 4.4.2 or 5.01.
Click to expand...
Click to collapse
In 2013 there were S4 with 4.2.2. Why I can't roll my system back?
I have an N910C currently on 5.1.1 with an OXX CSC. A few days ago Samsung finally released an OXX version of Marshmallow, so I'm preparing to upgrade.
Is it safe to simply flash using Odin, then reroot and restore any tweaks? Or is there something nasty hidden in the bootloader (e.g. mandatory dm-verity or signed-kernels-only) that requires flashing in some custom way?
Odin is THE SAFEST and most recommended thing to flash a ROM for a Samsung phone.
But is it safe to flash the unmodified full 6.0.1 ROM from Samsung, including bootloader and everything? Or is there something nasty hidden inside, like a new bootloader lock? I'm asking because that has happened before on Samsungs.
.NetRolller 3D said:
But is it safe to flash the unmodified full 6.0.1 ROM from Samsung, including bootloader and everything? Or is there something nasty hidden inside, like a new bootloader lock? I'm asking because that has happened before on Samsungs.
Click to expand...
Click to collapse
Bootloader is locked in n910c after COJ5. Having that said ypu won't be able to downgrade to Kit Kat
How does one upgrade to 6.01 in the first place? I just bought a note 4 and it seems stuck on 5.1.1. I don't have a PC to use Odin. They haven't pushed MM to the N910C? All my Google searches seem to show up articles of that occurring back in April, but it is not so for my phone.
Sent from my SM-N910C using XDA-Developers mobile app
warning
This method will not work anymore if you upgraded to QI5 new bootloader/baseband because it's locked to binery 5 it's impossible to downgrade and dev firmware will fail in odin.
This method will only works with older bootloaders only before QI5
I have successfully downgraded to kitkat after pull my hair for days and unlocked for any sim worldwide if you guys like kitkat like me and wanna unlock your sim network follow these institutions.
1,download developer kitkat firmware and flash via odin 3.10 this firmware is for developers without user apps and its empty but good thing is it will let us downgrade to kitkat bootloader no matter you are on 5.0,5.1 1,6.0.1 just flash.
2,after flash developer firmware dont let phone boot immediately go to download mode and flash twrp recovery.
3,after flash twrp recovery flash sprintxnoteRC2 kitkat rom this will boot flawlessly to kitkat.
4,if you like to try other n910p based kitkat roms go to twrp and backup (boot) thats your kernel of sprint xnote RC2 rom before flash any kitkat rom cuz i donno somehow kernel of sprint xnoteRC2 let boot every rom successfully without any errors.just after flash any rom immediately go to twrp restore and restore (boot) kernel that you made earlier from sprintxnoteRC2 rom.
4,FOR UNLOCKING download SSU APK this will work with kitkat if your phone says INVALID SIM CARD just install as normal APK and open it will ask for root permision PRESS GRANT and unlock then reboot if still your phone dosent get signal bars then go to dialer and dial ##72786# and press YES it will reboot automatically your phone and hopefully you will have signal on gsm sim. if SSU apk method does not work download gt galaxy tools apk and unlock.grant root permission to galaxy tools and open app go down and you'll see UICC unlock just hit and restart device . also you can unlock tethering hotspot permanently from galaxy tools . THATS ALL. I AM SHARING YOU GUYS MY EXPERIENCE I HAVE TESTED THIS METHOD ON MY DEVICE AND i HAVE SUCCESSFULLY UNLOCED MY N910P AND DOWNGRADED FROM 6.0.1 TO KITKAT
DISCLAIMER:- TRY AT YOUR OWN RISK PLEASE YOU MUST BACK UP YOUR EFS AND ANY IMPORTANT DATA BEFORE DO ANYTHING FOLLOW INSTRUCTIONS CAREFULLY AS I HAVE BEEN MENTIONED IN THREAD AND IF ANY QUESTIONS FEEL FREE TO ASK ME. HIT THANKS IF THIS THREAD IS USEFUL FOR YOU.
1. Download developer fimware link.
https://androidfilehost.com/?fid=457095661767098816
2. Download TWRP recovery link
https://mega.nz/#!HUN1nILZ!_7KP4H223nlNAbwx6EIjLLkPxqKXNg_yxjptDbYPwas
3. Download sprintxnoteRC2 rom link
https://mega.nz/#!jdsmEAKa!FH3RvThxgDj_gnxCDgrEAyZi-n3R19RcNmBGJi3Ly7M
4. Download SSU APK LINK
https://mega.nz/#!qVtgzTxK!409cHS7_VuerOqrKg4AnsrskO4nJDbhAtCyf8umaEE8
5. DOWNLOAD GALAXY TOOLS APK LINK
https://mega.nz/#!bElkjZzI!OTtzYjYxsUM8Sf-GP71rHilIXNpWCLIitEgkkx2uJZ8
DOWNLOAD NADIA 4.4 4 CUSTOM KERNEL WORKS ON ALL SNAPDRAGON MODELS N910F/P/T/V
https://mega.nz/#!accnkb6B!f_wdM79WXZ2UYy2El87DXYctihB40MBjV4imBKlhoDo
GUYS I HAVE ALSO FOUND A WAY TO DOWNGRADE N910T TMOBILE NOTE 4 TO KITKAT CHECK THR POST LINK BELOW.
http://forum.xda-developers.com/not...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
I MADE THIS THREAD SPECIALLY FOR NETWORK LOCKED N910P USERS TO TEMPORORY DOWNGRADE TO UNLOCK NETWORK. BUT IF YOU END UP USING KITKAT ROMS THE FINGERPRINT SENSOR WILL NOT WORK.
FIX FOR FINGERPRINT
Flash og5 5.1.1 bootloader only along with with Nadia 4.4.4 kernel flash in twrp and you get everything working with any kitkat rom.
Or flash 5.1.1 6.0.1 stock firmware the fingerprint will work fine and unlocking will stick permanently
HiT THANKS:good::good::good:
Can I go back to a non-rooted, stock KitKat ROM without tripping KNOX?
Trex888 said:
I have successfully downgraded to kitkat after pull my hair for days and unlocked for any sim worldwide if you guys like kitkat like me and wanna unlock your sim network follow these institutions.
Click to expand...
Click to collapse
Can you Odin any firmware after this?
If so, this is a game changer for kitkat lovers.
You can upgrade again to 5.1.1 & 6.0.1 n910p firmware but you cannot flash n910p official kitkat it will simply fail in odin.you can flash any kitkat n910p roms in twrp recovery with diffrent kernels also i have tested deodexed 4.4.4 n910p based rom and it works flawlessly with custom kernel .i have tested everything every firmware but sadly 4.4.4 n910p fail in odin .
Which kernel is it in that SprintxnoteRC2 rom? Any other kernel working with KitKat?
Ael kernel.
shadowcliffs said:
Which kernel is it in that SprintxnoteRC2 rom? Any other kernel working with KitKat?
Click to expand...
Click to collapse
Ael kernel
how long has this kitkat developer firmware been leaked?
and can't you downgrade to official kitkat from the oldest 5.0.1? most of the "first new OS upgrade" won't block downgrades
6.0.1 --> 4.4.4 dev --> oldest 5.0.1 --> 4.4.4 official
edit:
also, does the dev firmware format internalsd like PB5?
Does the unlocking persist when upgrading to newer firmware?
Returned from PG1 to NK2 ( BoBCaTROM v2.0) following OP's tips. Since the purpose of flashing the dev tar is to update bootloader, I deleted the system file from the tar ball and ended up with a smaller file about 130 MB
download here.
From the attached screenshot we can see, the modem is AOF1, the kernel is AEL 5.5 (which is not shown in the screenshot).
Sterist said:
how long has this kitkat developer firmware been leaked?
and can't you downgrade to official kitkat from the oldest 5.0.1? most of the "first new OS upgrade" won't block downgrades
6.0.1 --> 4.4.4 dev --> oldest 5.0.1 --> 4.4.4 official
edit:
also, does the dev firmware format internalsd like PB5?
Click to expand...
Click to collapse
This dev firmware i found accidently from a Chinese website they use to refurbish and spoof usa models to international models and resale again . I tried to flash official 4.4.4 but it fails in odin.its something to do with this developer firmware that it can let us downgrade to 4.4.4 .anyway you can use this dev firmware to downgrade and flash kitkat custom roms and kernels.
Binary invalid
Trex888 said:
This dev firmware i found accidently from a Chinese website they use to refurbish and spoof usa models to international models and resale again . I tried to flash official 4.4.4 but it fails in odin.its something to do with this developer firmware that it can let us downgrade to 4.4.4 .anyway you can use this dev firmware to downgrade and flash kitkat custom roms and kernels.
Click to expand...
Click to collapse
Dev firmware does not work. Tried downloading with chrome, firefox,opera and straight to the mega app. Odin shows this error message: md5 invalid! Binary is invalid. Have try to download the file 12 time, no luck. Any suggestions or help?.
MexiMax said:
Dev firmware does not work. Tried downloading with chrome, firefox,opera and straight to the mega app. Odin shows this error message: md5 invalid! Binary is invalid. Have try to download the file 12 time, no luck. Any suggestions or help?.
Click to expand...
Click to collapse
Try this one
Thanks. Downloading now, will let you know if it works. Thanks again.
Sterist said:
how long has this kitkat developer firmware been leaked?
and can't you downgrade to official kitkat from the oldest 5.0.1? most of the "first new OS upgrade" won't block downgrades
6.0.1 --> 4.4.4 dev --> oldest 5.0.1 --> 4.4.4 official
edit:
also, does the dev firmware format internalsd like PB5?
Click to expand...
Click to collapse
4.4.4 dev --> oldest 5.0.1 failed : sw rev check fail
Originally Posted by DjeMBeY
SW REV. CHECK FAIL : fused:2, Binary: 1 is when you try to downgrade aboot.mbn (bootloader) or try to flash incorrect system/csc etc..
Click to expand...
Click to collapse
Try this one
Thanks. It did work. Really appreciated your help.
shadowcliffs said:
Try this one
Click to expand...
Click to collapse
The file size is just 120.2 MB??
robinhood1808 said:
The file size is just 120.2 MB??
Click to expand...
Click to collapse
With system partition removed as mentioned in my earlier post. After all, bootloader is all you need.
shadowcliffs said:
With system partition removed as mentioned in my earlier post. After all, bootloader is all you need.
Click to expand...
Click to collapse
Hmmm... After flashing this firmware, without rebooting and going into download mode, one has to flash TWRP & then any Kit-Kat based custom ROM. Got it! :good:
MexiMax said:
Dev firmware does not work. Tried downloading with chrome, firefox,opera and straight to the mega app. Odin shows this error message: md5 invalid! Binary is invalid. Have try to download the file 12 time, no luck. Any suggestions or help?.
Click to expand...
Click to collapse
download file by mega app without pause or stop while downloading.
robinhood1808 said:
Hmmm... After flashing this firmware, without rebooting and going into download mode, one has to flash TWRP & then any Kit-Kat based custom ROM. Got it! :good:
Click to expand...
Click to collapse
flash kitkat rom with ael or any custom kernel otherwise it won't boot.