Develop Bugs

xperia play bricked? pls help

hi all im hoping u can help me i have an xperia play which i tryed to root using cynogen mod 12 but it fails on install it will then reboot and show the blue cynogen logo but sit thier untill battery pull. i can access cyonogen recovery but thats all. ive tried installing other roms such as 9, 10 and 11 but all do the same thing (although 11 does seam to install/unpack).
i unlocked the bootloader and rooted the phone successfully. i also used flashtool to flash the boot.img.
i have heard i could fix the problem by sideloading another better recovery tool but i dont know how to do that. as off now im stuck in cynogen recovery.
any advice you could give would be greatfully appreciated, at this point im completely out of ideas and if you need anymore info i would be happy to provide it
thanks in advance

Hi,
It would be nice if you linked the exact ROM you tried to flash on you phone. It sounds like the boot.img is incorrect.
You can try flashing this kernel forum.xda-developers.com/showthread.php?t=1804003 . This one is for ICs roms(4.0.x).
Or this one - for Jelly Bean versions(4.1-4.2) - forum.xda-developers.com/showthread.php?t=1861970 .
All you have to do, is boot into fasboot mode and flash the given .img file as boot.img. (The difference between 480p and 720p kernels, are that 480 can't capture 720p videos, but sometimes 720p kernel doesn't work with all roms).

hi tnx for the help the rom i tried to install was cm-12-20150314-UNOFFICIAL-LegacyXperia-zeus
i think your idea would work but im unable to boot into fastboot mode as i used flashtool before and it doesnt recognise my phone anymore ( i dont know if i can use ADB as that option is available on my boot loader)
if you could provide me with a link to how to flash a new .img/rom using another way other than flash tools that would be really helpful. im sry to be such a noob, i have rooted every phone i had and never encountered this problem before and am completely stuck.
tnx again for your help

ok ignore my last msg i managed to flash the .img in fastboot no problem but now it wont let me into recovery mode so i think im stuck in some infinate boot loop no matter how many times i click volume down it just reboots after about 2 mins, anything i can do about that or am i now really bricked?
tnx again for your help

rob17zero1 said:
ok ignore my last msg i managed to flash the .img in fastboot no problem but now it wont let me into recovery mode so i think im stuck in some infinate boot loop no matter how many times i click volume down it just reboots after about 2 mins, anything i can do about that or am i now really bricked?
tnx again for your help
Click to expand...
Click to collapse
Well you could try to return to point zero by flashing your phone to stock rom and try to begin from there.
You can do that by using flashtool and downloading stock ROM from these forums.
BTW, you can enter flash mode by inserting usb cable and holding search button(i think, you can try other buttons). Your LED has to turn green, blue is fast boot.
Also if your flashtool give you errors, download earlier version (see some other threads about flashtool, there are links to older version). Maybe it doesn't recognize your phone, because of the new version, i've had problems with it too, but i had to download old version and everything started to work as expected.

Stuck in fastboot. No recovery... no bueno :(

So I had my ze551ml / Z00A rooted, was loving life, all was great. Then I tried getting XPosed access and didn't read up on it prior. Anyways, now my phone is stuck in fastboot, I'm able to flash partitions and all, including recovery partition, yet I cannot enter any mode but the hung ASUS logo, or fastboot. I weas even able to load CM's "upgrade to MM bootloader" package, but still the same thing only with green letters where they once were blue..... Please help, I need my beloved phone back.....

I'm not a pro but if you can access fastboot it is just a soft brick and I'm sure many people can point you on the right thread to recover it.

I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....

joecost85 said:
I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....
Click to expand...
Click to collapse
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?

timbernot said:
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?
Click to expand...
Click to collapse
0094.0183

joecost85 said:
0094.0183
Click to expand...
Click to collapse
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link

timbernot said:
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link
Click to expand...
Click to collapse
So I've yet to try your solution, but I do have an update, I was able to, one by one, flash all the stock files (stock as in the stuff I downloaded from asus site) and was almost able to boot to recovery, but when I got to the red triangle android, I couldn't get it to go further. I've heardf alternate key combos for proceeding from there, and tried them all, but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**

joecost85 said:
So I had my ze551ml / Z00A rooted, was loving life, all was great. Please help I need my beloved phone back.....
Click to expand...
Click to collapse
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
joecost85 said:
So I've yet to try your solution,
but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**
Click to expand...
Click to collapse
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108

timbernot said:
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108
Click to expand...
Click to collapse
Here's the thing. I'm super stubborn, and I think I know everything (cuz I do....) so of course I decided that I could figure something out, so I tried my way first............ didn't pan out.... anyway, I'm finding any time I flash a TWRP file, I have no access to recovery mode. Regardless if I do it manually through fastboot, or CM upgrade/downgrade or even the giovix fix (yes I tried it). My question is this, Where is there a return to stock option? of the giovix DLs I could find, I see a 'magisk root' 'TWRP' 'bootloader unlocker' and 'Xposed' tools, nothing else.... Am I missing something? or am I just skimming over that part?
I do appreciate all the help, seriously. Even if it seems like I'm not taking suggestions very well. It's moreso I don't have access to a computer most of the day, and it's not a huge priority since I went and bought a zfone 3 max a few days ago (decent phone for what it is....crazy battery life)

https://forum.xda-developers.com/zenfone2/general/tool-ze551mlmodder-t3458145
Functions:
1- Check connection status
2- Bootloader Unlocker
3- Flash TWRP 3.0.2-0 M1
4- Full-auto xposed flasher!
5- Full-auto root flasher!
5B- Full-auto root (Magisk+Phh's) compatible with 184!
6- ADB Shell
7- Return back to stock
8- Erase /system, /data and /cache for a clean upgrade
9 (HIDE)- Auto-reboot to bootloader
10- More functions inside!

well then forgive me for not downloading the correct option. I nowhere see this list among anything I downloaded, so maybe specify which is which ('full' or 'auto')....... I'm already downloading both of them again, because I'm not sure which I already had. But yea, one of the 2 only has the 4 options I mentioned.

Its not rocket science

timbernot said:
Its not rocket science
Click to expand...
Click to collapse
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?

joecost85 said:
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?
Click to expand...
Click to collapse
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )

timbernot said:
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )
Click to expand...
Click to collapse
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.

joecost85 said:
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.
Click to expand...
Click to collapse
EDIT"""" because i got it wrong too , i dont even think about , i just do it
It`s ->
From powered off position
Press Power and Vol +
at two vibes, release power
at boot up screen ,release vol+
in bootloader ,scroll vol up or down to and then select(press power) at recovery selection.
At dead android guy -> press vol + and power for 4 seconds -> release Vol +
You should be in recovery.

i am replying in this post since i have a similar problem, and I am as stubborn as OP. Me posting here is a big step in acknowledging my defeat at last. Hours of digging through the internet didn't solve my problem
I have changed my ifwi and dnx more times than i can remember. (my clean slate is mostly using xFSTK downloader with xFSTK_ZE551ML-sal358-amtech.vn files)
Using the above mentioned method (giovix`s modder tool) to go back to stock i still boot into fastboot, not recovery mode.
trying to unlock bootloader it says on the phone "unlock fail"
Using asus flash tool with raw files i get "gpt command failed"
Using a manual method i get the "gpt command failed" on the "6. fastboot oem partition /tmp/partition.tbl" step
in my opinion as soon as i get some kind of recovery my problems are solved. But have been working four hours on this problem with all possible solutions i could think of, nothing but frustration.
info: current ifwi 0094.0183 (wich should be M)
serial 01234........EF
and using the toolkit on "https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293" i found out my device firmware version is 198 (wich is probably not good in combo with the ifwi)
little update in a certain config (android 5 / ifwi 0094.177 / stock recovery) i can boot up untill the dead android icon, but with whatever key combo can't get past it... (vol up + power) / (vol down + power)
fastboot flash boot recovery.img (yep i am really desperate to get into recovery) doesn't even give me the dead android.
thank you beforehand!

Last paragraph with android 5 ifwi 0094.0177
Is your serial correct ?
Press vol + once is it correct?, if not you will have to xfstk first again and flash raw (twice) with temp bootloader 0094.1069
See my unbrick video for help

First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?

Speybrouck said:
First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?
Click to expand...
Click to collapse
Did you get this device in this condition ?
If not, what happened so that you lost serial ?
Anyway , i have never tried this because i have ALWAYS succeeded flashing raw (twice) to correct serial BUT it may work for you.( i am not sure you have a device that can have the serial corrected due to whether its been tampered with previous ) which affects recovery and IMEI.
Usually , xFSTK is used to install temp bootloader - Its supposed to be the lowest level form of unbricking procedure and restores temp bootloader so you can fastboot after-- flashing raw in fastboot via AFT(twice) restores serial -- 1st flash approx 3mins is with incorrect serial and temp bootloader.
After a couple of mins, cmds on phone pauses on RESULT=OK on phone.
You close AFT and open AFT again , input raw and set AFT up -- press Vol+ on phone -> once, serial will be corrected and 2nd flash can be started and left until it boots into android 5 by itself.
If GPT trouble , that link may help.
There is other programmes for starting to create serial and restoring .
Usually people who use these , have to dig deep into buildprop stuff which if tampered with can end up with problem such that you have.
Good luck
see if anything here helps
https://forum.xda-developers.com/showpost.php?p=70223946&postcount=8

Mi A2 Lite bricked on stock

Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options

pocchio said:
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
Click to expand...
Click to collapse
Two quick questions:
1.The phone died on its self without your intervention or...?
2.Have you tried to flash the stock firmware via MiFlash , while the phone is in edl mode(the command is: fastboot oem edl)?

1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?

pocchio said:
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
Click to expand...
Click to collapse
pocchio said:
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
Click to expand...
Click to collapse
I think you are confusing some things here; adb is not an option now so you can´t boot device normally and also you said "fastboot edl" but they are different modes.
While in fastboot how did you try booting to TWRP image? (you said through adb but this is not right)

Can you get to fastboot? (hold vol down while booting, should see a rabbit on the screen)

pocchio said:
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
Click to expand...
Click to collapse
When your phone is in EDL mode(you won't be seeing any logo on your phone ,only black screen) it's absolutely normal to see the device as COM port , because the device is in another factory mode. And there is no problem flashing stock ,when your phone is seen as COM port. So if you can't flash the stock firmware in fastboot mode or EDL mode , maybe you have a hardware issue. To be sure -take a screenshot of the error in MiFalsh when the phone is in edl Mode (seen as a COM port) and you try to flash the stock firmware.

Ok, I understand the difference between EDL (black screen) and Fastboot mode. I can get in both mode. I tried to flash fastboot stock rom (taken from the thread in xda) and everything goes smoothly, but it stays in fastboot mode at the end and when I send the command fastboot reboot it gets stuck again on the Android One logo (no animation).
When I tried the EDL mode, mi flash returns something missing (I will post the screenshot asap) and it seems like is not the right thing I'm trying to flash or something similar (I will post more information as soon as I can). (I'm trying to flash the same fastboot roms found in xda)
So, just to make sure I'm doing the right thing, where I can find the stock firmware to flash?
Thanks again for your help!

pocchio said:
Ok, I understand the difference between EDL (black screen) and Fastboot mode. I can get in both mode. I tried to flash fastboot stock rom (taken from the thread in xda) and everything goes smoothly, but it stays in fastboot mode at the end and when I send the command fastboot reboot it gets stuck again on the Android One logo (no animation).
When I tried the EDL mode, mi flash returns something missing (I will post the screenshot asap) and it seems like is not the right thing I'm trying to flash or something similar (I will post more information as soon as I can). (I'm trying to flash the same fastboot roms found in xda)
So, just to make sure I'm doing the right thing, where I can find the stock firmware to flash?
Thanks again for your help!
Click to expand...
Click to collapse
Here is the stock firmware from Xiaomi site:
https://en.miui.com/getrom-354.html?m=yes&mobile=2
Don't worry that it says MIUI , the firmware is Android One , they just forgot to change the name from MIUI to Android One , I have already tried it ,and I can confirm that it's 100% stock Android One firmware , good luck!

Ok I performed the flash but the error i get is new.
I get the error ACK count don't match!
I tried the version
daisy_global_images_V10.0.9.0.PDLMIXM_20190514.0000.00_9.0_f9d0c739e0.tgz

pocchio said:
Ok I performed the flash but the error i get is new.
I get the error ACK count don't match!
I tried the version
daisy_global_images_V10.0.9.0.PDLMIXM_20190514.0000.00_9.0_f9d0c739e0.tgz
Click to expand...
Click to collapse
I will give a solution in a minute
EDIT: Are you sure your bootloader is unlocked? (fastboot oem unlock)
You have two choices , you need to find an older version of MiFlash beta , i'll give you a video :
https://m.youtube.com/watch?v=-7O1Svib14g
In the video description you can find a link for the MiFlash beta ,I hope it helps.
If not , you'll have to consider the Testpoint unbrick method , there are several guides.

OK, thanks to the use of the BETA version I was able to flash the rom but unfortunately I still get the same AndroidOne logo without any animation....
I really don't know what to do now...
Yes the bootloader is unlocked and I checked with fastboot getvar

pocchio said:
OK, thanks to the use of the BETA version I was able to flash the rom but unfortunately I still get the same AndroidOne logo without any animation....
I really don't know what to do now...
Yes the bootloader is unlocked and I checked with fastboot getvar
Click to expand...
Click to collapse
Ok , it totally sound like some kind of hardware issue with the storage . Is there any way to boot in TWRP ?
Download the TWRP version 3.3.3-1 offain and try to boot with it (fastboot boot recovery(the name of the recovery).IMG) and wait until the TWRP logo disappear. Wait at least 1 minute if the logo doesn't disappear , then in my opinion , you have a hardware problem , if you succeed to booting in TWRP download the GM 1.1 version from this thread :
https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704
and flash it via TWRP. Then reboot and leave the phone without touching at least 10 minutes (until you see some movement like on the bottom of the screen , there will be a MI logo , right above the logo if you see 3 dots moving , then you're saved . From there we can proceed , but if you can't flash even this rom , if nothing helps. I hope you have a warranty , reflash the stock rom with the option flash_all_lock and go to your warranty service center.
EDIT: I googled and found another issue, that might be causing this strange situation: You may got scammed , and the device might not be a Mi A2 Lite , but rebranded Redmi 6X. See this thread:
http://en.miui.com/thread-5984082-1-1.html
If your phone is displayed "Wayne" ,not "Daisy" ,then you'll have to flash a Redmi 6X firmware to get rid of the bootloop

nikoman1987 said:
Ok , it totally sound like some kind of hardware issue with the storage . Is there any way to boot in TWRP ?
Download the TWRP version 3.3.3-1 offain and try to boot with it (fastboot boot recovery(the name of the recovery).IMG) and wait until the TWRP logo disappear. Wait at least 1 minute if the logo doesn't disappear , then in my opinion , you have a hardware problem , if you succeed to booting in TWRP download the GM 1.1 version from this thread :
https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704
and flash it via TWRP. Then reboot and leave the phone without touching at least 10 minutes (until you see some movement like on the bottom of the screen , there will be a MI logo , right above the logo if you see 3 dots moving , then you're saved . From there we can proceed , but if you can't flash even this rom , if nothing helps. I hope you have a warranty , reflash the stock rom with the option flash_all_lock and go to your warranty service center.
EDIT: I googled and found another issue, that might be causing this strange situation: You may got scammed , and the device might not be a Mi A2 Lite , but rebranded Redmi 6X. See this thread:
http://en.miui.com/thread-5984082-1-1.html
If your phone is displayed "Wayne" ,not "Daisy" ,then you'll have to flash a Redmi 6X firmware to get rid of the bootloop
Click to expand...
Click to collapse
I will now try your solution, I just tried the testpoint unbrick method but still same problem.
The output from fastboot getvar all shows a DAISY bootloader. Where I can see the real name of the device to see if it is a Mi 6X?

pocchio said:
I will now try your solution, I just tried the testpoint unbrick method but still same problem.
The output from fastboot getvar all shows a DAISY bootloader. Where I can see the real name of the device to see if it is a Mi 6X?
Click to expand...
Click to collapse
the command is: fastboot oem get-product-model

nikoman1987 said:
the command is: fastboot oem get-product-model
Click to expand...
Click to collapse
Unfortunately I get unknown command.
Additionally when I try to boot the TWRP I get stuck at logo forever....

pocchio said:
Unfortunately I get unknown command.
Additionally when I try to boot the TWRP I get stuck at logo forever....
Click to expand...
Click to collapse
tried the command too, it doesn't work.
So test point doesn't work too.. That's bad news
EDIT: fastboot getvar product command works , you can try it
And another question , have you tried to boot with patched boot.IMG ?

It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....

pocchio said:
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
Click to expand...
Click to collapse
You need a recovery to flash , which has a specific partition in the phone storage. You can flash only via fastboot . You need to boot into recovery , so try with a patched boot image for your version of the rom
---------- Post added at 02:47 PM ---------- Previous post was at 02:38 PM ----------
pocchio said:
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
Click to expand...
Click to collapse
So the last resort , we'll try to flash the ROM that I have mentioned before via fastboot. Place the zip file GM 1.1 in your PC (it has to be in the same directory as your adb and fastboot tools)
then open cmd and run the command
fastboot flash (the full name of the zip).zip
and hit enter
maybe that will solve it
And if this doesn't help again... type these fastboot commands :
fastboot format userdata
fastboot format system
fastboot format cache
fastboot format vendor
fastboot format recovery
fastboot format boot
then try again to reflash the stock rom (first try in edl mode ,if this doesn't do anything ,you'll have to format everything via fastboot commands again ,and try to flash the ROM in fastboot mode)
And if this doesn't help too... Then you're free to hit that ? in the ground hahahah (just kidding)

Tried both these two last but nothig works, I always get the same problem.
I just saw your comment on patched boot, can you elaborate a little bit on this?
I'm honestly very close to throw it in the trash

pocchio said:
Tried both these two last but nothig works, I always get the same problem.
I just saw your comment on patched boot, can you elaborate a little bit on this?
I'm honestly very close to throw it in the trash
Click to expand...
Click to collapse
which version of the firmware you are flashing? 10.0.9.0 or another version , so I can send you a link and walk you through the procedure.
And when you flashed the GM 1.1 the boot screen didn't changed from Android one? (the GM 1.1 version is a MIUI stock port and has to change your boot screen to black screen with white MI logo on it) It is very important to know
One of my friends told me to try this: just open the directory of the stock firmware , navigate to flash_all.bat and run the bat file (NOT THE FLASH_ALL_LOCK!!!) and wait for the end of the process. He had a similar problem , and it worked. He explained that for any reason , the recovery was the problem , because it was flashed in the boot partition. When you use flash_all.bat The file will erase all partitions and rewrite them. MiFlash won't , so try that

NERVOUS about flashing Lineage 18 :-(

HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler

Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom

Tsuragi said:
Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom
Click to expand...
Click to collapse
Thanks Tsuragi,
Forgot about that - it was me who posted that solution some time ago duh!
Pootler

pootler said:
HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler
Click to expand...
Click to collapse
Hey bro same experience, thats why im stock in android 10 with unlock bootloader. but i successfully flashed lineage with unofficial twrp but the problem is i cant flashed gapps thats why i cant install pre apps and cant use the default message and call. please help me

Question Poco f3 Error: Sending modem_ab

good evening
I have been trying to return to stock miui from Pixel Experience since yesterday but get this error every time I try to flash the Firmware and do not know what I can do about it. I would be happy if somebody knew what this error is from and what might fix it.

Same problem. Don't try more things because you will brick your phone like mine.

Thanks for your reply. What did you do that bricked your Phonem? This way I know what to avoid. Thanks you in advance

As you are sure your device is a eea one, try with this last official stable firmware : Version: V13.0.7.0.SKHEUXM
You can find it here https://new.c.mi.com/global/miuidownload/detail/device/1900394
Fastboot version here at bottom : https://xiaomifirmwareupdater.com/miui/alioth/stable/V13.0.7.0.SKHEUXM/
Or https://bigota.d.miui.com/V13.0.7.0...EUXM_20220627.0000.00_12.0_eea_e461331a7d.tgz

Thanks you so much I will try that

and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots

Still the Same Error unfortunatelly

nockcx said:
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Click to expand...
Click to collapse
Ok,
Do you have any idea what you did that may have caused this bootloop ?
Have you used any Qualcomm Tools or any soft in EDL mode ?

No, I did not do anything that would mess with the system to my knowledge . which is why i really do not know what to do. Can This Error occur because of a USB 3.0 used to flash? The Phone even tries to reboot when it is detected as a Fastboot device, maybe This has Something to do with it. Maybe it loses the Connection and therefore the flashing process stops. Are there possible ways to fix This?

Try with the latest android platform tools.
Put the content of platform tools archive in the fastboot folder and launch flash_all.bat don't use flash_all_lock

Still the Same Error . Can This be because of a Driver or a hardware issue?

i had similar issues but with the super partition when trying to flash from cmd.
flashing with miflash instead solved it.

It doesnt seem to make any difference to the error whether i flash it via cmd or miflash

nockcx said:
Still the Same Error . Can This be because of a Driver or a hardware issue?
Click to expand...
Click to collapse
Maybe : So as you can try with other PC, USB cable, USB connector, reinstall USB drivers...

I already tried with two Notebooks, I will try again tomorrow with another PC and installing USB drivers again. Thank you

You could try redownloading the MIUI ROM... you got it from xiaomifirmwareupdater.com right?
And yes ^^, try other PCs/laptops and other USB-cables.
Just please make sure
Unfortunately, Fastboot-Flashing is a gamble. It's not a solid protocol. It has zero protection against sudden USB-connection loss.
And manufacturers like Xiaomi go out of their way and block Qualcomm's EDL Mode, which is the only way to recover your phone in case Fastboot Mode stops working, because that Mode itself can also get damaged.

Fixed - first flash a miui recovery rom from twrp make sure the rom version lower than the latest one, now flash and boot miui , now just update from miui updater once you updated to the latest version , now try to flash the fastboot rom that you trying to flash, it should work.

I cant access a bootloader like TWRP because the phone still keeps rebooting after a couple of seconds in the bootloader so i cant really do much. I only have access to fastboot

nockcx said:
just flash a custom vbmeta and then install a custom recovery in to the boot partition like fastboot flash boot ....flash both the slots boot_a and boot_b the run fastboot reboot recovery do all this with latest platform tools
Click to expand...
Click to collapse

okay Im as far as I have never been with a very weird method, maybe somebody can explain. Because my poco always wants to reboot I found out a way to keep in in Fastboot mode. I repeatedly press the power and volume down button, This way it stays on for a lot longer, but it still is not enough to succeed at flashing the rom. It also lets me believe that my problem is not a software but probably a hardware problem, otherwise and cannot explain this suuuper weird behavior. what do you guys think? is there a possible fix you know?