Related
Unlocked bootloader and tried to with SuperSU but no boot. Having a hard time to go back to stock but need to find stock recovery for newest FW C567B190. I could not boot into TWRP only flash it so I couldn't make a backup. I just was able to get into the wifi restore screen and it downloads the 2.4gb image and installs but then said I have serious errors and recommended a factory restore, did it but same error. I did make a backup of all the other partitions so I hope to be able to get something going. New here and all this was certainly easier on my 6P and OP3. Thanks for the help.
rzracer2 said:
Unlocked bootloader and tried to with SuperSU but no boot. Having a hard time to go back to stock but need to find stock recovery for newest FW C567B190. I could not boot into TWRP only flash it so I couldn't make a backup. I just was able to get into the wifi restore screen and it downloads the 2.4gb image and installs but then said I have serious errors and recommended a factory restore, did it but same error. I did make a backup of all the other partitions so I hope to be able to get something going. New here and all this was certainly easier on my 6P and OP3. Thanks for the help.
Click to expand...
Click to collapse
Which SuperSU did you try? The only official working one is SuperSU 2.82 SR1, the others fail to install.
And unless you decrypted (Wipe - 'Format Data' button in TWRP) SuperSU will remove the encryption flag in fstab in ramdisk... That means you'll boot but stay encrypted, which leads to a bootloop.
You could try flashing this stock boot image for C567B190 in TWRP (Install - Install Image - select 'boot' partition): https://mega.nz/#!cw01zCCS!AX3wKw0V7pbIYC79Ny6OJ5CTuyxq-xA1ibltLMIRRZQ
Then flash this SuperSU (It's to stay encrypted): https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
If that fails, here's stock recovery for C567B190: https://mega.nz/#!hgsEhBiC!Jf2Utp768UIS0N1-3jhPeoN0qaW_TlFsFf5uN9vKLEs
Recovery needs to be flashed with fastboot in download mode.
Thanks for the information Stockholm! After the second wifi recovery download it booted fine but did relock the bootloader. I did use 2.82 Sr1 but didn't format data which as you stated caused a bootloop. Might give it another try but I might just return it. Not happy with the stock firmware so I need to spend some time and see if there is a ROM available proper smartlock, raise to wake would be nice as it even works on my S8 with Glipse Notifications but not on the Mate. Thanks again!
ante0 said:
Which SuperSU did you try? The only official working one is SuperSU 2.82 SR1, the others fail to install.
And unless you decrypted (Wipe - 'Format Data' button in TWRP) SuperSU will remove the encryption flag in fstab in ramdisk... That means you'll boot but stay encrypted, which leads to a bootloop.
You could try flashing this stock boot image for C567B190 in TWRP (Install - Install Image - select 'boot' partition): https://mega.nz/#!cw01zCCS!AX3wKw0V7pbIYC79Ny6OJ5CTuyxq-xA1ibltLMIRRZQ
Then flash this SuperSU (It's to stay encrypted): https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
If that fails, here's stock recovery for C567B190: https://mega.nz/#!hgsEhBiC!Jf2Utp768UIS0N1-3jhPeoN0qaW_TlFsFf5uN9vKLEs
Recovery needs to be flashed with fastboot in download mode.
Click to expand...
Click to collapse
Hello, I would like some help since I got this device just yesterday.
I got it with the EMUI 4 Android 6.0 stock installed on it. Since there was no update for it I unlocked the bootloader installed twrp rooted and manually flashed EMUI 5 7.0. Everything worked fine.
I created a backup through TWRP and restored it succefully multiple times.
Then I installed the Meticulus TWRP (since I was told it is a prerequisite for the AOSP). I Flashed the AOSP but it stuck during the boot animation (30 minutes afterwards I powered it off).
I reflashed my old TWRP and tried restoring my backup. IT fails with the explanation "Cannot wipe /vendor" while at the top it says "Cannot mount /vendor (invalid argument)" "Cannot mount /product (invalud argument)".
Anyone has a clue how to fix this? Fastboot adb all works so there should be a way to boot into an OS properly?
Since AOSP was not booting i guess you forgot formatting /data partition to ext4... And did u Used Stock vendor and not openkirin ones ?
Gesendet von meinem Honor 6X mit Tapatalk
As said I have replaced the custom TWRP with the default one so I think this should not apply anymore?
The "cannot mount vendor/product" messages came from the default TWRP after I reflashed it again.
At the top it says "cannot mount /vendor" either so I guess that is the actual problem?
It would be nice to get teh AOSP up but I really want to be able to boot into something first honestly.
And did u Used Stock vendor and not openkirin ones
Click to expand...
Click to collapse
Can you please explain? When I flashed your ROM i was on your TWRP. Does this even matter anymore?
At best I would be able to restore my backup.
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
algg said:
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
Click to expand...
Click to collapse
Yes you can but not creating it through twrp, but flashing it by fastboot mode: this is because
image (.img) files needs to be flashed by fastboot mode to avoid any kind of problem.
So, you should look for the last version of stock firmware on which you was before going custom, like BLN-L21CXXXB368 for example; tell me your build number and I'll find the package for you. Then, extract from the UPDATE.APP (a very big file that contains every partition in your phone like recovery, vendor, data, ecc. - you'll find this file inside the zip archive that contains the downloaded update) the vendor.img using Huawei Update Extractor, and then flash it through fastboot mode using the command "fastboot flash vendor vendor.img".
Otherwise, you could rely on dload method to reflash a full update package, and this should really fix everything since that it'll be like a new and clean installation of the OS. Then, unlocking the bootloader again and reflash TWRP to finally restore your previous backup made when it was working would be the final step.
Feel free to ask for further help
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
algg said:
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
Click to expand...
Click to collapse
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload because package verification always failed at 5%, i tried every combination but without success.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
RedSkull23 said:
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload, i never be able to using it successfully because package verification always failed at 5%.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
Click to expand...
Click to collapse
For fastboot yes flashing recovery or boot do work but vendor does not. Maybe the ISO is corrupted somehow I will try it again on a different machine now with the tool.
The link you posted the dload method from is the one where I initially found it as well so yea.
Also it shouldn't matter what I install since the only thing I need is the actual vendor (and product?) partition to work. I have a functional backup just TWRP cannot create/mount the partitions. So even a way to just create them without any data would actually fix my problem (at least I hope so?)
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
algg said:
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
Click to expand...
Click to collapse
@RedSkull23, thanks for the tag mate.
@algg, No need to flash the vendor image as you already had the stock vendor img.
Now what else you can try is to flash the stock recovery, boot to stock recovery, select factory reset and reboot. It should most probably fix the issue.
If not, reflash the TWRP, a regular TWRO available and not specific to elite or meticulous, but generic one given by OldDroid.
I hope you have downloaded the content for dload, if not, download these for B140.
Flash this via TWRP- http://update.hicloud.com:8180/TDS/...afnaf/update_data_full_BLN-L21_hw_meafnaf.zip
no further changes and Then use dload method for this file- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v105054/f1/full/update.zip
Try above and provide feedback. This is what I could think of best possible way to have everything with all system app working.
If not, let me know and I will try to help further.
Hi, I thought I need the vendor image since TWRP (all versions) tell me "Could not mount/wipe vendor" and "Could not mount/wipe product" "invalid argument" for both.
I tried the factory reset before but it does not work. It stops at 23% then shows a red exclamation mark and just goes to the original screen with the 3 buttons (restart, shutdown and wipe).
I am currently trying to get it to recognize my sd card. But somehow it does not work through TWRP it just does not recognize the 8GB SD Card. Also I am currently on the TWRP I was before all of this happened (3.1 openkirin). Without the SD Card recognized I can't put the dload files for it on it and in turn I can't use the dload.
I mean technically it should very well be possible to fix the device since it isn't a real brick and even TWRP and Fastboot load. It's just that all those little things are somehow ruining it.
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
algg said:
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
Click to expand...
Click to collapse
Sure, let me explain.
The first file is the data file which will install few systems apps like file manager, updater, themes, clock, fm radio etc. This will work via dload as well but the installation time is around 3-7 seconds so, over the course of time and flashing few times, i realised that these PV files cannbe flashed via TWRP and it works perfectly fine specific to PV files( twrp won't supoort other stock zips). We foash this first so that it updates your buld number and also does not replace the recovery with stock (as if you flash the main update zip first, it will replace with stock recovery so flashing the 2nd file will be quick but with unstable system apps, sometime).
Now we flash the main zip file with update.app via dload and it Install the main firmware for boot, vendor, recovery, system, usrdata etc.
Hope this explanation helps, if not let me know and I will rephrase myself.
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Is there any way I can "debug" what is going on while the boot animation is playing?
What is confusing me is that the boot animation plays just normal but it simply does not continue to the actual OS.
algg said:
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Click to expand...
Click to collapse
Not bricked..its just Data is not mounted or encryption. Should never encrypted it. NVM.
Do one thing, boot to twrp recovery. Try flashing and get error, then go to main TWRP page and click on reboot, select recovery out of 4 options( power off, system, bootloader and recovery). It will boot to recovery, now try flashing it again and see. Most if the time it helps.
Else, go to main page, select wipe, click on format rather than wipe here, it will prompt for typing Yes to confirm. Biit to recovery from main twrp page ( as mentioned above). And try this same thing of formatting data couple of times and then flash the zip and then dload.
I know these are tedious steps but inhave revived my device many a times with all these tricks after some efforts.
Good luck
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
algg said:
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
algg said:
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
I'm happy for you man, indeed it would be so bad, especially because you got this device 3 or 4 days ago if i didn't read bad, anyway what matters is that now it works. Are you able to restore the previous backup through TWRP now? (But before trying... Make a backup of your actual OS )
shashank1320 said:
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
Click to expand...
Click to collapse
Are you joking man? I just tagged you for more help, but practically you helped him in everything, not me; I'm sure that you would noticed the thread and helped as always even without my tag, i just speeded up things for being helpful to algg.
algg, I'd like to apologize myself; i didn't vanished after tagging shashank, today i just was at work and obviously i was busy for help, but as i saw with pleasure he already helped you to restore your OS and that was the objective. Nice one, guys!
I was on Havoc OS and tried to go back to stable OS throught TWRP. The plan was to flash stock OOS 9.04 then TWRP blu spark then reboot to recovery again and flash again stock OOS 9.04 and again TWRP and then reboot again to recovery to do a wipe and finally boot up and setup. The problem is that after flashing OOS over Havoc and then TWRP, when I selected to reboot to recovery it did but all files seem to be gibberish. I think this means that the device is encrypted cause when entering TWRP it doesn't ask me for my password. I know that if I do a full wipe it will 99% fix but I want my files in data/media. Is there a solution???
Please help!
I had this happen to me after a failed rom update, all the directories were numbers and hex code, there was no way for me to fix it other than flash using the bricktool
Sorry
eltarod said:
I was on Havoc OS and tried to go back to stable OS throught TWRP. The plan was to flash stock OOS 9.04 then TWRP blu spark then reboot to recovery again and flash again stock OOS 9.04 and again TWRP and then reboot again to recovery to do a wipe and finally boot up and setup. The problem is that after flashing OOS over Havoc and then TWRP, when I selected to reboot to recovery it did but all files seem to be gibberish. I think this means that the device is encrypted cause when entering TWRP it doesn't ask me for my password. I know that if I do a full wipe it will 99% fix but I want my files in data/media. Is there a solution???
Please help!
Click to expand...
Click to collapse
Probably because the Security Patch level was higher on Havoc.
You could try flashing Havoc again, but i don't know how since your storage is encrypted ...
Last time i tried this, it failed to boot, and switched slots, booting into the old ROM.
But if you flashed OOS two times, it's impossible.
There must be a way since I know the password to decrypt the files... Right?
I did flash Havoc successfully again with sideload method but doesn't seem to work. Maybe install Gapps too?
Ok so I flashed havoc+gapps. Phone booted up and I was in working condition but folders and files stayed encrypt and can't be moved with PC or anything. Should I give up and go to MsmDownloadTool ?
eltarod said:
Ok so I flashed havoc+gapps. Phone booted up and I was in working condition but folders and files stayed encrypt and can't be moved with PC or anything. Should I give up and go to MsmDownloadTool ?
Click to expand...
Click to collapse
No need to use Msmdownloadtool, you can use fastboot ROM and boot the phone in fastboot mode. You will lose your files as always (the moment the encription broke you lost your key and the files are permanently encripted), but the procedure is much less painful than the Msmdownloadtool.
Just format your internal storage (using format data) in twrp and you can flash oos and boot into the rom without any issues. I do that all the time whenever I need to flash back oos from custome roms. No need for those msmtool or even fastboot rom..
eltarod said:
There must be a way since I know the password to decrypt the files... Right?
I did flash Havoc successfully again with sideload method but doesn't seem to work. Maybe install Gapps too?
Click to expand...
Click to collapse
Did you try flashing Havoc, then going back to TWRP ? I worked for me when i had the issue, having the good ROM flashed and active on the slot allowed me to enter my password in Blu_Spark TWRP.
By the way, MSMDownloadTool will just Format Everything and flash OOS, so if you're stuck, better just flash OOS from recovery and Format Data, same result, less hassle.
You should solve with last beta cause It has the same patch security.
Just boot TWRP recovery through fastboot (via a PC!) , works for me when encryption messes up.
P.S. - Always have a backup before flashing ANYTHING.
---------- Post added at 10:20 AM ---------- Previous post was at 10:15 AM ----------
eltarod said:
Ok so I flashed havoc+gapps. Phone booted up and I was in working condition but folders and files stayed encrypt and can't be moved with PC or anything. Should I give up and go to MsmDownloadTool ?
Click to expand...
Click to collapse
If my last post before doesn't work, try switching boot slots.
Thanks for all the replies. Didn't have the time to try what all of you suggested. Finally I formated everything and lost a couple of things but I couldn't stay without a phone.
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
Today i tried to root my samsung galaxy j4+ SM-J415FN i failed. I Flashed TWRP using odin successfully but this is where the problems started. I tried to mount and access partitions to flash rmm lock bypass so i would not get locked out and no verity opt encrypt but i could not access the file. I could not connect to pc using usb. I decided to search on the forum. I cleared cache, dalvik, tried to format and repair partitions but it didn't work. After try to boot to OS i seen "recovery is not seandroid enforcing" error. I decided to flash stock recovery. I was stuck in only boot loop but the error stopped happening. Then i decided to re-flash the entire firmware and now im left with working os but i flashed polish rom but the language is not polish... its fine but how can i flash TWRP correctly without screwing everything up and root? i got every zip i need i think and custom kernel (i read that to root i need to flash custom kernel i didn't flash any zips and it because i could not access files from pc or on partitions (i read in a post on the forum that on android pie i need custom kernel to do rooting)).
So how do i flash it correctly and root without screwing up everything again?
And by the way version of TWRP i used is twrp-3.6.0_9-1-j4primelte.img.tar
The RMM/LG lock did not trigger
Bootloader unlocked
Edit: i found out that i flashed t mobile firmware
Oh yes and screen locks were and are disabled
TWRP showed that data partition size is 0mb
I'm also searching for a stable way to root J415FXXU6.
Tried the old method, but can't use lockscreen on it.
Edit:
Tested this tutorial so far lockscreen and root are stable
Galaxy J4 Plus : TWRP Magisk Root
This blog has move and will not be update again.For new update please follow ▶▶
langithitam.wordpress.com