Is it possible to install oem stock rom, root and install twrp? I've been trying but the knox text remains on boot twrp doesn't stick and if it does the phone doesn't boot just loops. I've done the magic thunder to bypass the prenormal only then did twrp stick, before that it wouldn't and just require to factory restore after start. I've tried several custom roms but all had some issues, random restarts, requiring to hold down - home and power and cancel to get into the os. other has wrecked audio etc.
Dammit can't edit title.
Related
Nexus 4 on 4.4.2 stock rooted with Xposed and Matr1x kernel.
I can get to TWRP but after wiping dalvik/cache and reflashing diff kernels (problems started after flashing a new version of a custom kernel), it either gets stuck at "Starting Apps" (after it goes through the Android is upgrading applications thing) or get stuck at the kitkat booting animation.
One time I did manage to get it booted and the Titanium Backup data was still there. I'd like to avoid doing a factory reset and lose the TiBu data and have to set up everything again and lose all my data/pics.
How can I do this?
Or alternately, how can I load a stock kernel onto the device in this condition?
[edit: this is getting worse, I had the phone plugged into my PC (to keep it charged while it's stuck in bootloop or trying to get it to work) and when I pressed the vol buttons + power button to reboot to recovery, the red light came on a couple of times, and now the screen says "Download Mode, DO NOT UNPLUG the device until the process is complete"....... Sigh.
If you can still get into twrp you can use adb pull to pull the titanium backup files off your phone. not sure where titanium backup directory is but you can pull your entire sdcard with 'adb pull /sdcard/'
After that try factory reset, if you still have problems either try flash an older version of the kernel or just flash a stock image. You should still be able to get into fastboot and flash whatever.
mgs333 said:
Nexus 4 on 4.4.2 stock rooted with Xposed and Matr1x kernel.
I can get to TWRP but after wiping dalvik/cache and reflashing diff kernels (problems started after flashing a new version of a custom kernel), it either gets stuck at "Starting Apps" (after it goes through the Android is upgrading applications thing) or get stuck at the kitkat booting animation.
One time I did manage to get it booted and the Titanium Backup data was still there. I'd like to avoid doing a factory reset and lose the TiBu data and have to set up everything again and lose all my data/pics.
How can I do this?
Or alternately, how can I load a stock kernel onto the device in this condition?
[edit: this is getting worse, I had the phone plugged into my PC (to keep it charged while it's stuck in bootloop or trying to get it to work) and when I pressed the vol buttons + power button to reboot to recovery, the red light came on a couple of times, and now the screen says "Download Mode, DO NOT UNPLUG the device until the process is complete"....... Sigh.
Click to expand...
Click to collapse
Just use fastboot and flash the boot.img file. It'll replace the bad kernel with the stock one
fastboot flash boot boot.img
You can extract the boot.img from the factory image
Sent from my Nexus 5
Hello
I had my phone on the VNS-L31C113B132 firmware, unlocked, rooted.
Then I got a message about a new update (VNS-L31C113B141), so naturally, I downloaded the update.app and tried to flash it through twrp with no success, so I used the up+down+power method, it worked, and all was well, except i lost root, lost twrp, and the bootloader seemed to be locked again. No data or apps were deleted though. Then I updated to B150 same method.
any idea why root and recovery are gone? and how can I check if my bootloader indeed is relocked?
That is a completely regular behavior. You can check by booting to bootloader (holding up and power button when the phone is turned off), it will show you a white screen with the Android robot and info on bootloader and FRP status. To get everything back, just unlock the BL again, flash TWRP again and root again, no harm will be done, and your root software (e.g. Xposed) will start working again (although for xposed, you'll have only the client, the framework has to be flashed via TWRP once again).
Klorec said:
That is a completely regular behavior. You can check by booting to bootloader (holding up and power button when the phone is turned off), it will show you a white screen with the Android robot and info on bootloader and FRP status. To get everything back, just unlock the BL again, flash TWRP again and root again, no harm will be done, and your root software (e.g. Xposed) will start working again (although for xposed, you'll have only the client, the framework has to be flashed via TWRP once again).
Click to expand...
Click to collapse
unlocking again may result in factory reset.... or is there another method that keeps everything?
Moemen Shahawy said:
unlocking again may result in factory reset.... or is there another method that keeps everything?
Click to expand...
Click to collapse
Unfrtunately yes, the phone will be reset. All you can do is to back it up and then restore it. Next time you update firmware, update it with "update.zip" from TWRP, this way, only recovery and root will be removed, but not the BL unlock.
look around, it is a workaround for skip factory reset in unlock/relock procedure.
Hi, everyone.
I have a galaxy s8 SM-G950FD. I have once flashed TWRP and rooted the device successfully.
Then I tried to install a custom ROM but I got bootloop.
After that, I flash official ROM to unbrick my device. But since then, whenever I tried to flash TWRP again I got this message "Verification failed unable to restart your device the integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
My device is still working fine but I want to try to flash a new ROM (even if I may brick my device forever). I don't know what to do. Can you guys give me some advice ?
Thank you!
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
But I cannot boot into TWRP. How can I do that ?
If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.
MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
MikeTheTechSavvy said:
If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.
Click to expand...
Click to collapse
I cant flash/get into TWRP. I tried to boot into stock recovery and do a system wipe/factory reset. Then I flash TWRP again but nothing seem to happen. I tried to boot into recovery and it get me to the stock recovery not TWRP.I did unlock OEM, used Odinv3.12, twrp-3.1.1-2-dreamlte.img.tar.
I had the same issue.
After Odin has flashed the Recovery it performs an auto reboot (if checked in Odin). So at this reboot hold Vol up + Home + Power as soon the screen goes of. You need to be quick. Then it should boot into TWRP.
True, Samsung's stock recovery is very persistent lately and if you tick the auto-reboot you have to be very fast in switching to Recovery mode combo.
Otherwise you can choose not to tick auto-reboot, force restart the device after the TWRP flashing was successful and immediately switch to the Recovery combo.
Here you go: two ways of doing this.
Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.
Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.
Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com
It seems every ROM I’ve tried installing never boot after “successfully” through TWRP. (Like even 10 mins of waiting)
My idea is that unlocking the bootloader (where it gives you warnings every time the thing boots) has something to do with it, seeing as the flashing guides don‘t mention this in depth.
Factory reset through TWRP after flash, that wipe after flashing that has the button on the finished page
Now it can’t boot into TWRP, or download mode, just stuck between the power screen and black (seemingly turned off)
Did you flash Magisk-v23.0.apk through TWRP?
burningcreation said:
Did you flash Magisk-v23.0.apk through TWRP?
Click to expand...
Click to collapse
No, I was following this and this which don’t list Magisk as a step
Would that have been important to do?
Also any ideas on how to get it to download mode? So far it just gets stuck on the Galaxy A20 screen with a warning about it being unlocked, no button combo gets past that, even though it does reboot