[OTA][KRT16S][GROUPER]signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip - Nexus 7 Android Development

This is just the Grouper KRT16S OTA package from Google. Bugfixes, 1.4Mb in size. ZIP file attached. I am not your tech support to get ADB working on you laptop or why your Nexus 7 does weird things after installing so don't be surprised if I ignore questions that can be answered by searching.
Original file name:
3aad414bf97cede8ecbc2027597e7f01bfe1ce47.signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip
If you are stock and want to update from KRT16O then just drop the zip into your adb folder and sideload it in recovery:
Code:
adb sideload signed-nakasi-KRT16S-from-KRT16O-3aad414b.zip
Help this helps someone.

kpetrie77 said:
This is just the Grouper KRT16S OTA package from Google. Bugfixes, 1.4Mb in size. ZIP file attached. I am not your tech support to get ADB working on you laptop or why your Nexus 7 does weird things after installing so don't be surprised if I ignore questions that can be answered by searching.
Original file name:
3aad414bf97cede8ecbc2027597e7f01bfe1ce47.signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip
If you are stock and want to update from KRT16O then just drop the zip into your adb folder and sideload it in recovery:
Code:
adb sideload signed-nakasi-KRT16S-from-KRT16O-3aad414b.zip
Help this helps someone.
Click to expand...
Click to collapse
I have a question. If this can be side loaded to recovery and I assume you mean twrp or cwm why can't it just be down loaded to device and flashed through recovery? Maybe I just don't understand what you mean by sideloaded. Thanks if you reply and if not I read the op and thanks for this
Sent from my HTCONE using Xparent Blue Tapatalk 2

Also with unlocked Bootloader and TWRP I get this update OTA and installation went fine.

ml_taz said:
Also with unlocked Bootloader and TWRP I get this update OTA and installation went fine.
Click to expand...
Click to collapse
Same for me, OTA went fine with TWRP

Received tonight at 02.30 cet!!! :good:

ml_taz said:
Also with unlocked Bootloader and TWRP I get this update OTA and installation went fine.
Click to expand...
Click to collapse
How did you update via twrp? I'm having bluetooth.apk error. It always fail. =(
Sent from my Nexus 7 using xda app-developers app

ianmedina said:
How did you update via twrp? I'm having bluetooth.apk error. It always fail. =(
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
use adb sideload command, read the OP

ianmedina said:
How did you update via twrp?
Click to expand...
Click to collapse
I didn't update via TWRP! I get the update OTA! Also I have unlocked BL, Root and TWRP.
If you didn't get it via OTA you can sideload the Zip from Post #1.

ml_taz said:
I didn't update via TWRP! I get the update OTA! Also I have unlocked BL, Root and TWRP.
If you didn't get it via OTA you can sideload the Zip from Post #1.
Click to expand...
Click to collapse
Whefe can i find the adb folder? Sorry about the question..
Hopefully you can walkthrough me or tell me the step by step.
Sent from my Nexus 7 using xda app-developers app

ianmedina said:
Whefe can i find the adb folder? Sorry about the question..
Hopefully you can walkthrough me or tell me the step by step.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
platform-tools, SDK
View attachment 2404062

treIII said:
I have a question. If this can be side loaded to recovery and I assume you mean twrp or cwm why can't it just be down loaded to device and flashed through recovery? Maybe I just don't understand what you mean by sideloaded. Thanks if you reply and if not I read the op and thanks for this
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
The stock recovery does not look for a zip on the device without a command file telling it there is one present to flash.

ivn888 said:
platform-tools, SDK
View attachment 2404062
Click to expand...
Click to collapse
Thanks... But i think i'm gonna lose root?
Sent from my Nexus 7 using xda app-developers app

ianmedina said:
Thanks... But i think i'm gonna lose root?
Click to expand...
Click to collapse
No, doesn't touch su.
Sent from my HTC6500LVW using Tapatalk

kpetrie77 said:
No, doesn't touch su.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
How about my twrp? I might lose it.
Sent from my Nexus 7 using xda app-developers app

ianmedina said:
How about my twrp? I might lose it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I believe the stock recovery will be installed with the update? but you can always reinstall TWRP with flashify......

What folder was this update downloaded too?

Re: OTA
bonzer2u said:
I believe the stock recovery will be installed with the update? but you can always reinstall TWRP with flashify......
Click to expand...
Click to collapse
The OTA process works with TWRP but reloads stock recovery AND removes root. No problem getting both back through the usual methods.

ianmedina said:
How about my twrp? I might lose it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It's a nexus. Its not hard to get back recovery and root.
Sent from my Nexus 7 using XDA Premium HD app

ianmedina said:
How did you update via twrp? I'm having bluetooth.apk error. It always fail. =(
Click to expand...
Click to collapse
ianmedina said:
Whefe can i find the adb folder? Sorry about the question..
Hopefully you can walkthrough me or tell me the step by step.
Click to expand...
Click to collapse
ianmedina said:
Thanks... But i think i'm gonna lose root?
Click to expand...
Click to collapse
ianmedina said:
How about my twrp? I might lose it.
Click to expand...
Click to collapse
I'm going to say some things not to be mean or rude but to keep you out of trouble. It is not installing because you do not know what you are doing and have not taken the initiative to learn some basics for yourself. Except for the fact you are not on the correct ROM to install this update in the first place, I would say losing root and TWRP would be the best thing for now.
You are going screw up your device and have no idea how to fix it yourself or even what information to provide for others to help you fix it. Your best bet would to be restoring to stock with a factory image and not screw around until you are up to speed.
There are ton of FAQ's and guides on this site in the general sections. Learn how to install and use ADB and fastboot. Read up on the different types up zip files and how they are installed. If you are using a one click, understand what ADB or fastboot commands are going on behind the scenes and exactly what it is pushing to your device.
Once you have a general understanding of things, please come and play around as much as you want. If you do something that causes a bootloop you will at least know how to recover your device.
bonzer2u said:
I believe the stock recovery will be installed with the update? but you can always reinstall TWRP with flashify......
Click to expand...
Click to collapse
ChauncyG said:
The OTA process works with TWRP but reloads stock recovery AND removes root. No problem getting both back through the usual methods.
Click to expand...
Click to collapse
A 5.4Mb recovery is not going to fit in a 1.4Mb zip file. Also see post 3, 4 and 8. Root and TWRP or CWM will remain intact. Bad information is worse than no information.

"Once you have a general understanding of things, please come and play around as much as you want. If you do something that causes a bootloop you will at least know how to recover your device.A 5.4Mb recovery is not going to fit in a 1.4Mb zip file. Also see post 3, 4 and 8. Root and TWRP or CWM will remain intact. Bad information is worse than no information."
Not trying to give bad info just relating my personal experience. You are correct that a full recovery image file at 5.4mb could not fit, even zipped, in a 1.4mb update, however, a full recovery image file is not needed to change the behavior of things. Root and the ability to boot back into TWRP were lost during my update process. It was easily corrected but it did happen. Others have reported a different experience. That was mine.
A good scientist reports ALL observations and reserves judgement until a complete data set is established.

Related

Difference between XNPH22R and XNPH22Q?

so cyanogen website has the XNPH22Q zip file, however its not flashable with TWRP when I tired, but xda forum has XNPH22R which is flashable version. What's makes the difference? And how would I go about to flashing the original XNOH22Q ROM from official cyanogen website? Thanks in advance.
Sent from my One using Tapatalk
zabih107 said:
so cyanogen website has the XNPH22Q zip file, however its not flashable with TWRP when I tired, but xda forum has XNPH22R which is flashable version. What's makes the difference? And how would I go about to flashing the original XNOH22Q ROM from official cyanogen website? Thanks in advance.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Where did you see the 22Q on official CM website?
It's already for a couple of weeks 25R.
https://cyngn.com/products/oneplusone/
And it's specifically says cm-11.0-XNPH25R-bacon-signed-fastboot.zip, so should be pushed with fastboot.
Oh lol nvm I'm going crazy . lol.
Would u know how to push with fastboot? The commands and process I mean
Sent from my One using Tapatalk
zabih107 said:
Oh lol nvm I'm going crazy . lol.
Would u know how to push with fastboot? The commands and process I mean
Sent from my One using Tapatalk
Click to expand...
Click to collapse
IF I'm not mistaken it should be used SIDELOAD METHOD:
adb sideload NAMEofROM.zip
more reading is here:
http://wiki.cyanogenmod.org/w/Install_CM_for_bacon
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
RalphLauren said:
IF I'm not mistaken it should be used SIDELOAD METHOD:
adb sideload NAMEofROM.zip
more reading is here:
http://wiki.cyanogenmod.org/w/Install_CM_for_bacon
Click to expand...
Click to collapse
You don't adb sideload a factory image file, its not a flashable zip to begin with. Doing so might brick your device
zephiK said:
You don't adb sideload a factory image file, its not a flashable zip to begin with. Doing so might brick your device
Click to expand...
Click to collapse
of course you do not sideload if you have factory image as xxx.img file, than you just flash.
But in case of OPO, we have xxx_fastboot.zip file (and it's not a flash-able in recovery from SD card file).
Please give your version, how to instal OPO's "factory_image.zip" into OPO
Yes, please can someone explain how to flash a factory image on the OPO.
Sent from my One using XDA Premium 4 mobile app

What is eu.chainfire.supersu.MainActivity Emblem?

This process is important? I was deleting SuperSU and in says that if I delete SuperSU I will delete this file too...
If you're unrooting, you don't need to keep it.
Ok, thanks.
There is a way to see if there is any modifications to the system's file?
Sent from my Nexus 5 using XDA Free mobile app
There's an OTA checker flashable zip in general I think.
No, not in the ota, I say in general, if I want just to control of there is any modifications without flash anything
Sent from my Nexus 5 using XDA Free mobile app
Giolte_ said:
No, not in the ota, I say in general, if I want just to control of there is any modifications without flash anything
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I don't understand. Please rephrase
If I want to check if the system's file are modified, how can I do?
Sent from my Nexus 5 using XDA Free mobile app
Giolte_ said:
If I want to check if the system's file are modified, how can I do?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
There is only one way. By flash the OTA checker zip in custom recovery. It can be found in the general forum I believe.
---------- Post added at 10:15 AM ---------- Previous post was at 10:12 AM ----------
Here it is
http://forum.xda-developers.com/showthread.php?t=2927865
Ok, so I have to flash this with flashify (rooted with towelroot)
After the flash I'll have to unroot the phone and just install Lollipop with the ota?
Sent from my Nexus 5 using XDA Free mobile app
Giolte_ said:
Ok, so I have to flash this with flashify
Click to expand...
Click to collapse
Flash what with Flashify?
I think the best bet for you is to read the thread about root / update in my signature. OTA is proving too troublesome. I can't hand hold you through the whole process.
I mean the zip checker
Sent from my Nexus 5 using XDA Free mobile app
Giolte_ said:
I mean the zip checker
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I already told you.
Ok, I've read your thread about how to upgrade to Lollipop the Nexus.
The fact is that my main pc have no working USB ports, so if I want to unlock the bootloader and stuff like this I have to use my second pc, and it is very slow (the last time to just fastboot a factory image it tooks me one hour of suffering).
I think that the method 2b is the one that is closest to my situation:
1. Unlock bootloader if necessary (This wipes data)
2. Accept OTA update
3. Fastboot flash a custom recovery image (of your choice)
4. Fastboot flash a custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
5. Flash from recovery, SuperSU
Click to expand...
Click to collapse
I don't want root, so:
2. Accept OTA update
Click to expand...
Click to collapse
If I have understood, the only thing that I have to do is use flashify to flash the OTA checker zip. file and than proceed with the OTA, right?
If there is another way to do this without use the PC, it will be great, but I don't know.
Is what I said right or I forgot something?
Thank you with your help anyway!
Giolte_ said:
If I have understood, the only thing that I have to do is use flashify to flash the OTA checker zip
Click to expand...
Click to collapse
You haven't understood. I told you how to flash it. I did NOT say flash via flashify please try to read properly
There is only one way. By flash the OTA checker zip in custom recovery.
Click to expand...
Click to collapse
This is what you mean?
If yes, I can't flash with a custom recovery because I have the stock recovery (because I'm rooted with only Towelroot, so stock recovery and locked bootloader)
Giolte_ said:
This is what you mean?
If yes, I can't flash with a custom recovery because I have the stock recovery (because I'm rooted with only Towelroot, so stock recovery and locked bootloader)
Click to expand...
Click to collapse
Then you can't use it! Wait for the OTA and install it.
I already have the OTA, but I think that there could be some issues, this is why I want to check if everything it's good, I don't want to brick/bootloop the device
Giolte_ said:
I already have the OTA, but I think that there could be some issues, this is why I want to check if everything it's good, I don't want to brick/bootloop the device
Click to expand...
Click to collapse
You wont brick it. If you're not stock, it wont install.
Thank you, it works

Root 5.0.1?

Hi I was going to use chainfires method but the best the web page it only sates 5.0 with the build number LRX210- which is different to 5.0.1?
Is there any way to root then?
Sent from my Nexus 5 using XDA Premium 4 mobile app
dec1153 said:
Hi I was going to use chainfires method but the best the web page it only sates 5.0 with the build number LRX210- which is different to 5.0.1?
Is there any way to root then?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
of course there is a way to root 5.0.1.
use fastboot to either flash a custom recovery (TWRP is probably your best bet), or use fastboot to just boot into the custom recovery without flashing. Either way, once your in recovery, flash SuperSU (download here http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip)
done and done.
jss2 said:
of course there is a way to root 5.0.1.
use fastboot to either flash a custom recovery (TWRP is probably your best bet), or use fastboot to just boot into the custom recovery without flashing. Either way, once your in recovery, flash SuperSU (download here http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip)
done and done.
Click to expand...
Click to collapse
You sir are very wrong, you cannot flash that zip in recovery because it no longer works with lollipop... (Sigh)
PS. I have a custom recovery and unlocked boot loader so your suggestion are invalid
Sent from my Nexus 5 using XDA Premium 4 mobile app
dec1153 said:
You sir are very wrong, you cannot flash that zip in recovery because it no longer works with lollipop... (Sigh)
PS. I have a custom recovery and unlocked boot loader so your suggestion are invalid
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
actually, it does work. with 5.0.1, I'm rooted. Except when I flashed 5.0.1, SuperSU v2.40 hadn't yet been released, so I rooted with SuperSU v2.37, and then updated via the playstore when 2.40 came out. but it definitely works with Lollipop.
p.s. you need to have an unlocked bootloader to install a custom recovery (which is what I suggested doing). So in fact, my suggestion is completely valid and 100% relevant. In fact, I had assumed that you already had an unlocked bootloader when I posted.
jss2 said:
actually, it does work. with 5.0.1, I'm rooted. Except when I flashed 5.0.1, SuperSU v2.40 hadn't yet been released, so I rooted with SuperSU v2.37, and then updated via the playstore when 2.40 came out. but it definitely works with Lollipop.
p.s. you need to have an unlocked bootloader to install a custom recovery (which is what I suggested doing). So in fact, my suggestion is completely valid and 100% relevant. In fact, I had assumed that you already had an unlocked bootloader when I posted.
Click to expand...
Click to collapse
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app
dec1153 said:
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes, and the way to "manually re-root" is to flash the ZIP in a custom recovery. You the app installed, but not the SU binary. So flash it in TWRP.
dec1153 said:
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CF Auto Root and flashing the superSU2.40.zip in recovery both root android 5(0.1/0.2). Did it myself and confirming root access.
You can root with the same chainfires files for 5.0, and then you can update supersu and twrp
dec1153 said:
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It astounds me how you have the guts to ask for help - then someone gives you an answer that is completely right and you do a hard six and blatantly flame them for trying to help you.
JayR_L said:
It astounds me how you have the guts to ask for help - then someone gives you an answer that is completely right and you do a hard six and blatantly flame them for trying to help you.
Click to expand...
Click to collapse
Crazy. Done it to me a few times. I even decided not to help him ever again some time ago, then took pity on him yesterday or the day before and the he did it AGAIN!
He's just a school kid, but you'd hope he would learn from his attitude, but apparently not.
What's worse, is he isn't even picking up the knowledge that people give him or reading the stickies. He's been Here pretty much a year in the n5 forum and cannot even be bothered to.understand the basics. Asks the most basic questions every time.

URGENT HELP PLEASE XT1548 OTA to marshmallow TWRP BOOT RESTART

Hello i was wondering if you could help me with something. My XT1548 just got an OTA update. And i tried updating too it, but my phone keeps restarting every 2 minutes into TWRP instead of updating
i am on lollipop 5.1.1 trying too get the latest OTA.
SpitFire727 said:
Hello i was wondering if you could help me with something. My XT1548 just got an OTA update. And i tried updating too it, but my phone keeps restarting every 2 minutes into TWRP instead of updating
i am on lollipop 5.1.1 trying too get the latest OTA.
Click to expand...
Click to collapse
When twrp starts, clear caches and reboot. Should be good to go, and don't accept ota again, you must be stock to take ota.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
When twrp starts, clear caches and reboot. Should be good to go, and don't accept ota again, you must be stock to take ota.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
So i unrooted VIA superSU
is the next step too install the stock rom?
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
SpitFire727 said:
So i unrooted VIA superSU
is the next step too install the stock rom?
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Click to expand...
Click to collapse
Maybe... If you had installed Xposed or other root app, it's best to that, or restore your pre-rooted nandroid backup. Otherwise, if you didn't modify system, just fastboot flash stock recovery and take the ota.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Maybe... If you had installed Xposed or other root app, it's best to that, or restore your pre-rooted nandroid backup. Otherwise, if you didn't modify system, just fastboot flash stock recovery and take the ota.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
i removed a bunch of bloatware. mostly sprint junk
SpitFire727 said:
i removed a bunch of bloatware. mostly sprint junk
Click to expand...
Click to collapse
Then an OTA may fail, depending on what the update script checks for. I would flash back to pure stock to be safe.
Sent from my Motorola XT1575 using XDA Labs
i don't have a pre rooted backup :/
SpitFire727 said:
i don't have a pre rooted backup :/
Click to expand...
Click to collapse
Then I would flash back to stock...
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Then I would flash back to stock...
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
could you walk me through all the steps i need too take?
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
moving discussion to Q&A..
acejavelin said:
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
Click to expand...
Click to collapse
so i did all the steps, i updated too 6.1. but now i face a new problem, no devices are found in adb when in boot loader mode. it is detected while the phone is started up though.. in the progress of trying too fix this.
acejavelin said:
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
Click to expand...
Click to collapse
so followed all the steps and am now on 6.1, but now i face a new challenge. my adb is not finding any devices while in boot loader but it detects it while the phone is fully booted up.
SpitFire727 said:
so followed all the steps and am now on 6.1, but now i face a new challenge. my adb is not finding any devices while in boot loader but it detects it while the phone is fully booted up.
Click to expand...
Click to collapse
You phone will never be detected with adb in the bootloader, that isn't what adb is intended for, but that is where you use fastboot.
Your situation is completely normal.
acejavelin said:
You phone will never be detected with adb in the bootloader, that isn't what adb is intended for, but that is where you use fastboot.
Your situation is completely normal.
Click to expand...
Click to collapse
oh okay so how too i install TWRP, its in the internal storage and the command fastboot boot twrp.img just says waiting for device
SpitFire727 said:
oh okay so how too i install TWRP, its in the internal storage and the command fastboot boot twrp.img just says waiting for device
Click to expand...
Click to collapse
The TWRP img file needs to be on the computer in the fastboot directory. Start the bootloader and type 'fastboot devices' to make sure the device is recognized, then 'fastboot boot twrp.img' (remember to use the actual filename in place of twrp.img)
Sent from my Motorola XT1575 using XDA Labs

[Completed] Rooted but no supersu

Greetings XDA
I have a rooted samsung galaxy s6 edge(At&t) version lollipop 5.1.1 that i rooted with Odin.
I have no custom recovery installed and my problem is that supersu does not work, it says that su binary need to be updated.
After searching google i could not find a recovery.img for my specific model number SM-G925A.
I need help if there is a way i can install a custom recovery or how to update su binary so i can grant root access to apps.
By the way i am a newbie in the rooting world.. so simple answers will be appreciated!
Regards
You see a pop-up window with a warning and 2 buttons at the bottom:
1. Normal
2. Using TWRP.
Right?
blinoff82 said:
You see a pop-up window with a warning and 2 buttons at the bottom:
1. Normal
2. Using TWRP.
Right?
Click to expand...
Click to collapse
Actually i tried with kingroot.net even though i had no clue if it is compatible with my device or not and i just tried it and the results were positive , my device was rooted and i could use root access with apps but now a different problem appeared i lose root access on reboot or crash , it turns out that this is cause my bootloader is not unlocked or something like that , i dont really know if it is or not and i dont have TWRP installed i have stock recovery from android..
lunaso said:
... i dont have TWRP installed i have stock recovery from android..
Click to expand...
Click to collapse
You can try to update binary file "Normal", without TWRP.
Sent from my OnePlus One using XDA Labs
blinoff82 said:
You can try to update binary file "Normal", without TWRP.
Sent from my OnePlus One using XDA Labs
Click to expand...
Click to collapse
I tried but it just crashes my phone and it reboots automatically.
lunaso said:
I tried but it just crashes my phone and it reboots automatically.
Click to expand...
Click to collapse
OK, then read this thread https://forum.xda-developers.com/showthread.php?t=2276863
Sent from my OnePlus One using XDA Labs
blinoff82 said:
OK, then read this thread https://forum.xda-developers.com/showthread.php?t=2276863
Sent from my OnePlus One using XDA Labs
Click to expand...
Click to collapse
No useful help there i am stuck.
I want to check if my bootloader is unlocked or not , how can i check that? Even though 70 % i am sure it is unlocked but is there a way to confirm it?
lunaso said:
No useful help there i am stuck.
Click to expand...
Click to collapse
I meant that you can try to place su binary in appropriate place manually and give permissions. See this tutorial for manual install section https://github.com/koush/Superuser/issues/216#issuecomment-38354585
If this not helped you need to reroot your device. Unfortunately, I do not know the other options, it is a pity that you have no custom recovery.
Sent from my OnePlus One using XDA Labs

Categories

Resources