Related
Hello,i accidentally deleted my operating system,i tried everything to flash a new one ,every custom roms out there.
The TWRP version is 2.5.0.0
Everytime i execute the ZIP files from TWRP errors appear :
Error flashing zip '/sdcard/BackToBasicsV2.zip'
Error executing updater binary in zip : 'sdcard/BackToBasics'
Could you provide me a working tutorial?I tried every tutorial from here and nothing worked,i don't know what to do anymore.
I had a similar problem in which I accidentally pressed factory reset in bootloader instead of recovery (WHY ARE THEY SO CLOSE?!). Anyway, I ended up having to factory reset from recovery and wipe everything on my phone, then I adb pushed a rom to my phone and it finally let me flash it. Although I recommend waiting until someone else posts something as this is more of a "last resort" lol
S1mpleR said:
Hello,i accidentally deleted my operating system,i tried everything to flash a new one ,every custom roms out there.
The TWRP version is 2.5.0.0
Everytime i execute the ZIP files from TWRP errors appear :
Error flashing zip '/sdcard/BackToBasicsV2.zip'
Error executing updater binary in zip : 'sdcard/BackToBasics'
Could you provide me a working tutorial?I tried every tutorial from here and nothing worked,i don't know what to do anymore.
Click to expand...
Click to collapse
Connect your phone to your PC find it in devices and format it... Download twrp 2.3.3 recovery image and install it with fast boot.. Then paste a ROM to your SD card and flash away NP...don't forget the boot.IMG when flashing your new ROM it will have to be flashed with fast boot also..
Sent from my One S using xda premium
Still not working,anyone please,any other ideas?
I had pixel experience rom installed and tried to flash the new update when it showed error 7. Anyways, trying to fix it, i decided to wipe and install fresh rom. But when i try to boot to recovery now, the twrp opening screen comes up and instead of going into recovery menu, goes into boot loop. Tried flashing dummy img and flashing new twrp img too but same result. Tried booting to recovery using fastboot boot twrp.img too still same result.
btw device is redmi note 5 pro
[email protected] said:
I had pixel experience rom installed and tried to flash the new update when it showed error 7. Anyways, trying to fix it, i decided to wipe and install fresh rom. But when i try to boot to recovery now, the twrp opening screen comes up and instead of going into recovery menu, goes into boot loop. Tried flashing dummy img and flashing new twrp img too but same result. Tried booting to recovery using fastboot boot twrp.img too still same result.
btw device is redmi note 5 pro
Click to expand...
Click to collapse
Try reinstalling the stock ROM, it'll delete any modification brought to the device...
Hello!
I tried installing TWRP which i successfully did (I was planning to install a custom rom) but then I delete everything on wipe section these are:
•Dalvik
•Cache
•Vendor
•Data
After wiping these, I accidentally turned off the phone and now it can't boot to recovery and says "The system has been destroyed". Good thing is I can still go into fastboot mode.
I tried flashing stock MIUI ROM but it keeps getting error on MiFlash. I can confirm the bootloader is unlocked and I also tried other ROMs but I feel like the phone won't accept it.
I keep getting error whenever I flash even if I use original China ROM.
I know messed it up but please.....
Please save my poor phone.
kiyu07 said:
Hello!
I tried installing TWRP which i successfully did (I was planning to install a custom rom) but then I delete everything on wipe section these are:
•Dalvik
•Cache
•Vendor
•Data
After wiping these, I accidentally turned off the phone and now it can't boot to recovery and says "The system has been destroyed". Good thing is I can still go into fastboot mode.
I tried flashing stock MIUI ROM but it keeps getting error on MiFlash. I can confirm the bootloader is unlocked and I also tried other ROMs but I feel like the phone won't accept it.
I keep getting error whenever I flash even if I use original China ROM.
I know messed it up but please.....
Please save my poor phone.
Click to expand...
Click to collapse
which error r u getting
kiyu07 said:
Hello!
I tried installing TWRP which i successfully did (I was planning to install a custom rom) but then I delete everything on wipe section these are:
•Dalvik
•Cache
•Vendor
•Data
...
Click to expand...
Click to collapse
1. The real error is not turning off the phone. The real error is wiping Vendor. Why on earth would you want to do that? You should never wipe vendor manually. If you just wiped data and dalvik/cache (which is all that you should wipe) you could turn off your phone one thousand times, and the ROM would still boot when you turn on the phone again.
2. You say you tried flashing stock MIUI - but you have not indicated which kind of stock MIUI you have tried flashing (ie, are you trying to flash a fastboot ROM or a zip?).
3. What error are you getting from Mi Flash?
DarthJabba9 said:
1. The real error is not turning off the phone. The real error is wiping Vendor. Why on earth would you want to do that? You should never wipe vendor manually. If you just wiped data and dalvik/cache (which is all that you should wipe) you could turn off your phone one thousand times, and the ROM would still boot when you turn on the phone again.
2. You say you tried flashing stock MIUI - but you have not indicated which kind of stock MIUI you have tried flashing (ie, are you trying to flash a fastboot ROM or a zip?).
3. What error are you getting from Mi Flash?
Click to expand...
Click to collapse
How can he flash a custom rom without wiping vendor???
Sourab debnath said:
How can he flash a custom rom without wiping vendor???
Click to expand...
Click to collapse
Easily. Each ROM will flash its own vendor. The process of flashing to the partition involves wiping the partition and then immediately flashing. So, there is absolutely no point in wiping vendor manually. On the contrary, you can already see the pitfalls of doing so (a similar situation will occur if the new ROM that you want to flash doesn't flash its own vendor - lots of tears!!).
you should try flashing again twrp and then flash the miui zip...
thank you for all the help. got it fixed by using miflashpro, the normal one doesn't flash anything on my phone. i got the stock rom flashed then i was able to get twrp and PE10 working!
kiyu07 said:
Hello!
I tried installing TWRP which i successfully did (I was planning to install a custom rom) but then I delete everything on wipe section these are:
•Dalvik
•Cache
•Vendor
•Data
After wiping these, I accidentally turned off the phone and now it can't boot to recovery and says "The system has been destroyed". Good thing is I can still go into fastboot mode.
I tried flashing stock MIUI ROM but it keeps getting error on MiFlash. I can confirm the bootloader is unlocked and I also tried other ROMs but I feel like the phone won't accept it.
I keep getting error whenever I flash even if I use original China ROM.
I know messed it up but please.....
Please save my poor phone.
Click to expand...
Click to collapse
We'll need one tar or fastboot file of miui extract it and place it in c drive under folder name note 7 pro then again go in fastboot mode open mi flash tools search for the same then no error whole process of flashing will take 10 to 15 minutes once done will reboot your phone immediately and will sure work I messed. Up my device 100 times went to Xiaomi service centre many times but due to their errogance I came back did it myself no issues it's easy but you have to try
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
My realme gt neo2 is stuck on bootloop, already tried OFP Flash but nothing, still stuck.
update --
I have managed to get back to realme ui recovery, but not even if I format data, still on fastboot
is it on bootloop or just constantly restarting to fastboot? try flashing the stock rom with the twrp flashable stock rom firmware.
rafaelpcosta said:
is it on bootloop or just constantly restarting to fastboot? try flashing the stock rom with the twrp flashable stock rom firmware.
Click to expand...
Click to collapse
If I start the device, it goes on fastboot, if I click recovery it goes on rui recovery mode, but even if I format data and restart it does the same (start on fastboot)
Lucxq said:
If I start the device, it goes on fastboot, if I click recovery it goes on rui recovery mode, but even if I format data and restart it does the same (start on fastboot)
Click to expand...
Click to collapse
Flash twrp via fastboot and flashable stock rom from twrp.
Alexj7 said:
Flash twrp via fastboot and flashable stock rom from twrp.
Click to expand...
Click to collapse
already did, still nothing..
hi, i have mine since two days.
1. unlock bootloader
2. boot in twrp with "fastboot boot recovery.img"
3. install twrp by press "install -> image install"
4. install magisk in trwp et boot the stock rom
5. restart in twrp and install elixir..A13...
6. reboot the phone with result of touch screen not responding
7. 8. 9. ....... try format Data, change twrp version, flash other rom with no succes.
Now i'm on elixir[A13] and will give a try at arrowsOS.
my solution if it can help you:
1. go here: https://forum.xda-developers.com/t/...-realme-gt-neo-2-bitra-fastboot-mode.4399223/
and try to remember whaat was the last android version you had on your phone.
2. download it and flash it with the little application, if it failed or stuck on "flashing ..." WAIT first 10min, disconnect your phone and reflash it with same method (i flash it three time and no one go to the end).
3. reboot your phone and if you're lucky, you can enter in.
4. make all updates for your android version
5. when you will be on rui3.0, you can remade the first step for playing with bootloader, recovery and recent custom rom.
hope it help you...
soory for my english
sanzostef said:
hi, i have mine since two days.
1. unlock bootloader
2. boot in twrp with "fastboot boot recovery.img"
3. install twrp by press "install -> image install"
4. install magisk in trwp et boot the stock rom
5. restart in twrp and install elixir..A13...
6. reboot the phone with result of touch screen not responding
7. 8. 9. ....... try format Data, change twrp version, flash other rom with no succes.
Now i'm on elixir[A13] and will give a try at arrowsOS.
my solution if it can help you:
1. go here: https://forum.xda-developers.com/t/...-realme-gt-neo-2-bitra-fastboot-mode.4399223/
and try to remember whaat was the last android version you had on your phone.
2. download it and flash it with the little application, if it failed or stuck on "flashing ..." WAIT first 10min, disconnect your phone and reflash it with same method (i flash it three time and no one go to the end).
3. reboot your phone and if you're lucky, you can enter in.
4. make all updates for your android version
5. when you will be on rui3.0, you can remade the first step for playing with bootloader, recovery and recent custom rom.
hope it help you...
soory for my english
Click to expand...
Click to collapse
Hi!
I fixed the problem by using a OFP flash tool
The only thing that I have to do now is to upgrade the version of android (from 11 to 13)
Thanks for the reply tho!
Lucxq said:
Hi!
I fixed the problem by using a OFP flash tool
The only thing that I have to do now is to upgrade the version of android (from 11 to 13)
Thanks for the reply tho!
Click to expand...
Click to collapse
you're welcome, yesterday i cry about my two days phone so if that can help. and yes OFP is the link i post in my answer.
sanzostef said:
hi, i have mine since two days.
1. unlock bootloader
2. boot in twrp with "fastboot boot recovery.img"
3. install twrp by press "install -> image install"
4. install magisk in trwp et boot the stock rom
5. restart in twrp and install elixir..A13...
6. reboot the phone with result of touch screen not responding
7. 8. 9. ....... try format Data, change twrp version, flash other rom with no succes.
Now i'm on elixir[A13] and will give a try at arrowsOS.
my solution if it can help you:
1. go here: https://forum.xda-developers.com/t/...-realme-gt-neo-2-bitra-fastboot-mode.4399223/
and try to remember whaat was the last android version you had on your phone.
2. download it and flash it with the little application, if it failed or stuck on "flashing ..." WAIT first 10min, disconnect your phone and reflash it with same method (i flash it three time and no one go to the end).
3. reboot your phone and if you're lucky, you can enter in.
4. make all updates for your android version
5. when you will be on rui3.0, you can remade the first step for playing with bootloader, recovery and recent custom rom.
hope it help you...
soory for my english
Click to expand...
Click to collapse
there is one stock rom firmware that gives that problem, at least that's what happened to me previously or also when touch did not work it was when flashed custom rom on wrong firmware version, let's say rom required rui 3 c05 but I used rui 3 c07 which caused problems.
rafaelpcosta said:
there is one stock rom firmware that gives that problem, at least that's what happened to me previously or also when touch did not work it was when flashed custom rom on wrong firmware version, let's say rom required rui 3 c05 but I used rui 3 c07 which caused problems.
Click to expand...
Click to collapse
exactly. not really the first time for me. it can append when your recovery is out of date also.
i'm not a dev but interresting with for long year and i think flashing rom don't errase all that why we always need to flash custom rom according to our android version.