Is there any custom rom for galaxy a8 and any root support
http://choimobile.vn/threads/a800f-spacex-kernel-v0-1-auto-root-busybox-android-5-1-1.60311/
Root is done. No custom recovery yet.
WARNING DO NOT USE THE METHOD ABOVE IF YOU HAVE MODEL SM-A800I IT WILL SOFT BREAK YOUR DEVICE
YOU WILL NOT BE ABLE TO INSTALL STOCK FIRMWARE TO RESTORE YOUR DEVICE
IT WILL FAIL ON WRITING boot.img.
if that happened you have to download stock firmware and open it using winrar then extract boot.img, find a tool to create boot.tar for odin I used this one tar-Tool_Odin3-v3.07_by_mkh.mourad and flash it.
i had wiped my system for flashing rom but wasn't able to flash it bcoz i was showing error no when i try to reboot it shows no os wht should i do now plz help i dont have a backup and my model no. is a800i
If you have checked out, downloaded and flashed RaymanFX's latest CM13 Unofficial Nightly ROM for Note 4 N910C/H/U users here: http://forum.xda-developers.com/not...-cyanogenmod-13-semi-official-builds-t3259878 chances are you failed miserably at getting back to Samsung's Stock Firmware as you have encountered a series of unending bootloops. The bootloops exist because your downgrading from Android 6.0.1 Marshmallow (CM13 ROM) back to Android 5.1.1 Lollipop (Your previous Original Samsung Stock Firmware), however if you've received the Android Marshmallow Update for your Note 4 model number and region as an OTA Update from your device or Manually by downloading it from sammobile.com or any other external link and have flashed it before flashing CM13 no need to worry you won't need a backup of your Samsung firmware (Unless you want one) as you can perform a clean install of your Samsung Marshmallow Firmware via Odin v3.10.7 Here is where the fix lies; i have compiled a series of posts from 2 very helpful XDA Members from the community because from my experience i have managed to rescue my device using their methods which i will mention below.
Firstly if you have made an Efs partition backup from your previous Original Samsung Stock Firmware in the form of a .tar or .img file e.g "efs_backup_2015-06-01_02-37-16.tar" or "efs.img" respectively then you are good to go if not leave this thread.
Also you will need to download a Note 4 N910C/H/U Pit file corresponding to the region of your Samsung Firmware so here is a link to a selection of pit files. You will need to create an account at sammobile or simply sign if you have a current account to see the download links here: http://www.sammobile.com/forum/showthread.php?t=30022
Follow FR34K-B1B0's helpful post on getting back to stock here: http://forum.xda-developers.com/showpost.php?p=65414257&postcount=39 Skip the 1st Step since we are restoring our IMEI using our backed up Efs file and we will be using a different method to restore this backup.AND AFTER ODIN IS DONE FLASHING THE SAMSUNG FIRMWARE there is a chance that your phone will boot to the Stock Recovery and you will notice a message down there saying: "dm verification failed" so simply wipe data/factory reset and wipe cache and then reboot. Afterwards your phone should boot properly. Now close he's post and carry on down here.
After your phone boots up and you have set it you will notice that your mobile is not connected to your specific mobile carrier and you will see the Emergency calls only text on your lockscreen hence the Not registered on network error. Go to Settings--->About device--->Status and scroll down and you will search and find that your IMEI is literally not the one your phone has and that your Serial number is of an Android Serial number given to you from flashing CM13( Since it's a pure stock android software). If you want you can download the Phone INFO App from the Playstore to verify your device's information and if you do so you will notice that your Samsung Serial number is a bunch of 0's like this: 0000000000 or it's not even present hence wiped.
HERE IS THE MOST IMPORTANT PART FOR RECLAIMING YOUR MOBILE NETWORK CONNECTION, your IMEI is wiped and so you must restore it using your Efs backup file which i mentioned previously above. To do so you will need to root your device and the guaranteed way of rooting your device is using Chainfire's CF-Auto-Root Method.
Here are the links to the Odin flashable MD5 files based on your Note 4's Model Number that you must download ---> For SM-N910C: https://download.chainfire.eu/559/CF-Root/CF-Auto-Root/CF-Auto-Root-trelte-treltexx-smn910c.zip For SM-N910H: https://download.chainfire.eu/577/CF-Root/CF-Auto-Root/CF-Auto-Root-tre3g-tre3gxx-smn910h.zip For SM-N910U: https://download.chainfire.eu/557/CF-Root/CF-Auto-Root/CF-Auto-Root-trhplte-trhpltexx-smn910u.zip After downloading the file on to your computer simply load the file through Odin, power off your phone and boot it to download mode then connect your device to your computer and flash the md5 file. After it's done flashing your device will boot to a custom screen with a red android logo then it will boot.
Right now your device is rooted and you will see the Supersu app in your app drawer. Next if your Efs backup is stored on your computer and is of the format .tar simply open it with 7zip or Winrar you will find the .img present then extract it your desktop. In order to restore your IMEI with this .img file we will need an update package that we can flash from a custom recovery(CWM or TWRP). Here is the link to civato's awesome flashable update package: http://forum.xda-developers.com/showthread.php?t=2331853 and you'll find the package down in the attachment. After downloading the attached file, rename your Efs backup file from "efs.img" to "EFS.img" then extract the contents of the downloaded update package to a folder with the same name of the package, copy your EFS.img file to it and use 7zip or Winrar to add the files to an archive(.zip).
Last but not least copy the new repackaged flashable zip to your external or internal sd card. Run Odin and flash your desired Custom Recovery(CWM or TWRP). Boot to the custom recovery and flash the update package and finally reboot system. After booting your phone will have it's Efs partition restored; your IMEI and Samsung Serial number will be back and your mobile network will be back on again. :fingers-crossed:
Special thanks to FR34K-B1B0 for he's helpful post on getting back to stock firmware
And Many Many Thanks to civato for he's really useful Efs restoring update package! :victory:
And last but not least thank you Chainfire for your great CF-Auto-Root Method that helped root our device(s).
Hi XDA community, i want try to downgrade in my A310f from Android 6.0.1 to 5.1.1. It's possible? I try to download the 5.1.1 from Sammobile, but when i flash the firmware with odin i get the error "SW Rev Check Fail" in my phone and "md5 error" from odin.. there are some method?
MMBB29K.A310FXXU3BQC2 is my model. Tell me please here
allenbtc said:
MMBB29K.A310FXXU3BQC2 is my model. Tell me please here
Click to expand...
Click to collapse
If your bootloader also is upgraded to A310FXXU3 then it won't be possible to downgrade to 5.1.1 through odin.
Maybe with a modified package without cm.bin, modem.bin, sboot.bin. Otherwise, make it flashable and use twrp.
With Odin you'll only be able to downgrade to the latest 6.0.1 which is also A310FXXU3.
how i can flash with twrp?
---------- Post added at 02:02 PM ---------- Previous post was at 01:57 PM ----------
tys0n said:
If your bootloader also is upgraded to A310FXXU3 then it won't be possible to downgrade to 5.1.1 through odin.
Maybe with a modified package without cm.bin, modem.bin, sboot.bin. Otherwise, make it flashable and use twrp.
With Odin you'll only be able to downgrade to the latest 6.0.1 which is also A310FXXU3.
Click to expand...
Click to collapse
how i can flash with twrp?
tys0n said:
If your bootloader also is upgraded to A310FXXU3 then it won't be possible to downgrade to 5.1.1 through odin.
Maybe with a modified package without cm.bin, modem.bin, sboot.bin. Otherwise, make it flashable and use twrp.
With Odin you'll only be able to downgrade to the latest 6.0.1 which is also A310FXXU3.
Click to expand...
Click to collapse
I can confirm this method is working, I have successfully downgraded an A3 2016 from A310FXXU3BQD2 to A310FXXU2BQA3.
I used the Tar tool from this thread with all the files from the update I wanted to downgrade to, except sboot.bin, cm.bin and modem.bin. It's very important to NOT copy those files to the tool folder because otherwise your phone will be laggy and SIM unusable (if you use the old modem) or you will not be able to flash like with the original tar (if you use old sboot or cm).
So after I ran the batch file, I did a wipe data/factory reset using original recovery and then I flashed the "all files" tar the tool created using Odin in AP (only Auto Reboot and F. reset time checked) and the phone in download mode, and It worked like a charm.
With this method you can likely have any old update flashed while keeping the latest secure bootloader, cm and modem. (Notice that after the downgrade, the phone cannot find any new updates, maybe it's related to the bootloader being the latest or the fact I only downgraded to the previous update...)
dealth645 said:
I can confirm this method is working, I have successfully downgraded an A3 2016 from A310FXXU3BQD2 to A310FXXU2BQA3.
I used the Tar tool from this thread with all the files from the update I wanted to downgrade to, except sboot.bin, cm.bin and modem.bin. It's very important to NOT copy those files to the tool folder because otherwise your phone will be laggy and SIM unusable (if you use the old modem) or you will not be able to flash like with the original tar (if you use old sboot or cm).
So after I ran the batch file, I did a wipe data/factory reset using original recovery and then I flashed the "all files" tar the tool created using Odin in AP (only Auto Reboot and F. reset time checked) and the phone in download mode, and It worked like a charm.
With this method you can likely have any old update flashed while keeping the latest secure bootloader, cm and modem. (Notice that after the downgrade, the phone cannot find any new updates, maybe it's related to the bootloader being the latest or the fact I only downgraded to the previous update...)
Click to expand...
Click to collapse
Thanks for confirming. I've never tried it myself but I figured those bins are the U1/U2/U3 binary files that are protected for downgrade, so it should probably work without them
Now we know how to easily downgrade without errors.
Downgrade
Hello,
With my sm-a310f I downgraded from Nougat to Marchmallow but could not get back to Lollipop.
I used TWRP and Odin.
I saw that there were solutions but they are not universal. Can someone point me?
Thank you
menuisier3 said:
Hello,
With my sm-a310f I downgraded from Nougat to Marchmallow but could not get back to Lollipop.
I used TWRP and Odin.
I saw that there were solutions but they are not universal. Can someone point me?
Thank you
Click to expand...
Click to collapse
https://forum.xda-developers.com/samsung-a-series/general/rom-t3614602
flash combination rom before flash full 4 file stock rom 5.1 , u can downgrade your phone.
Tanle11 said:
flash combination rom before flash full 4 file stock rom 5.1 , u can downgrade your phone.
Click to expand...
Click to collapse
No! You can't downgrade bootloader even if you use a 4 file repair firmware.
As far as I am aware of, this is the only possible way to downgrade to 5.1.1 if you are on new bootloader/modem (tested by me - works fine, I am on the newer bootloader/modem combo) :
https://forum.xda-developers.com/samsung-a-series/general/rom-t3614602
(consider this however ONLY if you are willing to trade 5.1.1 for the warranty as you would need to flash TWRP in the process first)
I rooted the G950F italian version with oreo according to this guide
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
.... at last step in recovery twrp i didn't permit to install again twrp and unchecked. reboot shows samsung logo and then goes off. in recovery didn't access and i was constrict to install stock recovery. now i am on stock recovery but unable to flash again the twrp for error check file bootloader device 3 binary 1.
i can't flash the official stock rom because goes error only official can install......
ONLY OFFICIAL RELEASED BINAR ARE ALLOWED TO BE FLASHED please help
i installed in s8 italian version the files linked in first post. please help
IF I TRY TO INSTALL CRF7 ROM WITH 4 FILES AND HOME CSC IT SHOWS: CHECK FILES (BOOTLOADER) DEVICE 3 BINARY 1
is like i have not more recovery and i can't reflash with odin... i need help please
That error suggests you are flashing older firmware than what's on the device
how can i solve for motivation that every flash, even the last firmware goes on???
it stucks after click start button in cosmy odin.....
i cannot flash again the twrp, i cannot flash stock firmware, i flashed only bl file, but all errors.......
what can i try?
i hope a suggest
thanks
Here are some photo....
if i try flash 3 files with csc NOT home and without bl file, the result is so:
https://ibb.co/b2UA5K
https://ibb.co/jxZGee
If i try to flash all 4 files the results is so:
https://ibb.co/b2UA5K
https://ibb.co/muYnkK
if i try to flash only twrp the result:
https://ibb.co/mCSrCz
https://ibb.co/m4Geze
Why root this phone?
What mean with my problem???
hey,
Try flashing latest firmware with patched odin
Here is a long story. Please read carefully before reply.
I have SM-G955N which is for South Korea. Also I have latest stock firmware that can be flashed with Odin. It has AP, BL, CP, CSC. With this firmware, I can recover from almost every problems(including bootloop) because these files have everything that my S8+ should have, even PIT file.
As you know, modifying stock firmware is very dangerous and you don't know what would happen if you delete/modify certain file.
You might think 'Hmm... I think it is completely not related to system or samsung so maybe I can delete this' but you can get bootlooped. I even got bootlooped by only deleting DioDict which is just dictionary app!
I think It would be much easier to recover from bootloop when I have flashable ZIP file that is pure stock firmware.
Maybe you can say 'Just use TWRP backup feature!' but I can't trust TWRP backup feature now.
When I flashed stock firmware with Odin and right after(after solving KG State thing), flashed TWRP. Then I should have pure, clean stock firmware because I didn't touch anything about system except recovery(TWRP), right? I backupped whole system except Cache because It has 0 MB size.
After I got bootloop while modifying system, I restored that backup but still got bootlooped. That's why I can't use TWRP backup as fallback plan. I can't trust it 100%.
There are few 'Kitchen' scripts but I think they only handle AP files. When I tried to use SuperR's Kitchen Free, I used stock firmware file(tar.md5) and didn't do any modification. After I made flashable ZIP file with it and flashed it with TWRP, I've got bootlooped because It didn't have critical CSC files that system needed.
I think the Kitchen can't handle CSC well even though It is critical. 'Donate' would be last resort.
I've found batch script that convert S9 stock firmware to flashable ZIP (at GItHub, 'harise100/S9-Stock-ROM-TWRP') but I don't think It can cover S8+ files. In the scripts, it requires some files that S8+ firmware don't have. Maybe I should play with that script to fit with S8+ but It will take a lot of time which I don't have much.
Any good idea or information about converting stock firmware to flashable ZIP file?