Related
So i recently bought my Samsung galaxy A 10 ,I have been trying to root it but no luck.i unlocked the bootloader, installed proper adb drivers and latest version of odin on my Pc. I was following procedures from rootmydevice.com slash root-samsung-galaxy-A10(sorry cant post external links, im new).evrything went fine up until i got to the flashing part using odin. I am not sure weather the twrp file is corrupt or I am missing something.anyone who might know please help.
here is my device info:
SM-A105F
Have you tried this tutorial:
https://forum.xda-developers.com/galaxy-a30/how-to/root-galaxy-a30-magisk-canary-relaese-t3936481
I'm stuck in two problems here...
1- I dont have the option OEM Unlock on my developers option. I think that it maybe because ive checked that option before and after that it desapeared... When entering on download mode, it shows OEM Lock: ON (L), i dont know if that means OEM is unlocked or locked...
2- I cant find the files in step 2: .extract the boot.img.lz4 from the AP file.
Just came here to find a root method for the SM-A105M. Seems like not a lot of love for the A10 here.. Lol Anyways, I will be testing this method I came across out tonight. I will post the link but can't confirm it's working. I'll post my results tomorrow.
https://rootmydevice.com/root-samsung-galaxy-a10/
Sassiest said:
Just came here to find a root method for the SM-A105M. Seems like not a lot of love for the A10 here.. Lol Anyways, I will be testing this method I came across out tonight. I will post the link but can't confirm it's working. I'll post my results tomorrow.
https://rootmydevice.com/root-samsung-galaxy-a10/
Click to expand...
Click to collapse
do not flash that recovery is for sm-a720f aka A7 2017 https://www.gsmarena.com/samsung_galaxy_a7_(2017)-8335.php
hanonicaro said:
Have you tried this tutorial:
https://forum.xda-developers.com/galaxy-a30/how-to/root-galaxy-a30-magisk-canary-relaese-t3936481
I'm stuck in two problems here...
1- I dont have the option OEM Unlock on my developers option. I think that it maybe because ive checked that option before and after that it desapeared... When entering on download mode, it shows OEM Lock: ON (L), i dont know if that means OEM is unlocked or locked...
2- I cant find the files in step 2: .extract the boot.img.lz4 from the AP file.
Click to expand...
Click to collapse
Hi everybody,
I managed to root my A105FN with this method but with using the Magisk Manager v7.3.1 (no need of Magisk Canary)
It will be good to have a TWRP as welll but couldnt find a compatible one for the A10 (maybe useful for no-verity-opt-encrypt-6.0 and RMM-State_Bypass_Mesa_v2 patch)
we need :
1. odin 13.3.1
2. official firmware for your device (to get the boot.img from AP_xxxx part => follow the other tutorial how to get boot.img and boot.tar magisk patched)(keep an original boot.tar, just in case stuck at boot)
3. 7zip ZS
4. Last Magisk Manager (for me was v7.3.1)
5. computer + usb cable
Warning : this root will give you big warning messages at every boot !
First you need to unlock your bootloader :
1/Under android, activate internet and go under "Developper Mode" (Setting>About>Software>Build Number and Tap on the build number repeatedly). OEM unlock option should be there.
If not wait and retry to see if there ... (needs internet, dont know why)
2/Then go under Recovery Mode (VolUp + Power at phone boot). No method to go "Download Mode" directly for my device.
3/Under Recovery, we need to unlock the bootloader as well. I cant remember what exactly I pressed but try to press VolUp or VolUP+VolDown just after you click to reboot under bootloader... It should show you a page where you can choose to unlock bootloader by long pressing VolUP. if you dont have it, retry again ... without that no Flash possible.
Warning : this unlock will give you a big warning at every boot !
4/if you managed to unlock the bootloader, it s almost finished... know under Download Mode with bootloader unlock, flash with Odin the magisk patched boot.tar. Do not forget to untick "reboot" under Odin.
(reminder:follow the other tutorial to get the file and remember to use the Magisk Manager v7.3.1 and not the canary.)
5/when flash done, reboot by pressing VolDown+Power then immediately on reboot VolUp to go under Recovery Mode.
6/Under Recovery, erase data/factory reset and reboot to system
(7/I dont know if it s necessary the VolUp at reboot till the vibration)
8/wait the booting ... if you are stuck on the warning page for a long time, retry to reflash the original boot.tar and restart from "1/"
9/if you managed to boot under android, good news you are rooted but it s not finished yet....
Under Android check you have "OEM unlock option" under Developper Mode (cf. 1/) otherwise at the reboot the system will go KO.
So when you have "OEM unlock" enabled you can install Magisk Manager. It will ask you to install something and it will reboot automatically. That s why check you have "OEM unlock" enabled before doing that !
10/After reboot, Done. ROOTED.. enjoy ! you can reboot as you want ...
Hi everybody
Yes, I facing same everyone's problem, I see on "download mode" it's show "OEM Lock: On (L)" I try all the ways to unlock in YouTube but no any method to unlock
I try to unlock with all tools I have but useless (my tool: Z3X, Miracle box, MCT Dongle , NCK Dongle, Octopus Suite Unlock, Samkey Unlock Crack)
I try to flash Custom Rom with Odin , Try to Install "Magisk" and "TWRP" by method in many website , it's useless at all
However I think I need to unlock OEM first but I can't because OEM not show in the developer option
I try all the ways to appear the OEM Unlock toggle by a changing date, Flash tar.md5, factory reset in many website it's can't help me
Samsung developer very strong and can't hacking to "OEM Lock : On (L)" on Android Pie 9.0??
1.power off device
2.while press and hold vol+ and vol- plug the data cable with pc
3.then warning screen apper
4.volume up long press.
5.then press volume up.
bootloader will unlocked!
*sorry for my bad english
keepfun said:
Hi everybody,
er Download Mode with bootloader unlock, flash with Odin the magisk patched boot.tar. Do not forget to untick "reboot" under Odin.
Everything is about having this flash file you said you used. Please send us the link for that twrp file or whatever it is called right now as it is maybe not a Team Win Rom.
Thank you for your help
Click to expand...
Click to collapse
Hi,
It is not a TWRP file, it is the boot.img file from the original firmware for A10, patched with Magisk to access the root function, unfortunately it does not work, have tested it.
Benjamin.L said:
keepfun said:
Hi everybody,
er Download Mode with bootloader unlock, flash with Odin the magisk patched boot.tar. Do not forget to untick "reboot" under Odin.
Everything is about having this flash file you said you used. Please send us the link for that twrp file or whatever it is called right now as it is maybe not a Team Win Rom.
Thank you for your help
Click to expand...
Click to collapse
Click to expand...
Click to collapse
IneedFiveMore said:
Yes, I facing same everyone's problem, I see on "download mode" it's show "OEM Lock: On (L)" I try all the ways to unlock in YouTube but no any method to unlock
I try to unlock with all tools I have but useless (my tool: Z3X, Miracle box, MCT Dongle , NCK Dongle, Octopus Suite Unlock, Samkey Unlock Crack)
I try to flash Custom Rom with Odin , Try to Install "Magisk" and "TWRP" by method in many website , it's useless at all
However I think I need to unlock OEM first but I can't because OEM not show in the developer option
I try all the ways to appear the OEM Unlock toggle by a changing date, Flash tar.md5, factory reset in many website it's can't help me
Samsung developer very strong and can't hacking to "OEM Lock : On (L)" on Android Pie 9.0
Click to expand...
Click to collapse
If you have an US variant of the A10, don't expect TWRP to work on your device.
Hey all, hope everyone is having a great day (I'm not),
I own a SM-T510 Samsung Galaxy Tab A 10.1 WiFi.
It all started when I tried to flash Nexus and it worked partially, but I didn't gain access to my internal storage for some reason, so I reverted back to stock rom.
Then for some reason part of the nexus rom was still there, but I was afraid of damaging my device further.
For some reason, netflix wasn't working, so I tried to apply a software update to my device using Smart Switch.
The update didn't work and I was caught in a Nexus bootloop. I entered download mode and I tried flashing twrp using odin. I thought it worked until I realised that it wouldn't get past the teamwin screen.
I re-entered download mode and there it gave me an option to factory reset the device while locking the bootloader. This is where I screwed up as I thought what else could possibly happen to my device?
SO I locked my bootloader and whatever I did I couldn't get out of download mode. AND here I screwed up even more. I tried to flash the stock ROM again using odin as a last resort but it just wouldn't complete after 10 minutes, so I closed Odin and restarted my device and here I am, stuck in a screen that says, "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." Now obviously this wouldn't work because my device isn't even listed there. But to note, my device is recognised by Odin and my PC.
Note: I am an absolute noobie at rooting so be easy on me.
Note 2: adb and fastboot doesn't work for me for some reason, my powershell says, "The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again."
Thank you all for any help. I am at my wit's end.
I have uninstalled with adb the google package manager on my device, now it does not boot up. Does anybody has an idea to bring it back?
P.s: In developer options I have unlocked usb debudding and oem unlock. I can not find the fastboot mode.
Reflash Stock ROM.
FYI:
Fastboot is merely an executable you can operate on device's bootloader once it got unlocked.
I have found this tutorial, is it right? There are also the firmware files I need on this side.
Thank you very much, I have managed it!
I did it with the great lgup utility and the firmware you can get you can find here (for my
LG Q630EAW).
I have a Samsung Galaxy A5 2017 (SM-A520F/a5y17lte/android 8.0.0 oreo) but I cannot install TWRP on it. I tried many methods but its not letting me to do it:
-unlock bootloader /failed
-OEM unlock in dev options /hidden and cannot access/failed
-flash stock rom to unlock OEM /failed
-root phone with adb /no fastboot access /failed
-root phone with Odin /failed
-flashing TWRP with adb /no fastboot access/failed
-flashing twrp with odin /"only official binaries are allowed to be flashed" error message in download mode /failed
-uding heimdall (wtf is this program ive never heard it b4) /failed
Anyone got solution to install TWRP ? So i can flash to android 9 and also root my phone. Thank you if you suggest any solution that actually works.
ItsSuperPlayz said:
I have a Samsung Galaxy A5 2017 (SM-A520F/a5y17lte/android 8.0.0 oreo) but I cannot install TWRP on it. I tried many methods but its not letting me to do it:
-unlock bootloader /failed
-OEM unlock in dev options /hidden and cannot access/failed
-flash stock rom to unlock OEM /failed
-root phone with adb /no fastboot access /failed
-root phone with Odin /failed
-flashing TWRP with adb /no fastboot access/failed
-flashing twrp with odin /"only official binaries are allowed to be flashed" error message in download mode /failed
-uding heimdall (wtf is this program ive never heard it b4) /failed
Anyone got solution to install TWRP ? So i can flash to android 9 and also root my phone. Thank you if you suggest any solution that actually works.
Click to expand...
Click to collapse
Hello and good afternoon, @ItsSuperPlayz
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[ATTN] : Read before posting - Any questions posted here will be MOVED or CLOSED
Please read the below before posting. Any questions not development related will be moved or closed. Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread) Forum Rules Forum Search Google Forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
First you have to access developer mode. You have to tap several times on the build number. (Settings/about the phone) In developer mode you heve to enable oem unlocking and usb debugging. Wait for permission request on the phone for access of your PC when attached to the phone.
Next step is to unlock the bootloader.
After this you will be able to install TWRP, which finally gets you to the point where you can install a new ROM. Just follow step by step:
Install LineageOS on a5y17lte | LineageOS Wiki
wiki.lineageos.org
Of course, instead of Lineage, you can use any suitable ROM
chrysopra said:
First you have to access developer mode. You have to tap several times on the build number. (Settings/about the phone) In developer mode you heve to enable oem unlocking and usb debugging. Wait for permission request on the phone for access of your PC when attached to the phone.
Next step is to unlock the bootloader.
After this you will be able to install TWRP, which finally gets you to the point where you can install a new ROM. Just follow step by step:
Install LineageOS on a5y17lte | LineageOS Wiki
wiki.lineageos.org
Of course, instead of Lineage, you can use any suitable ROM
Click to expand...
Click to collapse
Thank you for replying but as I said above i cannot unlock bootloader in any way i tried. So maybe can u find another solution? (Note: i tried following the link u send me and its not working)
How far did you get? OEM unlocking and usb debugging successful?
When putting your phone in fastboot mode and attaching it to the pc, check with "adb devices", if your phone is properly recognised. Using windows, it´s often the drivers. On my system, I had to manually select the ADB driver, since I got no connection before.
chrysopra said:
How far did you get? OEM unlocking and usb debugging successful?
When putting your phone in fastboot mode and attaching it to the pc, check with "adb devices", if your phone is properly recognised. Using windows, it´s often the drivers. On my system, I had to manually select the ADB driver, since I got no connection before.
Click to expand...
Click to collapse
thanks for replying again
i tried to oem unlocking and usb debugging but unsucessful
furthermore my pc cant even recognise my phone when i turn on usb debugging or change the usb to media transfer protocol (mtp) mode after i flash stock firmware (it worked before i flash the firmware)
how am i gonna install anything if my pc cant even recognise my phone????
(ps: your question "how far did you get" my answer is i cant flash any mods or unlock anything. bootloader locked.)
Can you see the "developer options" in settings/system when scrolling down ? If not, then:
How to access developer options in Android
Step 1: Go to Settings > About Phone.
Step 2: Tap Software Info > Build Number.
Step 3: Tap Build Number seven times. ...
Step 4: Once developer options are activated, you will see a message that reads, You are now a developer.
Within developer options there are options to enable usb debugging and oem unlock. I recently did this on a Galaxy tab and saw..nothing.
First I had to establish a network connection to my wifi base. Weird, but this brought those wanted menu items...
For further connection, check your computer drivers. Both the manufacturers usb drivers and adb driver are necessary. While connected to a PC, check, if you´re on Windows, the device manager, if the proper driver is chosen.
chrysopra said:
Can you see the "developer options" in settings/system when scrolling down ? If not, then:
How to access developer options in Android
Step 1: Go to Settings > About Phone.
Step 2: Tap Software Info > Build Number.
Step 3: Tap Build Number seven times. ...
Step 4: Once developer options are activated, you will see a message that reads, You are now a developer.
Within developer options there are options to enable usb debugging and oem unlock. I recently did this on a Galaxy tab and saw..nothing.
First I had to establish a network connection to my wifi base. Weird, but this brought those wanted menu items...
For further connection, check your computer drivers. Both the manufacturers usb drivers and adb driver are necessary. While connected to a PC, check, if you´re on Windows, the device manager, if the proper driver is chosen.
Click to expand...
Click to collapse
I see the developer options and the usb debugging switch
But there are 2 problems
1. My pc running windows 10 cannot detect my device (like showing it as a disk so i can copy files to )
2. In developer setting there is no OEM unlock option, which is weird. I triee many solutions but cannot get acess to OEM unlock. I even tried to unlock it with ADB ut its useless since my phone cant even access fastboot mode.(download mode is considered to be fastboot but ADB wont recognise my phone)
*why are you putting so much effort replying me*
*also drivers seem to be down*
As for the drivers, you could try:
Samsung Galaxy A5 (2017) USB Driver for Windows (Official Mobile Driver)
Download the official USB Driver for Windows Computer.
gsmusbdriver.com
As for the OEM unlocking, Samsung seems to be tricky:
How to Fix Missing OEM Unlock in Developer Options on Samsung
Are you looking for the OEM Unlock in developer options but couldn't find it? Here's how to fix missing OEM unlock in developer options.
www.ytechb.com
or:
How to fix the missing OEM unlock in developer options on Samsung devices - KrispiTech
There are different methods available to fix the missing OEM unlock in developer options on Samsung devices. By using this option, you will
krispitech.com
ItsSuperPlayz said:
*why are you putting so much effort replying me*
Click to expand...
Click to collapse
Maybe I´m a reincarnation of genghis khan, trying to earn some good karma...
chrysopra said:
As for the drivers, you could try:
Samsung Galaxy A5 (2017) USB Driver for Windows (Official Mobile Driver)
Download the official USB Driver for Windows Computer.
gsmusbdriver.com
As for the OEM unlocking, Samsung seems to be tricky:
How to Fix Missing OEM Unlock in Developer Options on Samsung
Are you looking for the OEM Unlock in developer options but couldn't find it? Here's how to fix missing OEM unlock in developer options.
www.ytechb.com
or:
How to fix the missing OEM unlock in developer options on Samsung devices - KrispiTech
There are different methods available to fix the missing OEM unlock in developer options on Samsung devices. By using this option, you will
krispitech.com
Maybe I´m a reincarnation of genghis khan, trying to earn some good karma...
Click to expand...
Click to collapse
heimdall finally recognise my phone but whenever i try to flash twrp.img it says
"Only official binaries are allowed to be flashed(RECOVERY)" (the phone itself) HELP!!!!
*good karma +1*
On any other device, you would have enjoyed your new TWRP since several days. But Samsung is eager to build as many hurdles as possible, to prevent changing the original software. They invented "KnoxGuard" to "protect" the phone. In your case, it´s aprotection against it´s owner
The error message means, that your phone isn´t successfully unlocked.
Try this:
"FIXED IT!!
The time trick actually worked.
All I had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!"
The following Link may also be of interest:
Prevent Prenormal KG/RMM State on Samsung Galaxy Devices (Guide)
Is the OEM unlock toggle missing on your Samsung Galaxy device? That's probably because your phone has entered Prenormal KG/RMM State. In this guide, we will show you how to prevent Prenormal KG/
www.thecustomdroid.com
chrysopra said:
On any other device, you would have enjoyed your new TWRP since several days. But Samsung is eager to build as many hurdles as possible, to prevent changing the original software. They invented "KnoxGuard" to "protect" the phone. In your case, it´s aprotection against it´s owner
The error message means, that your phone isn´t successfully unlocked.
Try this:
"FIXED IT!!
The time trick actually worked.
All I had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!"
The following Link may also be of interest:
Prevent Prenormal KG/RMM State on Samsung Galaxy Devices (Guide)
Is the OEM unlock toggle missing on your Samsung Galaxy device? That's probably because your phone has entered Prenormal KG/RMM State. In this guide, we will show you how to prevent Prenormal KG/
www.thecustomdroid.com
Click to expand...
Click to collapse
Sorry to say this but the method is useless. Its never gonna work.
Perhaps this (long) Thread may be helpful:
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
the idea is to simply deggogle my a10. i found a few videos on how to do it. however i took the liberty of making a note of the base build number and after searching the internet, i found a firmware farchive that contained several md5 files. i figured i may need this in case anything went wrong.
so i went into settings and developer mode, turned on unlocking oem and usb debugging and attempted to flash the phone by booting into rescue mode (power off phone then power on while holding the volume up button) then selecting boot into bootlader from the menu before using a toll called odin on my pc, which given the threads i've seen on here, most of you are aware odin. i tried to flash the tar file reccomended on the site. odin reported failure. so without rebooting i flashed the firmware that matched my phone my selcting the respective md5 files and telling odin to do it. it reported neither success nor failure but gave a message of something like cs select. i have no idea what that means. however on rebooting the phone it booted fine. no errors or anything, just a completely reset phone. I like to add that this is not may main phone as i am a newbie on this area and wouldn't be so reckless as to experiment on my main phone. hower there is an app on there now called lazade which i beleiv is a shopping app based in the asian continent which isn't where i'm from. i unlocked developer mode once again as it had reset and found that the unlock oem option is missing. is it becasuse of the firmware i burned on it and to i need to reburn another? or is ther another way to get it back?
the baseband version is a105gdxu8cvg2
android 11
one ui 3.1
Your post isn't very clear....have you been able to unlock your bootloader?
The OEM Unlock toggle often disappears if 1) the bootloader is already unlocked, or 2) the system has not yet verified whether OEM unlocking is allowed. This is most likely not a firmware issue.
V0latyle said:
Your post isn't very clear....have you been able to unlock your bootloader?
The OEM Unlock toggle often disappears if 1) the bootloader is already unlocked, or 2) the system has not yet verified whether OEM unlocking is allowed. This is most likely not a firmware issue.
Click to expand...
Click to collapse
it's an old phone. i've had it for a number of years, but i got a new phone recently so i took the oppounity to attempt to degoogle my old one. apparently there's more than one way to do this One is to replace android with other operating system. if youtube is to be beleived. i doubt the phone needs veryfying as it's an old phone although the firmware is fresh. perhaps it is unlocked. in tairness i don't know how to determine that.
fjb59 said:
it's an old phone. i've had it for a number of years, but i got a new phone recently so i took the oppounity to attempt to degoogle my old one. apparently there's more than one way to do this One is to replace android with other operating system. if youtube is to be beleived. i doubt the phone needs veryfying as it's an old phone although the firmware is fresh. perhaps it is unlocked. in tairness i don't know how to determine that.
Click to expand...
Click to collapse
The best I can suggest is to flash a LineageOS GSI without Gapps. There are other custom ROMs available that are sanitized of all Google services.
V0latyle said:
The best I can suggest is to flash a LineageOS GSI without Gapps. There are other custom ROMs available that are sanitized of all Google services.
Click to expand...
Click to collapse
are they available here?
fjb59 said:
are they available here?
Click to expand...
Click to collapse
Just Google LineageOS, they have a website. You should be able to flash a GSI image via TWRP.
V0latyle said:
Just Google LineageOS, they have a website. You should be able to flash a GSI image via TWRP.
Click to expand...
Click to collapse
that's my next goal. i haven't got twirp on there. none of the methods i saw on youtube worked.
fjb59 said:
that's my next goal. i haven't got twirp on there. none of the methods i saw on youtube worked.
Click to expand...
Click to collapse
i found the site for it but the a10 is not listed on thier choice of phones
Assuming your bootloader is already unlocked, here is the TWRP thread for your device., which you probably could have found by searching. Instructions for flashing are in that thread. And here is the LineageOS 19.x GSI thread.
If you haven't unlocked your bootloader yet, that's your first step. Some devices are not bootloader unlockable.
V0latyle said:
Assuming your bootloader is already unlocked, here is the TWRP thread for your device., which you probably could have found by searching. Instructions for flashing are in that thread. And here is the LineageOS 19.x GSI thread.
If you haven't unlocked your bootloader yet, that's your first step. Some devices are not bootloader unlockable.
Click to expand...
Click to collapse
i don't know if i have yet. i went though a process and now the oem unlocking option disappeared ffrom the developer menu. i can boot into the bootload from the rescue menu. I assume that's what you mean.
fjb59 said:
i don't know if i have yet. i went though a process and now the oem unlocking option disappeared ffrom the developer menu. i can boot into the bootload from the rescue menu. I assume that's what you mean.
Click to expand...
Click to collapse
When you're in download mode, you should see OEM LOCK among the text in the upper right of the screen. If this says ON, your bootloader is locked.
V0latyle said:
When you're in download mode, you should see OEM LOCK among the text in the upper right of the screen. If this says ON, your bootloader is locked.
Click to expand...
Click to collapse
oem lock onu1)
looks like it's on. how do i disable it for this phone?
Turn the phone completely off, and leave it off for a few minutes. Then, while holding both Volume buttons together, plug in the USB cable. The device should start in Download mode. Hold Volume + until the bootloader unlock screen appears, then follow the prompt to unlock your bootloader. This will wipe data.
V0latyle said:
Turn the phone completely off, and leave it off for a few minutes. Then, while holding both Volume buttons together, plug in the USB cable. The device should start in Download mode. Hold Volume + until the bootloader unlock screen appears, then follow the prompt to unlock your bootloader. This will wipe data.
Click to expand...
Click to collapse
never shows up. i get to the download screen but pressing the vol up keys doesn't do anything. not even adb can see the device. use debugging is turned on. and usb mode is set to file transfer mode. it weorked finde before i reflashed it. perhaps i need another version of the firmware
development, i noticed the wifi wasn't turned on. i turned it on the went into the development mode. unlock oem was there and ticked
so i did what you said again, this time the option for unlocking oem in download was present. i followed the instructions. it booted and came telling me the oem is unlocked and won't be able to verify the intergrty of the os. now it's doing a reset. i think we got here. what next? you you said twrp?
fjb59 said:
never shows up. i get to the download screen but pressing the vol up keys doesn't do anything. not even adb can see the device. use debugging is turned on. and usb mode is set to file transfer mode. it weorked finde before i reflashed it. perhaps i need another version of the firmware
Click to expand...
Click to collapse
ADB only works in Android or in recovery mode. Samsung devices don't have a fastboot mode.
fjb59 said:
development, i noticed the wifi wasn't turned on. i turned it on the went into the development mode. unlock oem was there and ticked
so i did what you said again, this time the option for unlocking oem in download was present. i followed the instructions. it booted and came telling me the oem is unlocked and won't be able to verify the intergrty of the os. now it's doing a reset. i think we got here. what next? you you said twrp?
Click to expand...
Click to collapse
Yep. Since you don't already have TWRP installed, follow "Method 2" in the thread I linked.
V0latyle said:
ADB only works in Android or in recovery mode. Samsung devices don't have a fastboot mode.
Yep. Since you don't already have TWRP installed, follow "Method 2" in the thread I linked.
Click to expand...
Click to collapse
yep it does. i had a little bit of trouble between installing the first and second file. it kept reporting a corrupt operating system but i noteiced it cycled a reboot wo i held hte power and volume up buttons together when it cycled. this allowed me into rescue mode. from there i was able to power down the phone so i could reboot it back into download mode then upload the rescue file contained in the zip file mentioned. after that it booted ok but keeps claiming that the operating system isn''t offician but then boots into android ok. i expect installing the disable_drm_very app wil fix that. then i can try installign a new os.
but that's for tomorrow
Jjflick said:
I noticed this thread and would like to keep looking
Click to expand...
Click to collapse
i hope it helps you. i've detailed the steps i took as best as i could.