Database Develop

Tried installing titan rom + updating boot loader

Well I tried installing Titan Rom and then had to update the bootloader.
While fastboot didn't recognize my phone when i typed "adb devices" it still said it was connected, so I gave it a shot with the following instructions here.
http://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007
So I noticed that it erases modem 1 and 2.
I have wifi, but no network for my carrier to make calls or receive data.
My backup didn't reset the modem either. Phone is back to the way it was saved during TWRP backup, except for the modems/network.
Any suggestions?
Thanks.

hi
Mmm i will try to help you - tell me what version bootloader and recovery you have installed pls.

TWRP 2.8.6.0
bootloader v, can't tell you, trying different things to find out now.

TWRP 2.8.6.0
bootloader 0x4882

CindysD said:
Well I tried installing Titan Rom and then had to update the bootloader.
While fastboot didn't recognize my phone when i typed "adb devices" it still said it was connected, so I gave it a shot with the following instructions here.
http://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007
So I noticed that it erases modem 1 and 2.
I have wifi, but no network for my carrier to make calls or receive data.
My backup didn't reset the modem either. Phone is back to the way it was saved during TWRP backup, except for the modems/network.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
I'm not sure what model of Moto G you have, but for the data problem, you'll have to input your API settings. Flashing will usually wipe them out. Go to Settings, More (under Wireless & Networks at the top), Cellular Networks, Access Point Names. There you should see your carrier. When you click on it, it will open and here you will need the settings for your carrier. If you give me your carrier, maybe I can tell you what to input or someone else here will surely have the same carrier.
Going back one step, where you see Network Operators, click on that and see if your operator comes up. If so, that may fix the phone problem when you select the carrier.

you probably flash the wrong ''modem NON-HLOS.bin'' file.
did you notes that in the download folder have 5 folder one for it device model?
Did you download the one for your's device exactly model?
If so it may be wrong...
Find a XML ROM of yours exactly device and flash again the ''modem NON-HLOS.bin''
to find the ROM search here
Use this commands but with the right file.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
modemst1 and 2 is only erasing the temp stats of modem not erase the modem files.

No Wi-Fi MAC adress.

I have a problem. My mi5 told me: An error occured with Google Services. So i rebooted the phone. It booted just OK. But I've seen that wifi doesn't work and the phone always reboot after 2-3 minutes. I've seen that the wi-fi MAC-adress is 02:00:00:00:00:00.
So i've tried to flash different firmwares using twrp and miflash. But there is still no MAC. How to change it and make my phone work?

if you dont have a backup of efs and efs2 partitions using twrp 1.0.3-2 or later then youre screwed...
youll have to get qualcomm diagnostic tool and manually input your original mac address to get it working again.. you can find some posts about it on miui forums

You should flash the fastboot ROM via MiFlash tool and while you will flash, you should also select the clear internal storage option or something like that. This will cause to delete all your files, applications, photos or etc. So be aware of this, firstly backup your files and apps and then flash the fastboot ROM. Your problem will be solved.

xaiomi mI5 loop,stuck.

hi friends, i need so much your help!.
I have xaiomi mi5, the operating system of the cellphone has been updated, and then the device has entered the loop.
He can not get up at all.
I've tried to do so far:
FAST BOOT - but even the computer can not read the device despite all the permissions I have approved for the computer.
MIPCSUIT - does not work well because the computer does not recognize the device.
Your help must be smart and good people!

I am also stuck with the same problem.
At least I can get fastboot.
I think if you OK to loose data then just go to recovery mode with Volume up + power button pressed together. And wipe all. This may solve the problem. But I don't want to loose data I am skipping this option.
If any one knows other way to unbrick without full wipe then please let us know.
Thanks

have you unlocked bootloader?
you can try run by fastboot twrp recovery mode.
Code:
fastboot boot twrp.img
after few seconds phone boot to recovery, you can encrypt the phone and copy data.
twrp is here

My bootloader is locked I think.
I tried that command. Didn't boot to twrp.
Any other way.
Anyway Thanks for suggesting.

Are you on latest MIUI global stable? I think Xiaomi's guys ****ed it up this time around and got bootloop for everybody on latest update.
Take a read here and good luck: http://en.miui.com/thread-2776961-1-1.html

ok listen me... if you have got unlock permission and unlocked your phone or you have unlock code.. you must bind your acc with other xiaomi phone easly enter your acc and bind acc now go fastboot download mi flash unlocker install adb driver and unlock then you can flash stock rom i had that problem and i solved

Hello,
I had similar issue.
To be able to start phone/miui you should remove sim card,
in my case it was connected to connecting to cell network that caused reboot.
Than it will be possible to update phone using WiFi.
For me issue was solved with V9.5.2.0.NAAMIFA update.
BR Jarek.

jarek102 said:
Hello,
I had similar issue.
To be able to start phone/miui you should remove sim card,
in my case it was connected to connecting to cell network that caused reboot.
Than it will be possible to update phone using WiFi.
For me issue was solved with V9.5.2.0.NAAMIFA update.
BR Jarek.
Click to expand...
Click to collapse
Lifesaver here!
This worked perfectly for me! Go figure?
Cheers

You can try
I tried version gemini global images v10.2.2.0. OAAMIXM 2019115 GLOBAL but failed then tried v8.11.22.20181122.000 8.0 GLOBAL but failed then 2 month later i tried with good battery and good on off and main important is version GEMINI GLOBAL IMAGES 6.11.10 _20161110 and version GEMINI GLOBAL IMAGES V7.2.4.0.MAAMIDC 20160129. AND GUESS WHAT SUCCESS. NEVER TRY WITHOUT BATTERY AND WITHOUT EDL POINT. EDL POINT FOR UNLOCKING BOOTLOCK AND DOWNLOAD SOFTWARE FLASH FILES WITH GOOD INTERNET WITHOUT INTERUPPT SO FLASH SUCCESS. MY 2 MOTHERBOARD OF MI5 SAVED WITHOUT HARDWARE. HOW TO KNOW SOFTWARE OR HARDWARE....1ST CHECK CHARGING HAPPENING OR NOT IN SWITCH OFF AND CAN IT GO TO FASTBOOT MODE OR RECOVERY MODE. IF ALL THIS GOOD GO FOR FLASH IN SAME PROCESS. OTHERWISE HARDWARE AS STATED THAT RESISTOR ALSO PLAY A VITAL ROLE IN BOOTING OR STUCK AT MI LOGO. MOISTURE IN PHONE UNDER IC REQUIRE HEAT WITH PASTE AT HARDWARE LEVEL.

Question regarding bootloop

Hi all,
First of let me start by saying I have a Mi 9T and I know that it has its own forum, but I didn't find a solution to my problem there, so I thought I'd ask in this forum as well, since the devices look a lot like each other but here are more people.
So my problem is I got stuck in a bootloop which I can't seem to get out of. I can boot into fastboot mode and adb fastboot AND Miflash recognize my device, so I'm able to flash things, but the bootloop still stays.
I started on global rom, and then installed twrp. Then I flashed the latest 9.7.25 ROM from mi-globe for MI 9T. It booted up fine, but my TWRP was removed and I couldn't install it anymore like the first time. For some reason I did a factory reset then. And tried to flash a new ROM by using MiFlash. It said it was succesfull, but it only took 1 second and it didn't automatically boot (it stayed in fastboot mode). I tried again and it said anti-rollback error.
So that didn't work, so I tried flashing boot.img, recovery.img and system,img seperately by using adb fastboot. That worked and it booted normally. I went through the startup configuration like selecting wifi network and gmail,etc. But after trying to set a fingerprint, the screen went completely black but the phone was still on. I could reboot it normally, but when the lockscreen came up or I tried to use fingerprint scanner it went black completeley every time.
I was desperate, so I used 'fastboot erase system -w' in adb fastboot, which is a factory reset apparently. Then I flashed the 3 .img files like I did before, but this time it didn't boot, but went into bootloop.
I also tried 'fastboot boot twrp.img' which also didn't get me into twrp, it just goes to bootloop again.
So to summarize: I CAN get into fastboot and adb fastboot and miflash DO recognize my device, but I can't get out of bootloop no matter what I flash.
Does anyone know a solution for this problem? I would be very thankful.
I also don't understand why flashing or booting TWRP doesn't work, while it worked the first time. I also don't understand why flashing the 3 .img files doesn't work this time, like it used to work the first time.
Btw my anti getvar is 1.

Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working

DaveHTC200 said:
Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working
Click to expand...
Click to collapse
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?

Rapydax said:
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?
Click to expand...
Click to collapse
I've not had your issue but that was causing the flash tool to just carry out the task in 1 second, which isn't possible

i have the same situation here. did your issue solve?

Question Redmi Note 11 Stuck/boot loop in Recovery mode

I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.

mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)

Sheist! said:
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)
Click to expand...
Click to collapse
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Edit:
I saw this in another thread, we have the same problem.
KMS45 said:
Hello to everyone,
So basically i read all the 10 pages of this thread and I have not found someone that have the same problem as me. I have the “bootloop” but the thing is that my phone is not even turning on. It is just booting and going back to the recovery menu. So I choose the reboot option but still coming back to the menu. I have already turned on the debug usb option because I used to be using it before my phone dies. I have a Xiaomi MI10 Lite 5G. I also tried the MiAssisstant but no succes because device not detected.
If someone have a solution without wiping all my precious data pls ?
Click to expand...
Click to collapse
KMS45 said:
Here is a video to understand what is happening when:
Reboot:
https://imgur.com/a/rB9QhSZ
Safe Mode:
https://imgur.com/a/X0KH5AD
Click to expand...
Click to collapse

mhegz said:
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Click to expand...
Click to collapse
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.

Sheist! said:
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.
Click to expand...
Click to collapse
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.

mhegz said:
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.
Click to expand...
Click to collapse
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.

Sheist! said:
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.
Click to expand...
Click to collapse
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files

mhegz said:
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files
Click to expand...
Click to collapse
Then ignore my steps, since they won't work on a locked bootloader. I will defer to others who have clues regarding a locked bootloader and a down system.
You COULD try to unlock it, but that would definitely wipe all your data:
"Unlocking the bootloader will wipe all data"
Get the unlock tool and instructions here, if you so choose anyway:
Apply for permissions to unlock Mi devices
en.miui.com
NOTE: that gives you unlock version 6.5.224.28 but it might/should prompt you after install to install the updated version since mine is 6.5.406.31 from April of 2022. When you run it, it makes you wait a week.
NOTE 2: It does state this warning, however:
"First, confirm that your device can be unlocked
Your device functions normally and not in a bricked, soft-bricked, bootloop state."

mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
I am facing same problem my phone is stuck in recovery mode it keeps rebooting I have tried selecting safe mode recovery reboot but it keeps rebooting did you find a solution to this problem please let me know.Thank you.