Related
Good day everyone,
Thanks for taking the time to read this. I am in desperate need of your help. I recently purchased a HTC One S from an online store they told me it was new never used locked phone. Turns out phone was rooted, 4g does not work, and it could not recognize e drive, (internal sd card)
After reading the all in one i re-rooted it and install the teamwin version of recovery.
Now i never had any back ups or any factory files. as i got the phone rooted with software that did not work. My phone now has no rom and i cannot install from adb sideloader, or an other means. I am new to this and cannot seem to figure out how to get my phone back to even stock un-rooted etc. I tried multiple forums and download links but nothing.
i was able to install vipers rom at one point but despite several attempts to reinstall. recovery does not see files loaded. which i can see on my mac or pc.
the other strange thing i notice is that at the top in fastboot mode i sometimes see unlocked in pink only and other times i see both unlocked and tampered. when its unlock only none of my computers recognize connection.
I also tried boot.img for flash. The furthest my screen no goes is the htc logo, then goes black.
Please help, even to just point me in rite direction to have this resolved.
the boot.img, did you flash it via fastboot? (fastboot flash boot boot.img)
And, one question that comes to mind... they sold you a device as new, yet it wasnt.. Why didnt you return it?
Goatshocker said:
the boot.img, did you flash it via fastboot? (fastboot flash boot boot.img)
And, one question that comes to mind... they sold you a device as new, yet it wasnt.. Why didnt you return it?
Click to expand...
Click to collapse
Yes I tried several times loading the boot.img via fastboot.
As far as returning the device i trashed the mailing box but kept original packaging so no return address. I called the company which i made the purchase from "N1wireless" several times and sent several emails to them. They have yet to reply or answer any of my calls. Which is why I am so frustrated.
mnitllc said:
Yes I tried several times loading the boot.img via fastboot.
As far as returning the device i trashed the mailing box but kept original packaging so no return address. I called the company which i made the purchase from "N1wireless" several times and sent several emails to them. They have yet to reply or answer any of my calls. Which is why I am so frustrated.
Click to expand...
Click to collapse
Boot into recovery, select mount > mount usb storage. From pc move the Rom.zip to your sd card which should now be showing on your pc. After it is moved to your phone select unmount then press home button in twrp recovery. Then install the Rom. After install open up adb and type adb reboot bootloader then press enter. Now fastboot flash the boot img from inside the Rom.zip on your computer. After that reboot your phone and report back
Sent from my HTC One S using xda premium
bochocinco23 said:
Boot into recovery, select mount > mount usb storage. From pc move the Rom.zip to your sd card which should now be showing on your pc. After it is moved to your phone select unmount then press home button in twrp recovery. Then install the Rom. After install open up adb and type adb reboot bootloader then press enter. Now fastboot flash the boot img from inside the Rom.zip on your computer. After that reboot your phone and report back
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Hi, thanks for the reply, thats just the thing I cannot in recovery install any rom loaded to sd card. It fails. I tried reinstalling the recovery and it still not reading my sd card.
So my guess is i need a new twrc or how to do it from my mac, as now when i try on my pc it is failing as-well. Once I get the recovery to work I will try your other suggestions as I think it will work based on the steps you mentioned.
I am trying to figure out how to use terminal to reinstall recovery. any suggestions or links will be greatly appreciated.:good:
you install recoveries through fastboot, fastboot flash recovery recovery.img
Goatshocker said:
you install recoveries through fastboot, fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I reinstalled recovery several times now and it wont recognize the sd card. is there another recovery i can download and use? Also is there any instructions for a newby to use terminal to re-boot, everything from scratch. Meaning if the phone is completely blank except the fast boot and a recovery manager no backups or stock kernel etc. what is the format to be used in order for the computer and recovery to recognize the sd card?
I think I need a good recovery rom like cmod if there is one for the htc one s or the stock one if someone has it.
hi i had that problem
mnitllc said:
I reinstalled recovery several times now and it wont recognize the sd card. is there another recovery i can download and use? Also is there any instructions for a newby to use terminal to re-boot, everything from scratch. Meaning if the phone is completely blank except the fast boot and a recovery manager no backups or stock kernel etc. what is the format to be used in order for the computer and recovery to recognize the sd card?
I think I need a good recovery rom like cmod if there is one for the htc one s or the stock one if someone has it.
Click to expand...
Click to collapse
I had that problem the sd card would not be seen by my laptop and the phone would not boot at all if you plug in the phone to your go to start and then computer right click on your c drive go to manage and see if you can see it there if so try to format it and then reboot the phone if it works you can then install cwm as a recovery system then you can put what rom you wont on it i am use in zenRom 1.05 and to me its the best coz it like the htc rom that the phone come with if that don`t work let me know coz i have more tricks to try i hope this helps you out.
Theres only TWRP and CWM for the S afaik, and CWM sucks. TWRP is the one to use.
I had a similar problem a few days ago, luckily there's not such a bad solution.
1) Pick a custom ROM you want to install from the HTC One S developer forums (I went with Trickdroid) and download the ROM/boot image.
2) Then download and flash the stock recovery here: http://www.4shared.com/file/1UuxTh0k/stock_recovery.html
3) Boot into bootloader, clear storage and then reset to factory defaults.
4) Flash TWRP
5) Reboot into recovery, sdcard should now be mounted/visible
Then push the ROM to your sdcard with adb or mount USB storage and flash it/flash the boot image and you should be sorted.
Edit: Here's where I got the solution from btw (post #8):
http://forum.xda-developers.com/showthread.php?t=1630459
Hope that helped!
violentlighting said:
I had a similar problem a few days ago, luckily there's not such a bad solution.
1) Pick a custom ROM you want to install from the HTC One S developer forums (I went with Trickdroid) and download the ROM/boot image.
2) Then download and flash the stock recovery here: http://www.4shared.com/file/1UuxTh0k/stock_recovery.html
3) Boot into bootloader, clear storage and then reset to factory defaults.
4) Flash TWRP
5) Reboot into recovery, sdcard should now be mounted/visible
Then push the ROM to your sdcard with adb or mount USB storage and flash it/flash the boot image and you should be sorted.
Edit: Here's where I got the solution from btw (post #8):
http://forum.xda-developers.com/showthread.php?t=1630459
Hope that helped!
Click to expand...
Click to collapse
got it. will try it asap.
I could not get the stock recovery via that link you provided. If there is another link to the stock I would appreciate it. I had to flash it wit cwm twice then reflash with twrc to get it to identify the sd card. i had tried the viper rom but my 4g and wifi doesnt work. Will try trickmod hopefully that works with no more issues
violentlighting said:
I had a similar problem a few days ago, luckily there's not such a bad solution.
1) Pick a custom ROM you want to install from the HTC One S developer forums (I went with Trickdroid) and download the ROM/boot image.
2) Then download and flash the stock recovery here: http://www.4shared.com/file/1UuxTh0k/stock_recovery.html
3) Boot into bootloader, clear storage and then reset to factory defaults.
4) Flash TWRP
5) Reboot into recovery, sdcard should now be mounted/visible
Then push the ROM to your sdcard with adb or mount USB storage and flash it/flash the boot image and you should be sorted.
Edit: Here's where I got the solution from btw (post #8):
http://forum.xda-developers.com/showthread.php?t=1630459
Hope that helped!
Click to expand...
Click to collapse
Hey thanks allot for your suggestions. I made some progress. It kinda worked. However I my wifi and data connections no good. I tried the 9.1 update and then tried the tweaks.
Do you know if it is possible to get stock kernel and stock rome to undo changes on device?
I believe I have bricked my phone. I was running a rooted HTC One X AT&T with an odex Jellybean/HTC Sense 4+ ROM. I wanted to test out a Cyanogenmod. Big mistake. I tried to flash it from TWRP recovery, after backing up my previous ROM, however, it was stuck in an endless boot loop. I took advice from some people online and reflashed it/ wiped caches/dalvik cache etc... When I realized it would not work unless I fastbooted it myself using USB debugging I tried to reinstall the old ROM, of course, after wiping the Cyanogenmod. Long story short there was no backup even though I backed up the phone! I now have no ROM and everything on my system is gone! My SD card folder only has a TWRP recovery and I can't install any .zip files. TWRP isn't even allowing me to mount my SD card so putting any files are out of the question. I believe, however, that usb debugging was on the whole time (is it on if on the boot loader it says fastboot usb when I plug in a USB?). Is there anyway to fix this?? I'm really screwed if I can't and please don't direct me to another thread because I need personalized help. I'm doing this on a mac by the way so anyone who knows how to use the terminal would help a lot. I can get access to windows though if needed. Just please help.
Have you tried to flash the boot.img from the zip file in fastboot?
Do you know what a brick is? When your phone does NOTHING... Similar to a brick.
What happened to you is you didn't flash the boot.img through fastboot, which caused your first problem, the bootloop..
Second thing you did incorrect was perform a factory reset in boot loader... Which completely wipes your SD card and corrupts it, and which just so happened to contain your backup no worries, easily fixable...
Download a rom on your computer. While its downloading, enter recovery and choose mount. Navigate to my computer and right click the removable storage option. Choose format. Once its done, drag rom onto phone.. Flash rom in twrp.
Extract rom on your computer, grab the boot.img and flash with fastboot.
Fastboot flash boot boot.img
Reboot phone and profit
EDIT: sorry but I hastily skimmed through your post... Those are half-assed instructions for windows, I have no clue what to do on a mac
Sent from my One X using Tapatalk 2
What he said. Toolkits are easily found too
Alright, so, my tablet decided to one day just cease stop working. The recovery for some reason can't flash anything now, is used to be able to flash a backup, but not anymore. It used to be able to boot past the animation, but not anymore. I cannot flash a ROM from recovery because it says that the file is bad (and please, don't tell me to check to see if the md5's are correct, they are, I've triple checked.) I've flashed CWM recovery and TWRP recovery, and TWRP cannot fix permissions, but CWM recovery can, but neither can flash a single ROM. I've tried sideloading a rom but i get this error from the CMD window
Code:
* failed to write data 'protocol fault (no status)' *
. I'm at my wits end here. The bootloader is perfectly fine, it works 100% but I can't flash a single thing from recovery. I've flashed non-corrupted recoveries, and still I cannot flash a thing.
You have flashed the latest TWRP via fastboot and it still wont flash roms? Also, what bootloader are you on?
Sent from my ASUS Transformer Pad TF700T Infinity using Tapatalk HD
Rom: CleanRom 3.4.4
Phultara said:
Alright, so, my tablet decided to one day just cease stop working. The recovery for some reason can't flash anything now, it used to be able to flash a backup, but not anymore. It used to be able to boot past the animation, but not anymore. I cannot flash a ROM from recovery because it says that the file is bad (and please, don't tell me to check to see if the md5's are correct, they are, I've triple checked.) I've flashed CWM recovery and TWRP recovery, and TWRP cannot fix permissions, but CWM recovery can, but neither can flash a single ROM. I've tried sideloading a rom but i get this error from the CMD window
Code:
* failed to write data 'protocol fault (no status)' *
. I'm at my wits end here. The bootloader is perfectly fine, it works 100% but I can't flash a single thing from recovery. I've flashed non-corrupted recoveries, and still I cannot flash a thing.
Click to expand...
Click to collapse
What tablet do you have?
From where did you download which recovery for which Asus tablet.
Sounds like the recovery version doesn't match the device.
Thats OK said:
What tablet do you have?
From where did you download which recovery for which Asus tablet.
Sounds like the recovery version doesn't match the device.
Click to expand...
Click to collapse
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Phultara said:
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Click to expand...
Click to collapse
Have you ever unlocked the bootloader? (If not: do so by searching on Asus' site for the Unlock Bootloader Tool v7) It's a simple apk which you install and then check and let it unlock.
Only then, you can start flashing!
If you already have unlocked, maybe you sent it in (?) Or flashed an official Asus rom (?), you might want to unlock it again.
Let us know if any of these answers above helped
Phultara said:
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Click to expand...
Click to collapse
If you have the 4 icons that indicates JB.
Sounds like the custom recovery is not installed if your on the RCK icon and press the up volume rocker and nothing happens.
adelancker said:
Have you ever unlocked the bootloader? (If not: do so by searching on Asus' site for the Unlock Bootloader Tool v7) It's a simple apk which you install and then check and let it unlock.
Only then, you can start flashing!
If you already have unlocked, maybe you sent it in (?) Or flashed an official Asus rom (?), you might want to unlock it again.
Let us know if any of these answers above helped
Click to expand...
Click to collapse
Unlocking it would require an OS to be installed, but none is installed because I was wiping to install a different ROM. I have unlocked it. In response to the boot loader, yes, it has 4 icons. So I guess it is the JB boot loader. When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Phultara said:
When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Click to expand...
Click to collapse
Can you get adb shell access to your recovery?
Which ZIP are you actually trying to flash? What is the exact error message from the recovery? Try running md5sum (inside the adb shell) on the file you want to flash. Check the output of "mount". Check if /cache/recovery/log contains interesting info.
Phultara said:
Unlocking it would require an OS to be installed, but none is installed because I was wiping to install a different ROM. I have unlocked it. In response to the boot loader, yes, it has 4 icons. So I guess it is the JB boot loader. When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Click to expand...
Click to collapse
AH sorry!
I only read the title and replied lol
Does adb do anything?
Or is adb not working either?
adelancker said:
AH sorry!
I only read the title and replied lol
Does adb do anything?
Or is adb not working either?
Click to expand...
Click to collapse
How would I go about connecting through ADB?
Phultara said:
How would I go about connecting through ADB?
Click to expand...
Click to collapse
* Connect your tablet to a computer with proper drivers and adb installed.
* Boot tablet to recovery.
* On computer, type "adb shell".
_that said:
* Connect your tablet to a computer with proper drivers and adb installed.
* Boot tablet to recovery.
* On computer, type "adb shell".
Click to expand...
Click to collapse
Alright, I'll have to try that when I get home in about 3-4 hours. I'll get back to you on that. Also, I noticed last night that when I was on fast boot, it would stay stuck as waiting for device on the cmd window. I'm not sure if it was my computer that didn't detect it or a new symptom. O hope its just a fluke!
Alright, here's the log from my recovery.
Phultara said:
Alright, here's the log from my recovery.
Click to expand...
Click to collapse
OK, I assumed that you're not using data2sd. 1. Make sure your microsdcard is good (reformat and recopy your backup or rom if needed),2. Boot into twrp and wipe cache, dalvik cache, factory reset, wipe system, wipe internal then finally the most important part, FORMAT SDCARD. Now reflash a new rom or try to restore from backup. I would try step#2 first. Good luck.
EDIT: format sdcard instead of wipe sdcard.
buhohitr said:
OK, I assumed that you're not using data2sd. 1. Make sure your microsdcard is good (reformat and recopy your backup or rom if needed),2. Boot into twrp and wipe cache, dalvik cache, factory reset, wipe system, wipe internal then finally the most important part, FORMAT SDCARD. Now reflash a new rom or try to restore from backup. I would try step#2 first. Good luck.
EDIT: format sdcard instead of wipe sdcard.
Click to expand...
Click to collapse
That did it!!! Thank you!!!! Looks like it was the SD that was the root of the issue! Thanks!!
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
ttakacs said:
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
Click to expand...
Click to collapse
When you flashed to stock you erased your recovery.. Reconnect to your computer and push a recovery onto your phone and you're good to go..
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
ttakacs said:
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
Click to expand...
Click to collapse
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Setting.Out said:
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Click to expand...
Click to collapse
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
ttakacs said:
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
Click to expand...
Click to collapse
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Setting.Out said:
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
ttakacs said:
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
Click to expand...
Click to collapse
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Setting.Out said:
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Click to expand...
Click to collapse
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
ttakacs said:
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
Click to expand...
Click to collapse
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Sent from my Nexus S using xda premium
Setting.Out said:
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Click to expand...
Click to collapse
I am too. Every method known to me (Odin, fastboot, adb) to flash a ROM, whether custom or stock, has failed to boot. Thanks for hanging with me on this; if you can think of solution I'll be glad to have it. Or if I solve it, I'll post here.
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