Hello, I am using a Redmi 9 Global (64/4) lancelot device. Since yesterday I have been using the Pixel Experince Android 13 Vendor S ROM, anyway yesterday i was testing something on TWRP recovery and performed the following actions (to the best of my recollection):
I mounted almost all partitions, then, I went to Advanced > Addons and experimented with options like 'Enforce decrypt' (I'm not sure about the exact name), 'Primissive,' and another option that failed immediately upon running but it has almost same name.
Afterward, I wiped Dalvik/Art cache, system, data, internal storage and caches. I flashed the same ROM (Pixel Experience) again, but upon reboot, the device went back into recovery mode, regardless of how many times I rebooted.
Anyway, I tried that 'Enforce' option (i didn’t remember its exact name), and it allowed the system to boot. However, both Wi-Fi and hotspot functionality were not working but the SIM cards are functional, providing data, call services, and other features. However, I did not check if the IMEI 1 and 2 were still there or not.
In an attempt to resolve the issue, I flashed the official fastboot ROM using Mi Flash Tool. However, the device entered official recovery mode and displayed the error message 'NV data is corrupted'. I attempted to resolve the problem by flashing the official fastboot ROM using SP Flash Tool, i tried it 3 times using different optios such as 'download only' 'firmware upgrade' and 'format all + download' Unfortunately, the problem persisted.
Then I tried to reinstall TWRP and use a custom rom without WIFI to be able to use my phone until i can find a way to fix it but my bootloader was locked, and when I attempted to unlock it using the Mi Unlock Tool, I received a message stating that my phone did not have the permission. This was wierd because during my previous use of SP Flash Tool(few months ago), I was able to unlock the bootloader.
Currently, I have installed an engineering ROM. Here's the situation: Wi-Fi and both SIM cards are working fine, but I cannot see any IMEI numbers in the settings or using the *#06# code for any of the slots. I'm unsure if this is due to the engineering ROM or if the IMEI numbers were wiped.
Fortunately, I still have the box and that lable which IMEI is written on it. I am now seeking a solution to fix this issue. I know there is a tool that can help write my IMEI for slot 2, but I'm unsure if it will resolve the problem. I have seen some Youtube videos where people fixed this problem using Unlock tool, but I don't have it, and the cracked versions are all fake and viruses.
Anyway , I wonder if there is any way to install Gapps on my engineering ROM. I know it's not ideal, but I could use it for a while. If its possible to install Gapps on Engineering ROM using custom recovery then which recovery should i use? I mean my Eng ROM android is 10 so should i use a custom recovery that designed for Vendor Q and then how to install it while my bootloader is locked ? Or is there anyway to install Gapps using adb sideload?
I attached some screenshots below
Thanks for any help
Related
Hello,
Thought I would share my recent bad experience and the resulting solution.
My phone was on a GPE ROM, and I encrypted it for work reasons, encryption went smoothly, but once encrypted, it was impossible to go into recovery with the encrypted partitions visible (hence impossible to flash a new rom or even do a factory reset which is the only - or so I thought - way to remove encryption).
After many attempts including flashing the latest TWRP (not solved yet, they say 2.7 should include a solution) I was still getting the "unable to decrypt phone" error after entering the password (which works perfectly on regular boot) in TWRP.
Eventually, through a lucky mistake, I found the solution, at one point I mistakenly re-locked my phone (fastboot oem lock), later when I was trying to flash a stock recovery I realized I had to unlock it again... well, unlocking it through HTCdev automatically does a factory reset, regardless of the encryption!
viola, problem solved!
Hi guys,
I am kind of stuck here.
I am using the xtrasmooth rom with the elemental x kernel (Marshmallow) and everything worked fine. Today I decided to add a little more security, so in the security settings I required a password when starting up android. I had been using the feature a while ago on android 5.x and everything worked fine.
Somehow my phone crashed today and now I am stuck on bootloop. It is not even asking me to enter a password.
However, I can access the recovery (TWRP) normally after entering my password to decrypt storage. I tried to wipe system and restore a backup. Still no success. I did a fresh clean install but no sucess again. It's always stuck on bootloop.
I don't want to factory reset or flash the complete stock image, since I do not want to lose my data. I tried to active ADB Sideload in TWRP, but somehow that is stuck at "starting adb" after cancels after a while with no success.
Do you guys maybe have an idea how to fix the problem? I guess I would need to disable the password but I do not know how to do that without an functioning rom.
Many thanks for your help!!
Reboot to your bootloader and use fastboot to flash
Sent from my Nexus 6 using Tapatalk
stupid me. That would have worked too.
I just connected my phone to the computer using twrp, used the file browser to push a file to the phone (regular storage) and installed another Light rom that is close to stock.
Everything worked fine. Must be a ROM or Kernel Issue. I will report to the according thread in this forum.
Thanks!!
Hi,
I had recently tried to root my Moto G 2014 (running 6.0) so I could install the latest CM13. I followed all the instructions and even came across the red WARNING BOOTLOADER UNLOCKED SCREEN every time I try to reboot the device(status code=3). After installing TWRP 3.0.2.3 and making a backup of current state, I ran into a few bootloops which I managed to fix by flashing it back with a stock as shown on this thread http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682 (I downloaded both the download links and extracted everything to a single folder before following all the commands)
The SIM wasn't receiving any signal thereafter, which I luckily managed to fix with help from another thread.
My problem is that I've tried to install SuperSU more than a couple of times with different versions and it almost always sends my phone into a bootloop. The few times where I was able to boot into system, it kept giving me the error that the necessary binaries weren't installed and I was not able to do as well, due to the bootloop issue. Working RootChecker told me that my device wasn't rooted properly, which I wasn't surprised at.
Although I read somewhere that rooting isn't necessary to flash a custom ROM like CM13, so I decided to negate SuperSU (I did the unroot everything option on SuperSU and factory reset the device, cleared data, cache and dalvik too) and try flashing it directly instead through TWRP. It kept giving me the Error 7 even after I had removed the assert checks.
Can someone tell me what I did wrong and what can I do to go ahead? Also, is my bootloader completely unlocked? I tried checking *#*#7378423#*#* but nothing happened, so I rebooted into bootloader and used the 'fastboot oem device-info' command but it said that the command was invalid or something.
As of right now, the phone is running 6.0 with all the stock apps. The bootloader unlocked warning still shows up every time I reboot the phone though.
Boot into twrp and wipe cache , dalvik cache, system and data and flash cm13 and wipe cache and dalvik cache and reboot you should be good to go if u want root access flash the latest version of supersu or you can for a rom which has preinstalled supersu such as dirty unicorns.
phoenix964 said:
Hi,
I had recently tried to root my Moto G 2014 (running 6.0) so I could install the latest CM13. I followed all the instructions and even came across the red WARNING BOOTLOADER UNLOCKED SCREEN every time I try to reboot the device(status code=3). After installing TWRP 3.0.2.3 and making a backup of current state, I ran into a few bootloops which I managed to fix by flashing it back with a stock as shown on this thread http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682 (I downloaded both the download links and extracted everything to a single folder before following all the commands)
The SIM wasn't receiving any signal thereafter, which I luckily managed to fix with help from another thread.
My problem is that I've tried to install SuperSU more than a couple of times with different versions and it almost always sends my phone into a bootloop. The few times where I was able to boot into system, it kept giving me the error that the necessary binaries weren't installed and I was not able to do as well, due to the bootloop issue. Working RootChecker told me that my device wasn't rooted properly, which I wasn't surprised at.
Although I read somewhere that rooting isn't necessary to flash a custom ROM like CM13, so I decided to negate SuperSU (I did the unroot everything option on SuperSU and factory reset the device, cleared data, cache and dalvik too) and try flashing it directly instead through TWRP. It kept giving me the Error 7 even after I had removed the assert checks.
Can someone tell me what I did wrong and what can I do to go ahead? Also, is my bootloader completely unlocked? I tried checking *#*#7378423#*#* but nothing happened, so I rebooted into bootloader and used the 'fastboot oem device-info' command but it said that the command was invalid or something.
As of right now, the phone is running 6.0 with all the stock apps. The bootloader unlocked warning still shows up every time I reboot the phone though.
Click to expand...
Click to collapse
while @kushal_10 explained most of the things to do, i would like to remind you that CM13 has inbuilt Root. You just have to enable Developer options, then in Developer Options,under Root Access, choose Apps and ADB. Don't flash SuperSu
Hope I helped you.
kushal_10 said:
Boot into twrp and wipe cache , dalvik cache, system and data and flash cm13 and wipe cache and dalvik cache and reboot you should be good to go if u want root access flash the latest version of supersu or you can for a rom which has preinstalled supersu such as dirty unicorns.
Click to expand...
Click to collapse
I read somewhere that wiping the system isn't advisory because in case something goes wrong, there will be no way to restore. Can you confirm this?
Dear community,
I have a Lenovo K3 Note which I would like to flash using
. Team Win RP v. 2.8.7.0 was already installed on the device and I wiped Davik cache, System, Cache and Data using "Advanced Wiping". The OS is therefore gone. When trying to install a new ROM Teamwin just restarts and prompts the menu, no error messages. Some LOG messages like "MTP enabled" are briefly displayed, then I can see the Teamwin logo. I have tried multiple ROMS from needrom, this seems to be TWRP related.
I am new to this and I assume the phone was already rooted before I wiped the OS. I have tried flashing it again with TWRP using Fastboot and ADB (cf. [URL="https://www.longren.io/flash-twrp-img-file-from-ubuntu-using-fastboot/"]https://www.longren.io/flash-twrp-img-file-from-ubuntu-using-fastboot/ ), but the bootloader does not seem to be unlocked (fastboot oem unlock prompts FAILED (remote: Unlock operation is not allowed). Maybe these problems are related, on other hand I read in another forum that Lenovo blocked fastboot somehow (??), it may also be unrelated.
Since the system is wiped I cannot unlock USB-Debugging in the developer options, but it was checked last time I saw it.
I would appreciate any help,
Dabooja
Update TWRP
Hi,
Use SP Tools to flash the latest TWRP for Note K3 - 3.0.2-7:
https://basketbuild.com/filedl/devs?dev=andreya108&dl=andreya108/twrp-3.0.x/Lenovo_K3/recovery-twrp-3.0.2-7-k3.img
File source: http://www.needrom.com/download/twrp-3-0-2-7-2/
Hi everyone, I wanted to root my phone because my google pay way not working after I unlocked the bootloader of my phone.
I used magisk to flash a version for my redmi 2201117TY, but after using fastboot to flash my "patched" rom back to my phone, it is now booting over and over again.
I installed twrp to try to install another ROM, but I'm not sure it'll work.
I installed several redmi note 11 img to see if it would fix it but i did not (V13.0.6.0.SGKEUXM, V14.0.2.0.TGKMIXM and V13.0.3.0.SGKEUSF which was my original one i suppose)
I just want to have an usable phone even if it means cleaning everything. How can I format everything back to make it usable?
I have access to adb, fastboot, TWRP. (usb debugger on)
I am not sure I can find the exact rom as it was a really wierd version from my operator (SGKEUSF) and I can only find one on internet which happen to not work. How can I unbrick my phone now?
NOTE : the SGKEUSF is an overlayer of the SFR (Altis) network so i would rather not use it
Format (not wipe) data in twrp, flash a rom that fits your needs (on sdcard), reboot recovery (!), reboot system. If fastboot access is given it's fixable. Had the same thing many times with spesn. This is the way it always works for me.
When you say "flash a rom", you mean a recovery or a fastboot one? Does it have an influence?
Just download latest version of MiFlash, download RN11 fastboot ROM, flash the ROM via MiFlash. In MiFlash make sure to to check the box whether of not to lock the bootloader after flash. Just to be safe leave it unlocked until after the phone is safe.