Related
My phone is f'd up.
I tried installing Liquid Smooth 6/10 version, and I got nothing but system UI FC's over and over. So, I held power and volume up until the screen rebooted, and then volume down to get to bootloader.
Then, I selected recovery from there. When I got into recovery, there was nothing in the internal memory, so I did the "fix" where you type in adb on your computer. Every thing went well, I suppose, but when I tried to reboot, it went to the splash screen and did nothing else.
Well, I went back into recovery to restore a backup, a stock Sense back up, and TWRP rebooted. It has been doing this every time I try to get into recovery. I can't do anything. I even installed a previous TWRP by going into bootloader and using an SD converter card with my PC, because ADB doesn't even recognize the device anymore.
I was using Cpt Throwbacks recovery, the newest one, and then I tried reverting to an older one.
Any help....PLEASE!?
Have you tried formatting data and internal storage?
Do you have a recovery log?
Captain_Throwback said:
Have you tried formatting data and internal storage?
Do you have a recovery log?
Click to expand...
Click to collapse
I tried redoing a wipe of dalvik, cache, system, and data....have not tried to do internal, but it reboots before it finishes anyway.
I will try again to do internal.
mcwups1 said:
I tried redoing a wipe of dalvik, cache, system, and data....have not tried to do internal, but it reboots before it finishes anyway.
I will try again to do internal.
Click to expand...
Click to collapse
Sounds like an RUU might be in your future. Some partition(s) seem to be corrupted.
Captain_Throwback said:
Sounds like an RUU might be in your future. Some partition(s) seem to be corrupted.
Click to expand...
Click to collapse
Capt, I did this "fix".
http://forum.xda-developers.com/showthread.php?t=2773203
Could this mess up my partitions?
mcwups1 said:
Capt, I did this "fix".
http://forum.xda-developers.com/showthread.php?t=2773203
Could this mess up my partitions?
Click to expand...
Click to collapse
I honestly don't know. If you used that command I assume you also had the random encryption issue, which could mean you have a different problem altogether.
Did you try using the partition repair options in TWRP?
Captain_Throwback said:
I honestly don't know. If you used that command I assume you also had the random encryption issue, which could mean you have a different problem altogether.
Did you try using the partition repair options in TWRP?
Click to expand...
Click to collapse
I will try partition repair, but is that on the newest version only?
I can still get into bootloader, and when I plug it in to my computer, it still makes the connection sound, but recovery will not stay active. After about 10 seconds, it reboots to splash screen, but goes no further because I don't believe there is anything installed now.
Well, it won't stay in TWRP long enough to do anything. My internal is there now at least. I just don't get it.
Running RUU as we speak. I hope that since I have the .13 firmware installed, that it won't mess up.
Wow. Again.
I made a mistake by doing a backup, then trying to install another ROM, but forgot to wipe data. Went through the process (splash screen, boot animation, updating apps) and it booted for a second and rebooted. I figured it would happen, since I didn't wipe correctly.
Try to go into TWRP, and the damn thing reboots out of TWRP! I can't stay in TWRP for more than 5-7 seconds, before it reboots on its' own. Went to flashboot to reinstall TWRP, no change. I can't even do a restore.
I know I installed a ROM once through fastboot with a "fastboot flash zip rom.zip" command, but that isn't working either. Can't get a log, because I can't stay booted in anything other than fastboot/bootloader.
I searched for an answer, and this is all I got! My phone must be borked. Guess I'll have to RUU again.
I had this issue last night and I got it to restore a backup by unplugging it from the wall first. I think the voltage is too high or something during a flash or something.
mcwups1 said:
I know I installed a ROM once through fastboot with a "fastboot flash zip rom.zip" command, but that isn't working either. Can't get a log, because I can't stay booted in anything other than fastboot/bootloader.
Click to expand...
Click to collapse
You can't install a custom ROM this way, unless it's been built into an image file. This is only for flashing image files that have been zipped up with an android-info.txt file.
Have you tried updating firmware, then booting back into recovery?
Captain_Throwback said:
You can't install a custom ROM this way, unless it's been built into an image file. This is only for flashing image files that have been zipped up with an android-info.txt file.
Have you tried updating firmware, then booting back into recovery?
Click to expand...
Click to collapse
I already RUU'd, so I should have had the appropriate firmware.
mcwups1 said:
I already RUU'd, so I should have had the appropriate firmware.
Click to expand...
Click to collapse
I was suggesting flashing the firmware to normalize your device, so that maybe you could get back into recovery. I wasn't suggesting it because I thought you were on the wrong firmware.
Captain_Throwback said:
I was suggesting flashing the firmware to normalize your device, so that maybe you could get back into recovery. I wasn't suggesting it because I thought you were on the wrong firmware.
Click to expand...
Click to collapse
I ended up RUU'ing again.
If it happens again, I will take your advice and report back.
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
RealROGWaffle said:
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
Click to expand...
Click to collapse
its a normal m error. flash a custom kernel to get rid of it. despair has one, elite has another, and there are more out there.
RealROGWaffle said:
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
Click to expand...
Click to collapse
This error is often a result of system/bootloader mismatch. Do you have 5.1.1 with M bootloader?
simms22 said:
its a normal m error. flash a custom kernel to get rid of it. despair has one, elite has another, and there are more out there.
Click to expand...
Click to collapse
Awesome, thank you very much.
cam30era said:
This error is often a result of system/bootloader mismatch. Do you have 5.1.1 with M bootloader?
Click to expand...
Click to collapse
Nope, running M with the M bootloader.
Did you flash TWRP recovery or the M (factory) recovery?
If TWRP, did you allow it to try and flash SU?
I didn't have that error until flashing TWRP and allowing it to try and root upon exiting TWRP.
I was a able to clear it by flashing a different kernel, booting to TWRP, and wiping caches (I didn't do a Factory Reset).
jasoraso said:
Did you flash TWRP recovery or the M (factory) recovery?
If TWRP, did you allow it to try and flash SU?
I didn't have that error until flashing TWRP and allowing it to try and root upon exiting TWRP.
I was a able to clear it by flashing a different kernel, booting to TWRP, and wiping caches (I didn't do a Factory Reset).
Click to expand...
Click to collapse
everyone who flashed m without a separate kernel got that error. its a m thing for now.
my phone wont boot up after it flashes that.. dont know what to do..
dave2metz said:
my phone wont boot up after it flashes that.. dont know what to do..
Click to expand...
Click to collapse
what did you flash? .img files or via twrp flashable zip? did you flash the bootloader? you have to or it won't ever boot.
simms22 said:
what did you flash? .img files or via twrp flashable zip? did you flash the bootloader? you have to or it won't ever boot.
Click to expand...
Click to collapse
My device keeps flashing as well. I fastboot .img files
I only had this error when I flashed twrp. When I was stock M and no twrp didn't have this issue
md1008 said:
I only had this error when I flashed twrp. When I was stock M and no twrp didn't have this issue
Click to expand...
Click to collapse
Same... flashing twrp kills my M install. Say's it's booting but all I get is a black screen.
Now it's my turn to join. Any fixes for those that won't boot up at all? I think I may have a brick. How did you get out of this?
sbrownla said:
Now it's my turn to join. Any fixes for those that won't boot up at all? I think I may have a brick. How did you get out of this?
Click to expand...
Click to collapse
you have to flash the m bootloader before flashing m, or it will never boot up.
Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)
kitsunezero said:
Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A inorder to get expertise help
-Vatsal
I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?
paulgiro said:
I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?
Click to expand...
Click to collapse
I'm a idiot http://forum.xda-developers.com/memo-pad-7/general/5-0-brick-solution-asus-memo-pad-7-t3134814,
I didn't read this "This package is for "K013" devices; this is a "K013_1"." I was bricked for a week because of a random device "name change?" Well here are the steps I took to make a flashable lollipop that wouldnt brick me. What you are doing here is telling the script that does the update that it does not need to verify your tablet model since it is wrong anyways.
Now i follow the steps and my tablet is boot, i'm waiting.
EDIT: Still bricked, now i can enter in fastboot mode but when i power on the tablet, after the logo, the screen is black
I have the same problem and can't find any solution yet :crying::crying:
sidane12 said:
I have the same problem and can't find any solution yet :crying::crying:
Click to expand...
Click to collapse
i can install the original firmware, but now still bricked with the same error
kitsunezero said:
i can install the original firmware, but now still bricked with the same error
Click to expand...
Click to collapse
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.
Ruben Craveiro said:
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.
Click to expand...
Click to collapse
how can i do that? can you make a tutorial please ><?
kitsunezero said:
how can i do that? can you make a tutorial please ><?
Click to expand...
Click to collapse
Load temp recovery select wipe, advanced wipe, format all, reboot to bootloader, load temp recovery, install, reboot normally, if it boots but its on bootloop just make another rebokt and itshould boot
Unavailable
Thank you...very good working on tab 2:good:
Jancar 52 mcpe said:
Hi to everyone! I've been working hard trying to port Lineage OS 14.1 (LOS) to Galaxy Tab 2 (for the moment only is available in espresso3g). I've ported Lineage OS from the Nexus 7 2013 (LTE-deb), because both of them have an ARMv7a processor.
REMEMBER THAT IS IN AN EARLY BETA RELEASE, THIS MAY CONTAINS SO MUCH BUGS!
MAKE A BACKUP BEFORE INSTALL
Guide:
1st. Wipe Dalvik/ART cache, system, cache and data. ...
GApps: go a bit up
Click to expand...
Click to collapse
It takes forever to install on my P3100!!! is this normal it is flashing for more than an hour???
and I am using twrp 3.0.3.0!
thanks.
I look forward to expressowifi version .......tanX
ginore said:
I look forward to expressowifi version .......tanX
Click to expand...
Click to collapse
+1
test by its dev too pls for more detail result.
never stop developing, ty.
It seems some people has installing errors (the installation never ends), so let's start the bug fixing time!
ballakanzri said:
It takes forever to install on my P3100!!! is this normal it is flashing for more than an hour???
and I am using twrp 3.0.3.0!
thanks.
Click to expand...
Click to collapse
Try to install a newer version, if this doesn't works tell me and I will try to fix the error
Hi again guys! I have a quickly update! I fixed the infinite install, but now says error 7 when verify the image, don't worry about it, I wiped dalvik/art cache but it gets stucked in bootloop, fixing it now
twrp 3.1.0-2, espresso3g.
when i'm installing the signed_lineage-14.1-20170402-UNOFFICIAL-espresso3g-BETA.zip,
it stuck at the "patching system image unconditionally..."
somebody can help me?
pedrobiscoito said:
twrp 3.1.0-2, espresso3g.
when i'm installing the signed_lineage-14.1-20170402-UNOFFICIAL-espresso3g-BETA.zip,
it stuck at the "patching system image unconditionally..."
somebody can help me?
Click to expand...
Click to collapse
Same here, Please fix it!!!
+1 me too! twrp 3.1.0-2
Is the download link broken? I get the message "no mirrors found".
EDIT: Never mind, finally it worked.
pedrobiscoito said:
twrp 3.1.0-2, espresso3g.
when i'm installing the signed_lineage-14.1-20170402-UNOFFICIAL-espresso3g-BETA.zip,
it stuck at the "patching system image unconditionally..."
somebody can help me?
Click to expand...
Click to collapse
I meet this case, too.
nguhanhson said:
I meet this case, too.
Click to expand...
Click to collapse
Me to, what's the heck
hey, thanks for your work, what does your lineage.dependencies file look like? thanks
Not flashing
TWRP 3.03
it stuck at the "patching system image unconditionally..."
lucien68 said:
Not flashing
TWRP 3.03
it stuck at the "patching system image unconditionally..."
Click to expand...
Click to collapse
I'm working on it, it seems is an error of system.transfer.list or updater-script, but I will try to solve it, after this I will start with something you maybe will like, sorry for the inconvenience
EDIT: I have the solution but it gives error 7, system partition has unexpected OTA contents. Working on it since 2 weeks ago, sorry for the inconvenience again :b
idk why this need to be ported from a different device...
Jancar 52 mcpe said:
I'm working on it, it seems is an error of system.transfer.list or updater-script, but I will try to solve it, after this I will start with something you maybe will like, sorry for the inconvenience
EDIT: I have the solution but it gives error 7, system partition has unexpected OTA contents. Working on it since 2 weeks ago, sorry for the inconvenience again :b
Click to expand...
Click to collapse
Thank you for the answer.
Have you got a link to download the ROM with error7, i would like to test it, i have a oneplus one with LOS14.1 and i like this ROM.
Thank you for your job, and sorry for my bad english
If i try to uninstall magisk from my Honor 8 i will end up with a bootloop until i reinstall magisk.
I tried to uninstall from the app and with the uninstaller zip same result.
Does someone know how to fix this
After uninstalling, also flash the stock boot image from your ROM/firmware package/factory image.
Didgeridoohan said:
After uninstalling, also flash the stock boot image from your ROM/firmware package/factory image.
Click to expand...
Click to collapse
OK so did as you said but i still get bootloops . No idea how something like that can happen but something seems not right guess i am stuck with magisk installed until i wipe and reinstall it completly.
resov said:
OK so did as you said but i still get bootloops . No idea how something like that can happen but something seems not right guess i am stuck with magisk installed until i wipe and reinstall it completly.
Click to expand...
Click to collapse
Did you try a complete dirty flash of your ROM/firmware package/factory image?
Didgeridoohan said:
Did you try a complete dirty flash of your ROM/firmware package/factory image?
Click to expand...
Click to collapse
If i do that my data will get wiped right? I would like to avoid that. But it looks like isn't only on my end someone else reported the same problem so maybe it's a magisk bug.
resov said:
If i do that my data will get wiped right? I would like to avoid that. But it looks like isn't only on my end someone else reported the same problem so maybe it's a magisk bug.
Click to expand...
Click to collapse
Dirty flashing means you don't wipe your data.
It's possible there's some kind of verified boot thing that you're going to have to restore, or something like that. Ask in your device's forum.
resov said:
If i do that my data will get wiped right? I would like to avoid that. But it looks like isn't only on my end someone else reported the same problem so maybe it's a magisk bug.
Click to expand...
Click to collapse
Not magisk, it seems to be something with your device, some samsungs too.
Seems lke this happens to phone's that has auto-encrypted /data partition. This happens to me on a Samsung S7 (Android 8/oreo) and my "stock os" has auto-encrypt of /data if /system is touched. When uninstalling via Magisk, usually Magisk will restore your original boot.img (it did so during my uninstall, but still i get bootloop). Tried two nandroid's done of just boot-partition, but only one of them worked, and it only worked if I reinstalled Magisk. Without magisk I had bootloop's with all my stock.img availible (ps: i've not yet tried the "dirty flash replacement of the boot.img", I guess using ODIN? But hey, dunno if it is the AP,BL,CP,or CSC part that needs to be dirty-flashed then, so since im tired of setting up the /data patition (going through first phone install, installing apps and settings again, then I'll wait for further/better info.
But hey
Didgeridoohan said:
After uninstalling, also flash the stock boot image from your ROM/firmware package/factory image.
Click to expand...
Click to collapse
I don't know how to thank you, you saved my life!