I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
First flash this file and then Rom. That's right?? Or its other way around
karan khara said:
First flash this file and then Rom. That's right?? Or its other way around
Click to expand...
Click to collapse
If u have dm verity error on boot. Just flash it..
Wouldn't this procedure downgrade some performance on the device?
Giocarro said:
Wouldn't this procedure downgrade some performance on the device?
Click to expand...
Click to collapse
No..
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Nitesh13 said:
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Click to expand...
Click to collapse
Yes u can..
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
cool.boy said:
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
Click to expand...
Click to collapse
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
I have no DM verity error and I have cb9 firmware and rooted
Sent from my OnePlus 3 using XDA Labs
Why would you want to flash old firmware and modem, not made for this ROM, just to get rid of a pointless message?
Especially when there are other methods to fix this so called issue ...
Sent from my OnePlus 3 using Tapatalk
puschkin said:
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
Click to expand...
Click to collapse
Yes..
snippem said:
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
Click to expand...
Click to collapse
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
cesar.mk4 said:
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
Click to expand...
Click to collapse
dlhxr said:
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
Click to expand...
Click to collapse
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
cesar.mk4 said:
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
Click to expand...
Click to collapse
I never had that till now only after flash does not reboot.
In my opinion it is more a twrp incompatibility that will be resolved when N sources are out by oneplus
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
Don't even need to wait, just press the power button to skip it (same applies to first bootloader unlocked message).
Sent from my OnePlus 3 using Tapatalk
it's easily avoidable (but the phone will be decrypted)
after flashing ob9 successfully and booting to system, reboot to TWRP (.28) and wipe convert data to f2fs then wipe it, then wipe internal storage (back up your data to your pc 1st)...and that's it, if you want root, reboot back to TWRP and flash root, then roboot to system, dmverity will be gone, and the phone decrypted,
(this will work if you started with a clean ob9 install like sideloading, and you ended with a full stock ob9)
Related
There is an update notification that keeps popping up . bought my nexus 6 from tmobile nov 22.
If i update will i loose root etc and or if i do uodate and loose root will it keep me from rooting?
Im on build
lnx07m
clorbag said:
There is an update notification that keeps popping up . bought my nexus 6 from tmobile nov 22.
If i update will i loose root etc and or if i do uodate and loose root will it keep me from rooting?
Im on build
lnx07m
Click to expand...
Click to collapse
You will lose root but you can reroot.
Sent from my Nexus 6
Seems it goes straight to twrp. Do I need to flash stock recovery first?
clorbag said:
Seems it goes straight to twrp. Do I need to flash stock recovery first?
Click to expand...
Click to collapse
yes, it has to be in "out of the box" configuration to accept an OTA
clorbag said:
Seems it goes straight to twrp. Do I need to flash stock recovery first?
Click to expand...
Click to collapse
Not just stock recovery - the entire system partition will need to be stock from what I've read. So, boot/system/radio - all images
Edit: just saw ebrown205's post - "out of the box" config is right.
Might just wait to flash a ROM then... Don't see the benefit to stock out for an update
clorbag said:
Might just wait to flash a ROM then... Don't see the benefit to stock out for an update
Click to expand...
Click to collapse
Or you could just flash the images from the latest google images (which is what you should do anyway) - unless you want a different ROM of course.
yeah i always only keep stock as long as it takes for a slim or pa rom to come out, but 5.0 is actually pretty good! still though stock will be gone asap
It showed up this morning for me on T-Mobile, Folsom, CA. but I didn't go for it yet.
No problems for me so far. Seems about the same as 5.0
Thanks!
Seems like only yesterday I re-rooted after going to 5.0.
My OTA failed. I have put stock recovery back but I am still rooted and have installed the custom LTE radios. Would one of the two be causing the problem?
Well, With 0 knowledge in the world of compiling and recompiling - can someone assist and build an flashable update to those who have closed bootloader but has TWRP recovery? (I've closed it in the past)..
10x
ForMartha said:
Well, With 0 knowledge in the world of compiling and recompiling - can someone assist and build an flashable update to those who have closed bootloader but has TWRP recovery? (I've closed it in the past)..
10x
Click to expand...
Click to collapse
One question why would you install TWRP and reclose the bootloader? That doesn't make scense.
_jay_uk_ said:
My OTA failed. I have put stock recovery back but I am still rooted and have installed the custom LTE radios. Would one of the two be causing the problem?
Click to expand...
Click to collapse
Yes. Both will cause it to fail.
Flash the factory image manually (leave out the "-w" to keep your data), then re-root / flash radio if desired.
flopower1996 said:
One question why would you install TWRP and reclose the bootloader? That doesn't make scense.
Click to expand...
Click to collapse
In the past I used to install custom roms. I've stopped but the TWRP was still on there.. and the locked bootloader is a mistake that iv'e made :/
well, got any clue what can I do without opening the bootloader once again?
you could root your phone and reopen the bootloader with an app called boot unlocker.
Long story short, I finally got the job done with Wugfresh Nexus Root Toolkit, what a breeze.
Any changelogs?
Is the upgrade worth?
Better than 5.0
rooting 5.0.1
Is the any difference in rooting 5.0.1 compared to 5.0?
kisller said:
Is the any difference in rooting 5.0.1 compared to 5.0?
Click to expand...
Click to collapse
No
flopower1996 said:
No
Click to expand...
Click to collapse
Any suggestions for a tutorial for a noob?
5.0.2 is on the way.
OTA's should return to root if rooted.
RASTAVIPER said:
5.0.2 is on the way.
Click to expand...
Click to collapse
That might just be for the Nexus 7 (2012 WiFi).
Does anybody get mobile internet connection issues like slowing down or anything like that after 5.0.1?
udakar said:
Does anybody get mobile internet connection issues like slowing down or anything like that after 5.0.1?
Click to expand...
Click to collapse
This should be your device's matter.
Either reflash the same or try other radio.
I can no longer write any custom roms to my N6. Started with PURE 3.5 but now effects any rom i try to flash. I have brought my N6 back to factory state multiple times even relocking it. Only thing I can do is Fastboot flash N6 image from google manually piece by piece. I do have working 5.01 and phone works. Roms either hang or have errors. or just write the boot.img file. TWRP works other wise i can backup and restore, I am using 2.8.3.1. I have searched all over for a fix....
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
dipstik said:
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
Click to expand...
Click to collapse
I had no problem updating Pure for over a month from like 2.0 to 3.4.
they all hang when writing to system as far as i can tell. happens regardless of Pure....from a fresh clean image of 5.0 or 5.01 i can not flash any roms. driving me nutzo....i can no longer flash pure 3.4 either but i can restore the phone from a nandroid backup i had on my pc and run Pure 3.4 just fine.
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Pilz said:
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Click to expand...
Click to collapse
yes and both cache.....
also made sure system not mounted.
very frustrating.
Bignoze73 said:
yes and both cache.....
also made sure system not mounted.
very frustrating.
Click to expand...
Click to collapse
That is very odd, did you try reflashing TWRP or using a different version.
Pilz said:
That is very odd, did you try reflashing TWRP or using a different version.
Click to expand...
Click to collapse
mutiple times......tried all versions of TWRP too.
I can write a custom kernal like elementalx no problem.....just not roms.
Bignoze73 said:
mutiple times......tried all versions of TWRP too.
Click to expand...
Click to collapse
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Pilz said:
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Click to expand...
Click to collapse
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Bignoze73 said:
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Click to expand...
Click to collapse
If you restore your stock recovery on your phone you could try this.
Make sure TWRP is not installed on your phone and that the stock recovery is installed and working:
Have TWRP in your platform tools folder named however you want
Then use "fastboot boot recovery 'whatever you named TWRP' "
This will boot TWRP without installed it. Then try to flash the ROM using TWRP. You can also use the"adb push" to sideload the ROM onto your phone so you can find it via TWRP.
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Bignoze73 said:
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Click to expand...
Click to collapse
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Pilz said:
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Click to expand...
Click to collapse
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
laureanop said:
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
Click to expand...
Click to collapse
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Pilz said:
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Click to expand...
Click to collapse
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
laureanop said:
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
Click to expand...
Click to collapse
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Pilz said:
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Click to expand...
Click to collapse
Is there a tool or command to do a full memcheck of both ram and storage
rgraville said:
Is there a tool or command to do a full memcheck of both ram and storage
Click to expand...
Click to collapse
I'm not sure I've never had the need to do one from adb or fastboot
Pilz said:
I'm not sure I've never had the need to do one from adb or fastboot
Click to expand...
Click to collapse
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Bignoze73 said:
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Click to expand...
Click to collapse
I assume you are also out of the return window. Well if you are unlucky or lucky (depending on how you view it) you could have an issue eventually. They will RMA for burn in, camera issues etc... The camera issue was common in the earlier production models that I had. There should be another method, I would look into it if you have time.
So my phone is rooted with unlocked bootloader running faux kernel. I just received the ota update and clicked the button for restart and install. When I did that it brought me to my main option list in twrp. I didn't know what to do so I hit reboot system. It rebooted but nothing showed updating when I did that. Showing I'm still on 5.0.0.
What did I need to do? How do I still update now?
You cannot accept ota if you're modified.
You'll have to flash a ROM.zip or fastboot flash system.and boot image.from the factory images
rootSU said:
You cannot accept ota if you're modified.
You'll have to flash a ROM.zip or fastboot flash system.and boot image.from the factory images
Click to expand...
Click to collapse
See that's what I thought but was confused that I got the ota. I'm having a problem finding the rom.zip. Only finding images and I don't want that. Do you happen to have a link?
HyperM3 said:
See that's what I thought but was confused that I got the ota. I'm having a problem finding the rom.zip. Only finding images and I don't want that. Do you happen to have a link?
Click to expand...
Click to collapse
If you download the image from google there is a zip drive with the files you are looking for inside of them. You can fastboot them individually.
Or you could just flash one of the many roms on here that are using the newer 5.0.2
xxfwmxx said:
Or you could just flash one of the many roms on here that are using the newer 5.0.2
Click to expand...
Click to collapse
That's the thing, I was trying to keep it relatively stock for a while. I don't see any reliable roms out there yet.
Give Sinless rom a try. There is a thread on here for it. It is based off of the office 5.0.1 image and not aosp. Great speed and features and decrypted
HyperM3 said:
So my phone is rooted with unlocked bootloader running faux kernel. I just received the ota update and clicked the button for restart and install. When I did that it brought me to my main option list in twrp. I didn't know what to do so I hit reboot system. It rebooted but nothing showed updating when I did that. Showing I'm still on 5.0.0.
What did I need to do? How do I still update now?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-5-0-1-lrx22-stock-root-t2980206
^^ thats stock rooted, that you can flash thru TWRP. I don't personally use it because I rooted and modified my own.
t2noob said:
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-5-0-1-lrx22-stock-root-t2980206
^^ thats stock rooted, that you can flash thru TWRP. I don't personally use it because I rooted and modified my own.
Click to expand...
Click to collapse
Great, thanks for that!
5.02 is out?
cobyman7035 said:
5.02 is out?
Click to expand...
Click to collapse
Only aosp
I made a thread outlining how to update to 5.0.1 after rooting/unlocking yesterday after noticing the same problem:
http://forum.xda-developers.com/nexus-6/help/how-to-flash-ota-updates-rooted-custom-t2996149
Should help
Hey Xda,
Today I present you a guide on how to
REVERT TO STOCK OR REFLASH firmware on the Asus Zenfone 2 Laser ZE5550KL.
This guide is applicable to both types of users ie who use TWRP and who don't use TWRP.After following this guide your phone will also be unrooted.
For TWRP Users
Here I give you links to two firmwares which you can directly flash via TWRP recovery.
Version:1.13.40.496
Link
Version:1.17.40.1234
Link
For Stock/Non-TWRP Users
The procedure is a little long here ==>
1. Download the official firmware from asus website.
2. Copy the firmware to the Micro-SD and rename the file (firmware) by one more(version).This renaming should be according to your current firmware version.If you have 17.something firmware and you download 16.something firmware then rename the 16.x.x file to some thing like 17.x.x For eg. if you have 1.17.40.763 then rename 16.x.x file to 1.17.40.764.
3. Reboot the phone.Android should automatically find the update file and offer to automatically update the software.Do it !!
4. Go to stock Recovery and wipe cache , dalvik cache and data.
5. Reboot device. Your phone will now be unrooted(if it was rooted before).
DONT FORGET TO PRESS THE THANKS BUTTON IF I HELPED YOU.
CREDITS
CREDITS
@abhishekr700
@LuK1337
@abhishekr700: You could atleast credit me for TWRP method. The zips you uploaded are obviously made using my guide.
LuK1337 said:
@abhishekr700: You could atleast credit me for TWRP method. The zips you uploaded are obviously made using my guide.
Click to expand...
Click to collapse
Yes ofcourse,
Would you provide me links to your guide? @LuK1337
abhishekr700 said:
Yes ofcourse,
Would you provide me links to your guide? @LuK1337
Click to expand...
Click to collapse
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482
is it applicable for asus_z00LD
kris12344 said:
is it applicable for asus_z00LD
Click to expand...
Click to collapse
Yes
Sent from my C2305 using Tapatalk
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Lololololololo
tmjm28 said:
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Click to expand...
Click to collapse
Lemme guess. You use that stupid custom kernel? That'd explain why About Phone says it's Z00LD.
Sent from my ASUS_Z00TD using XDA Labs
Does this work with zenfone500kl
LuK1337 said:
Lemme guess. You use that stupid custom kernel? That'd explain why About Phone says it's Z00LD.
Sent from my ASUS_Z00TD using XDA Labs
Click to expand...
Click to collapse
Well, I'll be damned. I was doing so much flashing at the time that I didn't put it together. Oh well. I've been back on the stock CM kernel for days and everything finally works as it should again.
Will flashing this stock ROM on TWRP replace my current TWRP recovery to stock recovery on boot?
Sent from my ASUS_Z00LD using Tapatalk
tmjm28 said:
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Click to expand...
Click to collapse
This issue has been fixed on V4.0of kernel .
Hope you like it.
HampTheToker said:
Lololololololo
Click to expand...
Click to collapse
This issue has been fixed on V4.0 .
Hope you like it.
mohamedelkholy said:
Does this work with zenfone500kl
Click to expand...
Click to collapse
Yes
HampTheToker said:
Well, I'll be damned. I was doing so much flashing at the time that I didn't put it together. Oh well. I've been back on the stock CM kernel for days and everything finally works as it should again.
Click to expand...
Click to collapse
This issue has been fixed on V4.0 .
Hope you like it.
kunalchitara said:
Will flashing this stock ROM on TWRP replace my current TWRP recovery to stock recovery on boot?
Nope !
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
Hi
May I know if the above worked for downgrading from Marshmallow 6.0.1 back to Lollipop 5.x.x ??
Thanks
Man, so how should I do if I wanna flash back to LP and upgrade to MM?
The TWRP won't be replace to stock you said above.
I'm now using TWRP and CM13
- Thanks!
jasonshao88 said:
Man, so how should I do if I wanna flash back to LP and upgrade to MM?
The TWRP won't be replace to stock you said above.
I'm now using TWRP and CM13 and stock LP firmware.
- Thanks!
Click to expand...
Click to collapse
How can you use cm13 and stock lp together?
This is for reverting to stock nothing else.
Sent from my C2305 using Tapatalk
.
will get updates again if i flash this? tnx
My friend I installed TWRP and accidently deleted all android system. . . Now only appears the TWRP .... How to do reinstall android 5.0 system ??
hi
I have rooted my ze550kl and unrooted it through su iam not able to install ota updates i have twrp i want removery twrp and install stock rom to get ota updates but i cant find recovery img for my firmware
Can u please provied recovery.img,boot.img,bootdriod.img files for ww.1.17.40.1234 firmware for my asus zenfone2 laser ze550kl