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.

IOroot25 issue

Hello, all! I've been out of the country since February, and just got back yesterday. Anyways, my G2 was obviously severely outdated, so I downloaded and flashed the debloated Verizon OTA as well as 24a firmware. With that, I lost my previous root (no biggie). Anyways, I downloaded IOroot25, and followed its instructions located here. I have everything set up properly, and I can see my phone in adb devices; however, once the script reboots the phone, the phone just stays off and I get like 10 popups on my screen that I must format drive U in order to use it. At one point, it also failed at installing a USB driver (no idea why when I installed the official Verizon LG drivers).
Does anyone have any advice they could throw my way so I can get back into business with this phone? Also, I re-downloaded the drivers for Verizon he has in that thread, but no .exe file actually starts an installation process - you just click on it and it goes nowhere.
Sorry, I'm not extremely computer savvy anymore, so any help would be greatly appreciated. Thanks, everyone.

25226583 2353
BoostinBen said:
Hello, all! I've been out of the country since February, and just got back yesterday. Anyways, my G2 was obviously severely outdated, so I downloaded and flashed the debloated Verizon OTA as well as 24a firmware. With that, I lost my previous root (no biggie). Anyways, I downloaded IOroot25, and followed its instructions located here. I have everything set up properly, and I can see my phone in adb devices; however, once the script reboots the phone, the phone just stays off and I get like 10 popups on my screen that I must format drive U in order to use it. At one point, it also failed at installing a USB driver (no idea why when I installed the official Verizon LG drivers).
Does anyone have any advice they could throw my way so I can get back into business with this phone? Also, I re-downloaded the drivers for Verizon he has in that thread, but no .exe file actually starts an installation process - you just click on it and it goes nowhere.
Sorry, I'm not extremely computer savvy anymore, so any help would be greatly appreciated. Thanks, everyone.
Click to expand...
Click to collapse
I used the guide here:
http://www.droidviews.com/root-and-...lg-g2-verizon-att-sprintt-mobile-bell-rogers/
Try the drivers indicated in step 2. If you do get the current loki drivers from Github the name has changed to loki_tool rather than loki_flash. The only difference is you need to type in "loki_tool flash recovery" rather than "loki_flash recovery".

[Q] Need Help Unlocking Bootloader/Installing CM

I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?

Seriously?
There aren't enough threads and guides for you to read already? Everything you need is already out there on this forum so why start another thread just because you are too lazy to search and read for yourself?

I have read around and have tried a number of guides a number of times. They haven't worked for me and I'm just wondering what i'm doing wrong. Even though all the information is out there, I don't have the experience to understand it apparently. I've spent hours trying to figure things out but i keep reading conflicting info and half-explained steps and now I'm just confused and would like a clear point in the right direction.
So, do i need to reflash the latest firmware, wait a few hours, then try again on a full charge? Or do i need a euro firmware? Which guide should i follow?
I've downloaded a few applications and driver packages and whatnot but if those could possibly conflict with each other and cause problems i could work with a fresh OS. I'm running OS X but i have linux VMs and friends with clean windows installs (mine is all sorts of messed up)

eatfoodnow said:
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Click to expand...
Click to collapse
It isn't a question of firmware, the phone needs to have an unlockable bootloader to be able to be, well, unlocked. Here is a list http://forum.xda-developers.com/showthread.php?t=2181581 of P880 bootloader versions. Follow the guide to check which BL your phone has.

Thats obsolete, all versions can be unlocked afaik, either with official method or by fuse editing. No need to keep sim card in,you just need proper drivers

Oh, OK, I didn't know that. But, even better, OP should not have any trouble, provided he follows the BL unlock guide here http://forum.xda-developers.com/showthread.php?t=2224020
Maybe his BL is already unlocked OR is relocked (meaning can't be unlocked anymore).

Its more likely that his drivers are messed up imo.
The fuse editing method should work for everyone, i recommend you give it a try

So the fuse method would be the "BL-unlock.bat" method on that bootloader unlock forum post? I've tried it before, but I'll try it again. The directions only say to run it, is there anything else I need? Now, since it's a .bat file I absolutely have to run it on Windows, right? Because if so I'll use a friend's computer instead of my windows installation.
What are the necessary installations before I run the file? How should I configure settings on my phone? (like what type of usb connection should it be)
There are a lot of things that people expect readers to know but I'm really not very knowledgeable about standard practices for phone stuff so I really need every step. Thanks for helping!

Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.

Flying_Bear said:
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Click to expand...
Click to collapse
Also, correct me if i'm wrong I only had stock for 2hours, but also stock needs usb debugging to be enabled or adb won't work?

Yep, afaik usb debugging needs to be enabled

When you are fast enough, it is possible in charging mode wihle the carger animation is shown. But you have install adb driver very fast...

So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!

eatfoodnow said:
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
Click to expand...
Click to collapse
you can check your bl status by entering sw mode (phone off, hold vol+ and insert charger) or reeboting into bl (adb reboot oem-unlock)
to install cm steps are:
-install recovery (you can choose either cwm or twrp, it's more about looks than functions)
-download rom zip onto sd card
-install said zip from said recovery, there's no adb involved
Now my personal opinion, I really don't see the point in flashing 10.1, i would go staright for cm11 if i were you

Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.

eatfoodnow said:
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
Click to expand...
Click to collapse
Factory reset then get nandroid manager app and see if you can restore your stuff with that
CM11 is bugless atm and performance (imo) is way superior

So after a factory reset/data wipe, my phone just booted into CM10.1 and now that's working. And it looks like all of my stuff on the phone is still there (though of course apps aren't installed and whatnot, that wouldn't make sense). Thanks for all the help!
I tried to find a feature list or something to see what exactly is better about CM11, and found out that "stable" doesn't exactly mean stable for CM, and that it looks like a good idea to update, so I think I will try to update to that. Do you know anywhere that has an actual feature list to show me what CM11 does that CM10.1 doesn't?

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.