Database Users

[Q] soft Bricked with twrp recovery

Ok today I rooted my lg g2 installed twrp all fine. Then I decided to install the new kit kat Rom. All ready to go went to wipe everything to start a clean install then stupidly wiped the internal storage too. So can't restore back up and can't install the blasted Rom. Phone will get as far as the lg logo. I can get into recovery but usb mounting doesn't work and Adb sideload will not start. If I try to use Adb push it says nothing is attached. Odd thing is the storage left being reported in twrp is just over 10 gig and it is a 16 gig phone so I thought it should be more. I know if it is booting into recovery there is hope but I'm stumped . Any help would be greatly appreciated.

darrenmdr said:
Ok today I rooted my lg g2 installed twrp all fine. Then I decided to install the new kit kat Rom. All ready to go went to wipe everything to start a clean install then stupidly wiped the internal storage too. So can't restore back up and can't install the blasted Rom. Phone will get as far as the lg logo. I can get into recovery but usb mounting doesn't work and Adb sideload will not start. If I try to use Adb push it says nothing is attached. Odd thing is the storage left being reported in twrp is just over 10 gig and it is a 16 gig phone so I thought it should be more. I know if it is booting into recovery there is hope but I'm stumped . Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try to flash your variant older ROM/radio . 16GB phone should have around 11-12GB as free

TWRP OTG to load rom
I was using the d80010d_to_20c.zip firmware + SuperSu.zip + TWRP 2.7.0.0.zip.
i.e. "kitkat" with a custom recovery and root.
I had only the 3 above zips on the phone.
d80010d_to_20c.zip contains the kk_system and a custom kk_kernel, no bootloader.
The bootloader came from the LGFlashTool and a d80010d.tot file on my laptop.
After taking the April 8 OTA from AT&T, my phone was stuck in recovery.
Could not get into download mode or use ADB.
I made the mistake of wiping my phone hoping to get download mode to work.
I should have used the terminal in TWRP and typed:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
which has been reported to work. After wiping the phone it was too late for this.
I was stuck in TWRP 2.7.0.0 which has OTG capability, so I loaded a usb flash drive with d800_Kitkat.zip,
connected it to my phone via an OTG cable, and copied d800_Kitkat.zip to the sdcard using TWRP.
Then flashed it using TWRP. I also flashed SuperSU.zip before booting to system. I'm back to stock Kitkat + root.
I'm hoping someone with Kitkat + root reports whether the April 8 AT&T OTA works on a rooted phone.
We know it fails badly on a custom recovery phone with Jellybean bootloader/custom Kitkat kernel/Kitkat system.
AT&T claims that it just updates Google+, Google Wallet, and makes Google Hangouts the default messaging app
which sounds safe but isn't.

if you can get in recovery then you should also be able to get into donwload mode. Have you tried flashing a kdz for your phone through the lg flash tool?
Sent from my TF701

{
"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"
}
I can confirm root on AT&T new ota is fully functional. No problems thus far. I haven't tried a custom recovery yet though
Edit. Can confirm xposed is working as well. Has anyone with the new ota and root tried this yet? http://forum.xda-developers.com/showthread.php?t=2715496
Sent from my LG-D800 using Tapatalk

Thanks for replies been trying all day and can't pc to even recognise phone. Goes into download mode but no Adb or sub connectivity think it's drivers so trying on different pc .

[QWondarrenmdr;51867286]Thanks for replies been trying all day and can't pc to even recognise phone. Goes into download mode but no Adb or sub connectivity think it's drivers so trying on different pc .[/QUOTE]well not a lot of hope all the kdz files failed tried using Adb sideload no dice. Giving up for today will try again t I tomorrow

ok now this is getting silly. I managed eventually by using Koush's drivers to get adb to work and got cm11 working. Whoopee at least the phone works. So I make a backup. then wipe remembering this time to check the backup works. Then install new 4.4 rom. Restarts but then the touch screen input is all over the place so I can't get anything to work. Ok fine go back to recovery and restore from backup.
But noooooooooooo:crying: The flipping TWRP Recovery has gone. I can get as far as the phone saying it is going to install TWRP and reboot, but it doesn't and doesn't. The KDZ files I've found don't seem to work and the part on the lg support tool that starts updating the phone after you have changed to Korean does zip zilch nada. I can get into download mode.
So is there a CM or lightweight kdz file I can try rather than these 2 gig monstrosities?
Any idea why R and D Test tool doesn't work? I've followed instructions and videos?
Why do I do this every time I get a new phone, it was fine I could have waited but no I had to go and tinker
I know this is fixable because I can get into a software installation but I am stumped at the moment.
Any sort of help or pointing to other tutorials would be greatly appreciated.

fixed
Wow what a kerfuffle. After all that I am back to a stock 4.2 Rom with bloat but I don't care the thing works.
All that was wrong was a # in the wrong place.
Next time read and read again. It's like carpenters with their measures twice cut once

[Solved] [Q] [4.4] [Nexus 7 2012 3G] Rooting problem: ineffective flashing of superSU

Hello,
I just updated my Nexus 7 2012 3G from 4.2 (unlocked, rooted) to 4.3 manually (fastboot), then 4.4.2 via OTA.
Now I'm trying to root my device again, by flashing SuperSU-v1.80 through CWM interface (recovery-clockwork-6.0.1.9-grouper).
Problem is, even though the SuperSu app appears after flashing it, I get the message
HTML:
no su binary installed and supersu cannot install it
Updating it changes nothing.
I tried to flash again the same file, and now the app simply disappeared. Installing the Play Store app does nothing either. I'm stuck here.
Any idea ?
For reference, after I tried to flash a first time (and it didn't work) I noticed that an incorrect storage size was recognized. So I did a factory reset, got the correct storage size, then tried to flash SuperSu again to gain root, to no avail. So I tried more than twice, with a factory reset inbetween.
Solution
I was just using outdated tools : my version of CWM and SuperSU were both too old to work on 4.4.2
Always get the latest of those two on their respective websites.

OneXdude said:
Hello,
I just updated my Nexus 7 2012 3G from 4.2 (unlocked, rooted) to 4.3 manually (fastboot), then 4.4.2 via OTA.
Now I'm trying to root my device again, by flashing SuperSU-v1.80 through CWM interface (recovery-clockwork-6.0.1.9-grouper).
Problem is, even though the SuperSu app appears after flashing it, I get the message
HTML:
no su binary installed and supersu cannot install it
Updating it changes nothing.
I tried to flash again the same file, and now the app simply disappeared. Installing the Play Store app does nothing either. I'm stuck here.
Any idea ?
For reference, after I tried to flash a first time (and it didn't work) I noticed that an incorrect storage size was recognized. So I did a factory reset, got the correct storage size, then tried to flash SuperSu again to gain root, to no avail. So I tried more than twice, with a factory reset inbetween.
Click to expand...
Click to collapse
Hi, OneXdude...
Due to security changes in KitKat, Chainfire had to re-work the way root worked, so it's probable your rather old SuperSU-v1.80 (which worked with Jellybean) is the cause of the problem...
Try the latest version, SuperSU-v1.93...
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Rgrds,
Ged.

Thanks for the quick reply, GedBlake.
Though it still doesn't work.
Here is what I did :
- Boot into CWM
- Factory Reset
- adb sideload of SuperSU-v1.93
- reboot
- initial setup
- tap on superSU app : "no su binary installed and supersu cannot install it"

OneXdude said:
Thanks for the quick reply, GedBlake.
Though it still doesn't work.
Here is what I did :
- Boot into CWM
- Factory Reset
- adb sideload of SuperSU-v1.93
- reboot
- initial setup
- tap on superSU app : "no su binary installed and supersu cannot install it"
Click to expand...
Click to collapse
Hi, OneXdude...
Try it this way...
** Download SuperSU-v1.93 direct to your Nexus 7 using Chrome or other Android browser.
** Boot into CWM.
** In CWM, select the 'Install Zip' option, followed by 'Choose zip from /sdcard'...
**...and then navigate to the folder where the SuperSU .zip just downloaded to... usually the '/download' folder.
** Flash the SuperSU-v1.93 zip.
** Reboot... and you should be rooted
Rgrds,
Ged.

GedBlake said:
Hi, OneXdude...
Try it this way...
** Download SuperSU-v1.93 direct to your Nexus 7 using Chrome or other Android browser.
** Boot into CWM.
** In CWM, select the 'Install Zip' option, followed by 'Choose zip from /sdcard'...
**...and then navigate to the folder where the SuperSU .zip just downloaded to... usually the '/download' folder.
** Flash the SuperSU-v1.93 zip.
** Reboot... and you should be rooted
Rgrds,
Ged.
Click to expand...
Click to collapse
I followed this exact procedure, but sadly the problem remains.
I still get the error message.

OneXdude said:
I followed this exact procedure, but sadly the problem remains.
I still get the error message.
Click to expand...
Click to collapse
This is very puzzling...
Rooting the Nexus 7 should be a piece of cake... it certainly was for me.
I have to go out for an hour or so... but when I get back, I'll test flash SuperSU-v1.93 on my own Nexus 7 using ClockWorkMod recovery.
Normally, I use TWRP for such things... but I'll see how it goes with CWM and see if I can grab some screenshots and any error messages that may result.
--------------------------
Incidentally, I notice the version of CWM you have installed, is an older version - v6.0.1.9... the latest is v6.0.4.3, and is available from here...
https://www.clockworkmod.com/rommanager
Possibly fastboot flashing a more up to date version of CWM on your Nexus 7 may resolve your problem.
Rgrds,
Ged.

Hi again, OneXdude...
Further to my previous post...
As I've said, I normally use TWRP recovery (TeamWin Recovery Project) for rooting and flashing stuff like Custom ROMs and flashing 'mods' like Xposed framework...but I have used CWM (ClockWorkMod) recovery in the past... so my recollection of how CWM works, as it currently stands, is now a little hazy.
Hunting around on my laptop, I find the earliest version of a copy of CWM I have for the Nexus 7, is v6.0.2.3 with a date/time stamp of 3rd of January 2013!!
Which means your currently installed version of CWM v6.0.1.9 significantly pre-dates that...
...and is very, very out of date!!. Possibly dating it back to 2012.
So, I would strongly recommend you update your version of CWM to the latest version... which is v6.0.4.3.
I suspect, because you're using such an old version of CWM to root, is the probable cause of why your attempts to root have so far failed.
---------------------
Anyway...
I've just test flashed SuperSU-v1.93 on my own Nexus 7 (2012-WiFi ony) model... via CWM v6.0.4.3.
And it largely succeeded... the SU binary was successfully 'pushed' to /system/xbin... the only thing missing was the SuperSU app itself.
I've had this rather peculiar problem before... but it's easily resolved by just installing it from Google PlayStore.
Here is my CWM v6.0.4.3 output listing, when flashing SuperSU-v1.93... and is the sort of thing you should expect to see...
(Apologies for the poor quality of this screen shot... both TWRP and CWM recoveries lack the ability to directly take screenshots, so I had to photograph the screen using my Samsung Galaxy).
{
"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"
}
--------------------------------------------------
So, in conclusion...
I would recommend you update your version of CWM to the latest version... and try flashing SuperSU v1.93 again.
Hope this helps... and good luck.
--------------------------------------------------
EDIT: Additional info...
Just spotted an incongruity/inconsistency in your first post... and which I have higlighted in red.
OneXdude said:
..
...I just updated my Nexus 7 2012 3G...
..
Click to expand...
Click to collapse
...and...
OneXdude said:
..
....by flashing SuperSU-v1.80 through CWM interface (recovery-clockwork-6.0.1.9-grouper).
..
Click to expand...
Click to collapse
-----------------------------------
If your Nexus 7 is 3G capable (and has a SIM card it in it), then you MUST ENSURE you have the correct Custom Recovery installed for your specific Nexus 7 type.
So... not only are you running a very old version of CWM, you're also running an incorrect version of CWM.
-----------------------------------
A 'grouper' Custom Recovery is intended for WiFi only Nexus 7's... like mine, for example.
However, your Nexus 7 is a 3G Nexus 7... and so you need a 'Tilapia' Custom Recovery installed.
For the latest version of CWM for your 3G/GSM device, that would be... recovery-clockwork-touch-6.0.4.3-tilapia.img.
And which you can find here...
https://www.clockworkmod.com/rommanager
...under the title of Google Nexus 7(GSM).
Download to your PC... and fastboot flash it.
Regrds,
Ged.

You were right, I was just using outdated tools to root my Nexus 7. I have it rooted now.
Thanks for your help and time, sorry that it was such an obvious answer.
Regards.

OneXdude said:
You were right, I was just using outdated tools to root my Nexus 7. I have it rooted now.
Thanks for your help and time, sorry that it was such an obvious answer.
Regards.
Click to expand...
Click to collapse
No apologies required... What is obvious to some, may be obscure to others.
You got there in there end... and that's what matters.
But make sure you have the right version of CWM installed (see the edit to to my previous post)... it will matter if you need to perform NANDROID backups.
Rgrds,
Ged.

[Q] Headache : need to update with Stock Recovery without USB port

Hi,
I have a Samsung Galaxy S4 GT-i9505. The micro USB port doesn't work : please don't even ask anything to try to make it work, I just tried nearly everything possible (clean up the port, 4 different PC and OS, all the drivers, KIES or nos KIESS, tried to play with the pins, tons of USB mods, tons of cables...). This USB doesn't work at all (apart from charging!).
I would like to update the phone since I'm stuck with a (stock I think?) 4.2.2 not rooted. :crying:
It seems also that I have only Custom Recovery (no wipe data, dalvik and stuff options at all, just basic stuff like "update from zip"..).
I can copy stuff on my ext CD Card or via AirDroid
=> I heard that i could make an OTA update via Stock Recovery but i can't find any file like that. Like that I could do a "update from zip" from Stock Recovery mode (UP+HOME+ON BUTTON)
=> Do you know where i can find this file ? Or do you have any ideas how I would update my phone ? :highfive::highfive:
Here is an image of what i currently have on my galaxy S4 :
{
"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"
}
[/url][/IMG]

Come on, no one can help ? Stuck forever on my 4.2.2 ? Damn, can't even use some features of my chromecast...

Up...

Ill get back at it.

Thanks, I'm all ears !

Before I begin, trying to OTA in the settings menu doesn't work? Settings > About phone > Software update. What is the error message you are getting?
The problem is as follows:
- Because you don't have a working usb port, it's a lot harder to fix things if it goes wrong.
- You can't upgrade/restore using Odin, because you don't have download mode.
There are a few things you can do. It's up to you what you want. The problem is that if something goes wrong, you will probably be unable to restore without a new usb port.
A.
Root your phone using Towelroot. Install Xposed Framework and then install Wanam Xposed. Open Wanam Xposed and click on "Fake system status". That should give you OTA updates back.
Downside to this method: You will probably be unable to root in the new version. The downside of not having root is that having a custom recovery would benefit you greatly, sinds you can't use download mode. In your case you will need root to flash the custom recovery.
B.
Use a custom rom.
There are a few things you will need to get everything working.
1. You will need root.
2. You will need a custom recovery
3. You need to update your modem (Wifi fix/non-hlos).
1.
Rooting should be possible using Towelroot. It should work on 4.2.2.
2.
After that you can flash a custom recovery true "Terminal Emulator". You can download that app in the market. You can find the instruction on how to flash the custom recovery here. http://teamw.in/project/twrp2/182
That's TWRP recovery, if you want a different one, go ahead just use the instructions.
If you the flashing was succesfull, then make a backup in the recovery.
3.
You need to update your modem so that everything will work on the old bootloader. You need Mobile Odin (probably the payed one) to flash the modem. You need a wifi-fix/non-halos version because you are on the old bootloader.
4.
You can flash any custom rom you want.

Lennyz1988 said:
Before I begin, trying to OTA in the settings menu doesn't work? Settings > About phone > Software update. What is the error message you are getting?
The problem is as follows:
- Because you don't have a working usb port, it's a lot harder to fix things if it goes wrong.
- You can't upgrade/restore using Odin, because you don't have download mode.
There are a few things you can do. It's up to you what you want. The problem is that if something goes wrong, you will probably be unable to restore without a new usb port.
A.
Root your phone using Towelroot. Install Xposed Framework and then install Wanam Xposed. Open Wanam Xposed and click on "Fake system status". That should give you OTA updates back.
Downside to this method: You will probably be unable to root in the new version. The downside of not having root is that having a custom recovery would benefit you greatly, sinds you can't use download mode. In your case you will need root to flash the custom recovery.
B.
Use a custom rom.
There are a few things you will need to get everything working.
1. You will need root.
2. You will need a custom recovery
3. You need to update your modem (Wifi fix/non-hlos).
1.
Rooting should be possible using Towelroot. It should work on 4.2.2.
2.
After that you can flash a custom recovery true "Terminal Emulator". You can download that app in the market. You can find the instruction on how to flash the custom recovery here. http://teamw.in/project/twrp2/182
That's TWRP recovery, if you want a different one, go ahead just use the instructions.
If you the flashing was succesfull, then make a backup in the recovery.
3.
You need to update your modem so that everything will work on the old bootloader. You need Mobile Odin (probably the payed one) to flash the modem. You need a wifi-fix/non-halos version because you are on the old bootloader.
4.
You can flash any custom rom you want.
Click to expand...
Click to collapse
Man, thank you so much. Your explaining are crystal clear. I've been stuck for months without no solution until now. :crying::crying:
So here is what I did :
0. First of all as you asked when i was clicking on "update" to search for some OTA updates i didn't have anything. Absolutely nothing happen : i just click on it wihtout any warning. Please note that before I used to have a typical warning message "your device has been modified..." or something like that
1. I rooted my i9505 wIth towelroot, had to change a code in it because i had a message "your device is not yet supported". It woked after that, i installed SuperSu and RootChecker which are working perfectly. Of course RootChecker is telling me that I am well rooted.
2. I downloaded all the Xposed stuff : framework, update, reboot and also the Wanam Exposed.
3. On Wanam i found the "fake system status" on the "security" part. I did it (several times actually). After the reboots my status was on "OFFICIAL" in android AND in the download mode BUT the Binary Status stay always in "Custom". :silly: So when i try again to update via OTA my phone i doesn't do anything at all, just like before...
=> Then I saw that in this case you have to install TriangleAway to set back the official Binary Status to "officiel" again? Is it this way ?
=> I saw your warnings about the flashing. I think that it's too risky, I'm not very confident and don't want to brick it. I flashed a ROM once but doesn't know anything about wifi flash/non-halos, I doesn't even what that means !
=> But i would love to install a "pure" android 4.4.2 or 5.0, i'm just fed up with touchwizz... So I installed GooImager but unfortuately the servers are down now. So I couln't go any further to install a custom recovery. Could you give me another way and also maybe where to find the wifi/non-halos stuff to flash ? or at least a tutorial ?
Thank you very much? :highfive:

Once again, if you have a little time to help me about my last message.. Thank you in advance

I'm not sure if you need a new rmodem. Just go ahead and flash a recovery true the terminal, that's not really dangerous. Then backup and flash a custom rom that you want. If it works, then it works. If it doesn't work, you can always revert back.

The easier thing to do is replace the USB board. The part is less than £10 and is a piece of piss to fit.

Nope, I aleady tried this. Even with a new USB board it wasn't working.
It's either a bug bad bug on the ROM or a bug on the mainboard. I guess...

[GUIDE] Root OnePlus X without TWRP. No PC needed.

*** Spoiler ****
If you are looking to flash custom ROMs or Xposed Modules, then this is absolutely inappropriate method for you. Installing Xposed without unlocking bootloader is absolutely bad idea it is always safe to unlock bootloader and then do mods and stuff bc if you messed up with it without unlocking, most of the times, it is difficult to clean it. For installing ROMs, Xposed etc., I suggest you should unlock your bootloader, then flash TWRP. The correct way to install ROM is Unlock bootloader -> Flash custom recovery -> Flash rom. Rooting won't help you there. For unlocking bootloader and install TWRP, I suggest you to follow this guide.
Before you start rooting with this method, I suggest you read what KingRoot is in this thread. Bc there are several opinions regarding the KingRoot, do a google search about what actually KingRoot is.
Warning: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try.
Let me get few things straight one by one since there are too many questions targeted to this method.
1. I have posted this method so that people can root OPX without unlocking bootloader.
2. Using ADB via PC needs so much trouble like having drivers and so. Hence I found something pretty easy that will give easy access to root.
4. Kingroot needs internet access to root your device. Though it's safe root with this method.
4. Anyways kingroot will be uninstalled as soon as SuperSu is pushed into the system. :good: :good:
Still anyone has doubts about KingRoot, stop rooting with this method NOW.
Once you root your phone with this method, you will not be able to install OTAs directly. However there is a way out to install OTAs at the bottom of this post.
Precaution: Make sure your phone has enough charging to make things proceed everything without draining all juice. Min 50% charging will be recommended.
I was finding a easiest way to root Oneplus X, cz ADB and such tools are pretty hectic. Finally I found a way to root OnePlus X without TWRP or any custom recovery and without even unlocking bootloader.
So all we going to do is root our device with KingRoot and then then will replace it with our favorite SuperSU app. So here we go.
Rooting your OnePlus X:
1. Download KingRoot and install it from here.
2. Once KingRoot is installed, open it and root OnePlus X with just one click. Process of rooting will take 2 - 5 mins. One done, Download Root Checker from play store and check if device is rooted. It has to be, congratulations.
Ok, hold your horses, we still have to Install SuperSu to replace KingRoot.
1. Download Terminal Emulator for Android from play store.
2. Download and unzip Replace_Kingroot_With_SuperSU.zip which contains SuperSU installation stuff.
Steps to install SuperSu.
1. Copy the downloaded Replace_Kinguser_with_SuperSU-v2.0 to your phone and extract it, extracted folder will contain "mrw" folder. Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files. This should be the path for your mrw folder. "/sdcard/mrw"
2. Open Terminal emulator and type
Code:
su
this will ask for super user permissions for terminal app, allow it.
3. Type :
Code:
sh /sdcard/mrw/root.sh
It might display some error, at the end it will launch supersu or open supersu manually.
Update su binary normal, then reboot.
Viola, your OnePlus X is fully rooted without needing the TWRP or even a cable or PC. [emoji14]
You can now uninstall KingRoot and Purify apps.
Cheers :good::good:
How To Install OTA's after rooting with this method
1. Download OnePlusOxygen_14_OTA_008_all_201601221550.zip .
2. Just flash it.
3. You'll be on OxygenOS 2.2.0 without any other files to flash. Don't wipe data and cache to retain your apps and data.
Re-rooting again after OTA's?
FOLLOW SAME GUIDE. \0/
Credits:
Kingxteam for KingRoot app
Unknow guy who made Replace_Kinguser_with_SuperSU-v2.0 zip file.
Let me know if your name should be here.

Looks good, will try when some custom roms come out

StraightEdgeKid said:
Warning: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try.
Precaution: Make sure your phone has enough charging to make things proceed everything without draining all juice. Min 50% charging will be recommended.
Well, I read the method CafeKampuchia's method to root OnePlus X, I even had some interaction with him, his method is good, though a obstacle later one can face will be installing OTA's. Our device, OnePlus X received 2 updates in a time of one week, which forced me to think that there will be more updates coming soon to fix things. (Like we can't move apps to sd after updating from OTA, though there is a option to do so). Hence I tried different things to root this device. first I tried installing SuperSU.zip from stock recovery, and I failed in it. Well XDA has lot of options to try it. Finally I found a way to root OnePlus X without TWRP or any custom recovery and I think we will be able to install OTA updates with having root too.
So all we going to do is root our device with KingRoot and then then will replace it with our favorite SuperSU app. So here we go.
Rooting your OnePlus X:
1. Download KingRoot and install it from here.
2. Once KingRoot is installed, open it and root OnePlus X with just one click. Process of rooting will take 2 - 5 mins. One done, Download Root Checker from play store and check if device is rooted. It has to be, congratulations.
Ok, hold your horses, we still have to Install SuperSu to replace KingRoot.
1. Download Terminal Emulator for Android from play store.
2. Download and unzip Replace_Kingroot_With_SuperSU.zip which contains SuperSU installation stuff.
Steps to install SuperSu.
1. Copy the downloaded Replace_Kinguser_with_SuperSU-v2.0 to your phone and extract it, extracted folder will contain "mrw" folder. Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files. This should be the path for your mrw folder. "/sdcard/mrw"
2. Open Terminal emulator and type
Code:
su
this will ask for super user permissions for terminal app, allow it.
3. Type :
Code:
sh /sdcard/mrw/root.sh
It might display some error, at the end it will launch supersu or open supersu manually.
Update su binary normal, then reboot.
Viola, your OnePlus X is fully rooted without needing the TWRP or even a cable or PC.
You can now uninstall KingRoot and Purify apps.
Cheers :good::good:
Credits:
Kingxteam for KingRoot app
Unknow guy who made Replace_Kinguser_with_SuperSU-v2.0 zip file.
CafeKampuchia for beginning the topic of rooting (And my warning section is copied from his post. ).
Let me know if your name should be here.
Click to expand...
Click to collapse
Bro i tried kingo root before this post n it dosnt work

mohammedtabish said:
Bro i tried kingo root before this post n it dosnt work
Click to expand...
Click to collapse
Well, try this. I have rooted my OnePlus X with this method, tested it and then I have wrote this big post.
and yes, avoid quoting whole OP post, specially when it's too big.

Rossyyy said:
Looks good, will try when some custom roms come out
Click to expand...
Click to collapse
For sure

StraightEdgeKid said:
Well, try this. I have rooted my OnePlus X with this method, tested it and then I have wrote this big post.
and yes, avoid quoting whole OP post, specially when it's too big.
Click to expand...
Click to collapse
Okay sir am new on xda actually i used to follow just read posts but now when i buyed opx i created an account...and i have rooted with twrp so i will try later when i will go back to stock..

Working in my OnePlus X with the latest firmware version! Thank you for all.

Mie said:
Working in my OnePlus X with the latest firmware version! Thank you for all.
Click to expand...
Click to collapse
Well, Thanks button is up there. Hehe
Thanks, for confirming that this stuff is working for others too.

Did you lose IMEI partitions (modem files) while rooting?
Can you confirm they're still there via screenshot on Partitions Backup app?
Also, does it require Unlocked bootloader?

it works perfectly! thanks from portugal!

ota
will rooting avoid getting updates for one plus x

Calvin2394 said:
Did you lose IMEI partitions (modem files) while rooting?
Can you confirm they're still there via screenshot on Partitions Backup app?
Also, does it require Unlocked bootloader?
Click to expand...
Click to collapse
Nope, it does not need unlocked bootloader. IMEI partitions are still there, no worries, attaching screen just to clear your doubts.
{
"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 ONE E1003 using Tapatalk

vinay7 said:
will rooting avoid getting updates for one plus x
Click to expand...
Click to collapse
Nope, I rooted with this method this afternoon, and received no update since, hence not sure about it. But according to me this method does not make any changes to stock recovery, hence it will not affect OTAs, you will be able to install OTAs.
Sent from my ONE E1003 using Tapatalk

Works fine, thanks dude !

StraightEdgeKid said:
Nope, I rooted with this method this afternoon, and received no update since, hence not sure about it. But according to me this method does not make any changes to stock recovery, hence it will not affect OTAs, you will be able to install OTAs.
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
And even if it would change the stock recovery, by now we should be able to re-flash the stock recovery and therefore get the updater (and then use this method again), right?

Thx mate, this method works best I think. I was worried about kingroot being some shady app, but was relieved when reading that I should replace it with supersu
From here I could even install TWRP with flashify don't I?
Thx in advance.

Works flawlessly on my E1003 on the first try. Thanks a ton for this.

David1one said:
Thx mate, this method works best I think. I was worried about kingroot being some shady app, but was relieved when reading that I should replace it with supersu
From here I could even install TWRP with flashify don't I?
Thx in advance.
Click to expand...
Click to collapse
Yes, you will be able to install TWRP with flashify without any trouble. Just remember you will not be able to install OTAs after installing TWRP.
Sent from my ONE E1003 using Tapatalk

FYI @StraightEdgeKid: OTA would fail regard less of stock or twrp recovery until you have root and system would detect it and warn at OTA screen, you would have to unroot in order to install the OTA. Thanks for the tutorial though i prefer TWRP anytime over stock.

StraightEdgeKid said:
Yes, you will be able to install TWRP with flashify without any trouble. Just remember you will not be able to install OTAs after installing TWRP.
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
How is this possible without unlocking your bootloader?
Funk Wizard said:
FYI @StraightEdgeKid: OTA would fail regard less of stock or twrp recovery until you have root and system would detect it and warn at OTA screen, you would have to unroot in order to install the OTA. Thanks for the tutorial though i prefer TWRP anytime over stock.
Click to expand...
Click to collapse
^^^ True. Any change to system (including root) will cause the OTA to fail.

[GUIDE] How to flash the COS 13 update. Even if you get the release keys error

Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"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"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.

If you could provide us the guide to root and come back to twrp I would be extremely happy

bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve

bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.

bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.

y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).

bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.

If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?

thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.

can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!

Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.

I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.

This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.

I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!

u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file

#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.

InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762

u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.

Having tried many other ways, I got it done with this instruction.
Thank you!

marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.