Database Info

Flashed wrong boot file

Hi Well I had this big problem and I was close to solving it until i messed things up, I tried to not ask for help here but it's been a week and I can't find anything ): My g925p is just useless right now. I hope you can help me
Short version
Using Twrp I picked the efs.img to flash it and I didn't see it had two options ( Boot, recovery ) It's on boot by default so I guess the file flashed as boot and now everytime i turn the phone on it goes directly to download screen ( for odin ) ... I think if someone can make a backup of their boot.img file and upload it somewhere i could flash it and then everything would be back to normal ? At least boot into the rom .-. Thanks for your time !
By the way, When I try to transfer files via sideload twrp tells me i need a higher version for that device, And I have the latest version .-. Thank you guys
Long version
It all started when I tried to flash twrp with flashify, I guess i flashed a wrong version and my phone got stuck on a bootloop, I fixed it by installing the latest version of twrp and factory reset, But then it got into a bootloop in the initial setup, So I decided to Flash a light rom and it worked ! but it wouldn't connect to data, Before I had this problem I backed up esf.img and I thought it would restore connection, But then ... ( Continue in short version B) )
Thanks you so much for reading guys !

Download and install the firmware via odin that should fix your problem

dhonzik said:
Download and install the firmware via odin that should fix your problem
Click to expand...
Click to collapse
That was the first thing I tried but Odin would give me the nand write error, And googling People would just say " Try different cable, different usb port, your nand is burned and you need to replace it " I did the two first things but the second, Well I succeded flashing a rom through twrp so i dont thing there's something wrong with it.
Thanks for the answer tho.

Help: I accidentally flashed TWRP to boot, not recovery.

I accidentally flashed TWRP to my boot partition, not my recovery partition. I googled how to flash stuff, and alas, googled wrong. I used the thread on this forum to get the twrp and SuperSU.zip.
Now when I boot my phone, I get the TeamWin TWRP, not my OS.
What should I do next?
Is there a way to get the original boot.img for the phone?
Thanks!

Did you tried to flash that http://forum.xda-developers.com/showpost.php?p=64250021&postcount=163 OR http://forum.xda-developers.com/showpost.php?p=64253022&postcount=166 that?

He fixed by flashing the BLU_BOOT_0.img from my post 163.

ShanethP said:
I accidentally flashed TWRP to my boot partition, not my recovery partition. I googled how to flash stuff, and alas, googled wrong. I used the thread on this forum to get the twrp and SuperSU.zip.
Now when I boot my phone, I get the TeamWin TWRP, not my OS.
What should I do next?
Is there a way to get the original boot.img for the phone?
Thanks!
Click to expand...
Click to collapse
Can you please post how you fixed this problem. I am currently having the exact same problem. I am at a loss on how to fix it. This is the first post I found that is the exact same problem I am having. Unfortunately I did not download the twrp and SuperSU by accident.

acheron1502 said:
He fixed by flashing the BLU_BOOT_0.img from my post 163.
Click to expand...
Click to collapse
Can you post a link to the post 163 you mentioned please.

BabySquee said:
Can you post a link to the post 163 you mentioned please.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pure-xl/help/guide-unbrick-softbricked-blu-pure-xl-t3371981
1. read the thread (Yes I know its LONG)
2. learn to use SP Flash Tool
3. ????
4. Profit
https://forum.xda-developers.com/showpost.php?p=66747073&postcount=51

That is exactly what I did. Thank you @tbirdguy. BTW I have come to love SP Flash Tool.

I too accidentally flashed TWRP to boot. I solved it by pressing on wipe and then performing a factory reset. Then, I connected my phone to my PC and copied boot.img onto my phone. When it finished copying, I pressed on install in the TWRP home screen, pressed on the img button and selected the boot.img that I copied over. When it was done flashing, I rebooted my phone. I thought I had ended up just bricking my phone, but after a couple minutes my phone went to the setup screen.
boot.img for Nexus and Pixel-developers.google.com/android/images

Hanging during Boot animation

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!

How To Successfully Install Twrp For G7 Play

Im Pretty Sure Everyone that will read this thread will have an unlocked bootloader.
Requirments: an Unlocked Bootloader. A PC. And Some Knowledge about Android Coustomization.
So for twrp to boot Correctly Your Going to need a modified dtbo image with out it your going to have twrp boot into a black screen with minimal file transfer capabilities
The DTBO image i use is This One
https://drive.google.com/file/d/1pV6-LbNoMG0J8vcyAWN0QWYGx67vxBgT/view?usp=sharing
next your going to need a twrp thats stable i suggest this one
https://drive.google.com/file/d/13MROGlEA_TdgHFTaiqOswo4w0NgXhGbx/view?usp=sharing
now that you have the files
first hold power and volume up till you see a black screen with text saying fastboot flash mode
now we are going to get the recovery installed by running two commands in fastboot
first command fastboot flash dtbo /path/to/yours.img
run the next command fastboot boot twrp4.img
now you should see the twrp recovery splash screen
now we are going to go to mount this will pop up a file transfer window on your pc
drag twrp4.img to a directory you know where its at
backout of mount and go to install
select the directory where your twrp4.img is at
then click install image
it should show you that twrp is there click on twrp4.img
select install to recovery ramdisk
swipe to confirm flash
wait till its done then click back
go to advanced click fix recovery bootloop
swipe to confirm
then go back click reboot
select recovery
you can unplug your phone now
and you will see twrp is now installed on your device
click reboot select poweroff
hold volume down and power untill you see that text again from fastboot
this time use volume up to scroll through your options untill you find recovery mode then press power
you will be booted into twrp do that for when ever you need to access your recovery
hope this tutorial helps
and thanks to spaceminer for making this twrp
and thanks to scritch007 for modifing the dtbo img

it doesnt work we need a flashable.zip method
---------- Post added at 07:35 AM ---------- Previous post was at 07:11 AM ----------
must add must wipe data first , flash disable verity.zip will post , then install recovery to ramdisk after copying it to the sdcard , didnt click fix recovery bootloop and it works perfectly fine

thenatti said:
it doesnt work we need a flashable.zip method
---------- Post added at 07:35 AM ---------- Previous post was at 07:11 AM ----------
must add must wipe data first , flash disable verity.zip will post , then install recovery to ramdisk after copying it to the sdcard , didnt click fix recovery bootloop and it works perfectly fine
Click to expand...
Click to collapse
flash this after format data , then follow steps mentioned above , thank you everyone for your hardwork on bringing us a stable release

thenatti said:
flash this after format data , then follow steps mentioned above , thank you everyone for your hardwork on bringing us a stable release
Click to expand...
Click to collapse
Yeah I forgot to put the decryptor zip in the tutorial
I did use it tho ill edit the tutorial in a few

Linuxassassin said:
Yeah I forgot to put the decryptor zip in the tutorial
I did use it tho ill edit the tutorial in a few
Click to expand...
Click to collapse
I noticed with stock firmware it boot loops I'm currently running the dot os treble image and it's consistent , but not with stock unless there is no data ,.but when data is created it boot loops , I recommend flashing the treble gsi image , the only bug is no proper notch support and I don't have a Linux but to attempt to create an overlay

thenatti said:
I noticed with stock firmware it boot loops I'm currently running the dot os treble image and it's consistent , but not with stock unless there is no data ,.but when data is created it boot loops , I recommend flashing the treble gsi image , the only bug is no proper notch support and I don't have a Linux but to attempt to create an overlay
Click to expand...
Click to collapse
the notch is
the notch isnt terible to be honest also to flash gapps get the device id apk will help you certify your device to be able to install stuff from the google play store

Well. The touchscreen is not working for me. But I think is because I am on 1952-1.

Savinu' said:
Well. The touchscreen is not working for me. But I think is because I am on 1952-1.
Click to expand...
Click to collapse
what slot are you on

Linuxassassin said:
what slot are you on
Click to expand...
Click to collapse
On slot a

thenatti said:
flash this after format data , then follow steps mentioned above , thank you everyone for your hardwork on bringing us a stable release
Click to expand...
Click to collapse
Can you tell me the right how should I flash this zip? I'm new to TWRP and Magisk, and I'm trying to get root for my G7 Play. I know there is the sideload flashing from ADB and the install update option in stock recovery, but I don't know if one of them is the way to flash it or if it's a way that I don't know.
Thanks in advance

on my moto g7 play xt1952-2 the touchscreen stopped how to solve?

great job
big thank you to all that had a hand in getting a working twrp for the g7 play!!! it worked perfectly the first time i did it

Fails to install twrp to recovery ramdisk
Hi!
I've tried to follow the guide but somehow I fail to install the twrp image to the recovery ramdisk.
When updating partition details, it fails to mount '/vendor' (invalid argument)
Then when it tries to backing up the boot it fails:
cd /tmp/repackorig/ && /sbin/magiskboot --unpack -h '/tmp/repackorig/boot.img' process ended with Error 1. Error unpacking image.
Any suggestions to solve this?
Output from recovery.log
[IMAGE FLASH STARTED]
Image to flash: '/sdcard/twrp4.img'
Unpacking Boot...
Backing up Boot...
I:Reading '/dev/block/bootdevice/by-name/boot_b', writing '/tmp/repackorig//boot.emmc.win'
I:Restored default metadata for /tmp/repackorig//boot.emmc.win
Parsing boot image: [/tmp/repackorig/boot.img]
cd /tmp/repackorig/ && /sbin/magiskboot --unpack -h '/tmp/repackorig/boot.img' process ended with ERROR: 1
I:Error unpacking /tmp/repackorig/boot.img!
Error unpacking image.
I:Set page: 'action_complete'
Iperation_end - status=1

Got stuck trying to follow the above recipe as it hasn't yet been edited to include the additional details about for example the no-verity thing... Would appreciate an update. Thx.

There's a new build that should work on all models including RETUS. You guys can find that here. It has /vendor & /oem backup and restore but they're untested. I do need some help with it if anyone here is savvy enough. In it's current state, it bootloops with the stock OS installed. But not when a GSI is installed. The recovery loop fix in twrp doesn't work, and I'm not sure how to make it work.

need help
i can boot to twrp using fastboot but any other time it just flashes and wont load plz help also i dont have root just saying

Spaceminer said:
There's a new build that should work on all models including RETUS. You guys can find that here. It has /vendor & /oem backup and restore but they're untested. I do need some help with it if anyone here is savvy enough. In it's current state, it bootloops with the stock OS installed. But not when a GSI is installed. The recovery loop fix in twrp doesn't work, and I'm not sure how to make it work.
Click to expand...
Click to collapse
I'm pretty sure I've sussed it out.
I noticed that G7 River has an extra step.. once TWRP in ramdisk and also bootloop fix ran...
They use https://dl.twrp.me/river/twrp-installer-3.3.1-2-river.zip.html
So , Hope you don't mind, I unpacked your TWRP and exchanged the ramdisk-trwp.cpio in the river zip with yours.
Flashed it after the bootloop fix and it installs to boot a and b.
I then formatted data, installed latest canary magisk manager zip
then no verity from here
it's succesfully rebooted to setup (as I formatted data obviously) .... now to go through setup... but the fact it's got this far looks good

CFKod said:
I'm pretty sure I've sussed it out.
I noticed that G7 River has an extra step.. once TWRP in ramdisk and also bootloop fix ran...
They use https://dl.twrp.me/river/twrp-installer-3.3.1-2-river.zip.html
So , Hope you don't mind, I unpacked your TWRP and exchanged the ramdisk-trwp.cpio in the river zip with yours.
Flashed it after the bootloop fix and it installs to boot a and b.
I then formatted data, installed latest canary magisk manager zip
then no verity from here
it's succesfully rebooted to setup (as I formatted data obviously) .... now to go through setup... but the fact it's got this far looks good
Click to expand...
Click to collapse
I'm not upset at all, if anything I am very pleased. Nice work!

Man so close but still not quite. Installed magisk manager but no root...
When I reboot to Twrp it shows the two front screen but then starts having a seizure flashing n ****....... Works to fastboot into the IMG again...
So close.. ummmm

CFKod said:
Man so close but still not quite. Installed magisk manager but no root...
When I reboot to Twrp it shows the two front screen but then starts having a seizure flashing n ****....... Works to fastboot into the IMG again...
So close.. ummmm
Click to expand...
Click to collapse
Try dumping the boot.img after you've done everything to install twrp, then manually patch it with magisk, and flash it with fastboot.

Problem with flashing custom ROM (error 255)

Hey guys,
after searching through different websites and guides you are my last resort to get a custom ROM running on my Redmi S2.
Everytime i try to flash a custom ROM i get the error 255. Here is what i tried until now (bootloader is unlocked):
- flashing twrp(twrp-3.2.1-0-ysl) to recovery using fastboot
- wiping phone (first wipe to disable encryption since miui puts some kind of password on the hard drive that i dont know, second wipe to ensure partitions are clean for new OS)
- mounting phone to pc to transfer OS image (tried Lineage and Havoc, both modified for S2 (ysl version)) and GApps
- finally, installing OS zip (after which i get error message 255, telling me that twrp wasnt able to install the zip file)
please help me out, ask away if something's not clear

flying_shitnugget said:
Hey guys,
after searching through different websites and guides you are my last resort to get a custom ROM running on my Redmi S2.
Everytime i try to flash a custom ROM i get the error 255. Here is what i tried until now (bootloader is unlocked):
- flashing twrp(twrp-3.2.1-0-ysl) to recovery using fastboot
- wiping phone (first wipe to disable encryption since miui puts some kind of password on the hard drive that i dont know, second wipe to ensure partitions are clean for new OS)
- mounting phone to pc to transfer OS image (tried Lineage and Havoc, both modified for S2 (ysl version)) and GApps
- finally, installing OS zip (after which i get error message 255, telling me that twrp wasnt able to install the zip file)
please help me out, ask away if something's not clear
Click to expand...
Click to collapse
change your recovery..

Baim alif said:
change your recovery..
Click to expand...
Click to collapse
Mind elaborating? What do you mean exactly?

flying_shitnugget said:
Mind elaborating? What do you mean exactly?
Click to expand...
Click to collapse
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip

Baim alif said:
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip
Click to expand...
Click to collapse
so... i first tried taking the recovery.img out of the zip and flashing it via fastboot, didnt worked. after that i tried first flashing my old twrp and then (after wiping) installing the whole zip. the install finished successfully, sayed it will restart to recovery in 5 seconds... aaaand got stuck on the android screen. now it wont boot to recovery at all anymore, unless i flash the old twrp again. suggestions?

flying_shitnugget said:
so... i first tried taking the recovery.img out of the zip and flashing it via fastboot, didnt worked. after that i tried first flashing my old twrp and then (after wiping) installing the whole zip. the install finished successfully, sayed it will restart to recovery in 5 seconds... aaaand got stuck on the android screen. now it wont boot to recovery at all anymore, unless i flash the old twrp again. suggestions?
Click to expand...
Click to collapse
try to boot recovery with power button and volume up

Baim alif said:
try to boot recovery with power button and volume up
Click to expand...
Click to collapse
yes, that's what i did. i also tried booting into from fastboot and still nothing.

flying_shitnugget said:
yes, that's what i did. i also tried booting into from fastboot and still nothing.
Click to expand...
Click to collapse
hmmm... try this bro..
https://androidfilehost.com/?fid=6006931924117927913

flying_shitnugget said:
yes, that's what i did. i also tried booting into from fastboot and still nothing.
Click to expand...
Click to collapse
Try this, you have to flash first this in fastboot https://files.orangefox.download/OrangeFox-Beta/ysl/ the R10.0-1 RC1 .img file
And THEN flash this https://orangefox.download/en/device/ysl once you are in the recovery.
Then it worked for me, finally, hope this helps.

celephrn said:
Try this, you have to flash first this in fastboot https://files.orangefox.download/OrangeFox-Beta/ysl/ the R10.0-1 RC1 .img file
And THEN flash this https://orangefox.download/en/device/ysl once you are in the recovery.
Then it worked for me, finally, hope this helps.
Click to expand...
Click to collapse
so i tried this approach. i first installed how you told me to (orangefox R10.0-1 RC1 .img first), but factory reset nor installing the second recovery img worked because of the encryption miui puts on the phone. So i flashed twrp, wiped memory, flashed first orange fox img and from then installed the second img (as a zip). until here everything worked, orange fox told me that he's going to reboot to new recovery -- and i got stuck on the boot logo again. :c

flying_shitnugget said:
so i tried this approach. i first installed how you told me to (orangefox R10.0-1 RC1 .img first), but factory reset nor installing the second recovery img worked because of the encryption miui puts on the phone. So i flashed twrp, wiped memory, flashed first orange fox img and from then installed the second img (as a zip). until here everything worked, orange fox told me that he's going to reboot to new recovery -- and i got stuck on the boot logo again. :c
Click to expand...
Click to collapse
Did you flash the firmware? https://github.com/XiaomiFirmwareUpdater/firmware_xiaomi_ysl/releases/tag/stable-16.03.2020
Other thing you could try is flash the other .img files from https://files.orangefox.download/OrangeFox-Beta/ysl/ and the flash in there the same .zip file you did as before.

celephrn said:
Did you flash the firmware? https://github.com/XiaomiFirmwareUpdater/firmware_xiaomi_ysl/releases/tag/stable-16.03.2020
Other thing you could try is flash the other .img files from https://files.orangefox.download/OrangeFox-Beta/ysl/ and the flash in there the same .zip file you did as before.
Click to expand...
Click to collapse
im currently on MIUI V.10.3.1.0.OEFMIXM | Stable 654M, is it important to flash newer firmware?

flying_shitnugget said:
im currently on MIUI V.10.3.1.0.OEFMIXM | Stable 654M, is it important to flash newer firmware?
Click to expand...
Click to collapse
Could solve the issue, I'd give it a shot!

celephrn said:
Could solve the issue, I'd give it a shot!
Click to expand...
Click to collapse
i suppose you flash it using MiFlash right? If so, i have a problem with flashing new roms using it because my Mi account isnt allowed to do that, i unlocked the bootloader using a tool (dont know if this has something to do with the custom rom problem)

flying_shitnugget said:
i suppose you flash it using MiFlash right? If so, i have a problem with flashing new roms using it because my Mi account isnt allowed to do that, i unlocked the bootloader using a tool (dont know if this has something to do with the custom rom problem)
Click to expand...
Click to collapse
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.

celephrn said:
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.
Click to expand...
Click to collapse
so i flashed the firmware as you said, now neither orangefox or twrp throw me the error "unable to locate storage device", i cant mount the storage to the pc and cant copy the custom rom stuff as well

celephrn said:
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.
Click to expand...
Click to collapse
UPDATE: i finally ****ing did it. So here are the steps that i took (incase anyone has to go through this **** as well)
1. flash MIUI on mobile device using MiFlash (at least i did this by shorting 2 pins on the back)
2. (VERY IMPORTANT!!!) instantly boot to fastboot using Power button + Volume down. this has to be before android starts setting up the phone
3. flash recovery with the image that celephrn provided in this thread
4.boot to recovery by holding Volume up + Power button
5. install the miui update that celephrn provided in this thread
6. reboot to recovery
7. install orange recovery zip that celephrn provided in this thread (phone reboots to recovery)
8. now you can reboot to system (Do NOT (!!!) set the phone up, just let it work its things until you see the MIUI setup screen)
9. Now, finally you can dirty flash your custom rom (and GApps)
10. after flashing the new rom android will throw you alot of errors so you will have to wipe Dalvik/Cache, System, Data and Internal Storage.
11. now you can flash your Rom clean and you're good to go
(huge thanks to celephrn, helped me out after me struggling for a few good weeks with this damn phone)

Baim alif said:
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip
Click to expand...
Click to collapse
bro please help me i have the same issue error 255 on 3.2.1-0 ysl twrp.please help

Farrellclay said:
bro please help me i have the same issue error 255 on 3.2.1-0 ysl twrp.please help
Click to expand...
Click to collapse
so far, what have you done