Hello! Long time lurker on here but first time posting. I follow this guide to unlock bootloader and install twrp on the zc553kl. https://forum.xda-developers.com/zenfone-3/how-to/zenfone-3-max-zc553kl-bootloader-unlock-t3691837
It kind of worked, and it did flash twrp. The only problem is that the twrp although launching, didnt seem to have permissions to access storage, probably due to a data encryption problem. all the storages had 0mb sizes and i couldn't do anything.
So naturally i googled my problem and tried a few methods.
Nothing seemed to work, and i ended up doing an advance wipe. That also failed and it said it didnt have access or permission to do it (something along those lines). Next day i decide to try again and now my internal storage seemed to show.
So i ended up formatting it, and while the files seem to be still there, i changed .ext4 to .ext2 and back again, and then it stopped recognizing the stock rom i still had installed. Please note that before all of this, although twrp didnt work properly, the phone still worked fine and booted into android. My problem is now the stock rom is gone, twrp says no OS installed, and i have tried my best to reinstall the stock rom, but that hasn't worked. Any ideas or help would be welcome thanks guys
Nyoxx said:
Hello! Long time lurker on here but first time posting. I follow this guide to unlock bootloader and install twrp on the zc553kl. https://forum.xda-developers.com/zenfone-3/how-to/zenfone-3-max-zc553kl-bootloader-unlock-t3691837
It kind of worked, and it did flash twrp. The only problem is that the twrp although launching, didnt seem to have permissions to access storage, probably due to a data encryption problem. all the storages had 0mb sizes and i couldn't do anything.
So naturally i googled my problem and tried a few methods.
Nothing seemed to work, and i ended up doing an advance wipe. That also failed and it said it didnt have access or permission to do it (something along those lines). Next day i decide to try again and now my internal storage seemed to show.
So i ended up formatting it, and while the files seem to be still there, i changed .ext4 to .ext2 and back again, and then it stopped recognizing the stock rom i still had installed. Please note that before all of this, although twrp didnt work properly, the phone still worked fine and booted into android. My problem is now the stock rom is gone, twrp says no OS installed, and i have tried my best to reinstall the stock rom, but that hasn't worked. Any ideas or help would be welcome thanks guys
Click to expand...
Click to collapse
i downloaded a previous rom version from asus site and that flashed fine.
Related
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
not_su said:
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Rhymey said:
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Thanks - that's exactly what I've been trying to do. I haven't tried reflashing back to stock with Odin though. Hmmm...
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Click to expand...
Click to collapse
Bell, up here in the Great White North. I don't think locked bootloader is an issue - I was on the previous version of Danvdh's ROM, and everything was hunkydory. I just made the unfortunate decision to encrypt. Big mistake.
May try flashing back to stock. Nothing to lose, at this stage...
Thanks!
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
not_su said:
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
Click to expand...
Click to collapse
Good to hear. Should be able to flash to the rom once again no problem now that it's unencrypted!
Hello to all. First, thank to the devs for all the fantastic work done, and to all the people willing to check and answer these threads. So down to my problem.
When I first got my S5 (SM-G900F) I immediately rooted with cf-autoroot. Tripped knox but worked well. From there I went on to install Twrp and then CM 11. The bugs drove me off, so I wanted a tw based rom. At the time I chose XtrStoLite (spelling?) And that worked a treat.
So after a while I found alliance rom and thought wow, this is great. So I installed it as per the instructions in the OP. Now we get to problem one: I got stuck at the Samsung boot screen. No boot logo, nothing, no matter what I did, even formatted /system, still nothing. I tried a few suggestions from the extremely helpful dev, @Goldie, none of which worked, such as flashing another rom first, so I tried with cm and slimkat. Didn't work. Tried updating supersu, didn't work. Tried different TWRP version, nothing. Tried Philz. Tried different Kernel with and without SELinux set to permissive and still it would need a battery pull at the Samsung "powered by android" screen.
Okay, last resort, flashed stock for my country (south africa), flashed TWRP, installed towelroot, rooted, flashed newest supersu, installed busybox and retried. This time something changed. Instead of freezing at the first Samsung screen, it now showed "Set Warranty Bit: kernel" in yellow at the top. Then the screen would go black, phone would vibrate twice and then reboot. So now I had a boot loop.
It was suggested to try omega, to see what happens. Well, it works fine. To date I've tried 5 different working roms. Was told to flash via omega, so I did, but same issue. At some point when I was on stock I even did a factory data reset, effectively wiping sdcard. Just in case. Formatted the external sdcard too. Formatted everything from /system to dalvik to /cache and /data, and eventually /data/media, and still that didn't work.
I'm really at a loss here. I'm the only one of all the other users with this issue. The devs have gone way over and beyond to help me, and that makes me happy. I donated because they've done more than others would. But basically I just need ideas of what the problem could be and why this is happening, if anyone has any ideas.
Find a screen shot of my "About" page here.
My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.
vizavalk said:
My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.
Click to expand...
Click to collapse
Format Data from twrp sometime corrupts the file system and brick the phone. (It's happened to me once)
The best way is to flash official firmware via odin and start from there.
I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.
vizavalk said:
I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.
Click to expand...
Click to collapse
CWM is outdated. Your best bet is TWRP. Try version 3.0.0.
Factory reset doesn't wipe your internal memory, if that's what you mean, you will have to do it manually.
Also, I recommend wiping data, cache, dalvik and system partitions manually from the advanced wipe menu. Factory reset only wipes data and caches, not system.
Oh, and about that stuck at setup issue, just skip that step if possible, you can still change that crap later
If you are unable to set up the ROM, you could flash back to a completely stock ROM and start over.
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.
vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
GDReaper said:
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.
Click to expand...
Click to collapse
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Lennyz1988 said:
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
Click to expand...
Click to collapse
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?
vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?
Click to expand...
Click to collapse
Not that I know. Just pick the one without Dynamic.
vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Click to expand...
Click to collapse
The initial setup process is related to gapps. And I don't recall there being any software update requests during the initial setup. It tells me to wait while it scans for network and WiFis, but I always skip those steps.
Open gapps sometimes work and sometimes they don't. It varies from day to day, since they are updated daily.
Just find a gapps package that works and stick to it until another version of android.
I just want to report back that my CM13 works perfectly with Banks GApps. Thanks to everyone who has helped!
Yeah. I was trying to unlock my bootloader using Controllerboy's guide, and I managed to install TWRP. I also managed to unlock my bootloader. When I tried to restore my phone using the backup I put on my computer and back to my A7, it won't boot - it's stuck on the "ZTE powered by android" boot screen.
I think that the problem is that when I was copying the backup from my phone to my computer it said "unspecified error" but still let me copy the files (the files and the sizes remained the same) so I just ignored it. Whoops!
So I tried to install CM13 in hope that it will somehow fix things, and unsurprisingly everything is still the same.
So. What do I do? I think that the problem was that I backed-up system and tried to restore system (probably).
Anyone got a solution? Or even a system restore that will cure my phone?
Any help will be greatly appreciated! Thanks in advance!
I managed to solve the problem myself by re-wiping dalvik and installing CM 13! Odd that it worked this time and not the other time I tried it, but at least it works
I haven't followed development of the 6T since November so please forgive me if this has been answered 100 times.
The steps to flashing custom non-OOS ROM's is to; flash ROM/flash TWRP installer/reboot recovery/flash gapps/flash magisk
The weird issue for me is when I reboot recovery after flashing the ROM and TWRP when I go to install gapps all my files are encrypted. My way around this was to sideload gapps and magisk and everything booted up fine. When I go back to recovery after the first boot all the files are normal again.
This has happened both times I've flashed a ROM.
I'm sure this has an easy answer and it's most likely due to a step I didn't execute properly -- or at all. I did a lot of reading and making sure I understood the process before rooting my device but as far as flashing ROM's I was noticing a lot of conflicting info which I've never seen before on any other device. Anyway, other than this I haven't had any issue.
Thanks for any feedback.
Security issue. Best way around it is to either format data before flashing and/or remove your lockscreen security pin before flashing.
Deleted
ogkillergreen said:
Security issue. Best way around it is to either format data before flashing and/or remove your lockscreen security pin before flashing.
Click to expand...
Click to collapse
I never use any lock. Always just use Swype to unlock. I'm aware of the issue with using a lock though. I read that people had problems. I just haven't seen where any one brought up my exact issue. It doesn't seem to effect anything so I'm not stressing it too bad. Eventually I'll get around to troubleshooting it.
I've flashed almost every ROM for 6T till now and every time I flash a ROM I'm having exactly the same issue as you. I've also tried formatting data several times, but the issue with unreadable data in TWRP after flashing a ROM returns every single time. I've tried multiple combinations of flashing, wiping etc. and it's always the same. However, what I'm doing in such case is flashing gapps + magisk from USB-C pendrive, no need to sideload, just mount USB and flash files from that as usual. After doing that I can boot to ROM and the data is readable again. I just need to remember to have this pendrive close to me when I'm flashing a new ROM.
BreathingWounds said:
I've flashed almost every ROM for 6T till now and every time I flash a ROM I'm having exactly the same issue as you. I've also tried formatting data several times, but the issue with unreadable data in TWRP after flashing a ROM returns every single time. I've tried multiple combinations of flashing, wiping etc. and it's always the same. However, what I'm doing in such case is flashing gapps + magisk from USB-C pendrive, no need to sideload, just mount USB and flash files from that as usual. After doing that I can boot to ROM and the data is readable again. I just need to remember to have this pendrive close to me when I'm flashing a new ROM.
Click to expand...
Click to collapse
Thanks for the tip and info. I don't mind sideloading because it's fast and anytime I mess with my phone it's when I'm at my PC. I've been using adb for so many years it's my go-to whenever my phone is acting stupid.
The second time I flashed a ROM I didn't even worry about flashing gapps, just magisk. And I stacked them. So ROM, TWRP, Magisk. Then rebooted system. I actually prefer this anyway because then you boot straight to the launcher with no setup process. Then I go back and flash GAPPS. I actually have used this flashing process for years because I hate the setup after a first time boot.