Hi all,
Have had the same version of orange fox recovery installed for the last couple of years. Never had issues with it when I did need to boot into it and do what I needed to do.
Yesterday, i finally decided to move from Android 11 to Android 12 Lineage based ROM.
I did through the .zip file install, using orange fox recovery. All went well.
But I haven't been able to get back into Orangefox Recovery since. I use a 3x3 pattern, keep punching in the pattern, to no avail.
Any assistance would be greatly appreciated
Regards
Related
Hi,
I flashed successfully CM 12 on my Yureka. Managed to install TWRP recovery; I installed CM recovery, flashed root.zip file, and then installed flashify and thus installed TWRP recovery.
However, Stock ROM email app dont work for hotmail as push. Hence, installed PacMAN and one more before I went to Blisspop ROM.
Both these ROMs take APN settings of both SIM as same. and Bliss POP ROM started giving me process.android.com error that I could hardly operate the phone. when I went to recovery, to my surprise, the TWRP recovery was missing
I must also mention here that while I was installing Bliss POP, I did wipe Dalvik Cache, internal storage and media.
so, I went to fastboot mode, installed cyanogen recovery and flashed CM 12 again. My phone is working fine now. However I want to install a Custom ROM s
And Hence since last 48 hours I have been trying to install TWRP recovery with no success.
I have now realised that on fastboot command for unlocking bootloader, it shows waiting for device. Tried Yureka all in one tool for CM 12, no luck
I have tried to install PDA net, it works fine
on Device Manager, ADB interface is shown properly.
I have deleted the drivers, and when machine is rebooted, it again installes ADB interface.
But I cant unlock the bootloader.
I am nearly certain it is a problem with my drivers for Yureka.
Searched, googled since two days, but no luck.
Can anyone help me who went through similar issues please?
I locked boot loader using all in one tool and then unlocked the bootloader again. and yes, it worked
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?
Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Nikodominiko said:
Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Click to expand...
Click to collapse
So I managed to fix the problem. When you root this phone or in fact just flash a custom recovery like TWRP, it changes the model of the phone, If you unroot the phone you won't be able to receive OTAs anymore even if you are on stock ROM, you'll always get an error at the end of the update even if you do it manually, if you are dumb like me and didn't make a backup of your stock system, you won't find any help on the internet more than to install a custom ROM and learn to live with the errors and bugs. I did not want that so to be able to get the phone to its factory state, what I did was this:
1. Download: stock recovery image for Le s3 x522 (official, you can find it anywhere), LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip, twrp_s3.img (the chinese TWRP recovery) and S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
2. Save those zips to the root of the phone, obviously the .img files you are going to flash them through your PC
3. Put the phone in bootloader mode. command: fastboot flash recovery recovery.img (the official recovery)
4. fastboot boot twrp (the chinese one)
5. From this step what I did was pure luck
6. wipe cache and dalvik and install LeEco_X522_5.8.019S_OTA.zip
7. wipe cache and dalvik and install bootloader-20S-s2.zip
8. wipe cache and dalvik and install S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
9. Reboot
How and Why did this worked I don't know, I am a noob but please try if you find yourself in the same situation as I was, you don't lose anything with trying, if this doesn't work don't blame me, this worked for my phone.
Greetings friends!
Thanks for putting this guide together, I am in a similar situation in that I reverted to stock everything (1. Installed YDSS chinese twrp, 2. Installed S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip. This flash was supposed to have installed the stock recovery and overriden the ydss twrp, but didn't, I had to manually flash that after. Everything came back smooth but my updates also failed at recovery.
I am wondering where you got the LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip & twrp_s3.img from?
Nice to hear you finally got it to work ! Aren't the X520 and the X522 the same phone ? Why official ROMs are not compatible ?
Good day! I am here asking for a few help as I seem to have trouble getting my phone back to life.
Earlier, I tried flashing android 9.0 pie beta rom I found on a certain group here locally in my country. The rom's link is as follows https://drive.google.com/file/d/15egbHONHGgm0AnvFYm2PCOmSyz0_utRR/view?fbclid=IwAR0I_akz9JcbpZxzitLNfm9OM2a-HH7FiDIDEHPM0-5wj0vIsuvz1TunrQQ. I came from Pixel Experience 9.0 Pie. I downloaded the rom above and rebooted my phone to fastboot mode without clearing data, etc through twrp first. Then I flashed the rom directly using Mi Flash. Once finished, the phone was not booting up properly and resulted in bootloop. Then, I downloaded the official stock rom and had it flashed directly to my phone. However, to no success, I only keep getting bootlooped. I then again tried to boot into fastboot and unlocked oem and flashed twrp and cleared dalvik, system, data and reinstalled pixel experience. Still no joy as upon rebooting, still bootloop.
Can anyone please help or assist on what further actions should I do? I'll greatly appreciate all the help I can get. Thank you!
**Update**
So I tried flashing the AEX Rom using this link https://forum.xda-developers.com/mi-a1/development/rom-aospextended-rom-v4-6-t3757436 and I can see the AEX logo and it stucks up there and just freezes my device.
First install 8.1 with MI Flash
https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533
Necrodaemon said:
First install 8.1 with MI Flash
https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533
Click to expand...
Click to collapse
You sir, just earned a fan! A million thanks!
Hello I just bought this device off eBay. Everything worked so I immediately charge the device rebooted to the bootloader AKA fastboot, OEM unlock the device, downloaded all the proper zips to install a custom rom and TWRP, flash TWRP, wipe system, data, cache, reboot to recovery, install the ROM, install SuperSU after removing lineage SU, install gapps, and rebooted the device. And it just hangs on the boot animation. Everything seems to have installed properly it just won't boot past the animation. Any assistance would be greatly appreciated I think this is an incredible tablet and I'm really eager to be able to use it.
Nevermind. I plugged it back in and when I got home I tried to boot it again and it worked. Not sure what went wrong though. So far everything is a-ok.
Just wanted to add...I was able to do everything I needed from my Amazon HD 10. Yes...I used an android device to unlock, root and flash another android device. I think these little things, are what made these old school android devices the best ones. Also wanted to add...such a shame Samsung doesn't make them like this anymore...or Google. TBH I am equally as happy with a stock ROM as I am with a custom ROM. Can't say that for many android devices anymore.