I've run into a couple of problems with Lineage and TWRP. Followed the instructions for Lineage installation and it worked, except that vibration stopped working. I had also flashed Magisk. No typing feedback, no vibration for incoming calls, etc. Tried putting stock back on. Still no vibration. Tried flashing TWRP again, but now I can't boot to recovery. Is it an issue with Magisk? I tried uninstalling according to Magisk's instructions, but no luck.
So the problems are no vibrations anymore and not able to to boot to recovery. Just goes back to bootloader.
Okay, got it back to stock using fastboot commands, but vibration is still broken. Any way to fix it?
Related
Hey guys,
i'm in trouble installing a custom ROM on a S4 Active (GT-I9295, Baseband IXXUDOB4, 5.0.1).
Flashed CF--Autoroot with Odin, no problem.
Then i flashed TWRP, Odin showed its green "PASS!"-message but i can't boot into recovery.
I'm well aware of the timing issue when doing the first reboot into a custom recovery, and i assure you this isn't the problem.
I tried countless times, after a while i installed ROM manager to try if i could flash the ROM file that way.
It installed another custom recovery -CWM- on top, and also showed up the TWRP recovery:
http://imgur.com/kSSiuld
Still, booting into any recovery does not work, neither from ROM managers menu or via any button-press combination.
When pressing vol up+home+power, the phone shows the blue "revovery loading"-line AND the red line *****ing about the root, but continues to boot as if it had been switched on normally.
I even looked for the ominous "install-sh" script in system/etc to understand why nothing gets me into recovery-
what the heck can this be?!
Did the same thing to S6 and S5 without any hassle, i'm stuck with this for several days now and i am running out of ideas.
Anyone...?
Not a very technical answer, but have you tried pulling the battery out for 30 seconds and trying again?
Yes we did, unfortunately, this also didn`t help.
Tried loads of things actually, still impossible to access that damn recovery
Installing TWRP was one of the first things I did when I got this Lenovo phone.
It worked like a charm, I pressed the Volume Keys and the Power button simultaneously and voila! TWRP opened. I was planning to install a custom ROM, so I decided to backup my device, just in case something goes completely wrong. I backed it up, then tried to move the backup from the /data partition. That went kinda wrong and for some weird reason TWRP didn't do anything but show this loading bar on the bottom of my screen.
Since TWRP was being unresponsive, I decided to remove the battery from my phone.
When I tried to access TWRP again, to my surprise, it was gone. The stock recovery appeared instead. I tried reflashing TWRP using both SFP and ADB/Fastboot, and even though the transfer was successful, the Lenovo recovery was still there. I booted to Android and saw that the "OEM Unlocking" option was disabled, even though I had enabled it. I re-enabled it, tried all the things I mentioned before and I got the same result. I opened up Android and.. OEM Unlocking got disabled.. Again.
I enabled it, yet again, tried going to fastboot, where I tried unlocking the bootloader. FAILED! I also tried side loading SuperSU.zip. FAILED!
As a last resort, I used Kingoroot to root my device, and to my surprise it worked.
I still can't seem to be able to flash CWM/TWRP, though, and I would like to install Xposed. SuperSU is also a necessity for me.
TL;DR I can't flash a custom recovery even though I could, Kingoroot worked for me, I need to get SupeSU, Xposed and a custom recovery. Side loading/Flashing using ADB isn't working, OEM unlocking gets disabled every time I reboot my device.
Now that you are rooted, i would suggest you to try 'flashify' and check if you can get your twrp working again. I still doubt it would, since you said you werent able to get it installed through fastboot before, but first give it a try.
When you confirm it working just flash the supersu zip using whichever method you like.
When I tried reinstalling Stable OxygenOS 4.1.6, the phone locks up upon install and setup screen. This goes for previous OS versions, as well. It takes force quits, restarts, and numerous install attempts and the phone still locks up. I tried stock recovery, old and new TWRP versions, all of which are clean installs, Nothing. LineageOS and other Hydrogen based roms still lock up, either at the setup screen, or when I try and activate developer options. Every Rom I tried after activating developer options, it doesn't leave the gear icon in the menu, either. It takes a restart (force quit) for it to show up. Also, WiFi doesn't work. Sometimes when I try and install OxygenOS either by sideloading, or through TWRP, the phone locks up at the wifi setup screen. This goes for every version of OxygenOS I tried. Your advice is appreciated. Thanks.
I had some problems last night while switching back and forth between Beta and stable. I could try to help but I'm not a guru at this, so wait for confirmation if you are not sure.
First I think you need the right TWRP version. 3.1.1-2 is the latest one, but I'm using 3.0.4-1 (flashed stableOOS with it) and everything is back to normal for me.
Try a clean flash of stableOOS. TWRP > Advanced wipe, select dalvik,cache,data,system and swipe.
Then install the OS. Don't reboot yet, and instead boot into recovery after going back. I read that this ensures you keep TWRP.
It may say No OS installed, but go ahead. Then boot into system again. This worked for me and I restored my backups
I just went from beta 10 to 4.1.6 and have no issues at all.
I followed the basic procedure, in TWRP (recommend to use the latest bluesparks one from his kernel thread - just TWRP no need for his kernel), I did a factory reset, (in TWRP just swipe to Factory reset from the WIPE screen where it says 'Most of the time this is all you need'), its correct nothing else needed, then flashed the full v416 file, then flashed Magisk 13.2, rebooted to system, that was all. TWRP was not lost with this method.
System booted to stable v4.1.6 and no issues.
Check what format are your partitions fornatted in. Make sure they are f2fs. Otherwise try the debrick tutorial. It helped me fix a lot of bugs on my 3T.
I tried all of the above, and I'm certain under the right circumstances, your advice would work. In the end, I used the unbrick tool which brought it back to it's original locked state, and I'm still running into issues. I wonder if there's a hardware issue somewhere that was the result of using Beta. The OS boots up and I'm finally able to access developer options, but no WiFi and the phone still refuses to restart or power off unless I do a hard shutdown. I've never seen anything like it. Numerous ROMS, recoveries, and sideload installs using the One Plus Recovery, and it still doesn't work.
Thanks for everyone's input, but I feel like this phone is done.
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
flobbadob said:
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
Click to expand...
Click to collapse
Which twrp version are you using?
Did you actually flash any custom rom or do you try to start miui?
Did you change any partition?
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
lanceindie said:
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
Click to expand...
Click to collapse
+1! Thanks :highfive:
Did you solve it? I might have some ideas.
Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?
Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?
Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.