Database Users

Nexus 10 does not boot after Update

After attempt at installing software update to Nexus 10 tablet will not boot. Have wiped Cache and even then did a factory reset. Nothing. Google appears and then twirling colorful dots and nothing. For hours just twirling dots., Samsung and Google and Best Buy geeks says nothing they can do. No longer under warranty but very upset since tablet was working great until update. I am not very tech savvy but can anyone help or do I just have a new paperweight? Thanks for any advice.
I have not made any modifications to the tablet.

Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images

yes flash the newest image

After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?

VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Gibbothegreat said:
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
Click to expand...
Click to collapse
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx

Khaon said:
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Click to expand...
Click to collapse
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?

same problem
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
as a newbie .I'm not allowed to reference your link !!
I rooted my nexus 10 using xda instructions., installed CWM. All good. I tried backup and recovery and screwed something up in recovery. Got stuck in recovery mode reboot loop. Many gyrations, no fix, so I tried factory reset. Still no fix.
I decided to install a new version of the OS using the Mantaray tar you reference above. UBS connecting and fastboot. All messages look good. Now I have the problem reported in this thread. Stuck with flying balls and no boot. Very interested in any suggestions you may have.
Click to expand...
Click to collapse

Gibbothegreat said:
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
Click to expand...
Click to collapse
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.

Khaon said:
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Click to expand...
Click to collapse
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.

Gibbothegreat said:
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Click to expand...
Click to collapse
Oh I see, well, you should just flash a custom ROM or if you want to stay with official factory images, you should just follow instruction there:
https://developers.google.com/android/nexus/images
What you do need is just have fastboot executable once you are into the bootloader.
You can easily access the bootloader from twrp : shutdown > reboot into booatloader

Cool thx for your continued help :good:

The problem is due to your attempting an OTA update with a custom recovery (TWRP). You can only do OTA with stock recovery. Once you are in this situation, your easiest way out of it is to simply apply the latest factory image using "fastboot", but this will also wipe your user data so backup any photos, music, etc. before you start. You will also have to reload programs from Playstore once the new image is installed.

Bootloop Help After Trying To Root 7.1.1

So I flashed the 7.1.1 update and everything was fine. I then tried to root through TWRP with the most recent version of recovery and and SuperSu and when I went to reboot it would get to the "Google" splash screen and go back to the warning. I then tried to restore to my Nandroid that I made right before the 7.1.1 flash but it does the same thing. I ended up doing a factory reset, still looping. I tried flashing an old firmware but it still would loop. I got desperate and did a full wipe and then flashed the old firmware from September's update but it still will not boot. I'm a long time lurker I just don't post much. Any help will be appreciated. Thanks in advance!

http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club

jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Ahh, great. I tried searching to see if anyone else posted anything, couldn't find it.

jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Wait are you able to get into Recovery?

ChazLanier said:
Wait are you able to get into Recovery?
Click to expand...
Click to collapse
Nope. And so are other folks.
But if you can, there's still hope to save your device.

What version of twrp were you using?? Also what company makes the storage (not memory) on your device?

jamaniek said:
Nope. And so are other folks.
But if you can, there's still hope to save your device.
Click to expand...
Click to collapse
I can still get into recovery. I just can't get it past the Google splash screen.

ChazLanier said:
I can still get into recovery. I just can't get it past the Google splash screen.
Click to expand...
Click to collapse
Have you tried installing custom ROM, instead of a stock one?
And tell us what @ArminasAnarion asked for. There may be a pattern here. :good:

I haven't tried a custom ROM. I'll try that if I get any down time at work. Also, I'll check for you @ArminasAnarion in a bit.

Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?

ChazLanier said:
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
Click to expand...
Click to collapse
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!

ArminasAnarion said:
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
Click to expand...
Click to collapse
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.

ChazLanier said:
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
Click to expand...
Click to collapse
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.

ArminasAnarion said:
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
Click to expand...
Click to collapse
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.

ChazLanier said:
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
Click to expand...
Click to collapse
Oh okay cool! Good luck!

ArminasAnarion said:
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
Click to expand...
Click to collapse
Samsung storage, and I thought I was on -2 but it seems like I was on -1.

ArminasAnarion said:
Oh okay cool! Good luck!
Click to expand...
Click to collapse
Newest image didn't work either..

Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.

FWIW, I successfully updated to 7.1.1 NPF10C and rooted by using fastboot to flash bootloader, radio, boot, system, and vendor. Then used TWRP 3.0.2-2 to flash SuperSU 2.78 SR1. No issues.

Howie Dub said:
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
Click to expand...
Click to collapse
No luck on this either.

I can no longer boot into EMUI on my Huawei Honor Note 8

I unlocked the bootloader, installed TWRP. Everything was fine. I put SuperSU.zip into the phone, booted into TWRP, installed SuperSU.zip, and then selected wipe cahe/dalvik before exiting. Now I only get the erecovery. I then did a factory reset within TWRP and now I just get the Chines erecovery. Is there anything I can do?
Thank you
edit: I can see about 2GB of data in my system folder as well as others. It looks like the EMUI is there. My phone just doesn't know how to boot to it.
edit 2: I was able to sideload KangVIP but I'd rather have the stock ROM. Does anybody know where one is available?

Hello, as you have unlocked the bootloader? With the dc-unlock software?
Thanks

flint24 said:
I unlocked the bootloader, installed TWRP. Everything was fine. I put SuperSU.zip into the phone, booted into TWRP, installed SuperSU.zip, and then selected wipe cahe/dalvik before exiting. Now I only get the erecovery. I then did a factory reset within TWRP and now I just get the Chines erecovery. Is there anything I can do?
Thank you
edit: I can see about 2GB of data in my system folder as well as others. It looks like the EMUI is there. My phone just doesn't know how to boot to it.
edit 2: I was able to sideload KangVIP but I'd rather have the stock ROM. Does anybody know where one is available?
Click to expand...
Click to collapse
How did you install TWRP if you only see the erecovery?
My adb was working earlier today, but now, when I "adb reboot bootloader", it just says "error: device '(null)' not found"
EMUI isn't loading now.
That last thing I did was run "flash_all.bat" in "EDI-AL10-C233B027_6.0" from https://mega.nz/#!VRN2AICD!HqTY2ai1XAl-bOoCFW_YfBoyhOr6GhoiWXL68l7QNhg
The flashing was successfull but after it rebooted, I just encountered bootloops.

MarkAndroid said:
Hello, as you have unlocked the bootloader? With the dc-unlock software?
Thanks
Click to expand...
Click to collapse
Yes I unlocked the bootloader. I think when I went back into TWRP, ran the SuperSU.zip file and then wiped the cache/dalvik, that's what did it. Before I did that, after I unlocked my bootloader, I was able to reboot and boot back into EMUI no problem.

jetherson said:
How did you install TWRP if you only see the erecovery?
My adb was working earlier today, but now, when I "adb reboot bootloader", it just says "error: device '(null)' not found"
EMUI isn't loading now.
That last thing I did was run "flash_all.bat" in "EDI-AL10-C233B027_6.0" from https://mega.nz/#!VRN2AICD!HqTY2ai1XAl-bOoCFW_YfBoyhOr6GhoiWXL68l7QNhg
The flashing was successfull but after it rebooted, I just encountered bootloops.
Click to expand...
Click to collapse
So this is the stock Honor Note 8 image? I think I'll just do an adb sideload within TWRP with this badboy and be ok. I'm going to backup beforehand.

flint24 said:
Yes I unlocked the bootloader. I think when I went back into TWRP, ran the SuperSU.zip file and then wiped the cache/dalvik, that's what did it. Before I did that, after I unlocked my bootloader, I was able to reboot and boot back into EMUI no problem.
Click to expand...
Click to collapse
For unlocking the bootloader you followed the step by step instructions to the topic:
http://forum.xda-developers.com/general/general/huawei-honor-note-8-unlock-bootloader-t3488142
You're forced to buy the key (4 euro) on the site:
https://www.dc-unlocker.com/how-to-r...er-unlock-code
Thanks

flint24 said:
So this is the stock Honor Note 8 image? I think I'll just do an adb sideload within TWRP with this badboy and be ok. I'm going to backup beforehand.
Click to expand...
Click to collapse
No! That's NOT the stock note8 image.
That came from http://forum.xda-developers.com/showpost.php?p=70055340&postcount=658

MarkAndroid said:
For unlocking the bootloader you followed the step by step instructions to the topic:
http://forum.xda-developers.com/general/general/huawei-honor-note-8-unlock-bootloader-t3488142
You're forced to buy the key (4 euro) on the site:
https://www.dc-unlocker.com/how-to-r...er-unlock-code
Thanks
Click to expand...
Click to collapse
Yes. I actually bought 7 credits but yes I did that. My backup failed and I continued anyway.

jetherson said:
No! That's NOT the stock note8 image.
That came from http://forum.xda-developers.com/showpost.php?p=70055340&postcount=658
Click to expand...
Click to collapse
Ok got it. But is it safe to use on my HN8 anyway? This KangVIP rom sucks so bad.

flint24 said:
Ok got it. But is it safe to use on my HN8 anyway? This KangVIP rom sucks so bad.
Click to expand...
Click to collapse
The B017 stock honor note 8 is EDI-AL10C233B017CUSTC233D002_Firmware_China_Chann.zip
Try searching for that file.
BTW, I solved my problem awhile ago. I actually used that file. I had to extract the UPDATE.APP from it.
This phone is very difficult to brick.

jetherson said:
The B017 stock honor note 8 is EDI-AL10C233B017CUSTC233D002_Firmware_China_Chann.zip
Try searching for that file.
BTW, I solved my problem awhile ago. I actually used that file. I had to extract the UPDATE.APP from it.
This phone is very difficult to brick.
Click to expand...
Click to collapse
What about the B022 stock honor note 8 firmware? I believe that's the exact one that came with my phone.
Thank you very much for the help!

Nevermind. Everything is fine now. I loaded the firmware you have in your post saving the data on my sdcard. Everything works beautifully. Thank you very much. Consider this case closed.
Sent from my EDI-AL10 using Tapatalk

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.

Not geting any update after 7.10.14

hello guys
i am not getting any update after 7.10.14
can any one also facing it
i am rooted with magisk and also twrp is installed
i have also done no. of tweaks on my device
is there any solution to solve it

Red_Man 898 said:
hello guys
i am not getting any update after 7.10.14
can any one also facing it
i am rooted with magisk and also twrp is installed
i have also done no. of tweaks on my device
is there any solution to solve it
Click to expand...
Click to collapse
Same this side. I can see there is an update from the notifications. When I am clicking it.. its not opening.
Sent from my ONEPLUS A3003 using Tapatalk

When you install twrp, forget about updates. You need to flash full stock image using miflash application on Windows. I had the same problem, flashed stock images using miflash and update worked! I did not even lose my phone data.
Edit: Just boot into twrp to flash magisk. Don't flash twrp or system update will fill after downloading.

I was in the same situation (even if i've never flashed twrp).
Solved by flashing 17.10.30 Rom (after that I got the update)
Cheers.

tonycapuozzo said:
I was in the same situation (even if i've never flashed twrp).
Solved by flashing 17.10.30 Rom (after that I got the update)
Cheers.
Click to expand...
Click to collapse
How do I flash this version now ? I am already on 17.10.30

ProudRed said:
How do I flash this version now ? I am already on 17.10.30
Click to expand...
Click to collapse
Well...try re-flashing the same image or wait for the full November Rom.
Cheers

tonycapuozzo said:
Well...try re-flashing the same image or wait for the full November Rom.
Cheers
Click to expand...
Click to collapse
Just the boot image ? Where do I get the extracted boot image ?

If you have done multiple tweaks, I suppose that those were done to system directly. In such case you'll need to flash system partition as well. Both are included in full ROM, just extract them from archive http://en.miui.com/download-333.html.

https://www.youtube.com/watch?v=5Ozdhl-JdvU
give it a try.

If not getting updates (like: Your phone is already update) try to clean Google Service Framework app data from Settings - App - 3 dots on corner - Show system apps

If your device is rooted, then make clean installation of os. There will be ota update.

I am stock not rooted nor unlocked. Ad still stuck no more updates for me