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.
Related
!!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?
There seems to be an OTA update, and it's 10h.
Still ICS but comes with some bug fixes.
Anyone get their updates yet?
gbssengo said:
There seems to be an OTA update, and it's 10h.
Still ICS but comes with some bug fixes.
Anyone get their updates yet?
Click to expand...
Click to collapse
Bell/rogers/telus?
E971, E970, E973?
Unlocked with freegee?
did you update?
edit: im on rogers e971 and i also disabled/froze the LG update software
Nothing for Telus's E973...
Nothing here....Sastel E973
Have a Rogers E971, woke up to a software update.
Tried to update and was told that I could not due to root, removed root via SuperSU. Ran update again, update seemed to run but then rebooted and got a security error, Boot Certificate (I had unlocked boot loader via FreeGee, couldn't restore the FreeGee backup so decided to give it a go and see what happened).
Anyways, managed to recover via the "How to unbrick your optimus G" thread (http://forum.xda-developers.com/showthread.php?t=2010624), the software update now appears to be applied (at least it's no longer detecting an update but I'm not sure what version the update changed it to so I'm not sure how to check).
Obviously my bootloader is no longer unlocked and my device is no longer rooted. Tried to root again with the same method as before (Korean Batch File) and it no longer works. The device gets to the first reboot and then when it comes back up the cmd window says something about "access denied, is your device rooted?" and "Press any key to continue", at which point it exits.
Just my experience.
jpom18 said:
Have a Rogers E971, woke up to a software update.
Tried to update and was told that I could not due to root, removed root via SuperSU. Ran update again, update seemed to run but then rebooted and got a security error, Boot Certificate (I had unlocked boot loader via FreeGee, couldn't restore the FreeGee backup so decided to give it a go and see what happened).
Anyways, managed to recover via the "How to unbrick your optimus G" thread (http://forum.xda-developers.com/showthread.php?t=2010624), the software update now appears to be applied (at least it's no longer detecting an update but I'm not sure what version the update changed it to so I'm not sure how to check).
Obviously my bootloader is no longer unlocked and my device is no longer rooted. Tried to root again with the same method as before (Korean Batch File) and it no longer works. The device gets to the first reboot and then when it comes back up the cmd window says something about "access denied, is your device rooted?" and "Press any key to continue", at which point it exits.
Just my experience.
Click to expand...
Click to collapse
thanks for the heads-up man
in my opinion:
nope nope nope
also maybe try the latest version of Bin4ry's
http://forum.xda-developers.com/showthread.php?t=1886460
might help
---------- Post added at 11:06 AM ---------- Previous post was at 10:58 AM ----------
http://mobilesyrup.com/2012/12/18/s...rings-stability-and-performance-improvements/
seems this is the update they are talking about
for bell and rogers atm
jpom18 said:
Have a Rogers E971, woke up to a software update.
Tried to update and was told that I could not due to root, removed root via SuperSU. Ran update again, update seemed to run but then rebooted and got a security error, Boot Certificate (I had unlocked boot loader via FreeGee, couldn't restore the FreeGee backup so decided to give it a go and see what happened).
Anyways, managed to recover via the "How to unbrick your optimus G" thread (http://forum.xda-developers.com/showthread.php?t=2010624), the software update now appears to be applied (at least it's no longer detecting an update but I'm not sure what version the update changed it to so I'm not sure how to check).
Obviously my bootloader is no longer unlocked and my device is no longer rooted. Tried to root again with the same method as before (Korean Batch File) and it no longer works. The device gets to the first reboot and then when it comes back up the cmd window says something about "access denied, is your device rooted?" and "Press any key to continue", at which point it exits.
Just my experience.
Click to expand...
Click to collapse
Can you take a couple of pictures with ISO @ Auto to see if they fixed it?
Thanks!
t1mman said:
Can you take a couple of pictures with ISO @ Auto to see if they fixed it?
Thanks!
Click to expand...
Click to collapse
I can do that, is there anything specific that I should be looking for or that you would like to see? I almost never take pictures and have never used the camera on here, I didn't even know that there was an issue.
t1mman said:
Can you take a couple of pictures with ISO @ Auto to see if they fixed it?
Thanks!
Click to expand...
Click to collapse
any work around if we dont want to update yet
I got fed up for I cannot restore the KDZ (Not responding stuff). I tried the hard mode method of using LG's support tool and it downloads a whole ROM! Will keep you posted.
EDIT: Yes you cannot root ATM.
BloodBaron said:
any work around if we dont want to update yet
Click to expand...
Click to collapse
I used Titanium Backup pro to freeze the Software Update app. Seems to take away the notification and no problems thus far.
If you don't have TBpro, you can just slip into the app info in the settings menu and disable it from there. (Settings > Apps > List All, find Software Update, disable.
Freezing is the same as disabling as far as I can tell.
yes and you cannot root atm....LOL!
So its safe to say disable the lg update software?
Sent from my LG-E971 using xda premium
BloodBaron said:
So its safe to say disable the lg update software?
Sent from my LG-E971 using xda premium
Click to expand...
Click to collapse
yes just "Disable" via Settings > Apps > Software Update > Tap Disable.
Not Freeze via any root apps.
So I am gonna suffer from being unrooted ATM but no biggy. Good thing LG (and most manufacturers) has a stock app back-up tool in place of TB.
Absolutely nothing for TELUS OGs.. -_-
For those that are wondering what is in the update (for Bell at least):
Code:
Short description
A software update is now available for the LG Optimus G, and Bell strongly recommends that customers update their device to ensure the best possible experience.
Dates
Start date: Tuesday, December 18, 2012
Description
Software update version [V10h] includes device improvements to stability and performance including:
•Google security patch
•Improved touch response while charging
•Fixed exchange email setup to avoid customer confusion
Procedure
Has anyone successfully backed up su by copying it to various directories before updating?
I've put a copy in /system/etc, /system/bin, /data, /data/data, & /cache. I'm hoping one of those will still be there after the update.
Problem for me right now is no update is showing up when I check.
Anyone wanting to try doing this backup make sure you copy the su binary with the - p flag to keep setuid/setgid. I'd also recommend renaming the backup to something other than 'su'.
xxbeanxx said:
Has anyone successfully backed up su by copying it to various directories before updating?
I've put a copy in /system/etc, /system/bin, /data, /data/data, & /cache. I'm hoping one of those will still be there after the update.
Problem for me right now is no update is showing up when I check.
Anyone wanting to try doing this backup make sure you copy the su binary with the - p flag to keep setuid/setgid. I'd also recommend renaming the backup to something other than 'su'.
Click to expand...
Click to collapse
IMHO, the software update wipes /system and /cache (not /data in my experience) so everything you put in those directories will be wiped out. Those SU files though are in the zip if you used Bin4ry's rooting tool, and you can download it from androidsu.com (just unzip these files and you should be able to see them).
jpom18 said:
I can do that, is there anything specific that I should be looking for or that you would like to see? I almost never take pictures and have never used the camera on here, I didn't even know that there was an issue.
Click to expand...
Click to collapse
Something collorfull with not much lights, to see if it gets a grainy feel like this (with AutoISO)
{
"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"
}
or colourfull clean image like this (with Manual Iso)
Thanks!
gabby131 said:
IMHO, the software update wipes /system and /cache (not /data in my experience) so everything you put in those directories will be wiped out. Those SU files though are in the zip if you used Bin4ry's rooting tool, and you can download it from androidsu.com (just unzip these files and you should be able to see them).
Click to expand...
Click to collapse
The problem is that some people are reporting that Bin4ry's recovery exploit is no longer working after the update.
Hey everybody,
I've researched this topic for days and I'm not coming up with any good solutions here.
Essentially, I am trying to figure out what the best firmware as of current date that runs really well on the Samsung Galaxy SPH-D700 Epic 4G.
I'm on 2.3.6 currently and from what I know the latest firmware for Android is 4.3 Jellybean. Is Jellybean available for the SPH-D700? If so, does it run well? If not, what's the next best alternative?
How do I root this phone using a Macbook Pro? I've read about "Wine", "Wine Bottler", "Heimleter" ( I don't think that's how it's spelled but I'm sure some of you know what I am talking about )
From what I have read, Wine doesn't seem like it's going to be very effective. Heim is more of a manual root which I could do but there isn't really a straight forward set of directions. The directions I've found have been written by many different sources and neither of them are the same.
If anybody has suggestions, I would greatly appreciate some. This will be the officially the 2nd phone I've ever rooted, the first being an HTC Hero and my 2nd droid phone ever owned.
DarkXShadowX21 said:
Hey everybody,
I've researched this topic for days and I'm not coming up with any good solutions here.
Essentially, I am trying to figure out what the best firmware as of current date that runs really well on the Samsung Galaxy SPH-D700 Epic 4G.
I'm on 2.3.6 currently and from what I know the latest firmware for Android is 4.3 Jellybean. Is Jellybean available for the SPH-D700? If so, does it run well? If not, what's the next best alternative?
How do I root this phone using a Macbook Pro? I've read about "Wine", "Wine Bottler", "Heimleter" ( I don't think that's how it's spelled but I'm sure some of you know what I am talking about )
From what I have read, Wine doesn't seem like it's going to be very effective. Heim is more of a manual root which I could do but there isn't really a straight forward set of directions. The directions I've found have been written by many different sources and neither of them are the same.
If anybody has suggestions, I would greatly appreciate some. This will be the officially the 2nd phone I've ever rooted, the first being an HTC Hero and my 2nd droid phone ever owned.
Click to expand...
Click to collapse
v4.3 isn't released yet, that I'm aware of, but v4.2.2 is released and stable (mostly).
For most yes it does run well, but for me JB roms and my list of apps installed leaves ~3-9MB of RAM remaining. So that causes crazy lag and is incredibly annoying. You basically have to try it out yourself with your apps and decide if it'll work for your needs.
You can use Odin (in Windows via bootcamp), or Heimdall (in Linux and possible OSX).
nikon120 said:
v4.3 isn't released yet, that I'm aware of, but v4.2.2 is released and stable (mostly).
For most yes it does run well, but for me JB roms and my list of apps installed leaves ~3-9MB of RAM remaining. So that causes crazy lag and is incredibly annoying. You basically have to try it out yourself with your apps and decide if it'll work for your needs.
You can use Odin (in Windows via bootcamp), or Heimdall (in Linux and possible OSX).
Click to expand...
Click to collapse
I don't have a Windows via bootcamp. I deleted that from my Mac last year. Is 4.2.2 available for the Epic 4G?
Do you have any good sources for how to root the Epic 4G from 2.3.6 to 4.2.2? It's been quite a long time since I've rooted. Thanks.
I would like to get my phone to be all set up with this.
http://forum.xda-developers.com/showthread.php?t=2131117
Well rooting or flashing a custom rooted rom is easy, if you can use Odin in Windows. I'm not familiar with Heimdall enough to give you a tutorial.
I posted this in a thread halfway down page 1 of Q/A:
nikon120 said:
TWRP: Flashes through CWM; OR you can pull the recovery.bin file from the zip file and flash that in Odin.
Root:
Power down device
Open keyboard, press and hold both the 1 key and power button. This places the phone into download mode.
Plug the device into your computer, and most likely drivers will install. Allow that to finish before proceeding.
Within Odin, wait until you see COM and a port number appear. That means your phone is recognized.
Next, uncheck all boxes on the left side, including auto-reboot.
Place the victory_8G_100528.pit file in the PIT box. Place CWM v5.0.2.7 .bin/.tar/.md5 file in the PDA box.
Click start and will complete relatively quickly.
Disconnect the phone from USB and pull the battery out.
Replace battery.
Press and hold Vol down, Camera and Power buttons until the capacitative lights light up, then release. This will place you in recovery mode.
From there you will boot into CWM, where you can flash whatever you want (custom rom or a compatible kernel for FC09 & SuperSU) off the SD card. So place those files prior to doing all the above.
Keep in mind, that if you want to remain on stock FC09, but rooted, you will need to flash a custom kernel. The stock kernel will replace CWM with stock recovery every time. That is why in the list above you must disable auto-reboot and battery pull.
All files are in my devhost, in my signature. If not, then they expired and I can reupload them if notified.
Click to expand...
Click to collapse
Just flash Avatar rom from your SD card when booted into CWM v5.0.2.7. Typically when coming from stock, you will be rebooted into a newer version of CWM that is MTD compatible and have to go through the same flashing steps as you just performed to flash Avatar. If you are still on the same CWM version (5.0.2.7), then you need to manually flash either TWRP (2.6.0.0 is current) or CWM (6.0.3.2 is current) before attempting to flash Avatar again.
Unfortuantely, Odin doesn't work for mac. Wine/Wine Bottler is extremely unpredictable. All I need is a way to root my Sph-D700 using the latest version of Mac OS without Windows via dualboot.
Heimdall seems to be the best solution but to be honest, I don't quite understand the procedure. I tried to do it earlier and I didn't have any luck. Since I'm posting this from my phone currently, I'll post the sources I tried in a bit when I jump back on the computer.
Here are the sources I have been trying to use:
http://wiki.cyanogenmod.org/w/Install_CM_for_epicmtd
http://www.glassechidna.com.au/products/heimdall/
http://www.youtube.com/watch?feature=player_embedded&v=1ILk3Dlo9Gg
Here are the steps I've tried taking.
1st Step: I download DRockStar's ClockworkMod Recovery
{
"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"
}
2nd Step:
I download Heimdall Suite 1.4RC1 Command-line Binary:
Place the libusb-1.0.0.dylib library from the zip inside /opt/local/lib on the machine.
I don't know where this folder is on my Mac. I've searched for it and it doesn't exist and it also doesn't specify where I should create it if necessary.
Building From Source: The source code for the Heimdall Suite is available on Github. For more details about how to compile the Heimdall Suite, please refer to the README provided on Github or refer to the instructions to Install and compile Heimdall.
I don't quite understand how to do this earlier. I'm pretty familiar with xCode since I am being taught how to use it from my University. Even with that being said, I'm still not understanding exactly how to build it from the source. I read through the read me and it seems a bit more advanced than what I know how to do. Even with following instructions, it's very confusing to follow.
Booting the phone into download mode is a given to me.
This doesn't relate to me since I am using a Mac.
Number 4: Place DRockStar's ClockworkMod Recovery file into the Heimdall directory.
I'm not sure exactly what this is asking to be honest.
Putting phone into download mode....
Here's what I type into Terminal. I've tried with and without Sudo and I always get the same error.
Also, Heimdall version 1.40 doesn't even recognize my device.
I also tried selecting the Avatar zip from the sd card from going into "Apply update from sdcard" and I got the following error.
This is where I am basically stuck at. I'm not sure what else to do honestly.
DarkXShadowX21 said:
This is the tar file I downloaded:
Zedomax Epic Touch Kernal v3.
Click to expand...
Click to collapse
Don't use that file. It's for the D710, aka Epic Touch.
Sent from my Nexus 7 using Tapatalk 2
nikon120 said:
Don't use that file. It's for the D710, aka Epic Touch.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Which file should I be using? I updated my last post with a bunch on information by the way.
To anyone else following this, I have responded on the Github issue:
https://github.com/Benjamin-Dobell/Heimdall/issues/149
DarkXShadowX21 said:
Hey everybody,
I've researched this topic for days and I'm not coming up with any good solutions here.
Essentially, I am trying to figure out what the best firmware as of current date that runs really well on the Samsung Galaxy SPH-D700 Epic 4G.
I'm on 2.3.6 currently and from what I know the latest firmware for Android is 4.3 Jellybean. Is Jellybean available for the SPH-D700? If so, does it run well? If not, what's the next best alternative?
How do I root this phone using a Macbook Pro? I've read about "Wine", "Wine Bottler", "Heimleter" ( I don't think that's how it's spelled but I'm sure some of you know what I am talking about )
From what I have read, Wine doesn't seem like it's going to be very effective. Heim is more of a manual root which I could do but there isn't really a straight forward set of directions. The directions I've found have been written by many different sources and neither of them are the same.
If anybody has suggestions, I would greatly appreciate some. This will be the officially the 2nd phone I've ever rooted, the first being an HTC Hero and my 2nd droid phone ever owned.
Click to expand...
Click to collapse
Have you tried using heimdall and the instructions found here?
I've recently bought this tablet for storing books and such for school and such that I won't have to carry around an extra 10 kilograms in my backpack. The Ematic Genesis Prime is a very basic Android Tablet that you would most probably find on eBay, Alibaba, etc. I've been trying to find if rooting was possible on this device. I've heard this saying - "Everything is possible on Linux", and so was rooting this tablet. While I was browsing around threads, I've found a way, and decided to make this guide, such that everyone who looks for the method will find it easily.
Rooting Guide
To root this tablet, we will be using Cydia Impactor -
Cydia Impactor is a GUI tool for working with Android devices. It has features already, but is still very much a work-in-progress.
Right now, its key feature is an end-to-end exploit of the Android "Master Key" vulnerability, allowing a user to obtain root access on many Android devices (including Glass and TV).
- http://www.cydiaimpactor.com
Click to expand...
Click to collapse
I have done this method of rooting on my EGS004-BL. It should most work for other colours. (-BL or anything after the - dash is your colour, so in my case, it is black. ) It would most probably work for the other variants such as EGS102 (Genesis Prime XL), and EGW004 (Waterproof version of the EGS004).
Before you start:
I am in no way, shape or form, responsible for the outcome, positive or negative, of you following the provided instructions on this thread.
It worked for me, but that does not mean it will 100% work for you.
You are responsible for any side effects and damage caused to your device, your property, anyone nearby, or yourself, which includes, but not limited to, robbery, riots, injury, death, acts of god, epidemics/pandemics, natural disasters, government shutdowns, mutations, growing an extra arm or any limb, etc.
Rooting will void your warranty.
Preparing to Root
First, you will need to download the program from its website. The download links are in bold letters so it should stand out. The website is at http://www.cydiaimpactor.com
Once the download has finished, extract the .ZIP file onto your Desktop (or whichever folder you like).
Now, move over to your tablet. Hit the settings icon from your desktop or app drawer. Go to { } Developer Options.
One you're there, make sure that the options are on with the 'switch' on the top right corner of the screen. If not, tap it and turn it on.
Once the Developer Options are set to ON, check off USB debugging. Tap OK when the "Allow USB debugging?" window pops up. Screenshot:
{
"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"
}
Rooting
Using the USB cable, connect your tablet to your computer. Then, go to the place where you extracted Cydia Impactor and open it.
Once Cydia Impactor is open, click on USB and then Driver Scan. If you are asked to select which device/port, chose the right one and hit OK/Yes. Wait until it installs the drivers. NOTE: You may be asked to reboot your computer. If so, reboot first, then continue to the next step. Screenshot:
Once that's done, click Start in Cydia Impactor. DO NOT CHANGE THE TEXT IN THE TEXT BOX. It should try to root the tablet with the methods that it has in store. Wait until it roots your tablet.
Once it says it successfully rooted your tablet, reboot it for safety's sake. (You don't have to, but just do it anyways).
After your tablet has started up, open up Play Store and download a Superuser program. I personally like Chainfire's SuperSU.
After installing a Superuser program, it may ask you to update the SU binary. Please hit OK/Yes and let it update.
That's it! Your tablet has been (or should be) rooted! If you want to check, you can download Root Checker from the Play Store.
CWM Recovery
@dolorespark has created CWM Recovery for A10/A13 Tablets. The EGS004 is an Allwinner A13 Tablet so use the A13 version of it.
It's here: http://forum.xda-developers.com/showthread.php?t=2189640
Custom ROMs
There is an unofficial CyanogenMod 10 for the tablet (meant for generic A13 tablets) available at: http://forum.xda-developers.com/showthread.php?t=2343531
Known Issues
- On EGS 102 (XL PRIME), Cydia Impactor will report an unsuccessful root job, but will actually root the tablet. (Thanks to @oldsoldier2003)
Hit the thanks button if I've helped you. If you ran into troubles, have suggestions, or just want to say that it worked, please don't hesitate to reply.
Finally!!!
Hey thank you so much...I Testify that this rooting is 100% safe and successful on my EGS004-bl from my experience... i am new here i just register say thanks :good: :laugh::laugh:
One small issue noted on the EGS 102 (XL PRIME). Impactor didn't report a successful root job, but did indeed root the tablet. Thanks for the quick guide and pointing out this tool.
as i am used to rooting name-brand android devices...this actually works, and quite easier than galaxy devices...my wife got this for me...we dont have a lot of money so couldnt get a nexus...its a little slow responding, but hopefully there is a rom that can speed it up...but this works quick and easy and don't even have to copy files over...thanks...
It may be awhile before you can find a ROM for it because most of the talented devs are quite busy on other devices that are more popular. It is my hope that these devices become a little more popular and get some love here too
Sent from my EGS102 using XDA Premium HD app
oldsoldier2003 said:
It may be awhile before you can find a ROM for it because most of the talented devs are quite busy on other devices that are more popular. It is my hope that these devices become a little more popular and get some love here too
Sent from my EGS102 using XDA Premium HD app
Click to expand...
Click to collapse
There's an unofficial ROM - http://forum.xda-developers.com/showthread.php?t=2343531
recoveries
Has anyone found a recovery for this tablet yet or one that is comparable,so we can back up and restore them if something gets fubared
ed196741 said:
Has anyone found a recovery for this tablet yet or one that is comparable,so we can back up and restore them if something gets fubared
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2189640
There^
Also updated on the OP. (Thanks for the reminder, it's been here for a while, just didn't get around to adding it )
Thanks, now I have some more questions !
We recently purchased a EGS114 its a Ematic Genesis 2 , we used your guide to root it and it worked out great, thanks! Now what do i do, basically I'm saying this is brand new to me, I've put Nova Settings on there and it made it look better, have the Superuser chain fire, but really kinda at a loss of what to do. I understand this might be in the wrong location but I cannot find any information on these tablets, this is the sole reference to the Ematic series i have found and one you tube video showing gibberish. What i would like to do / plan is Ive seen videos on making your external SD card your internal so i can have more app space - Have a 32gb Micro SD Card in route, plan on partitioning it and all really no idea but you tube helps. Secondly saw on how to use the sd card for your Ram to speed up applications plan on trying that. Also I've been trying to overclock the CPU but cant, I believe i need to change the kernel or ROM something or other, i have no idea how to do this??? Well that's some of what i believe is possible with this device if you guys could help me out i would really appreciate it . Try not to bash to hard on the new user that i am i apologize in advance.
:fingers-crossed:SweetAction
SweetAction said:
-snip-
Click to expand...
Click to collapse
Looking to do the same! If you find links, mind posting here, or making a how-to comment? would love to do more with this thing!
PS: in Linux, simply running Impactor after extracting it wasn't doing it for me, I had to hop in terminal and run it as su (sudo ./Impactor, after navigating to the folder). It then ran just fine, with no problems. Ends up I needed the adb server to be started as root(sudo adb start-server as opposed to adb start-server), otherwise it gave me the finger - aka ????????? - no permissions.
SweetAction said:
We recently purchased a EGS114 its a Ematic Genesis 2 , we used your guide to root it and it worked out great, thanks! Now what do i do, basically I'm saying this is brand new to me, I've put Nova Settings on there and it made it look better, have the Superuser chain fire, but really kinda at a loss of what to do. I understand this might be in the wrong location but I cannot find any information on these tablets, this is the sole reference to the Ematic series i have found and one you tube video showing gibberish. What i would like to do / plan is Ive seen videos on making your external SD card your internal so i can have more app space - Have a 32gb Micro SD Card in route, plan on partitioning it and all really no idea but you tube helps. Secondly saw on how to use the sd card for your Ram to speed up applications plan on trying that. Also I've been trying to overclock the CPU but cant, I believe i need to change the kernel or ROM something or other, i have no idea how to do this??? Well that's some of what i believe is possible with this device if you guys could help me out i would really appreciate it . Try not to bash to hard on the new user that i am i apologize in advance.
:fingers-crossed:SweetAction
Click to expand...
Click to collapse
indestructibleguy said:
Looking to do the same! If you find links, mind posting here, or making a how-to comment? would love to do more with this thing!
PS: in Linux, simply running Impactor after extracting it wasn't doing it for me, I had to hop in terminal and run it as su (sudo ./Impactor, after navigating to the folder). It then ran just fine, with no problems. Ends up I needed the adb server to be started as root(sudo adb start-server as opposed to adb start-server), otherwise it gave me the finger - aka ????????? - no permissions.
Click to expand...
Click to collapse
Sorry for the VERY late reply. My xda account is currently hooked up to my gmail which I don't really check anymore because I have my own domain name & an email address on that.
Regarding the overclocking issue:
Yes, you cannot overclock this device. Mine came underclocked actually - NoFrills CPU Control was showing 1.008 GHz instead of the claimed 1.5 . I was able to bump the value up to 1.2 before the app would crash after hitting 'Apply'.
There is an unofficial CM Rom for this tablet - http://forum.xda-developers.com/showthread.php?t=2343531
(I tried flashing this but I derped and now the tablet itself is bricked and there's no way I know to fix it other than buy another one, which I won't do.. I probably forgot to clear the cache which is why I bricked it).
I believe you can overclock after installing that ROM (unless it already does it for you).
SweetAction said:
We recently purchased a EGS114 its a Ematic Genesis 2 , we used your guide to root it and it worked out great, thanks!
Click to expand...
Click to collapse
I have a quite recent EGS114 and it's a substantially different tablet than the EGS004, having an ARMv7 CPU, more RAM & memory, etc.. I am wondering if this model number has been recycled with a different tablet and the EGS114 you got is different than mine -- and if this root procedure will still work.
The original message is quite old and the graphics are 404ed out.
If anyone has any suggestions for rooting this unit, I'd be grateful:
Model: EMatic EGS114
CPU: ARMv7
Android: 4.0.4 ICS
Kernel: 2.6.34
Does anybody know if this works on the Ematic EDG103?
I too have got the EMatic EGS114/ Android: 4.0.4 ICS/ Kernel: 2.6.34. Purchased from TigerDirect.
The current memory {RAM allocated} is poor for APPS. Not sure what to do with this tablet. .
Any success on rooting the tablet ?
JohnLNU said:
I have a quite recent EGS114 and it's a substantially different tablet than the EGS004, having an ARMv7 CPU, more RAM & memory, etc.. I am wondering if this model number has been recycled with a different tablet and the EGS114 you got is different than mine -- and if this root procedure will still work.
The original message is quite old and the graphics are 404ed out.
If anyone has any suggestions for rooting this unit, I'd be grateful:
Model: EMatic EGS114
CPU: ARMv7
Android: 4.0.4 ICS
Kernel: 2.6.34
Click to expand...
Click to collapse
Judging by the last comment (on the OP's post), this looks like it works on the EGS102 as well?
No Volume Buttons
Hello all,
I have gotten as far as getting CWM onto my EGS004, but I have arrived at a problem: the EGS004 does not have volume up/down buttons, so I have no way of doing anything in the recovery menu. Is there something I am missing, because I can't find a way to navigate the menu in CWM via touch.
thexfactor04 said:
Hello all,
I have gotten as far as getting CWM onto my EGS004, but I have arrived at a problem: the EGS004 does not have volume up/down buttons, so I have no way of doing anything in the recovery menu. Is there something I am missing, because I can't find a way to navigate the menu in CWM via touch.
Click to expand...
Click to collapse
Just attach an USB keyboard to the tablet, but don't bother, I flashed that custom firmware on my laptop and now it is bricked and I'll need to figure out a way to boot into CWM without using adb or the volume button. Oh well
biscoito1r said:
Just attach an USB keyboard to the tablet, but don't bother, I flashed that custom firmware on my laptop and now it is bricked and I'll need to figure out a way to boot into CWM without using adb or the volume button. Oh well
Click to expand...
Click to collapse
I figured another method out: there is a tiny pin-reset button hole above the USB port on the left. This can be pressed with a paper clip to cycle through menu items in the recovery. I haven't tried, but I'll bet you could boot into recovery by holding power+pin-reset.
thexfactor04 said:
I figured another method out: there is a tiny pin-reset button hole above the USB port on the left. This can be pressed with a paper clip to cycle through menu items in the recovery. I haven't tried, but I'll bet you could boot into recovery by holding power+pin-reset.
Click to expand...
Click to collapse
The pin-reset method you mention did not work, and I didn't a make a livesuit suitable backup before I flashed my tabled. I only backed up using CWM and they are not compatible with each other. Would you mind uploading a rom dump of you tablet so I can try to make a flashable rom in order try to save my tablet ? I found these instructions on how to do it http://www.imajeenyus.com/computer/...et/android/livesuit_creating_final_image.html
Hi, i have an ematic egs114 and i want to install a cwm recovery but i dont know which one i have to install and since it wont boot i dont know how to figure it out either, can anyone helpme please????
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?