Develop Bugs

[Q] Explanation Needed (Post-Root to Un-Root)

Okay, so I've just rooted my Nexus 7 tablet after being told a custom ROM would fix my GPS issues with my N7v2. I'm familiar with the rooting process, having done it to my HTC One. I rooted it successfully, installed the SuperSU and TWRP. Everything went smoothly, and then I realized, only minutes later, after browsing XDA, that Google JUST released an OTA to fix the issues.
So I browsed around and found this post: http://forum.xda-developers.com/showpost.php?p=44888268&postcount=97&nocache=1&z=675614455249160
I followed the instructions. I opened a CMD in the correct folder and ran the flash-all.bat. It ran... HOWEVER it generated a few errors. The errors in CMD were that it was unable to find files that are contained within the img-razor-jss15q.zip folder that was inside the downloaded TGZ archive. When I finally figured out how to use 7zip (never had a use for it before now), I ended up with a folder that looked like this (which is where I ran the CMD):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see the image-razor-jss15q.zip was still inside that folder. I did not unzip it because I didn't know if I was supposed to or not.
At any rate, the tablet SEEMS to be fine. I rebooted into the bootloader and then to recovery and got the android with an exclamation mark which is what I ASSUME I'm supposed to have. TWRP is gone, at least.
I also looked at the system information and it's showing the build number as JSS15Q.
So my questions are simple:
1. Did I do this correctly and are the errors normal?
2. If "no" to 1, what do I need to do to fix it?
Edit: It appears I've put this in the wrong section, I apologize. I'd appreciate it if a moderator moved it for me. Thanks!!

Your first error was not correct but you figured it out and the next time around it was done right. If your tablet says JSS15Q then you successfully installed it
Twrp gone means the stock recovery in the image zip flashed correctly

Seems you've already answered your own question.
The guide could have probably better explained to extract the actual image files to your ADB/Fastboot folder.
I prefer to reflash the relevant images individually with
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase system
fastboot flash system system.img
fastboot erase data
fastboot flash data data.img
fastboot erase cache
fastboot flash cache cache.img
I exclude the bootloader image when reflashing unless necessary due to the remote chance of bricking your device if it fails to flash completely.
http://forum.xda-developers.com/showthread.php?t=2404833

sfhub said:
Your first error was not correct but you figured it out and the next time around it was done right. If your tablet says JSS15Q then you successfully installed it
Twrp gone means the stock recovery in the image zip flashed correctly
Click to expand...
Click to collapse
Ah! The OP of that useful information! Thank you for that!
At any rate, regardless of the error, it still managed to work correctly. Still, though, while waiting for a response I figured "Well, I can just redo it but after extracting the relevant files to the main folder. This time it did not give me that set of errors but instead gave me these:
http://i.imgur.com/k6Mgn2I.png
I could not find those files anywhere in the included files so I'm not really worried about it because at this point the tablet seems to be working fine.

Username invalid said:
Seems you've already answered your own question.
The guide could have probably better explained to extract the actual image files to your ADB/Fastboot folder.
I prefer to reflash the relevant images individually with
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase system
fastboot flash system system.img
fastboot erase data
fastboot flash data data.img
fastboot erase cache
fastboot flash cache cache.img
I exclude the bootloader image when reflashing unless necessary due to the remote chance of bricking your device if it fails to flash completely.
Click to expand...
Click to collapse
Well I wouldn't have rooted it in the first place had I known about the OTA. Regardless, I'm not sure what you mean by "you answered your own question"...?
I really don't care about the method so long as it works. I'm not actually interested in rooting this tablet, really. I love it as-is. I'll reserve all my tweaking for my phone.

Just a heads up for anyone who has TWRP or CWM installed, you can use this flashable .zip to update to latest OTA update. Download update. Reboot to recovery. Wipe Cache/Dalvik. Flash .zip. Reboot and you're done. Worked pefectly on mine and you won't lose your recovery in the process.
Edit: Just wanted to point out, this is obviously for those running stock ROM.

railed said:
Just a heads up for anyone who has TWRP or CWM installed, you can use this flashable .zip to update to latest OTA update. Download update. Reboot to recovery. Wipe Cache/Dalvik. Flash .zip. Reboot and you're done. Worked pefectly on mine and you won't lose your recovery in the process.
Click to expand...
Click to collapse
Hey cool, thanks for that! I'm sure people will find this useful!

wolfbuck22 said:
Well I wouldn't have rooted it in the first place had I known about the OTA. Regardless, I'm not sure what you mean by "you answered your own question"...?
I really don't care about the method so long as it works. I'm not actually interested in rooting this tablet, really. I love it as-is. I'll reserve all my tweaking for my phone.
Click to expand...
Click to collapse
You can still receive OTAs with root. You just need to reflash the stock recovery which only takes a few seconds.
wolfbuck22 said:
It ran... HOWEVER it generated a few errors. The errors in CMD were that it was unable to find files that are contained within the img-razor-jss15q.zip folder that was inside the downloaded TGZ archive.
At any rate, the tablet SEEMS to be fine. I rebooted into the bootloader and then to recovery and got the android with an exclamation mark which is what I ASSUME I'm supposed to have. TWRP is gone, at least.
I also looked at the system information and it's showing the build number as JSS15Q.
So my questions are simple:
1. Did I do this correctly and are the errors normal?
Click to expand...
Click to collapse

Username invalid said:
You can still receive OTAs with root. You just need to reflash the stock recovery which only takes a few seconds.
Click to expand...
Click to collapse
I only tried the flash-all.bat once. It ran with the errors. Tablet still worked even with errors. Had regular recovery back and everything.
Though, I wasn't satisfied so I went back and unzipped those files to the main folder and re-ran the flash-all.bat again. That time it gave me a different set of errors but the tablet seems to be working just fine so I'm not exactly worried about it.

wolfbuck22 said:
Ah! The OP of that useful information! Thank you for that!
At any rate, regardless of the error, it still managed to work correctly. Still, though, while waiting for a response I figured "Well, I can just redo it but after extracting the relevant files to the main folder. This time it did not give me that set of errors but instead gave me these:
http://i.imgur.com/k6Mgn2I.png
I could not find those files anywhere in the included files so I'm not really worried about it because at this point the tablet seems to be working fine.
Click to expand...
Click to collapse
Those missing .sig files are expected. Google did not sign their factory restore images which is why you need an unlocked bootloader to flash them

sfhub said:
Those missing .sig files are expected. Google did not sign their factory restore images which is why you need an unlocked bootloader to flash them
Click to expand...
Click to collapse
Great. Thank you so much, everything appears to be working fine at this point.
I may venture into the custom ROM realm later but for now I'm quite happy with the Nexus 7's stock ROM (never had a pure Android device before).

Bricked ZL550 - Any ideas?

I bricked my U.S. market ZL550 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl

ConnCarl said:
I bricked my U.S. market ZL551 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl
Click to expand...
Click to collapse
I'm surprised!! Why do you need link2sd??? with 32 GB Internal, I have 118 Apps installed along with movies and music. Still I have space( I have not used SD Card).
Anyways,
From what you mentioned, you seem to have a ZE551ML. And you Installed Z008-WW-2.18.40.7. It should be Z00A and not Z008. Please download the correct firmware and try out.:good:
Thumb-rule,
ZE550ML = Z008
ZE551ML = Z00A
I guess thats what you did Wrong

Thanks for pointing that out! It's actually a 16GB 550.

I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload

ConnCarl said:
Thanks for pointing that out! It's actually a 16GB 550.
Click to expand...
Click to collapse
for MOFD_SDUPDATE.zip to work, you need to place it on the external sd card and reboot into recovery. It will automatically start to install.
Placing it on the Internal card wont help.
---------- Post added at 08:58 AM ---------- Previous post was at 08:57 AM ----------
lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
I wouldnt recommend that.
He is unable to use adb properly. And if he messes up something, he might even lose his warranty

lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
Tried all that. Many times.

ConnCarl said:
Tried all that. Many times.
Click to expand...
Click to collapse
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.

godgib said:
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.
Click to expand...
Click to collapse
I can't sideload the image, because I can't connect with ADB.

ConnCarl said:
I can't sideload the image, because I can't connect with ADB.
Click to expand...
Click to collapse
but you can get into recovery, it's just when you click on "ADB update" your computer doesn't see the phone, that's my understanding...

Right, correct. I can get into recovery, and fastboot works, but not ADB.

ConnCarl said:
Right, correct. I can get into recovery, and fastboot works, but not ADB.
Click to expand...
Click to collapse
It sounds like you still in fastboot and not recovery. This is what recovery looks like and then you put in it "Apply update ADB sideload."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.

ConnCarl said:
Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.
Click to expand...
Click to collapse
I'm pretty sure if it timse out using ADB sideload then it should also timeout when you type ADB deviecs, but try it you should see your serial number sideload.... If you don't then
1. Make sure you have ADB 1.42 with intel drives 1.9
2. Use the stock cable.
3. In device manager make sure there's no unknown Android devices.
4. if ADB still doesn't work then try and flash via fast boot a new boot.img and recovery.img.
5. If you do get to the point where you can sideload...
6. Downloaded the ASUS firmware with WW not CN.
7. Also make sure the firmware package doesn't have ext .zip.zip, because of unknown file ext in windows.

Not sure if this works but you can give it a try.
Have you boot it with Temp CWM?
Delete all cache, including those of under advanced section
install zip file should work to install your full rom. since you stated you cant adb to detect.

Thanks everyone for all the suggestions!
I was just sort of reviewing godgib's screen grab when it slowly dawned on me that at least part of the solution had been staring me in the face all along.
It had never occurred to me that adb might not be able to connect even though fastboot could. Then when I read "you need adb 1.0.32 or newer to sideload to this device", it started to make sense. I upgraded adb and connected but still couldn't sideload. After reviewing godgib's methodical list, I realized it was a driver problem. Once I squared that away, sideload went without a hitch.
Interesting side note...I don't know what build I had originally, but it had to be at least a month old or so. I figured I might as well get the latest release, so I went with Z008_WW_2.18.40.7, and I updated boot/droidboot/recovery while I was at it. The funny thing was that when it booted, it was set for 250 dpi and everything was tiny.
Luckily, since adb was finally working (thanks again godgib) I was able to send "adb shell wm density 480" to put it back to normal.
Thanks again, everyone!
Carl

Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app

godgib said:
Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
Appreciate that.
Of course now auto-rotate is borked. I'll have to either wait for a patch or downgrade.

Did you ever figure out the sdcard problem? I just got the same card and want to do the same thing. But the phone wont see the second partition at all.

i have similar problem too

[Updated 9/23/2015] A hard bricked N1! Please help me to find the solution!

Hi there I bought Chinese version of N1 and flashed with Taiwan system.img which was great everything was awesome~!
but somehow I was curious what would happen if I install layer manager onto N1 that triggered tragedy of hard brick incident of owning N1 within 3 days. After I install some layer it asked me to reboot to apply the layers so I did and bootloop started.
I could see my tablet as MTP and ADB at that time so I could use ADB command to get bootloader but I couldn't get into recovery so I dug more around on xda-forum and installed it. Some said factory reset will fix all my issues especially bootloop so I didn't worry about what I was doing pressed couple time to navigate Yes factory reset/wipe all in stock recovery mode.
After it wiped it all I didn't know that the bootloop is still exist but I can't find my tablet in computer as ADB anymore but moorefield device with unknown driver exclamation mark so I googled more some suggest to use Intel Phone Flash tool.
So I could install right driver for moorefield also I could navigate the N1 as some device so I can flash something into tablet but I need components to fresh install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes I'm stuck on here now please help or command me what to do!!
updated 09/05/2015 - Still waiting for solution now I will donate who will find out unbrick my N1 through paypal donation. Please help me out!
updated 09/23/2015 - Couldn't find help from anyone so I ordered one more N1 from now, is there any possible to use the data from new tablet to flash or install onto bricked tablet? I heard linux or ubuntu can connect the bricked N1 even it only shows the tablet as MTP on Windows which I can't even see the device's file or folder. Also Intel phone flash tool doesn't support N1 yet and there are nothing possible without ADB connection on Windows which is probably many boot-loop users have the issue.

i'm here with you, same problem T_T, havent got a solution
---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------
i found dnx and ifwi firmware in Ifwi.zip , but it can not flash

kaikool said:
i'm here with you, same problem T_T, havent got a solution
---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------
i found dnx and ifwi firmware in Ifwi.zip , but it can not flash
Click to expand...
Click to collapse
Can you give links to these files?

you can download and extract your firmware, here: http://forum.xda-developers.com/showpost.php?p=59750742&postcount=2 , you'll see ifwi.zip. Extract it, then you'll find 4 files:
1.bom-token_ann_a0-mofd_v1-N1.bin, => i dont know
2.dnx_fwr_ann_a0-mofd_v1-N1.bin, => dnx firmware (guess)
3.ifwi_ann_a0-mofd_v1-N1.bin, => iwifi firmware (guess)
4.version => i dont know

daion said:
Hi there I bought Chinese version of N1 and flashed with Taiwan system.img which was great everything was awesome~!
but somehow I was curious what would happen if I install layer manager onto N1 that triggered tragedy of hard brick incident of owning N1 within 3 days. After I install some layer it asked me to reboot to apply the layers so I did and bootloop started.
I could see my tablet as MTP and ADB at that time so I could use ADB command to get bootloader but I couldn't get into recovery so I dug more around on xda-forum and installed it. Some said factory reset will fix all my issues especially bootloop so I didn't worry about what I was doing pressed couple time to navigate Yes factory reset/wipe all in stock recovery mode.
After it wiped it all I didn't know that the bootloop is still exist but I can't find my tablet in computer as ADB anymore but moorefield device with unknown driver exclamation mark so I googled more some suggest to use Intel Phone Flash tool.
So I could install right driver for moorefield also I could navigate the N1 as some device so I can flash something into tablet but I need components to fresh install.
Yes I'm stuck on here now please help or command me what to do!!
updated 09/05/2015 - Still waiting for solution now I will donate who will find out unbrick my N1 through paypal donation. Please help me out!
Click to expand...
Click to collapse
How to flash the Taiwan system. img . I need your help .

Velunce said:
How to flash the Taiwan system. img . I need your help .
Click to expand...
Click to collapse
soondin said:
Thank you for your upload.
I was successfully change to taiwan version.
I use ADB Shell and restore use your file.
My one's build number be A5FM51C.
If any chinese version user already rooted N1.
May be can change from china to taiwan.
1. Move system.img to N1's internal storage
2. ADB shell (enabled debug mode)
3. SU (need accept at your N1)
4. dd if=/sdcard/system.img of=/dev/block/pci/pci0000:00/0000:00:01.0/by-name/system
(/pci/pci0000:00/0000:00:01.0 is my one's directory name but I don't know other N1 is same or not)
5. wait some minute. until done shell command.
6. ignore some error message.
7. exit su and adb shell
8. reboot to recovery (adb reboot recovery)
9. wipe cache.
10. reboot N1 and it will update.
I don't try wipe data partion at recovery.
Cause My one is A5CN51C.
I will make some more screen shot like can find google Chrome at playstore.
Click to expand...
Click to collapse
I followed the way it's in Nokia N1 general forum.

daion said:
I followed the way it's in Nokia N1 general forum.
Click to expand...
Click to collapse
I would not recommend any further, i have flashed alot with that program (custom flashing) as i had the layers theme brick too, and after like 30 flashings of recovery, system, iwifi etc (flashed but without success) my bootloader now shows a locked state where i cannot flash anything anymore (i was on 5.0.2 but i wiped my system by accident instead of factory reset to recover from layer theme), so don't flash to much or to reckless as this will lock down your nokia completly like mine. (I now regret buying it though)

adb/twrp issues....

Firstly, when plugging my 7t in to my windows 10 PC, I am asked to choose which mode to go in within usb preferences, as I did previously in order to achieve and ADB driver connection I chose file transfer.......
this didn't work for some reason, only when in MIDI did I get a confirmation with adb devices.....even though there is still no sign of adb interface in device manager.....
any ideas? I can get adb connection with MIDI but is this good enough to flash recoveries/boot images etc....?
I tried to flash twrp and I could successfully boot into twrp directly via fastboot but twrp couldn't seen any of my storage, despite having all security methods turned off...
all i want to do is gain root access but I am having no joy....
ever since android 10 rooting anything for me has been a pain in the ass......truly fed up....it shouldn't be this hard......
I also flashed a patched boot image in an attempt to gain root access but it all did was break my wifi........which i fixed by copying over the latest image and installing locally......
please HELP....

Everything about this issues is already said in this forum.

Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961

ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
sweet, ill check it out.....

ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?

mediaman123 said:
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?
Click to expand...
Click to collapse
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root

Josh McGrath said:
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root
Click to expand...
Click to collapse
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..

mediaman123 said:
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..
Click to expand...
Click to collapse
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

fawazahmed0 said:
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
Click to expand...
Click to collapse
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..

mediaman123 said:
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..
Click to expand...
Click to collapse
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp

fawazahmed0 said:
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp
Click to expand...
Click to collapse
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....

mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access

fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?

mediaman123 said:
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?
Click to expand...
Click to collapse
it wipe's the data

mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
TWRP is not functional at the moment, so stay away from it.
The only way to root right now is to use the patch boot image method.

Lossyx said:
No don't do this.... This is not about encryption at all. It's about the major partitioning changes that has happened in Android 10. Wiping the system will just make everything worse.
Avoid using TWRP at all.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Oh, I didn't know this phone was on Android 10, Thanks for letting me know.
TWRP doesn't support Android 10 yet.
You can see it here
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Actually there is a twrp compiled for this phone, but that doesn't work , you can see the messages in thread:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
The steps I told, was for Android 9 and earlier devices, I assumed, this is an old device.
@mediaman123, So please wait, until twrp starts supporting the Android 10.
And for rooting, I am not sure, whether magisk supports this new phone or not.
Maybe @Lossyx can help you on that.

https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...

mediaman123 said:
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...
Click to expand...
Click to collapse
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
So if it boots an older image successfully I can move it over to the phone to patch to then flash it or use the already patched one and flash that...?..

Question Red Warning and UnWorking Lockscreen. HELP

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)

Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...

redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?

Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely

i have this error also what should i do?
the phone not boot up
the red warning are stuck

yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot

[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.

[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!

yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.

[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!

turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"

izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!

[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.