Database Users

[Q] Nexus 7 (4.1.2) can't root

Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message

IAmNice said:
usb debugging on? Have you checked that?
Click to expand...
Click to collapse
Hi. Yes mam (usb debugging on) have a look to the attachment.
Toolkit me boot into fastboot then reboot then for something to fastboot loaded and back to android and trying to upload the files but nothing superuser is not recorded because of (read-only file system).
have a look on the attachment is there to see everything ...

yep same issue here - problem with the forum regs is unless you have enough posts you can't actually address the issue to the appropriate person can you? Anyway, able to unlock but then is unable to root and rest due to a permissions problem. have tried as administrator but of coure this doesn't make any difference.

NexusTropers said:
Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message
Click to expand...
Click to collapse
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.

try:
http://forum.xda-developers.com/showthread.php?t=1796109

comminus said:
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.
Click to expand...
Click to collapse
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.

bazabaza said:
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.
Click to expand...
Click to collapse
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.

comminus said:
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.
Click to expand...
Click to collapse
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.

NexusTropers said:
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
Click to expand...
Click to collapse
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
NexusTropers said:
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.
Click to expand...
Click to collapse
I'm not really sure what you're trying to say...

I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.

comminus said:
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
I'm not really sure what you're trying to say...
Click to expand...
Click to collapse
1. THX u i try it.
2. AH sorry translator make crazy text.
homerbrew said:
I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.
Click to expand...
Click to collapse
Oki THX u i try this tool...

I'm also having this same problem but here's my story:
Using the Nexus 1.5.4 Toolkit, I Unrooted + Flashed jzo54k, success. I locked OEM, success. I unlocked again, success. Then I ran the root process again, and it keeps freezing at the android recovery screen. Following the prompt in the toolkit, I walked away for a few hours hoping time would resolve the issue.
If you're wondering why I unlocked + rooted, and decided to unroot, lock, unlock, and root again, its because I'm super-noob to anything android related after version 1.5, I wanted to learn the processes after I found out I was having troubles with certian things after my Nexus 7 updated from 4.1 to 4.1.2

I am having the same issue as you. 4.1.2 is not rooting for me. I can't install CWM or TWRP because it needs to rename recovery files, and to do that you need to be rooted. If I boot in recovery I always get stock

Having the same issue with a stock 4.1.2. I can unlock no problem but I cannot get it rooted. Everything appears to have worked, but it is not rooted. If I revert back to 4.1.1 I can unlock, root, etc. without issue. I was able to root 4.1.1 and use the root keeper app to then update to 4.1.2 and I was rooted still. However, it would not let me install CWM or anything. ROM Manager says it was installed, but booting to recovery always too me to stock.
Any ideas?

Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app

MetalMadness said:
Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I used Nexus Root Toolkit v1.5.4 and selected the "Flash Stock + Unroot" option. When prompted I choose the default 4.1.1 option and away it went.

To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.

hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!

hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Indy1204 said:
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!
Click to expand...
Click to collapse
Thanks. I did this earlier and it didnt work, but I checked boot instead of flash
FLASH THE OLDER BOOTLOADER DON'T BOOT IT!!!

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

Nexus 10 stuck at Fastboot Mode....I think

I have a Samsung Google Nexus 10 (Wi-Fi) GT-P8110HAAPHE Which was running Android 4.4.3 (I think but it is definitely the latest version) and I simply wished to root it.
I started following a video on Youtube and now I am stuck at what I think is called the Fastboot mode where My options are to scroll through START/RECOVERY MODE/RESTART BOOTLOADER/POWER OFF. I was using the Wugs Nexus Root Toolkit v1.8.3.
No matter which I select it returns me to the screen with the START option. When I select POWER OFF it does indeed power off but when I switch it on again it returns to the fastboot mode START option. I can get into download mode if that helps.
I did create a backup but cannot restore it.
I have done some research and downloaded the Android SDK Suite and fastboot/ADB and drivers etc ready to try and recover but I don't know where to start.
I have a Samsung Galaxy S3 which I have rooted and installed a number of different ROMS on so I am familiar with rooting but not sure if I can use Odin or something similar.
I think I have included all the information I have and hope someon can assist.
Thanks.

matrixmainframe said:
I have a Samsung Google Nexus 10 (Wi-Fi) GT-P8110HAAPHE Which was running Android 4.4.3 (I think but it is definitely the latest version) and I simply wished to root it.
I started following a video on Youtube and now I am stuck at what I think is called the Fastboot mode where My options are to scroll through START/RECOVERY MODE/RESTART BOOTLOADER/POWER OFF. I was using the Wugs Nexus Root Toolkit v1.8.3.
No matter which I select it returns me to the screen with the START option. When I select POWER OFF it does indeed power off but when I switch it on again it returns to the fastboot mode START option. I can get into download mode if that helps.
I did create a backup but cannot restore it.
I have done some research and downloaded the Android SDK Suite and fastboot/ADB and drivers etc ready to try and recover but I don't know where to start.
I have a Samsung Galaxy S3 which I have rooted and installed a number of different ROMS on so I am familiar with rooting but not sure if I can use Odin or something similar.
I think I have included all the information I have and hope someon can assist.
Thanks.
Click to expand...
Click to collapse
This is why I tell people not to use toolkits. Since everything is automated, it's hard to tell what went wrong and where. When it comes to Nexus devices, toolkits are entirely unnecessary IMO. These Nexus devices are so super simple to flash manually it's ridiculous. /END RANT
Okay. Sorry about that. Now, back to the issue at hand. The menu you are describing is, in fact, the Bootloader (aka Fastboot mode). Prior to using the NRT, were you completely stock? Was your bootloader already unlocked? To me, it sounds like you may have wiped your OS. Have you tried flashing the 4.4.3 factory image?

I was completely stock. Whilst using NRT I believe I had just succeeded in unlocking the Bootloader and the video then stated that with 4.4.3 a Factory reset was required which is what I did but I did not realise that deleted the O2. I thought that was on a protected partition like my S3 phone.
I can't flash the factory image as I can't get into recovery or is there another way of doing it?
I suppose where tablets are concerned I'm a book but if you could point me to any instructions on how to flash manually I'm hoping I can recover my tablet. Thanks.
Sent from my GT-I9300 using Tapatalk

Sorry, predictive text is rubbish. O2 should read OS and last paragraph I'm a book should read I'm a noob
Sent from my GT-I9300 using Tapatalk

matrixmainframe said:
I was completely stock. Whilst using NRT I believe I had just succeeded in unlocking the Bootloader and the video then stated that with 4.4.3 a Factory reset was required which is what I did but I did not realise that deleted the O2. I thought that was on a protected partition like my S3 phone.
I can't flash the factory image as I can't get into recovery or is there another way of doing it?
I suppose where tablets are concerned I'm a book but if you could point me to any instructions on how to flash manually I'm hoping I can recover my tablet. Thanks.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Dont know how you got your os erased. But im using a custom recovery since I got mine so maybe the stock recovery erses the os when doing a factory reset. A factory image cant be flashed via recovery and must be flashed via fastboot. Its really easy. But it will wipe the entire device. If you dont want to wipe everything you need to edit it..
Sent from my Galaxy Nexus using XDA Free mobile app

Cannot access Recovery Mode. Can Access Download Mode!
mrgnex said:
Dont know how you got your os erased. But im using a custom recovery since I got mine so maybe the stock recovery erses the os when doing a factory reset. A factory image cant be flashed via recovery and must be flashed via fastboot. Its really easy. But it will wipe the entire device. If you dont want to wipe everything you need to edit it..
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
I don't mind wiping the device but I cannot access Recovery Mode. When I select RECOVERY MODE and press the Power button to take me there it just returns me to the START screen.
I don't know if the fiollowing is relevent but it displays the word START vertically in the top left of the screen and next to it
Device Information
Product Name: manta
Variant: wifi
H/W Version: 8
Bottloader Version: MANTAMF01
Carrier Info: None
Serial Number: Don't think I should show that
Lock State: Unlocked
Reboot Mode Flag: None.
I have tried RESTART BOOTLOADER and that brings me back to the Start screen but still cannot access RECOVERY MODE.
Holding down the Power Button and Volume Up/Down brings me back to the Start screen again
I can get into DOWNLOAD MODE
Is there ANY way I can flash anything onto my Nexus 10 without using RECOVERY MODE like using Odin or Heimdall with a Samsung phone?

SORTED
Great news everyone..........well for me that is :laugh:
Thanks to Androidbeat.com I now have a fully operational Nexus 10.
Just in case anyone else was following this I did it by downloading all the necessary files into on folder on my Windows Desktop, opening a Command Prompt from there and followed the instructions.
Thank you to those who offered advice here and although my Nexus 10 is showing itself to be unlocked I think I'll give a miss to rooting it and just suffer the limitations rather than risk bricking it again.

matrixmainframe said:
Great news everyone..........well for me that is :laugh:
Thanks to Androidbeat.com I now have a fully operational Nexus 10.
Just in case anyone else was following this I did it by downloading all the necessary files into on folder on my Windows Desktop, opening a Command Prompt from there and followed the instructions.
Thank you to those who offered advice here and although my Nexus 10 is showing itself to be unlocked I think I'll give a miss to rooting it and just suffer the limitations rather than risk bricking it again.
Click to expand...
Click to collapse
Glad everything worked out for you. Just an FYI for future reference, the stock recovery factory reset does not wipe the OS (at least it shouldn't). By default, AFAIK there are no custom recoveries that will wipe your OS either while doing a factory reset. It must've been something with the toolkit.
Regarding root, it's super easy to get root on this device. All you have to do is download the custom recovery image file of your choice. I prefer Philz, but you can use CWM or TWRP as well. Then, download the latest SuperSU zip file (I believe it's v1.99r4 now). Simply fastboot flash the recovery image, boot into recovery, and install the SuperSU zip, and you're good to go. The whole process takes two minutes, and no toolkit required.

charesa39 said:
Glad everything worked out for you. Just an FYI for future reference, the stock recovery factory reset does not wipe the OS (at least it shouldn't). By default, AFAIK there are no custom recoveries that will wipe your OS either while doing a factory reset. It must've been something with the toolkit.
Regarding root, it's super easy to get root on this device. All you have to do is download the custom recovery image file of your choice. I prefer Philz, but you can use CWM or TWRP as well. Then, download the latest SuperSU zip file (I believe it's v1.99r4 now). Simply fastboot flash the recovery image, boot into recovery, and install the SuperSU zip, and you're good to go. The whole process takes two minutes, and no toolkit required.
Click to expand...
Click to collapse
charesa39 thanks for that. All done so thanks again.

[Urgent Help needed] Android 7.0 Flashable Zip

Does anyone have a clean flashable zip for Android 7.0 because I have tried to flash for Nexus 6P? because I tried to flash with the factory image that provided by google on this page :https://developers.google.com/android/nexus/images#angler
when I clicked on flash-all.bat keep getting waiting for devices no mater what I do reboot, re-plugged, nothing changed so i'm very desperate right now, I wiped everything in my phone. Please help. :crying::crying:
Edit: or if you can help me with the current problem, please help me.
thank you

HerySean said:
Does anyone have a clean flashable zip for Android 7.0 because I have tried to flash for Nexus 6P? because I tried to flash with the factory image that provided by google on this page :https://developers.google.com/android/nexus/images#angler
when I clicked on flash-all.bat keep getting waiting for devices no mater what I do reboot, re-plugged, nothing changed so i'm very desperate right now, I wiped everything in my phone. Please help. :crying::crying:
Edit: or if you can help me with the current problem, please help me.
thank you
Click to expand...
Click to collapse
There are no factory image flashable zips, as those have to be unpacked and flashed as individual partitions. However, there are OTA zips that you can sideload via ADB. If you're looking for a full Nougat factory image that you can flash with TWRP, you won't find it.
The index of all Nougat factory images and OTA updates are at http://www.xda-developers.com/facto...nexus-going-live-updated-with-nexus-6p-links/ and the OTA is listed down the page ... https://dl.google.com/dl/android/aosp/angler-ota-nrd90u-519758d5.zip
Finally, and most importantly for you, you need to be stock MM (right down to stock recovery) to apply a factory OTA via sideload. For a factory image update, you're actually much better off unpacking the factory image and flashing all partitions via fastboot, by following Heisenberg's guide. This would be the way to go right now, provided you have no problem booting into your bootloader.

The OTA can be quite normal flash with TWRP, without sideload

The simplest way out of your predicament would be to download nexus root toolkit here http://www.wugfresh.com/. This will let you flash stock, it will download all the files for you.

I am still trying to figure out what so urgent about it?!
You probably don't have ADB drivers installed or you're not in bootloader mode.
No need to make a big fuss about such tiny thing.

tommyg562000 said:
The simplest way out of your predicament would be to download nexus root toolkit here http://www.wugfresh.com/. This will let you flash stock, it will download all the files for you.
Click to expand...
Click to collapse
Can you tell me what to do with this application in bootloop situation? because right now my phone is in boot loop, I tried to restore the backup but when it goes to about 50% of progress it automatically reboot in went in boot loop. :crying:
wizardwiz said:
I am still trying to figure out what so urgent about it?!
You probably don't have ADB drivers installed or you're not in bootloader mode.
No need to make a big fuss about such tiny thing.
Click to expand...
Click to collapse
Actually I did install ADB driver, but it still doesn't work, right now my phone is in bootloop for 2 days and I can't do and don't know what to do about it

OK
1. Push the power button until your device is turned off.
2. after a minute or so, power on the device holding at the same time " Volum DOWN + POWER" until the device will turn on and you will see the FastBoot screen, then let go of the two buttons
3. While in Fastboot mode, make sure your PC manage to "see" your device. If it does, then move on . If it doesn't something is wrong with your ADB drivers and you need to fix this before moving on.
4. Assuming your ADB drivers are installed properly, you have three choices:
4.1 Make a clean install using the Google Factory Image Which will result in a lose of all user data and you will probably have a functioning device.
4,2 Use a toolkit such as Wugfresh's one and restore to a clean Install just as in section 4.1
4.3 You can try and change the flash-all.bat file that comes with Google factory images and remove the "-w" from the last line of the file. That will keep your data and will refresh your OS.
There you go.

HerySean said:
Does anyone have a clean flashable zip for Android 7.0 because I have tried to flash for Nexus 6P? because I tried to flash with the factory image that provided by google on this page :https://developers.google.com/android/nexus/images#angler
when I clicked on flash-all.bat keep getting waiting for devices no mater what I do reboot, re-plugged, nothing changed so i'm very desperate right now, I wiped everything in my phone. Please help. :crying::crying:
Edit: or if you can help me with the current problem, please help me.
thank you
Click to expand...
Click to collapse
Reinstall drivers again and see if the waiting for device issue is gone !

wizardwiz said:
OK
1. Push the power button until your device is turned off.
2. after a minute or so, power on the device holding at the same time " Volum DOWN + POWER" until the device will turn on and you will see the FastBoot screen, then let go of the two buttons
3. While in Fastboot mode, make sure your PC manage to "see" your device. If it does, then move on . If it doesn't something is wrong with your ADB drivers and you need to fix this before moving on.
4. Assuming your ADB drivers are installed properly, you have three choices:
4.1 Make a clean install using the Google Factory Image Which will result in a lose of all user data and you will probably have a functioning device.
4,2 Use a toolkit such as Wugfresh's one and restore to a clean Install just as in section 4.1
4.3 You can try and change the flash-all.bat file that comes with Google factory images and remove the "-w" from the last line of the file. That will keep your data and will refresh your OS.
There you go.
Click to expand...
Click to collapse
Worked, thank you.

HerySean said:
Worked, thank you.
Click to expand...
Click to collapse
Glad to hear you have managed to revive your device.

How to fix DM-VERITY issue for 7.0 flashed updates

Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!

Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.

Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?

Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.

Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.

I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me

Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.

does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...

PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.

card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently

What causes the dm-verity issue in the first place?

guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?

saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk

Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update

noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm

Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom

jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.

lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom

card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.