I apologize for the lengthy back-story -
I had, but have since returned, an Asus Zenfone Max M1 ZB555KL. I thought it was a decent phone, but after spending the better part of the week setting it up (rooting, etc...) I inserted my sim and that sent the phone into a non-stop cyclic boot loop. Took the sim out & it worked fine. Research on the Asus forums proved that this is a widespread problem with the phone. Hence, I unrooted, factory reset it, and returned it.
Anyway, while playing with this phone for the week, I managed to root it with Magisk, and port a mostly functional TWRP. I never flashed TWRP...just booted to it. So that may, or may not, be the cause of my issues. I was able to select/browse the external sd card & flash zips as well. I had even performed a backed up to the external sd card. I was not, however, able to select/browse the internal storage. Also, each time I booted to TWRP, I was asked for a decrypt password. Simply cancelling it got me into TWRP. After some research, I determined that I needed to flash no-verity to disable encryption on the phone.
I followed instructions by wiping/formatting data then flashing no-verity. Rebooting to TWRP did not ask for a decrypt password anymore and I was then able to select/browse internal storage as well as external. Unfortunately, rebooting to the system caused a bootloop. Flashing Magisk and rebooting did not help either. I "restored" the backup I had made, and it appeared to work. But rather than booting to my original configuration, it rebooted as if it had been factory reset and I had to go through the whole setup process again.
Knowing I could get back to a factory reset at least, I tried a couple other versions of no-verity along with flashing magisk...all to no avail. At that point I decided that having root, along with the ability to flash some zips here and there, along with Titanium Backup was good enough. But then I found out about the reboot issue when inserting my sim and that was the final straw. So...my questions are:
1. Does the version of no-verity flashed matter? When downloading no-verity, there are about 6 versions but no change log, and no mention about if it is device specific. My understanding is that no-verity is universal. Is that correct?
2. Does TWRP need to be permanently flashed to the phone for no-verity to work? Is that why I ran into problems...because I was booting to TWRP but it was not the permanent recovery?
3. Did my backup not restore properly since the phone was not decrypted and was not able to write to the internal system? Why would it have restored to factory reset? (Thank goodness it did or I likely would not have been able to return it).
Thanks for helping clear up any misunderstandings I have about the whole process!
Related
Hi there,
I just read a lot of threads in this section, but it realy seems as nobody was as stupid as me.
Today I decided to root my Prime and it was all simple.
I used vipermod to root, unlock and install cwm.
I made Titanium Backup of all my Apps (nothing important here), and made a backup via cwm.
With cwm I flashed Virtuous Prime and all was fine.
Then I made the big mistakes:
-I restored most of the apps with Titanium Backup.
-I used a code to unlock my prime and I also wanted to test the encryption.
After the reboot that comes after the encryption, I entered the key, and the Prime booted.
As the lockscreen appears I entered my lockscreen code (which is the same as the encryption code) and it was ... wrong!
I don't know exactly how this happend, but maybe it was due to the Titanium Backup that I restored. Maybe I restored a system app which included the code?! I don't know.
So I couldn't enter my device, but I still had cwm, so I thought this wouldn't be a problem.
I thought I could do a factory reset, and all would be ready to go.
I did a factory reset, wipe cache, wipe dalvik - nothing helped.
It was a problem, because cwm didn't let me do anything, neither restore my backup (not found, because encrypted) nor flash the ROM again (the same here).
The only thing left I tried, was formating all the things, that I could format, but this sucked me even harder in this desaster. Now my Prime got bootloops and I don't know anything to do.
Any ideas or help is apreciated!
I would thank you so much, if anyone could help me get my Prime back to me!
have you tried to adb into your device from a PC? there's a thread in developement section called do's n donts of unlocking. I think it tells you in there how to get out of bootloop.
Thanks for your answer!
You mean this, right?
Seems as I'm nearly at Brick 2, even if I don't get "unrecoverable bootloader error", but my Device also hangs in this splashscreen with the "Eee Pad" in the middle.
Looks like I'm lost
Edit: Needed a bit to get familiar with adb, but I was able to push the rom again on the sdcard.
I fullwiped and installed the rom. First reboot askes me for encryption code, then the rom needs a bit to start.
Problem remaining: The code on the lockscreen is still wrong. I can't enter my device
Is there there any possibility (if even a full wipe doesn't help) to get back to my device?
Solved: I just had to wipe via the boot menu (voldown + power button, then wait the 5 secs)
Encrypted partition has gone!
I've been trying to root my wife's HTC Rhyme and in my efforts, something hosed the WiFi. All I get is "ERROR" under WiFi in the wireless network settings menu. This happened to me once or twice on my incredible and a kernel re-flash fixed it. I really want to root it so that she can have the benefit of being able to completely backup everything. I've tried ZergRush, TocoRoot, SuperTool, OneClick, SuperOneClick... none of it worked. The only thing that I've been able to do successfully is unlock/re-lock the bootloader.
Is it possible to extract the ROM and/or all critical system files from a stock rooted phone and use them to restore another phone that is malfunctioning? I was thinking that if I found someone with a rooted HTC Rhyme who would be willing, they could send me whatever files I would need to completely restore the phone, WiFi and all.
Any help with at least the WiFi issue wold be appreciated. Rooting would be nice too but I don't want to be greedy.
Thanks.
I was able to install an RUU which fixed the WiFi issue, but now the phone is stuck in a boot-loop. I've flashed it three times (doing it twice each attempt) but its the same result every time. The phone boots normally the first time, then goes into loop on the next restart. Could be the wrong RUU, could be corrupted or maybe I'm doing it wrong. I don't know.
Please... Any suggestions would be most appreciated.
I fixed it.
RuLEoF2 said:
I fixed it.
Click to expand...
Click to collapse
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks!
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
RuLEoF2 said:
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
How did you get the ruu to run i keep getting a error 140 wrong bootloader version i tried ruu 1.26.605.11 and 1.26.605.6 i attempted to flash a ics rom and the phone got stuck on the splash screen so then i used my backup i made before i flash the ics rom and wouldnt boot so i extracted the boot.img from the ruu and flashed it to get the phone back up and running the phone is still rooted but i have no wifi no bluetooth no cam i been searching everywhere for a rhyme kernel bt no luck if anyone could help that would great
Click to expand...
Click to collapse
Greetings-
I used the Cyanogenmod procedures to compile an image for my Note 3. The first time I installed it, the imaged booted up but I got a message about nfcservice not working. I do not recall the exact words, but it implied that nfcservice has an issue. I then, went into recovery and recovered an earlier image. The initial recovery try did not go well, and it was stuck. The last message was about the modem. But my next try worked. I had to use a backup I had from my stock firmware. Then I tried to install my unofficial image again. This time the phone went into download mode after I flashed my image. This keeps repeating, and I don’t know where to begin to troubleshoot this issue. Are there any logs I can look through? Aside from factory reset, I tried to clear all the other data; everything except the internal memory which holds my backups. But this did not fix anything. Do you have any advice for me? Oh, btw, this image is patched with seek-for-android patches. And I went through a lot to get it to work, since they did not support version 11. Thanks in advance.
RE
In my experience trying to troubleshoot something like this can be way more time consuming then un-rooting doing a factory reset back to stock OEM rom and then re-rooting and flashing the image again.
I'm new to rooting and it took me a while to get it working on my phone. It was going great though for over a year until today. I updated my phone with an AT&t update and after it booted me to the recovery area which I believe is called teamwin. I updated that too (like I have a couple of times) and my phone completely stopped working.
After troubleshooting for a few hours I was able to boot into safe mode, which I then did a factory reset. I've been able to install apps, but I none of them seem to work. Spotify is giving me error messages saying, (no storage area found) and when I installed zedge to look at ringtones and whatnot I couldn't install anything through there.
I'm assuming I have to redo the root process, but I was hoping there was another fix I'm not seeing. Like I said I'm very new to all of this. Any help would be awesome and also if I have to reroot is there any specific I have to do? Like getting rid of what I've done already?
KStef56 said:
I'm new to rooting and it took me a while to get it working on my phone. It was going great though for over a year until today. I updated my phone with an AT&t update and after it booted me to the recovery area which I believe is called teamwin. I updated that too (like I have a couple of times) and my phone completely stopped working.
Click to expand...
Click to collapse
You need stock recovery, as well as stock ROM (never rooted, unrooting does not work) in order to update OTA.
The phone tried to boot into stock recovery to install OTA; and since you don't have it (TWRP is a custom recovery), update fails.
General rule on Android, is that OTA updates don't play well with root. You should always research (for the specific device) before applying an OTA to a rooted device. That includes requirements to OTA, and also the expected results. On past devices, I've seen it not uncommon that an update removes the ability to unlock the bootloader and root. So its good to know what you are getting into before installing OTA.
KStef56 said:
After troubleshooting for a few hours I was able to boot into safe mode, which I then did a factory reset. I've been able to install apps, but I none of them seem to work. Spotify is giving me error messages saying, (no storage area found) and when I installed zedge to look at ringtones and whatnot I couldn't install anything through there.
I'm assuming I have to redo the root process, but I was hoping there was another fix I'm not seeing. Like I said I'm very new to all of this. Any help would be awesome and also if I have to reroot is there any specific I have to do? Like getting rid of what I've done already?
Click to expand...
Click to collapse
I suspect that your internal storage got corrupted somewhere along the way (as you were trying to OTA, recover, etc.). I'm not clear on the current status, you are still on the stock rooted LP ROM, with TWRP custom recovery?
If you still have working TWRP, I'd suggest booting into TWRP, select Wipe from the main menu, then the option to "Format Data" which will format internal storage. Strongly suggest not picking any other options (particularly in "Advanced Wipe" section) unless you know exactly what you are going. Lots of posts on here, by folks that delete things like System (OS) and wonder why there is no longer any OS!
After formatting internal storage, reboot and see if you still have the same issues accessing storage. If so, you may need to RUU back to full stock image, and root again. But we'll cross that bridge if the TWRP format storage option doesn't work.
I got TWRP on it and working, no problem. When I initially rooted it, I used SuperSU, not knowing that would lock me out of some apps that refuse to run on a rooted device. When I uninstalled SuperSU (with the "remove root" button in its settings) and then tried to install Magisk, I kept getting the error that my boot.img is patched.
I'm on EUI 5.8.016S (US Version), and I would greatly appreciate it if someone could get me the (unmodified?) boot.img that Magisk will accept. (I'd ask for one pre-patched for Magisk, but then I wouldn't have the second unmodified copy for Magisk to work with, and I might as well use SuperSU.) Alternately, a Magisk installer that works with the 16S boot.img. I've tried fastboot flashing in the boot.img from every 16S ROM package I could find, with no luck. (Using the command .\fastboot flash boot boot.img.)
Please help? I greatly enjoy the openness that rooting brings, but the fact that some apps lock you out is supremely frustrating.
same happen to me and I wasn't able to solve it. I'm on SuperSu
First a disclaimer: I ditched EUI almost immediately, so I'm going off info I've read around the 'net and my personal experience with other phones.
First step is make a full backup, copy to your PC, Google Drive, or anywhere you trust other than on the phone itself. You may want to backup individual files as well.
Second step gather all the files you need for a clean install of EUI (not using the backup) on your PC. I don't have the files, but a quick search of the forums should get you what you need.
Third step Factory Data Reset. You'll lose everything. Reboot, try setting up as new, you can sign into your Google account, but don't restore apps yet just in case. Get the basics working (WiFi, APN settings, updates to installed apps, etc) then reboot into TWRP. Install the latest non-bleeding edge beta of Magisk (17.2 as of time of writing). Reboot and see if it's working.
Fourth hopefully unnecessary step: If the above steps still fail, destructively wipe the phone. DO NOT follow this step if you're not sure, if there's a nagging voice in the back of your head saying maybe you shouldn't, etc. You could wind up with a bricked phone or a multiple hour headache to get it working again. Restore your backup and hope someone posts a clean boot.img. OK, warning out of the way. Wipe everything except internal. You might need to individually format each type to be certain, formatting them to something other than ext4 then reformatting back to ext4. Reboot through TWRP back to recovery to avoid mounting issues. It will give you the no os installed message. Once back in recovery reinstall EUI, boot and set up as outlined in third step. You'll have to reinstall TWRP if EUI overwrites it with stock recovery.
I hope this helps if no one has a clean boot.img for you. One last piece of advice to everyone: if you think you'll ever install Magisk, skip SuperSU completely. Older versions, before the original developer left completely, were better but they're outdated. For some reason SuperSU currently leaves "pieces" behind, even when uninstalled properly, that often cause problems.