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.

How to root OxygenOS 3.0.2

Hi
I am new to the OnePlus 2. When I bought it, stock 5.1.1 installed, I downloaded and installed the latest Marshmallow stock build via an OTA update. I then followed the official OnePlus video guide on unlocking the bootloader and rooting the device. I successfully unlocked the bootloader, flashed TWRP and then went on to flash SuperSU. Unfortunately, then device did not reboot - and I was soft-bricked, stuck on the boot animation. I am not sure what went wrong here.
In order to un-brick and recover my device, I downloaded the latest Marshmallow OxygenOS 3.0.2 zip from OnePlus. I was able to get this onto my device and I flashed it successfully in TWRP, and all is well.
My questions are:
1) Having flashed the latest stock, Marshmallow OxygenOS 3.0.2, will my bootloader still be unlocked?
2) Will I still have TWRP recovery, or stock recovery?
3) How can I successfully root?
Thank you in advance

I already forget what it is looks like when I change from stock to custom ROM.
But hey, here is the guide to help you:
1. use Fastboot command -> fastboot oem device-info
If "Device unlocked: ture" than your bootloader is unlocked. Normally, if you have not yet touch anything, oem is locked. But if you do unlock it, it will STAY unlock unless you use fastboot command line to change back to locked.
2. OP website only show is optional to use official recovery, so I think it is depend on you. Just go and check on it
3. For OnePlus Brand is easy. Just go and download SuperSU 2.74, place into your "sdcard", and flash it.

qingmui said:
I already forget what it is looks like when I change from stock to custom ROM.
But hey, here is the guide to help you:
1. use Fastboot command -> fastboot oem device-info
If "Device unlocked: ture" than your bootloader is unlocked. Normally, if you have not yet touch anything, oem is locked. But if you do unlock it, it will STAY unlock unless you use fastboot command line to change back to locked.
2. OP website only show is optional to use official recovery, so I think it is depend on you. Just go and check on it
3. For OnePlus Brand is easy. Just go and download SuperSU 2.74, place into your "sdcard", and flash it.
Click to expand...
Click to collapse
Hi - many thanks for the reply and information
Just to confirm, question 2: I flashed the latest stock from TWRP to recover from a soft brick. Would that process have flashed stock recovery also? Do I need to check this out by pressing Vol. down and Power buttons on boot?
Thanks again

pretty pixel said:
Hi - many thanks for the reply and information
Just to confirm, question 2: I flashed the latest stock from TWRP to recover from a soft brick. Would that process have flashed stock recovery also? Do I need to check this out by pressing Vol. down and Power buttons on boot?
Thanks again
Click to expand...
Click to collapse
TWRP will ask you, if you want to disable stock recovery flash, after you flash official firmware.
Rooting the newest stock firmware with the latest supersu from chainfire's website will turn your device into a bootloop.
Here you can find the right supersu for your firmware:
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Greetings LordHelmchen

LordHelmchen89 said:
TWRP will ask you, if you want to disable stock recovery flash, after you flash official firmware.
Rooting the newest stock firmware with the latest supersu from chainfire's website will turn your device into a bootloop.
Here you can find the right supersu for your firmware:
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Greetings LordHelmchen
Click to expand...
Click to collapse
Hello and thank you for sending me the information and links. Flashing the modified supersu worked and I am now rooted
Just a final question please...Before I received your reply I had flashed stock several times and tried different supersu versions. And ended up in bootloops as a result of this. Is this likely to have damaged my device in any way?

pretty pixel said:
Hello and thank you for sending me the information and links. Flashing the modified supersu worked and I am now rooted
Just a final question please...Before I received your reply I had flashed stock several times and tried different supersu versions. And ended up in bootloops as a result of this. Is this likely to have damaged my device in any way?
Click to expand...
Click to collapse
No, this will not damage your phone. I can not say too much about it, but the device shouldn't be damaged, it's a software-thing
PS: Hope my english is okay...and if I helped you, I would be very grateful if you click the Thanks-Button ...thank you

LordHelmchen89 said:
No, this will not damage your phone. I can not say too much about it, but the device shouldn't be damaged, it's a software-thing
PS: Hope my english is okay...and if I helped you, I would be very grateful if you click the Thanks-Button ...thank you
Click to expand...
Click to collapse
Thank you for the reassurance

Bricked my LeEco Pro 3 while installing CM13, need some help and advice.

Hi Guys,
Long story short, I bought the LeEco Pro 3 US version due to the awesome Tmobile network support. The modem supports band 12 and WiFi calling and I was happy with it. But eventually notification issues and the horrible EUI got under my skin and I decided to install CM13 keeping the phone as untouched as possible so that I can revert back to stock whenever needed.
I followed below steps:
1. Enabled developer options and enabled USB debugging.
2. Went the Developer Options and enabled OEM Unlocking.
3. Did adb reboot bootloader to get into the bootloader menu.
4. Did fastboot unlock-go command to unlock the bootloader. I noticed that if I did this command and rebooted the phone, the phone reverted back to being locked again. But I could run the command again from bootloader screen and unlock it (as long as the developer options had the OEM unlocking enabled). So I was never permanently unlocked, just unlock at will whenever I wanted.
5. Then I downloaded the twrp.img file and from fastboot screen i did fastboot boot twrp.img, which booted me inot twrp screen. I was able to switch the language to english but i didnt do the permanent system modification. I did not root the phone as well through the menu.
6. Now, I plugged in a USB OTG drive in the phone. Usb OTG drive had CM13 ROM + Gapps on it.
7. Using the TWRP menu, I did a factory data reset and made a backup of all partitions of the LeEco Phone and saved it into USB OTG drive.
8. Then I installed the CM13 rom on the phone. Followed by Gapps and then rebooted the phone. The phone wouldnt boot.
9. I immediately rebooted the phone into the fastboot menu and tried to run the fastboot boot twrp.img, and got an error message that the device is not unlocked. Which is when i noticed that the phone is bricked.
So Long story short, I have a locked bootloader and I want to to retain my modem. I was given a suggestion to boot into the stock recovery and put the x720 update.zip file and install it. But that would flash the CN modem as well. Can I delete the modem file from the CN rom and flash the update.zip? Can someone help me there? All I want is the modem for the US rom and CM13, thats it.
Thank you guys for reading this post, it helps to talk to XDA about such issues, my wife would just kick my butt because I broke a phone, again!

Did you wipe the system using twrp before installing CM?

sunbinyuan said:
Did you wipe the system using twrp before installing CM?
Click to expand...
Click to collapse
No I didn't wipe the system before installing CM13. Usually the ROM installation scripts do system wipes.

This is the reason why I am hesitant to do this thing as there are no clear (step-by-step) procedures and there is no solid benefit (in fact your will lose some features). Can't it be possible to just create a CM or any other ROM that could be downloaded and rename into update.zip and load it directly renaming the X720 ROM? ^_^

Try unlocking bootloader again with fastboot method as you didn't do it the first time. Then try fastboot boot twrp.img

srikanthc said:
Try unlocking bootloader again with fastboot method as you didn't do it the first time. Then try fastboot boot twrp.img
Click to expand...
Click to collapse
He will not be able to unlock again due to the fact that he installed CM13 on an unlocked bootloader. I did read where you can flash the CN bootloader on a locked bootloader. Look at post #44 from the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" thread.
http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
"I finished the setup and run fastboot again and it is good so for anyone having the same issue as I was having of not able to unlock, just run: Fastboot Flash aboot emmc_appsboot.mbn get the file from dr4stic zip file"
Followed by post #47:
"Yeah I can confirm that flashing the aboot worked like dish soap on a squeaky hinge."
If that doesn't work then you will need to install the CN rom using the stock bootloader.

zoid_99 said:
He will not be able to unlock again due to the fact that he installed CM13 on an unlocked bootloader. I did read where you can flash the CN bootloader on a locked bootloader. Look at post #44 from the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" thread.
http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
"I finished the setup and run fastboot again and it is good so for anyone having the same issue as I was having of not able to unlock, just run: Fastboot Flash aboot emmc_appsboot.mbn get the file from dr4stic zip file"
Followed by post #47:
"Yeah I can confirm that flashing the aboot worked like dish soap on a squeaky hinge."
If that doesn't work then you will need to install the CN rom using the stock bootloader.
Click to expand...
Click to collapse
I ended up installing CN ROM as my last resort. I have an unlocked bootloader and twrp installed now, with CM13. Now I need the way to go back to US modem so I can get all the bands.
Sent from my LEX720 using Tapatalk

ceo.mtcl said:
I ended up installing CN ROM as my last resort. I have an unlocked bootloader and twrp installed now, with CM13. Now I need the way to go back to US modem so I can get all the bands.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
1. Download the rom from here: https://www.androidfilehost.com/?fid=601275311581036717
2. Unzip and extract the NON-HLOS.img file.
3. Reboot into fastboot mode.
4. Flash the modem "fastboot flash modem NON-HLOS.img"
You will not notice a change in the modem version in "About Phone" as they both report Baseband version MPSS.2.0.c1.9.1-00010. Who knows, they may be the same.

zoid_99 said:
1. Download the rom from here: https://www.androidfilehost.com/?fid=601275311581036717
2. Unzip and extract the NON-HLOS.img file.
3. Reboot into fastboot mode.
4. Flash the modem "fastboot flash modem NON-HLOS.img"
You will not notice a change in the modem version in "About Phone" as they both report Baseband version MPSS.2.0.c1.9.1-00010. Who knows, they may be the same.
Click to expand...
Click to collapse
Is this NON HLOS.img file from US baseband? Can you please help me in locating where it came from before I flash it. Thanks in advance.
Sent from my LEX720 using Tapatalk

ceo.mtcl said:
Is this NON HLOS.img file from US baseband? Can you please help me in locating where it came from before I flash it. Thanks in advance.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
That is from the US baseband. That rom will convert a CN install back to a US install.

zoid_99 said:
That is from the US baseband. That rom will convert a CN install back to a US install.
Click to expand...
Click to collapse
Thank you, is that from your phone or did you found it in some other post out here that I missed Zoid? I'm just looking for source of the file.
Sent from my LEX720 using Tapatalk

It's from this thread.
http://forum.xda-developers.com/le-pro3/how-to/flashing-guide-roundup-leeco-le-pro-3-t3511901
"
Okay, if you chose to use the long route and installed the Chinese ROM, you can still get back to the full US version, complete with all LTE bands. dr4stic is responsible for this gem, and was my way back to US ROMdom.
To go from Chinese or Custom ROM back to Stock US version:
The file is located in his Android File Host space here: https://www.androidfilehost.com/?fid=601275311581036717
"

ceo.mtcl said:
No I didn't wipe the system before installing CM13. Usually the ROM installation scripts do system wipes.
Click to expand...
Click to collapse
Sorry for the late answer but to add to that, it happened to me that the ROM didn't have a wipe script thus bricking another of my device. I reinstalled it after wiping the system and it worked.

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.

Stock 7.1.1 TWRP Issue

Hi there!
Well as the title says, it is an issue...
Here, i'll explain: If i flash the 7.1.1 ftf and boot it afterwards it works. Okay, then i put the phine into fastboot mode and on my computer i flash the advanced stock kernel and twrp 3.1.1.0 afterwards. And i boot the phone and phone starts like usually, but if i boot to recovery it does boot to twrp and all is working. But if i rebooted from twrp to system it says Sony logo > reboot > (this message is there always, i unlocked the bl) this device has been unlocked and phone boots in 5 sec. > the boot image is broken and phone shuts down. But i can still boot to twrp when i use pwr vol down and pushing vol buttons like usually... And if i install a custom rom, in my case paranoid android 7.2.3 it works. I just wanted to install magisk on the stock 7.1.1 and keep the slo mo stuff and so on... I have tried 6.0.1 and did the same stuff and it worked. I want my XZ3c back so bad...

XperiaGUY47 said:
Well as the title says, it is an issue...
Here, i'll explain: If i flash the 7.1.1 ftf and boot it afterwards it works.
Click to expand...
Click to collapse
"Advanced stock kernel
-For 34.1.A.1.198"
Click to expand...
Click to collapse
That's a MM kernel, mod your own using Trim Area Proof Of Concept and try again.

SXUsr said:
That's a MM kernel, mod your own using Trim Area Proof Of Concept and try again.
Click to expand...
Click to collapse
But does the XC Genesis Kernel v. 1.06 work with it?