Hi
I am trying to install lineageos onto a used samsung galaxy s4 mini I recently bought, but I cannot boot TWRP (yes, I am using the correct recovery-boot button combination,
vol-up + home + power). I've tried searching, but nearly all posts with similar titles have been closed when someone tells OP the recovery-boot button combination, and the
others were various unique problems, as far as I can see.
I used the v3.0.3-0 TWRP from here https://forum.xda-developers.com/showthread.php?t=2678420, extracted the file recovery.tar.md5 and used odin v 3.12.3 to flash it onto the
phone using the "AP" option. Odin displayed no errors, only "PASS" and other success messages. I had switched off auto-reboot, so I rebooted to recovery using vol-up + home + power but I only get the screen:
"Could not do a normal boot. ODIN MODE PRODUCT NAME: GT-I9195I CURRENT BINARY: Custom SYSTEM STATUS: Custom REACTIVATION LOCK(KK): OFF KNOX WARRANTY VOID: 0x0 QUALCOMM
SECUREBOOT: ENABLE (CSB) AP SWREV: S1, T1, H1, A1, P1 SECURE DOWNLOAD: ENABLE"
"Downloading... Do not turn off target!!"
This is not download mode (which I normally reach with vol-down + home + power), but looks very similar aside from the
"Could not do a normal boot." message.
I've tried this several times, trying alternatives Odin 3.10.6 and TWRP v2.6.3.0.
I've not got to any recovery mode for this phone, TWRP or otherwise.
It is not bricked or in a bootloop. If I reboot I can get to android and use the phone.
Can anyone help me install and boot to TWRP please?
I don't know what to try next.
I bought this phone used so I do not know its installation/updates/rooting/flashing history, though it looks pretty vanilla.
Thanks
Crap, I have the exact same issue with TWRP versions higher than 3. Version 2.8.7.0-serranoveltexx does work, but I cannot install lineage (I tried 16 and newer). I simply get "Error executing updated binary in zip '...' and 'Error flashing zip'. And before that, for most versions of linage, it says "the package is for device: serranovelte,serranoveltexx; this device ."
If I tried a lineageversion from another developer, it says that the device is "serranovelte". So yeah, I'm stuck with that unfortunately. Any help would be much appreciated.
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
tnsmani said:
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
Click to expand...
Click to collapse
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
EpicLawR said:
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
Click to expand...
Click to collapse
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
tnsmani said:
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
Click to expand...
Click to collapse
My device was detected as a 9008 by my computer, but by the tool it was detected as a com device. driver signature vertification was disabled when trying the tool multiple times, but i can try to use it on another computer.
Sideloading the OOS rom didn't work the first time i tried it, but i am not very familiar with that so i can try that again aswell.
Thanks.
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Try to flash stock recovery if succeeded then wipe complete, after twrp with root and then install stock oos
Msmdownload is low level format tool, another method of flashing won't work if it isn't.
Since you said that msm reported succeed but after it you still got a hash fail, it's either you flash the wrong file or a you've got a bad emmc..
You can't easily brick a Oneplus device. At worst you've screwed up your options for self-contained flashing via twrp. The two most common issues restoring to stock via sdk tools on a PC are i) wrong drivers being used, make sure you've installed the oneplus drivers on your computer and the device is recognised properly; and ii) you don't have full admin rights - make sure you've run the CMD shell as administrator before you execute any of the sdk commands.
hello
1.do u unlocked your bootloader?
2.connect your phone to PC into bootloader, if you can... try these codes with fastboot
fastboot erase cache
then
fastboot flash recovery ***.img
then
fastboot boot ***.img
then you should see you recovery....
before flashing ROM go to mount and mount system,recovery and data
then flash ROM
Hello. I attempted to flash my SM-G960U (from Cricket Wireless) with firmware, G960U1OYM4CSC7, from SAMMOBILE. I downloaded the Samsung USB drivers. I used 7-zip to extract the files from SAMMOBILE. There was an MD5 error on the extraction of the AP file. I deleted the ".md5" file extension, making it just a .tar file to allow it to load into Odin. I used the Odin3 v3.13.1_3B_PatcheD. I put my phone into download mode, connected to my PC, and started the flash. The process failed. Now the phone says "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." I downloaded that, but selecting the recovery function doesn't do anything. There is an option to recover using a recovery code, but I don't know what code to use.
There is a small black bar with "SECURE CHECK FAIL : system" in the top left corner of the S9 screen. It doesn't seem to respond to any of the buttons.
I did manage to note the baseband version of my phone. It's G960USQS3BRJ6. Any help to recover my phone and correctly flash would be greatly appreciated.
Work only on Oreo 8
You must be Stat Normal
Oem Unlocked
Enable USB Debugging Mode and OEM Unlock in your mobile. To do this; go to settings >>> about >>> Tap on the “Build Number” 7-10 times consistently to enable “Developer Options,” then go to the “Developer Options” and enable USB Debugging Mode and OEM Unlock. There is no complicated process in the Samsung Galaxy J7 Duo.
Download and install the Samsung USB driver to your computer system.
Also, download the ODIN software. Select above Oreo version in the ODIN list. Install ODIN in your PC.
Download Magisk.Zip (Download Latest version) and forced encryption disabler, Copy it to Your Phone Memory. We Need to flash encryption disabler to avoid Boot Warnings in the future after the Root process.
Download and save the TWRP File. Select Correct TWRP file from Below. This TWRPs can support Up to Oreo.
SM-J720F
SM-J720M
Flash TWRP using ODIN
Samsung Galaxy J7 Duo Download Mode
Connect your USB Cable with PC. Switch off your device. Then, enter into Download mode. To do this; press and hold down the Volume Down + Home + Power buttons and connect your micro USB Cable.
Samsung Galaxy J7 Duo Download Mode Warning Screen
Press the Volume Up button to continue when you see the warning message.
Now, connect the Samsung Galaxy J7 Duo mobile to the computer via USB cable.
Launch the Odin app on your computer. If the device is detected by this app (Odin), it will show you a message that reads – added!!!
ODIN Added Message
However, if the device is not correctly connected to the PC, you won’t see this message. So, you have to check the USB cable if it is reasonable and reconnect the device.
After connecting the Samsung device, click on the PDA/PA button to browse/search and get the TWRP from where you saved it on your PC. Also, navigate to “options” and tick the Auto Reboot.
Odin Auto Reboot
Click on “Start”
Once the file is loaded into the device, reboot your device.
Kudos, you have just Installed the TWRP on your Samsung Galaxy J7 Duo. If you installed TWRP, Don’t turn on your mobile. Immediately, move to Magisk Installation steps.
You should not Boot into Normal OS Booting, after TWRP. After TWRP Flash, Immediately Boot into Recovery or twrp will gone
Boot it Into recovery mode->Volume Up + Power Button.+Home
Now it Will Boot into TWRP Recovery Mode.
Install Magisk, forced encryption disabler in your Samsung Galaxy J7 Duo using TWRP
Select Wipe->Advance Wipe->Select Cache Data.
Return to Home of TWRP select Install.
Select Magisk.Zip.
After Installation again Navigate to Home select Install. Select forced encryption disabler.
After the Installation Reboot Your Mobile.
You can also install Magisk.apk in your Mobile Applications. Forced encryption disabler is used to avoid the boot loop issue after rooting.
enjoy
SM-J720F
SM-J720M
encryption disabler
Samy6699 said:
Work only on Oreo 8
SM-J720F
SM-J720M
enjoy
SM-J720F
SM-J720M
encryption disabler
Click to expand...
Click to collapse
Can it be used on the Dual-Sim version SM-J720F/DS released in 04/2018 ?
Can i install it on Galaxy J7 Duo running Android pie
Nitin devarasetty said:
Can i install it on Galaxy J7 Duo running Android pie
Click to expand...
Click to collapse
i also need that man.
Please make one thing clear
Do we have to turn off "Auto reboot"
Or keep the "Auto reboot" option checked on?
Android 9.0
Hello, when it will be possible ? If never, why ?
I followed the exact process but everytime i tried to boot into TWRP recovery immediately after the flashing, the device still boots into stock recovery instead of TWRP
Please help me with this
Thank you
I figured out a way to root the Galaxy J7 duo
Actually i have tried lot of ways to root using TWRP flash and all.. but one day i accidentally bricked my device
So i downloaded the stock ROM to flash my device
And i downloaded the 8.0 android ROM
So this root method basically tested on android 8.0
So now i have android 8.0 stock ROM downloaded
Step 1 -
So make sure you also downloaded the ROM
And extract the ROM file (you must have got the "AP" "CP" "BL" "CSC" and "HOME CSC" file)
Then copy the "AP" file in your phone
Then install magisk manager in your phone
Open magisk, select install, select and patch a file from magisk
Then select "AP" file
And wait while magisk is patching the "AP" file
When flashing is done the patched file will be saved on storage, emulated, 0, download (file will be saved as "magisk_patched.tar")
Then simply copy the patched file in your computer
Step 2 -
Open odin in your Computer
In odin, select "magisk_patched.tar" in "AP" section
Select "BL" from the stock ROM folder in the odin's "BL" section
Select "CP" from the stock ROM folder in the odin's "CP" section
Select "HOME CSC" from the stock ROM folder in the odin's "HOME CSC" section
make sure you select all the official files from the stock ROM folder... just instead of the "AP" file, select the "magisk_patched.tar"
Then connect your phone via USB cable
Odin will detect and show "added" message
Start the flashing process
It will take few minutes
When its done your phone will boot up
But it will show something like "erasing" and "verification unsuccessful"
Just agree with that and erase the phone
(It will cause a data loss because everything will be deleted and your phone will reset, so i suggest to make a backup using samsung smart switch)
Then when your phone will reboot, just follow the steps to setup
Amd install magisk latest apk
Open magisk and boom!
You can already realize that magisk root is activated
Amd magisk will ask you to "setup environment"
Just agree and your phone will reboot withing 5 seconds
And done!
Your phone is now rooted
Install root checker and verify your root status
how to un-brick
Same thing here,
Tell me how you un-bricked your phone
I bricked my phone by installing wrong twrp file to sm-j720f android pie with odin
and now it shows only bootloader screen and I can't even go to recovery mode or home screen just showing " SAMSUNG GALAXY J7 DUO secured by Knox powerd by android" noting else
That is exactly what was happened in my phone
So what i did just downloaded the Stock ROM for J7 duo from the sam mobile website.
Then extract the ROM and you will get few files ("AP", "BL", "CP", "CSC", "HOME CSC")
Then boot your phone into download mode using this method
(Connect the phone to your PC using USB cable, then press and hold Power + volume down + home, then when the "powered by android" logo appears release only the power button... so your phone will boot into download mode, press volume up to continue)
Now, in odin you can see "added" message that means device is connected
Now select the ROM files respectively, BL, AP, CP, CSC
Then click start, and the process will start, will take few minutes
When done, your phone will boot normally
Yeah everything is right until...
[grand_theft;83142325]That is exactly what was happened in my phone
***********
So what i did just downloaded the Stock ROM for J7 duo from the sam mobile website.
Then extract the ROM and you will get few files ("AP", "BL", "CP", "CSC", "HOME CSC") *********
Then boot your phone into download mode using this method
Fact that I cant even go to download mode I tried out many times
Just follow this step
(Connect your computer with your phone using USB cable, then press and hold Power + volume down + home, then when the phone vibrates and appears the samsung logo again just release only the power key, while holding the volume down and home key)
(Just release only the power key when the "powered by android" logo appears)
Thats how you can go to the download mode
No virtual change
Done it as u say,
But my mobile shows noting but just logo screen
*****SAMSUNG GALAXY J7 DUO secured by Knox powered by android*****
again and again
These is not first time, last I did the same mistake before and I went to Samsung service store they recovered it, I don't know how they did but it worked.
These time I want to (tring to) do it on my own bcoz I love playing with ROM's, root, etc.
Thanks for replys
I also did the same mistake by flashing wrong TWRP
But however i managed to enter into downlod mode following those steps
And flashed official ROM to unbrick the phone
You must go into download mode to flash the official ROM using odin
Thanks alot
Thanks man,
I'm able to enter download mode and I installed official ROM. Now in using it as normal but (1)Secure folder and Pay mini are not working.
(2)Do you have any idea on other ROMs that works on SM-J720F other than Samsung's one UI.
(3)can I install android 8 on it in ordered to root as you said it in previous post.
(4)from previous your post on oreo twrp explanation, is twrp works fine. What happens to twrp if I update phone to Q (from system updater)
I'm glad you made it!
Now,
1) Secure folder and pay mini won't work because the phone thinks you rooted your phone and maybe your binary is cracked (so forget using those)
2) I'm not sure about any ROMs which is stable with this model. But you can search the internet (I think pixel ROM is pretty popular)
3) I'm not sure if my process of rooting supports android 9.0 or not, because i personally tetsted it on 8.0, So you can download the oreo ROM from the internet and then follow all the steps i mentioned before
4) If you want to install TWRP, you can still install TWRP after rooting via the method i provided
(You can install TWRP using flashify on a rooted phone)
But if you want root access then you can simply root your phone first..
And whatever custom ROMs you want to install, install it using flashify
Because if you update software via official OTA, the root access and TWRP both will be gone
And if you root your phone, then however you won't be able to perform a official OTA update.
(First root your phone, then simply download your TWRP file and flash it with root permission within your phone)
Instated of Oreo AP file,
grand_theft said:
I figured out a way to root the Galaxy J7 duo
Actually i have tried lot of ways to root using TWRP flash and all.. but one day i accidentally bricked my device
So i downloaded the stock ROM to flash my device
And i downloaded the 8.0 android ROM
So this root method basically tested on android 8.0
So now i have android 8.0 stock ROM downloaded
Step 1 -
So make sure you also downloaded the ROM
And extract the ROM file (you must have got the "AP" "CP" "BL" "CSC" and "HOME CSC" file)
Then copy the "AP" file in your phone
Then install magisk manager in your phone
Open magisk, select install, select and patch a file from magisk
Then select "AP" file
And wait while magisk is patching the "AP" file
When flashing is done the patched file will be saved on storage, emulated, 0, download (file will be saved as "magisk_patched.tar")
Then simply copy the patched file in your computer
Step 2 -
Open odin in your Computer
In odin, select "magisk_patched.tar" in "AP" section
Select "BL" from the stock ROM folder in the odin's "BL" section
Select "CP" from the stock ROM folder in the odin's "CP" section
Select "HOME CSC" from the stock ROM folder in the odin's "HOME CSC" section
make sure you select all the official files from the stock ROM folder... just instead of the "AP" file, select the "magisk_patched.tar"
Then connect your phone via USB cable
Odin will detect and show "added" message
Start the flashing process
It will take few minutes
When its done your phone will boot up
But it will show something like "erasing" and "verification unsuccessful"
Just agree with that and erase the phone
(It will cause a data loss because everything will be deleted and your phone will reset, so i suggest to make a backup using samsung smart switch)
Then when your phone will reboot, just follow the steps to setup
Amd install magisk latest apk
Open magisk and boom!
You can already realize that magisk root is activated
Amd magisk will ask you to "setup environment"
Just agree and your phone will reboot withing 5 seconds
And done!
Your phone is now rooted
Install root checker and verify your root status
Click to expand...
Click to collapse
************************************************************************************************************************************************************************************************************************************************************************************************************
Ok I agree with you,
But what if I replace Oreo's AP file with android 10's AP file(which I installed recently on my phone), will it boot with root or not.
************************************************************************************************************************************************************************************************************************************************************************************************************
I have not tested this method on any other android version, you can still try it on your own, there is nothing to lose, just make a backup before flashing. If you succeed then that's great
But i have personally tested this method only on android 8.0
(Before doing anything, just make a proper backup using samsung smart switch. So you can restore your important data)
Success
Replaced with android 10's AP file and flashed with Odin. Now my phone has rooted with Magisk manager.
Any suggestions to tweak android
Claudio4780 said:
Can it be used on the Dual-Sim version SM-J720F/DS released in 04/2018 ?
Click to expand...
Click to collapse
Have you ever got the answer or figured it out? I've got the same model and I cannot find anything on the net to help me with rooting this phone.
Hello everyone,
How do I resolve the message "MDM IS SET. Phone will be reboot 3 sec" and or "MDM MODE. CAN'T DOWNLOD [2] eMMC write fail: SBL1".
I have a device samsung galalxy A6+ (SM-a605GN) in a loop showing the message "MDM IS SET. Phone will be reboot 3 sec", I can't get into recovery mode or hard reset, I can only access download mode. However, I can't install a new rom via odin (stock or custom, I tried several versions of binary and odin), how do I solve or what would be "MDM MODE. CAN'T DOWNLOD [2] eMMC write fail: SBL1" or would it have some other way to fix without odin
You're in the wrong forum buddy.