Hi,
I am currently on a 6.0.1 version of RR (Resurrection Remix) and trying to install a 7.1 nougat rom on my redmi-1s.
TWRP version: 3.0.2
Firmware: 8.0.1.0 (flashed the 21 mb files given by the AICP dev)
Old rom: RR (default kernel) (6.0.1)
I am getting Error:7 when flashing a nougat rom. I have tried RR(14.1) and AICP. Both gave the same error.
I followed the procedure given by both devs exactly step by step.
Any idea on how I could fix this issue ?
Use the latest version of TWRP, 3.0.2-1.
It's problem with updater script it's a small mistake done by developer hope so they will fix in their next update
I'm also getting the same problem. Please help
It worked for me.
Thanks
thegrinreaper said:
Hi,
I am currently on a 6.0.1 version of RR (Resurrection Remix) and trying to install a 7.1 nougat rom on my redmi-1s.
TWRP version: 3.0.2
Firmware: 8.0.1.0 (flashed the 21 mb files given by the AICP dev)
Old rom: RR (default kernel) (6.0.1)
I am getting Error:7 when flashing a nougat rom. I have tried RR(14.1) and AICP. Both gave the same error.
I followed the procedure given by both devs exactly step by step.
Any idea on how I could fix this issue ?
Click to expand...
Click to collapse
I try this method and worked :
1. Reboot to recovery (I use TWRP 3.0.2-1)
2. Click Wipe -> Advanced Wipe
3. Thick on Data, System, Cache, Dalvik / ART Cache -> Swipe to Wipe
4. After Complete Wipe then Reboot to Recovery again.
5. Click Wipe -> Advanced Wipe
6. Thick only Data -> Repair or Change File System -> Repair File System -> Swipe to Repair, after done repairing -> Back -> Resize File System -> Swipe to Resize -> Back -> Back
7. Do the number (6) method on System and Cache (One by One), After that you must Reboot to Recovery again.
8. Then you can flash Nougat ROM and GAPPS.
Knoxz said:
I try this method and worked :
1. Reboot to recovery (I use TWRP 3.0.2-1)
2. Click Wipe -> Advanced Wipe
3. Thick on Data, System, Cache, Dalvik / ART Cache -> Swipe to Wipe
4. After Complete Wipe then Reboot to Recovery again.
5. Click Wipe -> Advanced Wipe
6. Thick only Data -> Repair or Change File System -> Repair File System -> Swipe to Repair, after done repairing -> Back -> Resize File System -> Swipe to Resize -> Back -> Back
7. Do the number (6) method on System and Cache (One by One), After that you must Reboot to Recovery again.
8. Then you can flash Nougat ROM and GAPPS.
Click to expand...
Click to collapse
when reparing data it is saying unable to repair data
agriculture said:
when reparing data it is saying unable to repair data
Click to expand...
Click to collapse
try this, Thick On Data -> Repair or Change File System -> Change File System -> EXT4 -> Reboot Recovery -> then repeat method number (6)
Related
I was facing bootloop (stuck at mi logo) issue with installing any custom Rom on my Redmi 1s, and i think many other people suffering this prob too.
Today i finally did it! So, now going to tell you how to excatcly flash any ROM on Redmi 1S!
Follow these steps : (STEP No. 4 and No.6 is too RECOMMENDED) !!
1.Flash TWRP Recovery (Latest one)
2.Backup your ROM (RECOMMENDED)
3.Go to "wipe > Swipe to Factory Reset"
4.(INPORTENT!) after Factory reset, go back on Home, then go to "Reboot > Recovery" (NOTE: reboot into recovery, not in system)
5.After that go to "wipe" again, then click on "Advanced Wipe" then select everything except "USB OTG" and "External SD".
6.After that, reboot into recovery again! Follow 4th no step again! (RECOMMENDED)
7.Now flash the custom ROM zip.
8.After flash, dont reboot! clear delvik cache! (this option will come on left side when your flashing will done)
9.Now Reboot to System and enjoy the ROM
boot loop still exists
Hey i tried this step by step ,,,still failure ,,,, after flashing rom when i reboot to system its just coming to mi screen n blinking
abhijeet.mitra.7 said:
I was facing bootloop (stuck at mi logo) issue with installing any custom Rom on my Redmi 1s, and i think many other people suffering this prob too.
Today i finally did it! So, now going to tell you how to excatcly flash any ROM on Redmi 1S!
Follow these steps : (STEP No. 4 and No.6 is too RECOMMENDED) !!
1.Flash TWRP Recovery (Latest one)
2.Backup your ROM (RECOMMENDED)
3.Go to "wipe > Swipe to Factory Reset"
4.(INPORTENT!) after Factory reset, go back on Home, then go to "Reboot > Recovery" (NOTE: reboot into recovery, not in system)
5.After that go to "wipe" again, then click on "Advanced Wipe" then select everything except "USB OTG" and "External SD".
6.After that, reboot into recovery again! Follow 4th no step again! (RECOMMENDED)
7.Now flash the custom ROM zip.
8.After flash, dont reboot! clear delvik cache! (this option will come on left side when your flashing will done)
9.Now Reboot to System and enjoy the ROM
Click to expand...
Click to collapse
sauman said:
Hey i tried this step by step ,,,still failure ,,,, after flashing rom when i reboot to system its just coming to mi screen n blinking
Click to expand...
Click to collapse
Which rom have you flashed??
I have tried with Ressurection Remix & Xperience both marshmallow version,,,,
vicky romero said:
Which rom have you flashed??
Click to expand...
Click to collapse
sauman said:
I have tried with Ressurection Remix & Xperience both marshmallow version,,,,
Click to expand...
Click to collapse
First wipe cache,dalvik cache,system, data and internal then flash rom then without wiping anything flash gapps then again without wiping anything flash firmware then reboot to system without wiping
Hi you guys
Can anyone tell me how back from custom rom to miui.eu, how to do that?
I had Resurrection Remix Oreo RR-O-v6.1.0-20180817-sagit-Official.zip and I wanted update to RR-O-v6.2.1-20181017-sagit-Final.zip.
After update I have all issues: can not unlock phone after power on, reboot to system almost everytime.
Newest TWRP twrp-3.2.3-4-arian-sagit make a big mess with my time zone and all next attempts to install any version of twrp take over the same time zone error
I came to the conclusion that I think I will return to miui.eu
And forget how to do that
1. Try:
- Boot into this TWRP
- Wipe system, cache and dalvik cache, art, data
- install xiaomi.eu_multi_MI6_8.10.25_v10-8.0
- reboot to system
Code:
No OS Installed! Are you sure you wish to reboot?
2. Try:
- Boot into this TWRP
- Wipe system, cache and dalvik cache, art, data
- format data - write yes tap ok
- Boot into this TWRP again, copy rom from pc
- install xiaomi.eu_multi_MI6_8.10.25_v10-8.0
- reboot to system
Code:
No OS Installed! Are you sure you wish to reboot?
as a result, I have a clean phone with no OS and recovery twrp-3.2.3-4-arian-sagit
I format data and then wipe all, try that.
that no os msg ur getting, if u can get miui to boot then it doesnt matter. give it a few min after you reboot even if it says there's no OS, mby its worth the try.
_euphonic_ said:
Hi you guys
Can anyone tell me how back from custom rom to miui.eu, how to do that?
I had Resurrection Remix Oreo RR-O-v6.1.0-20180817-sagit-Official.zip and I wanted update to RR-O-v6.2.1-20181017-sagit-Final.zip.
After update I have all issues: can not unlock phone after power on, reboot to system almost everytime.
Newest TWRP twrp-3.2.3-4-arian-sagit make a big mess with my time zone and all next attempts to install any version of twrp take over the same time zone error
I came to the conclusion that I think I will return to miui.eu
And forget how to do that
1. Try:
- Boot into this TWRP
- Wipe system, cache and dalvik cache, art, data
- install xiaomi.eu_multi_MI6_8.10.25_v10-8.0
- reboot to system
2. Try:
- Boot into this TWRP
- Wipe system, cache and dalvik cache, art, data
- format data - write yes tap ok
- Boot into this TWRP again, copy rom from pc
- install xiaomi.eu_multi_MI6_8.10.25_v10-8.0
- reboot to system
as a result, I have a clean phone with no OS and recovery twrp-3.2.3-4-arian-sagit
Click to expand...
Click to collapse
Foa this is the wrong place, use the Question / Help section.
Sad to hear you can't use the final RR build, which works just fine. Also my twrp build inst nuking the time, it isn't working on all new builds.
To go to miui you just need to do the steps from your try 2.
1. Download resources:
a. Download the rom UL USER, leave it there and do nothing to it yet.
b. Download the twrp.zip file https://mega.nz/#!l8BXgaDL!Y1AH5TM9jKI5r6LtEKFN_4Po105glHNR602yVDipfF8 (if you still have twrp installed beforehand)
c. Magisk 20.0 https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2. Proceed:
Do not update the UL USER rom from the device's interface (SYSTEM UI), power off, boot into TWRP. Select install zip in the following order:
a. Rom UL USER
b. Twrp.zip
c. Magisk v20.0 (or exit the main menu, select Advanced, install root also)
Done, exit the main menu select advanced wipe, wipe cache, dalvik.
Reboot the device.
Done.
By chicken
This did not completely work for me going from .35 to .64. All the steps completed successfully but when I rebooted the phone, Magisk was not installed so I didn't have root. I was able to then boot to TWRP and successfully install Magisk, but I don't know why it didn't work the first time. Anyone else try this? Did it work as intended for you?
One other thing I noticed - TWRP no longer has an option to wipe the cache under wipe > advanced, only for Dalvik/ART cache. Why?
Wish I would have tried this before i updated and lost root, i flashed a root boot.img with fastboot now im bricked and don't know what to do.
EDIT: got twrp did a factory reset and im in now.
dungnghien said:
1. Download resources:
a. Download the rom UL USER, leave it there and do nothing to it yet.
b. Download the twrp.zip file https://mega.nz/#!l8BXgaDL!Y1AH5TM9jKI5r6LtEKFN_4Po105glHNR602yVDipfF8 (if you still have twrp installed beforehand)
c. Magisk 20.0 https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2. Proceed:
Do not update the UL USER rom from the device's interface (SYSTEM UI), power off, boot into TWRP. Select install zip in the following order:
a. Rom UL USER
b. Twrp.zip
c. Magisk v20.0 (or exit the main menu, select Advanced, install root also)
Done, exit the main menu select advanced wipe, wipe cache, dalvik.
Reboot the device.
Done.
By chicken
Click to expand...
Click to collapse
In my experience after install back twrp reboot back to recovery (twrp) before flashing magisk .
Does this work when updating to A10?
Hi,
i was using LineageOS 17.1(Android 10) on my pixel Xl (32 gb storage)
when android 11 came out, I thought I would switch to pixel experience. So I went to their official website and downloaded the android 11 version of pixel XL
There was an instruction guide provided by the developers on how to install android 11
So I followed that and even after applying update from the adb, there was no issue at all
but when I pressed "Reboot to system" Bootloop is happening
Note: I didn't noticed the official instruction first so i installed twrp to flash the rom just like I flashed LineageOS, but in the advance wipe section, there was only 4 option available
-Dalvik / ART cache
-System
-Data
-Internal Storage
there was no cache option
I formatted the data and wiped all of them and tried to both install and sideload the rom but every time during the installation, an error (code 28) occurs
Then I downloaded the rom again hoping that the previos 1 was corrupted and i saw the instruction guide this time.
So I followed the guide and installed their recovery image, flashed recovery partition and flashed the rom using sideload.
But after rebooting the system, Bootloop keeps occurring
*sorry for any misspell or grammatical mistake*
ROM and Recovery image Downloaded from - https://download.pixelexperience.org/marlin (Android 11, 2021/04/16)
ROM and Recovery image installation guide - https://wiki.pixelexperience.org/devices/marlin/install/
I'm having the same issue. Did you flash the repartition zip?
I ended up reflashing stock rom https://developers.google.com/android/images#marlin
Try doing that and restarting the process
GalaxyWhy said:
I'm having the same issue. Did you flash the repartition zip?
I ended up reflashing stock rom https://developers.google.com/android/images#marlin
Try doing that and restarting the process
Click to expand...
Click to collapse
I actually solved the problem a few moments ago
What i did wrong was, when i sideload the rom rom file with twrp i always cleared the dalvik and cache file
let me make a little guide for you..hope that will help
1. install twrp recovery
2. go to wipe section -> advanced wipe -> wipe all 4(Dalvik/ART cache, System, Data, Internal Storage)
3. do a factory reset and format data
4. go to mount section and check all the boxes (system, data, vendor)
5. sideload the repartition zip according to your storage and device model (mine was pixel xl 32gb)
6. after sideload is done reboot the system..it will reboot into recovery again
7. then again sideload the rom file (don't check the clear cache and dalvik boxes)
8. after that is done, go back to main menu and go to reboot-> switch to slot B-> Reboot into system
Hopefully you're done
Note: don't skip any step regarding how minor it is
and if you wish you can also follow the official instruction: https://wiki.pixelexperience.org/devices/marlin/install/
Let me know if it works for you
Best of luck!
Here's my story.
I successfully installed TWRP followed by LineageOS-19.1 (Android 12) on my Z5 Premium Dual (E6833), but after realising that the camera didn't work, I decided to try LineageOS-17.1 (Android 10).
I was following the install script on this thread ...
Xperia Z5 Premium Android Development
Android development for the Sony Xperia Z5 Premium
forum.xda-developers.com
1) Reboot into TWRP Recovery.
2) Select Wipe -> Swipe to factory reset -> Advanced Wipe -> Dalvik /ART Cache, System, Cache and Data -> Swipe to Wipe.
3) Go back to TWRP's main menu -> Select Install -> Locate and choose lineage-17.1-2022XXXX-UNOFFICIAL-satsuki.zip file -> Swipe to confirm flash.
However, after step 2, I had to leave TWRP , and now when I try to boot TWRP again I just get the frozen splash screen.
I have tried flashing different versions of TWRP (3.3, 3.5 & 3.6), but they all act the same.
I did find one suggestion, to use 'fastboot -w', which didn't throw up an error, but made no difference.
I have no system now either, so I would seem to be up a creek without a paddle ....
Any help would be very much appreciated.
chipsxda said:
Here's my story.
I successfully installed TWRP followed by LineageOS-19.1 (Android 12) on my Z5 Premium Dual (E6833), but after realising that the camera didn't work, I decided to try LineageOS-17.1 (Android 10).
I was following the install script on this thread ...
Xperia Z5 Premium Android Development
Android development for the Sony Xperia Z5 Premium
forum.xda-developers.com
1) Reboot into TWRP Recovery.
2) Select Wipe -> Swipe to factory reset -> Advanced Wipe -> Dalvik /ART Cache, System, Cache and Data -> Swipe to Wipe.
3) Go back to TWRP's main menu -> Select Install -> Locate and choose lineage-17.1-2022XXXX-UNOFFICIAL-satsuki.zip file -> Swipe to confirm flash.
However, after step 2, I had to leave TWRP , and now when I try to boot TWRP again I just get the frozen splash screen.
I have tried flashing different versions of TWRP (3.3, 3.5 & 3.6), but they all act the same.
I did find one suggestion, to use 'fastboot -w', which didn't throw up an error, but made no difference.
I have no system now either, so I would seem to be up a creek without a paddle ....
Any help would be very much appreciated.
Click to expand...
Click to collapse
I fixed this myself, by doing the following ....
1. Downloaded and installed the Emma flash tool from the Sony website on my Windows 10 PC.
2. Attached my phone to Windows PC, and run the latest of the recommended services, which restored my phone with Android 6.
After this I still had a problem, because although I could boot directly to TWRP using ADB fastboot, I couldn't boot to Recovery (where I had also installed TWRP).
To fix this, I did the following ....
1. Downloaded and installed the ReiBoot for Android utility to my Windows PC.
2. Attached my phone and run the Recovery mode repair option.
After this, I could reboot into Recovery and run TWRP.
Then successfully installed LineageOS-17.1 on my phone, along with Gapps and Magisk, which I still find bl**dy confusing by the way..... but that's another story ....