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.
Related
So this is my first post, but whatever.
So it's safe to say I screwed up, I accidentally deleted my stock (rooted) Samsung OS. I somehow managed to download Paranoid Android 6.0.1 onto the Samsung Galaxy S3 GT-I9300 I received. I heavily dislike Paranoid Android, and I would like to give Cyanogen 14.1 a shot. The problem is since I wiped everything, every time I do a factory reset for my device, it goes into a bootloop, even if I flashed CM 14.1.
I have TWRP installed, if that helps, and all files (that I know of) are installed on my computer (Odin, CM14.1 ZIP, and Paranoid is backed up).
I'd like to thank everyone who even comes and reads this thread, and I'd be very grateful if I managed to get CM 14.1 on the Samsung Galaxy S3 GT-I9300.
Which version of TWRP is installed? If you have 2.87, try 3.02. Are you performing a full system and data wipe before installing cm14.1?
Hi bro
I am agree with the first reply to you.
All You need the official CM14.1 ROM
Download here https://download.cyanogenmod.org/?device=i9300
And then download Gapps for android 7.1 pico
Download here http://opengapps.org/
If yoy havn't twrp recovery ! Download it from here
https://dl.twrp.me/i9300/
The file end with (tar) it flashing with Odin.
And the file end with (img) it is update from other version to new with Flashify app (you can find the app in playstore free)
Now You have all requirements files
Let's flashing Your device:
Move the files to Ext.sdcard
Make sure you have 80% battery charge
Then reboot your device to (recovery mode)
Turn off your device and Push (Power+home+volume up) keys at the same time for 5 sec untill u see the recovery icon
Now go to wipe your phone choose advance wipe check the dalvilk + cache + system + data + inernal storage ,, done
Now go back and choose install
Search to your Ext.sdcard then choose the CM14.1 at the same time click on Add more zips
And choose Gapps 7.1 pico
Now swipe to flash
Wait to flash finish and then click on Reboot system
Done
Good luck
audit13 said:
Which version of TWRP is installed? If you have 2.87, try 3.02. Are you performing a full system and data wipe before installing cm14.1?
Click to expand...
Click to collapse
I'm using the latest TWRP, I made sure to install the latest one, and I'm performing a full data and system wipe before I install CM14.1. My question is does it HAVE to be on an external SD card, because I just port it over to a folder in my internal SD card.
It can be installed from the internal memory. Simplest way would be to boot into TWRP, mount storage, copy over CM and gapps, and flash.
Maybe try TWRP 2.87?
audit13 said:
It can be installed from the internal memory. Simplest way would be to boot into TWRP, mount storage, copy over CM and gapps, and flash.
Maybe try TWRP 2.87?
Click to expand...
Click to collapse
I've tried to do that multiple times, but everytime I try it, the S3 goes into a bootloop.
Due to the bootloop issue, I would flash a stock ROM with Odin, perform a factory wipe from stock recovery, and then see if the phone will boot properly.
Is the phone a gt-i9300 in download mode?
audit13 said:
Due to the bootloop issue, I would flash a stock ROM with Odin, perform a factory wipe from stock recovery, and then see if the phone will boot properly.
Is the phone a gt-i9300 in download mode?
Click to expand...
Click to collapse
Yeah, I managed to install the stock OS. I also tried to install CM14.1 again, following the instructions to the letter, but still no CM build. I have no idea what I'm doing wrong, since I've read multiple threads on XDA and the CM site.
Not exactly sure what you mean by in download mode, since I'm new to all this rooting business.
You need download mode to flash a stock ROM; otherwise, Odin can't install a stock ROM.
audit13 said:
You need download mode to flash a stock ROM; otherwise, Odin can't install a stock ROM.
Click to expand...
Click to collapse
Oh if that's the case, then yes. I put it in Odin mode to flash the stock ROM.
Okay, just to confirm but these are the major steps you took:
flashed the latest stock ROM to the phone;
flashed the latest tar version of TWRP using Odin;
booted into TWRP and copied CM14 to the internal memory or an SD card;
wipe data, system, and cache in TWRP;
flash CM14 in TWRP and rebooted.
Yup, those are the exact steps I took. I think I'm just going to tinker around with the Samsung a little longer, until I manage to brick it, or I'll just continue doing research. I'm already happy I managed to get out of a boot loop on my own, with and without OS.
Are you in Canada? Where did you get the i9300? The i747m is sold in Canada and the i747 is sold in the USA.
audit13 said:
Are you in Canada? Where did you get the i9300? The i747m is sold in Canada and the i747 is sold in the USA.
Click to expand...
Click to collapse
My dad got it for his work during his visit in Turkey, is that a factor during flashing of new OS's? What surprises me is that I could install Paranoid Android 6.0.1 onto it without an OS with little or no problem.
A pre-existing OS on the phone is not a requirement to flash a custom ROM.
As long as the ROM is for the i9300, you should be fine.
audit13 said:
A pre-existing OS on the phone is not a requirement to flash a custom ROM.
As long as the ROM is for the i9300, you should be fine.
Click to expand...
Click to collapse
I made sure it was for the i9300. I'm confused to where it doesn't work because I would see the CM battery charging logo, but when I wanted it to boot, it kept bootlooping for 10 minutes on end. The longest I've let it run was whilst I was sleeping, 8 hours, still nothing.
Maybe try a different version of CM14.1 or a different version of TWRP.
audit13 said:
Maybe try a different version of CM14.1 or a different version of TWRP.
Click to expand...
Click to collapse
I'll give those options a shot. I'll try out clockwork and see. I guess I'll keep going until I brick it. Thanks for aiding me, and enjoy having a happy new year.
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
hi i tryed to convert my redmi note 4x to global when flashing with mi flash tool i did it without clean and after that firmware finish installing but got stuck in bootloop now i flashed twrp and tryed to flash custom rom but again bootloop when i check my storage it shows 9gb now when its actual is 32gb i think i disturbed partitions any solution available?
Are you able to boot into TWRP?? If not flash TWRP first using fastboot.
Once you have access to TWRP boot into it and perform a full wipe (System + Data + Cache + Dalvik + Internal Storage). Perform a format too after wipe to be on the safer side. Now copy a custom ROM or MIUI ROM to your Internal Storage or SD card through a computer. Once copied install your ROM.
If you flashed custom ROM flash Gapps after flashing ROM. Reboot.
If you flashed MIUI, flash lazyflasher after that(or phone will be stuck at MI logo). Reboot.
You can find download links for lazyflasher here on XDA or you can google it too.
ArK96 said:
Are you able to boot into TWRP?? If not flash TWRP first using fastboot.
Once you have access to TWRP boot into it and perform a full wipe (System + Data + Cache + Dalvik + Internal Storage). Perform a format too after wipe to be on the safer side. Now copy a custom ROM or MIUI ROM to your Internal Storage or SD card through a computer. Once copied install your ROM.
If you flashed custom ROM flash Gapps after flashing ROM. Reboot.
If you flashed MIUI, flash lazyflasher after that(or phone will be stuck at MI logo). Reboot.
You can find download links for lazyflasher here on XDA or you can google it too.
Click to expand...
Click to collapse
awais_666 said:
hi i tryed to convert my redmi note 4x to global when flashing with mi flash tool i did it without clean and after that firmware finish installing but got stuck in bootloop now i flashed twrp and tryed to flash custom rom but again bootloop when i check my storage it shows 9gb now when its actual is 32gb i think i disturbed partitions any solution available?
Click to expand...
Click to collapse
@ArK96 is right but the only thing i suggest is to, flash miui and lazyflasher first so as to properly set up the initial firmware, and partitioning. After miui boots properly, you can do anything you want. :highfive:
ArK96 said:
Are you able to boot into TWRP?? If not flash TWRP first using fastboot.
Once you have access to TWRP boot into it and perform a full wipe (System + Data + Cache + Dalvik + Internal Storage). Perform a format too after wipe to be on the safer side. Now copy a custom ROM or MIUI ROM to your Internal Storage or SD card through a computer. Once copied install your ROM.
If you flashed custom ROM flash Gapps after flashing ROM. Reboot.
If you flashed MIUI, flash lazyflasher after that(or phone will be stuck at MI logo). Reboot.
You can find download links for lazyflasher here on XDA or you can google it too.
Click to expand...
Click to collapse
thank you for a quick reply yes i am able to go into twrp and i did format system data cache dalvik and internal storage and after wipe did format too but still stuck at same issue and when i open the internal storage in my computer it shows only 9gb storage
MyNameIsRage said:
@ArK96 is right but the only thing i suggest is to, flash miui and lazyflasher first so as to properly set up the initial firmware, and partitioning. After miui boots properly, you can do anything you want. :highfive:
Click to expand...
Click to collapse
ok so the normal global firmware will do? i didnt do with lazyflasher but will do it now
awais_666 said:
ok so the normal global firmware will do? i didnt do with lazyflasher but will do it now
Click to expand...
Click to collapse
you mean the global rom? yes the one you downloaded from en.miui.com
MyNameIsRage said:
you mean the global rom? yes the one you downloaded from en.miui.com
Click to expand...
Click to collapse
yes thats the one downloading now thank you guys for quick response ill update once done
@MyNameIsRage thank you for correcting me.
Yes. Please do flash MIUI and lazy first. Looks like you messed up your partitions.
Peace.
hey guys i tryed the following method luckily now storage is shown as 23 gb but when i flash miui rom in twrp the process doesnt complete its like the process bar goes till 95 percent and after that it keeps flashing but nothing happening i left the phone like this for 2 hours for 2 times but nothing happened am i doing something wrong here
awais_666 said:
hey guys i tryed the following method luckily now storage is shown as 23 gb but when i flash miui rom in twrp the process doesnt complete its like the process bar goes till 95 percent and after that it keeps flashing but nothing happening i left the phone like this for 2 hours for 2 times but nothing happened am i doing something wrong here
Click to expand...
Click to collapse
After flashing MIUI and lazy you flashed MIUI again is that what you are saying?
ArK96 said:
After flashing MIUI and lazy you flashed MIUI again is that what you are saying?
Click to expand...
Click to collapse
nop i formatted everything and then install miui rom for redmi note 4x which doesnt finish installing
awais_666 said:
nop i formatted everything and then install miui rom for redmi note 4x which doesnt finish installing
Click to expand...
Click to collapse
Go here and download the Global Stable worldwide release version firmware.
Boot into twrp wipe and format everything. Also after that reflash TWRP again using fastboot.
Once reflashed boot into TWRP and again perform a full wipe and format, then install the downloaded firmware zip. After that reboot TWRP and try flashing MIUI.
ArK96 said:
Go here and download the Global Stable worldwide release version firmware.
Boot into twrp wipe and format everything. Also after that reflash TWRP again using fastboot.
Once reflashed boot into TWRP and again perform a full wipe and format, then install the downloaded firmware zip. After that reboot TWRP and try flashing MIUI.
Click to expand...
Click to collapse
cool will try that in a while just a quick question i read somewhere that do the same process with red wolf recovery rather then twrp does that make any difference
awais_666 said:
cool will try that in a while just a quick question i read somewhere that do the same process with red wolf recovery rather then twrp does that make any difference
Click to expand...
Click to collapse
Yes. Red wolf is more MIUI friendly, it is made with OTA survival in mind. But your issue is that the ROM is not getting flashed. You can try what I said above about TWRP reflash, if it doesn't work you can go ahead and try redwolf. REDWOLF is nothing but modded TWRP, base code is still TWRP.
ArK96 said:
Yes. Red wolf is more MIUI friendly, it is made with OTA survival in mind. But your issue is that the ROM is not getting flashed. You can try what I said above about TWRP reflash, if it doesn't work you can go ahead and try redwolf. REDWOLF is nothing but modded TWRP, base code is still TWRP.
Click to expand...
Click to collapse
hey mate finally i got time to do the procedure i flashed the kernel that you told and on top of it the firmware and lazyflasher it went through in just few minutes and was all done and working perfectly now thanks alot
awais_666 said:
hey mate finally i got time to do the procedure i flashed the kernel that you told and on top of it the firmware and lazyflasher it went through in just few minutes and was all done and working perfectly now thanks alot
Click to expand...
Click to collapse
Good job mate.
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
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
gabritb01 said:
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
Click to expand...
Click to collapse
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
gabritb01 said:
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
Click to expand...
Click to collapse
Holy **** how did you come up with this.
Either the zip with Magisk somehow fixed it or installing the android 10 rom somehow. Either way doesn't make sense
flairepathos.info said:
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Click to expand...
Click to collapse
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
heroboy107 said:
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
Click to expand...
Click to collapse
i think somewhere in the process the persist partition gets damaged .
heroboy107 said:
i think somewhere in the process the persist partition gets damaged .
Click to expand...
Click to collapse
so if you have magisk you can use a zip file to chmod 744 or 644 (it may be "chmod root 744" )the /persist partiton and thatll mean only true root has access
so 7 is read write execute 6 is read and write 4 is read only 5 is read execute i forgot which number was execute only 1 maybe?
so play with the permissions or look in the root folder for boot.p or permissions.sh then you can modify in there the permissions, it can cause bootloop , so always keep an original copy or youll hae to reflash(DISCLAIMER)
so you can pull the file using adb+root / or a root explorer
Copy it to phone then edit then copy to SDCARD
reboot to twrp then use shell/terminal "chmod 777" the partition where the file is / or read write everything
then copy the file and overwrite the original