Develop Bugs

[R&D][DUMP] Official AT&T ROM JDQ39.I337UCUAMDB

Hello Guys,
Thanks to the djrbliss and the root http://cleanimport.xda/index.php?threads/2252248/ , I dumped the system files from the AT&T version and am uploading the original files so that someone can make a Pre-Rooted , Custom Rom , Recovery , etc . Let me know if the dump is full and enough or if i need to do something more.
Kernel_ramdisk_unpacked (boot -> /dev/block/mmcblk0p20) : http://www.sendspace.com/file/o0iklo
Stock_Recovery (recovery -> /dev/block/mmcblk0p21 ) : http://www.sendspace.com/file/pgwjed
Hidden.img (hidden -> /dev/block/mmcblk0p27 ) : http://www.sendspace.com/file/reg61v
System partition backup : Attached is the torrent, tried uploading the system image file to a file hosting site but couldn't, hence the torrent.
The factoryfs is 2.7GB , and will upload it soon.
[size=+3]Warning:
Please[size=+5] do not DIRECTLY flash these files[/size] , as they haven't been tested and may not be fully operational.
At this point, since there are no custom recoveries or stock images available, it may not be possible to repair your device should you accidentally break it. Please be aware of this before performing any modifications to your phone.
[/size]
Thanks

THANKS!
Working on recovery now...

zedomax said:
THANKS!
Working on recovery now...
Click to expand...
Click to collapse
When our devices are locked - does rooting them essentially unlock them? or is there some other step that is required? Same question for flashing a custom recovery - how or does - this effect the locked booterloader thing -
I tried doing a GOOGlE search to see if I could figure it ouit on my own and wasnt quite sure so - I thought I would ask - at the risk of looking like a dummy
thoughts?

mocsab said:
When our devices are locked - does rooting them essentially unlock them? or is there some other step that is required? Same question for flashing a custom recovery - how or does - this effect the locked booterloader thing -
I tried doing a GOOGlE search to see if I could figure it ouit on my own and wasnt quite sure so - I thought I would ask - at the risk of looking like a dummy
thoughts?
Click to expand...
Click to collapse
yes it does...but if you install a custom ROM then it will have all the customizations which make the phone run faster and better than stock and other stuff which we cannot have with a stock rom.
custom recovery adds a step of protection by which you can install/backup roms and other stuff. and you can only install a custom recovery and rom if you have an unlocked bootloader.

How will you override the bootloader lock ?

lowspeed said:
How will you override the bootloader lock ?
Click to expand...
Click to collapse
Am not sure that's why i posted them here

lowspeed said:
How will you override the bootloader lock ?
Click to expand...
Click to collapse
Exactly why I am stumped atm, there's write protection on bootloader, I wonder if AT&T is the only S4 with this??? Can anyone confirm who has another S4 like i9505?

if the root method works, then you should be able to flash the recovery and custom kernel as long as the bootloader does not do signature checks (which some people have claimed to be true, will see). You will not be able to use ODIN,
but shouldn't matter.
Did it the "root" work for anyone else? I remember the kernel config allow full permissive root access, so we should be golden..

mohan_kr said:
if the root method works, then you should be able to flash the recovery and custom kernel as long as the bootloader does not do signature checks (which some people have claimed to be true, will see). You will not be able to use ODIN,
but shouldn't matter.
Did it the "root" work for anyone else? I remember the kernel config allow full permissive root access, so we should be golden..
Click to expand...
Click to collapse
Yes , the root worked for everyone who tried. From browsing the thread , i seen that it worked for AT&T and SPRINT SG4's so someone should be able to make a custom kernel soon enough

Dare{D}evil said:
Yes , the root worked for everyone who tried. From browsing the thread , i seen that it worked for AT&T and SPRINT SG4's so someone should be able to make a custom kernel soon enough
Click to expand...
Click to collapse
cool..will pick up the device then..time to make some kernel and ROM..hopefully the source should be out soon..sammy is pretty good about that..

Dare{D}evil said:
yes it does...but if you install a custom ROM then it will have all the customizations which make the phone run faster and better than stock and other stuff which we cannot have with a stock rom.
custom recovery adds a step of protection by which you can install/backup roms and other stuff. and you can only install a custom recovery and rom if you have an unlocked bootloader.
Click to expand...
Click to collapse
THanks - I apprecaite the info

2.7GB...damn gurl dat bloat

Just another reminder to those still newly getting their S4's, remember the bootloader IS STILL LOCKED and your are pretty much stuck if anything happens to your phone while Rooted :/
Best bet just wait for the bootloader unlock, if you can't wait then I guess it sucks to be you XD
I don't even think it's gonna take long for the bootloader to get unlocked and I'm also willing to bet that someone from Samsung will probably end up releasing something helpful.

Dare{D}evil said:
Hello Guys,
Thanks to the djrbliss and the root http://cleanimport.xda/index.php?threads/2252248/ , I dumped the system files from the AT&T version and am uploading the original files so that someone can make a Pre-Rooted , Custom Rom , Recovery , etc . Let me know if the dump is full and enough or if i need to do something more.
Kernel_ramdisk_unpacked (boot -> /dev/block/mmcblk0p20) : http://www.sendspace.com/file/o0iklo
Stock_Recovery (recovery -> /dev/block/mmcblk0p21 ) : http://www.sendspace.com/file/pgwjed
Hidden.img (hidden -> /dev/block/mmcblk0p27 ) : http://www.sendspace.com/file/reg61v
The factoryfs is 2.7GB , and will upload it soon.
Warning:
Please do not DIRECTLY flash these files , as they haven't been tested and may not be fully operational.
At this point, since there are no custom recoveries or stock images available, it may not be possible to repair your device should you accidentally break it. Please be aware of this before performing any modifications to your phone.
Thanks
Click to expand...
Click to collapse
do you happen to have a backup that can be flashed as an update or zip file mine wont boot tried to install google wallet like some others on here and didnt work

will this work in odin?

animeware said:
will this work in odin?
Click to expand...
Click to collapse
No
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Rooting this device was such a breeze! And being able to do it the day after it arrived in the mail was just awesome. Thanks for the dump. I have been freezing the bloatware with Titanium Backup, didn't want to begin stripping things until a recovery was available and I could do a backup of the stock rom. I was surprised to see that I could also freeze most of the bloat through the built in Application Manager (selecting an app then tapping Disable) even before I rooted the phone.

ericos123 said:
do you happen to have a backup that can be flashed as an update or zip file mine wont boot tried to install google wallet like some others on here and didnt work
Click to expand...
Click to collapse
sorry nope not until we have a workable recovery..

Dare{D}evil said:
sorry nope not until we have a workable recovery..
Click to expand...
Click to collapse
thanks, any idea how long this stuff generally takes?

ericos123 said:
thanks, any idea how long this stuff generally takes?
Click to expand...
Click to collapse
first the dev's need to find and unlock the bootloader, we cannot say how much long that will take because it depends on the dev's and the device, i can say about 20 days to a month and after which the recovery can be done, which will be soon if we get the bootloader unlocked , then the custom roms will come out...

[HOW TO] Rooting Flashing Custom Recovery & Kernal

Hello Mates!
Since there is hardly any detailed guide as to how to Root, Flashing custom kernel & Recovery I decided to make a detailed guide that might help you.
Disclaimer:
Following this will void your warranty
This method will trip Knox and Samsung pay may not work (Until some Dev might come up with better method)
The steps mentioned here are was tested but in case if it didn't work I or the developers take no responsibility so use it on your own risk
Click to expand...
Click to collapse
Prerequisites
Odin v3.10.7
USB Drivers
Phil Recovery & Arter97 Kernal or TWRP Recovery
Super SU
Supported Devices:
g920fi
g920skl
g920tw8
g925fi
g925skl
g925tw8
g928fci (You can flash this on Indian firmware as well)
g928skl
g928tw8
So let's start
Backup your device before following this guide
First download and install the USB driver from the above link
Download Odin and unpack to a folder
Download Phil Recovery from Arter97 Kernel thread (recommended)
Download Arter97 Kernel & SuperSU and copy them to your device
Enable Developers option in your phone
Go to Settings -> Above device ->Software Info and tap on Build number 10 times to enable Developers Mode
Then Go to Settings & Developers option and Make sure "USB Debugging" is enabled & "OEM Unlock" is enabled
Flashing Recovery:
Now let's reboot the device into Download Mode
Power off the device.
Press Volume Down + Home + Power button at the same time and hold them.
Now open Odin and connect your device to your PC (Sometimes it might take some time for the Odin to detect the device)
Once Odin detects your device choose AP button and select the recovery file you downloaded (File name with extension .tar.md5)
Now go to the options tab and make sure everything else is unchecked expect F. Reset Time
Now click on Start to Flash the custom recovery
Once it's completed your see "PASS" in a green box on top left corner of Odin
Congratulations! You have successfully flashed your Custom Recovery
Flashing Kernel & Rooting
Now let's reboot the device in Recovery mode
Holding Power +Volume Up+ Home key for a couple of seconds.
Once you are in Recovery it's recommend to take a backup
Now Flash the Kernel (It will remove Knox)
Once you Flashed the Kernel, Flash SuperSU
Congratulations! You have successfully rooted your device.
You are facing any issues? Please post your question so I or one of our community members will help you out.
Update:
For Android Marshmallow you could use Chainfire's CF Root. For SM-G928C visit https://autoroot.chainfire.eu/ or download it from here
Also you could check Dr. Ketan's Root and Deep sleep fix guide: here
Update 27th March 2016:
Seems like the some of the root methods out there is hit and miss like CF Auto Root etc. But seems like lot of people reported rooting with SkyHigh Kernel seems to working.
SkyHigh Kernel

@ShyamSasi
That's brilliant...it will help a lot of people out and stop a lot of silly questions lol. Now only for some Roms or deodexed stock lol for xposed.
Sent from my SM-G928F using Tapatalk

nice write up. you might want to note that after the recovery is flashed. do not reboot the device system. i did it twice on accident and both times, because after the flash, it stays in download mode. the system re-installed the stock recovery. so what i did was hold: vol down, home and power to reboot back into download mode then from there i hit vol up to cancel. then as soon as the phone is about to reboot, i did the: vol up + home + power button combo to boot into the new recovery. *my phone didn't let me boot into recovery from download mode.

tatoo069sv said:
@ShyamSasi
That's brilliant...it will help a lot of people out and stop a lot of silly questions lol. Now only for some Roms or deodexed stock lol for xposed.
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
Thank you
swift2fly said:
nice write up. you might want to note that after the recovery is flashed. do not reboot the device system. i did it twice on accident and both times, because after the flash, it stays in download mode. the system re-installed the stock recovery. so what i did was hold: vol down, home and power to reboot back into download mode then from there i hit vol up to cancel. then as soon as the phone is about to reboot, i did the: vol up + home + power button combo to boot into the new recovery. *my phone didn't let me boot into recovery from download mode.
Click to expand...
Click to collapse
Yes I understand. That's why I asked you uncheck everything from Odin i.e. Auto reboot option. Thanks for the tip. I'm sure this will help out.

i have this model they are not root yet ??
Edge+ Model SM-G928G

Does it work with the Canadian g928w8. Thanks much.

ShyamSasi said:
Thank you
Yes I understand. That's why I asked you uncheck everything from Odin i.e. Auto reboot option. Thanks for the tip. I'm sure this will help out.
Click to expand...
Click to collapse
i had Auto Reboot un-checked. so after the flash it just stays on download mode. therefore i did the steps that i had previously mentioned.

x.Orville.x said:
i have this model they are not root yet ??
Edge+ Model SM-G928G
Click to expand...
Click to collapse
I have G928G model and I used g928fci to root.
flutos said:
Does it work with the Canadian g928w8. Thanks much.
Click to expand...
Click to collapse
I'm not sure mate, seems like it's not listed. Browse around the kernel thread to see if anyone has reported flashing a compatible kernel.
swift2fly said:
i had Auto Reboot un-checked. so after the flash it just stays on download mode. therefore i did the steps that i had previously mentioned.
Click to expand...
Click to collapse
Ah alright. Thanks for sharing it.

Is SM-928F supported?

ShyamSasi said:
I have G928G model and I used g928fci to root.
(...)
Ah alright. Thanks for sharing it.
Click to expand...
Click to collapse
Same here. G928G model (Brazil, not India, different basebands), seems to work perfectly with F, C and I version.

sergio.custodio said:
Same here. G928G model (Brazil, not India, different basebands), seems to work perfectly with F, C and I versions.
Click to expand...
Click to collapse
Thanks!

Is possible used The same method to root s6 edge+ that s6 edge normal?

guta12 said:
Is possible used The same method to root s6 edge+ that s6 edge normal?
Click to expand...
Click to collapse
I don't believe so. So far the research I did S6 Edge could use a app to root but that doesn't support Android 5.1.1 version. Until they support 5.1.1 we have to use this method.

guta12 said:
Is possible used The same method to root s6 edge+ that s6 edge normal?
Click to expand...
Click to collapse
i can confirm that the steps are the same for the s6 edge, the kernel and required files are different. Just search and you will find it. I know this because i previously had the s6 edge (international) on 5.1.1

So this question sounds kinda dumb for me...
With this method I can root my SM-G928F right?
Does it wipe my phone?
Sorry for those questions but it's my first Samsung Phone.
-Lychee

xLychee said:
So this question sounds kinda dumb for me...
With this method I can root my SM-G928F right?
Does it wipe my phone?
Sorry for those questions but it's my first Samsung Phone.
-Lychee
Click to expand...
Click to collapse
Yes! It will root G928F.
No, it will not wipe the phone.

Thank you very much, then I will proceed and enjoy my adblocker again.
Another quite dumb question: Is F928fci the right kernel version / recovery for my device?
-Lychee
EDIT: Yes it is, reading helps alot.

is there anything for the mac?

JazzyStahh said:
is there anything for the mac?
Click to expand...
Click to collapse
There is Odin version ported for MAC http://forum.xda-developers.com/showthread.php?t=2598203 but I am not sure if it's compatible with Edge+

ShyamSasi said:
I have G928G model and I used g928fci to root.
I'm not sure mate, seems like it's not listed. Browse around the kernel thread to see if anyone has reported flashing a compatible kernel.
Ah alright. Thanks for sharing it.
Click to expand...
Click to collapse
Wherw i can find it i can see it
Sent from my SM-G928G using Tapatalk

Help needed ! stuck in Bootloop

Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.

porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me

Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .

I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153

mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .

mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !

porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?

flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.

porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.

flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !

porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks

flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.

porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !

porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does

flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you

Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well

[ROOT] SM-J730G/GM/F Galaxy J7 Pro

Below you will find my procedure to root the SM-J730G/GM Galaxy J7 Pro - Exynos 7870
(may also work for J730F, see post #3)
This procedure has been tested on J730GMDXU1AQF8 firmware. It may work for future releases or it may not.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the files below:
sm-j730gm_SR3-SuperSU-v2.79-SR3_root_boot_32
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to RECOVERY mode then select FACTORY RESET. THIS WILL WIPE YOUR DEVICE AND YOU WILL LOSE ALL DATA. (This procedure is required to remove encryption or your device won't boot)
◘ 4. From RECOVERY, IMMEDIATELY Boot your device to DOWNLOAD mode then connect your USB cable. (DO NOT LET YOUR DEVICE REBOOT NORMALLY OR YOUR DEVICE WILL RE-ENCRYPT)
◘ 5. Run ODIN and place the sm-j730gm_SR3-SuperSU-v2.79-SR3_root_boot_32.tar file as is in the AP slot. Don't change any options and hit START.
◘ 6. Wait for the device to flash and reboot.
◘ 7. Install the SuperSU apk from Play store and you should be rooted.
◘ 8. Have fun!
Credits: Me, @Chainfire(for supersu), @mottx(for testing)
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU

Great work Thanks hit.
Sir, flashing zips thru Flashfire? I Hope TWRP will be released soooon.

works for 730F
Hi ashyx, thanks you! I can confirm that this method is working for the J7 730F/DS model whith Version J730FXXU1AQF4.

Does anyone know why the bloatware can not uninstall on Android 7 Nougat? I have rooted my J730G and use Link2SD app to uninstall the default apps, but the apps can not remove. I can use link2sd app on Android 6 Marshmallow to remove default app.

I use System App Remover from Playstore.

ilsor76 said:
I use System App Remover from Playstore.
Click to expand...
Click to collapse
I have used the apps and others apps but It failed, It looks like storage protection.
Update:
I could removed the apps using ES File Explorer by activated Root Exlorer -> Mount R/W

Great buddy

Is this boot image built from kernel source ? Whats the difference in 64 bit and 32 bit version u gave at oves thread? Pls explain as it will help me for future development
Sent from my SM-J730GM using Tapatalk

Berong said:
Great work Thanks hit.
Sir, flashing zips thru Flashfire? I Hope TWRP will be released soooon.
Click to expand...
Click to collapse
TWRP already available here:
https://forum.xda-developers.com/galaxy-j7-2017/how-to/guide-j7-pro-2017-t3647101/post73181512

v00d007 said:
TWRP already available here:
https://forum.xda-developers.com/galaxy-j7-2017/how-to/guide-j7-pro-2017-t3647101/post73181512
Click to expand...
Click to collapse
I think its only for GM variants...

Berong said:
I think its only for GM variants...
Click to expand...
Click to collapse
Yes, you are right. It does not work for SM-J730F and SM-J730G (tested). Stuck on samsung logo.

redymedan said:
Yes, you are right. It does not work for SM-J730F and SM-J730G (tested). Stuck on samsung logo.
Click to expand...
Click to collapse
After installing it reset phone

So it does work for G?

Berong said:
So it does work for G?
Click to expand...
Click to collapse
according to @redymedan yes.

ashyx said:
according to @redymedan yes.
Click to expand...
Click to collapse
I mean, will the TWRP work for G/DS?
I'm sorry for messing the thread...
I know the modified boot.img will work for G/DS.
But Oves said flashing TWRP and wipe data will make it work ( Correct me if I'm wrong)
Sent from my LG-H502 using XDA-Developers Legacy app

Berong said:
I mean, will the TWRP work for G/DS?
I'm sorry for messing the thread...
I know the modified boot.img will work for G/DS.
But Oves said flashing TWRP and wipe data will make it work ( Correct me if I'm wrong)
Click to expand...
Click to collapse
As long as the variants don't differ in CPU/SoC (Qualcomm/Exynos), with Samsung it never was a big deal to use twrp from a "brother" model. Always make a backup first before flashing critical system parts and keep the original odin flash file in handy.

Thanks. Now I know sir.

File not found
ashyx said:
◘ 1. Download the files below:
sm-j730gm_SR3-SuperSU-v2.79-SR3_root_boot_32
Click to expand...
Click to collapse
Hi. I read through this new thread, and the original thread by Oves (India) who was working on the root for the J730G/DS as well. @ashyx love the work, thank you very much. But when I click on the 32 bit root file on androidfilehost.com it gives me a 404 error, file not found.
I think the link is either broke, or the file has been removed. If people are reading the old thread, they may eventually make there way here to find the updated file.
Can you please repost the link for the proper file? Thanks again for all your hard work!

superkid333 said:
Hi. I read through this new thread, and the original thread by Oves (India) who was working on the root for the J730G/DS as well. @ashyx love the work, thank you very much. But when I click on the 32 bit root file on androidfilehost.com it gives me a 404 error, file not found.
I think the link is either broke, or the file has been removed. If people are reading the old thread, they may eventually make there way here to find the updated file.
Can you please repost the link for the proper file? Thanks again for all your hard work!
Click to expand...
Click to collapse
It hasn't been removed it's still working just checked.
Maybe try a different browser or disable any ad blockers.

That is strange, I still can't get it to work via Chrome or Firefox. I just tried it now on my mobile, same thing.
This is the link from the browser:
https://www.androidfilehost.com/?fid=673368273298979779"
Well, no worries, I'm sure somehow I will figure it out. I'm using the link on the first page of this thread for the 32 bit file.

Root w/ Magisk: almost successful. Any Help?

[EDIT] Root successful!!!! thanks to @ammarwajihi for the hint!
Hi,
I have recently bought this phone and I need root to restore my Titanium Backup .
I am following https://topjohnwu.github.io/Magisk/install.html @ "Samsung (System-as-root)" section.
I successfully unlocked bootloader and done the first part of instructions: I created magisk_patched.tar and flashed it.
Unfortunately I always get a bootloop and never reach the Samsung logo, except made for two times when it booted correctly but Magisk was not recognized as installed.
I tried:
-Patching AP file both retaining and not retaining encryption
-Flashing it with all other files and HOME_CSC or CSC
-Skipping and not skipping step 9 Full data wipe ) and this lead me to the two successful bootups.
-pressing recovery combination (volup + power), only before the system-non-official warning, and also a small period after to boot into magisk
But still no boot with Magisk and subsequent boots after one success lead to bootloop again. (without reaching samsung logo).
Anyone does have advice? ideas?
We can make this work!! :good:

Hey,
Try the file provided in this group - https://t.me/joinchat/FrDuSBgUxDGSZ1vVmej7fw
I haven't tried it but many others have rooted it. You can even ask their if you face any problem. The developer helps a lot.

ammarwajihi said:
Hey,
Try the file provided in this group - https://t.me/joinchat/FrDuSBgUxDGSZ1vVmej7fw
I haven't tried it but many others have rooted it. You can even ask their if you face any problem. The developer helps a lot.
Click to expand...
Click to collapse
HI! Thanks a lot!
The method works!!!
I just rooted my S10 Lite!

loripino13 said:
HI! Thanks a lot!
The method works!!!
I just rooted my S10 Lite!
Click to expand...
Click to collapse
Yes, saw your message in the group. You're welcome

ammarwajihi said:
Yes, saw your message in the group. You're welcome
Click to expand...
Click to collapse
Hi, can we have a tutorial step by step with the nessesary file?Thanks,

sosimple said:
Hi, can we have a tutorial step by step with the nessesary file?Thanks,
Click to expand...
Click to collapse
You can follow this official guide - https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
File you can join the group and get it, its not shareable.

sosimple said:
Hi, can we have a tutorial step by step with the nessesary file?Thanks,
Click to expand...
Click to collapse
You need to join the group and get the boot.img file, as @ammarwajihi said.
To root the device, follow the official guide linked by @ammarwajihi, but instead of performing steps 1-8, just flash the boot.img provided in the group. You need to be on firmware stated on group, but for me worked latest firmware downloaded with Frija.
You don't need to boot into recovery to have magisk, just boot normally. Data wipe is required.
Let us know if everything worked.
loripino13

loripino13 said:
You need to join the group and get the boot.img file, as @ammarwajihi said.
To root the device, follow the official guide linked by @ammarwajihi, but instead of performing steps 1-8, just flash the boot.img provided in the group. You need to be on firmware stated on group, but for me worked latest firmware downloaded with Frija.
You don't need to boot into recovery to have magisk, just boot normally. Data wipe is required.
Let us know if everything worked.
loripino13
Click to expand...
Click to collapse
Thanks. I won't try it I'll stay unrooted for a while. I just want to know how when I'll need it.
I suppose this method trip knox?

sosimple said:
Thanks. I won't try it I'll stay unrooted for a while. I just want to know how when I'll need it.
I suppose this method trip knox?
Click to expand...
Click to collapse
Yes, unlocking the bootloader will always trip knox.