Develop Bugs

[Win32 Tool]GUI One Click Root and UN-Root / VZW / US ONLY / DOWNLOAD ADDED

!!Check out the Video on how it works!!!
http://www.youtube.com/watch?v=ZANt0vaiZYs
[Disclaimer]:
The method of rooting your Android device as described below is solely by your choice and your choice only!
IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA.
I, XDA, and other forum members claim no liability for any harm that may come to your device, including, but not limited to: bricked phones, voided manufacturer warranties, bootloops, loss of data, etc
While generally this software is safe, and does have fail safe and error checking, it does not mean that something can/shell/or will not go wrong. Please be prepared if it does.
[/Disclaimer]
[Information]:
Device Supported:
MZ600 VZW 3G/4G
Software Supported:
3.0 Build HRI39
3.0.1 Build HRI66
3.1 Build HMJ37
Method Used:
Fastboot oem unlock
Unsecured boot.img for device software.
Features:
Fast and easy 1 click root method for supported sw.
Error checking to prevent mistakes as much as possible.
Takes 5-8 Mins to Unlock/Root device.
Install's SU and Superuser.apk
Detects Software version to version selected, helps install correct files needed.
Other Information:
This will WIPE ALL USER DATA.
Tested with:
3.0 Build HRI39
3.0.1 Build HRI66
3.1 Build HMJ37
I have personally restored to all three version's of the software and tested root and unlock on all software version's. This should/will work as long as you follow instructions. Its really not hard, and its hard to mess up.
[/Information:]
I know there is just a WIFI Version and I will add support later. It will auto detect you're phone mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[DOWNLOAD LINK HERE]
Download Here DO NOT POST ON OTHER FORUMS IF ITS POSTED ON OTHER FORUMS I WILL REMOVE LINK AND STOP SUPPORT THIS IS FOR XDA ONLY!
Download Unroot_tools, please extract into the unroot_tools folder.
If you use this software please leave feedback.

Supported Devices:
US VZW 3G/4G on either 3.0/3.0.1/3.1
Support for other devices planed:
US VZW WIFI on either 3.0/3.0.1/3.1
EU Xoom's
Support to flash Clockwork Recovery is planned.
Support to install new framework for SMS/MMS/UAString on either 3.0/3.0.1/3.1
*I will not enable phone features untill a phone app can be used, i use another carrier other then VZW and I myself would like to be able to use the phone feature as well but can't untill a new phone.apk is compiled for honeycomb or one comes out that works with it*

Looking pretty smooth. Just took the plunge to root via adb though.
The unroot method will let you lock without getting any LNX errors,?

The LNX error from what I seen is because the device needs to be unlocked again in order to boot.
Ill have too check it out again, I restored mine last night and received this LNX error. The way to recover was to boot fastboot by shutting the device off first VOL UP + PWR let it stay off for a min then boot into fastboot by VOL UP + PWR this kicked me into fastboot and running the cmd fastboot oem unlock my device was able to boot properly without an issue.

I am assuming the device cannot be locked and boot because the img files are not signed files from Motorola? I ran into this problem recently while trying to revert back to stock and locked to give the video app a try. I had a terrible experience with LNX 0x0004. Pretty severe brickage. Kinda scurry thought I had a high dollar paper weight.
amoamare said:
The LNX error from what I seen is because the device needs to be unlocked again in order to boot.
Ill have too check it out again, I restored mine last night and received this LNX error. The way to recover was to boot fastboot by shutting the device off first VOL UP + PWR let it stay off for a min then boot into fastboot by VOL UP + PWR this kicked me into fastboot and running the cmd fastboot oem unlock my device was able to boot properly without an issue.
Click to expand...
Click to collapse

Yes, sorry still at work so short answers.
From what it seems is that you have to return completely to stock images, even then it might now work. From what it seems the application the removes the lock might also implement security in order to prevent from being locked again.
While the lock method works for some I think its all dependent on when people got their xoom. Mine is new and came loaded with latest software.
I think you hit it right on the nail. I think that even returning back to stock because the images and boot partitions have been modify the device will fail to boot. I have tried RSDLite to restore the SBF all the way from version 4.8 to 5.3.1 and it will not restore it fails each time. Only way to recover it was to re unlock the device and the device booted fine.
Tried to relock again and it failed to boot.

W00t just what we need...

It should be much more difficult for them to brick there device with this tool. As the user isnt using a 1 click method made for 1 version of the system.
The problem with the 1 click's out is currently they flash 1 boot.img for only 1 system either 3.0 or 3.01 this cause the device to hang at boot then people thinking something went wrong.
The program is designed with error checking in mind.
As seen in the video I show you this by purposely selecting the wrong software version, it notify's me that i'm trying to install the wrong boot.img for the a mismatched version of the os.
Also i was receiving the LNX errors before when trying to relock the device i figured out a good method and it will be implemented.

This is amazing if this works flawless, and I'm Super new to android, and I just bought a Xoom, I'm curious what does Rooting do for the device?, also why do people try to Un-Root for?

This is 3G only?

Yes 3G only, once the 3G is completly done ill focus on the WIFI version. I do not have a WIFI version myself so it will be based of whats posted.

Bad ass! Can't wait for wifi version! Great work
Azrael X 4.0

Can you tell me where the download link is?

Its comming as soon as i fix the MD5 Checks for the files and images.

Download Link Added.

Thanks op, I used this to unroot my xoom and it worked perfectly.

Thank you for the reply glad you liked it.

I'm eagerly awaiting the WIFI version! Woot!
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I dont have a WiFi version so I need someone with adb experience so that I can implement a wifi version.
I take it just need the right boot images as well for the wifi version as there seems to be some hardware differences. But i need someone who can adb the device and get me some getprop information so that i can implement the wifi version of the device. I have rooted and unrooted my device over 20 times with this tool. Its fast and easy to use. I actually just updated it again with a new help box when it gets to fastboot oem unlock. I will have to also add one for the fastboot oem lock feature as I think I forgot to add that one.
Anyway.
If you have used this software Please Please leave feedback so that other users can see the success to fail rate. *THERE SHOULDNT BE ANY FAIL RATE* but if it fails i need to know so i can fix what ever it didnt do.

Will u not being doing this for EU xooms?

[GUIDE] Rooting and Unbricking p930/p935/p936

EDIT: I no longer support this guide, as I've not owned a nitro for at least 2 years now. It is all still accurate however, just make sure to follow the steps.
The package is hosted on my google drive, and I have no plans to remove it, so if this thread is still up, so are the files.
Good luck!
--------------------
This guide will work for P930, P935, and P936 users.
I have merely put all the pieces together to have a concise all-in-one solution for rooting/unbricking the LGE-IPROJ. Credit is given to original contributors at the bottom of the guide.
As always, I am not responsible for any damage done to your phone by following this guide. Follow at your own risk.
I strongly suggest removing your SDCARD from the phone until step 18 since it causes the phone to boot slower and makes this process take longer.
Ensure that you have the LG USB drivers installed on your computer. If you don't they can be downloaded Here.
Foreword - This guide allows the phone to keep its correct build ID, so it hasn't got leftover data from the SU640 kdz which is flashed using the other method. We flash the experimental ICS build, root it, run keeproot, flash the p936 kdz, then run keeproot to restore root access. We then install CWM, and then we can flash ROMs to our heart's desire.
The reason we have to flash the p936 KDZ is that it overwrites the v18f secure bootloader, allowing us to flash CWM and not brick the phone.
1 - Download this package
2 - Backup your phone if you want.
3 - Extract the Unbrick Package
4 - Place phone in Download Mode (Turn off phone, then hold volume up while plugging in USB cable)
5 - Run the file - P930_UDT_v18f_04112012
6 - Set your phone to allow installation from unknown sources, and enable USB debugging.
7 - Run TPSparkyRoot.bat, following the instructions in the window.
8 - Perform a factory reset of the phone. This is done by shutting off the phone, then holding VOL DOWN + Power until the phone says FACTORY HARD RESET, then following the prompt (pressing power twice)
9 - Allow USB Debugging on the phone.
10 - Run Before.bat contained in the KeepRoot folder.
11 - In the KDZ tools folder, install msxml and run B2CAppSetup (Close the application after it has installed)
12 - Run Windows Enabler as Administrator, and press the icon in the system tray to activate it. (Windows enabler allows you to click on grayed out options to unlock them in programs. You can then set the option as you normally would.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
13 - Place the phone in Download Mode (Turn off phone, then hold volume up while plugging in USB cable)
14 - Run KDZ_FW_UPD.exe. You need to set Type to 3GQCT, PhoneMode to CS_EMERGENCY, and point the KDZ file field to V10F_00.kdz
(SOME PEOPLE HAVE REPORTED HAVING TO PRESS "Read Phone Info" FOR THIS STEP TO WORK!)
Once these settings are enabled, hit the "Launch Software Update" button.
15 - After the update has run, the phone should bootloop on the second logo screen. While it does this, run AfterROOT.bat from the KeepRoot folder.
16 - Perform factory reset. This is done by pulling the battery, then holding VOL DOWN + Power until the phone says FACTORY HARD RESET, then following the prompt (pressing power twice)
17 - Set phone's language to english, then enable usb debugging.
NOTE: The following steps are optional. Downloading Rom Manager from the Play Store and installing CWM from there will do the same thing.
18 - Place the recovery.img file in the root directory of your phone's SD card
19 - Open cmd in KeepRoot\adb
20 - Run the following commands, while the phone is plugged in and has USB Debugging enabled
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Click to expand...
Click to collapse
21 - Accessing CWM - This is done by shutting off the phone, then holding VOL DOWN + Power until the phone says FACTORY HARD RESET, then following the prompt (pressing power twice)
Congratulations. Your phone now has CWM 6.0.1.5 installed, and you can flash any of the CWM flashable zips available for the P930 on XDA.
Edited: Added images, included more information, took corrections from posters.

Credit
- TPSparky for his root method
- alexw88 for This Post
- usercim for This Post
- Drumist, for helping me figure out how to use this method

It work for SU640? I want to downgrade ICS to GB.

I would use mazchalets or drumists, stickied guide for su640. If you replace the KDZ file in this method with a SU640 kdz, I see no reason why it wouldn't work. Even with the files included it will work, but you will have a P930 build ID.
Sent from my LG-P930 using XDA Premium HD app

I tried that guide but not success. However, thank for your advise.
Sent from my LG-SU640 using xda app-developers app

Work for anyone yet.....? and whats wrong with the one that exists that covers it all cuz all this does is diminish other guides that others have used, just trying to understand WHY sooooo many guides and no wonder many are confused??

I'm missing something. What benefit is there to keeping the build id?
Sent from my LG-P930 using xda premium

X0dus said:
I'm missing something. What benefit is there to keeping the build id?
Click to expand...
Click to collapse
Unsure. However, that is not the only difference. Another one I have noticed is that when turning on your phone, it will vibrate to indicate you've held the button long enough. This is something that never works after using the standard unbricking method. A Korean KDZ also means you will have a Korean baseband installed which doesn't work on the P93x devices, and you'll have to flash a new baseband at some point.
All in all, these are minor things though. I don't know if there is any major difference. This method does not require modifying your hosts file OR configuring the https.exe program, which makes it a little bit easier in my opinion.

drumist said:
Unsure. However, that is not the only difference. Another one I have noticed is that when turning on your phone, it will vibrate to indicate you've held the button long enough. This is something that never works after using the standard unbricking method. A Korean KDZ also means you will have a Korean baseband installed which doesn't work on the P93x devices, and you'll have to flash a new baseband at some point.
All in all, these are minor things though. I don't know if there is any major difference. This method does not require modifying your hosts file OR configuring the https.exe program, which makes it a little bit easier in my opinion.
Click to expand...
Click to collapse
Thanks. Clears up things a bit for people that haven't used a guide yet.

Thank you for this! Can any of the people who used this confirm whether or not this has an impact on the camera reboot bug in CM10?
Also wondering if it would be OK to follow this and then restore a full nandroid backup.
Sent from my LG-P930 using Tapatalk 2

Also wondering if it would be OK to follow this and then restore a full nandroid backup.
Click to expand...
Click to collapse
Yes, that's safe to do.

Not sure if it's due to aokp or having used this guide, but I haven't had a random reboot or bsod since. I also don't have the camera reboot issue.
EDIT: Screen not waking from sleep has happened once now, and I have started getting random reboots again. The camera reboot issue is still eliminated though. Probably going to switch to HO!NO!'s Full Throttle 9 and see if that improves my reboot situation.
Sent from my LG-P930 using XDA Premium HD app

hereric said:
Not sure if it's due to aokp or having used this guide, but I haven't had a random reboot or bsod since. I also don't have the camera reboot issue.
Sent from my LG-P930 using XDA Premium HD app
Click to expand...
Click to collapse
I will probably give this a try later on today. Thanks for making this write-up!

Was on Liquid Nitro, made a CWM full backup and did the new unbrick process this afternoon.
its easier than the su640 one.
Two little problems:
1. on step 12, after running windows enabler, have to left-click the icon on system tray to active it.
2. all prompts in bat files are in Chinese...need to change to English.
After that, I restored my backup over the GB ROM and it seemed to work fine. But I later learned that CWM didn't backup baseband, so I reflashed Liquid Nitro again then did another restore over the Liquid Nitro just to be safe.

If I have the P930, and I've successfully flashed and rooted the ICS build, is there really any need for me to continue further with the guide? What's preventing me from just flashing recovery right now and being on my way?

LiquidSolstice said:
If I have the P930, and I've successfully flashed and rooted the ICS build, is there really any need for me to continue further with the guide? What's preventing me from just flashing recovery right now and being on my way?
Click to expand...
Click to collapse
ICS bootloader doesn't work with CWM so we need to do the unbrick to back to GB bootloader.

Every time I open the KDZ fw update, all the options are greyed out. I'm stuck there. Ideas?

arda99 said:
ICS bootloader doesn't work with CWM so we need to do the unbrick to back to GB bootloader.
Click to expand...
Click to collapse
Thanks. Indeed, I was dumb and flashed recovery and got the secure boot issue. Now that I have that, should I redo the whole process?

I've done the whole thing over twice now, I simply cannot get the KDZ firmware updater to do anything. If I try "Read Device Information" it always freezes and exits.
EDIT: No matter what I do, even going so far as to try this on a computer with freshly installed Windows 7 on it (and of course, installing the provided LG driver), I keep getting stuck at this infernal screen:
http://db.tt/Ro57bvLc
MSXML is installed, the Window Enabler is started as Admin, but the damn thing just won't let me use any of its options .

LiquidSolstice said:
I've done the whole thing over twice now, I simply cannot get the KDZ firmware updater to do anything. If I try "Read Device Information" it always freezes and exits.
EDIT: No matter what I do, even going so far as to try this on a computer with freshly installed Windows 7 on it (and of course, installing the provided LG driver), I keep getting stuck at this infernal screen:
http://db.tt/Ro57bvLc
MSXML is installed, the Window Enabler is started as Admin, but the damn thing just won't let me use any of its options .
Click to expand...
Click to collapse
After running windows enabler, left click the icon on the system tray, you'll see an "ON" shown on the icon. Then the grayed area will be enabled.

"Your device has been modified"

Here's the deal. I bought this Note 2 off a friend's friend so I can't *really* be sure what went on with this. It's under warranty still though.
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available". Here's what I tried:
1. Factory reset: Made no difference
2. There's no SD card so it can't be anything to do with the SD card (as reported in some other similar threads)
3. Flash counter is ZERO
4. Phone is unrooted.
So I don't really know what to do now. I'd flash 4.1.2 with odin but my dad is using it and he wants to do it the 'legitimate way' whatever that means.
Anyway, so do we have a 'fix' for this? If not, am I safe to go to the Samsung service center with this since the flash counter is 0 so they can't say that I've modified it?

cyanide911 said:
Here's the deal. I bought this Note 2 off a friend's friend so I can't *really* be sure what went on with this. It's under warranty still though.
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available". Here's what I tried:
1. Factory reset: Made no difference
2. There's no SD card so it can't be anything to do with the SD card (as reported in some other similar threads)
3. Flash counter is ZERO
4. Phone is unrooted.
So I don't really know what to do now. I'd flash 4.1.2 with odin but my dad is using it and he wants to do it the 'legitimate way' whatever that means.
Anyway, so do we have a 'fix' for this? If not, am I safe to go to the Samsung service center with this since the flash counter is 0 so they can't say that I've modified it?
Click to expand...
Click to collapse
Humour yourself, reset again, see if it helps.
Another thing you can try doing, which I've read somewhere:
Go into Settings
App Manager
Clear data for SysScope and Enterprise SyssSope
Click to expand...
Click to collapse
If not, the other way is to flash stock firmware using odin.
Once you've flashed stock, root and use triangle away to set it back to zero then unroot by going into SuperSU and choosing "Unroot"
There are loads of threads on here if you get stuck during any steps/
Though you might to leave it before flashing firmware, your warranty is pretty useless.
When you really need to claim then you should go ahead, but until then, there really isn't much use until an update comes out.

Download Samsung kies.
http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
Connect your note 2 to your pc and open kies.
It will tell you if an update is available.
this will remove all modifications.
This is the legitimate way.

cyanide911 said:
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available".
Click to expand...
Click to collapse
I am also little bit curious about it.
I bet it shows that Samsung somehow detected that we have modified device (root,flash, Odin...) - and prevents us from legitime update. But still dont know if I am right - also have the same notification about "modified device" since root.
I hope that in Kies there is somehow to repair device(like Sony Ericsson suite has) and this tool was able to reflash device even with unlocked bootloader

kies.
tools.
firmware upgrade and initialisation.

You must try root your device with stock recovery ery stock kernel stock rom and xposed framework
SYSCOPE MODULE
Sent from my GT-N7100 using xda premium

I experience almost the same thing,. I got my note2 from my service provider,. i had never rooted the phone since its still under warranty, however, there are times when i try to check for an update it warns me that i cant do OTA because my device has been modified. and on the status itself it says modified. Restarting my phone fixes this, the status goes back to "normal". It's just irritating to know that it says its modified although for a fact i know I never did. It's hard enough to resist the itch to root then the phone slaps you in the face making this kind of jokes on me.. looks like its teasing me (because this is the only mobile phone I had that I refused to root/flash for the meantime).. lol

I'm not able to update via Kies either. So I guess updating via Odin and then resetting the counter is my only possible path left?
I just want a device that can be updated via OTA updates, nothing else. I don't want to root or install any custom ROM or Kernel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nameless21 said:
Download Samsung kies.
http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
Connect your note 2 to your pc and open kies.
It will tell you if an update is available.
this will remove all modifications.
This is the legitimate way.
Click to expand...
Click to collapse
Second that. Just finished "clean up"...
---------- Post added at 07:12 PM ---------- Previous post was at 07:08 PM ----------
cyanide911 said:
I'm not able to update via Kies either. So I guess updating via Odin and then resetting the counter is my only possible path left?
I just want a device that can be updated via OTA updates, nothing else. I don't want to root or install any custom ROM or Kernel.
Click to expand...
Click to collapse
I didn't see XXX before. As you're on 4.1.1 you may use CSC changer without root. But definitelly change your CSC (best if you pick CSC for the country where you are). There's a list of CSC's in the forum, search and change. Then reflash ROM via KIES and it'll be clean

It seems I'm unable to change my CSC. Whatever I try to set it to via the play store CSC changer app, it remains the same (as you can see in the Kies screenshot in my previous post).

cyanide911 said:
It seems I'm unable to change my CSC. Whatever I try to set it to via the play store CSC changer app, it remains the same (as you can see in the Kies screenshot in my previous post).
Click to expand...
Click to collapse
Well... The XXX is Unknown CSC. Go to sammobile.com and try to find firmware for your country. If not available, then try international version (BTU or XEU). Do hard reset and flash with Odin 3.0.4. After flashing do hard reset again and you should be OK.
Sent from my GT-N7100 using xda premium

aspot72 said:
Well... The XXX is Unknown CSC. Go to sammobile.com and try to find firmware for your country. If not available, then try international version (BTU or XEU). Do hard reset and flash with Odin 3.0.4. After flashing do hard reset again and you should be OK.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yeah just downloaded the INU firmware, I'll go ahead with it. One more thing that I noticed in this whole process.
My phone's IMEI behind it's battery is different to the IMEI it displays inside the phone. After some brief googling, it seems it's either improper flashing or maybe an unofficial mainboard installed am I right?

When there is CSC is XXX even after flashing Full ROM with wipe, there is little chances of EFS messed up. Again as you said your IMEI is different on device setting and on back of device under battery, there are two chances
- Motherboard is changed by unauthorised person but still not illegal way.
- Illegally tempered IMEI.
In case of first option I think flashing ROM with wipe may solve issue and you may get future update, but in case of corrupt EFS, you always need to flash with odin
and in case of last scenario (Tempered IMEI), your device may get banned from service.
Another thing, as per last screen shot if you still have 4.1.1 then you should flash 4.1.2 as soon as possible, otherwise your device may gets bricked anytime without any reason.

dr.ketan said:
When there is CSC is XXX even after flashing Full ROM with wipe, there is little chances of EFS messed up. Again as you said your IMEI is different on device setting and on back of device under battery, there are two chances
- Motherboard is changed by unauthorised person but still not illegal way.
- Illegally tempered IMEI.
In case of first option I think flashing ROM with wipe may solve issue and you may get future update, but in case of corrupt EFS, you always need to flash with odin
and in case of last scenario (Tempered IMEI), your device may get banned from service.
Another thing, as per last screen shot if you still have 4.1.1 then you should flash 4.1.2 as soon as possible, otherwise your device may gets bricked anytime without any reason.
Click to expand...
Click to collapse
Okay this is getting extremely strange. I flashed the latest 4.1.2 ROM for INU from Sammobile via ODIN. Everything works well except, well, the phone! I can't make any calls or texts or even receive any. If someone else calls me, my phone rings at their end but nothing happens at my end. Nothing at all. If I try to make any calls it says "Not registered on network".
I tried fiddling around in mobile networks in the settings, but nothing makes it work.
What the hell? I can't help but think this is something related to that IMEI number thing.

Very suggestive of your IMEI get banned.
Can you tell me first 5-7 digit of IMEI you seeing in device setting?
(Don't put full imei on public forum)
If your imei in setting is starting with
00499 then it is generic.
Sent from my GT-N7100 using xda premium

Hmm, I used this patch after rooting and installing busybox:
http://forum.xda-developers.com/showthread.php?t=1918601
And now everything seems to be working fine. And now my device status is back to 'Modified' haha.
So what does all this mean? My IMEI number being different in the phone and behind the phone? And I don't even know what that patch above 'fixed', but it fixed my network issue.
None of the two IMEI numbers above are starting with generic type IMEI...

That's good
I said earlier your imei changed due to unauthorized mobo replacement, samsung ppl replace old imei if they change mobo.
So in that case it is repaired by unauthorized person (which can just cause problem in warranty) but not unofficially.
If still your csc is unknown then flash same rom with CSC tab in odin instead of PDA (which may factory reset, so make backup of your imp data)
Still it remain xxx in kies, then may be efs is corrupted and only previous backup is savior.
Sent from my GT-N7100 using xda premium

your device has been modified
Hi, I have successfully installed cynogen mod 10.1 nightly. And I again restored my original 4.1.2 but now when I trying to check OTA update it says "your system has been modified, software update is not available. Please please please help me.

your device has been modified
Hi, I have successfully installed cynogen mod 10.1 nightly. And I again restored my original 4.1.2 but now when I trying to check OTA update it says "your system has been modified, software update is not available. Please please please help me.

Ota to won't take

I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time

cmjester6421 said:
I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time
Click to expand...
Click to collapse
Try using FlashFire, it's basically Odin for your phone. I think you have to join the Google+ Community to download it, but it works great.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Without root or anything that will work.... I kinda feel like that may not be the case another thing at one point a long time ago I changed my modstrings would that impede on the install with ota
Edit: ya flash fire won't work need root
Edit2: nvm the modsring is stock so I'm still at a total stop here

cmjester6421 said:
Without root or anything that will work.... I kinda feel like that may not be the case another thing at one point a long time ago I changed my modstrings would that impede on the install with ota
Edit: ya flash fire won't work need root
Edit2: nvm the modsring is stock so I'm still at a total stop here
Click to expand...
Click to collapse
Modstrings? What are you talking about?

cmjester6421 said:
I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time
Click to expand...
Click to collapse
Once you update to the latest firmware, towelroot will not work. The exploit towelroot uses has been patched. And no one knows what you mean by "modstrings"

Well it don't work now anyway and forget the modstrings part I just need a way at this point to root and I cab roll with what I need to do worst case I have to go buy a new computer but I would rather not

cmjester6421 said:
I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time
Click to expand...
Click to collapse
bilgerryan said:
Modstrings? What are you talking about?
Click to expand...
Click to collapse
madbat99 said:
Once you update to the latest firmware, towelroot will not work. The exploit towelroot uses has been patched. And no one knows what you mean by "modstrings"
Click to expand...
Click to collapse
This will help everyone understand what he means by modstrings...
https://towelroot.com/modstrings.html
This would make a great t-shirt!..."Modstrings? What are you talking about?"
Yes he is right the latest update patches the towelroot exploit. But you can still use another method without computer. But basically if you want your whole world to open up then you will not need that update. For example im running 5.1 lollipop on my gs3 so that ota update is not helping me at all. Rooting your stock rom opens a couple door in an old phone. But installing a custom rom, kernel, mod, framework, etc. will open every door. My gs3 outperforms my sisters gs6 in many ways and i had 5.1 update before she did. Amd i can always put my phone back to stock rom, unroot, and make it under warranty terms again because i made backup. But if you want slight upgrade i can help you troubleshoot the ota installation. But if not its ok because my wife has same phone and didnt update and she is running same custom rom, kernel, mod, framework, etc that i am with no problems.
Check out this thread i started last night as its related and has more info...
http://forum.xda-developers.com/galaxy-s3-sprint/help/samsung-galaxy-s3-lollipop-5-1-custom-t3162496
Let me know what u decide to do

I'm doing full mods to this phone I had a s6 I really don't like it look as I said I don't have a computer I need the fastest path to getting cwm once I have the rom I want I can go fron there howevrr the fine tuning help would be a big plus from you if I evrr get this done lol the plan is to get cm 12.1 and go as far as I can to make this bettrr then the s6 please let me jnow where I need to go fron here

cmjester6421 said:
I'm doing full mods to this phone I had a s6 I really don't like it look as I said I don't have a computer I need the fastest path to getting cwm once I have the rom I want I can go fron there howevrr the fine tuning help would be a big plus from you if I evrr get this done lol the plan is to get cm 12.1 and go as far as I can to make this bettrr then the s6 please let me jnow where I need to go fron here
Click to expand...
Click to collapse
Fastest path to cwm is rooting your phone using towelroot or cf autoroot then install root checker app to verify root and then install app supersu and then install app called rommanager from app store and update the recovery in the app. Should only take a few minutes plus reboot time. No computer needed. Forget about the ota upgrade for now since you want cm12.1. Once cwm running do a nandroid backup so you have a stock rom image before doing anything else. Later you can revert back to the moment after you rooted if you run into any problems and try again, try ota update again, or unroot and get it back to warrantied state. Before updating to custom rom check out my new thread to get some ideas on what to back up to save your important data and other ideas. Yes i can help you furthur just message me anytime or ask in my thread..
http://forum.xda-developers.com/galaxy-s3-sprint/help/samsung-galaxy-s3-lollipop-5-1-custom-t3162496

Cf needs a computer right? And as for towel root I have ran it many times it says it worjed but su won't install....

cmjester6421 said:
Cf needs a computer right? And as for towel root I have ran it many times it says it worjed but su won't install....
Click to expand...
Click to collapse
My fault. I meant framaroot. Try this i think this is what i had to use from xda..
http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
The towelroot saying success is throwing me off. I will try to find out info on that. Did you use root checker app to verify root or no root? My first root i thought nothing happened at first. Let me know

Error 7 first exploit and error 9 secong exploit.... as for towel root years ago I paid for root checker advanced I know better its not rooted I have done factory resets and tried again I'm running 4.1.2 this is stock from a ota a long time ago I know you have no reason to hekp but if you can get me in the right place to make this work you save me a grand plus if I'm getting a new pc its asus gaming level what I had was 6k I won't take much less please let me know what you find I have been reserching for the last six hours.... no luck

Thanks to zip addict he found me king root and I looked in to it the 4.5 version I git root no pc all is needed after that is super sume from what he told me so that you can install the right super user and move on to a recovery now at this time I'm trying to find a dl for super sume that is not the play store as it says not compatible

About those root files

Hello. I'm just making this post to clear up some things and rumors about the posts going around about root firmware etc for newer ATT Galaxy phones like the s6, s6 edge, s6 edge + and the Note 5...
First of all these files have been around for some time now and only very few people in the unlocking/imei repair scene had them (including me) and just a few days ago someone decided to leak them and well they are now being offered for sale etc etc...Anyways these are what is called "engineering" kernel boot images with insecure adbd enabled meaning that it gives you root shell access.
Now the software that we use for our "unlocking" purposes only require this access to perform the operations that we want. However with all the new security Samsung has implemented, these kernels are by no means full root options. For example trying to use apps that require root (Titanium, Root checker) won't work and updating the SU binary under supersu app will send the phone on a bootloop because of SELINUX etc etc and as you know the only way to get around that is by flashing a custom kernel but ATT models having a locked bootloader this is not an option.
TL,DR : These files will only grant you "half assed" root that most people won't be able to take advantage of because it is all run over adb shell..maybe kernel wizards like @arter97 would like to take a look at them and see if he can find something useful
Any questions feel free to ask

Sunderwear said:
Hello. I'm just making this post to clear up some things and rumors about the posts going around about root firmware etc for newer ATT Galaxy phones like the s6, s6 edge, s6 edge + and the Note 5...
First of all these files have been around for some time now and only very few people in the unlocking/imei repair scene had them (including me) and just a few days ago someone decided to leak them and well they are now being offered for sale etc etc...Anyways these are what is called "engineering" kernel boot images with insecure adbd enabled meaning that it gives you root shell access.
Now the software that we use for our "unlocking" purposes only require this access to perform the operations that we want. However with all the new security Samsung has implemented, these kernels are by no means full root options. For example trying to use apps that require root (Titanium, Root checker) won't work and updating the SU binary under supersu app will send the phone on a bootloop because of SELINUX etc etc and as you know the only way to get around that is by flashing a custom kernel but ATT models having a locked bootloader this is not an option.
TL,DR : These files will only grant you "half assed" root that most people won't be able to take advantage of because it is all run over adb shell.
Any questions feel free to ask
Click to expand...
Click to collapse
Very informative, pretty much everything I needed to know. If you can't use root apps then I'm sure a lot of users will disregard the files, myself included as I only would like to use said apps. Thanks for the info?

all root files https://www.dropbox.com/s/gkxk32f778odlxu/AT&T_Root_Files.rar?dl=0

ohap said:
all root files https://www.dropbox.com/s/gkxk32f778odlxu/AT&T_Root_Files.rar?dl=0
Click to expand...
Click to collapse
how can we use that boot img with is associated with the N920AUCE2APB2 firmware, which no one has.
edit: turns out that the N920AUCE2APB2 firmware is based on the MashMallow (6.0.1) link below for proof . so i guess it wouldn't work on 5.1.1
img link
http://www.phone-probe.com/wp-conte...63_10205787832278168_2060735319_n-169x300.jpg

Would it be possible to use the ENG kernel to manually install the superuser binary and push the superuser apk to system? Or would that cause the same bootloops also?

We need a working recovery odin file first.

jellybear456 said:
Very informative, pretty much everything I needed to know. If you can't use root apps then I'm sure a lot of users will disregard the files, myself included as I only would like to use said apps. Thanks for the info?
Click to expand...
Click to collapse
As not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1.Updated to newest firmware @Sunderwear posted PB2 (BL/AP/CP/CSC) this will wipe your device. In the pics provided I did try a couple firmware combinations after flashing PB2. I wouldn't suggest this but to each their own.
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-galaxy-s6/general/root-5-1-1-qa-oj7-root-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.
8. After it reboots you have root access.
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
None of this is my work, I just figured out how to get it going on our device. If you want to try it out and your successful thank @metalcated and everyone listed in the thread as they did all the work..
A couple people reported their Knox warranty tripped to 1. So i felt I needed to check if this tripped my own Knox counter. So I'm bootlooped for now but my Knox is 0 !!!! @TechNyne66 and @jrtran I'm posting the instructions on how to do this if you decide to try this method I originally pm'd to you both.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6P using XDA-Developers mobile app

Michael3214 said:
As not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1.Updated to newest firmware @Sunderwear posted PB2 (BL/AP/CP/CSC) this will wipe your device. In the pics provided I did try a couple firmware combinations after flashing PB2. I wouldn't suggest this but to each their own.
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-galaxy-s6/general/root-5-1-1-qa-oj7-root-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.
8. After it reboots you have root access.
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
None of this is my work, I just figured out how to get it going on our device. If you want to try it out and your successful thank @metalcated and everyone listed in the thread as they did all the work..
A couple people reported their Knox warranty tripped to 1. So i felt I needed to check if this tripped my own Knox counter. So I'm bootlooped for now but my Knox is 0 !!!! @TechNyne66 and @jrtran I'm posting the instructions on how to do this if you decide to try this method I originally pm'd to you both. View attachment 3705507
View attachment 3705513View attachment 3705514View attachment 3705515
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Wow that's great information and great news. Thanks! I'm going to give this all a few reads and possibly give it a shot. I'll be sure to inform anyone if I try it and have success. A long process, but I don't mind if I can successfully gain root access and use root apps that may make my battery life a bit better. Thanks again!

@Michael3214 I tried and it works good on G920A, G925A, G928A and N920A. If you have stock firmware for N920A (PB2), please post it. Thanks

If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.

I'm sure somebody much smarter than me has tried already, but could we push a script to set SELinux to permissive upon boot?
http://forum.xda-developers.com/ver...ipt-permissive-selinux-stock-kernels-t2854364

XRange said:
If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.
Click to expand...
Click to collapse
Without access to a pc its a bad spot to be caught in. I ran the "root-Boot.cmd" to recover from the bootloop. The phone hangs on the splash screen for 45 seconds then finishes booting back into android.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
---------- Post added 4th April 2016 at 12:05 AM ---------- Previous post was 3rd April 2016 at 11:57 PM ----------
jrtran said:
@Michael3214 I tried and it works good on G920A, G925A, G928A and N920A. If you have stock firmware for N920A (PB2), please post it. Thanks
Click to expand...
Click to collapse
Here's the link to the firmware.
http://forum.xda-developers.com/showthread.php?t=3331843
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

I have OGG firmware restore and can try different methods if needed. I've tried a few with no success. But am able to recover from bad flashes. Willing to test anything that doesn't flash recovery or kernel.

XRange said:
If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.
Click to expand...
Click to collapse
Excuse my ignorance if this strikes anyone as a noob question... If my device bootloops I obviously cannot go into download mode... My question is twofold: 1: Is my only recourse to flash firmware via Odin?.. And if so... 2: Will my computer/Odin recognize my phone while it is in bootloop?

2Tone23 said:
Excuse my ignorance if this strikes anyone as a noob question... If my device bootloops I obviously cannot go into download mode... My question is twofold: 1: Is my only recourse to flash firmware via Odin?.. And if so... 2: Will my computer/Odin recognize my phone while it is in bootloop?
Click to expand...
Click to collapse
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.

TechNyne66 said:
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.
Click to expand...
Click to collapse
And this works if you're caught in a bootloop, correct? Also, the I have the files for AOJ1 not APB2. there shouldn't be an issue restoring through odin from APB2 to the older AOJ1 because it's still lollipop, right?

can we use this just to debloat and be good?

blane3298 said:
can we use this just to debloat and be good?
Click to expand...
Click to collapse
Yes about all root is good for anyways.
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
jellybear456 said:
And this works if you're caught in a bootloop, correct? Also, the I have the files for AOJ1 not APB2. there shouldn't be an issue restoring through odin from APB2 to the older AOJ1 because it's still lollipop, right?
Click to expand...
Click to collapse
Doesn't matter just don't downgrade firmware or flash anything but AP in odin.

have you tried this yet?

TechNyne66 said:
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.
Click to expand...
Click to collapse
Thanks for your response... I just want to be clear, while in bootloop I can put my phone into download mode by the usual means?