TWRP Freeze - close call? - Nokia 6.1 (2018) Questions & Answers

Hi,
I had the bootloader unlocked on my 6.1 today.
Seemed to go well and guy was ver y professional.
Anyway connected my pc, and through adb rebooted to bootloader.
Phone entered download/fastboot mode.
Was recognised by my pc so I then booted into a temporary twrp - I got the image from the twrp site as compatible with the device.
Up came the twrp opening screen
--and that was that?
Did not go beyond this screen, and phone became completely unresponsive- not even holding power button for a minute helped.
Oh dear.
Fortunately, I left it for a couple of minutes and then held power and volume up for quite a while, and ''whew'' it booted fine, and is back to normal?
ANy ideas what I did wrong?
Many Thanks
pootler

pootler said:
Hi,
I had the bootloader unlocked on my 6.1 today.
Seemed to go well and guy was ver y professional.
Anyway connected my pc, and through adb rebooted to bootloader.
Phone entered download/fastboot mode.
Was recognised by my pc so I then booted into a temporary twrp - I got the image from the twrp site as compatible with the device.
Up came the twrp opening screen
--and that was that?
Did not go beyond this screen, and phone became completely unresponsive- not even holding power button for a minute helped.
Oh dear.
Fortunately, I left it for a couple of minutes and then held power and volume up for quite a while, and ''whew'' it booted fine, and is back to normal?
ANy ideas what I did wrong?
Many Thanks
pootler
Click to expand...
Click to collapse
Ok so quick update
I decided to use a different recovery
I was installing lineages 17, so used their recovery.
Everything worked fine?

HI,
I obtained a nokia 6.1 recently.
I had the bootloader unlocked.
I then went to flash the latest ( official) lineage 17
I did all the usual stuff ( i am not a stranger to installing custom roms ), and then tried to temporarily boot into twrp, in order to flash the lineage zip.
I was using the twrp as recommended on lineage site for this device ( nokia 6.1 TA 1050 )
For some reason, after using fastboot boot twrp.img, ( I renamed the image) the phone just booted back to android one screen.?
I could use power/vol up, to get out and back to existing installation, but nothing else.
I then tried temporarily booting the lineage recovery. ( according to the lineage installation instructions)
This involves using a combination of ''fastboot flash boot'' and hardware keys to get there
This worked fine - and I was able to sideolad the lineage zip.
Problem is, if I want to flash images , and do other stuff the lineage recovery cant, i need twrp ( even temporarily).
After installing lineage 17, I tried again to get into twrp, with the same (non) results.
I was wonderinfg if I was getting confused about slots.
I believed that booting twrp temporarily would boot to the right slot? - maybe not.
I then decided to do fastboot flash boot_a, ( etc, ) and then fastboot flash boot_b, ( etc ) to make sure it would boot off either slot. With hindsight, this was dumb
That got me twrp., but lost me the ability to boot into the lineage installation.
After a bit of a panic, I managed to get back to my lineage install.
I have tried since to temporarily boot twrp ( not to both slots ), and am still getting the same results- it boots to the android one screen, and just sits there.
But - if I try to get to recovery using the hardware buttons, I can get to Lineage recovery - which I find strange, because I thought official lineage packages did not install their recovery by default?
Makes me wonder when I thought I had booted lineage recovery temporarily, that maybe I hadn't, and I just booted into a pre installed recovery using the hardware method.
I am probably doing something stupid ( quite common for me ), can anyone enlighten me ?
Many Thanks
pootler

O.k
So I think I found a method in the thread below this - on the third page
I will chek iif it works
Pootler

pootler said:
O.k
So I think I found a method in the thread below this - on the third page
I will chek iif it works
Pootler
Click to expand...
Click to collapse
Yes - it appears that if you cannot boot into twrp temporarily , then this worked for me!
--at your own risk---
fastboot flash recovery <filename>.img
This will FAIL - but ignore and then right after,
fastboot boot <filename> .img
Voila - boots into TWRP temporarily.
Cheers
pootler

I wanted to ask what firmware you are running because I am having the exact same issue on my Pixel 3. I tried the final method you outlined but no luck. I'm running stock Android 10 build QQ3A.200805.001. I have the google USB driver from the platform sdk tools installed, I have ADB added to my $Path.
fastboot boot C:\twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.251s]
Booting OKAY [ 3.451s]
Finished. Total time: 3.784s
Something strange happens, it looks like the reboot to TWRP screen comes on for an instant before going to the unlocked bootloader warning message. Then it proceeds to boot into the android screen instead of the recovery. No idea why, could it be the ADB drivers?

MigueTK said:
I wanted to ask what firmware you are running because I am having the exact same issue on my Pixel 3. I tried the final method you outlined but no luck. I'm running stock Android 10 build QQ3A.200805.001. I have the google USB driver from the platform sdk tools installed, I have ADB added to my $Path.
fastboot boot C:\twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.251s]
Booting OKAY [ 3.451s]
Finished. Total time: 3.784s
Something strange happens, it looks like the reboot to TWRP screen comes on for an instant before going to the unlocked bootloader warning message. Then it proceeds to boot into the android screen instead of the recovery. No idea why, could it be the ADB drivers?
Click to expand...
Click to collapse
HI,
I am sorry but my knowledge is really limited in this area - I wish you luck

pootler said:
HI,
I am sorry but my knowledge is really limited in this area - I wish you luck
Click to expand...
Click to collapse
Thanks for the reply, I still haven't figured it out and am running a manually patched boot image for magisk without a recovery, fastbootd is "enough". Another weird thing is If I installed a custom Rom certain pixel features would be lost such as the OCR and lens integration into the recents menu, pixel stand standby and wallpapers. I love the features of a custom Rom but the overview copy and paste functions are a must have for me.

Well, I use Raghu Varma's unofficial TWRP. It works like a charm, I've had no issues with it so far. Just be careful to choose the correct one between the build for Android 10 and the one for Android 11 -- I think that got me into trouble once, can't remember clearly.

Related

Nexus 7 completely bricked?

So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Cortimi said:
So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Click to expand...
Click to collapse
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
someolddude said:
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
Click to expand...
Click to collapse
WiFi model, fastboot and adb are fine, no toolkits.
Cortimi said:
WiFi model, fastboot and adb are fine, no toolkits.
Click to expand...
Click to collapse
Get the toolkit by wugfresh and you should be able to restore it.
someolddude said:
Get the toolkit by wugfresh and you should be able to restore it.
Click to expand...
Click to collapse
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.283s]
finished. total time: 1.412s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 754455404 bytes
error: update package missing system.img
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
Click to expand...
Click to collapse
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Cortimi said:
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Click to expand...
Click to collapse
Same problem with mine, cm11 as well.
I like some of the CM features but ever device Ive flashed and had trouble with it has been when Ive went with "Cyanide Mod"
You figure something out, please let me know and I will do the same.
I've got the LTE but my daughter has the WiFi only and is also unlocked. I can make a bone stock backup of here's which is on 4.4.4 if you want to try and restore it to yours.

[Q&A] [RECOVERY][h815] TWRP 2.8.6.0 touch recovery [2015-06-02]

Q&A for [RECOVERY][h815] TWRP 2.8.6.0 touch recovery [2015-06-02]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][h815] TWRP 2.8.6.0 touch recovery [2015-06-02]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
TWRP not installing?
Hi all!
I have some what of a problem here.
I have an international G4 and I've unlocked it with the unlock.bin. It was successful and it says bootloader unlocked during startup.
I then flash TWRP in fastboot with:
fastboot flash recovery twrp-2.8.6.0-h815.img
With the response:
target reported max download size of 536870912 bytes
sending 'recovery' (31796 KB)...
OKAY [ 1.121s]
writing 'recovery'...
OKAY [ 0.297s]
finished. total time: 1.418s
I then reboot the device and then turn it off. I've then tried a bunch of different combinations to get in to recovery without luck.
Never mind i thought and allowed the phone to boot and then run: adb reboot recovery
This rebooted the device to a black screen with a android on his back and a red triangle with an exclamation mark.
I've tried flashing the device with TWRP in fastboot twice and it says OKAY but it doesn't seem to work?
Am I an complete idiot and are missing something here?
---------- Post added at 07:33 AM ---------- Previous post was at 06:53 AM ----------
I got it working, sort of...
I ran Fastboot boot twrp-2.8.6.0-h815.img
This brought me in to TWRP. From there i flashed supersu.zip and twrp-2.8.6.0-h815.img.
This apparently worked. Although I still can't figure out how to get in to TWRP through keypresses during boot. All I've found is to hold volume down and power, when the LG logo comes I release them for 1 second and press again. Sometimes the notification light comes on blue and the phone starts up in safe mode but no recovery.
But since I flashed supersu I've downloaded the TWRP-app from playstore and restart to recovery from the app, works great.
So, for anyone else having this problem. Boot the device from the image and flash supersu and recovery from there.
But the question about keycombos for recovery during boot still stands. Sure the app works but what about if I f-ck up and get bootloops, then I'm screwed
Swe.sharkie said:
Hi all!
I have some what of a problem here.
I have an international G4 and I've unlocked it with the unlock.bin. It was successful and it says bootloader unlocked during startup.
I then flash TWRP in fastboot with:
fastboot flash recovery twrp-2.8.6.0-h815.img
With the response:
target reported max download size of 536870912 bytes
sending 'recovery' (31796 KB)...
OKAY [ 1.121s]
writing 'recovery'...
OKAY [ 0.297s]
finished. total time: 1.418s
I then reboot the device and then turn it off. I've then tried a bunch of different combinations to get in to recovery without luck.
Never mind i thought and allowed the phone to boot and then run: adb reboot recovery
This rebooted the device to a black screen with a android on his back and a red triangle with an exclamation mark.
I've tried flashing the device with TWRP in fastboot twice and it says OKAY but it doesn't seem to work?
Am I an complete idiot and are missing something here?
---------- Post added at 07:33 AM ---------- Previous post was at 06:53 AM ----------
I got it working, sort of...
I ran Fastboot boot twrp-2.8.6.0-h815.img
This brought me in to TWRP. From there i flashed supersu.zip and twrp-2.8.6.0-h815.img.
This apparently worked. Although I still can't figure out how to get in to TWRP through keypresses during boot. All I've found is to hold volume down and power, when the LG logo comes I release them for 1 second and press again. Sometimes the notification light comes on blue and the phone starts up in safe mode but no recovery.
But since I flashed supersu I've downloaded the TWRP-app from playstore and restart to recovery from the app, works great.
So, for anyone else having this problem. Boot the device from the image and flash supersu and recovery from there.
But the question about keycombos for recovery during boot still stands. Sure the app works but what about if I f-ck up and get bootloops, then I'm screwed
Click to expand...
Click to collapse
have you tried opposite button - i mean to use volume up and power ?
Yup.
Ok, this is what I've tried...
1. Hold power + vol down, release when LG logo comes and hold again. -> Sometimes nothing, sometimes safemode (probably timing with keys)
2. Hold power + vol down, don't release -> Nada
3. Hold power + vol down, release power when LG logo comes. -> Factory data reset
4. Hold power + vol up, release when LG logo comes and hold again. -> Nothing.
5. Hold power + vol up, don't release -> Nothing.
6. Hold power + vol up, release power when LG logo comes. -> Nothing.
7. Hold vol up + vol down (not power) -> IMEI Display with barcode.
8. ?
I've experimented with a lot of timings and can't always reproduce these results. Factory data reset only worked once for instance so I'm thinking timing is very important here.
I'll keep trying and update if I find anything....
...
iateyourmic said:
...
Click to expand...
Click to collapse
somboons said:
Click to expand...
Click to collapse
That worked!
Exactly like he showed on the video. Choose yes and it asks if you are sure, choose yes again and boom your in TWRP. Haha weird way to get there but sure works....
Thanks a million :good:
somboons said:
Click to expand...
Click to collapse
Edit: never mind.... Though this video was another purpose.. Thanks anyway
great post!
Thanks !
thank you!
Perfect !
Works first time .
thank you a lot
Hello,
I'am trying to get root on my lg g4. I do have the h815 version with an unlocked bootloader. My problem is that flashing twrp is not working. Fastboot is saying that everything went allright, but booting into recovery is not working for me.
If I use adb to boot to recovery, I only see an android robot with a red warning sign. That means that the flash was not done correctly. When I use the button combination to boot into recovery, I do see a robot with an animated gear for a short time., but end up on stock rom.
I have tried the current version 2.8.7.0 and the oldest available 2.8.6.0 to no avail.
Could it be that it is not working, cause of some updates I have installed? So far I done every single system update and whatever lg provided.
Edit: I fixed my problem! I had to directly boot into recovery after flashing twrp. Which I had never done before...
trouble
guys i have some trouble
i unlock bootloader as the official guide says
now i install twrp i install it but i click on reboot and when twrp ask me to root i clicked on ( no)
so i tried to go again in twrp to install supersu but with key combination won't enter and if in adb i write " adb reboot recovery " a dead android with box open appear
if i try to flash again twrp
i write " adb reboot fastboot" it won't go in fastboot and reboot normally
how can i solve it?
hi
just a little Q
when i do a nandroid in twrp i have this:
Boot (40mb)
System (3150mb)
*System Image (4140mb)
Data (6380mb)
Cache (1mb)
Recovery (40mb)
I dont have to backup *System Image?
What is that for?
Thanks, for make the ? to a !
Sent from my unlocked and rooted LG-H815
please guys, i have google it and i dont find any answer about it!
Sent from my unlocked and rooted LG-H815
*bump
does not anyone know what "system image" is and if i need to include that in a nandroid?
Sent from my unlocked and rooted LG-H815
System image is everything bar data as far as I know just an alternative to doing system and stuff all separate
Sent from my LG-H815 using Tapatalk
delete me! please
Hey there,
I have the same problem like some other users posted already. I flashed TWRP with unlocked bootloader and everytime I try to boot into recovery via "adb reboot recovery" I get the little android with a red triangle. Then I tried to do it with hardware buttons, clicked 'yes' and 'yes' when I was asked to wipe and then....lol....it wiped my phone. No data left. I really would like to install super user, but I'm on anroid Marshmallow already and the rooting process doesn't work for me. So I have no Twrp and no root. Any guide on how to install TWRP properly in my situation would be appreciated gratefully
Cheers

Recovery boots to black screen, can't flash on OP 5T

I have an old OP5T that is still on an older version of LOS, so I thought I'd start from scratch and first flash the Lineage Recovery instead of TWRP (an equally old version, but still working at this point).
USB debugging is active and OEM unlock enabled.
However, when I flash the image with
fastboot flash recovery lineage-17.1-20201229-recovery-dumpling.img
I get this output:
Sending 'recovery' (26685 KB) OKAY [ 0.698s]
Writing 'recovery' OKAY [ 0.252s]
Finished. Total time: 0.951s
First thing I found weird is how it took less than a second. Is it supposed to be that fast? It obviously did something:
When I try to boot to recovery now, I only get a black screen and a solid white notification LED (after the boot splash).
Same thing when I use the TWRP image instead: terminal shows it's finished in a second, but recovery wont boot afterward.
fastboot boot leads to the same black screen.
I tried it from two different computers, one with Fedora and the other with Windows; same thing happens on both.
The installed OS still works just fine, it's an old version though (and OTA updates don't work for some other reason).
Anyone have an idea what's wrong? What else could I try to get a working recovery?
Hi Mike
I had this very same issue. Regardless of what recovery (codeworkx, blu_spark, LOS etc.) I tried (I was on TWRP 3.2.x before) it always ended up with the solid white led. Eventually I got at least stock recovery from here working again (I was copying the recovery.img to internal storage, then booting to bootloader and went from there to recovery). This then allowed me to get adb sideload back so I could upgrade my old LOS 15.1 to OOS 10.0.1 (via 5.1.3, then 5.1.4, 5.1.7, 9.0.11 and finally 10.0.1). Once I was on the latest OOS I went back to fastboot bootloader and then flashed recovery with a more recent TWRP image (I took twrp-3.3.1-x_blu_spark_v9.101_treble-op5_op5t.img). Not sure if all those steps are actually required (I think you need at least 5.1.3 and 5.1.4 to get around this treble/vendor partition issue if you are on a version that didn't have the vendor partition yet) but this is how I got to a working TWRP recovery again. Hopefully this is of any help to you.
Cheers

Xiaomi Mi 10T keeps booting into fastboot

Hello guys, I recently formatted data on my phone to fix a bootloop I had. After fixing everything, SIM card and wifi was not working, I downloaded the Official Stock ROM of my phone and flashed bluetooth, modem, dsp and dtbo. The original plan was to run "flash_all_except_storage.bat" but that kept throwing errors. After I flashed those things I booted successfully and unlocked my phone. Problem is Wifi still doesn't work. So once again got into fastboot, tried running "flash_all_except_storage.bat", once again it threw an error, so I restarted my phone and ever since I can't boot into system. Whenever I restart it goes straight into fastboot, Power off and on again goes to fastboot, I can boot into TWRP, rebooting from there still goes into fastboot mode. I fix a problem and 2 more take it's place, I really need your help here.
Thanks a lot !
Edit:
Fix Attempt 1 (FAILED): I tried formating data through TWRP as I read online, it did not work
Attempt 2 (FAILED): Used
Code:
fastboot continue
and got this error:
Code:
Resuming boot FAILED (remote: 'Failed to load image from partition: No Media')
fastboot: error: Command failed
Attempt 3 (HALF FIX): After some digging I realized after a failed attempt to run "flash_all_except_storage.bat", the boot was erased. I tried flashing only the boot.img and the phone booted up with the wifi working as well. Problem is after a reboot I go back into fastboot and I have to flash boot.img again to boot into system.
Here is recovery.log Pastebin
Leonniar said:
Hello guys, I recently formatted data on my phone to fix a bootloop I had. After fixing everything, SIM card and wifi was not working, I downloaded the Official Stock ROM of my phone and flashed bluetooth, modem, dsp and dtbo. The original plan was to run "flash_all_except_storage.bat" but that kept throwing errors. After I flashed those things I booted successfully and unlocked my phone. Problem is Wifi still doesn't work. So once again got into fastboot, tried running "flash_all_except_storage.bat", once again it threw an error, so I restarted my phone and ever since I can't boot into system. Whenever I restart it goes straight into fastboot, Power off and on again goes to fastboot, I can boot into TWRP, rebooting from there still goes into fastboot mode. I fix a problem and 2 more take it's place, I really need your help here.
Thanks a lot !
Edit:
Fix Attempt 1 (FAILED): I tried formating data through TWRP as I read online, it did not work
Attempt 2 (FAILED): Used
Code:
fastboot continue
and got this error:
Code:
Resuming boot FAILED (remote: 'Failed to load image from partition: No Media')
fastboot: error: Command failed
Attempt 3 (HALF FIX): After some digging I realized after a failed attempt to run "flash_all_except_storage.bat", the boot was erased. I tried flashing only the boot.img and the phone booted up with the wifi working as well. Problem is after a reboot I go back into fastboot and I have to flash boot.img again to boot into system.
Here is recovery.log Pastebin
Click to expand...
Click to collapse
Can you flash full rom with mi flash tool
Rares6567 said:
Can you flash full rom with mi flash tool
Click to expand...
Click to collapse
Already did, it didn't work...
Leonniar said:
Already did, it didn't work...
Click to expand...
Click to collapse
Maybe is some motherboard issues?
I don't believe so. The problem I originally had was that after a restart the phone was booting into fastboot. But if I didn't restart the phone was working fine, cellular, wifi google services everything. So in order to fix that I flashed the full stock rom and that's how I ended up in the restart loop in the first place.
https://forum.xda-developers.com/t/decrypting-xiaomi-mi10t-pro-internal-storage.4544271/page-2#posts
Here are all the details, I started from a completely different problem and ended up here. They entire process I took is in that thread
Leonniar said:
I don't believe so. The problem I originally had was that after a restart the phone was booting into fastboot. But if I didn't restart the phone was working fine, cellular, wifi google services everything. So in order to fix that I flashed the full stock rom and that's how I ended up in the restart loop in the first place.
https://forum.xda-developers.com/t/decrypting-xiaomi-mi10t-pro-internal-storage.4544271/page-2#posts
Here are all the details, I started from a completely different problem and ended up here. They entire process I took is in that thread
Click to expand...
Click to collapse
There is no volume buttons problem?
If no maybe you should reflash whole phone, fastboot, recovery, all, using edl ig.... I don't have this phone or any Snapdragon phone, so I don't really know....
Yeah I did, I used the flash_all.bat that comes with the ROM file and pretty much replaced everything. I tried to run it a couple of times and it failed mostly but I was able to run it twice I think (without changing anything, just running it again and again at some point it worked)
Leonniar said:
Yeah I did, I used the flash_all.bat that comes with the ROM file and pretty much replaced everything. I tried to run it a couple of times and it failed mostly but I was able to run it twice I think (without changing anything, just running it again and again at some point it worked)
Click to expand...
Click to collapse
So then why your phone goes to fastboot?
I really don't know, after running flash_all the second time now my phone is stuck in a restart loop. Shows the MI logo and restarts. I can manually boot to recovery or fastboot but if I leave it on it's own it keeps turning on and off
Leonniar said:
I really don't know, after running flash_all the second time now my phone is stuck in a restart loop. Shows the MI logo and restarts. I can manually boot to recovery or fastboot but if I leave it on it's own it keeps turning on and off
Click to expand...
Click to collapse
It seems that this a software bug ig, can you try go to recovery and flash the rom?
I could try but I am not sure how to do that. My rom comes in a .tgz format and not .zip and all guides mention you need a .zip file
Leonniar said:
I could try but I am not sure how to do that. My rom comes in a .tgz format and not .zip and all guides mention you need a .zip file
Click to expand...
Click to collapse
So where u downloaded the fastboot rom, there is a recovery rom too :
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Be sure u download the recovery rom not fastboot.
Btw use your miui version u had
Tho I'm not 100% sure if you flashed the fastboot rom correctly, did u :
1. Open MiFlashTool : download the tool from here if you don't have it ---> https://xiaomiflashtool.com/
2. Select your rom ( make sure your path to the rom isn't long and the folder/folders don't have long names )
3. Connect your phone
4. Click Refresh ( to make your device appear)
5. And click flash
I didn't do it with MiFlashTool because it kept throwing errors at me whenever I launched it so I tried the flash_all.bat batch file that runs cmd commands and flashes everything. the ROM I installed was the fastboot version. The official website on the recovery ROM stated that "This page shows a single update only" so I assumed it's just an update and not the full ROM. I was also told I should use the fastboot variant in the above mentioned thread
Leonniar said:
I didn't do it with MiFlashTool because it kept throwing errors at me whenever I launched it so I tried the flash_all.bat batch file that runs cmd commands and flashes everything. the ROM I installed was the fastboot version. The official website on the recovery ROM stated that "This page shows a single update only" so I assumed it's just an update and not the full ROM. I was also told I should use the fastboot variant in the above mentioned thread
Click to expand...
Click to collapse
Ok so to fix the error : go to miflashtool folder and create a new folder called : log
Fixed the start up error, I get the screen that says "Please install driver", I press Install and I get this:
https://prnt.sc/I53g6bs_8i5w
Pressing ok gets me back to the "Please install driver" screen
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Rares6567 said:
It seems that this a software bug ig, can you try go to recovery and flash the rom?
Click to expand...
Click to collapse
flashing miui_APOLLOEEAGlobal_V12.5.4.0.RJDEUXM_451a2324af_11.0.zip from stock recovery is good idea, you can do this from MicroSD card to circumvent any usb issues you are obviously facing on fastboot.
Leonniar said:
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Click to expand...
Click to collapse
So it worked?
This "error" isn't an "error" so don't worry about it
Leonniar said:
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Click to expand...
Click to collapse
This error is normal since you are not re-locking the bootloader.
If some functions are inoperative.
Try to flash the same rom (fastboot) that you had when you bought the phone, probably an A11.
Use clean all(flash_all.bat).
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

Question HELP, device stuck in bootloop, tried every method.

Hi everyone,
maybe someone here might help me. I was on bliss rom and my phone suddenly froze yesterday.
And oh boy did that started a very long day of messing with miflash tool and twrp.
The situation right now is like this,
I have full access to TWRP, and fastboot and mi flash tool.
I tried flashing stock rom with mi flash, got success with no error and yet still stuck in frozen POCO logo.
Tried flashing with TWRP couple of ROMs with correct fw and still got POCO logo stuck.
Tried sideloading with adb some ROMs and same results, stuck on POCO logo.
Also tried to use flash_all bat without mi flash tool, and it boots me to MIUI recovery...
I can always come back to fastboot and boot to TWRP and tried miflashtool many time , I always result in success (0) but nothing works...
Is there anything I'm missing?
Of course I waited at least half an hour every time on POCO logo beacuse I know It can take some time for first boot but nothing happens, If I had to guess is there a possibility that the Storage it self in the phone is broken?
kmo1997 said:
Hi everyone,
maybe someone here might help me. I was on bliss rom and my phone suddenly froze yesterday.
And oh boy did that started a very long day of messing with miflash tool and twrp.
The situation right now is like this,
I have full access to TWRP, and fastboot and mi flash tool.
I tried flashing stock rom with mi flash, got success with no error and yet still stuck in frozen POCO logo.
Tried flashing with TWRP couple of ROMs with correct fw and still got POCO logo stuck.
Tried sideloading with adb some ROMs and same results, stuck on POCO logo.
Also tried to use flash_all bat without mi flash tool, and it boots me to MIUI recovery...
I can always come back to fastboot and boot to TWRP and tried miflashtool many time , I always result in success (0) but nothing works...
Is there anything I'm missing?
Of course I waited at least half an hour every time on POCO logo beacuse I know It can take some time for first boot but nothing happens, If I had to guess is there a possibility that the Storage it self in the phone is broken?
Click to expand...
Click to collapse
Did you format the data partition at all while doing this? If not, then try running "fastboot -w" while in bootloader mode.
DarthJabba9 said:
Did you format the data partition at all while doing this? If not, then try running "fastboot -w" while in bootloader mode.
Click to expand...
Click to collapse
yes i tried. it gives me an error :
Erasing 'userdata' OKAY [ 0.032s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
C:\Users\Moti\Desktop\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
kmo1997 said:
yes i tried. it gives me an error :
Erasing 'userdata' OKAY [ 0.032s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
C:\Users\Moti\Desktop\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Click to expand...
Click to collapse
Hmmm ... that shouldn't happen. You may have a hardware problem.
Try booting to recovery and formatting data from there. If that doesn't work either, then I have no other suggestions.
DarthJabba9 said:
Hmmm ... that shouldn't happen. You may have a hardware problem.
Try booting to recovery and formatting data from there. If that doesn't work either, then I have no other suggestions.
Click to expand...
Click to collapse
i tried , no luck.
is there any way to fing out if it is truely hardware problem?
Hi,
just a thought,
I have been in a situation were Miui stock would not complete it`s installation, I don`t use MIflash tool, i found a tip that involved moving the ADB flies from Miflash and put them into the Miui fastboot stock rom folder and move the re-named folder to my C: Drive.
After some panicking i tried my old faithful a "Xiaomi.eu Fastboot rom", i installed it from fastboot, it completed as it should and i carried on where i left off, flashing custom roms,
its worth a try
i do the same
johnr64 said:
Hi,
just a thought,
I have been in a situation were Miui stock would not complete it`s installation, I don`t use MIflash tool, i found a tip that involved moving the ADB flies from Miflash and put them into the Miui fastboot stock rom folder and move the re-named folder to my C: Drive.
After some panicking i tried my old faithful a "Xiaomi.eu Fastboot rom", i installed it from fastboot, it completed as it should and i carried on where i left off, flashing custom roms,
its worth a try
Click to expand...
Click to collapse
thanks for the answer, in my situation miui stock completes the installation successfully with a beautiful green success in miflashtool and yet I'm still stuck at the POCO logo till botting itself to MIUI recovery.
regardless I tried your advice and no luck
I have tried a couple more things, I flashed with locking the bootloader the oldest MIUI ROM I found on the archive, of course no luck, still stuck on POCO logo and as always somehow, I'm able to boot into fastboot so unlocked the bootloader again and tried a xieomi.eu rom without mi flash tool with the .bat file and flash_all.
same result, no luck
I'm starting to think it might really be a hardware issue, yet I'm baffled at how the phone was working perfectly fine and suddenly froze while i was using it and started bootlooping which started this whole mess.
kmo1997 said:
.... I'm starting to think it might really be a hardware issue, yet I'm baffled at how the phone was working perfectly fine and suddenly froze while i was using it and started bootlooping which started this whole mess.
Click to expand...
Click to collapse
That is often how hardware problems manifest themselves.
kmo1997 said:
thanks for the answer, in my situation miui stock completes the installation successfully with a beautiful green success in miflashtool and yet I'm still stuck at the POCO logo till botting itself to MIUI recovery.
regardless I tried your advice and no luck
Click to expand...
Click to collapse
If possible try gsi builds to boot bro it may boot directly to system
Try flashing different Fastboot stock Roms using miflash, don't use just one version, try only without locking the bootloader, probably it is a boot partition error, you just need to find the right one, also use a different miflash version (older ones seem to be more stable)
I have just read one of your recent comments, it seems like e miflash problem, flashing with lock must lock the bootloader, try using known versions especially older ones
Have you tried turning it off and on again?
Jk.
First of, which twrp Version are you using? You should try the latest skkk versions. https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/alioth/
Are you sure that you have full twrp storage access? If you boot into twrp, how big is your internal storage, as seen from twrp? Does it show 0?
I had this error once, couldnt flash anything anymore because twrp couldnt handle some encryption and needed to reformat the internal storage to ext2, then back to ext4 again. Then the storage was readable and writable again.
Encryption can be a weird, just like A/B partitioning.
Make sure to use the latest version of MIUI for your specific region.
A.k.a. the exact version of MIUI that your phone shipped with, but use the latest version of it.
And don't download from a weird third party website.
I think the official site is mi.com (but you'll have to google the exact link).
Otherwise, my go-to for MIUI ROMs is xiaomifirmwareupdater.com

Categories

Resources