I have been playing around with viper4android and now my phone does not seem to boot.
It is stuck on the alcatel logo screen.
I do have TWRP backups, but I am unable to get into fastboot mode.
- Power + Volume UP brings the "stock" recovery, can I adb sideload twrp backup? Do I have to adb sideload stock rom?
- Power + Volume DOWN supposed to get me into the fastboot mode, but that always fails. How do I get into fastboot mode w/o adb (adb reboot-bootloader)
Power plus down puts the phone in "download mode" in preparation for running the Mobile Q windows software which can reset the phone to factory. It does not put you into fastboot. If you don't have twrp installed (rather dangerous to not have it when you are installing things that state they may hang the device) then your only hope is to use adb (if you had usb debugging enabled) to reboot to bootloader so you can flash twrp or use the mobile Q software to reset your phone to factory.
Got it!
So after installing the Mobile Upgrade Q, and 30 minutes the phone is back to life.
twrp restored the backups w/o any issues.
However, now it seems that I am unable to flash supersu.zip, twrp installs it w/o any issues, but once the phone boots, there is no root, and /system/xbin/su does not exist, and Xposed installer fails, since /system is read-only, which seems weird to me.
I do not think I am missing anything
famewolf said:
Power plus down puts the phone in "download mode" in preparation for running the Mobile Q windows software which can reset the phone to factory. It does not put you into fastboot. If you don't have twrp installed (rather dangerous to not have it when you are installing things that state they may hang the device) then your only hope is to use adb (if you had usb debugging enabled) to reboot to bootloader so you can flash twrp or use the mobile Q software to reset your phone to factory.
Click to expand...
Click to collapse
It appears that TWRP is having issues with /system partition now and it's in the read-only mode.
Here is the twrp log, with all the read-only issues:
http://pastebin.com/1mU1ykHs
JupoozunEd3 said:
It appears that TWRP is having issues with /system partition now and it's in the read-only mode.
Here is the twrp log, with all the read-only issues:
http://pastebin.com/1mU1ykHs
Click to expand...
Click to collapse
Go in advanced twrp settings and allow r/w of system.
famewolf said:
Go in advanced twrp settings and allow r/w of system.
Click to expand...
Click to collapse
That did not help either, nor "doing a mount -o rw,remount /system" from the TWRPs terminal. I think the issue was caused by restoring ALL partitions via TWRP (system, system image, efs, data, boot)
After a session with Mobile Upgrade Q, and just restoring /data, all is back to normal.
Related
Hi, today I wanted to restore a twrp backup (in order to unroot and get the OTAs updates) posted there : http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745, the Model: 6045Y(Europe) Firmware: 5.0.2-010 05 (my idol 3 is the 6045Y).
I wiped everything but OTG and external sd.
I first restored the system image and then the boot because there are 2 files with this backup.
My idol 3 now just boots fine, but every 4-5 minutes, depending on how hard I am using it, it reboots to system.
When I try to boot in fastboot mode with adb reboot fastboot, it doesn't work and shows a black screen. When I press vol up + power, it goes into a kind of "recovery" (don't know if it's the right name of this mode, but there are a lot of options like wipe data, cache, install update with adb and it seems to be stock) (I precise I tried to factory reset/wipe data multiple times and it didn't solve my problem).
When I try to go into recovery, it does the same thing except it never reboots (I can only factory reset/wipe via the "recovery I told you about up there).
On my SD I have 3 working twrp backups which I could restore if i could access the option to.
What I would need to do to solve my problem is, I guess, figure out how to access my recovery (which should still be installed) or how to boot on it with adb on my computer, and then restore one of the twrp backups on my SD which are working.
If you know how to do that or just how to solve this reboot problem, please answer the thread. Thanks in advance.
T0mSIlver said:
Hi, today I wanted to restore a twrp backup (in order to unroot and get the OTAs updates) posted there : http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745, the Model: 6045Y(Europe) Firmware: 5.0.2-010 05 (my idol 3 is the 6045Y).
I wiped everything but OTG and external sd.
I first restored the system image and then the boot because there are 2 files with this backup.
My idol 3 now just boots fine, but every 4-5 minutes, depending on how hard I am using it, it reboots to system.
When I try to boot in fastboot mode with adb reboot fastboot, it doesn't work and shows a black screen. When I press vol up + power, it goes into a kind of "recovery" (don't know if it's the right name of this mode, but there are a lot of options like wipe data, cache, install update with adb and it seems to be stock) (I precise I tried to factory reset/wipe data multiple times and it didn't solve my problem).
When I try to go into recovery, it does the same thing except it never reboots (I can only factory reset/wipe via the "recovery I told you about up there).
On my SD I have 3 working twrp backups which I could restore if i could access the option to.
What I would need to do to solve my problem is, I guess, figure out how to access my recovery (which should still be installed) or how to boot on it with adb on my computer, and then restore one of the twrp backups on my SD which are working.
If you know how to do that or just how to solve this reboot problem, please answer the thread. Thanks in advance.
Click to expand...
Click to collapse
The correct adb commands are
Code:
adb reboot bootloader
or
Code:
adb reboot-bootloader
and from there you should be able to boot the TWRP image with
Code:
fastboot -i 0x1bbb boot <recovery image filename>
Hey guys,
Recently moving back to Android with a Samsung Galaxy S7 (SM-G930F) and I have some problems to get everything working. I didn't find (or didn't managed to find) the informations I was looking for on the forum or anywhere else on internet.
Here is what I did since now:
1. Rooted my phone with CF-Auto-Root.
2. Phone rooted correctly, SuperSU installed => no problem
3. Installed TWRP Manager.
4. Launched installation of TWRP from the TWRP Manager and selected the latest version of herolte (3.0.2-2).
5. Installation failed, relaunched it, didn't get any notice of success or failed this time so I presumed it was good.
6. Restarted the phone in normal mode => No problem.
7. Restarted the phone in recovery mode => Access to TWRP asking me if I want to stay in read only or allow read/write.
> Can I boot up at this stage in read/write without causing any issues since I saw in the TWRP root installation process (http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770)
"By swiping right, you will trigger dm-verity, and if you don't follow step 11 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications."
> Since I am already rooted, it shouldn't cause any issues right?
8. I tried to do a backup of my phone but the data folder is showing no data and when performing a backup I am getting a "failed to mount /data error"
> Don't really know how to fix this error.
> I can backup without any issue Boot and System.
Thank you per advance for your answers
1. You need to flash dm-verity and force encryption disabler before you swipe right and activate read/write. Otherwise it won't boot.
2. If you want to do a backup with TWRP you need to format data once, so the encryption is disabled. Just perform a backup via Titanium and format data in TWRP. Afterwards you can make backups in TWRP.
Thank You.
I just did the steps described but it seems that I lost my root after having wipe the data partition.
Now when I am rebooting the phone I am getting "kernel is not seandroid enforcing" in red on top of the screen but the phone still boot up fully.
Tried to reboot in recovery but it seems that TWRP is not present anymore.
I re-rooted the phone using CF-Auto-Root.
Now the phone is rooted, I installed once again TWRP Manager and tried to reboot in recovery mode but getting "dm-verity verification failed…"
I don't have the "kernel is not seandroid enforcing" error anymore.
Do I need to reinstall TWRP in order to solve the issue?
Julek_Fr said:
I re-rooted the phone using CF-Auto-Root.
Now the phone is rooted, I installed once again TWRP Manager and tried to reboot in recovery mode but getting "dm-verity verification failed…"
I don't have the "kernel is not seandroid enforcing" error anymore.
Do I need to reinstall TWRP in order to solve the issue?
Click to expand...
Click to collapse
Hi
did you do this?
Point 11
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Kernel thing is normal ........
MAX 404 said:
Hi
did you do this?
Point 11
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Kernel thing is normal ........
Click to expand...
Click to collapse
Thank you for your reply.
Since the phone was already rooted I didn't done the SuperSU but wipped the data partition and flashed with the "dm-verity and force encryption disabler".
After reboot I was not rooted anymore, so I re-rooted the phone and reinstalled the aps.
Now if I try to reboot in recovery mode, I get the error "dm-verity verification failed…"
If I try to factory default the phone I am getting the same error.
Do you think I can just flash back in stock firmware using odin and the good version downloaded from sammobile? It will remove TWRP and the root right ?
Julek_Fr said:
Thank you for your reply.
Since the phone was already rooted I didn't done the SuperSU but wipped the data partition and flashed with the "dm-verity and force encryption disabler".
After reboot I was not rooted anymore, so I re-rooted the phone and reinstalled the aps.
Now if I try to reboot in recovery mode, I get the error "dm-verity verification failed…"
If I try to factory default the phone I am getting the same error.
Do you think I can just flash back in stock firmware using odin and the good version downloaded from sammobile? It will remove TWRP and the root right ?
Click to expand...
Click to collapse
Hi
Flash a stock firmware is an option but not necessary at this point
Go back to TWRP page
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
and re do all this steps one by one ( 1 to 13 ), make sure OEM unlock is enables , back up important thing before you do anything just in case
FULL STEPS FOR OBTAINING ROOT
You can follow this video by Max Lee if you'd like: How to Root Galaxy S7 & S7 Edge! [Exynos ONLY]
Otherwise, follow these instructions:
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for herolte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 11 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 5-15 minutes for your device to finish setting itself up.
try this first....
GerasVille said:
1. You need to flash dm-verity and force encryption disablerbefore you swipe right and activate read/write. Otherwise it won't boot.
2. If you want to do a backup with TWRP you need to format data once, so the encryption is disabled. Just perform a backup via Titanium and format data in TWRP. Afterwards you can make backups in TWRP.
Click to expand...
Click to collapse
How to flash this file? Please treat me like an idiot. What exactly do I have to do?
I am trying to flash the ROM of a different model of my phone, and thus need TWRP, but this needs to be unlocked first somehow.
Hello all,
The phone was previously rooted, I just wanted to retry to get rid of the optimizing app problem. With that said, the phone is rooted, and I previously had USB debugging enabled. I reset to factory using the Android Recovery, so does this mean USB debugging was not enabled after resetting?
These were my steps:
Install and run KingRoot
Purchase Super-Sume Pro ($4) to replace KingRoot with SuperSu
On reboot it got stuck in boot loop. I have tried Android System Recovery (lmy47v) but my options are only
Code:
>reboot system now
>wipe data/factory reset
>wipe cache partition
>reboot to bootloader
>power down
>view recovery logs
I have tried all of these options several times.
I have installed ADB on windows as well as the Kyocera drivers here: kyoceramobile.com/support/drivers
I have not been successful in getting access to the phone with ADB.
I have tried to get the phone into fastboot mode by combinations of key presses, but I have not been successful. Does this phone have fastboot? Here are the recovery logs: imgur.com/a/Sn9zD
What is left? I really like this phone and use it as a waterproof GPS and would have to have made a paperweight out of it. Please help!
Hey all, looking for some general Android wisdom on how to get my phone to a state where the computer can detect it as a USB device so that I can use ADB or some other method. What are my options?
advhound said:
Hello all,
The phone was previously rooted, I just wanted to retry to get rid of the optimizing app problem. With that said, the phone is rooted, and I previously had USB debugging enabled. I reset to factory using the Android Recovery, so does this mean USB debugging was not enabled after resetting?
These were my steps:
Install and run KingRoot
Purchase Super-Sume Pro ($4) to replace KingRoot with SuperSu
On reboot it got stuck in boot loop. I have tried Android System Recovery (lmy47v) but my options are only
Code:
>reboot system now
>wipe data/factory reset
>wipe cache partition
>reboot to bootloader
>power down
>view recovery logs
I have tried all of these options several times.
I have installed ADB on windows as well as the Kyocera drivers here: kyoceramobile.com/support/drivers
I have not been successful in getting access to the phone with ADB.
I have tried to get the phone into fastboot mode by combinations of key presses, but I have not been successful. Does this phone have fastboot? Here are the recovery logs: imgur.com/a/Sn9zD
What is left? I really like this phone and use it as a waterproof GPS and would have to have made a paperweight out of it. Please help!
Click to expand...
Click to collapse
Hi..my XD bootloop too..BTW how to get in Android System Recovery?
Did you ever fix your phone?
I saw that the post just stops with you needing help
tl;dr
TWRP doesn't encrypt/mount storage,
Magisk kills WiFi.
Before I bricked the phone with a Magisk module, everything was working.
Had to revive my phone with MSM, stuck in qualcomm crashdump.
Now stock firmware is working, but I cannot get phone rooted with working WiFi / working TWRP.
==================================================
This is how I did it before (clean install, unlocked OEM)
1. boot into fastboot/bootloader
2. fastboot > fastboot flash boot twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
3. boot into recovery mode
4. install OnePlus7ProOxygen_21.E.21_OTA_021_all_1910071445_89e89c225a754eb6.zip
5. install twrp-installer-3.3.1-4-guacamole.zip
6. reboot into recovery
7. Install Magisk-v20.0.zip
8. reboot system
DONE and it worked.
NOW:
1-6 stay the same.
But when I get back into recovery, TWRP doesn't read/mount the storage.
adb push magisk to sdcard/ and try to install leads to following:
Updating partition details...
...done
Unable to mount storage
Failed to mount "/data" (Invalid argument)
Full SELinux is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
- blablabla
- installing
- Done
Updating partition details...
...done
Unable to mount storage
Click to expand...
Click to collapse
...guess what, Magisk is not installed/working
- Repair/change file system doesn't work.
(phone will boot into system instead of recovery, back to recovery still Internal Storage at 0 MB)
- formatting data + Wiping Dalvic / ART Cache, System, Cache doesn't work
(will all lead to stuck in Fastboot -> recovery due to fastboot image)
(installing boot.img (on A & B) and TWRP.zip doesn't help)
- install OOS and then just flash TWRP without flashing stock firmware doesn't change
Alternative
1-6 stay the same.
7. boot into fastboot
8. boot TWRP *-70 again
9. encrypting now works, mounted
10. isntall MAGISK (20.0 or 20.1)
11. reboot system
At this point it seems like everything is working, but with MAGISK now installed, WIFI won't work. Can't activate WiFi it at all.
So, i have no idea what I changed.
Rooting worked before the brick. Now it stopped working.
My friend has that problem after rooting his phone with magisk..
Just flaah the rom and wifi will be back..
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7 Pro in fastboot mode (Power and volume + and volume-);
Connect the OnePlus 7 Pro to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
https://forum.xda-developers.com/on...ock-fastboot-roms-oneplus-7-pro-t3931424/amp/
Click to expand...
Click to collapse
Thank you, Sir
I should have mentioned that I already flashed a dozen times to stock firmware. Used the package from your link as well when I was stuck in fastboot.
My mistake, I should have been more accurate with my problem.
Getting it back to stock firmware isn't the problem.
Getting it back as a rooted device with working WiFi and working TWRP is the problem.
Stock OOS - without TWRP, without Magisk » ROM working
Stock OOS + TWRP (3.3.1-4) » TWRP not working; ROM working (but this combo worked before)
Stocks OOS + TWRP (3.3.1-70) » TWRP working, ROM working[/b] (but TWRP *-70 should be replaced by *-4 afaik[/U]; correct me if I am wrong)
Stock OOS + Magisk + TWRP *-70/TWRP*-4 » Magisk working, ROM no WiFi. (fixable through reflashing stock firmware and deleting everything)
So maybe any ideas why Magisk/TWRP stopped working now? And how I can get my OP7P rooted and the stable TWRP working?
Solved
Reinstalling boot.img + TWRP 3.3.1-70 installer.zip + Magisk v20.1.zip did it this time
saexcore said:
Solved
Reinstalling boot.img + TWRP 3.3.1-70 installer.zip + Magisk v20.1.zip did it this time
Click to expand...
Click to collapse
Hey, can you go into more details? I'm having the same trouble of not being able to install magisk (stock rom with twrp installed).
Where can I get this boot.img? And what's the exact process to installing it? Thanks.
For me, I never booted into bootloader. I ran fastboot boot /path/to/TWRP.img, while still booted up and that took me to recovery and I used TWRP installer and flashed magisk from there.
I tried almost all the other methods, and kept soft bricking. I didn't patch anything, booting from fastboot soft bricked me.
I just started experiencing connection issues after installing a Magisk modules, but I read a custom kernel solves that.
meleeb4kr said:
Hey, can you go into more details? I'm having the same trouble of not being able to install magisk (stock rom with twrp installed).
Where can I get this boot.img? And what's the exact process to installing it? Thanks.
Click to expand...
Click to collapse
Sure.
The boot image I got from:
https://androidfilehost.com/?w=files&flid=294300
(download the fastboot firmware for your device, for me it was "10.0.1-GM21BA".
open the archive, open the next folder, extract the "boot.img" file to your PC)
Magisk I got from:
https://github.com/topjohnwu/Magisk/releases
(I used 20.1, 19.4/20.0 seems to work more stable for more people)
TWRP I got from:
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
(Download image for Q and twrp-installer.zip)
===================================
1. Boot into fastboot
(developer options > advanced restart > restart bootloader or power device off > HOLD volume down and press power till in fastboot)
2. In fastboot: "fastboot boot twrp70.img"
(#protip: drag & drop file into CMD)
2.1. wait till phone encrypted everything and TWRP started
3. Copy twrp70.zip, boot.img & Magisk-v20.1.zip to your phone
(I put it in the TWRP folder)
no reboots in-between!
3. In twrp homescreen: install > install image > boot.img > choose "boot" > install
4. In twrp homescreen: install > install zip > twrp70.zip > install
4.1 wipe dalvik
5. In twrp homescreen: install > install zip > magisk-v20.1.zip > install
5.1 wipe dalvik
6. In twrp homescreen: reboot > system
Done.
Hope it works for you too.
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password
#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though
Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!
#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?
you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.
I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine