Develop Bugs

[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.

Firmware for SM-T807P

Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.

Yes sammobile doesnt have firmware yet for snapdragon version

I just found out this tablet just came out to sprint. Which caused cf auto root to fail. Which could also mean it isn't on Sam mobile yet.

Is this a common thing? Does sammobile rarely get them for the Snapdragon variants?

Not sure, when the tab s wifi one came out there was already roms for them.

BDA_Rival said:
Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.
Click to expand...
Click to collapse
well...since u have already tried the worse thing possible which is to flash a fule meant for an exynos device on a qualcom chipset then u might as well try this suggestion since it cant really make things worse at this point & just MIGHT actually work. Instead of using the our cfautoroot attempt to use the tab pro SM-T525 cfautoroot (link below)...i just saw that someone suggested that in another thread but dont know if u have had chance to try it yet. Also....as @edan1979 suggested chainfire is pretty good about creating new root packages if u can get him the files that he requests. If u do get this thing rooted with the file below then please pos back because i have a few files i need from your device if its not too much trouble...thx in advacnce
http://download.chainfire.eu/393/CF-Root/CF-Auto-Root/CF-Auto-Root-picassolte-picassoltexx-smt525.zip
^TAB 10.1 LTE SM-T525 CFAUTOROOT (same chipset except for screen...just might be the magic fix)
on a related note....i have aso been searching for the new qualcom/carrier branded firmware files & culdnt find them on sammobile either so if someone finds the one for sprint or the att/verizon version (SM-T707) then please let me know.
@DUHAsianSKILLZ
Just to be clear...i saw in the other thread that u said the wifi root method worked so i'm wondering what version of the device do u actually own?
@BDA_Rival
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet

I dont even care about root at this point, id rather have my tablet boot up to the stock OS. And I'd rather not fully brick it.

@THEDEVIOUS1 in the other thread I didn't know he had a sprint LTE tab s. I own a WiFi version of the tab s 10.5 inch. Sorry for any confusion.

THEDEVIOUS1 said:
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet
Click to expand...
Click to collapse
so i tried this because why not, already went to a service center and they acted like theyve never seen my issue. before i tried this, i had the binary status saying custom and the kox counter said 0. i flashed this, it was successful finally and my knox counter is at 1 which is fine. it tries to boot up unlike before but restarts saying "Could not normal boot" but i atleast see the splash screen. one question i guess i have is what would happen if i flashed the firmware for th the sm-t525? not that im seriously contemplating but if its the closest, chipset wise, would it work? i dont really care about cellular signal and if i brick it, im probably better off calling sprint with a completely bricked tablet that they wouldnt know was once rooted than one that says custom binary and the knox counter set off.

Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also

THEDEVIOUS1 said:
Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also
Click to expand...
Click to collapse
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?

BDA_Rival said:
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?
Click to expand...
Click to collapse
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username

THEDEVIOUS1 said:
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username
Click to expand...
Click to collapse
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Edit: Got into recovery by holding home button, volume up button, and power but it says "Recovery booting, Recovery is not SEANDROID ENFORCING", not too sure what that means. heres the weird part. after it shows that, the screen starts turning gold within a matter of 15 seconds.
{
"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"
}
Ever seen that before?

BDA_Rival said:
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Click to expand...
Click to collapse
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
@BDA_Rival
U edited your post before I could finish my reply but long story short just leave recovery alone for right now...what u are seeing is most likely due to the different types of screens between the 12.2 & 10.5 so the display driver is causing that problem. No problem on the assistance...that's were all supposed to be here for
Just thought I'd throw this out there since u seem to be able to find your way back home now but maybe if u try the cfautoroot for the P905 12.2 note pro then MAYBE that will root it...just thinking out loud though
http://forum.xda-developers.com/showthread.php?t=1980683&page=24
^NOTE PRO 12.2 LTE P905 CFAUTOROOT (see post #235...just in case u get the guts to try it again good luck)

THEDEVIOUS1 said:
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
Click to expand...
Click to collapse
so i tried root checker, it said no root, i tried installing super su, said no root as well. i guess even though my device status says custom, im not actually rooted i went ahead and tried that CF Autoroot you suggested earlier in Odin and it gave me a boot loop so i flashed TWRP again and now its booting all the way. still says im not rooted so i just dont think its gonna work. If it did, i would have gotten that stuff for you for all your help. thanks for helping out.

Root method for Alcatel OneTouch Conquest 7046t

Looking for any information and help on rooting this device. Thanks in advance.

jslow3 said:
Looking for any information and help on rooting this device. Thanks in advance.
Click to expand...
Click to collapse
I managed to root this device today using king root. The first try failed. I ran it a second time and got it to work. I installed titanium backup which gave a warning that the superuser binary was functional but may cause problems. I installed supersu from the play store and tried to update the binary, which failed, even after a restart. Not sure what that means, perhaps someone more knowledgeable can tell me. I also installed other root apps, SD maid pro and rom toolbox pro, both of which seem to function as they should. I have yet to confirm root with a root checker but I intend to shortly. Hopefully this information will help with further development of this device.

The above listed method works. I did it this morning by fluke. I just tried it thinking it wouldn't work but it did. I have lollipop v 5.0.2 and the kingrooy file I downloaded was from google searching "king root" without apk. Half way down you should see the 4.6 link.
Current version is 4.6x which works on most newer mid grade phones. Then I used kingroot to SuperSU files and setup which I got from Google. Can't remember link but search kingroot to supersu and it should be the first link. Run and reboot enter supersu and update binary. You ready to install root apps, debloat, and customize. Haven't found any customs kernel, ROMs, recovery, or anything so I will be working on that soon. Keep an eye out in the near future. Unregistered user until I finish posting.
sosthenisRR

King root
King root version 4.5.0 works for Alcatel one touch conquest thank you very much. Titanium backup doesn't like the manager and anticipates problems and recommends superSU. I was unable to install the binary normally but haven't tried using the cwm or twerp option. Busybox 26 installed and I'm new to xda and will continue on the subject.

sosthenisRR said:
The above listed method works. I did it this morning by fluke. I just tried it thinking it wouldn't work but it did. I have lollipop v 5.0.2 and the kingrooy file I downloaded was from google searching "king root" without apk. Half way down you should see the 4.6 link.
Current version is 4.6x which works on most newer mid grade phones. Then I used kingroot to SuperSU files and setup which I got from Google. Can't remember link but search kingroot to supersu and it should be the first link. Run and reboot enter supersu and update binary. You ready to install root apps, debloat, and customize. Haven't found any customs kernel, ROMs, recovery, or anything so I will be working on that soon. Keep an eye out in the near future. Unregistered user until I finish posting.
Click to expand...
Click to collapse
Success! thank You

Yep, that method works great. I was looking for a.method to.root this device. The only difference was I used this link to switch from KingRoot to SuperSU
androidmtk.com/replace-kinguser-with-supersu
Thanks for the OP

Does anyone have a link to the stock firmware and or the version of Ono Touch Upgrade for this device?

Need stock rom!!
bmk072 said:
Does anyone have a link to the stock firmware and or the version of Ono Touch Upgrade for this device?
Click to expand...
Click to collapse
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work... netspoof said that i might have not given it superuser permissions ( which i did...when kingroot asked i clicked allow) and titanium backup pro said it failed to get root and that it recommends supersu....i installed superuser from chains sd and tried to update the binaries, but it failed......i notcied that in superuser it said that i had root and it said something about kinguser in superuser...so it bacame clear to me that i need to switch kinguser with superuser...or supersu like titanium backup and this thread suggested
so i followed the directions and found kingroot to supersu on google and let the app "supersu me" do its thing...
while supersume was uninstalling kingroot, and installing supersu....something popped up and asked me if i wanted to delete all the files associated with kingroot...i clicked yes....and thats what i think caused my phone to brick
when it said supersu was successfully installed, i went to the app and successfully updated the binaries...right....well it told me that i should reboot the phone because i just updated the binaries so i clicked the reboot now button that the app offered me and the phone went to reboot....but stayed at the alcatel onetouch screen and all i can access is the recovery mode....in recovery logs it says something about no such file or directory for dev/tty0 or soemthing. it said it again in something about the bootloader....
so i think what happened is when i told supersu me to delete all files associated with kingroot it went ahead and deleted a bootloader file or something....normally i would just reinstall the stock rom but this damn phone is so new there isnt one online anywhere
so anyways....can anyone tell me where to get the stock rom or how to unbrick my phone.....i want to just put the stockrom on an sd card and apply it as an update to restore whatever file that is missing and keeping it from booting up....i was thinking (since i happen to have a duplicate phone) that i could make a backup of the same exact phone in twrp and put it on the sd card, switch it to the bricked phone...recovery mode...apply update from phone storage...and bam...that shoulod work! right?
the only thing is....can you put twrp on this phone yet? there is really no development on it at all
so here are the questions i need answered
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one

mistaweeks said:
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work... netspoof said that i might have not given it superuser permissions ( which i did...when kingroot asked i clicked allow) and titanium backup pro said it failed to get root and that it recommends supersu....i installed superuser from chains sd and tried to update the binaries, but it failed......i notcied that in superuser it said that i had root and it said something about kinguser in superuser...so it bacame clear to me that i need to switch kinguser with superuser...or supersu like titanium backup and this thread suggested
so i followed the directions and found kingroot to supersu on google and let the app "supersu me" do its thing...
while supersume was uninstalling kingroot, and installing supersu....something popped up and asked me if i wanted to delete all the files associated with kingroot...i clicked yes....and thats what i think caused my phone to brick
when it said supersu was successfully installed, i went to the app and successfully updated the binaries...right....well it told me that i should reboot the phone because i just updated the binaries so i clicked the reboot now button that the app offered me and the phone went to reboot....but stayed at the alcatel onetouch screen and all i can access is the recovery mode....in recovery logs it says something about no such file or directory for dev/tty0 or soemthing. it said it again in something about the bootloader....
so i think what happened is when i told supersu me to delete all files associated with kingroot it went ahead and deleted a bootloader file or something....normally i would just reinstall the stock rom but this damn phone is so new there isnt one online anywhere
so anyways....can anyone tell me where to get the stock rom or how to unbrick my phone.....i want to just put the stockrom on an sd card and apply it as an update to restore whatever file that is missing and keeping it from booting up....i was thinking (since i happen to have a duplicate phone) that i could make a backup of the same exact phone in twrp and put it on the sd card, switch it to the bricked phone...recovery mode...apply update from phone storage...and bam...that shoulod work! right?
the only thing is....can you put twrp on this phone yet? there is really no development on it at all
so here are the questions i need answered
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one
Click to expand...
Click to collapse
same thing here, except I can't boot into recovery or download. fflashcustom custom twrp from the aforementioned. still won't boot into recovery, hangs at the alacatel logo. what I did was hold down volume and power til it reboots 3&4 times, than it seems to boot back to a android. I even tried the factory restore and it wouldn't do that either. *shrug* imma hafta do more research and find out wtf. but ya, that should fix your sh*t. also. and haven't found the boost stock rom yet either. it's a custom rom, it's not actually lollipop.

Alcatel Onetouch Conquest 7046t rooting, etc.
jslow3 said:
Looking for any information and help on rooting this device. Thanks in advance.
Click to expand...
Click to collapse
I couldn't find the Alcatel Onetouch Conquest 7046t listed in the list of devices on this site at all, other than in a few posts. Maybe people don't think it's a worthy device to work on? Anyway, enough of that rant, what I would like to contribute here is that I tried using kingroot for my old Motorola xt912 which I had install Dirty Unicorns KitKat ROM on successfully, but lost root on. First it said it couldn't root it, then, after trying again, said it could. I started receiving alerts from Avast staying it has detected viruses, and it seemed to install it's own version of super user, when I already had the one by chain installed.. Which struck me as suspect activity and rose yet more red flags.
I also find it suspect that the users posting here on this thread seem to only be newbies.
Any thoughts or feedback is greatly appreciated. Thanks for reading.
P.S. .. And yes, I am interested in rooting this phone, debloating it, installing custom rooms, etc.

mistaweeks said:
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work...
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one
Click to expand...
Click to collapse
Rusty, it's possible that the reason your phone bricked is that it was not fully/properly rooted in the first place. So when SuperSu tried to Un-kingroot it, something went terribly wrong. By the way, had you remembered to turn Developer Options on and set USB Debugging on before running the KingRoot app?
Anyway, there are a couple of options to easily unbrick since you have an identical device.
Note that you can't unbrick by installing TWRP or CWM on your working device, then flashing the bricked device, UNLESS you already have the same custom recovery installed on the bricked device and can boot into that recovery. These recoveries do not provide their backups as a flashable zip, nor are they compatible with each other, which is why you need the identical custom recovery on the bricked phone.
Here is how you can unbrick your device. Go to Alcatel's website and download and install their Mobile Upgrade S software - you will find the link in the support tab for most of their models (or use Google to find it). This is the official Alcatel tool that you would use to flash their stock ROMs onto your bricked phone.
That's the easy method. But if you want a learning adventure, let's pull out your working device. Lol. Go ahead and root it with the King Root app. You may have to try several times to get it fully and properly rooted. Make sure you run a root checker app to confirm that it's rooted. Do not use the SuperSu Me utility yet.
Once you've confirmed it's rooted, install busybox. I prefer the Busy Box X app from Rob Nedi over Stericson's.
Ok, so now we want to install the MTK Droid Tools on your computer. On your phone, make sure USB Debugging is still on. Now connect your phone to the computer and let the drivers for the phone automatically install. Once the drivers are installed, run MTK Droid. It should automatically detect your phone. Next select the Blocks Map button. Then save the scatter.txt file it gives you. Make a folder somewhere because you're going to next use SP Flash Tool to backup the ROM from your phone.
Use Google and XDA to learn how to use MTK Droid and SPF. Here's a helpful link:
http://freaktab.com/forum/mtk-based-devices/mtk-phones/13919-some-useful-tools-for-mtk-phones
Once you've installed SPF on your computer and created the ROM_0 readback of your ROM, go back to MTK Droid Tools and let it break the ROM_0 down into all the partitions that are contained in the ROM. You do this on the root.backup.recovery tab of MTK Droid. Select the "To Process File ROM From Flash Tool". Note that during this process, the Tool will give you the option to create the ClowWorkMod recovery for your phone!
Once the ROM partition files are created by MTK Droid, place them in that folder you created. At this point, you can use SPF to flash the stock ROM to your bricked phone. This will unbrick your phone.
(There's an even simpler way to unbrick your phone with SPF. Instead of backing up the entire ROM of your working phone with SPF and then processing that ROM woth MTK Droid, in this case, you will just READBACK the ROM up to the recovery partition and no further. Then do a direct MEMORY WRITE of that partial ROM to your bricked phone. This will unbrick it. But this approach will not allow you to create the CWM recovery.)
Finally, once you've unbricked your phone, you can install either the Flashify or Rashr app on your phone, and use that to flash the CWM recovery image you just made with MTK Droid onto your phone's recovery partition. I usually also flash the boot_patched boot image, which was also created by MTK Droid, to the boot/kernel partition.
Long post, but I wasn't sure if you were up to an adventure. Please note that there is always a risk that you brick your working device if you make a dumb mistake along the way. It's going to be really hard to brick your working phone because you're pretty much just reading from it and not writing anything to it except when you are rooting it....but just be careful. You've been warned. Lol. But I suspect that like me, a bricked device is just a learning challenge. So enjoy.
Don't forget to thank me!
Sent from my Nexus 7 using XDA Free mobile app

I'm not a newbie y
Ya I've been doin this for awhile and have an extensive list of phones I have rooted, debloated, installed custom roms on etc....and I have never had as much trouble with a device as I have with this phone....this pos phone isn't even on their site! I got another phone from boost (same one) And did the same root method....bricked it.....but I still have the one bricked phone....waiting for a stock ROM
Ya man........get a different phone.....

mistaweeks said:
Ya I've been doin this for awhile and have an extensive list of phones I have rooted, debloated, installed custom roms on etc....and I have never had as much trouble with a device as I have with this phone....this pos phone isn't even on their site! I got another phone from boost (same one) And did the same root method....bricked it.....but I still have the one bricked phone....waiting for a stock ROM
Ya man........get a different phone.....
Click to expand...
Click to collapse
Rusty they sent that phone to you special delivery from HELL! They're just testing you, bro. Lol
But seriously, I think if you could somehow get the scatter.txt for the demon (without having to risk rooting and bricking a good one), then it would be possible to use SP Flash to simply read back the ROM of a properly working phone (up to and including the recovery partition) then simply do a direct memory write onto any bricked device. Should wake it up immediately after the flash. The only exception would be if the custpack partition had something really stupid done to it...like someone messing with the buildprop.txt file! That would put it into a head-spinning bootloop.
So the key here for this demon is for someone on this thread to post the scatter.txt file PLUS a working stock ROM. Is there anyone out there who has already successfully rooted who can post a ROM? Or at least post the scatter.txt?
Sent from my Nexus 7 using XDA Free mobile app

CVAngelo said:
Rusty they sent that phone to you special delivery from HELL! They're just testing you, bro. Lol
But seriously, I think if you could somehow get the scatter.txt for the demon (without having to risk rooting and bricking a good one), then it would be possible to use SP Flash to simply read back the ROM of a properly working phone (up to and including the recovery partition) then simply do a direct memory write onto any bricked device. Should wake it up immediately after the flash. The only exception would be if the custpack partition had something really stupid done to it...like someone messing with the buildprop.txt file! That would put it into a head-spinning bootloop.
So the key here for this demon is for someone on this thread to post the scatter.txt file PLUS a working stock ROM. Is there anyone out there who has already successfully rooted who can post a ROM? Or at least post the scatter.txt?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
i tried rooting the new alcatel the same exact way ( usb debugging was enabled both times) and ended up bricking it....i was doing this for my friend...we ended up just going to boost and telling them that there was a defect in the phone they gave him the day before and told them to give him the moto e ( which has so much developement on it its insane)
anyways my friend just gave me the other bricked alcatel one touch conquest and said that if i can fix it i can have it. so i no longer have a duplicate device to work with . can i even flash a stock rom with the original recovery ? im going to try to download the program from alcatels website like you said and see if that works
then if i get it working im going to get the program you were talking about where u said i can make a clockworkmod recovery for it....

CVAngelo said:
Rusty, it's possible that the reason your phone bricked is that it was not fully/properly rooted in the first place. So when SuperSu tried to Un-kingroot it, something went terribly wrong. By the way, had you remembered to turn Developer Options on and set USB Debugging on before running the KingRoot app?
Anyway, there are a couple of options to easily unbrick since you have an identical device.
Note that you can't unbrick by installing TWRP or CWM on your working device, then flashing the bricked device, UNLESS you already have the same custom recovery installed on the bricked device and can boot into that recovery. These recoveries do not provide their backups as a flashable zip, nor are they compatible with each other, which is why you need the identical custom recovery on the bricked phone.
Here is how you can unbrick your device. Go to Alcatel's website and download and install their Mobile Upgrade S software - you will find the link in the support tab for most of their models (or use Google to find it). This is the official Alcatel tool that you would use to flash their stock ROMs onto your bricked phone.
That's the easy method. But if you want a learning adventure, let's pull out your working device. Lol. Go ahead and root it with the King Root app. You may have to try several times to get it fully and properly rooted. Make sure you run a root checker app to confirm that it's rooted. Do not use the SuperSu Me utility yet.
Once you've confirmed it's rooted, install busybox. I prefer the Busy Box X app from Rob Nedi over Stericson's.
Ok, so now we want to install the MTK Droid Tools on your computer. On your phone, make sure USB Debugging is still on. Now connect your phone to the computer and let the drivers for the phone automatically install. Once the drivers are installed, run MTK Droid. It should automatically detect your phone. Next select the Blocks Map button. Then save the scatter.txt file it gives you. Make a folder somewhere because you're going to next use SP Flash Tool to backup the ROM from your phone.
Use Google and XDA to learn how to use MTK Droid and SPF. Here's a helpful link:
http://freaktab.com/forum/mtk-based-devices/mtk-phones/13919-some-useful-tools-for-mtk-phones
Once you've installed SPF on your computer and created the ROM_0 readback of your ROM, go back to MTK Droid Tools and let it break the ROM_0 down into all the partitions that are contained in the ROM. You do this on the root.backup.recovery tab of MTK Droid. Select the "To Process File ROM From Flash Tool". Note that during this process, the Tool will give you the option to create the ClowWorkMod recovery for your phone!
Once the ROM partition files are created by MTK Droid, place them in that folder you created. At this point, you can use SPF to flash the stock ROM to your bricked phone. This will unbrick your phone.
(There's an even simpler way to unbrick your phone with SPF. Instead of backing up the entire ROM of your working phone with SPF and then processing that ROM woth MTK Droid, in this case, you will just READBACK the ROM up to the recovery partition and no further. Then do a direct MEMORY WRITE of that partial ROM to your bricked phone. This will unbrick it. But this approach will not allow you to create the CWM recovery.)
Finally, once you've unbricked your phone, you can install either the Flashify or Rashr app on your phone, and use that to flash the CWM recovery image you just made with MTK Droid onto your phone's recovery partition. I usually also flash the boot_patched boot image, which was also created by MTK Droid, to the boot/kernel partition.
Long post, but I wasn't sure if you were up to an adventure. Please note that there is always a risk that you brick your working device if you make a dumb mistake along the way. It's going to be really hard to brick your working phone because you're pretty much just reading from it and not writing anything to it except when you are rooting it....but just be careful. You've been warned. Lol. But I suspect that like me, a bricked device is just a learning challenge. So enjoy.
Don't forget to thank me!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
strike the alcatel mobile upgrade S off the list of possibilities...
first of all.... the alcatel onetouch conquest 7046t is not even listed in supported devices, and when i downloaded/ installed mobile upgrade to my windows computer it said " pick your device " and it wasdnt listed in the dropdown menu there either
i still tried selecting the 7047 , because it was closest to 7046, and tried to run the program and it just said it was scaning my device for an ungodly amount of time
so im looking for other methods

mistaweeks said:
strike the alcatel mobile upgrade S off the list of possibilities...
first of all.... the alcatel onetouch conquest 7046t is not even listed in supported devices, and when i downloaded/ installed mobile upgrade to my windows computer it said " pick your device " and it wasdnt listed in the dropdown menu there either
i still tried selecting the 7047 , because it was closest to 7046, and tried to run the program and it just said it was scaning my device for an ungodly amount of time
so im looking for other methods
Click to expand...
Click to collapse
Uh oh! I think I see the problem here. The Conquest runs a QUALCOMM chip! All along, I've been running with the assumption that this Alcatel was running the MTK chipset. Everything I've described here is thus for naught! Those tools, like SPF and MTK Droid, only work with phones that use the MTK platform. They will not even recognize the Conquest.
My sincere apologies, but I don't even know what tools would even work with this sucker. Oh my God... I'm beside myself with embarrassment...I can't believe I made such a serious mistake.
Sent from my Nexus 7 using XDA Free mobile app

Root Alcatel conquest 7046t
Kingroot rooted mine

can the phone work with GSM sim card. i have one piece which is locked i guess coz am overseas and it doesn't work says invalid simcard

Mcrome1018 said:
Kingroot rooted mine
Click to expand...
Click to collapse
Did you get full root with KingRoot? Do your root apps actually work properly? Please confirm as others have reported that the root with KingRoot did not function properly or with all root apps.
Another question several people have is where to get the flashable stock firmware for this phone?
Sent from my Nexus 7 using XDA Free mobile app

CVAngelo said:
Did you get full root with KingRoot? Do your root apps actually work properly? Please confirm as others have reported that the root with KingRoot did not function properly or with all root apps.
Another question several people have is where to get the flashable stock firmware for this phone?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Mine all works, ad away, root browser etc no clue for firmware though

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?

No access to recovery, cant install TWRP

Gidday
As the thread title says, I can't access recovery on my ZE551ML...
I recently wiped the custom ROM (SuperZen) and installed LP and then MM...all working good, no problems...then rooted and unlocked the bootloader and attempted to install TWRP and now can't access recovery mode...this means that I am unable to install TWRP....have tried to install using the TWRP app but no go...
Also, another issue I am having is trying to copy files to the SDCard...I get a permission problem that I can't get access when I have installed SUPERSU and have rooted the phone and X-plore has root access and so has ES file explorer...

cbrokey said:
Gidday
As the thread title says, I can't access recovery on my ZE551ML...
I recently wiped the custom ROM (SuperZen) and installed LP and then MM...all working good, no problems...then rooted and unlocked the bootloader and attempted to install TWRP and now can't access recovery mode...this means that I am unable to install TWRP....have tried to install using the TWRP app but no go...
Also, another issue I am having is trying to copy files to the SDCard...I get a permission problem that I can't get access when I have installed SUPERSU and have rooted the phone and X-plore has root access and so has ES file explorer...
Click to expand...
Click to collapse
in the general section above , there is a bl unlock modder tool by giovix specifically works only on M , set it up ..use return to stock option, flash boot.img ,then flash recovery.
Then , re unlock the boot loader option ,just in case
Then flash twrp option
Then root option.
You will be fine

timbernot said:
in the general section above , there is a bl unlock modder tool by giovix specifically works only on M , set it up ..use return to stock option, flash boot.img ,then flash recovery.
Then , re unlock the boot loader option ,just in case
Then flash twrp option
Then root option.
You will be fine
Click to expand...
Click to collapse
Thanks for the reply...went through the steps again (did this a couple of times yesterday but musta did sumptin wrong)...anyway, TWRP is up and running...now just have to get Xposed installed...
As I said in the OP I am having problems copying files to my SDcard on the phone...its rooted and X-plore and ES file manager have access to root but each time I try to transfer a file I get an annoying message saying that I cant
{
"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"
}

http://forum.xda-developers.com/showpost.php?p=70079801&postcount=126
^^^
When you say you mighta did sumfink wrong , yup -- you should`ve flashed stock recovery back in the link first ^^^ .
Just thought i`d give you that hint to prevent future probs
The sd card prob i have too but i know mine is driver conflicts which i have to live with , on my spare un-updated lappy with windows 10 , all is fine. Plus share link app allows to and thro to any sd from pc and vice versa ok.
Maybe ,you flash back stock boot.img - recovery with the modder tool . Return to complete MM stock.
See if anything you did was a little something wrong

timbernot said:
http://forum.xda-developers.com/showpost.php?p=70079801&postcount=126
^^^
When you say you mighta did sumfink wrong , yup -- you should`ve flashed stock recovery back in the link first ^^^ .
Just thought i`d give you that hint to prevent future probs
Click to expand...
Click to collapse
Ta :good:
The sd card prob i have too but i know mine is driver conflicts which i have to live with , on my spare un-updated lappy with windows 10 , all is fine. Plus share link app allows to and thro to any sd from pc and vice versa ok.
Maybe ,you flash back stock boot.img - recovery with the modder tool . Return to complete MM stock.
See if anything you did was a little something wrong
Click to expand...
Click to collapse
I have had this problem before but this was months ago when I initially installed SuperZen the custom ROM...I got around it somehow but I am flummoxed if I can remember how now
I need to be able to transfer the Xposed installer to the SDCard so I can flash it...

Ok try the info in ASUS file manager
open file manger , 3 dots , about , help and feedback , 2nd box down
Share link stock ASUS app is a great tool too

timbernot said:
Ok try the info in ASUS file manager
open file manger , 3 dots , about , help and feedback , 2nd box down
Click to expand...
Click to collapse
Tried that but no go...I was able to try it a couple of times and now when I go to the 3 dots menu the 2nd option down has changed and wont allow me to change the settings...
Share link stock ASUS app is a great tool too
Click to expand...
Click to collapse
It looks okay but I have X-plore...does the same thing and works well over the network but still won't let me copy to the SD card...despite trying many things

You really have borked it up, return to stock

timbernot said:
You really have borked it up, return to stock
Click to expand...
Click to collapse
Think I will...seems the easiest way to go...should get this uni assignment out of the way first though :silly:

cbrokey said:
Think I will...seems the easiest way to go...should get this uni assignment out of the way first though :silly:
Click to expand...
Click to collapse
Yup, stop playing with ya phone

timbernot said:
Yup, stop playing with ya phone
Click to expand...
Click to collapse
But its fun

Since the last posts regarding access problem to the SDCard I have since installed the update via sideload and thought that it would get around the problem of access but it hasnt (the FM Radio now works which is a bonus )...my phone is now not rooted and I havent done anything else to it...any help appreciated...
cheers
col

Im facing same recovery problem, unable to install it on my ZE550ML (6.0.1), it flashes fine but it wont go to recovery from bootloader, i can only go into recovery from android using adb command but that too takes me to stock recovery, i dont know why stock recovery comes back lol
EDIT: i found out what i was doing wrong, my bootloader got locked during something nd i didnt knew, unlocked it again nd everything works fine now!

I have now gone beyond the meagre problem of not being able to copy to the SD Card...I attempted to root the phone and now have soft bricked it...I am able to get to a recovery menu of sorts but when I try and sideload using ADB I get "device not found"...have been trawling the web for hours looking for a fix