Database Develop

[Q] Rooting an I8190N

Hello everyone.
I got a little problem with my phone, since i want to root it, i checked out which build I had installed on my phone, here's the results:
i.imgur.com/1sOmg7i.png
As you can see, my build is an AMG3/AMF3, and i couldn't find any guide for rooting with that build installed.
What should i do?
Thank you in advance,
Amaryl.

Hi there,
Firstly, I am new to all this too, so take my advice, or leave it, with that in mind!!
I have recently rooted mine from the AMG3 build with mskip's toolkit. I took the plunge and took his advice on choosing the closest available build. I donated so as to be sure I had his latest update of the toolkit. I am not near my pc, but it was the selection which included the AMD3 build (the most recent, ie bottom in the section for the model with NFC, as that is themodel I have). I had one root through odin which failed to give superSU any binaries or permissions at all, so then completely reinstalled the toolkit on my pc (possibly unnecessary) and then reflashed twrp recovery, but chose the cwm version of superuser and ot worked perfectly! As far as I can tell, my phone works exactly as it did before, but now with root access.
If you look in this section of the forum, I posted a q this morning which gives a couple more details about the process I went through re 1st failed attempt which I won't retype here, but I can confirm I have full rooted functionality with the toolkit over the AMG3 build on the N model of the mini, with twrp and superuser!
Btw I say a failed attempt, but my phone worked fine, I just got an error message at the end of the toolkit installing busybox, so booted the phone and superSU just said "there are no binaries I stalled, this is a problem!". So I assume I wouldn't have been able to exploit the root, but at no point did It stop the phone working as a phone.
As I say, I am faaaar from an expert, but that's my experience.

Working Root for T807A (AT&T)

I was reading some threads in the Fire Phone section since I've been waiting on root for that device too, but someone discovered and posted about the new version of Kingroot (v4.0), and how they were able to root with it. I immediately downloaded it and tested it out, and after two tries, I gained root access on my Fire Phone.
So I thought, what if this would work on my AT&T Tab S 10.5 (T807A)? WELL IT DOES!
I have root access on my carrier branded/bootloader locked tablet. I was surprised at first at how easy it was, and at the end, Kingroot even had a prompt to disable or remove KNOX. I don't know if it worked, but I had no problem with installing Xposed and some nice modules.
THIS APP IS ALMOST COMPLETELY IN CHINESE. I know, it sounds a little scary, but after a day of running root, I found it safe to post about it here.
Please read the english guide for some clear instructions. The links are below and make sure you download the newest version. It may take a few tries, but use a root checker to see if it actually worked or not. KingRoot will install KingUser. After obtaining root, you can delete KingRoot and the blue icon app with the Chinese name.
UNTESTED ON OTHER VARIANTS BESIDES T807A! I believe it may work on the other carrier variants also.
I am not affiliated with the app nor deserve credit for what it can do, as I just want to spread the word that this works with our damn bootloader locked devices. If the people of KingRoot have a donation page, it might be that day to actually give thanks.
THE NEWEST VERSION (4.0+) WILL WORK. All you will need to do is press the Blue Button when you open the app, allow the installation of KingUser, and it will give root access. I verified it with a root checker and both my devices after multiple reboots. I installed SuperSu and updating the Su binary will FAIL.
YOU ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. DOING THIS CAN POSSIBLY BRICK YOUR TABLET SO PLEASE BE CAUTIOUS! THIS WILL VOID WARRANTY AND TRIP THE COUNTER!
Official site for KingRoot:
http://www.kingroot.net/
Guide that I used in English:
http://androidxda.com/root-android-device-using-kingroot
DOWNSIDES:
1) Kingroot is in only chinese with no english version supported.
2) As of right now, I can not update SU binary with SuperSu, Kingroot installs its own app called KingUser, which serves the same function. (someone will eventually figure out how to make SuperSu work since we now have root)
3) Bootloader is still locked, DO NOT FLASH CUSTOM FIRMWARE OR RECOVERY!!!!! IT WILL BRICK YOUR DEVICE!

REQUEST:
I need someone to make a backup of the AT&T stock firmware and recovery. I made a mistake with an app that messed with my recovery and now I'm in a bootloop.
If someone could please make a backup of each with Flashify or something so I can try with Odin in download mode, then I think it might be okay or I just found root and messed up my tablet.. lol
I made a backup myself but I was stupid and chose SDcard thinking it was referring to the external microsd card.
I NEED THE STOCK RECOVERY IMAGE for the most recent update for the ATT variant. (NK1)
I will keep the file links in this post for reference and in case someone wants it.
PLEASE AND THANK YOU!

That's sweet! As for firmwares, there are currently none I've found. Flashing can only backup recoveries. The only thing I can suggest is using samsung kies.
Just to confirm, your still on Kitkat correct?
Sent from my SM-T800 using Tapatalk

DUHAsianSKILLZ said:
That's sweet! As for firmwares, there are currently none I've found. Flashing can only backup recoveries. The only thing I can suggest is using samsung kies.
Just to confirm, your still on Kitkat correct?
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
I've tried Kies but I can't get it to recognize my tablet. I'm currently on NK1 which is kitkat 4.4.2

Does it trigger Knox?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

xiaonan80 said:
Does it trigger Knox?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
No
Sent from my SM-T800 using Tapatalk

sram21092 said:
REQUEST:
I need someone to make a backup of the AT&T stock firmware and recovery. I made a mistake with an app that messed with my recovery and now I'm in a bootloop.
If someone could please make a backup of each with Flashify or something so I can try with Odin in download mode, then I think it might be okay or I just found root and messed up my tablet.. lol
I made a backup myself but I was stupid and chose SDcard thinking it was referring to the external microsd card.
I NEED THE STOCK RECOVERY IMAGE for the most recent update for the ATT variant. (NK1)
I will keep the file links in this post for reference and in case someone wants it.
PLEASE AND THANK YOU!
Click to expand...
Click to collapse
Just extract the stock recovery from the stock Rom and flash with flashify.
Also I'm surprised Knox got tripped with this method.
I've had great success with other devices with kingroot, but it's never worked on the tab s.
If they have now found a working exploit then that is great news for locked bootloader devices.
Also if the android app fails don't give up, try the pc version. I've had the android version fail where the pc version had success.

sram21092 said:
I've tried Kies but I can't get it to recognize my tablet. I'm currently on NK1 which is kitkat 4.4.2
Click to expand...
Click to collapse
The only thing I can suggest, is for someone to use flashfire or some sort. I don't know why there's no firmware for T805W yet
Sent from my SM-T800 using Tapatalk

ashyx said:
Just extract the stock recovery from the stock Rom and flash with flashify.
Also I'm surprised Knox got tripped with this method.
I've had great success with other devices with kingroot, but it's never worked on the tab s.
If they have now found a working exploit then that is great news for locked bootloader devices.
Also if the android app fails don't give up, try the pc version. I've had the android version fail where the pc version had success.
Click to expand...
Click to collapse
Currently there is no place to download the AT&T stock firmware, which is why I need someone who roots their T807A to pull it for me and upload it so we actually have it. I've been looking all over the internet but no luck. The only thing I have access to at the moment is download mode, and I've been trying stock recovery.img I found for similar variants, but Odin is failing each time because of the locked bootloader..
Btw, installation from unknown sources needs to be allowed and it will ask to install KingUser. The first time I tried it, it didnt ask or work for me. The second time it asked to install and the root worked.

sram21092 said:
Currently there is no place to download the AT&T stock firmware, which is why I need someone who roots their T807A to pull it for me and upload it so we actually have it. I've been looking all over the internet but no luck. The only thing I have access to at the moment is download mode, and I've been trying stock recovery.img I found for similar variants, but Odin is failing each time because of the locked bootloader..
Btw, installation from unknown sources needs to be allowed and it will ask to install KingUser. The first time I tried it, it didnt ask or work for me. The second time it asked to install and the root worked.
Click to expand...
Click to collapse
The recovery wont be device specific, so any recovery from stock will do.

ashyx said:
The recovery wont be device specific, so any recovery from stock will do.
Click to expand...
Click to collapse
Do you think I would be able to flash a stock NK1.tar using Odin and make it work again? I only get "FAIL" when I try to flash any recovery
Here is the log:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Erase...
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

What did you use that corrupted your recovery?
By the way I just returned my T805 tab s to stock kit kat. The first 2 times I ran king root it froze at 20% then rebooted. The 3rd time it continued past 20% to 23%, it then rebooted and then after a short while the king root app restarted from where it left off.
It took a while to complete and at the end it said it had failed, BUT it hadn't! I checked and had root access. I then downloaded the kinguser app. After that any app could get root.
I would think that this method will work on any version. Not sure about lollipop though. My advice is if it doesn't work first time try and try again!
Here is the king root v4 app: kingroot v4
Kinguser v4: kinguser v4

ashyx said:
What did you use that corrupted your recovery?
By the way I just returned my T805 tab s to stock kit kat. The first 2 times I ran king root it froze at 20% then rebooted. The 3rd time it continued past 20% to 23%, it then rebooted and then after a short while the king root app restarted from where it left off.
It took a while to complete and at the end it said it had failed, BUT it hadn't! I checked and had root access. I then downloaded the kinguser app. After that any app could get root.
I would think that this method will work on any version. Not sure about lollipop though. My advice is if it doesn't work first time try and try again!
Here is the king root v4 app: kingroot v4
Kinguser v4: kinguser v4
Click to expand...
Click to collapse
I was messing around with twrp manager and I somehow ended up flashing some recovery. I don't even know if it was for tab s or not.
I was able to flash stock recovery for a different version on Odin and now it says I need to take it to the att store. I'm still able to get into download mode, but it won't let me get into recovery to factory reset. Hopefully a stock.tar.md5 can save me, otherwise I get a fail in odin

sram21092 said:
I was messing around with twrp manager and I somehow ended up flashing some recovery. I don't even know if it was for tab s or not.
I was able to flash stock recovery for a different version on Odin and now it says I need to take it to the att store. I'm still able to get into download mode, but it won't let me get into recovery to factory reset. Hopefully a stock.tar.md5 can save me, otherwise I get a fail in odin
Click to expand...
Click to collapse
Does kies not give you the option to repair or reinstall?

ashyx said:
Does kies not give you the option to repair or reinstall?
Click to expand...
Click to collapse
It won't detect my tablet. It tries to connect and then fails. Drivers install properly too

sram21092 said:
It won't detect my tablet. It tries to connect and then fails. Drivers install properly too
Click to expand...
Click to collapse
I forgot your device is snapdragon. You need the snapdragon recovery.
I'm guessing the Sprint recovery will work. That is available. If you can't get it I may have it somewhere.

ashyx said:
I forgot your device is snapdragon. You need the snapdragon recovery.
I'm guessing the Sprint recovery will work. That is available. If you can't get it I may have it somewhere.
Click to expand...
Click to collapse
the AT&T and T-mobile version are actually Exynos processors and verizon/sprint is snapdragon.
KingRoot might only work on Exynos processor versions of Tab S. But then again, we have to wait til others are willing to test it out

ashyx said:
I forgot your device is snapdragon. You need the snapdragon recovery.
I'm guessing the Sprint recovery will work. That is available. If you can't get it I may have it somewhere.
Click to expand...
Click to collapse
all he needs is someone with the 807a to hook up to kies and when it downloads the firmware you can copy it from the pc to desktop before the firmware dissappears as it will be gone once process is complete
Sent from my SM-G925V using XDA Free mobile app

sram21092 said:
the AT&T and T-mobile version are actually Exynos processors and verizon/sprint is snapdragon.
KingRoot might only work on Exynos processor versions of Tab S. But then again, we have to wait til others are willing to test it out
Click to expand...
Click to collapse
My error you're correct, att is exynos.
I tried it on lollipop and it wasn't able to get root , so looks like its kitkat only.

[/COLOR]
elliwigy said:
all he needs is someone with the 807a to hook up to kies and when it downloads the firmware you can copy it from the pc to desktop before the firmware dissappears as it will be gone once process is complete
Sent from my SM-G925V using XDA Free mobile app
Click to expand...
Click to collapse
Would this guide help http://forum.xda-developers.com/showthread.php?p=60546134 I believe you also need a serial number in kies.
Sent from my SM-T800 using Tapatalk

Unable to enter Custom Recovery, Galaxy Pro 10.1 SM-T520 .Help Please, dead Robot

Hi all,
I have been hammering away at this one, and putting it on the back-burner, but now, it is really getting to me. Samsung Galaxy Tab Pro 10.1 SM-T520
It has been rooted with ODIN, and shows no problem, (things seem much easier now, as I have re-jigged lots of my old phones using so many more tools, I am not an expert, but can read and search without too much problems) I was very careful to choose the correct file, CF-Auto-Root-picassowifi-picassowifixx-smt520.zip, I have rechecked this step several times, as most of the instructions I found ODIN device ID:COM box should become yellow, when on newer versions it is blue I think, I wondered if I was going mad,
Root Checker Root access granted, all fine. I have Root access. n.
Installed CWM ,latest recovery for a Pro 10.1 wifi, recovery 6.0.3.1 Titanium backup-ed, all ready to go and Reboot and flash a new ROM.. No joy. .. Installed TWRP , same.
When it re-starts it ,shows the galaxy logo, flashes off, then back on, and then fails. Android dead with a red warning , standard recovery KOT49H.T520XXUANAE, all I can do is the usual options:apply update. The only thing I haven't tried is to just wipe all the data. I have a backup of my apps with Titanium Backup on the SD card,I am not that bothered really about much other data if its a pain. I just want control of my device and to try a new ,cleaner ROM(SMT520_GraveD_V3.0)
This has been bothering me for ages, I have read so many posts so am now getting really frustrated I have bought triangle away app. today although I think I sorted that issue early on anyway , but just in case...
Super SU seemed to have vanished so that is back installed
I think I searched and found the Mount/system issue and looked into an issue that lead me to the .system folder, but it is hidden, so I could not find the file it related to. I dont have the specifics to hand as I checked it out at work. I wondered if it is because I have ES file manager, not ASTRO as it said in some of the posts I found.but sure this is a red herring.
I have tried everything..I have a Mac at home and PC at work, I have tried ADB and can see &restart the device etc... so I am connected, first I got the error that it didn't recognise the sideload command. Read up on ADB , looked at the help etc. sideload isn't there as a command, very confusing. But I think I got there one I figured out paths, as of course they are different on a Mac, and possibly more so as I have 2 drives in it, which often confuses me ..grr.
I can of course get into the bootloader, with ON+VOL -, it tells me so far the system is : Official and Knox Warranty Void: 1 which I think is fine, but a chap at work suspected this, but after lots of threads I gather this is normal..
Sorry if long, just thought I should be as clear as possible. I have not really come across such an awkward issue as this , my HTC One was a breeze:crying:
*edit* Just worked out through trial and error, that to use the sideboot command I had to select send via ADB and now with the path /Desktop/SMT520_GraveD_V3.0.zip I was able to send the file but with the following messgae : E:footer is wrong and E:signature verification failed, twice.. So some progress
Thanks !

Just to say after being up waay too long on this, I discovered there is a newer firmware T520XXUANI1_T520BTUANI1_BTU which I may aswell upgrade to first, but of course I cannot do this OTA now As it recognises the device is 'tampered with' *sigh* so gun and games with Odin for Mac tonight, or JODIN3 , just to get the firmware upgrade(which seems to be a jungle of fake download links). before a Rom without bloatware..
I am also not completely clear why, as from another thread about KNOX, as I am basically running stock , without custom recovery.. According to this thread , but I am getting a bit confused now
http://forum.xda-developers.com/gal...neral/knox-warranty-void1-otas-t2996067/page2
Click to expand...
Click to collapse
however this is another story from the ROM install. Apologies

Well. No replies, but I did eventually solve this. Hopefully this can help someone. I am a tinkerer, but I really nearly gave up on this..But this was a cheap second hand tablet ( my first) and I want to see what it can do before I test drive one on my mother who is having nightmares with every Windows laptop I give her!
Once I got to a PC , I had access to Odin3, although it is not available online (apparently to Mac) I could not get it to work due to Java issues (JOdin3 online - brilliant idea but no joy for me so far)
I had the Rom I wanted ( GraveDigger- SMT520_GraveD_V3.0.zip ), the firmware update (T520XXUAOD2_T520BTUAOB1_BTU.zip(i think)) and the unlock file (CF-Auto-Root-picassowifi-picassowifixx-smt520.zip) , non of which I could install in any way , due to being locked out of using a custom Rom bootloader!
At this point I factory reset and cleared the cache( as that is the only options in the basic bootloader!) I also has ADB on the PC so attempted to install the files this way (after messing about using some software to produce the .tar and .md5 files needed for Odin. I tried everything to get this into proper 'bootloader mode' all from scrach again, including trying the adb oem unlockbootloader command, which I would never get to work as I could not get there!
With Odin, I was also again able to flash the firmware update, eventually, and of course had to unlock again. I was curious if I could now use the OTA update, and could not. At some point, in repeating this process( as I think it hung up several times and needed a hard reboot) I had at this point fully wiped the device as I know that is another reason to have glitches and an unstable ROM later.
I think I then tried to check and although T520XXUAOD2 seems to still be the firmware, at some point I managed to get online ( I think some superuser app which I have had to try several may have notified me that KNOX was reset:laugh:When I go to About>Software update it said I had the latest update! Good news!
At this point I had installed both CWM and TWRP again , and thought I would try TWRP.I had tried CWM and the same problem, like a double flash of the Samsung Logo , so I know it had reset !!
THIS TIME I used TWRP ( I thought of trying CWM touch, but its either paid, or I would have to find and ABD the file over I guess) , I managed to re-apply the Root file, Root checker confirmed this , as it had throughout this ordeal!, although apart from ACCESS GRANTED I dont really know what the rest means..Anyway although picassowifi , was still in Device name on TWRP I chose an earlier recovery version to install.- twp-2.7.0.0-picassowifi.img. When I re-booted, I was able to get the TWRP recover image, and install the ROM, I cannot remember if I re-rooted as I was so elated.
I had a few , freezing moments, reinstalling most of my apps through Titanium Backup, I think I just tried to reinstall everything which of was unnecessary, after a hard reset, all seems fine. I checked and the TWRP recovery seems to have stuck. I am not entirely sure how to check about the firmware , but for now I feel this is progress.
Good Luck if anyone found this any use.
Just to add, when you search this ( and probably many other models) you seem to get so many sites, offering exactly the same unlock information, in exactly the same way, many of the downloads seem to take you to many weird and wonderful places. So I tended to look here for downloads if possible. But I had to join SamMobile (which seems a useful site for the firmware upgrade) and trawl all over and assume similarities between other Samsung devices to fully check I was not being an idiot. But this was very odd and I could not find any posts or other workarounds that I did not try. But this new ROM feels lovely and smooth so far, and I now want to look into this tablet further

Stock TMobile D415 ROM D41520b_00.kdz Lollipop 5.0-- Can't root?

I'm a bit slow to realize this, but after updating to T mobile's latest 20b firmware (lollipop 5.0x), it lost root. I then tried to root it, using the three methods mentioned here: http://forum.xda-developers.com/showthread.php?t=2732311.
Towelroot clearly doesn't work anymore. The zip file in the above thread couldn't be flashed since there's no recovery operation possible (just showing an android with ! in a triangle sign). I also tried the purpledrake, but the script doesn't run when the phone is connected with all drives installed and adb devices showing the phone. I then tried to get fastboot mode back (to install twrp/cwm recovery to flash the zip file) by following http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825 which I have done successfully before, but then couldn't do it because it requires root (doh!).
So it seems that I just lost my ability to root, unless I downgrade to a stock kitkat (10e?) from tmobile, and then towelroot/etc. assume those work.
Anyone with experience on the stock 20b firmware? Can you root it and how? I'd love to use the beautiful 12.1 Cyanogen that's available here, but the camera doesn't work right on mine. Thus stock 5.0 seems to be the best option. Many thanks.

I got a bit further on the purpledrake method, in that I had to do a clean restart on the phone and connect to usb before the script will recognize. However, it ends up giving a really quick error message after trying a temp root: "your phone is not running a compatible software version. No vulnerable mode detected. Rebooting phone."
Anyway, many thanks to @brossovitch I followed http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/ and it works like a charm. I can't seem to delete this very short thread so I thought I'd wrap it up with a solution. If it seems a bit useless please remove the thread (or tell me how to do it since I can't find the "easy button"). Thanks.

Update to "Messed up badly with Xposed"

I rooted my SM-G530W Galaxy with Android 5.1.1 and it worked great until I tried to install Xposed.
Well after hours of work and gigabytes of files downloaded I'm still stuck.
Here is where I am at this point. I can't get the recovery screen, only the download screen so I can still flash CF-Auto-Root successfully but the phone just stops at the animated samsung screen after reboot again.
dr.fone won't even detect the device but ODIN and Kies3 do.
Uninstalled KIES3 to avoid possible conflicts with ODIN
I downloaded sdk tools for Windows but can't figure it out.
Lastly I downloaded a factory ROM and I've tried to flash it with ODIN which fails every time. ODIN checks the MD5 file and says it's ok but seems to fail after "NAND write start". Seems weird that CF-Auto-Root still works but the factory ROM won't but I really don't know much about that.
So ANY help will be much appreciated folks. Thank you very much, Wally.

WallusW said:
I rooted my SM-G530W Galaxy with Android 5.1.1 and it worked great until I tried to install Xposed...
Click to expand...
Click to collapse
I don't have this device but, one of the following threads may be helpful for what you are looking for and, if needed, post your question within one of them.
https://forum.xda-developers.com/showthread.php?t=3302883
https://forum.xda-developers.com/showthread.php?t=3530403
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Thanks but I was just messing around with ADB and I get an "unauthorized" message from the devices command so I think it may be boot locked.
Just something else to work on. Any Ideas ?
Thanks again