Database Info

Moto G 1st Gen XT1033 Boot Loop on Stock Lollipop

My Moto G (XT1033) 1st Gen with stock lollipop has stuck in a boot loop.
I am still able to go in to recovery mode. Have tried clearing cache, but that didn't seem to work.
I don't have CWM installed it's pure android as stock have installed updates only through OTAs.
Have googled about it and many are stating that a factory reset will solve the issue. But I don't want to lose data in the phone.
Main reason for the boot loop could be App as I use beta versions of Facebook, Whatsapp and Nova launcher from apkmirror.
What can be done to recover data or just get this boot loop fixed?
P.S: My device is not rooted and does not have any CWM or TWRP recovery.

I have got exactly the same issue yesterday itself. It was working fine, even received a call after which it was placed on a table. Picked up a few moments later & it was switched off. After that, whenever i'm trying to turn it on, its stuck on the M Logo - Powered by Android i.e Bootloop.
My phone was full stock and totally untouched as well. There weren't any apps installed from sources apart from Play Store. I'm able to access the stock recovery and tried clearing the cache but no respite. Whenever i try to factory format that, it gives an error of e:/could't mount /cache/recovery/xxxxxxxx errors.
I had read the forums for similar issues and got to know from this thread : http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492. The issue is cent percent same apart from the fact that i can access stock recovery.
Maybe @ravibhat & @lost101 can help us in this. I'm not worried about getting the data but bringing the phone back to life is more important for me !! Please help.

BBThumbHealer said:
I have got exactly the same issue yesterday itself. It was working fine, even received a call after which it was placed on a table. Picked up a few moments later & it was switched off. After that, whenever i'm trying to turn it on, its stuck on the M Logo - Powered by Android i.e Bootloop.
My phone was full stock and totally untouched as well. There weren't any apps installed from sources apart from Play Store. I'm able to access the stock recovery and tried clearing the cache but no respite. Whenever i try to factory format that, it gives an error of e:/could't mount /cache/recovery/xxxxxxxx errors.
I had read the forums for similar issues and got to know from this thread : http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492. The issue is cent percent same apart from the fact that i can access stock recovery.
Maybe @ravibhat & @lost101 can help us in this. I'm not worried about getting the data but bringing the phone back to life is more important for me !! Please help.
Click to expand...
Click to collapse
oh okay mate. I have been googling for such issue but the mostly suggested method is reset that I haven't done (not to lose data). Will wait for a day if I get any solution otherwise will reset it.
Let me know what happened to your phone. Hope it gets fixed soon

okay so here's the update. Was successful to take backup as per http://forum.xda-developers.com/showthread.php?t=2426426
And made factory reset after that but now it is still getting stuck on bootloop with M logo and powered by android screen. :crying:

I gave my phone to the service center guys today for reflashing the firmware. They were unable to do and suggested a motherboard replacement for which i obviously refused as they asked for ~INR 8000 as charges. So will start experimenting with it now and hope so i'm able to bring back to life.
What i'm planning is:
1. Flash Custom Recovery.
2. Wipe entire phone.
3. Flash stock ROM.
Will keep updating if i'm able to manage anything
EDIT : Did everything mentioned above but the phone is having same fate as before @krunalshah68. It gets stuck on the M Logo :crying: The internal memory although is being shown as 5xxx MB in TWRP unlike 0 Mb earlier.

Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​

BBThumbHealer said:
I gave my phone to the service center guys today for reflashing the firmware. They were unable to do and suggested a motherboard replacement for which i obviously refused as they asked for ~INR 8000 as charges. So will start experimenting with it now and hope so i'm able to bring back to life.
What i'm planning is:
1. Flash Custom Recovery.
2. Wipe entire phone.
3. Flash stock ROM.
Will keep updating if i'm able to manage anything
EDIT : Did everything mentioned above but the phone is having same fate as before @krunalshah68. It gets stuck on the M Logo :crying: The internal memory although is being shown as 5xxx MB in TWRP unlike 0 Mb earlier.
Click to expand...
Click to collapse
Damn mate ! I am going to follow same steps.
1) Unlock bootloader
2) Flash custom recovery if needed
3) Flash Custom rom
btw did you had unlocked the bootloader? @BBThumbHealer

lost101 said:
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
Click to expand...
Click to collapse
Thank you for you reply mate. :good:
I have somehow managed to backup data by script. but the problem is now even after resetting it is still stuck into bootloop.
But I am a bit confused here in steps.
1) Unlock bootloader
2) Flash custom recovery like TWRP and clear dalvik cache
3) and then flash any custom rom
correct me if I am wrong. I am going to follow these steps. @lost101

Phone started! yeeey!
So heres the update bro @BBThumbHealer.
Unlocked bootloader.
Flashed TWRP.
Cleared cache/dalvik cache/data.
Flashed http://forum.xda-developers.com/moto-g/development/nx-nexus-experience-rom-10-0-3-ambient-t3268555/
And device is working smooth as silk now and that too with Marshmallow !:fingers-crossed:
Let me know your status bro. Hope I could help you in some way

@krunalshah68 : Great to know bro that ur phone is as good as new now .. Many congratulations
As far as mine is concerned, did the following :
1. Unlocked bootloader
2. Flashed TWRP Recovery v3.0.2
3. Using mfastboot, flashed stock 5.0.2 and the phone booted up successfully finally !!
But now here's the catch, the phone once flashed up with a rom boots up fine for a single time only. Within that time frame, every damn thing works fine. Able to browse the net, configure apps & settings , blah blah etc etc ... every single thing. But as soon as i restart the phone, the rom fails to startup. It gets stuck on the boot loop.
Initially i thought the rom might have been corrupt, but then i tried the following roms:
1. Stock 5.1 Optimized as posted by @lost101
2. crDroid CM 13 6.0.1
And again the same fate was met.
And yes, i've been installing the above roms by flashing the zips in twrp. After every flash, cleared dalvik, cache & data.
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :

Hello guys, My phone is stuck on bootloop
I have already rooted device and now it is stuck on bootloop even the Recovery isn't opening. I know I would have to reset the phone with mfastboot but I want my internal storage to be backed up before doing all this Is there anyway to do so? Anyone here can help me out?

@sahil_arora05 : if you are able to access the bootloader mode, with the help of mfastboot, flash the latest version of twrp for moto g (mfastboot flash recovery recoveryfilename.img). After that, connect an otg disk to ur handset, boot into twrp and you'll be able to see all your files in the internal storage using the inbuilt file explorer for twrp. With that you can copy all ur data from the handset to the otg drive.

BBThumbHealer said:
@sahil_arora05 : if you are able to access the bootloader mode, with the help of mfastboot, flash the latest version of twrp for moto g (mfastboot flash recovery recoveryfilename.img). After that, connect an otg disk to ur handset, boot into twrp and you'll be able to see all your files in the internal storage using the inbuilt file explorer for twrp. With that you can copy all ur data from the handset to the otg drive.
Click to expand...
Click to collapse
I tried to do this stuff with fastboot but nothing happened. Phone is stuck at TWRP logo only.
by the way mfastboot or fastboot is same or not?

sahil_arora05 said:
I tried to do this stuff with fastboot but nothing happened. Phone is stuck at TWRP logo only.
by the way mfastboot or fastboot is same or not?
Click to expand...
Click to collapse
@sahil_arora05 Use mfastboot. It's been specifically designed for Moto devices as the regular fastboot is reportedly having some issues with Moto mobiles (read this on some XDA post itself)
@krunalshah68 : waiting for your suggestions to get my device up & running like urs

BBThumbHealer said:
@sahil_arora05 Use mfastboot. It's been specifically designed for Moto devices as the regular fastboot is reportedly having some issues with Moto mobiles (read this on some XDA post itself)
@krunalshah68 : waiting for your suggestions to get my device up & running like urs
Click to expand...
Click to collapse
Ok going to try that. Is there anyone who can provide me a link to download STOCK recovery for moto G xt1033. Can't find that.

@sahil_arora05 : http://forum.xda-developers.com/showthread.php?t=2649763 : Select XT1033 and from there u can choose the stock recovery for Asian model.

BBThumbHealer said:
@sahil_arora05 : http://forum.xda-developers.com/showthread.php?t=2649763 : Select XT1033 and from there u can choose the stock recovery for Asian model.
Click to expand...
Click to collapse
tThanks again buddy.

BBThumbHealer said:
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Click to expand...
Click to collapse
I already gave you the solution in post #6. Stop ignoring what I say and do it.

BBThumbHealer said:
@krunalshah68 : Great to know bro that ur phone is as good as new now .. Many congratulations
As far as mine is concerned, did the following :
1. Unlocked bootloader
2. Flashed TWRP Recovery v3.0.2
3. Using mfastboot, flashed stock 5.0.2 and the phone booted up successfully finally !!
But now here's the catch, the phone once flashed up with a rom boots up fine for a single time only. Within that time frame, every damn thing works fine. Able to browse the net, configure apps & settings , blah blah etc etc ... every single thing. But as soon as i restart the phone, the rom fails to startup. It gets stuck on the boot loop.
Initially i thought the rom might have been corrupt, but then i tried the following roms:
1. Stock 5.1 Optimized as posted by @lost101
2. crDroid CM 13 6.0.1
And again the same fate was met.
And yes, i've been installing the above roms by flashing the zips in twrp. After every flash, cleared dalvik, cache & data.
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Click to expand...
Click to collapse
Thank you @BBThumbHealer.
Damn man that's the basic steps that you are following and that too pretty neat and right. Even though it is causing issues then there might be some other hardware bug may be ! Hope your phone gets started soon!

Hi Guys,
phone : Moto G (XT1033), Falcon
- stuck in bootloop
- able to go to recovery
- unable to flash custom recovery such as twrp or cwm
- as suggested,
1. Unlocked the bootloader successfully, can see code status = 3 in recovery mode
mfastboot oem unlock <CODE>​2. Unable to flash twrp. It writes successfully but shows stock recovery only
mfastboot flash recovery twrp-3.0.2-0-falcon.img​3. so tried booting twrp using with success
mfastboot boot twrp-3.0.2-0-falcon.img​4. cleaned cache, dalvik etc.
5 using twrp, used ADB which enables MTP which let me transfer Android6.0.1_NX_R10.3.3_MotoG2013.zip to internal memory
6 Using twrp to flash ROM - Android6.0.1_NX_R10.3.3_MotoG2013.zip​
It seems it started installing but its been more than one hour and it seems its still doing something.
It has stuck at - "Patching system image unconditionally..."
is this normal? Did I miss anything?
Appreciate help in advance. thank you for your time...
Best Regards,
Jignesh

Moto G wont flash recovery wont flash new rom any help is appreciated

Hi guys in a new guy in xda Peace be upon you all .So here is the deal i have rooted quite a few phones and unlocked and got rid of softbrick .But this one is give me a headache .The owner gave me the phone he said he bought a 10 of those for his repair shop.I fixed the Htc One it was 2 nights of work barely any sleep.But never the less this device is moto g first generation the device is locked by pattern and wont let me in .If i slide to the camera at the lock screen camera stopped working .Fine i was like oke this would be easy its corrupted os .Next i tried to unlock the bootloader it failed with error battery was very weak like 5 %than i let it charge to about 80% and i managed to unlock the bootloader .Next i tried to install custom recovery to get rid of screen lock .when i go to recovery i got the screen with green android dude on his back with no comand then i hold volume up button for 10 sec and i tap the power button and it booted to android stock recovery .No matter what i do i couldnt get to install custom recovery it says finished without errors in cmd but i couldnt it always reverts me to stock recovery .Someone told me some stock roms after restart reinstalls stock recovery.Then i said fine i will do this in fastboot on cmd :fastboot boot recovery twrp.img and its the same it says downloading fine then goes and its the same stock recovery adb sideload wont work because usb debbuging is turned off i think because when i type adb devices it displays nothing emtpy so i even tried to get rid of whole stock rom but no go i tried fastboot erase data fastboot erase system fastboot erase cache it all displays sucesfull next reboot the same stock rom like i never touched anything i even tried factory reset in stock recovery it wont work it says done. like its completed but it doesnt do anything any help is apprecieted

Disclaimer: I am by no means an expert! But I have flashed twrp to 2 Moto Gs this week.
What I needed to do after flashing the recovery, was going immediately to recovery without rebooting.
When I rebooted after flashing the recovery I also got the 'no command' guy. But going to recovery from the bootloader menu after flashing worked for me.
Sent from my MotoG3 using Tapatalk

Thank you for replying i already tried that but it doesnt work i tried twrp cwm recovery you name it it doesnt work .Hm what i dont get i erased the whole stock os with fastboot erase data fastboot erase system and it still boots in to the os only tought that comes in to my mind is that the bootloader is corrupted messed up .Or is the eMMC it has errors .I dont know what to do i tried all or maybe the phone is stolen and it wont accept any permissions but i doubt it i get no errors in fastboot and trough flashing and factory reset all completed sucesfully .I dont know what to do .This is a tough one if i only had riff box jtag to try that Do you know some custom bootloader can you link me ?

You need to flash original stock 5.1 rom for your phone..From this link you have tutorial how to do it. You must do it because your partitions and file system is messed up..With this stock rom will be fixed bootloader and partitions..
After install stock rom you could install twrp again and any custom rom..

thank you kind sir i will try that thank you

why???
I done as it says in the tutorial cmd returns all okay when i finished the instalation the some old os locked screen same old recovery same thing nohing changed i done everything correct why mate do you know the reason i even put android 5.02 .Its like i never touched anything i done all right

Need help recovering my phone from bootloop after trying to update custom rom

Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc

Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now

twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.

Why nobody use orangefox?

is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable

joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you

Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.

CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?

K1 - So I think I may have bricked this thing. Looking for help, if any.

Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?

Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings

kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:

Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery

Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!

OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.

It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.

Mi 10 Ultra bricked! Help needed!

Hi all.
Have bricked my Mi 10 Ultra China Rom.
Have tried to flash a multi Xiaomi.eu Rom. Tried
TWRP. Tried to flash back to Stock Rom with XiaoMiTool V2.
Now, have Stock Recovery. Device hangs by the first white MI Logo in a Loop.
I can boot into Fastboot but adb devices don't shows
the Phone.
Well, any, any Help will be appreciated.
Helmut

if you can get into fastboot it's not bricked don't worry. I think your phone has no image at the moment or that stock image is not compatible in some way. I am laying the blame at Xiaomitoolv2 + stock rom - don't use it, you don't need it, let's forget that & try to get you to EU
This is the EU package to use:
https://www.androidfilehost.com/?fid=8889791610682929474
Use with this fastboot.exe http://www.mediafire.com/file/13j0xr5r4sq2c1w/fastboot.rar/file (unrar and rename it to exe)
if it is rebooting straight to recovery you should be able to wipe data cache partition (this is an option within recovery)- might be enough to fix. Heck, try that first!
Sounds like it is booting to a MIUI logo. OK, wait 20 minutes, if you see a little unlocked padlock icon you put that there by unlocking the phone - it is your clue the phone isn't dead. If it's not happening or that icon isn't unlocked? Go into recovery and wipe. (if it's chinese look at this https://www.devicesfaq.com/en/articles/reset-chinese-device) and see what happens next.
I would not worry about adb devices, for some reason this didn't work for me either as long as you can actually run commands in CMD and the phone responds. How are you putting on the EU ROM - as in, are you running the batch files they supplied; what happens now? (I want you to run the batch file because it wipes the phone and prepares it for you. I think you have a bad stock image there, you see)
If you go to fastboot mode and you're using the fastboot.exe above, I expect the EU package's batch file to work: windows_fastboot_first_install_with_data_format.bat
Because it starts with a full format. The only way it won't do anything is, I guess, drivers on your PC - and if that package still has a fastboot.exe in it, you *must* replace it, no ifs no buts
(Also FYI I was waiting at least 10 minutes on that logo when I first flashed the EU ROM. And that's when it WORKS. It is scary and you'll think it's dead... but it does just take a long time. Some people even had to reboot + wipe data at that point (wipe cache partition is sometimes all it ever needs to get a ROM working). So... Even if this WORKS you WILL be staring at that logo longer than you would like to!)
Try the batch files & come back please
------------------------------------
General status of this phone and its bootloops:
- if it boots straight into fastboot, it has no bootable image - sounds scary but you can just reflash the eu rom with a different fastboot.exe than the one bundled with the EU rom (using a different fastboot is not an optional step!). You can get stuck in this by using the latest fastboot.exe released; it is broken plain & simple
- if it boots into the stuck miui logo wait for like 20 minutes - seriously - anything else is within fastboot. At most might need to wipe the phone or factory reset (Can do this via cmd). Also look at https://www.devicesfaq.com/en/reset/xiaomi-mi-10-ultra
Also thinking about trying twrp again. You say "tried" this and the EU ROM but what actually happened?

Thanks for the fast Reply, ToneLa
Sorry for the Delay, had to charge the Phone!
Have done it like you described: Downloaded the special fastboot.exe, copied it in the "platform-tools-windows"-Folder of the ROM "xiaomi.eu_multi_MI10Ultra_20.9.3_v12-10-fastboot"
and start the Flash Process with the Batch File"windows_fastboot_first_install_with_data_format.bat". Right after the Phone restarts i pressed the Volume-Up Button and cleared the Caches
with "Wipe Data". Was a little of a Blind Flight because all was in Chinese!
After a couple of Minutes the Phone starts in my Language (German)!
Thanks a Lot for the Hint with the special fastboot.exe, i have tried this with the fastboot.exe from the ROM and from the ADB Developer Suite but with no Luck. Ended always in a Loop Boot.
Helmut

Sehr gut
Very happy this worked for you. The key is always fastboot.. The latest release is bugged, its not the ROM's fault, it's very annoying & will cause people grief!
But this is good news, it wasn't bricked, this is why I help people... It feels good when you help a bad situation
Enioy your phone, it will be like new!

helmut.eder said:
Hi all.
Have bricked my Mi 10 Ultra China Rom.
Have tried to flash a multi Xiaomi.eu Rom. Tried
TWRP. Tried to flash back to Stock Rom with XiaoMiTool V2.
Now, have Stock Recovery. Device hangs by the first white MI Logo in a Loop.
I can boot into Fastboot but adb devices don't shows
the Phone.
Well, any, any Help will be appreciated.
Helmut
Click to expand...
Click to collapse
Format data after flash eu rom

dungnghien said:
Format data after flash eu rom
Click to expand...
Click to collapse
Thanks for the Hint! ??

Perhaps...the Updater App on my Phone shows an Update to 20.9.17!
Can't see if this is a Multi Language Rom or China.
Does the Updater now shows only Equal Rom like the installed?
Thanks in advance
Helmut

helmut.eder said:
Perhaps...the Updater App on my Phone shows an Update to 20.9.17!
Can't see if this is a Multi Language Rom or China.
Does the Updater now shows only Equal Rom like the installed?
Thanks in advance
Helmut
Click to expand...
Click to collapse
Updater App doesn't work without TWRP or flash manually. You can reboot to recovery and if you have TWRP you can install it that way (but wipe too within TWRP)
I'm on that one. Weekly and stable are different... Both are multi language, that's the point of the EU Rom
Few bugs in each. I don't think you'll lose anything moving.
But you'll need to do it in TWRP so get that sorted! Flash it like you've done before... And if you switch between them, wipe to prevent errors
I like the weekly rom, some bugs. Videos are green if you use stabilisation. Settings search crashes if you are too slow!
But brilliant.
I would say install weekly if you want to be on the cutting edge and are prepared for some small bugs.
Stable is for 99% of users
And really this is where you want to be. Any new rom will need TWRP then root. I also rooted my phone with latest magisk
Root is great but some banking apps don't work. It's a personal choice, don't rush into it

Thanks for the Insight, ToneLa.
Will stay at the Moment with the 20.9.3.:angel:
Maybe later i will try an Update with the fastboot.exe
and Update Batch File from the Rom.
Thanks for your Efforts.
Helmut

helmut.eder said:
Thanks for the Insight, ToneLa.
Will stay at the Moment with the 20.9.3.:angel:
Maybe later i will try an Update with the fastboot.exe
and Update Batch File from the Rom.
Thanks for your Efforts.
Helmut
Click to expand...
Click to collapse
That rom is great. Weekly is hardly different...!
I did not use the batch files for updating. If you want to update, put on Chinese TWRP, download the update via updater and when at 100% do Reboot to Recovery option (it won't install).
Install in TWRP then wipe and reboot (I didn't even need to wipe... But it's good to)
Going forward the usual way with the EU ROM is via TWRP so it's good to have it
TWRP isn't official yet, suppose you know we are using an odd Chinese version we set to English.. Can dig out the link if you have no idea what I'm talking about

Hi all, I have the same problem: I have a MI Ultra, unlocked the bootloader (waiting for a week), and now I am stuck in a bootloop. I tried what you wrote:
Downloaded the ROM, replaced the fastboot.exe, used the batch file (seem to work without errors), Volume up on first restart, wipe, but I am back in a loop restarting every 2 minutes.
No problem to get into TWRP or Fastboot.
What shall I do?
EDIT::::: No idea why, tried the same thing again, now it works....

Always best to format, not just wipe on first boot. The bat file should do it when using a fastboot ROM, it may not have fully done that, hence the bootloop. But when you use your first .zip file flash from twrp, format data, not just wipe and again if you change ROM branches between stable and weekly.

Sathelp said:
Always best to format, not just wipe on first boot. The bat file should do it when using a fastboot ROM, it may not have fully done that, hence the bootloop. But when you use your first .zip file flash from twrp, format data, not just wipe and again if you change ROM branches between stable and weekly.
Click to expand...
Click to collapse
Big thank you all that contributed to that thread, I have now a great phone with German ROM.
Would you recommend me to use stable or weekly? I have weekly now and everything seems to work fine...

OnkelAlbert said:
Big thank you all that contributed to that thread, I have now a great phone with German ROM.
Would you recommend me to use stable or weekly? I have weekly now and everything seems to work fine...
Click to expand...
Click to collapse
Weekly gets the latest features, but there's a slight risk that a new weekly release might contain bugs that went unnoticed during internal testing by the devs.
The way I do it, is that I'll run weekly - and everytime a new weekly version gets released, I'll wait about 4 days before updating to it.
That's usually enough time for any critical bugs to surface.

Please remember that if you change branches between stable and weekly, you must format data as there may have been a change of partition tables and you could end up with bootloop again.

ToneLa said:
if you can get into fastboot it's not bricked don't worry. I think your phone has no image at the moment or that stock image is not compatible in some way. I am laying the blame at Xiaomitoolv2 + stock rom - don't use it, you don't need it, let's forget that & try to get you to EU
This is the EU package to use:
https://www.androidfilehost.com/?fid=8889791610682929474
Use with this fastboot.exe http://www.mediafire.com/file/13j0xr5r4sq2c1w/fastboot.rar/file (unrar and rename it to exe)
if it is rebooting straight to recovery you should be able to wipe data cache partition (this is an option within recovery)- might be enough to fix. Heck, try that first!
Sounds like it is booting to a MIUI logo. OK, wait 20 minutes, if you see a little unlocked padlock icon you put that there by unlocking the phone - it is your clue the phone isn't dead. If it's not happening or that icon isn't unlocked? Go into recovery and wipe. (if it's chinese look at this https://www.devicesfaq.com/en/articles/reset-chinese-device) and see what happens next.
I would not worry about adb devices, for some reason this didn't work for me either as long as you can actually run commands in CMD and the phone responds. How are you putting on the EU ROM - as in, are you running the batch files they supplied; what happens now? (I want you to run the batch file because it wipes the phone and prepares it for you. I think you have a bad stock image there, you see)
If you go to fastboot mode and you're using the fastboot.exe above, I expect the EU package's batch file to work: windows_fastboot_first_install_with_data_format.bat
Because it starts with a full format. The only way it won't do anything is, I guess, drivers on your PC - and if that package still has a fastboot.exe in it, you *must* replace it, no ifs no buts
(Also FYI I was waiting at least 10 minutes on that logo when I first flashed the EU ROM. And that's when it WORKS. It is scary and you'll think it's dead... but it does just take a long time. Some people even had to reboot + wipe data at that point (wipe cache partition is sometimes all it ever needs to get a ROM working). So... Even if this WORKS you WILL be staring at that logo longer than you would like to!)
Try the batch files & come back please
------------------------------------
General status of this phone and its bootloops:
- if it boots straight into fastboot, it has no bootable image - sounds scary but you can just reflash the eu rom with a different fastboot.exe than the one bundled with the EU rom (using a different fastboot is not an optional step!). You can get stuck in this by using the latest fastboot.exe released; it is broken plain & simple
- if it boots into the stuck miui logo wait for like 20 minutes - seriously - anything else is within fastboot. At most might need to wipe the phone or factory reset (Can do this via cmd). Also look at https://www.devicesfaq.com/en/reset/xiaomi-mi-10-ultra
Also thinking about trying twrp again. You say "tried" this and the EU ROM but what actually happened?
Click to expand...
Click to collapse
hello, i have problems with my 10 ultra. Person I'm new to this, I have downloaded the zip and the fasboot exe but now I don't know how to do it. There is a youtube type tutorial or manual to do steps. thanks i am somewhat lost. i need help

Here is my guide.... https://mega.nz/file/6UAhXCxZ#Np2KwhMnl8obmOvp4b-2R9ajo0zrtz3vwefy-Ya3PLs
Let us all know how you get on. We're here to help you, so no question is a silly question

ToneLa said:
if you can get into fastboot it's not bricked don't worry. I think your phone has no image at the moment or that stock image is not compatible in some way. I am laying the blame at Xiaomitoolv2 + stock rom - don't use it, you don't need it, let's forget that & try to get you to EU
This is the EU package to use:
https://www.androidfilehost.com/?fid=8889791610682929474
Use with this fastboot.exe http://www.mediafire.com/file/13j0xr5r4sq2c1w/fastboot.rar/file (unrar and rename it to exe)
if it is rebooting straight to recovery you should be able to wipe data cache partition (this is an option within recovery)- might be enough to fix. Heck, try that first!
Sounds like it is booting to a MIUI logo. OK, wait 20 minutes, if you see a little unlocked padlock icon you put that there by unlocking the phone - it is your clue the phone isn't dead. If it's not happening or that icon isn't unlocked? Go into recovery and wipe. (if it's chinese look at this https://www.devicesfaq.com/en/articles/reset-chinese-device) and see what happens next.
I would not worry about adb devices, for some reason this didn't work for me either as long as you can actually run commands in CMD and the phone responds. How are you putting on the EU ROM - as in, are you running the batch files they supplied; what happens now? (I want you to run the batch file because it wipes the phone and prepares it for you. I think you have a bad stock image there, you see)
If you go to fastboot mode and you're using the fastboot.exe above, I expect the EU package's batch file to work: windows_fastboot_first_install_with_data_format.bat
Because it starts with a full format. The only way it won't do anything is, I guess, drivers on your PC - and if that package still has a fastboot.exe in it, you *must* replace it, no ifs no buts
(Also FYI I was waiting at least 10 minutes on that logo when I first flashed the EU ROM. And that's when it WORKS. It is scary and you'll think it's dead... but it does just take a long time. Some people even had to reboot + wipe data at that point (wipe cache partition is sometimes all it ever needs to get a ROM working). So... Even if this WORKS you WILL be staring at that logo longer than you would like to!)
Try the batch files & come back please
------------------------------------
General status of this phone and its bootloops:
- if it boots straight into fastboot, it has no bootable image - sounds scary but you can just reflash the eu rom with a different fastboot.exe than the one bundled with the EU rom (using a different fastboot is not an optional step!). You can get stuck in this by using the latest fastboot.exe released; it is broken plain & simple
- if it boots into the stuck miui logo wait for like 20 minutes - seriously - anything else is within fastboot. At most might need to wipe the phone or factory reset (Can do this via cmd). Also look at https://www.devicesfaq.com/en/reset/xiaomi-mi-10-ultra
Also thinking about trying twrp again. You say "tried" this and the EU ROM but what actually happened?
Click to expand...
Click to collapse
Hi, I'm totally stuck... my phone just reboots in TWRP every time no matter what I try.
I just went through the instructions above as a final hope.... but no... completed and rebooted in TWRP...
Can anyone advise how to get out of this?
Thanks in advance.
Update after trying everything I could find on the web and just short Frisbeeing the phone out of the window I reinstalled the Chinese factory recovery, cleared the data .... rebooted and it worked!

Did you format after installing the ROM in twrp? Not just wipe but a proper format where you have to type yes to continue?
Please don't panic, your phone will be fine. Just install the ROM, format and reboot system. Here is a link to my guide.
File on MEGA
mega.nz

Hi guys, I just got my mi 10 ultra today, and now I want to change the rom to eu since I live in Europe... but I am afraid because I see that there are some camera changes in this custom room..? can anyone test out official and custom and confirm it there are such differences because I bought the phone just for it's cam