This thread is for whoever wishes to contribute to the development of this particular model, (Galaxy On5), Any and all help is appreciated!
As per request, I unpacked the stock recovery, repacked it, and attempted to flash it through odin. The result was "failed", on the odin side, but the device did not say anything, (This was in download mode).
hydroman202 said:
This thread is for whoever wishes to contribute to the development of this particular model, (Galaxy On5), Any and all help is appreciated!
Click to expand...
Click to collapse
Upload the boot image so I can compile it.
[email protected] said:
Upload the boot image so I can compile it.
Click to expand...
Click to collapse
I would, but all I have is the recovery img. How I got that was from another user who got the firmware. I will ask him to see if he can send me the boot img.
hydroman202 said:
I would, but all I have is the recovery img. How I got that was from another user who got the firmware. I will ask him to see if he can send me the boot img.
Click to expand...
Click to collapse
OK I have not compiled TWRP with a recovery before so just to be safe I use a boot image. I just split it with Mkboot tools and replace the images in the device tree source code made for the T-Mobile/Metro version.
---------- Post added at 05:53 PM ---------- Previous post was at 05:51 PM ----------
hydroman202 said:
As per request, I unpacked the stock recovery, repacked it, and attempted to flash it through odin. The result was "failed", on the odin side, but the device did not say anything, (This was in download mode).
Click to expand...
Click to collapse
The build prop has to match in order for it to work. Upload the boot image and I can work on it.
Deleted
[email protected] said:
https://www.mediafire.com/folder/u6vvauz8i30z0/SM-S550L
Test image. Make sure to backup your recovery before you flash this. Use Odin and in the options tab uncheck auto reboot. Once flash is complete pull out the battery and put it back in. Holding volume up button and the home button and power until you get into recovery. Only people who knows what they are doing so we don't have bricks. I used the device tree source code made for T-Mobile/Metro and used the DT image and kernel from an extracted boot image.
Click to expand...
Click to collapse
It's pointless at the moment even compiling custom recovery for this device as it won't flash.
It seems this device has a locked bootloader.
Well it compiled with no problem with the Metro version all you do is enable development settings and select OEM unlock and USB debugging. I didn't have to use ADB for "fastboot OEM unlock". So I don't know. Thanks for the heads up.
[email protected] said:
Well it compiled with no problem with the Metro version all you do is enable development settings and select OEM unlock and USB debugging. I didn't have to use ADB for "fastboot OEM unlock". So I don't know. Thanks for the heads up.
Click to expand...
Click to collapse
Compiling isn't the issue, it's the fact the image is unsigned. There are no special headers I can see in the stock recovery image, which could cause the issue, so it seems purely down to the bootloader being locked down.
Also regarding OEM unlock and USB debugging.
It isn't and never has been required to enable usb debugging to flash a recovery.
I know this is incorrectly posted all over the Internet, but usb debugging is purely an OS dependent operation and has no use outside of a booted OS.
We are looking at alternative ways, but options are extremely limited.
I took the link down. Thanks.
---------- Post added at 10:35 PM ---------- Previous post was at 10:24 PM ----------
Also check out the boot image. It's identical to the T-Mobile Metro version. Would you be able to test it out?
[email protected] said:
I took the link down. Thanks.
---------- Post added at 10:35 PM ---------- Previous post was at 10:24 PM ----------
Also check out the boot image. It's identical to the T-Mobile Metro version. Would you be able to test it out?
Click to expand...
Click to collapse
I dont own the device I'm just chipping in.
Where did you get the boot image, is it for the S550TL?
ashyx said:
I dont own the device I'm just chipping in.
Where did you get the boot image, is it for the S550TL?
Click to expand...
Click to collapse
Yes it's for the S550L @hydroman202 gave it to me so I split it with Mkboot tools and compiled.
[email protected] said:
Yes it's for the S550L @hydroman202 gave it to me so I split it with Mkboot tools and compiled.
Click to expand...
Click to collapse
That was the recovery image I sent him wasn't it?
It said boot image so I split it and compiled it as on5ltetfntmo
Does anyone know how to perform "oem unlock" without fastboot? Every time I try to access it, it reboots back into the normal os.
hydroman202 said:
Does anyone know how to perform "oem unlock" without fastboot? Every time I try to access it, it reboots back into the normal os.
Click to expand...
Click to collapse
You need to enable it in developer settings.
What was the image you sent to [email protected]?
ashyx said:
You need to enable it in developer settings.
What was the image you sent to [email protected]?
Click to expand...
Click to collapse
The image i sent him was the boot img from my device, which i found somewhere on the internet, (i don't remember where, i had done A LOT of googling), but i was lucky enough to find it. sorry i cant remember the exact site.
hydroman202 said:
The image i sent him was the boot img from my device, which i found somewhere on the internet, (i don't remember where, i had done A LOT of googling), but i was lucky enough to find it. sorry i cant remember the exact site.
Click to expand...
Click to collapse
Just the boot.img you found or the whole firmware?
also, i have been trying to find ways to unlock the bootloader of this device, but all of the methods i have found require root or fastboot. Do you have any ideas on how i might achieve root?
ashyx said:
Just the boot.img you found or the whole firmware?
Click to expand...
Click to collapse
I wish i had the whole firmware, but it was just the boot img. I was pretty sure it was the right one, but i might have been mistaken.
Related
Greets,
I think I may have bricked my Droid Maxx but I'm hoping someone can verify before I deem it a paperweight. I was on SU-2-3.3 and used Sunshine on it to unlock it and then TWRP to root it. After fully booting up the phone and verifying root, I rebooted into TWRP and ran a full back up w md5. After that, I booted up the phone and used supersu survival mode and then took the OTA update. Now the phone boots to fastboot, but says "boot failed" under any of the options. It won't go into recovery nor will it normally boot up. I tried to use RSD to reflash to the latest version but it just said flash failed at the first file and says something about downgraded security, etc. So now, I can get into fastboot mode and the phone connects and is detected but won't let me flash anything... it was unlocked via Sunshine, but I may have borked it up somehow. Thoughts?
Try a more recent firmware but check your recovery
Sent from my D6616 using Tapatalk
I took the OTA... is there something more recent? Also, I've tried to flash other recoveries but I get "boot failed" at the fastboot menu.
ohhhh you must mean try and use a more recent firmware via RSD. I'll give that a shot
Ok i tried a newer firmware via RSD, now the fastboot mode shows "failed to read signatures for partition aboot" RSD fails at flashing partition gpt.bin
Since I seem to have a partition related error, would this LINK help my situation at all?
Does anyone know of a way I can restore or rewrite the partitions via fastboot?
t3knokon said:
Does anyone know of a way I can restore or rewrite the partitions via fastboot?
Click to expand...
Click to collapse
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
t3knokon said:
Since I seem to have a partition related error, would this LINK help my situation at all?
Click to expand...
Click to collapse
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.
BladeRunner said:
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.
Click to expand...
Click to collapse
Ok to clarify, after I unlocked via sunsine on 2-3.3, I rooted and I took the over the air so now I'm on the newer bootloader. Post those events I started to receive "failed to erase partition xxxx" I also just tried reflashing individual images from 4.4.4 su6-7 release and I still receive back "failed to erase... failed to flash... etc." I can get into fastboot mode but it seems crippled somehow.
crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?
t3knokon said:
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?
Click to expand...
Click to collapse
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
BladeRunner said:
well, he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet
....
Click to expand...
Click to collapse
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!
crack.mech said:
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!
Click to expand...
Click to collapse
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?
t3knokon said:
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?
Click to expand...
Click to collapse
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.
BladeRunner said:
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.
Click to expand...
Click to collapse
Thanks for that. I posted there as well... from a software standpoint, I'm curious to know what would be denying access to the partitions...
I messaged jcase and he looked at logs for the sunshine preinstall and they were clean. It's possibly a hardware failure unless someone else with bootloader knowledge, knows how to get around the partition permissions access. thoughts?
I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?
t3knokon said:
I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?
Click to expand...
Click to collapse
the prognosis is not good.
VBlack messaged me about shorting a pin to put the phone in Qualcomm Downloader mode... and then pushing software onto it to at least try to the partitions set up and get the bootloader in a manner which will allow for writing. If that doesn't work, there's nothing else to do. I read up on it extensively, and it's now a last ditch effort. I've never take apart a phone in that manner before, so it'll be a first for me.
Similar boat, here...using a programmer cord, I can flash a ROM onto the Maxx, but it stumble-boots into BP Tools mode after 3 or so failed 0-battery/unlocked bootloader warning screen loops. I can get it into bootloader with program cord, or first thing with factory cord. It won't charge at all, battery is new. Izzit hosed?
Sent from my XT1254 using XDA Free mobile app
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Edit: CHECK THE COMMENTS FOR SOLUTION
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Ok, stop freaking, this is very fixable. Assuming you have the Google version, or the Verizon version unlocked.
Short answer, we are going to get it into fastboot mode and we are going to flash you back to stock and probably save your data.
First, we need to make sure you have the correct version of Fastboot/ADB. It must be from GOOGLE.
https://developer.android.com/studio/releases/platform-tools.html
Unzip that onto a spot on your desktop.
Then go here and download the latest image for the Pixel. I am assuming you are in the US, get 7.1.1 (NOF26V, Feb 2017) for the Pixel.
https://developers.google.com/android/images#sailfish
Unzip that into a the Platform folder you made above with the fastboot tools. When you are all done it should look like the picture below. The highlighted items are the items that came from the Factory Image you extracted in step two. Everything else is from the platform tools.
Now RIGHT click 'flash-all.bat' and edit it. Near the end...look for the -w and take it out and save it. Removing that is what is going to save your data.
Power down your phone, restart it in bootloader mode. Power and Vol Down. Connect it to your computer and then double click 'flash-all.bat'.
That will take you back to stock unlocked and all your data and settings will be there.
Get past that and let us know. Then we will get you properly rooted. Yea, you used the wrong root process.
I love you <3
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
AlexCoetzee said:
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
Click to expand...
Click to collapse
You are most welcome. Do you need help rooting now?
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
No thank you! I figured that out pretty quickly with TWRP and I am happily rooted now Quite a different process after jailbreaking iOS for 8 years. Thanks for your help!
Misterxtc said:
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
Click to expand...
Click to collapse
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Tulsadiver said:
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Click to expand...
Click to collapse
Good to see you here too. It feels great to be free of TouchWiz!!
Misterxtc said:
Good to see you here too. It feels great to be free of TouchWiz!!
Click to expand...
Click to collapse
And how. I'm done with Samsung.
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
stpbby said:
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
Click to expand...
Click to collapse
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Thanks! That worked.
I need help with unlocking bootloader and rooting phone
TonikJDK said:
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Click to expand...
Click to collapse
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If your on Verizon, no, you can't unlock the bootloader
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If it is a Verizon phone, no you can't unlock it. If it is a Google phone to unlock...below is a decent link on how to. Except use the ADB Fastboot tools I link to in the third post of this thread.
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
And be aware, when you unlock it...it will wipe all the data on your phone.
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
moeREM said:
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
Click to expand...
Click to collapse
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
TonikJDK said:
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
Click to expand...
Click to collapse
I think so, but am not 100% sure. Was bought unlocked from a retail shop. (Sorry, am a bit of a newb!)
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
TENN3R said:
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
Click to expand...
Click to collapse
I'm having bootloops at the initial white google logo screen with SR3-SuperSU-v2.79-SR3-20170114223742.zip flash method on 7.1.2-May
Re: https://theunlockr.com/2017/02/01/root-google-pixel-pixel-xl/2/
Hi all
I can't find the recovery and how to root my Sumsung j7 duo sm-j720F with oreo android
Any help plz
And thanx in advance .
No one answer seems like no root and twrp at thise time
Unfortunately the reason you can't find it is the same reason, why nobody can find it: it simply does not exist...
Try Magisk. (I've personally tried and succeeded).
1. Extract "boot.img" from J720F's latest stock firmware and copy it to your sd-card.
2. Install latest Magisk Manager apk.
3. Through Magisk patch the stock "boot.img" in Odin flashable ".img.tar" format.
4. Copy the "patched-boot.img.tar" to your pc and load it in Odin's "AP".
5. Make sure your phone is OEM unlocked.
6. Go to recovery mode and make factory reset/wipe data for best result (I've not tested whether it works without factory reset)
7. Go to download mode (Newer models like J720F doesn't support previous download mode access method by pressing and holding volume down+home+power buttons. New method is pressing and holding "volume down+home" button and attaching the usb cable).
8. Flash the "patched-boot.img.tar"
9. After restart finish additional setups in Magisk app.
10. Enjoy!
mastergg said:
Try Magisk. (I've personally tried and succeeded).
1. Extract "boot.img" from J720F's latest stock firmware and copy it to your sd-card.
2. Install latest Magisk Manager apk.
3. Through Magisk patch the stock "boot.img" in Odin flashable ".img.tar" format.
4. Copy the "patched-boot.img.tar" to your pc and load it in Odin's "AP".
5. Make sure your phone is OEM unlocked.
6. Go to recovery mode and make factory reset/wipe data for best result (I've not tested whether it works without factory reset)
7. Go to download mode (Newer models like J720F doesn't support previous download mode access method by pressing and holding volume down+home+power buttons. New method is pressing and holding "volume down+home" button and attaching the usb cable).
8. Flash the "patched-boot.img.tar"
9. After restart finish additional setups in Magisk app.
10. Enjoy!
Click to expand...
Click to collapse
Thank i ll try
The only thing that i not found is OEM unlocked i have not thise option in my j720f ?
You will find OEM unlock option under "Developer Options" menu. You need to enable the menu first by continuously tapping your "Build Number" for 7 times in a row. Remember that enabling OEM unlock will automatically factory reset your phone. So don't forget to take a backup first.
I suggest you to first install magisk, find the stock boot image and patch it through your phone, then copy it to your pc. Backup everything else you need. Then enable OEM unlock. This way you need to reset your phone only once.
Sir i m try alot to patch boot.img but installing failed error. Can u provide patched boot.img.tar file i really need it
Thank yo
mastergg said:
You will find OEM unlock option under "Developer Options" menu. You need to enable the menu first by continuously tapping your "Build Number" for 7 times in a row. Remember that enabling OEM unlock will automatically factory reset your phone. So don't forget to take a backup first.
I suggest you to first install magisk, find the stock boot image and patch it through your phone, then copy it to your pc. Backup everything else you need. Then enable OEM unlock. This way you need to reset your phone only once.
Click to expand...
Click to collapse
Thank you but i still can't find OEM unlock
In the pict is all what i have in Developer Options option
Samy6699 said:
Thank you but i still can't find OEM unlock
In the pict is all what i have in Developer Options option
Click to expand...
Click to collapse
Strange indeed! You should have the option! In my case it's between "Bluetooth HCI snoop log" and "Running services".
What's your firmware version? Is it the latest one? My build number is "R16NW.J720FDDU3ARI4".
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
prvnktl said:
Sir i m try alot to patch boot.img but installing failed error. Can u provide patched boot.img.tar file i really need it
Thank yo
Click to expand...
Click to collapse
I will try to provide it and will post the link.
But why can't you patch? Is there any problem with Magisk? Or you cannot install the patch through Odin?
mastergg said:
Strange indeed! You should have the option! In my case it's between "Bluetooth HCI snoop log" and "Running services".
What's your firmware version? Is it the latest one? My build number is "R16NW.J720FDDU3ARI4".
Click to expand...
Click to collapse
Yes its the last updat august 1 2018
As the pict show
I do some shearch and many have the same probleme i try to fix it
Samy6699 said:
Yes its the last updat august 1 2018
As the pict show
I do some shearch and many have the same probleme i try to fix it
Click to expand...
Click to collapse
Seems like you have been locked by your bootloader. You can refer to this guide if it helps.
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
mastergg said:
Strange indeed! You should have the option! In my case it's between "Bluetooth HCI snoop log" and "Running services".
What's your firmware version? Is it the latest one? My build number is "R16NW.J720FDDU3ARI4".
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
I will try to provide it and will post the link.
But why can't you patch? Is there any problem with Magisk? Or you cannot install the patch through Odin?
Click to expand...
Click to collapse
Yes problem with Magisk
prvnktl said:
Yes problem with Magisk
Click to expand...
Click to collapse
Install latest Magisk manager.
However for your convenience I am providing the patched boot image.
https://drive.google.com/file/d/1Qx3_wol2dN_RcPXhfvBv7vgVSDnEdi-E/view?usp=sharing
This is extracted from the latest stock firmware having build number J720FDDU3ARI4 so please confirm yourself that you are using the same firmware.
Download and flash it through Odin and let me know about what happens.
mastergg said:
Seems like you have been locked by your bootloader. You can refer to this guide if it helps.
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Click to expand...
Click to collapse
i try it and i try many other tutorial without success
i flash the same firm as you and no way no oem unlock :crying:
i can't get these oem unlock :crying::crying::crying::crying:
Samy6699 said:
i try it and i try many other tutorial without success
i flash the same firm as you and no way no oem unlock :crying:
i can't get these oem unlock :crying::crying::crying::crying:
Click to expand...
Click to collapse
Sorry to hear that. Did you tried a factory reset? And still there is no OEM unlock? If yes then wait till the next firmware release. Or continue searching for any other method. If I come across something then will definitely post here.
mastergg said:
Sorry to hear that. Did you tried a factory reset? And still there is no OEM unlock? If yes then wait till the next firmware release. Or continue searching for any other method. If I come across something then will definitely post here.
Click to expand...
Click to collapse
Yes i did with factory reset and i try flashing some other firmware with all tutorial talking about changing date
Desabling the auto update and many other
I still searching other trick my be ...
Any way thank you for your great help regards:good:
mastergg said:
Strange indeed! You should have the option! In my case it's between "Bluetooth HCI snoop log" and "Running services".
What's your firmware version? Is it the latest one? My build number is "R16NW.J720FDDU3ARI4".
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
I will try to provide it and will post the link.
But why can't you patch? Is there any problem with Magisk? Or you cannot install the patch through Odin?
Click to expand...
Click to collapse
yes problem with magisk hlp me out please
mastergg said:
Sorry to hear that. Did you tried a factory reset? And still there is no OEM unlock? If yes then wait till the next firmware release. Or continue searching for any other method. If I come across something then will definitely post here.
Click to expand...
Click to collapse
I get new updat of the system
How to do now to enable oem plz help
Samy6699 said:
I get new updat of the system
How to do now to enable oem plz help
Click to expand...
Click to collapse
Is the OEM unlock toggle still unavailable? Then wait for 7 days since update and check again.
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
prvnktl said:
yes problem with magisk hlp me out please
Click to expand...
Click to collapse
Flash the patched boot image first
mastergg said:
Is the OEM unlock toggle still unavailable? Then wait for 7 days since update and check again.
Click to expand...
Click to collapse
I don't think the trick of 7 day ll work it was fixed in last updat of august
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
Currently I have all patches after 4.88 base so may to october security patch...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
and Magisk(v17.2) prerooted patched myself here:
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
Mirror: (All Images)
https://mega.nz/#F!QQp1jQQZ!k5ejlU2NJyic0HusCa_IAQ
Nice job, i have been waiting for this for a long time. Thank you so much ??.
Trissi said:
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
Magisk Prepatched Images will be added later...
Click to expand...
Click to collapse
Thanks sir
Greatttttt
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Mo4o293 said:
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Click to expand...
Click to collapse
Thats weird... what model do you have? , I thought they work on all Models...
On my device (TA-1012)[Single sim 128gb/6gb], I have exactly the same patches on a and b and both work like a charm with their specific images... Just redownloaded and tested it again...
To narrow down your problem further:
Did you flash anything else? Is your device booting normally when just rebooting? Root? Twrp?
Mo4o293 said:
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Click to expand...
Click to collapse
If you have another model and some time leftover I would greatly appreciate if you(and everyone else reading this with Another model):
1. could reflash the 4.88 Stock Image
2. Turn off automatic update
3.follow this Upgrade guide over and over again
https://forum.xda-developers.com/no...root-nokia-8-ability-to-t3848390/post77751877
4. Afterwards send me the stock_boot_(randomstuff).gz Magisk generates as Backups in the folder /data or (only viewable with root explorer) AND a screensho of the file creation dates so I know which is which...
I would then upload them and add them to the thread to help others with your model...
No worry's if you don't have time...
Trissi said:
Thats weird... what model do you have? , I thought they work on all Models...
On my device (TA-1012)[Single sim 128gb/6gb], I have exactly the same patches on a and b and both work like a charm with their specific images... Just redownloaded and tested it again...
To narrow down your problem further:
Did you flash anything else? Is your device booting normally when just rebooting? Root? Twrp?
Click to expand...
Click to collapse
Thanks for the replay! My device is TA-1012 [4/64]. I haven't flashed anything. I neither have TWRP or root. When rebooting it is showing the warning that my bootloader is unlocked (offical method). But i noticed something strange. Maybe you will laugh at me :laugh: but the thing is when i boot the phone and the warning pops up it says to press the power button to continue but that doesn't work. I have to wait to boot itself. In the other hand when i boot the stock images you provided the power button works and when i press it, the warning disappears and the android logo pops up. I dont know if this was helpful in some way but i wanted to mention it. Also i will post the backed up img soon that you wanted up there.
Ok so i came up with another idea. I forgot to mention that all these steps i did on Linux so i have Windows also and switched to see if the things are the same. When i enter in cmd, adb recognizes the device without problem. When i write adb reboot bootloader everything is fine. BUT when i write fastboot devices when my phone is in download mode , nothing happens. When i try something like fastboot reboot or fastboot boot xyz.img it says <Waiting for device>. I tried adb and fastboot installer but again nothing. I cannot find nokia drivers, but in OST LA there are 3, i installed them and again nothing. So what should i do?
Edit: It worked when i downloaded new version of adb and fastboot CLI but again - booting the oct img even in Windows cmd makes the phone stuck on android logo
Mo4o293 said:
Thanks for the replay! My device is TA-1012 [4/64]. I haven't flashed anything. I neither have TWRP or root. When rebooting it is showing the warning that my bootloader is unlocked (offical method). But i noticed something strange. Maybe you will laugh at me :laugh: but the thing is when i boot the phone and the warning pops up it says to press the power button to continue but that doesn't work. I have to wait to boot itself. In the other hand when i boot the stock images you provided the power button works and when i press it, the warning disappears and the android logo pops up. I dont know if this was helpful in some way but i wanted to mention it. Also i will post the backed up img soon that you wanted up there.
Click to expand...
Click to collapse
The Power Button stuff is exactly the same for me... Don't think thats the issue...
Really weird, would love to debug further but really have not much other ideas...
Did you try newest fastboot/adb binaries on windows too?
Do you have access to another pc to try it on?
Switched out cables/ports used?
Trissi said:
The Power Button stuff is exactly the same for me... Don't think thats the issue...
Really weird, would love to debug further but really have not much other ideas...
Did you try newest fastboot/adb binaries on windows too?
Do you have access to another pc to try it on?
Switched out cables/ports used?
Click to expand...
Click to collapse
I've switched ports, tried another pc even with different OS (win7). Downloaded the newest adb and fastboot binaries from Android Developers site - nothing. Also i ran a test in fastboot and its says:
bootloader unlocked: true
critical unlocked: false. But i dont think critical is necessary, isnt it?
Mo4o293 said:
I've switched ports, tried another pc even with different OS (win7). Downloaded the newest adb and fastboot binaries from Android Developers site - nothing. Also i ran a test in fastboot and its says:
bootloader unlocked: true
critical unlocked: false. But i dont think critical is necessary, isnt it?
Click to expand...
Click to collapse
If critical was never unlocked it can't have been modified(I think)
Really outta ideas here sorry mate...
Have you tryed booting the prerooted imgs?
Trissi said:
If critical was never unlocked it can't have been modified(I think)
Really outta ideas here sorry mate...
Have you tryed booting the prerooted imgs?
Click to expand...
Click to collapse
Yep the same thing
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
I think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
I have similar issues. I have ta-1012 4/64. When it was of september patch, no september image worked (modified or not), it stucks at "android powered" logo. This is the volatile booting which is performed by "fastboot boot" command.
I use a linux desktop. I tried the latest fastboot executable which came with android-studio and also the one on archlinux android-tools package. (they are a bit different) Results are same.
Now it has october patch. No success with october boot images, too
---------- Post added at 21:59 ---------- Previous post was at 21:53 ----------
Mo4o293 said:
Yep the same thing
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
I think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
Click to expand...
Click to collapse
I think you should wait for TWRP.
Dr. Slump said:
I have similar issues. I have ta-1012 4/64. When it was of september patch, no september image worked (modified or not), it stucks at "android powered" logo. This is the volatile booting which is performed by "fastboot boot" command.
I use a linux desktop. I tried the latest fastboot executable which came with android-studio and also the one on archlinux android-tools package. (they are a bit different) Results are same.
Now it has october patch. No success with october boot images, too
---------- Post added at 21:59 ---------- Previous post was at 21:53 ----------
I think you should wait for TWRP.
Click to expand...
Click to collapse
Yep. We are the black sheeps. Anyway i will definitely wait for TWRP because the other things are risky and thats my daily driver. BTW Im on Manjaro which is based on Arch.
Mo4o293 said:
think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
.
Click to expand...
Click to collapse
If you do happen to do that please remember this if you have Time....
If you have another model and some time leftover I would greatly appreciate if you(and everyone else reading this with Another model):
1. could reflash the 4.88 Stock Image
2. Turn off automatic update
3.follow this Upgrade guide over and over again
https://forum.xda-developers.com/no...root-nokia-8-ability-to-t3848390/post77751877
4. Afterwards send me the stock_boot_(randomstuff).gz Magisk generates as Backups in the folder /data or (only viewable with root explorer) AND a screensho of the file creation dates so I know which is which...
Click to expand...
Click to collapse
Trissi said:
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
Currently I have all patches after 4.88 base so may to october security patch...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
and Magisk(v17.2) prerooted patched myself here:
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
Click to expand...
Click to collapse
You can download it on GoogleDrive? links do not open
Anatoly64RUS said:
You can download it on GoogleDrive? links do not open
Click to expand...
Click to collapse
Problem seems on your side
Anatoly64RUS said:
You can download it on GoogleDrive? links do not open
Click to expand...
Click to collapse
Works fine for me too...
I have A pretty restrictive https configuration on that server...
Do you use A massively outdated browser? If Not it should work...
Trissi said:
Works fine for me too...
I have A pretty restrictive https configuration on that server...
Do you use A massively outdated browser? If Not it should work...
Click to expand...
Click to collapse
Browsers are all updated, I'm just from Russia, so a big request to anyone is easy, upload to google drive
*****I am not responsible for anything you do to your device. Do this at own risk***** If all goes bad just flash Factory firmware with PIT file.
Credit goes to those who built twrp.img and the vbmeta image for the A30/A70. I am no dev, I read somewhere about the crossflash to DS firmware but cannot find it any more.
This is for people who understand Odin and have some experience flashing firmware.
Maybe someone will make noob friendly instructions, please feel free.
I currently have an a205u with an unlocked bootloader root and twrp.
1. Using Patched odin crossflash to DS firmware. OEM toggle-download mode-unlock bootloader.
2. You are now able to flash back to the W/U firmware keeping an unlocked Bootloader even though you will not see an oem toggle in developer options
3. Patch boot with magisk 8.02 compress it to tar file along with A30 vbmeta.
***** Important***** make sure to use 7zZ for all steps, and rename boot from magisk_patched_image to boot.img or you will receive errors.
( I may have used a70 vbmeta as I was trying various ideas someone will have to try this and let us know) It will hang at samsung logo for a while on first boot.
4. Then flash A30 TWRP using flashify. Probably works with odin too. Boot to recovery- Perform format data, reboot recovery, flash dmverity+magisk. May be able to get it to work in less steps that's just what I did to make it work.
Link containing vbmeta , magisk patched boot Patched odin . Bootloader 4
First time flashing I got a pass in Odin and fail on phone Flash the second time everything was good
https://drive.google.com/file/d/1F_Bjv8YzPqJLk4YqbXLjYamlPgIZ3nGN/view?usp=drivesdk
Drop that DS firmware.
Johnmoerike said:
*****I am not responsible for anything you do to your device. Do this at own risk***** If all goes bad just flash Factory firmware with PIT file.
Credit goes to those who built twrp.img and the vbmeta image for the A30/A70. I am no dev, I read somewhere about the crossflash to DS firmware but cannot find it any more.
This is for people who understand Odin and have some experience flashing firmware.
Maybe someone will make noob friendly instructions, please feel free.
I currently have an a205u with an unlocked bootloader root and twrp.
1. Using Patched odin crossflash to DS firmware. OEM toggle-download mode-unlock bootloader.
2. You are now able to flash back to the W/U firmware keeping an unlocked Bootloader even though you will not see an oem toggle in developer options
3. Patch boot with magisk 8.02 compress it to tar file along with A30 vbmeta.
***** Important***** make sure to use 7zZ for all steps, and rename boot from magisk_patched_image to boot.img or you will receive errors.
( I may have used a70 vbmeta as I was trying various ideas someone will have to try this and let us know) It will hang at samsung logo for a while on first boot.
4. Then flash A30 TWRP using flashify. Probably works with odin too. Boot to recovery- Perform format data, reboot recovery, flash dmverity+magisk. May be able to get it to work in less steps that's just what I did to make it work.
Click to expand...
Click to collapse
You have the only A205U in existence that is rooted.
Congratulations
Could you please change the title to A205U so others can find it
https://linksharing.samsungcloud.com/jQ6RcTYUMPxR
ninjasinabag said:
Drop that DS firmware.
Click to expand...
Click to collapse
I do not have the DS firmware, I did the unlock months ago then proceeded to break my phone screen. I just replaced it and came to xda to find custom roms. Thought this method would have been old news. Try flashing F firmware as they are identical processors. LINK TO PROOF ABOVE
physwizz said:
You have the only A205U in existence that is rooted.
Congratulations
Could you please change the title to A205U so others can find it
Click to expand...
Click to collapse
So you know what he means by ds firmware?
ninjasinabag said:
So you know what he means by ds firmware?
Click to expand...
Click to collapse
No.
I will try yo find out
DS could mean Dual Sim in firmware , Like mine is and SM-A205F/DS.
It is dual sim. @physwizz @ninjasinabag
physwizz said:
No.
I will try yo find out
Click to expand...
Click to collapse
So far it seems DS refers to the singapore version of a couple Samsung phones.
The a205FN would be the closest version in that regard and it's got a recent version of Android.
I'll give it a flash and see.
---------- Post added at 01:55 AM ---------- Previous post was at 01:42 AM ----------
KineSight said:
DS could mean Dual Sim in firmware , Like mine is and SM-A205F/DS.
It is dual sim. @physwizz @ninjasinabag
Click to expand...
Click to collapse
That's exactly what it means and I love you for pointing this out.
The singapore firmware on the F is universally unlocked.
ninjasinabag said:
So far it seems DS refers to the singapore version of a couple Samsung phones.
The a205FN would be the closest version in that regard and it's got a recent version of Android.
I'll give it a flash and see.
---------- Post added at 01:55 AM ---------- Previous post was at 01:42 AM ----------
That's exactly what it means and I love you for pointing this out.
The singapore firmware on the F is universally unlocked.
Click to expand...
Click to collapse
Awesome, glad I could be of help. @ninjasinabag
ninjasinabag said:
So far it seems DS refers to the singapore version of a couple Samsung phones.
The a205FN would be the closest version in that regard and it's got a recent version of Android.
I'll give it a flash and see.
---------- Post added at 01:55 AM ---------- Previous post was at 01:42 AM ----------
That's exactly what it means and I love you for pointing this out.
The singapore firmware on the F is universally unlocked.
Click to expand...
Click to collapse
So you're going to do it?
physwizz said:
So you're going to do it?
Click to expand...
Click to collapse
Yeah, I've downloaded a couple of firmwares with unlocked bootloaders. Gonna try out a couple and see if they stick.
Hit a few errors tonight trying out different versions of odin, so I'll try more tomorrow/today
ninjasinabag said:
Yeah, I've downloaded a couple of firmwares with unlocked bootloaders. Gonna try out a couple and see if they stick.
Hit a few errors tonight trying out different versions of odin, so I'll try more tomorrow/today
Click to expand...
Click to collapse
Good Luck
Re:
Omg I've been waiting almost 2 years for this metropcs a205U to be rooted can you please PM me if mine can be rooted and sent me the Odin and combination firmware so I can root mine to PLEASE bro this phone is complete ass with so many Samsung restrictions please let this be real!!
your instructions are completely vauge with no links and no clarification between which vbmeta to flash and your picture shows your on A205W VLU 4BTE3 which is a Canada variant of the phone..gah this is just too complicated for me can someone please reiterate with a proper guide to root a205U (metropcs)
Johnmoerike said:
https://linksharing.samsungcloud.com/jQ6RcTYUMPxR
I do not have the DS firmware, I did the unlock months ago then proceeded to break my phone screen. I just replaced it and came to xda to find custom roms. Thought this method would have been old news. Try flashing F firmware as they are identical processors. LINK TO PROOF ABOVE
Click to expand...
Click to collapse
Can you please post odin, vbmeta, patched boot.img ?
physwizz said:
Can you please post odin, vbmeta, patched boot.img ?
Click to expand...
Click to collapse
Its added to the first post, sorry I would wasn't able to be more clear. I unlocked the bootloader couple months ago, not realizing that I was the only one to have done so. If I can be of any more help let me know
Johnmoerike said:
Its added to the first post, sorry I would wasn't able to be more clear. I unlocked the bootloader couple months ago, not realizing that I was the only one to have done so. If I can be of any more help let me know
Click to expand...
Click to collapse
Thanks.
There are a lot of people who are waiting to root their a205U.
---------- Post added at 11:39 PM ---------- Previous post was at 11:21 PM ----------
ninjasinabag said:
Yeah, I've downloaded a couple of firmwares with unlocked bootloaders. Gonna try out a couple and see if they stick.
Hit a few errors tonight trying out different versions of odin, so I'll try more tomorrow/today
Click to expand...
Click to collapse
Tar and odin in post 1
The firmware I downloaded was a205fn. That's the answer let me know how it goes
Johnmoerike said:
The firmware I downloaded was a205fn. That's the answer let me know how it goes
Click to expand...
Click to collapse
Thanks
physwizz said:
Thanks
Click to expand...
Click to collapse
Any progress in the a205u root?