okay now I am starting to get lost and the guide for ''fixing your IMEI number'' caused my phone to soft-brick once again so it didn't really help
and yes I used the most recent SuperSU (stable) version V2.78 (I hope that is a correct version)
http://forum.xda-developers.com/oneplus-one/general/steps-how-to-recover-bad-imei-t3171452
my baseband gives a I think correct version but my IMEI number still is ''0''
Please!, can anyone tell me how to restore my IMEI number?
Also my phone uses tries to use LTE connection like I have U.S. drivers (I don't know if it makes a difference since I am pretty much noob)
I find that just wierd.. sorry to bother you guys with all this, I just want my phone to be fixed
dempixels said:
Also my phone uses tries to use LTE connection like I have U.S. drivers (I don't know if it makes a difference since I am pretty much noob)
I find that just wierd.. sorry to bother you guys with all this, I just want my phone to be fixed
Click to expand...
Click to collapse
Did you try to make a complete reset of the phone?
Dio-Genes said:
Did you try to make a complete reset of the phone?
Click to expand...
Click to collapse
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it
dempixels said:
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it
Click to expand...
Click to collapse
Download the zip from the oneplus link... extract it and read the "REEEEEADME.TXT" last paragraph how to type Imei in "RF_NV_manager.exe"...PM me if you need more help.
dempixels said:
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it
Click to expand...
Click to collapse
EXACTLY!!! follow these instructions step by step. Take a look how many sparsechunk files are in the image that you download and proceed as advised. Take care to choose the right image for your device, also about country and so.
http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486
Dio-Genes said:
EXACTLY!!! follow these instructions step by step. Take a look how many sparsechunk files are in the image that you download and proceed as advised. Take care to choose the right image for your device, also about country and so.
http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486
Click to expand...
Click to collapse
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''
bablu048 said:
Download the zip from the oneplus link... extract it and read the "REEEEEADME.TXT" last paragraph how to type Imei in "RF_NV_manager.exe"...PM me if you need more help.
Click to expand...
Click to collapse
well that's just it, it requires root but it's always when I install superSU that my phone soft-bricks. it's the third time that happened.
dempixels said:
well that's just it, it requires root but it's always when I install superSU that my phone soft-bricks. it's the third time that happened.
Click to expand...
Click to collapse
Here use this su2.62-3 it will work. http://forum.xda-developers.com/showpost.php?p=64452858&postcount=1
And remember NOT TO RESTORE THE QCN OF ONEPLUS edit your imei using RFNVmanager only.
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
dempixels said:
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''
Click to expand...
Click to collapse
Have you downgraded earlier??
dempixels said:
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''
Click to expand...
Click to collapse
As far as I remember that happened to me when I tried to relock the bootloader at that moment. Did it work anyway? I mean, did it reboot? Which image did you choose? 5.1 or 6.x? Probably start with 5.1 as this was the original image for the device and later let it update via OTA. Be sure still to grab the appropriate image.
Dio-Genes said:
As far as I remember that happened to me when I tried to relock the bootloader at that moment. Did it work anyway? I mean, did it reboot? Which image did you choose? 5.1 or 6.x? Probably start with 5.1 as this was the original image for the device and later let it update via OTA. Be sure still to grab the appropriate image.
Click to expand...
Click to collapse
According to the Motorola official developer forums I am not ALLOWED to install a android 5.X image when I last ran a 6.X android system. as the result could be that I could Hard brick my device
also some further info:
I think in the past when I tried to install the official stock rom. I accidentally removed/erased the EFS file. or some file that holds my IMEI information.
and now I practically have to re-write it (since.. well you can't just create a IMEI ID or Can I?). but it seems impossible if I look at it.
but I do have the original box with the original IMEI number.
bablu048 said:
Here use this su2.62-3 it will work. http://forum.xda-developers.com/showpost.php?p=64452858&postcount=1
And remember NOT TO RESTORE THE QCN OF ONEPLUS edit your imei using RFNVmanager only.
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
Have you downgraded earlier??
Click to expand...
Click to collapse
no I didn't downgrade earlier. (well i flashed a different logo.bin) but no I didn't downgrade.
so that means the superSU 2.78 does not work on android 6.X?
dempixels said:
According to the Motorola official developer forums I am not ALLOWED to install a android 5.X image when I last ran a 6.X android system. as the result could be that I could Hard brick my device
.
Click to expand...
Click to collapse
Sorry, that's beyond my knowledge.
dempixels said:
no I didn't downgrade earlier. (well i flashed a different logo.bin) but no I didn't downgrade.
so that means the superSU 2.78 does not work on android 6.X?
Click to expand...
Click to collapse
Idk about su2.78... I have always used su2.62-3 ..it worked on lollipop and it works on MM.
What is the need of updating SU app, all it does is give 'root' permissions.
bablu048 said:
Idk about su2.78... I have always used su2.62-3 ..it worked on lollipop and it works on MM.
What is the need of updating SU app, all it does is give 'root' permissions.
Click to expand...
Click to collapse
okay, because you have more experience rooting I am gonna ask you just to be sure.
correct me if i'm wrong:
first I have to flash twrp thingy
next I have to reboot android and copy SuperSU into my storage
then I have to reboot in fastboot and boot into twrp
in twrp I have to flash/install SuperSU into the system.
and.. that's it. so superSU practically roots my device?
oh and from what i've heard/seen I will not be able to update anymore? because when I installed/flash superSU I saw in the log:
''disabling OTA update survival'' or something like that
dempixels said:
okay, because you have more experience rooting I am gonna ask you just to be sure.
correct me if i'm wrong:
first I have to flash twrp thingy
next I have to reboot android and copy SuperSU into my storage
then I have to reboot in fastboot and boot into twrp
in twrp I have to flash/install SuperSU into the system.
and.. that's it. so superSU practically roots my device?
oh and from what i've heard/seen I will not be able to update anymore? because when I installed/flash superSU I saw in the log:
''disabling OTA update survival'' or something like that
Click to expand...
Click to collapse
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
alright 2 final questions before I am gonna start the whole flashing again
1. does this superSU version work with 6.0.1? (just to be sure)
2.what does it backup to be precise? only the system or everything (probably everything)
bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
YES!! it's rooted thanks for the guide but now... ermm.. how do I change my IMEI number?
bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
and.... nevermind.. it did not root!... what?
I don't understand I followed the steps on how to install superSU with systemless.. something and it all worked. but it did not root! how is that possible?
do I have to try it again?
dempixels said:
and.... nevermind.. it did not root!... what?
I don't understand I followed the steps on how to install superSU with systemless.. something and it all worked. but it did not root! how is that possible?
do I have to try it again?
Click to expand...
Click to collapse
you dont have su app even after flashing su2.62-3??
Related
As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
If this didn't work you can also try flashing this modified boot.img, it has only been tested with the Mexican AT&T variant, so I don't know if it will work properly with other variants.
Thanks!
I would try this if I was certain Flashfire would work...(don't want to reflash for an OTA)
diegochiva95 said:
where? I want to see him
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-z-play/help/unlocked-bootloader-t3459976/page4
Post number 34
I take it back, sadly it is stuck at boot for me I tried it yes. No other SuperSu? I think I had the 03 version and you have 02... I think?
EDIT: not true, I had 02 too, but it just wouldn't work.
EDIT: It forced somewhat of a factory reset on me when I tried the same SuperSU but no systemless, I didn't lose any media but I had to relog in my account and download and update all apps again.
I will just wait for nougat...
several people commented that password is required to enter the recovery......
Enviado desde mi XT1635-02 mediante Tapatalk
diegochiva95 said:
several people commented that password is required to enter the recovery......
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
The same password that you used to encrypt the phone while setting it up. If you're using a pattern you can use the numbers equivalent to the pattern you used.
FreedFromDeath said:
As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
Click to expand...
Click to collapse
Thanks for the tutorial. But was inquisitive to know why one cannot use systemless root on our Vertex??
Thanks!
great
just pick up my phone
btw 7 is not released yet right
hmnk said:
Thanks for the tutorial. But was inquisitive to know why one cannot use systemless root on our Vertex??
Thanks!
Click to expand...
Click to collapse
This isn't the Vertex though, this is the Addison.
FreedFromDeath said:
This isn't the Vertex though, this is the Addison.
Click to expand...
Click to collapse
http://www.gsmarena.com/moto_z_play...r_testing_55inch_screen_in_tow-news-19195.php
Anyways, coming back to the topic, why can't we use systemless root on our device?
Thanks,
Regards.
FreedFromDeath said:
As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
Click to expand...
Click to collapse
says it is not necessary to flash the .zip SuperSU only accept the root for the TWRP own. It is true?
diegochiva95 said:
says it is not necessary to flash the .zip SuperSU only accept the root for the TWRP own. It is true?
Click to expand...
Click to collapse
Isn't there a warning to never accept the root from the recovery?
Another thing, if deencryption doesn't work you can sideload the SuperSU zip using adb through TWRP.
Updated OP with a possible workaround.
FreedFromDeath said:
Updated OP with a possible workaround.
Click to expand...
Click to collapse
If you dont mind, could you provide the details of your device?
So I see there is a Chinese twrp for moto z play but is anyone working on a north American version? Same question for SuperSU? Will there be official versions with systemless root? I guess what I'm asking is should I wait a bit or go this route? I like otas. I also reeeeally like a rooted phone (exchange server BS needs to be bypassed for piece of mind).
Not enitrely sure what happened, but my phone wouldnt boot after flashing SuperSU, even after i restored stock system,boot, and EFS. The boot.img got me booting again though and now rooted. (US variant)
Edit: Can someone upload a stock boot.img for the US variant? I think my backup boot.img might be corrupt, as it causes my phone not to boot.
jon7701 said:
Not enitrely sure what happened, but my phone wouldnt boot after flashing SuperSU, even after i restored stock system,boot, and EFS. The boot.img got me booting again though and now rooted. (US variant)
Edit: Can someone upload a stock boot.img for the US variant? I think my backup boot.img might be corrupt, as it causes my phone not to boot.
Click to expand...
Click to collapse
My phone got frozen at boot, dual sim in the EU version.
I tried to flash the non-systemless SuperSU and that made it factory reset, still not rooted.
I will wait....
hmnk said:
Anyways, coming back to the topic, why can't we use systemless root on our device?
Thanks,
Regards.
Click to expand...
Click to collapse
Anyone??
Thanks
hmnk said:
Anyone??
Thanks
Click to expand...
Click to collapse
I tried to do systemless and it was unable to patch the boot image.
Also if someone could upload a US variant boot.img that would be very appreciated. On the mexican boot.img I cant get data or recieve calls. I can only make outgoing calls for some reason.
So I flashed the 7.1.1 update and everything was fine. I then tried to root through TWRP with the most recent version of recovery and and SuperSu and when I went to reboot it would get to the "Google" splash screen and go back to the warning. I then tried to restore to my Nandroid that I made right before the 7.1.1 flash but it does the same thing. I ended up doing a factory reset, still looping. I tried flashing an old firmware but it still would loop. I got desperate and did a full wipe and then flashed the old firmware from September's update but it still will not boot. I'm a long time lurker I just don't post much. Any help will be appreciated. Thanks in advance!
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Ahh, great. I tried searching to see if anyone else posted anything, couldn't find it.
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Wait are you able to get into Recovery?
ChazLanier said:
Wait are you able to get into Recovery?
Click to expand...
Click to collapse
Nope. And so are other folks.
But if you can, there's still hope to save your device.
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
jamaniek said:
Nope. And so are other folks.
But if you can, there's still hope to save your device.
Click to expand...
Click to collapse
I can still get into recovery. I just can't get it past the Google splash screen.
ChazLanier said:
I can still get into recovery. I just can't get it past the Google splash screen.
Click to expand...
Click to collapse
Have you tried installing custom ROM, instead of a stock one?
And tell us what @ArminasAnarion asked for. There may be a pattern here. :good:
I haven't tried a custom ROM. I'll try that if I get any down time at work. Also, I'll check for you @ArminasAnarion in a bit.
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
ChazLanier said:
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
Click to expand...
Click to collapse
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
ArminasAnarion said:
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
Click to expand...
Click to collapse
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
ChazLanier said:
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
Click to expand...
Click to collapse
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
ArminasAnarion said:
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
Click to expand...
Click to collapse
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
ChazLanier said:
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
Click to expand...
Click to collapse
Oh okay cool! Good luck!
ArminasAnarion said:
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
Click to expand...
Click to collapse
Samsung storage, and I thought I was on -2 but it seems like I was on -1.
ArminasAnarion said:
Oh okay cool! Good luck!
Click to expand...
Click to collapse
Newest image didn't work either..
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
FWIW, I successfully updated to 7.1.1 NPF10C and rooted by using fastboot to flash bootloader, radio, boot, system, and vendor. Then used TWRP 3.0.2-2 to flash SuperSU 2.78 SR1. No issues.
Howie Dub said:
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
Click to expand...
Click to collapse
No luck on this either.
How could I flash recovery without pc? I have twrp at the moment and i want the CWM. Im on 6.0 Emui 4.1
staska_lt said:
How could I flash recovery without pc? I have twrp at the moment and i want the CWM. Im on 6.0 Emui 4.1
Click to expand...
Click to collapse
Try with the Flashify app.
GaT7 said:
Try with the Flashify app.
Click to expand...
Click to collapse
I tried and i got black screen
Flash it via TWRP then? TWRP supports flashing .img too if you need to. :|
3. Post using a clear and descriptive subject and message.
You're most likely to receive a helpful answer to your question, if you use a short subject title that describes your problem and a message that explains in detail, what your problem is and what you've done to try solving it.
Click to expand...
Click to collapse
Source (Forum rules): http://forum.xda-developers.com/announcement.php?a=81
Just sayin bro...
And btw some things just dont work well without a PC. Even though it might be possible to work around it you might just wanna do this on a computer with these commands in adb:
Code:
adb reboot bootloader
and
Code:
fastboot flash recovery recovery.img
and then reboot
PCSE said:
Source (Forum rules): http://forum.xda-developers.com/announcement.php?a=81
Just sayin bro...
And btw some things just dont work well without a PC. Even though it might be possible to work around it you might just wanna do this on a computer with these commands in adb:
and
and then reboot
Click to expand...
Click to collapse
I tried to flash via twrp. It said that the install was succesful, but when i tried to go to recovery i got black screen
Why would you want cwm? TWRP is way better. Oh and your recovery is gone. You can be lucky that you didn't brick your phone. Next time, use TWRP instead and ONLY if you have the ability to restore everything with a PC. ONLY make such hard modifications to your phone if you have a PC nearby
Confirm that you're fully rooted using something like Root Checker
GaT7 said:
Confirm that you're fully rooted using something like Root Checker
Click to expand...
Click to collapse
Im sure im fully rooted
Ok, I suspect something may be wrong with your root or TWRP or ROM, which may be the reason for the odd problems.
So do check & confirm root anyway, & also tell us the versions of your TWRP & ROM (latter in Settings > About phone > Build number).
GaT7 said:
Ok, I suspect something may be wrong with your root or TWRP or ROM, which may be the reason for the odd problems.
So do check & confirm root anyway, & also tell us the versions of your TWRP & ROM (latter in Settings > About phone > Build number).
Click to expand...
Click to collapse
Im on sakoban's rom. B564
This is what I found accidentally by myself. There is actually an easy way to flash the OTA update if you are too lazy to find a download link for the zip file(like me).
Required: TWRP(Always use the latest version to avoid problems), Any file manager
1. Download the update in settings through OTA. (Make sure full zip file is downloaded which normally exceeds 1GB.)
2. After finishing the download, open your file manager and enable the Show Hidden Files function.
3. Go to Internal Storage and find the folder named .Ota then copy the zip file to any directory you like.(Visible one which is not hidden.)
4. Reboot to TWRP and flash the zip file you downloaded, Magisk/SuperSU and other mods you like.
5. Wipe Dalvik and Cache
6. Reboot
7. Enjoy the update.
Ps: You should root your device before rebooting to prevent the TWRP from getting overwritten by stock recovery.
Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct? I guess that could be the blah blah blah part of Step 4
counterfeit187 said:
Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct? I guess that could be the blah blah blah part of Step 4
Click to expand...
Click to collapse
No, TWRP remains. Flash the full rom, flash magisk/su and reboot to recovery then to system.
And isn't this the simple basic procedure to flash the rom on a rooted device(?) I wonder how to used to do it before and also that you can find the latest rom update on downloads.oneplus.net - can't you?
Plus won't this trigger dm verity and encryption? Because I usually wait for the modified boot.img for the latest update which disables dm verity and forced encryption.
DawoodSahi said:
No, TWRP remains. Flash the full rom, flash magisk/su and reboot to recovery then to system.
And isn't this the simple basic procedure to flash the rom on a rooted device(?) I wonder how to used to do it before and also that you can find the latest rom update on downloads.oneplus.net - can't you?
Plus won't this trigger dm verity and encryption? Because I usually wait for the modified boot.img for the latest update which disables dm verity and forced encryption.
Click to expand...
Click to collapse
The DM Verity is usually okay because of magisk patching the boot image
counterfeit187 said:
The DM Verity is usually okay because of magisk patching the boot image
Click to expand...
Click to collapse
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?
DawoodSahi said:
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?
Click to expand...
Click to collapse
Yes, usually. Just make sure you don't let it reboot before you flash magisk or SuperSU
what if we have flashed a kernel?
DawoodSahi said:
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?
Click to expand...
Click to collapse
Yes, what @counterfeit187 said was right. I have personally tried it last night by flashing only magisk after the update and after the bootup my device is still unencrypted.
Ramith96 said:
what if we have flashed a kernel?
Click to expand...
Click to collapse
You mean you're currently on a custom kernel? If so just follow the exact procedures and flash back your kernel which is the "blablabla" in the instruction.
Diatomix98 said:
Yes, what @counterfeit187 said was right. I have personally tried it last night by flashing only magisk after the update and after the bootup my device is still unencrypted.
Click to expand...
Click to collapse
Yup I updated last night, just flashing the open beta 14 zip and magisk in TWRP before reboot.
counterfeit187 said:
Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct?
Click to expand...
Click to collapse
If you root before rebooting (after flashing the full update zip), TWRP will remain. If you don't root, it will overwrite TWRP with stock recovery.
The whole process is already described (and in better detail) here: https://forum.xda-developers.com/showpost.php?p=70084260&postcount=3
Although admittedly, the info is not that obvious to find.
---------- Post added at 11:48 AM ---------- Previous post was at 11:44 AM ----------
Diatomix98 said:
This is what I found accidentally by myself. It's been told countless time that we should not update through OTA if our phone is rooted which will most probably brick the phone. However there is actually an easy way to flash the OTA update
Click to expand...
Click to collapse
What is meant by this (the sentence I've highlighted in red font), is if you try to flash the "partial" or "patch" OTA (less than 1 GB), it will soft brick the phone (fixable if you flash the full update zip). Therefore, rooted and/or TWRP users should only flash the "full" update zip (> 1 GB).
If you get the update notification, the system should detect you have TWRP, and download only the full zip.
---------- Post added at 11:57 AM ---------- Previous post was at 11:48 AM ----------
Diatomix98 said:
If so just follow the exact procedures and flash back your kernel which is the "blablabla" in the instruction.
Click to expand...
Click to collapse
It's completely unclear what is meant by "blablabla"
If the intent is to post a useful tutorial, the steps should be clear for everyone.
When we flash again doesn't it replace the twrp with the stock recovery?
redpoint73 said:
What is meant by this (the sentence I've highlighted in red font), is if you try to flash the "partial" or "patch" OTA (less than 1 GB), it will soft brick the phone (fixable if you flash the full update zip). Therefore, rooted and/or TWRP users should only flash the "full" update zip (> 1 GB).
If you get the update notification, the system should detect you have TWRP, and download only the full zip.
---------- Post added at 11:57 AM ---------- Previous post was at 11:48 AM ----------
It's completely unclear what is meant by "blablabla"
If the intent is to post a useful tutorial, the steps should be clear for everyone.
Click to expand...
Click to collapse
Yep, you are right it was a misunderstanding as I have been reading quite some posts mentioning how their phones got bricked when updating through OTA. I should have understood the whole situation better, my bad here. That "blablabla" actually means other mods that we are flashing along like Arise Sound and etc which are neither important nor will they affect the update. Anyway, I am going to edit the op. Thanks for the advic though.
Ramith96 said:
When we flash again doesn't it replace the twrp with the stock recovery?
Click to expand...
Click to collapse
If by "it" you mean the recovery, then as it was mentioned a few posts earlier, NO, TWRP remains.
Unleashed by ONEPLUS 3T rooted
Diatomix98 said:
Yep, you are right it was a misunderstanding as I have been reading quite some posts mentioning how their phones got bricked when updating through OTA. I should have understood the whole situation better, my bad here.
Click to expand...
Click to collapse
No worries. I understand the confusion, as I agree the info in some threads isn't specific enough.
Diatomix98 said:
That "blablabla" actually means other mods that we are flashing along like Arise Sound and etc which are neither important nor will they affect the update. Anyway, I am going to edit the op. Thanks for the advic though.
Click to expand...
Click to collapse
You're certainly welcome. Again, your tutorial will most certainly be useful to a lot of folks; as it will make the info easier to find. So having the best info (and easy to understand) is good all around. :good:
---------- Post added at 08:57 AM ---------- Previous post was at 08:55 AM ----------
Ramith96 said:
When we flash again doesn't it replace the twrp with the stock recovery?
Click to expand...
Click to collapse
Already answered a couple times in this thread.
If you update and immediately root, TWRP will remain.
If you update, and don't root, then yes TWRP may be replaced with stock recovery.
failed
I tried that exact procedure but couldn't get past the boot animation for about half an hour so reverted back to the nandroid backup.
Note: I have the latest twrp and it worked on previous update but couldn't execute this time.
thesishir said:
I tried that exact procedure but couldn't get past the boot animation for about half an hour so reverted back to the nandroid backup.
Note: I have the latest twrp and it worked on previous update but couldn't execute this time.
Click to expand...
Click to collapse
Did you verify the downloaded update file was larger than 1 GB?
redpoint73 said:
Did you verify the downloaded update file was larger than 1 GB?
Click to expand...
Click to collapse
Yes I did! The file size is 1.43 gb to be exact but still no luck
thesishir said:
Yes I did! The file size is 1.43 gb to be exact but still no luck
Click to expand...
Click to collapse
Not sure why it's not booting. But you might try to download the full update again, and install in TWRP (wipe Dalvik and cache, then flash): http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
redpoint73 said:
Not sure why it's not booting. But you might try to download the full update again, and install in TWRP (wipe Dalvik and cache, then flash): http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
Click to expand...
Click to collapse
I have tried it several times with official downlaod provided by my phone and also with official op website but it tries to boot and freezes at the boot logo (the one where two dots follow each other) so I am here at last in a hope to fix this.
thesishir said:
I have tried it several times with official downlaod provided by my phone and also with official op website but it tries to boot and freezes at the boot logo (the one where two dots follow each other) so I am here at last in a hope to fix this.
Click to expand...
Click to collapse
Only other think I can think of, is to do a full wipe (data, Dalvik, cache - the default wipe in TWRP). But you may not like that.
Or make sure you are on latest TWRP 3.1.1-2, or reflash TWRP.
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
MissCherry1241 said:
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
Click to expand...
Click to collapse
Just use twrp to install SuperSU.
ashyx said:
Just use twrp to install SuperSU.
Click to expand...
Click to collapse
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
MissCherry1241 said:
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
Click to expand...
Click to collapse
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
ashyx said:
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
Click to expand...
Click to collapse
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
MissCherry1241 said:
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
Click to expand...
Click to collapse
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
ashyx said:
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
Click to expand...
Click to collapse
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
MissCherry1241 said:
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
Click to expand...
Click to collapse
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
ashyx said:
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
Click to expand...
Click to collapse
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
MissCherry1241 said:
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
Click to expand...
Click to collapse
What is your current firmware build?
ashyx said:
What is your current firmware build?
Click to expand...
Click to collapse
Right now I am on Android version 7.1.1
MissCherry1241 said:
Right now I am on Android version 7.1.1
Click to expand...
Click to collapse
No, please post the firmware build version in settings/about.
ashyx said:
No, please post the firmware build version in settings/about.
Click to expand...
Click to collapse
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
MissCherry1241 said:
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
Click to expand...
Click to collapse
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
ashyx said:
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
Click to expand...
Click to collapse
Goodie! I'll try that out now and come back to confirm whether or not it works
MissCherry1241 said:
Goodie! I'll try that out now and come back to confirm whether or not it works
Click to expand...
Click to collapse
OK. Ensure you make a note of what odin and the device screen reports.
ashyx said:
OK. Ensure you make a note of what odin and the device screen reports.
Click to expand...
Click to collapse
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
MissCherry1241 said:
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
Click to expand...
Click to collapse
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
ashyx said:
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
Click to expand...
Click to collapse
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
MissCherry1241 said:
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
Click to expand...
Click to collapse
Finally a proper confirmation.
Glad its worked for you. :good: You MAY be able to update to Nougat by flashing the stock firmware with FLASHFIRE.
Just ensure EverRoot is enabled.