Related
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Same boat. No SIM
No SIM card detected here as well after the 123015 update. I am not using the custom kernel nor was I in airplane mode when I flashed.
Tried rebooting a couple times. Removed SIM card and replaced. Couldn't get it to recognize.
Same problem here with the 123015 update. Reverting to old roms did not work.
just use search ...
you probably use twrp 2.8.6.1 or greater, so new modem firmware in 30/12 nightly is not updated correctly, if you use cm, use cm recovery too or twrp 2.8.6.0! and update rom again
reflash old firmware and it will be back.
its a combination of bad luck and bad flash on the recovery you are using.
use twrp 2.8.7.6.0.
That one is not prone to bad flashes of firmware
no need to restore efs cause the bad flash can be corrected
Sent from my A0001 using Tapatalk
Startlinger said:
reflash old firmware and it will be back.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Where do I find the 'old firmware'
deleted
just back to 29/12 nightly, flash correct recovery and again flash 30/12
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
twrp-2.8.6.0
NoSyt15 said:
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
Click to expand...
Click to collapse
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Sent from my A0001 using Tapatalk
fronzinator said:
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Click to expand...
Click to collapse
Use 2.8.6.0 of twrp to update modem
Startlinger said:
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Click to expand...
Click to collapse
I restored my twrp to 2.8.6.0 (after wiping the entire phone previously... urgh), and then flashed the latest nightly. Everything worked again!
I ended up going back to my CM12.1 backup as the TrueCaller CM app keeps crashing in CM13. I could just keep the stock dialer, but I have grown accustomed to knowing who's calling me!
Thanks for your help all!
I get this issue as well.
IVIatty said:
I get this issue as well.
Click to expand...
Click to collapse
ok, thanks for informing us.
bastard79 said:
ok, thanks for informing us.
Click to expand...
Click to collapse
Thank your for thanking him for informing us
Sent from my A0001 using Tapatalk
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Startlinger said:
use twrp 2.8.7.6.0.
Click to expand...
Click to collapse
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
¿GotJazz? said:
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
Click to expand...
Click to collapse
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Startlinger said:
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Hi, @Startlinger - I've downloaded twrp-2.8.6.0-bacon.img with three different browsers (Chrome, MS IE, and Firefox). All three images acted the same way: They all matched the MD5 posted on TWRP, and they were all unbootable (either by flashing, or with a fastboot boot twrp-2.8.6.0-bacon.img command). I couldn't download the image to the phone via the internet, because I can't get an internet connection on my OPO anymore - probably because the modem is corrupted. I did copying one of the computer-downloaded 2.8.6.0 images to the phone, and tried flashing the image through TWRP 2.8.7.0, but the results were exactly the same ... it wouldn't boot into Recovery Mode after that.
Is the f69fa503419644851822d883c2388bb8 MD5 value correct? (I suspect it is)
One thing I've noticed is that I can't just power-off my phone anymore when 2.8.6.0 is loaded. If I try to power off, it comes back up in Normal Mode. This may be related to the corrupted 2.8.6.0 Recovery Mode.
Update: I've also noticed something else - I tried doing a fastboot boot twrp-image-file with other versions of TWRP (2.84.1 and 2.8.5.1). None of these boot into Recovery Mode - just the 2.8.7.0 image works.
Is there something else I need to recover on my phone (if it's even possible)? Is there any other way I can reinstall a workable Lollipop 5.0.2 Modem Image onto the phone?
well, thats a first gotjazz.
I would recommend 2.8.7.05 from here https://www.androidfilehost.com/?fid=24269982087010524
if same results, perhaps best to download latest fastboot rom from cyanogen. Then fastboot your way back to a complete stock situation. Before doing so wipe everything in 2.8.7.0, and repair all partitions that allow repairing.
when fastbooting everything take care in using the 64 if you got 64 gb
After let it boot, check if you can get reception. If that works, fastboot flash recovery of 2.8.6.0. or 2.8.7.05 and go back to whatever rom you want
Sent from my A0001 using Tapatalk
Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda
audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.
kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/
Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...
Hi !
I installed TWRP to root my honor view 10 3/4 weeks ago.
Today I installed an update. And since then, the phone won't boot past TWRP (which I can access) or Huawei eRecovery mode.
When I land in the eRecovery mode it offers me to shutdown, reboot, or connect to wifi and do a factory reset. When I attempt the factory reset it tells me that downloading package info failed.
I tried to do a reset from TWRP without success gives me ERROR 9. I also tired to install the stock rom (update.zip) from TWRP and I also get ERROR 9.
I'm a complete noob when it comes to phones. Anyone have an idea of a solution ?
Thank you for reading !
Get a microsd card flash Dload file
aditya desai said:
Get a microsd card flash Dload file
Click to expand...
Click to collapse
Tried and it tells me system installation failed, maybe I have the wrong file ?
Thanks for your help!
ouamakavoula said:
Tried and it tells me system installation failed, maybe I have the wrong file ?
Thanks for your help!
Click to expand...
Click to collapse
Whats your model, if it is L09 then get the stock ramdisk image from magisk thread in development section and also search for recovery image. Flash it via fastboot and boot normally.
Never ever try ota on rooted phone.
shashank1320 said:
Whats your model, if it is L09 then get the stock ramdisk image from magisk thread in development section and also search for recovery image. Flash it via fastboot and boot normally.
Never ever try ota on rooted phone.
Click to expand...
Click to collapse
My model is L09, I flashed the stock ramdisk image and now I can no longer get into TWRP but I am unsure of what to do now ?
Thanks
ouamakavoula said:
My model is L09, I flashed the stock ramdisk image and now I can no longer get into TWRP but I am unsure of what to do now ?
Thanks
Click to expand...
Click to collapse
Able to boot to system now? You cam always flash twrp from fastboot. Avoid as of now and boot to stock rom first
shashank1320 said:
Able to boot to system now? You cam always flash twrp from fastboot. Avoid as of now and boot to stock rom first
Click to expand...
Click to collapse
When I try to boot the phone it displays the message that the phone in unlocked and should no be trusted, it shows the honor booting screen and after a few seconds shuts down and the process is repeating.
If i try to press the volume up key when booting it takes me to huawei eRecovery where I can either shutdown the phone or download recovery but it fails everytime.
Thanks
Try flash the No check recovery, boot into and wipe cache. Then reboot
Powered by View 10
Try this
1. Flash stock ramdisk img
2. Flash stock recovery img
3. Reboot to recovery with button combination ie; power and vol down together
4. Wipe data and cache
5. Reboot.
Hopefully it'll work if it doesn't flash system.img after 1 & 2 steps and follow the next steps
Hi please specify model
And what update you installed...
If the update was genuinely meant for phone I believe a data and cache partation format should fix this..
I hope you are atleast seeing the honor bootscreen...
Specify model so that we could point you to correct system.img
Also did twrp gave any errors formatting cache memory?
same here
BKL-L09
hey guys i finally got my twrp back up and running here it is and i fixed format issue it had also supports f2fs now which is what stock uses and added a couple extra parititons it mounts and backs up
use cmd to flash twrp:
fastboot flash recovery updated-hannah-twrp-2019.img
hannah twrp:
https://drive.google.com/file/d/1ahEDJRaW6ZbpF7EgokQtQ6TEJ8yBUa9d/view?usp=drivesdk
cmd for nora:
fastboot flash recovery nora-twrp.img
nora twrp:
https://drive.google.com/file/d/12IPnevc7si2sNpxChMtPo5JJgwY4DJXh/view?usp=drivesdk
Sry i went MIA had alot happen lately so anyways im back here u go
for decryption patch a backed up boot.img with magisk beta both preserve boxes unchecked then flash in twrp as boot.img and flash zip below thanks @whodat711 for zip
https://drive.google.com/file/d/1-C4-ktJmW_oeyP1f5SAPGy3CX90mDuts/view?usp=drivesdk
then format data not wipe but format data button then type yes and press back all the way to main menu then flash masgisk 18.0.zip then reboot and it will not encrypt and u will have to start over as if phone is brand new ie. setting up google but enjoy ur decrypted e5+......
1.boot twrp and backup boot.img
2.make patched boot.img with magisk all perserve boxes unchecked while making it with magisk manager
3.flash twrp
4.flash patched boot.img and decryption zip from third link in post
5.format button in wipe section
6.flash magisk
7.reboot
Stock ROM MetroPcs xT1927-4 Hannah_T running good
skullkid383 said:
First and foremost I want to thank everyone in the twrp building group on telegram and @TwrpBuilder for the amazing guide on how to build twrp and guidance they gave to build this twrp
https://github.com/TwrpBuilder/twrpbuilder_tree_generator/wiki
So here is the twrp I built
https://drive.google.com/file/d/1aNTE6iAQQ4Ty1Zr1oM9ADb7xX_slrTzt/view?usp=drivesdk
After u flash twrp u need to edit fstab to disable force encryption then wipe phone flash latest beta magisk and ur all set
Refer to this guide for
Force encryption fstab file and how to disable force encryption thanks for this @CodyF86
https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323
Click to expand...
Click to collapse
just installed your Hannah-twrp.img and it booted just fine everything works thanks
Can you correct me if I'm wrong. So once I finish this process. I can go in and out of recovery with out computer. Also Then I can put apps directly into priv system with correct read and write,plus it will stick on reboots. Just wondering to .If this means I can flash custom kernals and roms with no worries other than normal issues. Thanks for your work.
Thank you so much for this!
jokono421 said:
Can you correct me if I'm wrong. So once I finish this process. I can go in and out of recovery with out computer. Also Then I can put apps directly into priv system with correct read and write,plus it will stick on reboots. Just wondering to .If this means I can flash custom kernals and roms with no worries other than normal issues. Thanks for your work.
Click to expand...
Click to collapse
Yes sir
jokono421 said:
Can you correct me if I'm wrong. So once I finish this process. I can go in and out of recovery with out computer. Also Then I can put apps directly into priv system with correct read and write,plus it will stick on reboots. Just wondering to .If this means I can flash custom kernals and roms with no worries other than normal issues.
Click to expand...
Click to collapse
So you can actually boot from device now yes awesome ...
Keeps trying to force encryption but fails when flashing a gsi.
Is there a way around this? No verity for this device?
JimmyJurner said:
Keeps trying to force encryption but fails when flashing a gsi.
Is there a way around this? No verity for this device?
Click to expand...
Click to collapse
Are u on stock with root I got easy solution for u to follow if fstab guide above is to hard
Hey skullkid383, thankyou for your work on this!! Twrp flashed and works NP. But I cannot decrypt. Following steps, the step you mount before pushing in twrp adb does not work, no such folder. The push goes thru fine although the mount did not. Format data worked, I can see internal storage and move things to and from PC through tether. But when I reboot its sticks on moto screen. When I flash back to patched boot for magisk the is boots to an "decryption unsuccessful" msg and asks me to reset the phone endlessly. Any help pls?
Project89Odin said:
Hey skullkid383, thankyou for your work on this!! Twrp flashed and works NP. But I cannot decrypt. Following steps, the step you mount before pushing in twrp adb does not work, no such folder. The push goes thru fine although the mount did not. Format data worked, I can see internal storage and move things to and from PC through tether. But when I reboot its sticks on moto screen. When I flash back to patched boot for magisk the is boots to an "decryption unsuccessful" msg and asks me to reset the phone endlessly. Any help pls?
Click to expand...
Click to collapse
I'm looking into how to flash fstab in a zip cause I don't think fstab worked for some reason try patched boot.img here see if it changes anything wipe after flash https://drive.google.com/file/d/1s-nS6rLk1tnO1JVFO1emTJdGcO6mNhBk/view?usp=drivesdk
With this boot and wiping after fastboot and twrp installs it boots past moto logo but hangs with the decryption unsuccessful msg
Project89Odin said:
With this boot and wiping after fastboot and twrp installs it boots past moto logo but hangs with the decryption unsuccessful msg
Click to expand...
Click to collapse
Ok so ur fstab is not edited for some reason so do u have a old stock backup I will have u change fstab manually in stock then boot to the twrp and wipe
I do not, I'll have to fastboot flash everything back to revert to stock. Was rockin with no SD tonight.
Project89Odin said:
I do not, I'll have to fastboot flash everything back to revert to stock. Was rockin with no SD tonight.
Click to expand...
Click to collapse
Grrr always make backup rule number one lol ok I'm looking into getting a flashable zip made but in mean Time revert stock tell me when booted
Back up fully stock, not even twrp lol. Metropcs variant btw
Project89Odin said:
Back up fully stock, not even twrp lol. Metropcs variant btw
Click to expand...
Click to collapse
1st make a backup just in case:
Ok here we go flash twrp and magisk beta then patched boot.img boot system get a file explorer with root permissions edit fstab.qcom find it here: /vendor/etc.
just replace current one with one I'm uploading
in guide to make easier to find wipe then u should be good of course flash magisk beta after u wipe as well
Hmm still decryption unsuccessful. About to reflash to stock. Sorry for the slow response. I have the next several hours free to test. I don't have an SD card, so i rooted the old way, using your patched boot, then used es file explorer to replace fstab, rebooted to confirm, and fstabs permissions had changed from rw r r to rw rw so it stuck. once I format data and internal becomes visible I move magisk over, flash then reboot and get dencryption unsuccessful. Also even flashing the recovery before formatting resulted in it being lost every reboot, only after format data it stuck.
Project89Odin said:
Hmm still decryption unsuccessful. About to reflash to stock. Sorry for the slow response. I have the next several hours free to test. I don't have an SD card, so i rooted the old way, using your patched boot, then used es file explorer to replace fstab, rebooted to confirm, and fstabs permissions had changed from rw r r to rw rw so it stuck. once I format data and internal becomes visible I move magisk over, flash then reboot and get dencryption unsuccessful. Also even flashing the recovery before formatting resulted in it being lost every reboot, only after format data it stuck.
Click to expand...
Click to collapse
Ok I am going to build new one in awhile my PC screen broke idk when but until then the link to Hannah twrp is down till I fix it
Ah man, so instead of fastboot flashing everything back to stock, I figured I'd just flash stock recovery back, after the decryption unsuccessful route. Flashed stock recovery, when it booted and asked me to reset the phone instead of going to twrp this time it went to the stock recovery image of a reset...phone booted, got to looking around and holy crap I'm decrypted! flashed your twrp and now I'm rooted with twrp and decrypted!! So maybe boot twrp the first time when formatting data and decrypting so when you boot and the device asks you to reset because of decryption failure it can use stock recovery to complete the process, then flash twrp for the finish? Your incredibly helpful man, again thankyou for all of your efforts and work on this!!
Still wanna fix twrp found a issue in formatting data I wanna fix but it shall take some time to get it done link is down til then cause it's something that needs fixed first before I put it back up
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