Hi!
I recently installed lineageOS 14 over stock 6.0, since everyone praised it. However, it randomly rebooted in my pocket during the day hourly, so I decided to go back to stock.
But it neither boots with stock based rom, nor on a freshly installed stock with flashtool. It stucks at the bootanimation for hours, and doesn't reboot like it does in similar situations.
What the hell is that, could anyone help me?
(Btw my Z1C has the same problem)
I also installed Lineage OS, but after having a problems with keyboard i revert to stock with flash tool ver 0.9.18.6. I accidentally installed 5.1.1 uk version then after reboot i download new 6.0.1 ver and installed it over. Phone is working ok, no reboots. Maybe you should try to install again stock rom or change the flash tool version
Wipe APPS_LOG and USERDATA is mandatory when rolling back to previous Android versions, maybe you have missed that part?
iXaidyiu said:
Wipe APPS_LOG and USERDATA is mandatory when rolling back to previous Android versions, maybe you have missed that part?
Click to expand...
Click to collapse
Last time I think it did work without wiping userdata, so I didn't check those to wipe, however, to make sure I did a factory reset before from recovery. But I guess apps_log is not erased with a factory reset?
Anyway, thank you very much, I will try again this way.
Ps. It might be the cause that it still didn't boot when I tried a different rom with flashtool.
Update: Thank you, that did the trick, successfully booted!
Related
Hey Guys,
I have an unusual issue when it comes to trying to flash custom ROM's onto my Nexus 9.
I have already unlocked the bootloaded, installed the latest version of TWRP which worked fine.
I then went to do the usual wiping everything off my tablet before going any further (Dalvik Cache, System, Data, Internal Storage and Cache)
Then I use MTP to move the ZIP's that I want to install onto the internal storage (I've tested CyanogenMod 12 and the latest version of LiquidSmooth (At seperate times) )
The install process goes okay and doesn't show up any errors.
Then when I go to reboot the Nexus 9, I get the static "Google" logo (the splash screen before the operating system's splash) and it just sits there for 12 hours until the battery slowly drains (litterally 12 Hours)
Any idea's how to fix this? I can boot back into fastboot and access the recovery. I can also restore using the softbrick option in the Nexus Tool Kit to boot back into a fully functioning Android 6.0 but obviously that's not the aim.
Thanks for taking the time to read this
TechKno said:
Hey Guys,
I have an unusual issue when it comes to trying to flash custom ROM's onto my Nexus 9.
I have already unlocked the bootloaded, installed the latest version of TWRP which worked fine.
I then went to do the usual wiping everything off my tablet before going any further (Dalvik Cache, System, Data, Internal Storage and Cache)
Then I use MTP to move the ZIP's that I want to install onto the internal storage (I've tested CyanogenMod 12 and the latest version of LiquidSmooth (At seperate times) )
The install process goes okay and doesn't show up any errors.
Then when I go to reboot the Nexus 9, I get the static "Google" logo (the splash screen before the operating system's splash) and it just sits there for 12 hours until the battery slowly drains (litterally 12 Hours)
Any idea's how to fix this? I can boot back into fastboot and access the recovery. I can also restore using the softbrick option in the Nexus Tool Kit to boot back into a fully functioning Android 6.0 but obviously that's not the aim.
Thanks for taking the time to read this
Click to expand...
Click to collapse
I haven't flashed either of those ROMs but perhaps you need different vendor images or something.
What build # are you on?
The latest is: mra58n
I personally am on Pure Nexus, and I didn't have to flash anything besides the ROM.
I just got the tablet on the 40% off deal a few weeks ago, it came with an early LP build, I first flashed the mra58n factory image, then I unlocked bootloader installed TWRP and rooted and made a backup.
Then I flashed Pure Nexus and all has been running smooth.
I would suggest giving that ROM a flash - it's been updated to Android 6.0 and runs great and battery is amazing.
andybones said:
I haven't flashed either of those ROMs but perhaps you need different vendor images or something.
What build # are you on?
The latest is: mra58n
I personally am on Pure Nexus, and I didn't have to flash anything besides the ROM.
I just got the tablet on the 40% off deal a few weeks ago, it came with an early LP build, I first flashed the mra58n factory image, then I unlocked bootloader installed TWRP and rooted and made a backup.
Then I flashed Pure Nexus and all has been running smooth.
I would suggest giving that ROM a flash - it's been updated to Android 6.0 and runs great and battery is amazing.
Click to expand...
Click to collapse
Thanks for the response, just tried flashing Pure Nexus to it but with the same thing happening. I know it's only been 5 mins so far but it surely should have atleast moved onto the OS's splash?
This was the version I used: pure_nexus_flounder-5.1.1-20150817.zip
I shouldn't need a working OS installed as the base due to the fact that installing a new OS would just overwrite it?
TechKno said:
Thanks for the response, just tried flashing Pure Nexus to it but with the same thing happening. I know it's only been 5 mins so far but it surely should have atleast moved onto the OS's splash?
This was the version I used: pure_nexus_flounder-5.1.1-20150817.zip
I shouldn't need a working OS installed as the base due to the fact that installing a new OS would just overwrite it?
Click to expand...
Click to collapse
that is Android 5.1.1 Lollipop
We want Android 6.0 Marshmallow
pure_nexus_flounder-6.0-20151113.zip
If this doesn't work I would personally flash the mra58n and start over.
Make sure to wipe in recovery before flashing.
andybones said:
that is Android 5.1.1 Lollipop
We want Android 6.0 Marshmallow
If this doesn't work I would personally flash the mra58n and start over.
Click to expand...
Click to collapse
Yeah, I think he's right. Sounds like you have a mishmash of android 5.1.1 and 6.0
Start clean by flashing the latest factory image (bootloader, boot, system, data, vendor). Once that's running, then you can flash TWRP (I suggest using the custom TWRP found under the FireIce kernel thread) and install an android 6.0 custom ROM.
Whichever ROM you choose, make sure to read thru its thread carefully. There are a number of things that can cause bootloops, so be sure to follow the installation instructions for that ROM.
TechKno said:
Hey Guys,
I have an unusual issue when it comes to trying to flash custom ROM's onto my Nexus 9.
I have already unlocked the bootloaded, installed the latest version of TWRP which worked fine.
I then went to do the usual wiping everything off my tablet before going any further (Dalvik Cache, System, Data, Internal Storage and Cache)
Then I use MTP to move the ZIP's that I want to install onto the internal storage (I've tested CyanogenMod 12 and the latest version of LiquidSmooth (At seperate times) )
The install process goes okay and doesn't show up any errors.
Then when I go to reboot the Nexus 9, I get the static "Google" logo (the splash screen before the operating system's splash) and it just sits there for 12 hours until the battery slowly drains (litterally 12 Hours)
Any idea's how to fix this? I can boot back into fastboot and access the recovery. I can also restore using the softbrick option in the Nexus Tool Kit to boot back into a fully functioning Android 6.0 but obviously that's not the aim.
Thanks for taking the time to read this
Click to expand...
Click to collapse
You should erase your internal storage. It happen to me I did the same steps that you did and I had to re flash the system files all over again. Once finish I only wipe dalvik cache,cache and data and it work perfectly
I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Dileter said:
I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Click to expand...
Click to collapse
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
Yes I am rooted and I tried flashing this ROM http://forum.xda-developers.com/lg-g5/development/unofficial-cyanogenmod-14-1-lg-g5-h850-t3494001
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
I also dont really care if I lose photos or anything I already got all of them saved on my pc before I even started rooting the damn thing. I do need to ask tho how do you dirty flash and Do i just flash twrp normally since im already in it or ??? As I said im rlly new to this
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
DidierMoulin said:
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
Click to expand...
Click to collapse
Okay thanks a lot I will see if Any of it helps.
Please report.
DidierMoulin said:
Please report.
Click to expand...
Click to collapse
UPDATE I fixed it I just downgraded to the 2nd to lates version of twrp and it booted normally. Now I regret flashing the pixel one XDD If you have any idea for a good custom rom tell me Thanks for the help it actually helped a lot gave me the idea to downgrade the twrp recovery.
What you mean by pixel one xxd?
DidierMoulin said:
What you mean by pixel one xxd?
Click to expand...
Click to collapse
Its a 7.1.1 android rom from the google pixel
Dileter said:
Its a 7.1.1 android rom from the google pixel
Click to expand...
Click to collapse
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Pphish20 said:
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Click to expand...
Click to collapse
What he asked [emoji32]
It's happened to me too! Like three times lol. Just use UpperCut / LG UP to flash the latest nougat rom. That will fix the issue. You will need to re-root after that. There are instructions in this forum that tell how to do all of that. Good luck
Well and don't flash a ROM which is not for your device...
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
gordonthegopher said:
Formatting /data in TWRP uses up all the blocks, but encryption from Lineage needs 16kb of free space at the end of the partition to store the headers.
Click to expand...
Click to collapse
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Hi guys,
I'm kind of stuck right now because I cannot encrypt my phone anymore and I don't know why. I got my phone last year and installed LOS 14.1 right away. For security reasons I also encrypted it - without any issues whatsoever. When LOS 15.1 came out, I upgraded my phone, with encryption still working. A couple of days back for some reason I decided to do a factory reset. Obviously, the device wasn't encrypted anymore after the reset. I then installed the new nightly of LOS (20180807) and tried to encrypt my phone once again. When I select "Encrypt phone", I need to enter my PIN, the phone restarts and reboots without encryption being started.
What I've done so far:
I've flashed two different TWRP versions: 3.2.3.0 and a customized one (https://forum.xda-developers.com/re...other-development/rom-lineageos-15-0-t3690465).
I've clean installed different LOS versions (unofficial LOS 14.1 and LOS 15.1 starting from the 20180710 release)
I've clean installed Omnirom (current release and a release from 20180107).
I've even flashed MIUI 9 and reinstalled LOS thereafter because some guy in the above mentioned LOS thread wrote, that this did the trick for him.
I've disabled WI-FI and mobile data before trying to encrypt my phone, because I found a blog article stating that this might help.
Nothing helped. The phone just reboots and stays unencrypted.
Do you guys have any additional hints or ideas how I can manage to encrypt my phone once again? Could another TWRP version do the trick? Is TWRP even involved in any kind when it comes to encryption of the OS? Do you think another ROM could be helpful?
Click to expand...
Click to collapse
Try orangewolf recovery ....
Sent from my Redmi Note 4 using Tapatalk
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
shakil002 said:
Try orangewolf recovery ....
Click to expand...
Click to collapse
Thanks for the advice. But I'm afraid it didn't help
CanBostanci said:
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
Click to expand...
Click to collapse
That's the most ****ed up part. For some people it does work, for some not.
There surely must be some ridiculous small detail we're not getting. Like disabling WI-FI while Bluetooth is enabled.
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
parkbank said:
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
Click to expand...
Click to collapse
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
CanBostanci said:
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
Click to expand...
Click to collapse
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
parkbank said:
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
Click to expand...
Click to collapse
I'm looking forward to hear the results. I'm about to become insane because of this encryption issue.
I've flashed both the dev and stable firmware found in this thread. No success
By flashing I mean factory reset, flashing the firmware and then installing LOS. I noticed, that flashing a new firmware while a ROM is still installed leads to some random ****ups.
After a couple of days of flashing, factory resetting, re-flashing, reading and a lot of cursing I finally found a working solution. I've added the fix to my initial post. Hopefully this helps
I was looking for solutions for quite a while and nothing else worked but did this and my device is encrypted again.
Thank you!
parkbank said:
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Click to expand...
Click to collapse
You have save my day "my MIDO" hehehehe
After the 1st PIE Rom the encryption was broken.
Your Step by Step save this and now Syberia 9 was able to encrypt with success :good:
Thank you one more time for sharing.
Thx!
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
Orangefox worked
is there any plan to fix twrp itself?? thx
Thank you. It worked for me to get Havoc OS 9.0 with hardware encryption on my Redmi Note 3 SE.
I bypassed unlocking the bootloader by doing this. Then I installed TWRP 3.1.0.0 from the recovery, did the reset and everything as instructed here, updated it to 3.3.1.0, rebooted, then flashed the Pie ROM and latest gapps without any further wiping.
I use the first link, I've modified the partition size -> did the trick wihtout formating nor loosing datas
Great, thank-You.
Hi, I want to ask, what is this encryption features you been using? can u tell me?
Its my daughters bog standard, cheap chinese MTK6580 phone (uhappy up580 if it matters)
It came with stock 5.0 a few years back so I flashed TWRP, rooted it, ported a CRdroid 5.1 rom for it and was working fine. Yesterday on boot every app refused to start, or stopped, or froze including stock launcher and settings so I couldnt do anything at all. Booted to TWRP and wiped cache and dalvik but although TWRP said completed, it hadnt.
So decided to wipe EVERYTHING including data and again TWRP said it had but upon reboot the faulty rom was still there, not working.
Tried to flash a backup that ended in tar error, fixed that and it flashed the backup fine, rebooted but it hadnt.
Tried to TWRP flash a new rom, said it had but it hadnt,
Used SPFlash tools to flash the stock 5.0 rom, THAT said it completed after the usual time and procedure, rebooted but it hadnt
Used SPFlash tools to completely format and wipe the phone which also said it had completed but it hadnt.
I CANNOT wipe this phone using any method I know of! or install or flash anything! Just this same custom rom that was fine for years and just went wrong. Does ANYONE know how I can somehow wipe this phone or flash a new rom? Tried flashing a TWRP with SP tools AND a TWRP .img and they all said completed but obviously, nothing did.... I've accidently bricked phones easier than I can deliberately wipe this one
Any help greatly appreciated.
emmc is weared out. therefore it is read only
aIecxs said:
emmc is weared out. therefore it is read only
Click to expand...
Click to collapse
Gah... exactly what I suspected but hoped not
cheers
EDIT: Ignore this!
It just worked this time...
Dear mods, this thread can be deleted.
Hi there,
i really need some help.
Got my hands on a xperia x compact today and it already was on latest stock.
So i unlocked it and flashed LineageOS 19.1
Everything was okay but i had some issues and decided to wipe and start over with lineage 18.1.
After 18.1 bootlooping, it automatically booted into TWRP and from there it hang on splash screen forever.
Also after a reset, it wouldn´t boot into TWRP.
So i tried erasing userdata and cache via fastboot...
After that, TWRP loaded up again but now it had the famous can´t mount data, cache, issue.
So i ended up with a device, that won´t format data, won´t boot any rom (automatically enters recovery mode).
I decided to flash stock via EMMA and accidentally flashed the oldest firmware from the list!
Why is it even on top???
I just noticed it booting up fine and all, but TWRP won´t recognize touch inputs (touch works in stock 7.0 though)
I guess it´s because of the old firmware i just flashed.
So i picked the latest version from the list but unfortunately it seems like it´s still on old android 7 firmware instead of oreo!
The version i flashed is 34.4.A.2.118 which corresponds to oreo, but it seems like something went totally wrong here.
It´s still on the old firmware somehow...
I´m not a noobie flashing phones and stuff but this really is 100% confusing and driving me crazy right now
I actually managed to get 34.3.A.0.252 flashed now, which is slightly newer but still 34.4.A.2.118 won´t upgrade...
Any help is very appreciated
Thank you very much