Hi, I've just recently switched over from iphone to android so I'm still new to the whole system. Anyway I've been trying to root my phone for the past 2 days to no avail so I'm at my wits end here. Before I start my phone is from korea which I don't know if whether or not impacts its ability to be rooted, I've done all the basics like enable USB debugging from dev mode, install samsung usb drivers, open ODIN in admin mode and allow MTP to computer. My Device details are below:
>Baseband version : G906SKSU1CPF1
>KERNEL : 3.10.40-8533426
>BUILD NUMBER : MMB29M.G906SKSU1CPF3
So anyway I first tried flashing using CF autoroot for sm-G906S with odin which while it said it was passed and was successful on pc it would be stuck on the samsung logo with a message at the top left that said :
>Recovery booting
>Recovery is not seandroid enforcing
>set warranty bit recovery
So then I tried flashing TWRP custom recovery and putting Super user zip in the internal storage which although got my phone back to working order still wouldnt let me root as the process required me to go to recovery mode from the fastboot mode after it was done flashing (I tried both with and without autoreboot), however once the flashing was done on fastboot I couldn't get to recovery mode no matter how long I held the Vol up/power/home button combination and when i tried it after rebooting it would show normal recovery mode hence there was no way to install the Super User. (Also attempted this with phils recovery)
I then tried to do the TWRP method using adb with command prompt however it would get stuck saying waiting for device when i tried to flash and needless to say kingroot also failed.
At this point as far I've gone through all the methods I could find for my particular device. Would greatly appreciate any insight or advice regarding this problem.
Thanks
start reading from here http://forum.xda-developers.com/gal...ner-thread-t2807639/post68725608#post68725608
Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!
Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.
SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?
Hello people.
So i got a custom recovery (TeamWin project) for my Samsung Galaxy A5 2016 [A510F] and disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Also fastboot doesn't recognize my device even though the right drivers are installed.
Have you tried Download mode ( vol - home button and power button) ?
Viesuliss said:
Hello people.
So i got a custom recovery (TeamWin project) for my Samsung Galaxy A5 2016 [A510F] and disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Also fastboot doesn't recognize my device even though the right drivers are installed.
Click to expand...
Click to collapse
Just download official firmware and flash with odin. (Make sure not to downgrade os version. )
go to downloadmode, be sure drivers are installed, COM must be green,flash firmware with odin "only PDA", return into bootlader after reboot, flash twrp, boot into recovery mode done
Same thing happened to me.
Don't search for any file, the solution is very simple: download Samsung Smart Switch (only Windows, Mac version didnt work for me).
On menu click "Others" then "Emergency software recovery". Write A510F and then your phone Serial Number. Wait 30/60 mins ?
Sent from my SM-A510F using XDA-Developers Legacy app
I am looking for a way to unlock the bootloader on my Samsung Galaxy S5 Plus (Sm-g901f, kccat6) with German t-Mobile branding (DTM) in order to flash Lineageos on it.
Is there a known way (executable for a newbie in Android flashing)?
Unfortunately my handset does not have a "OEM unlock" button in the developer options.
Is it possible to verify if the bootloader is locked apart from flashing a custom recovery and checking if it has been installed persistently?
i think you just have to flash twrp. if i remmeber correctly i had the same message that my bootloader was locked with my s4 i9506 back then
k2828 said:
i think you just have to flash twrp. if i remmeber correctly i had the same message that my bootloader was locked with my s4 i9506 back then
Click to expand...
Click to collapse
Even though my answer was posted a month ago, I want to present my solution:
As I said above, flashing TWRP did not worked on the way that all installation guides told me. But not because my bootloader was locked, the reason seems to be a bug (or is it a feature ) in TWRP.
The problem was, that the Stock OS is overwriting the bootloader on the first normal start.
What you have to do in order to prevent this mechanism:
1. Uncheck Auto-Reboot in Odin.
2. After Odin shows "PASS" shut your phone down and reboot it manually to the recovery.
3. In TWRP select Reboot and then System.
4. Done.
Now I am a lucky user of a LineageOS powered phone.
ooo yes thats a common odin bug for some phones..
dial25and said:
Even though my answer was posted a month ago, I want to present my solution:
As I said above, flashing TWRP did not worked on the way that all installation guides told me. But not because my bootloader was locked, the reason seems to be a bug (or is it a feature ) in TWRP.
The problem was, that the Stock OS is overwriting the bootloader on the first normal start.
What you have to do in order to prevent this mechanism:
1. Uncheck Auto-Reboot in Odin.
2. After Odin shows "PASS" shut your phone down and reboot it manually to the recovery.
3. In TWRP select Reboot and then System.
4. Done.
Now I am a lucky user of a LineageOS powered phone.
Click to expand...
Click to collapse
Why to shut down ?
When Odin passed !
Press download mode command keys
When screen goes black
Immediately press recovery commands !
And if u failed to reboot to recovery,flash firmware with nand erase all option !
As i experienced this issue!
I normally do the research myself and finally after a week i give up and can't find any sure way to do it. I've tried some stuff on Odin but get a fail message. I've rooted other phones before using Odin years ago, but this phone has been giving me lots of trouble. I have a Galaxy S7 with boost mobile. IT's a SM-G930P and awhile ago i updated it to 8.0 when it came out. Is there any way i can get TWRP on it or just anything at all?
Have you made sure FRP lock is disabled by ensuring enable OEM unlock is enabled in developer options in the phone settings? That will block flashing custom binaries (files) to the phone via ODIN download mode.
Steps below require factory resetting your phone so backup your data if you need to in advance.
I root most Samsungs with the following steps:
- Tap Build Number 7 times in settings > about phone > software info > build number to unhide developer options
- Enable OEM unlocking
- Reboot to download mode
- Flash TWRP custom recovery via ODIN that is compatible with your device and Nougat / Oreo
- Boot custom recovery, flash no-verity-opt-encrypt-6.0.zip, factory reset phone (optionally format data partition)
- Install / flash the SuperSU (version SR3 for example) via TWRP recovery to root your phone.
- Reboot phone and wait.
benjamen50 said:
Have you made sure FRP lock is disabled by ensuring enable OEM unlock is enabled in developer options in the phone settings? That will block flashing custom binaries (files) to the phone via ODIN download mode.
Steps below require factory resetting your phone so backup your data if you need to in advance.
I root most Samsungs with the following steps:
- Tap Build Number 7 times in settings > about phone > software info > build number to unhide developer options
- Enable OEM unlocking
- Reboot to download mode
- Flash TWRP custom recovery via ODIN that is compatible with your device and Nougat / Oreo
- Boot custom recovery, flash no-verity-opt-encrypt-6.0.zip, factory reset phone (optionally format data partition)
- Install / flash the SuperSU (version SR3 for example) via TWRP recovery to root your phone.
- Reboot phone and wait.
Click to expand...
Click to collapse
Thanks for the response. I think the issue from what i read is that TWRP can't be put on the SM-G930P, something about the bootloader being locked. I tried another method on here and had to end up wiping my phone since it bricked. It looks like my type of phone can't be rooted from the methods i've seen on here.