Related
Hey guys I could really use some help...I have twrp recovery but unfortuunately when i try to flash stock recoveryy back, it will not change. I have tried fastboot, nexus toolkit by wug, flashify, image flash gui, etc. Do you guys have any suggestions? Thanks so much!
Are you still unlocked or did you relock?
sfhub said:
Are you still unlocked or did you relock?
Click to expand...
Click to collapse
I am still unlocked
I don't think twrp recovery has the option to restore recovery (or I might have missed it last time I looked)
Are you doing
fastboot flash recovery stock-recovery.img
sfhub said:
I don't think twrp recovery has the option to restore recovery (or I might have missed it last time I looked)
Are you doing
fastboot flash recovery stock-recovery.img
Click to expand...
Click to collapse
Yea i did that put recovery.img in platform tools folder and executed the command....its almost like the recovery is flashed permanently...cant even flash cwm
Did you enable usb debugging in developer options before trying to flash recovery?
geckocavemen said:
Did you enable usb debugging in developer options before trying to flash recovery?
Click to expand...
Click to collapse
yes i did that...have you guys tried it? maybe its just a problem for everyone idk
slamdunksaliby said:
yes i did that...have you guys tried it? maybe its just a problem for everyone idk
Click to expand...
Click to collapse
Ive tried to reflash the stock recovery image and ended up with the same problems, anyone able to reflash the stock recovery after flashing twrp?
chuck313 said:
Have tried to reflash the stock recovery image and ended up with the same problems, anyone able to reflash the stock recovery after flashing twrp?
Click to expand...
Click to collapse
I even did a factory reset and still its sticking....i even tried to rename recovery-from-boot.bak back to .p and still nothing
I guess ill just flash cleanrom for now since the recovery is here forever lol
slamdunksaliby said:
I even did a factory reset and still its sticking....i even tried to rename recovery-from-boot.bak back to .p and still nothing
I guess ill just flash cleanrom for now since the recovery is here forever lol
Click to expand...
Click to collapse
I had a similar problem flashing the one that has "for razor" in its name. Found a different one and it worked fine.
TG2708 said:
I had a similar problem flashing the one that has "for razor" in its name. Found a different one and it worked fine.
Click to expand...
Click to collapse
interesting mine was from one of the stickies above...but ive tried multiple recoveries too...did you use fastboot? If you could maybe link the working one that would be much appreciated
slamdunksaliby said:
interesting mine was from one of the stickies above...but ive tried multiple recoveries too...did you use fastboot?
Click to expand...
Click to collapse
Yes i did use fastboot.
TG2708 said:
Yes i did use fastboot.
Click to expand...
Click to collapse
Hmm well if you could link to the working one that would be greatly appreciated I like twrp no doubt but i feel like this recovery may not even be updatable let alone changed if I ever needed to
update: after some testing It looks like the stock recovery file in the sticky above is actually twrp recovery...if someone can upload the real stock recovery file that would be great
slamdunksaliby said:
update: after some testing It looks like the stock recovery file in the sticky above is actually twrp recovery...if someone can upload the real stock recovery file that would be great
Click to expand...
Click to collapse
I've found three recoveries floating around on the forum so far. Two are in this thread -- one is in the first (1st) post under the "recovery" subtitle and the second is in the seventh (7th) post.
The other one is in this post. You have to download the Nexus_7_Restore_F.zip file and unzip it. Once you do that you will find a recovery.img file in it.
Hope one of these works. My bet is the last one will at the very least. Let us know how it turns out for you.
Thank you so much I'll let you know! Ah it looks like the stock kernel is in the last one too that's good..hopefully sometime soon we can get factory images to make things easier haha
geckocavemen said:
I've found three recoveries floating around on the forum so far. Two are in this thread -- one is in the first (1st) post under the "recovery" subtitle and the second is in the seventh (7th) post.
The other one is in this post. You have to download the Nexus_7_Restore_F.zip file and unzip it. Once you do that you will find a recovery.img file in it.
Hope one of these works. My bet is the last one will at the very least. Let us know how it turns out for you.
Click to expand...
Click to collapse
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.
minazaki said:
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.
Click to expand...
Click to collapse
Unless I'm mistaken the Android with a red exclamation is what you should see if you have the stock recovery installed...which means it was successful. At that point there is some combination of buttons that must be pressed to restore the recovery but I don't remember what it is (I think it might be Vol up + Power but I don't know for certain so I wouldn't try that until someone else confirms it).
minazaki said:
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.
Click to expand...
Click to collapse
That is what you are supposed to see.
Please see this post for instructions:
[Info] Guide to entering safe mode, bootloader, stock recovery
geckocavemen said:
Unless I'm mistaken the Android with a red exclamation is what you should see if you have the stock recovery installed...which means it was successful. At that point there is some combination of buttons that must be pressed to restore the recovery but I don't remember what it is (I think it might be Vol up + Power but I don't know for certain so I wouldn't try that until someone else confirms it).
Click to expand...
Click to collapse
sfhub said:
That is what you are supposed to see.
Please see this post for instructions:
Info] Guide to entering safe mode, bootloader, stock recovery
Click to expand...
Click to collapse
Oh right. I actually knew that too. Been so long since I had seen stock recovery.
5.0.1 Build LRX22C OTA to 5.1 Build LMY47M "T-Mobile"
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
Your bootloader MUST be unlocked already, if not, these instructions do not apply to you so don't do them, it won't work.
These are the steps I did that worked for me. No guarantees that it will work for you, or if it wipes or bricks your phone.
Basically, you're downgrading your phone to 5.0.1 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None. Set OEM Unlock in Developer Options on just in case.
2. Reboot phone to bootloader (adb reboot-bootloader), or Power+Vol Down while the phone is off.
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
Green Android with Red Exclamation mark is stock recovery. Press Power + Vol Up to activate the menus. I sometimes have to press them a lot to get it to show.
If your PC does not recognize ADB Sideload mode, unplug your phone and plug it back in, it should work. If not check Device Manager and reload ADB drivers.
nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
Click to expand...
Click to collapse
Thank You! THANK YOU! THANK YOU! lol thanks for sharing
How do i install this again what are the requirements
Looks like I'm reverting back to 5.01 to get this one.
Just installed it. Thank you!
iGoogleNexus said:
Just installed it. Thank you!
Click to expand...
Click to collapse
Good job, mine is still optimizing apps, super slow, 160 of 202.
someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???
simms22 said:
someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???
Click to expand...
Click to collapse
Radio is 95R, it's the same in the D system image.
nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
You must be bootloader unlocked already, if not, these instructions do not apply to you so don't do them.
Basically, you're downgrading your phone to 5.01 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None.
2. Reboot phone to bootloader (adb reboot-bootloader)
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
FYI, Radio is 95R, the E (Verizon build) is 98R
Click to expand...
Click to collapse
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?
the.emilio said:
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?
Click to expand...
Click to collapse
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.
nxt said:
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.
Click to expand...
Click to collapse
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol
Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!
I just finish side loading it......
mr pnut said:
I just finish side loading it......
Click to expand...
Click to collapse
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
the.emilio said:
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol
Click to expand...
Click to collapse
Same not sure. Ended flashimg all the img, 47E
jay661972 said:
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
Same not sure. Ended flashimg all the img, 47E
Click to expand...
Click to collapse
Yes sir.......
Sorry too far OT delete
kaos2569 said:
Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!
Click to expand...
Click to collapse
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?
LGSilva said:
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?
Click to expand...
Click to collapse
What if u already stuch with 5.1 47E bootloader, flash the one from op but when about tonto recovery, got the same woth the other guy, android with the spinning thing and not exclamation.
Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)
lainemac said:
Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)
Click to expand...
Click to collapse
98R and E build is for Verizon phones. The D builds are for all other non Verizon nexus 6 phones. I went back to 95R because 98R was giving me calling issues.
Update 2 after some fiddling I found that after flashing Pico Capps hdxposed is needed to make the play store work on this build http://forum.xda-developers.com/showthread.php?t=2618158
Update 1 New lolipop ota, this appears to be based on lolipop 5.1 and as such requires xposed unofficial by romracer if you want to use xposed Xposed for 5.0 would not flash for me. Same upgrade steps as before just this one instead of the bottom one and change your xposed package
https://mega.nz/#!i5RRCKQZ!NC291mcIo-2yzr23j8Vg_mLZ11ECql4lL_xen6xwXuM
update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin
siegesoldier said:
this is the developer preview, sorry if the title is a little misleading. Thanks to http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Use at your own risk.
https://www.dropbox.com/s/38i2lqq5p...review_ariel-20.5.2.0_user_520033250.bin?dl=0
Hopefully someone can figure out how to make this thing boot when flashed from TWRP
Click to expand...
Click to collapse
Important update, the instructions below are not to be followed !!! They are historical ...
Same drill as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Replace the original META-INF/com/google/android/updater-script with the one from the zip below. Remove "images" directory. This will ensure that your bootloader stays 4.5.3 and unlocked. When TWRP asks to add root, say yes.
If for some reason you lose TWRP (recovery), reflash it from within 5.0. Since you have root, no biggie. I'll play with this a bit too, but later.
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
siegesoldier said:
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
Click to expand...
Click to collapse
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip).
The trick is that you install Lollipop, install root, and install the new bootloader separately. It should boot OK and you should have root in 5, but you'll lose TWRP (it won't be able to boot since the bootloader will probably be signed). To get TWRP back you'll need to downgrade to 4.5.3
bibikalka said:
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip
Click to expand...
Click to collapse
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
siegesoldier said:
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
Click to expand...
Click to collapse
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Upon reflection, there is a chance you have a bit of a soft brick. If the factory reset option does not come up, it may end up a little tricky to fix things. I wonder if you'd be able to connect via adb before it reboots.
bibikalka said:
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Click to expand...
Click to collapse
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
siegesoldier said:
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
Click to expand...
Click to collapse
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
I think TWRP just blocked it from updating. Oh well, if the ports at home don't work, I was eventually going to get it replaced anyway since I had a blue discoloration on my screen. Glad to be of some moderate use to the community instead of a leecher for once. May the next person have some luck!
bibikalka said:
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
Click to expand...
Click to collapse
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
siegesoldier said:
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
Click to expand...
Click to collapse
So no adb anymore? I am not sure how SuperSu comes in, there gotta be su program somewhere.
Anyway, the great news is that JMZ is going to be back soon. That's going to boost our tinkering capabilities by 300%
siegesoldier said:
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Click to expand...
Click to collapse
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
bibikalka said:
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
Click to expand...
Click to collapse
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
siegesoldier said:
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
Click to expand...
Click to collapse
Interesting, at what stage of the update did this happen? 5.2.0 file system is slightly packaged and is pain in the neck to peak into, but in 4.5.3 the recovery is updated via a pretty specific command install-recovery.sh , and I cannot find any references to this in updater-script. So I wonder at what stage will this be run. Also, there is no direct image for recovery, one has to reconstruct it as the commands below do. A bit messy ...
install-recovery.sh
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Edit: It kind of looks like /system/etc/install-recovery.sh will be run at every boot. So I wonder if TWRP just renames it to something and calls it "protection". I guess one can double check the file system after 5.2.0 update while still in TWRP, and see what happened to recovery files.
Help
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
hawkazn said:
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
Click to expand...
Click to collapse
Last time this procedure ended up with a soft brick. Are you sure you want to pursue this route?
Help
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
hawkazn said:
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
Click to expand...
Click to collapse
Meaning exactly what? It'd be possible to replace the camera app, one for another. Do you think some other system stuff is involved such as some sort of settings?
You'll have to find a way to mount the big 5.2.0 system update file as a filesystem, then you could read what's in there, including the camera stuff.
TWRP help
So I downloaded the zip file for 5.0 and it flashed and asked to install super user. I had to download the apk for supersu and then update it.
But the problem is that I lost my twrp. I push the volume + and power and it just reboots. I also lost my play store. Any thoughts how to get twrp back on?
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Why dont you try to revert back stock using a factory image?
chichu_9 said:
Why dont you try to revert back stock using a factory image?
Click to expand...
Click to collapse
I used MDB08M factory instead of MDB08L which originally from the phone, I am not sure this the course of the problem.
The red exclamation usually means either no recovery or incompatible recovery. Did you flash mmb29m recovery for mdb08m rom? If you get stuck too bad you can always enter fastboot and just reflash everything its not that hard to do.
dontbeweakvato said:
The red exclamation usually means either no recovery or incompatible recovery. Did you flash mmb29m recovery for mdb08m rom? If you get stuck too bad you can always enter fastboot and just reflash everything its not that hard to do.
Click to expand...
Click to collapse
Yes, I flashed whole mmb29m factory image over mdb08m. Still can't boot to recovery manu . I'm worried about OTA will fail.
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Once you're on that screen, you've held down the power button then pressed and released volume up right?
Sent from my SM-N920T using Tapatalk
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Get into fastboot, then "fastboot flash recovery xxxxxxxx.img" obviously replacing the x's with the file name. Just reflash the recovery for the same factory image you flashed. Very possible that you just need to reflash the recovery image.
spc_hicks09 said:
Get into fastboot, then "fastboot flash recovery xxxxxxxx.img" obviously replacing the x's with the file name. Just reflash the recovery for the same factory image you flashed. Very possible that you just need to reflash the recovery image.
Click to expand...
Click to collapse
Tried but doesn't work.
Sent from my Nexus 6P using Tapatalk
Flash the recovery via fastboot :
fastboot flash recovery xxx.img
fastboot reboot-bootloader
Now, when your phone reboots to bootloader, using the volume keys, find "recovery" and use the power button to confirm.
profit.
he has to press the power button and vol up on that screen to get into recovery just like guy in post 7 said...
factory recovery doesnt boot all the way into it by default, requires a user button input once it gets to that android exclamation screen
kauemelhado said:
Flash the recovery via fastboot :
fastboot flash recovery xxx.img
fastboot reboot-bootloader
Now, when your phone reboots to bootloader, using the volume keys, find "recovery" and use the power button to confirm.
profit.
Click to expand...
Click to collapse
I did this, the red little thing didn't go away
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
I did this, the red little thing didn't go away
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Did you try downloading another recovery file?
That's really strange.
I was having this error when I tried to flash twrp and boot direclty to system (skipping the recovery boot).
Did you try to install twrp?
---------- Post added at 01:53 PM ---------- Previous post was at 01:48 PM ----------
Another thing..
The system boots up normaly?
To solve this, I did the procedure that I just told you + before booting into twrp, I flashed vendor.img..
Dunno if that could cause this issue
kauemelhado said:
Did you try downloading another recovery file?
That's really strange.
I was having this error when I tried to flash twrp and boot direclty to system (skipping the recovery boot).
Did you try to install twrp?
Click to expand...
Click to collapse
When I root I installed TWRP, revert back all to stock after unroot. I have to stay unroot because of the company app. Just want to be easy to update on OTA,
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
When I root I installed TWRP, revert back all to stock after unroot. I have to stay unroot because of the company app. Just want to be easy to update on OTA,
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I know that feel bro, my company also use an app that verifies for root..
I'm rooted, but on 6.0 I had only twrp w/ no root. no problems..
kauemelhado said:
I know that feel bro, my company also use an app that verifies for root..
I'm rooted, but on 6.0 I had only twrp w/ no root. no problems..
Click to expand...
Click to collapse
So you can install twrp without root as I understand. Then do you need to lock your phone after install twrp (unlock before install twrp, right?), and also how do you do the update OTA or upgrade to 6.0.1, etc..? Thx
VanGolfer said:
So you can install twrp without root as I understand. Then do you need to lock your phone after install twrp (unlock before install twrp, right?), and also how do you do the update OTA or upgrade to 6.0.1, etc..? Thx
Click to expand...
Click to collapse
I guess you can't lock your bootloader with Twrp.
Then, to take ota's just simply flash the img files.
;s
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.