I accidentally flashed the wrong logo.img and now my phone does not boot anymore, its just a black screen
idk if there is a way to write the phone without booting it, if someone got an idea what I could do, please help me :'(
GiantMurloc said:
I accidentally flashed the wrong logo.img and now my phone does not boot anymore, its just a black screen
idk if there is a way to write the phone without booting it, if someone got an idea what I could do, please help me :'(
Click to expand...
Click to collapse
can you boot into fast boot mode
muneeb rizwan said:
can you boot into fast boot mode
Click to expand...
Click to collapse
nope, the screen stays black and it doesn't even vibrate anymore
GiantMurloc said:
nope, the screen stays black and it doesn't even vibrate anymore
Click to expand...
Click to collapse
does your computer detects it
muneeb rizwan said:
does your computer detects it
Click to expand...
Click to collapse
the device list in linux stays the same when i plug or unplug it, so I think its not detected by the pc
It would be better if you told us exactly what you did. Step by step. Then we can more easily assess how serious the error may have been.
StaryMuz said:
It would be better if you told us exactly what you did. Step by step. Then we can more easily assess how serious the error may have been.
Click to expand...
Click to collapse
so, I broke my system img today, the phone was in a bootloop and I downloaded the system img and boot img from c.mi.com, then I found out that there is actually a logo.img for the splashscreen and tried to create my own, I thought it would be alright if I flash it and I could get back to fastboot if its not working. well seems like that was wrong, now the phone is not booting anymore :'(
I there any way to the phone before it tried to start the logo.img?
On my old lenovo tablet there was a software called mtk tool that was able to flash the device before it starts anything
so I found out that I could try to boot my phone into the edl mode, so I can flash it with mi flash tool, but I would need to remove the phone cover for that, so it would be my last option, any other idea?
The question is whether the phone doesn't actually report anything when connected to a PC. In Windows detection is easy, how it is verifiable in Linux I have no idea. The phone can report to different kinds of drivers, including the COM port. EDL mode can be triggered by test points from the phone's motherboard, but sometimes also by button combinations. I don't know of a suitable button combination yet, but it is used from the off state of the phone when the phone is connected to a PC.
As for the tablet connection you mentioned, it was definitely an MTK CPU and it has different procedures to upload than Qualcomm. With us, you have to connect the phone first.
So I tried it on my windows and it also didn't show up in device manager. Anyway I will buy a phone repair kid and try to fix it in the EDL mode, thank you ^^
Related
Hello everyone ill cut right to the point i rooted my Zte source using Kingo root app about a month ago and everything was fine and 3 days ago i installed a boot animation through rom toolbox and my phone now will not boot up i get black screen with flashing red light when i try to go into recovery mode by pressing and holding power and vol + it vibrates but stays at black screen and shows up on my pc as ZTE Handset Diagnostic Interface(DFU) (COM5) what do i do? Can i reset my phone?
King-Reaper said:
Hello everyone ill cut right to the point i rooted my Zte source using Kingo root app about a month ago and everything was fine and 3 days ago i installed a boot animation through rom toolbox and my phone now will not boot up i get black screen with flashing red light when i try to go into recovery mode by pressing and holding power and vol + it vibrates but stays at black screen and shows up on my pc as ZTE Handset Diagnostic Interface(DFU) (COM5) what do i do? Can i reset my phone?
Click to expand...
Click to collapse
i say there is still hope. seems the only thing you messed up is the boot animation. according to this thread http://forum.xda-developers.com/showthread.php?t=2520309
you have fastboot for your device, so in theory, you could use a fastboot flash recovery command to install CWM, and use it to install a ROM
The French Tickl3r said:
i say there is still hope. seems the only thing you messed up is the boot animation. according to this thread http://forum.xda-developers.com/showthread.php?t=2520309
you have fastboot for your device, so in theory, you could use a fastboot flash recovery command to install CWM, and use it to install a ROM
Click to expand...
Click to collapse
how do i get fastboot to recognize my device? i have correct drivers for phone since my brother has same phone i got drivers off his phone but fastboot does not see my device adb does not see my device as well
King-Reaper said:
how do i get fastboot to recognize my device? i have correct drivers for phone since my brother has same phone i got drivers off his phone but fastboot does not see my device adb does not see my device as well
Click to expand...
Click to collapse
did you enable usb debugging?
The French Tickl3r said:
did you enable usb debugging?
Click to expand...
Click to collapse
the last time my phone would boot up yea usb debugging was enabled by now it wont boot so i cant check to make sure
i dont use the same device as urs but as far as my knowledge goes
ur phone has usb degubbing on ...jus gt in fastboot and figure out a way to install a custom recovery
then u can just wipe data and ull b good to go...no need of a new rom
search xda forum for ur cell to flash recovery via fastboot
:good:
MOHIT.S said:
i dont use the same device as urs but as far as my knowledge goes
ur phone has usb degubbing on ...jus gt in fastboot and figure out a way to install a custom recovery
then u can just wipe data and ull b good to go...no need of a new rom
search xda forum for ur cell to flash recovery via fastboot
:good:
Click to expand...
Click to collapse
but fastboot dose not see my device and i dont know how to make fastboot see my device
King-Reaper said:
but fastboot dose not see my device and i dont know how to make fastboot see my device
Click to expand...
Click to collapse
dude...1st of all fastboot is a boot mode...to get into it u have to use combination keys while booting, some times use usb cord
just google how to fastboot with the name of ur device ull gt it!
Hey guys sorry I've been busy my phone is fixed I just took it to cricket and told them a software update broke my phone so this thread can be closed thanks for everyone's help
Sent from my ZTE_N9511 using XDA Free mobile app
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80110c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
brickedvice said:
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80120c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
Click to expand...
Click to collapse
theres several things you could do.. try srk tools to try and fix twrp, or fix download mode using nuke download.. i dont know how to i just know theres a way to do it.. if other fails and it doesn not go into download mode then you must short circuit the motherboard.... then look at thread g2 hard brick fix..
here but try other first as this one you have to open phone..
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
raptorddd said:
theres several things you could do.. try srk tools to try and fix twrp, or fix download mode using nuke download.. i dont know how to i just know theres a way to do it.. if other fails and it doesn not go into download mode then you must short circuit the motherboard.... then look at thread g2 hard brick fix..
here but try other first as this one you have to open phone..
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
thanks for the prompt reply! is this the srk tools you are referring to: http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 ?
also what is nuke download? Thanks in advance.
Edit: nvm I read what nuke download mode is (when no recovery and can't boot). I will try it now and see if it helps...
brickedvice said:
thanks for the prompt reply! is this the srk tools you are referring to: http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 ?
also what is nuke download? Thanks in advance.
Click to expand...
Click to collapse
yes.. and its a way to force or fix device to enter download mode.. like i said ive never used it but i know it might help. if it fails then you must open the phone .. and short circuit the motherboard.. good luck. :fingers-crossed:
raptorddd said:
yes.. and its a way to force or fix device to enter download mode.. like i said ive never used it but i know it might help. if it fails then you must open the phone .. and short circuit the motherboard.. good luck. :fingers-crossed:
Click to expand...
Click to collapse
I don't think my phone is hard bricked. USB debbuging is on and computer recognizes the device when it boots up. I simply don't know how to install twrp via adb commands or alternative methods ... or how to manually flash a custom kernel that would allow normal device boot up when dpi is changed.
brickedvice said:
I don't think my phone is hard bricked. USB debbuging is on and computer recognizes the device when it boots up. I simply don't know how to install twrp via adb commands or alternative methods ... or how to manually flash a custom kernel that would allow normal device boot up when dpi is changed.
Click to expand...
Click to collapse
well me neithe LOL.. but i think you can fix recovery with srk. i think.. read and i think you can fix that.. ive never used it..
raptorddd said:
well me neithe LOL.. but i think you can fix recovery with srk. i think.. read and i think you can fix that.. ive never used it..
Click to expand...
Click to collapse
lol I used the srk tool but now i got this error:
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
phone is in bootloop if I decide to reboot; while if I decide to go in download mode, it doesn't do anything...
brickedvice said:
lol I used the srk tool but now i got this error:
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
phone is in bootloop if I decide to reboot; while if I decide to go in download mode, it doesn't do anything...
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g2/help/demigod-crash-handler-critical-error-t3108512/page2
https://www.youtube.com/watch?v=x1mUpwfEeDo
raptorddd said:
http://forum.xda-developers.com/lg-g2/help/demigod-crash-handler-critical-error-t3108512/page2
https://www.youtube.com/watch?v=x1mUpwfEeDo
Click to expand...
Click to collapse
I saw those I just can't get it to be recognized by the computer. Did the guy in the video try the hard brick fix from XDA? It is not very clear how he gets his laptop to recognize the device
brickedvice said:
I saw those I just can't get it to be recognized by the computer. Did the guy in the video try the hard brick fix from XDA? It is not very clear how he gets his laptop to recognize the device
Click to expand...
Click to collapse
i do not know either.. shortening the mother board is to enter download mode..
brickedvice said:
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80110c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
Click to expand...
Click to collapse
This thread here : http://forum.xda-developers.com/showthread.php?t=2449670 might help you installing twrp via adb
While trying to set up a new boot animation, I came across an error which prevented my phone form booting up into the OS and instead showed me the Fastboot screen every time. I tried reflashing twrp, as well as flashing another boot animation into it. While reflashing TWRP for the third time (I didn't really know what to do so I just hoped it would work eventually), it seems like it corrupted some of my phone data, meaning preloader and I believe some other stuff. The phone now won't boot at all, and also isn't getting recognized by SPFlashTool. While plugging it into my PC I can still hear the "connected" and "disconnected" sound though.
Any ideas on what I could do?
I know its kinda late but
Have you tried using adb or fastboot and check if your device is recognized with the adb devices command?
noah_bfn said:
Have you tried using adb or fastboot and check if your device is recognized with the adb devices command?
Click to expand...
Click to collapse
I don't know how to do it But I'm having the same problem the screen is black , can you guys help me ?
Your phone sounds like it is soft bricked.
emersonsamuel said:
I don't know how to do it But I'm having the same problem the screen is black , can you guys help me ?
Click to expand...
Click to collapse
Your phone sounds as though it is soft bricked. It can be brought back to life.
Follow here to un-brick your device:
https://forum.xda-developers.com/android/general/ulefone-power-5-twrp-root-project-treble-t3943714
Loyal_Guardian said:
While trying to set up a new boot animation, I came across an error which prevented my phone form booting up into the OS and instead showed me the Fastboot screen every time. I tried reflashing twrp, as well as flashing another boot animation into it. While reflashing TWRP for the third time (I didn't really know what to do so I just hoped it would work eventually), it seems like it corrupted some of my phone data, meaning preloader and I believe some other stuff. The phone now won't boot at all, and also isn't getting recognized by SPFlashTool. While plugging it into my PC I can still hear the "connected" and "disconnected" sound though.
Any ideas on what I could do?
Click to expand...
Click to collapse
Just use the spflashtool. Try multiple times and try my updated guide. Make sure you installed the drivers properly AND USE A GOOD CABLE. I had some hard times flashing with spflashtool, but it was just the cable.
Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
lucasdeeiroz said:
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
Click to expand...
Click to collapse
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
adri_sefp said:
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
Click to expand...
Click to collapse
When did you buy this phone?
borksek said:
When did you buy this phone?
Click to expand...
Click to collapse
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
adri_sefp said:
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
Click to expand...
Click to collapse
did you manage to solve this problem?
claudiusuflea said:
did you manage to solve this problem?
Click to expand...
Click to collapse
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
that means there's no work-arround
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
Even if you do that, there's no blankflash for this model... as long as I know, I was looking forward to find it somewhere but there is none available.
claudiusuflea said:
that means there's no work-arround
Click to expand...
Click to collapse
That's correct, now my device shows nothing on screen, it is just black but when I plug the usb cable, fastboot detects it as fastboot mode, all commands are working but nothing else works.
I'm giving up now.
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
works if I have the bootloader still locked?
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
claudiusuflea said:
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
Click to expand...
Click to collapse
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
adri_sefp said:
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
Click to expand...
Click to collapse
Indeed, after flashing an Android 8 firmware my phone went into Qualcomm 908 EDL mode. After blankflashing and flashing the latest firmware had the same issue with "No bootable A/B slot". The same state before hardbricking the phone (AP Fastboot flash mode secure).
adri_sefp said:
Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
Click to expand...
Click to collapse
maybe works "lenovo rescue and smart assistant"
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
No, lmsa would recognise the phones after A10 update, but the problem persists. Someone who has repaired this or someone who has managed to take it to the service or managed to revive the phone from this state? With locked bootloader
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
That didn't help either, there's nothing else we can do than replacing the main board.
Hello.
I have a similar problem. I have tried all of the methods listed, unfortunately nothing works. I ended up replacing the motherboard. The old PCB is waiting, maybe someday it can be repaired.
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
UnequalB said:
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
Click to expand...
Click to collapse
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
UnequalB said:
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Click to expand...
Click to collapse
You can flash the TWRP image through fastboot and then boot to it through commands.
UnequalB said:
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
Click to expand...
Click to collapse
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
SubwayChamp said:
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
You can flash the TWRP image through fastboot and then boot to it through commands.
Click to expand...
Click to collapse
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
SubwayChamp said:
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Click to expand...
Click to collapse
Weirdly enough the error i got was not listed here..
SubwayChamp said:
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
Click to expand...
Click to collapse
This method doesn't work either since the phone won't stay off for more than 7 seconds.
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
UnequalB said:
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
Click to expand...
Click to collapse
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
UnequalB said:
Weirdly enough the error i got was not listed here..
This method doesn't work either since the phone won't stay off for more than 7 seconds.
Click to expand...
Click to collapse
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
UnequalB said:
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
Click to expand...
Click to collapse
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
SubwayChamp said:
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
Click to expand...
Click to collapse
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
UnequalB said:
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
Click to expand...
Click to collapse
Well, if you interrupted the process, that's not good at all. The only you can do is keeping trying it, if your motherboard was not damaged.
hi guys i am DELTIERO from the Philippines did you allready solve the problem?
If not yet done message me on my facebook page https://www.facebook.com/del.villalobos.1/
and i will help you im here veltech san carlos negross occidental phil
Help please! I flashed a gapps zip file using flashify on my infinix smart 5 x657 (Running on lineageos gsi android 12) then the phone just went off. and it not turning on. but it shows the charging indicator light when i connect it to power.
I've tried disconnecting the battery still nothing
what possible solution is there for this?