Database Users

[Q] Lost TWRP and root - Help needed

Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.

Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
tigas68 said:
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Click to expand...
Click to collapse

spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
thanks. :good:

tigas68 said:
thanks. :good:
Click to expand...
Click to collapse
Still isn't working...
When i tried to fastboot the recovery img the device turns off and never turns on again on is own!
Help please!
I like my root...!

here's the screens of waht happens.
This his what happens when i try to go into recovery mode...

first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip

I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.

zephiK said:
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
Click to expand...
Click to collapse
zephiK,
Already done that! I flashed the CWM recovery throught fastboot. The device turned off. When i turn it on again and tried to go into recovery mode, so i can flash the SU from chain fire, but got the image on my post!
The phone is unlocked!

That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!

Johnsonyc said:
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
Click to expand...
Click to collapse
I used the sctock rom downloaded from the google developers website!

Johnsonyc said:
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Click to expand...
Click to collapse
What he said. The recovery flash isn't going through.
Sent from my Nexus 4 using Tapatalk 4 Beta

Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world

spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.

kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.

kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Johnsonyc said:
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
Click to expand...
Click to collapse
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:

sn0warmy said:
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
Click to expand...
Click to collapse
I don't even really use root explorer anymore just like having the ability to make nandroid backups. But after doing a clean install of 4.3 in fastboot and it only took 30 minutes from start to finish including app and data restores nandroids to me are not that useful anymore (I don't flash custom ROMs anymore). Google automatically re-installed all my apps as soon as I reconfigured my WIFI, they also restored my APN and my work WIFI settings but not Bluetooth. And I used Helium to restore the user app data and all my texts and helium doesn't need root access to work.
Here is the start of Koush's post on Google+ where he talks about superuser on 4.3.
I finally had a chance to dig into seeing why Superuser is broken on Android 4.3. https://android.googlesource.com/platform/dalvik/+/9907ca3cb8982063a846426ad3bdf3f90e3b87c2
Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc.
This is a pretty nasty change. It seems that SuperSU works around this by replacing install-recovery.sh to run a su daemon that pipes subsequent through it. Pretty hacky, but understandable why it was done this way.
Will need to look into how to do this in a less invasive fashion, if that is even possible. Of course, if building from source, this change can simply be reverted.

Here's a better explanation about superuser from Android Police.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/

Rooting for me is used for restoring my apps and stuffs using titanium backup. Another useful thing about rooting is the ability to check saved wifi passwords.

Just install twrp from fastboot and then flash the su zip file in twrp
Sent from my Nexus 4 using Tapatalk 2

EddyOS said:
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
Click to expand...
Click to collapse
@EddyOS
Your answer is what forums are not about! Instead of helping you had an atitude of an ass...!
@ Everyone else
After 5 or 6 attemps, doing it by the book, the CWD worked and i now have a Recovery mode! I didn´t did anything different, so i couldn´t really understand what went wrong before... SU from chainfire works perfectly! It´s now Rooted! And yes, the tuturials are idiot proof!
There´s something that´s bothering my mind... I can´t unistall some trash that cames with the 4.3 version using titanium backup, because he can´t find the apk files...! I could do it with the 4.2.2 version, but not with this one. I'm using the deoxed version.
Does anyone has the same problems?

How to restore IMEI number on a official rom?

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??

Stuck On bootanimation

No matter what custom firmware i flash it always is stuck on the boot animation, Ive left it booting for 5 hours today and it never reached the setup screen, just constant booting, I erase EVERYTHING everytime I go to twrp, except for my internal and external storage. Aswell as If i flash/restore my stock rooted and unrooted firmware, it does boot, but NO wifi or data works, even with the removal and reinsertion of the simcard. Please help. If i didnt explain it well enough i can reply and add more detail.

DeliriousHD said:
No matter what custom firmware i flash it always is stuck on the boot animation, Ive left it booting for 5 hours today and it never reached the setup screen, just constant booting, I erase EVERYTHING everytime I go to twrp, except for my internal and external storage. Aswell as If i flash/restore my stock rooted and unrooted firmware, it does boot, but NO wifi or data works, even with the removal and reinsertion of the simcard. Please help. If i didnt explain it well enough i can reply and add more detail.
Click to expand...
Click to collapse
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.

ccic2491 said:
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.
Click to expand...
Click to collapse
Ill try that. Ill report back if it works or fails.

ccic2491 said:
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.
Click to expand...
Click to collapse
It did not work, Keeps saying "Could not find 'meta-inf/com/google/android/update-binary' in zip file.

DeliriousHD said:
It did not work, Keeps saying "Could not find 'meta-inf/com/google/android/update-binary' in zip file.
Click to expand...
Click to collapse
One thing to try is formatting the internal storage to make sure you have a clean start. TWRP wipes /data without wiping userdata by default; to completely wipe the internal storage you have to go into the format data wipe where you must type "yes" to confirm instead of a slider. Sometimes leftover files can cause permissions problems and roms fail to boot. It is more common on other phones than this one, but I've seen some people report your problem before here too.
If you do this, obviously make sure you back up all the files you care about on internal storage to a microSD or off device. Also make sure you have rom/gapps to flash and a working TWRP backup stored on a microSD, or you've verified you can USB copy with MTP or adb push files from a computer to your phone before formatting. Don't find out after wiping and formatting that your computer is missing something it needs to copy files to your phone properly when your phone is booted into TWRP, test it first if you're going this route. Otherwise you could be stuck with a blank phone and nothing to flash on it.
I do this every once in a while just to keep internal storage from getting too cluttered from chronic flashing; just be careful about how you go about it.

Okay, I can try that.

jason2678 said:
One thing to try is formatting the internal storage to make sure you have a clean start. TWRP wipes /data without wiping userdata by default; to completely wipe the internal storage you have to go into the format data wipe where you must type "yes" to confirm instead of a slider. Sometimes leftover files can cause permissions problems and roms fail to boot. It is more common on other phones than this one, but I've seen some people report your problem before here too.
If you do this, obviously make sure you back up all the files you care about on internal storage to a microSD or off device. Also make sure you have rom/gapps to flash and a working TWRP backup stored on a microSD, or you've verified you can USB copy with MTP or adb push files from a computer to your phone before formatting. Don't find out after wiping and formatting that your computer is missing something it needs to copy files to your phone properly when your phone is booted into TWRP, test it first if you're going this route. Otherwise you could be stuck with a blank phone and nothing to flash on it.
I do this every once in a while just to keep internal storage from getting too cluttered from chronic flashing; just be careful about how you go about it.
Click to expand...
Click to collapse
I did this and its still stuck on boot. Im trying to flash AICP

DeliriousHD said:
I did this and its still stuck on boot. Im trying to flash AICP
Click to expand...
Click to collapse
It was worth a try. What bootloader and twrp version are you using?

jason2678 said:
It was worth a try. What bootloader and twrp version are you using?
Click to expand...
Click to collapse
regular bootloader for the xt1575 I havent chnged it, and twrp 3.0.2-0

DeliriousHD said:
regular bootloader for the xt1575 I havent chnged it, and twrp 3.0.2-0
Click to expand...
Click to collapse
TWRP 3.1 is out. I doubt that's your problem since you're flashing successfully and failing to boot, but updating recovery is something else to check off the list.
Are you on the L or M bootloader? It changed. Just looking for anything that might be causing the trouble.
Code:
getprop ro.bootloader
returns 0xA04C for me, and aicp is working good.

jason2678 said:
TWRP 3.1 is out. I doubt that's your problem since you're flashing successfully and failing to boot, but updating recovery is something else to check off the list.
Are you on the L or M bootloader? It changed. Just looking for anything that might be causing the trouble.
Code:
getprop to.bootloader
returns 0xA04C for me, and aicp is working good.
Click to expand...
Click to collapse
I think im on L but do i just put that in cmd when in bootloader? I also just updated twrp to 3.1 just now.
EDIT: I actually cant even do that in cmd.

DeliriousHD said:
I think im on L but do i just put that in cmd when in bootloader? I also just updated twrp to 3.1 just now.
Click to expand...
Click to collapse
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.

jason2678 said:
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.
Click to expand...
Click to collapse
I just tried putting that into terminal and it does nothing.

jason2678 said:
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.
Click to expand...
Click to collapse
also BL: A0.1C (SHA-E29F91E, 2015-7-28 16;16;36)

DeliriousHD said:
I just tried putting that into terminal and it does nothing.
Click to expand...
Click to collapse
Well that's odd

jason2678 said:
Well that's odd
Click to expand...
Click to collapse
In your code you put to not ro XD

jason2678 said:
Well that's odd
Click to expand...
Click to collapse
Mine is 0xa01C

DeliriousHD said:
also BL: A0.1C (SHA-E29F91E, 2015-7-28 16;16;36)
Click to expand...
Click to collapse
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.

jason2678 said:
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.
Click to expand...
Click to collapse
Which thread? I can go looking but ive been to so many its confusing how to use the files.

jason2678 said:
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.
Click to expand...
Click to collapse
This thread https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 Shows a couple firmwares. but idk if i should get MPH24.49-18 , MPH24.49-18-3 or MPH24.49-18-4

unlock system file after root?

I have the phone rooted and bootloader unlocked. i still cannot modify the /system files. it's gives an error when changing permissions in a root explorer.

rmyc said:
I have the phone rooted and bootloader unlocked. i still cannot modify the /system files. it's gives an error when changing permissions in a root explorer.
Click to expand...
Click to collapse
This goes on Questions and Answers
You can fix it easily with a command. I assume that you have ADB on your computer, if not download the 15 seconds ADB installer
Connect your phone to your computer, enable USB debugging. Open CMD with admin privileges (just in case). Issue 'adb devices', if the phone appears, you're good to go. Otherwise check that the phone is unlocked, do it again, and allow the connection if a dialog appears.
Issue 'adb reboot disemmcwp' and you should be done

thanks alot, i really appreciate it. now i just need to figure out the delayed whatsapp msgs and this phone will be perfect

rmyc said:
thanks alot, i really appreciate it. now i just need to figure out the delayed whatsapp msgs and this phone will be perfect
Click to expand...
Click to collapse
Oh I hate that. The only fix I found was to reinstall the system (full wipe, then reinstall). If you find a way to fix it without doing thay, please tell!

Full system? Do you know which version.? I'm on marshmallow B29

rmyc said:
Full system? Do you know which version.? I'm on marshmallow B29
Click to expand...
Click to collapse
You obviously have to wipe everything. Use DrakenFX's files if you have an A2017U (over at the custom stuff thread). The version numbers are so different that I have no idea what Nougat for the U is...

Choose an username... said:
You obviously have to wipe everything. Use DrakenFX's files if you have an A2017U (over at the custom stuff thread). The version numbers are so different that I have no idea what Nougat for the U is...
Click to expand...
Click to collapse
are you on nougat? because nougat is fine but i'm required to run marshmello

rmyc said:
are you on nougat? because nougat is fine but i'm required to run marshmello
Click to expand...
Click to collapse
Okay use DrakenFX's M zips instead, it's the same

Unsure what I did

but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?

ms.journie said:
but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?
Click to expand...
Click to collapse
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.

Omg this saddens me! So there's no way I am unable to at least retrieve my pictures?
Scott said:
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.
Click to expand...
Click to collapse

Have u tested change boot partition ?

yup
J3zz said:
Have u tested change boot partition ?
Click to expand...
Click to collapse

ms.journie said:
yup
Click to expand...
Click to collapse
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code

I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
J3zz said:
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code
Click to expand...
Click to collapse

ms.journie said:
I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
Click to expand...
Click to collapse
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?

Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
J3zz said:
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?
Click to expand...
Click to collapse

ms.journie said:
Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
Click to expand...
Click to collapse
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ? Then boot and uninstall the "****in" fantastic module... maybe it works

I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
J3zz said:
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ?
Click to expand...
Click to collapse

ms.journie said:
I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
Click to expand...
Click to collapse
Good luck !!

I saw this happen when I used the official TWRP app.
It went away when I used this TWRP. Hope that helps.

I'm glad you already know not to use the MSM tool. Too many people jump straight to this.....
You just need to boot the correct recovery and your data will decrypt, and you will be able to back it up to a PC, then you can reload your ROM via TWRP or Fastboot to get the phone bootable again. So now it's a question of what ROM were you running before. Do you need a recovery with the latest security patch or something older? What TWRP are you running. Try 3.3.1-6 psychen6 linked too first. Boot that image from Fastboot. See if your password/pin will work to decrypt your data.