Hi,
I recently unlocked my bootloader after a really long time. I then proceeded to flash twrp and then flashed superSU and rooted my phone. I took a backup of my rom and then proceeded to install RR 5.8.4. I was given a error 7. Tried this method (https://forum.xda-developers.com/showthread.php?t=2522762) but then it gave me a error 6. Would someone help me out ?
Thx.
1) flash latest global developer MIUI ROM via MiFlash to updated firmware and to reset things if they messed up (watch out if you lock your bootloader while flashing, choosing the wrong .bat file);
2) after flash TWRP via fastboot;
3) boot TWRP and "advanced wipe" ALL partitions (except MicroSD if you have a MicroSD inserted and you want to keep its data);
4) reboot to recovery and install the RR .zip file (and the gapps .zip file if you use it);
5) after you boot into RR, you can then reboot to TWRP and install Magisk .zip to get root and other nice things.
Can i factory reset my device instead of flashing developer rom as the developer rom is quite big, around 1.4gb?
shalom170401 said:
Can i factory reset my device instead of flashing developer rom as the developer rom is quite big, around 1.4gb?
Click to expand...
Click to collapse
If you've TWRP installed at the moment then try this :
Boot to TWRP
Take a nandroid backup (just incase)
Wipe > advanced wipe > swipe to confirm
Flash firmware if you're coming from marshmallow based MIUI
Flash ROM & Gapps
Reboot
If you still get errors, probably corrupted zip. Try Re-downloading the zip.
shalom170401 said:
Can i factory reset my device instead of flashing developer rom as the developer rom is quite big, around 1.4gb?
Click to expand...
Click to collapse
You can try. Remember that if you download the full MIUI ROM, you should follow this guide http://en.miui.com/a-234.html
You can also upgrade the firmware without downloading the full ROM, from here https://forum.xda-developers.com/re.../firmware-firmware-update-2017-08-04-t3651537
Will try soon and reply
Even after flashing the firmware, i get the same error 7
I have downloaded this rom (https://www.google.co.in/amp/s/foru...nt/rom-resurrectionremix-5-8-2-t3567023/amp/) and flashed twrp using this guide (http://en.miui.com/thread-536180-1-1.html)
Maybe this is a stupid question, but your phone has MediaTek chipset or Qualcomm chipset?
I'm pretty sure it is qualcomm as the cpu speed is 2.0ghz
Now, i get this error and status error 7.
What should i do?
Where you can format all partitions, you can fix them too.
It looks like your /data is using f2fs, you should fix it converting the partition in ext4 (in official TWRP it's not possible to use f2fs).
Check all partitions, not only /data, to be formatted as ext4
So, what r the steps i should follow?
And btw, is there any unofficial twrp which i could use?
Enter TWRP, choose Wipe > Advanced Wipe
Check the box for "data"
Tap "change or repair file system"
Tap "Change file system"
Tap "ext4"
Swipe the button
Repeat for other partitions
I don't know if there are unofficial TWRP that support f2fs. Probably they exists, but you should also check if the default RR kernel supports f2fs, else you have to flash a custom kernel that supports f2fs.
Just one important question. During this process, if something weird happens ( like i get my phone soft bricked) and i got a nandroid backup. Will i be able to flash it successfully using twrp?
Yes, changing file system is a pretty safe operation (except for the erasing of the data inside the partition, as a normal format).
Flashing the backup or a full fastboot image will reset things back.
But it already shows it as ext4
Oh mahn, it still doesn't resolved?
Flash official TWRP via fastboot mode, skip this step if your already on official TWRP
Boot to TWRP
Wipe
Flash cm14.1 mido firmware
Flash Rom
Flash Gapps
??
Reboot
Note that, you should try Re-downloading all the things, like Rom / Gapps
Dude, i am unable to flash the rom due to cant install this package error and status error 7 !
shalom170401 said:
Dude, i am unable to flash the rom due to cant install this package error and status error 7 !
Click to expand...
Click to collapse
Yeah man, that's what I'm saying, you should try installing cm14.1 firmware first, then Rom..
Even after flashing the firmware, i get the same errors
Related
Hi,
I'm using a galaxy s2 gt-i9100 as a spare phone and i thought it would be a good idea to upgrade from CM13.1 to lineage os 14...
Unfortunately that didn"t go well, the phone is not bricked BUT :
1)i can only flash recovery using odin, heimdall says flash ok but recovery never changes, same as when i tried to install the TWRP recovery from a zip file in the CWM 6.0.2.9 recovery
2) flashing from that CWM version a lineage os zip file always resulted in the progress bar to be stuck at the very begining of the process so i updated the phone with a 3GB PIT file to fix the issue.
3) now the same CWM doesn"t want to mount the SD card while it's working perfectly from within the phone or with the phone(using latest stock firmware) on my PC
4) i can"t use that CWM as recovery because i can't use adb sideload or install zip from a file anymore(i guess due to the 3GB PIT file)
So is it possible to have a TWRP recovery flashable with odin for the GT-I9100 ?
Will that TWRP recovery finally allow me to flash the lineage os zip file?
thanks,
NHJ1981 said:
Hi,
I'm using a galaxy s2 gt-i9100 as a spare phone and i thought it would be a good idea to upgrade from CM13.1 to lineage os 14...
Unfortunately that didn"t go well, the phone is not bricked BUT :
1)i can only flash recovery using odin, heimdall says flash ok but recovery never changes, same as when i tried to install the TWRP recovery from a zip file in the CWM 6.0.2.9 recovery
2) flashing from that CWM version a lineage os zip file always resulted in the progress bar to be stuck at the very begining of the process so i updated the phone with a 3GB PIT file to fix the issue.
3) now the same CWM doesn"t want to mount the SD card while it's working perfectly from within the phone or with the phone(using latest stock firmware) on my PC
4) i can"t use that CWM as recovery because i can't use adb sideload or install zip from a file anymore(i guess due to the 3GB PIT file)
So is it possible to have a TWRP recovery flashable with odin for the GT-I9100 ?
Will that TWRP recovery finally allow me to flash the lineage os zip file?
thanks,
Click to expand...
Click to collapse
First--you can't mount sdcard after repit if you didn't format it
Second--repit using 3GB PIT is useless procedure, because you only changed the data partition size, instead repit with a 1GB_3GB.pit to change system partition to 1GB.
Third--to get TWRP 3 you must be on a rom with a kernel that supports isorec recovery, so you should flash a CWM kitkat compatible recovery through Odin and reboot to recovery and flash latest CM11 to get isorec support then reboot to recovery flash TWRP 3.0.2.1 image and then reboot recovery and flash your desired nogut rom and gapps.
If you couldn't understand me, then simply follow this guide
Hello,
thanks for your reply, it was exactly what i was looking for, i wish my Google searches about that matter redirected me to that tutorial.
IT worked brilliantly exept an error regarding formating and mounting of data partition after the use of the PIT file but upon restart, the procedure : 'Go to Wipe -> Advanced wipe,
select Dalvik, Cache, System, System, Data, Internal Storage then Swipe to Wipe, go back to TWRP Home.' completed without any errors.
That old phone is now running nougat.
NHJ1981 said:
Hello,
thanks for your reply, it was exactly what i was looking for, i wish my Google searches about that matter redirected me to that tutorial.
IT worked brilliantly exept an error regarding formating and mounting of data partition after the use of the PIT file but upon restart, the procedure : 'Go to Wipe -> Advanced wipe,
select Dalvik, Cache, System, System, Data, Internal Storage then Swipe to Wipe, go back to TWRP Home.' completed without any errors.
That old phone is now running nougat.
Click to expand...
Click to collapse
Great, happy to help
Enjoy the Nogut taste
Hi,
I wanted to upgrade my i9100 so i used odin 3.04 to flash the kitkat compatible .tar file you mentioned through download mode. The flashing in odin showed no errors but my phone is dead now and doesnt turn on!
Now i can only get into download mode using the key combinations.
What did i do wrong coming from CM9.1 with cwm 6.0.1.2 on it. And how to fix this?
ANDRiMiON said:
Hi,
I wanted to upgrade my i9100 so i used odin 3.04 to flash the kitkat compatible .tar file you mentioned through download mode. The flashing in odin showed no errors but my phone is dead now and doesnt turn on!
Now i can only get into download mode using the key combinations.
What did i do wrong coming from CM9.1 with cwm 6.0.1.2 on it. And how to fix this?
Click to expand...
Click to collapse
Your phone won't boot of course, because the kernel recovery you flashed is a kitkat kernel recovery, just reflash it again with a pit with 1GB system or more and your desired data partition size, all pits are available in repartition guide by saber, after you enter into recovery, you should navigate to mount then "format sdcard" or "format internal sdcard", i don't actually remember the option, then format it and format data and system and cache and dalvik cache, then install the latest cm11 rom to get isorec support, then let it reboot, then reboot to recovery and flash TWRP 3.0.2-1 image from the TWRP 3 thread's download section, then reboot recovery and flash your desired nogut rom and gapps
Just a sec i will give you some links..
Much appreciated. I am really stuck right now.
Can i conclude that when i flash CWM 6.0.1.2 my CM9.1 will be alive and kicking?
I think i want that right now, i postpone the upgrade to the future. Not really comfy right now....
hmmm i can't find the link to CWM 6.0.1.2 for i9100. Thats what i need right now...
ANDRiMiON said:
Much appreciated. I am really stuck right now.
Can i conclude that when i flash CWM 6.0.1.2 my CM9.1 will be alive and kicking?
I think i want that right now, i postpone the upgrade to the future. Not really comfy right now....
hmmm i can't find the link to CWM 6.0.1.2 for i9100. Thats what i need right now...
Click to expand...
Click to collapse
you have to flash a kernel not just a recovery, try dirty flashing your cm9.1 again that should make it boot correctly, and will replace the current recovery with the recovery that comes with the rom
I found my cm9.1. How does dirty flashing works? Can it be done with odin?
Does this erase all my data on my device?
edit:
Do i choose pda or phone when entering cm9.1 in odin. And where to select wipe cache and dalvik cache?
CM11
1.5GB PIT Files or 1GB PIT Files by ELgmal 1GB is enough.
Kitkat compatible recovery
this is for future update
---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------
ANDRiMiON said:
I found my cm9.1. How does dirty flashing works? Can it be done with odin?
Does this erase all my data on my device?
Click to expand...
Click to collapse
no just flash it in recovery and wipe cache and dalvik, if you had xposed then flash xposed after the rom and wipe dalvik and cache and reboot.
ps: next time you post, please quote my post or mention me in your post so i can reply faster to your post
no it won't delete any data
---------- Post added at 04:45 PM ---------- Previous post was at 04:18 PM ----------
andrimion said:
i found my cm9.1. How does dirty flashing works? Can it be done with odin?
Does this erase all my data on my device?
Edit:
Do i choose pda or phone when entering cm9.1 in odin. And where to select wipe cache and dalvik cache?
Click to expand...
Click to collapse
DON'T USE ODIN, the rom is zip flash it through recovery
The problem is i can't access the data partition in windows explorer so i can not place the cm 9.1 zip file on my device. I can enter the recovery mode though
ANDRiMiON said:
The problem is i can't access the data partition in windows explorer so i can not place the cm 9.1 zip file on my device. I can enter the recovery mode though
Click to expand...
Click to collapse
have you tried with an external sdcard?
you can use an adapter to connect your external sdcard to your pc and copy your rom to
That worked fine. My device is up and running.
Many thanks for your help!
ANDRiMiON said:
That worked fine. My device is up and running.
Many thanks for your help!
Click to expand...
Click to collapse
No problem, glad to help
MigoMujahid said:
First--you can't mount sdcard after repit if you didn't format it
Second--repit using 3GB PIT is useless procedure, because you only changed the data partition size, instead repit with a 1GB_3GB.pit to change system partition to 1GB.
Third--to get TWRP 3 you must be on a rom with a kernel that supports isorec recovery, so you should flash a CWM kitkat compatible recovery through Odin and reboot to recovery and flash latest CM11 to get isorec support then reboot to recovery flash TWRP 3.0.2.1 image and then reboot recovery and flash your desired nogut rom and gapps.
If you couldn't understand me, then simply follow this guide
Click to expand...
Click to collapse
thanks this really helped me, I was struggling to get lineage installed, I had CyAN12 rom before and wasnt easy to move from there
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Same here...i flash all nougat rom and got bootloop..now i stay in mm only...:C
Reflash newest stock image, than hack the emmc bootloader of it and try again
reemar said:
Reflash newest stock image, than hack the emmc bootloader of it and try again
Click to expand...
Click to collapse
So you mean to flash the latest stock ROM, won't it remove TWRP and lock the bootloader? And how to "hack" the emmc bootloader? Sorry, I'm a newbie
Just wait for at least 15 minutes after flashing
DdroidTHEGAMER said:
Just wait for at least 15 minutes after flashing
Click to expand...
Click to collapse
What do you mean, wait in TWRP for 15 minutes or when booting up the OS? As I said, I waited for 30+ minutes while it booted up.
Try installing ROM without flashing the firmware
Minions007 said:
Try installing ROM without flashing the firmware
Click to expand...
Click to collapse
That was the first thing I did (I didn't know a firmware was needed so I only flashed the RR ROM). Same bootloop
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
SpeRator said:
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
Click to expand...
Click to collapse
Did it, same result. Wiped everything, copied zips to internal storage, flashed from there and boom, bootloop
Hmm strange. You could test a good modified rom of rr.
Try this Rom:
https://www.androidfilehost.com/?fid=673791459329049490
And these Gapps:
https://www.androidfilehost.com/?fid=673791459329049438
If it all not Work, you have to flash actually official Rom to restore all with edl.
I have the exact same problem. Cant flash any ROM without getting bootloop. The bootloop though isnt a standard one, i think. I get the logo of the ROM and the phone starts to give Tiny vibrations in regular periods of time. I also left the phone for a long time hoping it'll eventualy boot. No luck. Tried flashing stock ROM with miflashtool and edl. Didnt help as well. I wonder if it could be the fault of any previous roms i had installed.
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
SpeRator said:
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
Click to expand...
Click to collapse
Changed to writemode.. default options selected in the mounts screen.
unable to flash any Nougat roms- stuck in boot animation.
is it because the bootloader was unlocked unofficially via lollipop fastboot ROM 7.1.8??
All right, got it working.
I flashed the latest official MIUI ROM with the official flashing tool with the option "clear all". Then I had to open the bootloader again, then flash TWRP, then flash RR, and it works! Looks like something was wrong with the previous installation, the clearing everything did the job.
Were your bootloader unlocked officially?
aldhi said:
Were your bootloader unlocked officially?
Click to expand...
Click to collapse
Unlocked Unofficially via this method https://www.youtube.com/watch?v=2FmaCdnLi58
tonyrulez said:
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Click to expand...
Click to collapse
Backup all of your data from internal storage and flash latest fastboot developer ROM and setup it. This will fix all issues regarding ROMs, zips, bootloops and firmware and any other. After that flash latest ZCX recovery as RedWolf recovery causes problems for flashing ROMs and zips as per my experiance. Then simply flash RR and gapps and boot and wait for 15 minutes and till then don't restart device.
Hey everybody,
I was on LOS 15.1 for a rather long time and I wanted to try RR, so as usual I backed up my system and tried to flash the RR-rom.
It did not work at all and I got several errors among which error 7 and the unability to mount system partition were the most prominent.
The device got bricked several times but I got it back to life with MiFlashTool, running either MIUI 8.5 or MIUI 9.
The strange thing is that even after flashing the MIUI-img - and basically bringing the device back to its factory firmware - I could not flash a rom.
I tried several recoverys; the latest TWRP, the TWRP linked in the LOS15.1 thread and OrangeFoxRecovery. None of them would work. I wiped all partition, nothing worked. I got different errors shown, most of them were error 7 or not being ablke to mount system, as stated before.
Right now I am back to MIUI and rooted it, which worked from OrangeFox, but I actually would like tzo run a custom rom again.
Any idea what I could do?
Cheers!
Noone who has an idea why it would not work?
I thought that after flashing via Flashtool the phone would be as good as new and all prioir changes would be gone? Wha can I not flash anything via recovery and get erros?
Or are there different versions of Orange Fox Recovery? RR would be treble, so I would need a treble recovery.
Cheers!
Have you tried to format internal storage?
If not backup data in sdcard or pc and format it using recovery.
Are you using trble supported recoveries?
Did you encrypted your data while using Lineage OS?
Hey,
well, yes, I encrypted data but since reinstalling MIUI via Flashtool this is gone. And I thought that this should be enough and reflashing it via MiFlash is like a factory reset? Is there anything I did not consider?
After Flashtool did not do the trick, wiped everything but External memory in TWRP, no kelp either.
I also did the normal wipe (where you dont have to choose which partition), this did not help.
As I said, I am currently on the latest OrangeFox Recovery but I also tried the latest TWRP and the TWRP in the LOS 15.1-Thread, which did not help.
To my knowledge all of the are treble recoverys?
I also tried to restore a vackup of LOS which did not work...
I flashed
wurst_wasser said:
Hey,
well, yes, I encrypted data but since reinstalling MIUI via Flashtool this is gone. And I thought that this should be enough and reflashing it via MiFlash is like a factory reset? Is there anything I did not consider?
After Flashtool did not do the trick, wiped everything but External memory in TWRP, no kelp either.
I also did the normal wipe (where you dont have to choose which partition), this did not help.
As I said, I am currently on the latest OrangeFox Recovery but I also tried the latest TWRP and the TWRP in the LOS 15.1-Thread, which did not help.
To my knowledge all of the are treble recoverys?
I also tried to restore a vackup of LOS which did not work...
I flashed
Click to expand...
Click to collapse
When you reply quote, I didn't get notifications for your reply.
Your bootloader is unlocked and you installed Twrp recovery.
Try copying Rom zip to SD card and wipe system, data, cache, dalviks cache, internal storage (exclude sd card off course). Then install it.
It should work
As I said, I did all of this, yet it does not work.
After wiping I tried to flash RR rom...
I get "Patching system image unconditionally...
Then I get E1001: Failed to update system image. (in white)
Updater process ended with: ERROR 7 (in red)
Error installing zip file 'patch...' (in red)
Updating partition details (in white)
Failed to mount '/system' (Invalid Argument) (in red).
As I said, that happens with different recoverys and different roms (treble and non treble)
wurst_wasser said:
As I said, I did all of this, yet it does not work.
After wiping I tried to flash RR rom...
I get "Patching system image unconditionally...
Then I get E1001: Failed to update system image. (in white)
Updater process ended with: ERROR 7 (in red)
Error installing zip file 'patch...' (in red)
Updating partition details (in white)
Failed to mount '/system' (Invalid Argument) (in red).
As I said, that happens with different recoverys and different roms (treble and non treble)
Click to expand...
Click to collapse
Are you sure the Rom you installating is for your device because error 7 occured if the rom you are trying install is not for your device.
Yes, of course, it was the correct ROM. Before error 7 I got error 1001 and I guess this was the initial problem.
My guess it that the problem was the decrypted partition which I did not format in twrp in my first go. Every wipe and format afterwards somehow did not help...
Now after having flashed recovery and different roms 10 times and using miflash 10 times it worked and now I am on RR. Don't ask me what eventually did the trick.
wurst_wasser said:
Yes, of course, it was the correct ROM. Before error 7 I got error 1001 and I guess this was the initial problem.
My guess it that the problem was the decrypted partition which I did not format in twrp in my first go. Every wipe and format afterwards somehow did not help...
Now after having flashed recovery and different roms 10 times and using miflash 10 times it worked and now I am on RR. Don't ask me what eventually did the trick.
Click to expand...
Click to collapse
Great to know
I hated MIUI because of the bloatware and ads. Have fun using RR. If you want you can use Liquid Remix Pie its a great ROM.
Yes. I also did not like MIUI that much, that's why I was using Lineage before I wanted to try RR: Thanks for the advice for anothe rom.
i fix this issue by format data, not only wipe then restart the recovery and install the ROM, then finally it works !
Shojimeguro said:
i fix this issue by format data, not only wipe then restart the recovery and install the ROM, then finally it works !
Click to expand...
Click to collapse
How did you format? noob
Shojimeguro said:
i fix this issue by format data, not only wipe then restart the recovery and install the ROM, then finally it works !
Click to expand...
Click to collapse
If I format data, then I have to reboot into the recovery menu to be able to use data again. But this is impossible, because it gets stuck into the bootloop every time I try to reboot. Any other option to fix this error?
EDIT:
I could fix it myself:
1. MIUI latest version; flash with MiFlash.
2. flash TWRP with e.g. YUware
3. flash latest fw_vendor in TWRP
4. full update pixel expierence (NOT incremental) rom flash
5. Partitions/Data/Format
6. Reboot and ready to use
So i installed Pixel E as said in the forum post and videos and it was working fine, TWRP was fine and installed with no problems, then i went back to MIUI for the L1 certificate update and decided that i wanna try oxygen OS
i install TWRP like i did the first time but this time i didnt get the menu that says swipe to allow modifications, after that i went and mounted vendor and system like i did the first time, and i went to wipe the data i didnt find the vendor option there, it was weird and i thought there`s something wrong with the phone
i go back to the install, i install the disable force encyption file and try to install the rom, i get the success thingy
i restart and it says encrypting your phone and i boots back to recovery
can anyone help with that please? i tried 4 different roms all are the same
and how can i show the vendor option again?
OxygenOS Comes With A Modified Vendor So When You Flashing OOS You Need To Flash DFE Due To Encryption Problem.
Decrypt Your Data By Formatting internal Storage.
Go To Wipe format Data Type Yes Reboot to system.
Just Allow that modification when you decrypt your phone and flashing a Rom that TWRP modification sign comes.
When you wipe data system , Vendor Partition will be Automatically Wiped.
Flash Orange Fox Recovery You Will Also Get that Vendor Partition.
iHookar said:
So i installed Pixel E as said in the forum post and videos and it was working fine, TWRP was fine and installed with no problems, then i went back to MIUI for the L1 certificate update and decided that i wanna try oxygen OS
i install TWRP like i did the first time but this time i didnt get the menu that says swipe to allow modifications, after that i went and mounted vendor and system like i did the first time, and i went to wipe the data i didnt find the vendor option there, it was weird and i thought there`s something wrong with the phone
i go back to the install, i install the disable force encyption file and try to install the rom, i get the success thingy
i restart and it says encrypting your phone and i boots back to recovery
can anyone help with that please? i tried 4 different roms all are the same
and how can i show the vendor option again?
Click to expand...
Click to collapse
just download
https://mirror.akhilnarang.me/MIUI/beryllium/beryllium-9.4.8-9.0-vendor-firmware.zip
and flash it via twrp! and reboot
Olystem said:
OxygenOS Comes With A Modified Vendor So When You Flashing OOS You Need To Flash DFE Due To Encryption Problem.
Decrypt Your Data By Formatting internal Storage.
Go To Wipe format Data Type Yes Reboot to system.
Just Allow that modification when you decrypt your phone and flashing a Rom that TWRP modification sign comes.
When you wipe data system , Vendor Partition will be Automatically Wiped.
Flash Orange Fox Recovery You Will Also Get that Vendor Partition.
Click to expand...
Click to collapse
I did that and it worked, thanks but the swipe to allow modifications page still didn't appear, it booted right to main page of TWRP
YasuHamed said:
just download
https://mirror.akhilnarang.me/MIUI/beryllium/beryllium-9.4.8-9.0-vendor-firmware.zip
and flash it via twrp! and reboot
Click to expand...
Click to collapse
I downloaded Vendor firmware but it still gave me the same problem, what fixed it is installing DFE after the rom not before, thanks a lot appreciate you helping
iHookar said:
I did that and it worked, thanks but the swipe to allow modifications page still didn't appear, it booted right to main page of TWRP
Click to expand...
Click to collapse
That Sign Comes Only One Time.
Swipe To Allow Modification Means You will not getting any error while Flashing.
Check in Mount Partition System Keep Read Only If It's Enabled Simply Remove that Mark or Tick Reboot To System.
Plz anybody help this out...
I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery.
Initially console shows decrypted FBE device with default password. But Encryption status : Encryped
So I went into wipe & Formatted Data inorder to get rid of encryption. Then I rebooted recovery & it shows Unable to decrypt FBE device.
[UPDATE] (24/12/20) : The console output Unable to decrypt FBE device was nothing but to tell us that incompatible operating system flashed.
I flashed global version roms which are the main cause for bootloops. I flashed stock rom, then immediately worked out of the box.
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
LoadOP2 said:
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
Click to expand...
Click to collapse
Thnx for reply. I've tried Orange fox too. When I format data, internal storage doesn't decrypt. Also when I flash custom roms, they flash, but I'm gonna stuck in bootloop.
My main problem is that I can't decrypt storage. Phone boots only when I'm on MIUI stock. Am I missing something ?
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
LoadOP2 said:
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
Click to expand...
Click to collapse
Thnx for the reply. I'm trying to have lineage 17.1 & resurrection remix official build. I think rom's not the issue here. I need to know one thing.
To exactly say my issue, I can do flashing. But when I do & then reboot, Internal storage doesn't show the size & mtp doesn't work too, with bootloop issues along together.
There is no official LineageOS for the device.
kalehrl said:
There is no official LineageOS for the device.
Click to expand...
Click to collapse
Oh, I've mistaken, I was about to say resurrection remix official build & lineage unofficial one. Btw what do you think my device is going up to ? How can I decrypt & use internal storage successfully? I can't use internal storage when I flash a rom. Bcaz internal storage renders useless because of encryption.
Which recovery are you using?
Try flashing magisk 20 or 21.
Flash twrp by marounfurio( I am sorry if I slaughtered the name) which is available on xda.
And format data.
It's midnight here and I am going to sleep I will help to tommorow morning.
LoadOP2 said:
Which recovery are you using?
Try flashing magisk 20 or 21.
Click to expand...
Click to collapse
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
Click to expand...
Click to collapse
And what about flashing magisk in twrp.
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
Click to expand...
Click to collapse
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
LoadOP2 said:
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
Click to expand...
Click to collapse
Yah, I'm feeling weird too. Normally there are 3 ways to remove decryption...I tried all those.
1. Formatting Data by typing "yes"
2. Formatting data partition from f2fs to ext4
3. Installing Decrypt script v2 zip immediately after flashing stock rom.
I tried everything I could. I know all sorts of common flashing things. I caz I always used to try so many roms on my previous redmi's, but this one is special case.
I'd suggest you use LineageOS recovery. That's how I removed decryption.
kalehrl said:
I'd suggest you use LineageOS recovery. That's how I removed decryption.
Click to expand...
Click to collapse
Sure. Encryption is the whole culprit for me to say exactly. I'm trying to decrypt & flash builds. I'll notify if it works. Nice to get help from you guys.
Try this.
How to decrypt rom/storage so you can easily switch roms without format
First I would thankx to @sakhatlonda for koutiliy.zip
Steps to download file
1. Download koutility.zip from below.
2. Documentation related to koutility
Read from below link (recommended)
Just a utility zip which can be flashed on every rom flash, to do some pre-defined tasks.
Can be used either to copy everything you place in sdcard/sudeep/system_root to respective dirs or to set config and use that to do predefined tasks
This is how it works:
Flash in recovery, every option has Note with it
Available Configs:
brbootdtbo - auto backup/restore boot & dtbo, will do backup if no backup present and will do restore if backup is there
bbootonly - always backup boot
bdtboonly - always backup dtbo
resbootdtbo - always restore boot & dtbo (brbootdtbo won't work if this is enabled)
enalways - encrypt always (edauto won't work if this is enabled)
dealways - decrypt always (enalways & edauto won't work if this is enabled)
edauto - auto change encryption state on each flash
avb - removes avb flags (if decrypted)
quota - removes quota flag (if decrypted)
keep - doesn't over-writes boot/dtbo backups
debloat - removes bloats
rebloat - restore removed bloats
patchD - same as flash but set in config
productsize - makes a product image from your currently flashed rom to sdcard/sudeep and adds 600mb to it. So you can flash gapps etc. without error. (PC needed to flash product.img)
Steps to decrypt rom/storage
1. Flash roms
2. Flash koutility.zip tested on aosp only
3. Format data (required only first time after flashing koutility)
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Congratulations your storage/rom is decrypted , you can switch roms without format
Next time when you want to switch roms
Steps
1. Wipe data,caches and dalvik caches
2. Flash rom
3. Flash koutility.zip
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Notes
Remember you need to config koutility.zip in recovery
How to config koutility for decryption
Volume down (set config) > yes
After that "No" till 5th option
Then "yes" for 6th option
Rest "No" till 15th option
Last "yes" to flash
@LoadOP2 Thanx for providing KoUtil & its read me.
But I think we shouldn't reboot to recovery immediately after formatting the data. Because the stock rom will start it's initial encryption process by then & I won't get decrypted storage. Isn't it ?
I think this is the case that's happening to me. I always reboot recovery after formatting data, my storage will encrypt again because of stock rom's existence.
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
LoadOP2 said:
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
Click to expand...
Click to collapse
Yes, you're correct, we should do that. But can you read my 1st post in this thread. This is about that specific problem. I'm rebooting recovery after formatting data, then recovery shows Unable to decrypt FBE device
Send your recovery logs after formatting data.
LoadOP2 said:
Send your recovery logs after formatting data.
Click to expand...
Click to collapse
That would help. I'll attach screenshots too. Currently I'm on stock & being busy. I'll do this by today night & post logs & screenshots.