ORANGE FOX - CONTINUES AFTER FLASH STOCK - Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe

Guys, I fleshed the stock rom through my flash, and when I reinstalled ofox I realized that there was some trace of it from the previous installation. I put a password inside the recovery long before I put the stock one, and when I reinstalled ofox it asked for the password again. Even when a stock rom is flashed, are Ofox files left on the cell phone?

Related

Problem flashing roms

So I've been trying to flash CM5.0.8 and I tried flashing Cm6, but neither of them will boot up, at the moment I have the leaked version of FROYO flashed on my Nexus one, whenever I try to flash one of those mentioned it doesn't work. I have the latest radio, I've tried wiping, but it doesn't work. Help?
FIXED: I Flashed Clockwork Recovery and used that instead of Amon Ra, and now everything is fine.
What steps are you executing to flash your phone?
well, I first do a nandroid backup, and then I do a wipe, and I flash the Cm6 zip file, and then the flash the FR91 zip file. It stays on the X with the pad lock.
latest radio meaning 5.08? or the 4.06?
I never have had problems flashing roms, I recommend going back and checking the md5 sum. Wipe data/factory, cache, dalvik cache, then flash the rom, the gapps. Should do the trick, it could take awhile to boot up on first time. Cyangoen has typically taken alittle extra time for me.
I have the 4.06 radio. I tried to flash FRF50 and it didn't boot up either. SO now I'm trying the FRF90 stock.
So neither the stock version of FRF50 works, or FRF90. I'm out of ideas. Help?
Your phone gets to the bootloader and can load recovery - which is good.
In recovery wipe EVERYTHING before loading ROM, install CM6 from ZIP or whatever ROM you want (shouldn't matter), wipe again (data/cache/dalvik/whatever), and reboot.
Please re-download the ROMs, as you may have faulty downloads (most probably).
Okay, I did as you said, I redownloaded CM6, and I tried wiping, reflashing, and wiping again, but for some reason, it still stays at the X screen with the padlock. Err, I tried it with the FRF50 and it seemed to work though, but I was wondering why I'm having troubles with other roms.
I've realize that a lot of times verification fails on updates. Does this have to do with the recovery?
Which recovery are you using?
AmonRA the latest one.
If you have verification failures - means that your updates are faulty. Nothing good will come out of flashing them.
So I'm guessing it's not the recovery that's messed up, but the zip files I'm trying to flash?
I have a lot of verification fails. :\ I'm not sure why. Anyone know?

[Q] Constant Boot Loops when trying to install new ROMs

I have CWM 4.00.15 installed and I tried to install Ryyu's Rom (Wipe) by putting it on the SD card and rebooting into recovery, then selecting the zip file and hitting apply. When the installation tried to update my kernel, it just froze and rebooted. I was then stuck on a boot loop between the Galaxy S screen and the CyanogenMod boot screen. I know that Ryyu's did not install correctly because the CyanogenMod boot screen was still there. I had to use 3 button recovery and erase cache, davlik cache and user data before trying to install AOSP Essence, but same problem happened. Installation dies and phone keeps rebooting in loops. Finally, gave up and went back to CyanogenMod Nightly and it worked.
Why can't I seem to install any other ROMs besides Cyanogen? I know I am doing something wrong, but not sure what. Any advice/help appreciated. Thanks.
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Br1g0 said:
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Click to expand...
Click to collapse
Hi,
this is what I initially did to get Cyanogen on:
1. Used Superoneclick root to root phone
2. Check that 3 button recovery and download mode works. Recovery version was 3e, so installed superlagfix from android market. This automatically installed ClockworkMod Recovery as well.
3. Use CWM and flashed recovery for Samsung Galaxy S i9000
4. Reboot into recovery and select the CyanogenMod zip file and click apply to install.
To install subsequent ROMs, I just put the zip file on my SD card, reboot into recovery and repeat step 4 above, after clearing cache and user data. It is after that I get stuck on boot loops.
I did do a Nandroid backup before my initial Cyanogen install so I can go back and restore it, but it would be Froyo.
when coming from CM / MIUI - Samsung based ROM
you MUST flash a 3 file firmware with pit and re-partition.
Cyanogen and MIUI use different partitions than samsung ROMs so this is why you are having issues.
Ok, just managed to flash Darky's EE 10.2 using Odin. Not sure if Odin is the ideal way, but it worked. Really enjoying Darky's. Thanks folks!

[Q] Phone constantly bootloops, data cannot be mounted

I've unlocked my bootloader, flashed a kernel, went into recovery and installed the ROM zip (I've tried both VanirAOSP and Mahdi ROM).
It remains in a bootloop.
When I press clear data/cache, recovery says the partition cannot be mounted.
Can anyone help, please?
Never mind, problem solved, I flashed a stock rom using flashtool and reinstalled the rom from there.

[HELP]Xperia SP stuck in cyanogenmod logo after update

Hello,
I flashed CM11 yesterday and everything went alright. This morning I noticed I had an update for it and proceed to do it.
After the instalation and optimizing all apps it asked me for my simcard PIN and after I unlocked the phone it just went back to the cyanogenmod logo over and over.
I tried to reboot phone but it didn't help.
I've tried to search for similar threads but since i'm a newbie (first time I ever flashed anything) to this I decided to create this thread.
What should I do?
Thank you!
try to use flashtool. google it on how to use flashtool or check other threads.
So I guess i have to flash a stock ROM with flashtool and do it all over again right?
And btw, any reason you guys might think It got stuck in bootloop after I updated CM11? I came from a fresh stock rom. I'm kinda scared it might happen again after the reinstall.
Can't you enter recovery to flash a nandroid backup? (If you have one)
If not, you have two options to choose from.
Fastboot or flash a kernel with CWM or TWRP.
ADB push a zip file of a ROM and flash that.
Flash an FTF file using flashtool and start all over again.
There are many reasons why you're stuck in bootloop at the moment.
With the info you provided, there's no way of telling what caused it for you.
Well, i flashed stock ROM with flashtool, installed CM11 and I had no problems.
Went to settings and OTA update was available. Downloaded it and installed it, stuck in loopboot again. I just can't figure out what's wrong. My phone has bootload unlocked.
Might just do it all over and not update, is that a problem?
Don't use OTA, just download and flash updates manually using recovery.
In the future, for your ease, if this happens again just wipe the phone very clean (cache, /system, /data etc except /boot) and then re-flash the CM zip that you have.
It is a good practise if you make a nandroid backup before flashing a newer version of zip, in case of breaks. Or, you can have Titanium Backup to backup your apps automatically (pro version) everyday, so that you can be ready if there will be something bad happen.

Can't flash recovery on my S3

Hello, just bought an used i8190. Since last friday i have been trying to flash a custom recovery on this phone via Odin, but after i flash it returns to the default recovery on next boot.
Yes, i have unchecked the "Auto-reboot" option on Odin. I turn off the phone and then manually enter recovery but with no results. I rooted the phone pretty easily and installed both TWRP and CWM apps to flash from android, but they don't work either (twrp crashes always and CWM just gives me an error.
Mi baseband model is XXAll2
kernel is 3.0.31 [email protected] (root name seems weird)
I searched the forum and found similar cases with the baseband, but even so i haven't found a concrete solution.
I even flashed a new pre-rooted rom from this thread: https://forum.xda-developers.com/showthread.php?t=2030282
Mi compilation number has changed to XXAMG1 but the baseband remains the same. I can't flash a recovery whatever i try.
I hope someone can give me an answer, cause i really want to use this phone feautures to it's fullest
Update:
Somehow, i managed to flash CWM via it's app successfully. However, when i tried to flash the TWRP via zip all i got was a blank screen and the phone booted directly to Android. I had to reflash the cwm with the app. However, i tried flashing via odin the Lineage os 14 from novafusion and i got a bootloop, reflashed the old stock firmware and now my device works but the recovery doesn't, and can't even flash this time via the app.
I tried flashing via ODIN stock recovery and other recoverys and i still get the same result. I have downloaded some stock roms, but im afraid to flash them in case i end up in a bootloop and unable to access recovery still
Any clues?
Glass_Arcana said:
Update:
Somehow, i managed to flash CWM via it's app successfully. However, when i tried to flash the TWRP via zip all i got was a blank screen and the phone booted directly to Android. I had to reflash the cwm with the app. However, i tried flashing via odin the Lineage os 14 from novafusion and i got a bootloop, reflashed the old stock firmware and now my device works but the recovery doesn't, and can't even flash this time via the app.
I tried flashing via ODIN stock recovery and other recoverys and i still get the same result. I have downloaded some stock roms, but im afraid to flash them in case i end up in a bootloop and unable to access recovery still
Any clues?
Click to expand...
Click to collapse
Flash the stock rom as it will fix bootloops and bricked devices. Make sure to have the right ROM and flash it with Odin. The os may take longer on first boot and make sure to factory reset it as data may cause bootloops, then try flashing the recovery.
I flashed twrp 3.1.1 through Odin

Categories

Resources