Develop Bugs

issues with bootloader

Hey i hope all is good.
I really need your help. I have a TILT 2 cell phone and by mistake a friend activated the bootloader. Previously the ROM has been updated. the phone got stuck in that screen and the only way to turn it off is removing the battery. so, i try to reboot the phone and it only loads the bootloader with a flash message saying "no image file". ok, i though, the ROM was damaged and after reading a lot in the forums, i followed the instruction to put a new ROM. I connected the phone the the computer and the message in the phone changed to USB and my PC installed the HTC USB Sync driver (but Active Sync does not detect the phone); anyways, i ran the task 29 and a new rom. I was able to see the progress bar in both (PC and Phone) but then the phone reboots and loads again the bootloader. I tried to use the HARD SPL 1.00 as well but it does the same thing after finishing the flash it loads again the bootloader.
can some help me pls?? i'm new in this and the phone is a work tool for me i really need your help.
rgds

You should do the HSPL before flashing a ROM (unless it was already done).
I would try to flash the newest HSPL, then a ROM.

Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls

jsolanon said:
Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls
Click to expand...
Click to collapse
Hrm, have you tried doing a task29? Re-flash the ROM after task29.

yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do

jsolanon said:
yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do
Click to expand...
Click to collapse
So you've flashed the stock ROM? Have you tried relocking? Probably won't do much, but worth a shot I guess.
When you flash back to stock you flash the stock ROM, then relock, then reflash stock.

Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help

jsolanon said:
Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help
Click to expand...
Click to collapse
My phone is never turned off. I'm not sure what else to suggest, you've tried seemingly every step that could remedy this problem. Radio firmware probably won't help, but it shouldn't hurt either - you could try a new radio...

hi , this happened to me, solved it by reloading the rom again via sd, once it finish maybe you will see the bootloader screen again, so with stylus pres the reset buttom a few times until the rom boot , this can take several times to make it boot. after revive your cell , do a task29 then reload the rom again then do a hard reset, this happened to my 2 times, and its still alive ,good luck.

Same Problem
Hi,
I'm having the same problem. Installed the latest official ROM from HTC/ATT (gorgeous), and same problem after install. Whenever you try to reboot, it gets stuck in the bootloader screen. The last 50 tries it will not reboot at all, even after removing the battery and hitting the power button. This used to work occasionally.
Any other process anyone knows for getting the device to read the ROM?
Is the phone just worn out?

I suggest you reflash the shipped rom to your device and after the flash finishes and your device begins to boot immediately remove the battery to turn it off before it boots. Then replace the battery and press and hold the Send and End keys and while holding them down press the Power button and follow the instructions to factory reset(hard reset).

[Q] HTC One X not switching on

Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.

dead battery
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found

jhakjhuk1853 said:
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found
Click to expand...
Click to collapse
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.

try changing battery
try changing battery by buying new battery and connecting
or remove battery and charge it with external source i guess u must have heard of jump starting battery
kartikeym309 said:
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.
Click to expand...
Click to collapse

kartikeym309 said:
Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.
Click to expand...
Click to collapse
After the phone updated did u extract and flash boot.img from M5.zip?

convict_moody said:
After the phone updated did u extract and flash boot.img from M5.zip?
Click to expand...
Click to collapse
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.

kartikeym309 said:
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.
Click to expand...
Click to collapse
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.

convict_moody said:
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.
Click to expand...
Click to collapse
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.

kartikeym309 said:
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.
Click to expand...
Click to collapse
Check the guides in here:
HTC One X Reference

convict_moody said:
Check the guides in here:
HTC One X Reference
Click to expand...
Click to collapse
Nah, nothing is suitable. There are guides on how not to brick your device but nothing to unbrick it. :|
Thanks anyways. It's appreciated.

Another bricked HOX apparently. There seem to be loads of these on the internet. In my case, it can't have to do with custom roms or rooting since I never messed around with stuff like that. I even opened the HOX and checked all cables etc. There is no part that looks damaged or otherwise suspicious.
What can we do? How can we at least get access to the data in the internal memory?

Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Click to expand...
Click to collapse
Then run the Batch File
Credit to Floepie for writing the .bat

Wilks3y said:
Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
Then run the Batch File
Credit to Floepie for writing the .bat
Click to expand...
Click to collapse
Unfortunately, there's no way this could help. because the HOX is literally dead. There is not even a charging indication when plugged into a PC or the wall charger. And thus it's not recognised by the PC and fastboot won't find it.

[PROBLEM] Not Bootloop - Please help [Intesting post]

Good evening everyone,
I come to you guys with a very particular problem. The LG G4 in question is an H815T (Asian variant). Let me clarify right now, it was not bootlooping. This one was getting STUCK at the LG logo, it didn't restart to it multiple times, it just got stuck there one day after turning off by itself. It did go into the download mode, though.
It went into the first part of the recovery, but when you selected that you wanted to factory reset, it got stuck there. The only way to get it out of the logo or the stuck recovery was taking the battery out. Interestingly enough, the phone DID charge at the stuck logo, albeit not so much due to the screen being constantly on at full brightness.
An even more interesting fact... I managed to fix it! I flashed the KDZ corresponding to the latest LP for the H815T, after the process was done, it did bootloop. I found the YouTube video about flashing a certain file to deactivate most of the cores and said "what the hell have I got to lose?"
Flashed the KDZ and.... VOILA! It showed the Recovery Android doing its job at Format Resetting !
Something even crazier... The phone booted into AndroidLP, I was worried about the cores thing, but the phone seemed to work at full speed... I was surprised to run HWmonitor and notice that all of the cores were active. The phone was fully working!!! Or so I thought... Now I have TWO problems:
I cannot update to MM. If I try to update from the phone itself (because it does say there's a new version available) I go back to being stuck at the LG logo.
When I make a call the screen goes off... nothing I do will turn it on, and if the other person does not hang up, the phone will remain locked. However, if I plug in a headset everything works normally.
Is there anything I can do about these two problems? Please, leave your comments and questions, I think this phone is pretty weird and I found nothing else like it on YouTube or here on XDA.
Take care :good:!

Idk for the call but for the mm you could try using something like lg mobile update tool... Something like that.
Be warned cuz i dont know if it will bootloop.

PhillipDSX said:
Good evening everyone,
I come to you guys with a very particular problem. The LG G4 in question is an H815T (Asian variant). Let me clarify right now, it was not bootlooping. This one was getting STUCK at the LG logo, it didn't restart to it multiple times, it just got stuck there one day after turning off by itself. It did go into the download mode, though.
It went into the first part of the recovery, but when you selected that you wanted to factory reset, it got stuck there. The only way to get it out of the logo or the stuck recovery was taking the battery out. Interestingly enough, the phone DID charge at the stuck logo, albeit not so much due to the screen being constantly on at full brightness.
An even more interesting fact... I managed to fix it! I flashed the KDZ corresponding to the latest LP for the H815T, after the process was done, it did bootloop. I found the YouTube video about flashing a certain file to deactivate most of the cores and said "what the hell have I got to lose?"
Flashed the KDZ and.... VOILA! It showed the Recovery Android doing its job at Format Resetting !
Something even crazier... The phone booted into AndroidLP, I was worried about the cores thing, but the phone seemed to work at full speed... I was surprised to run HWmonitor and notice that all of the cores were active. The phone was fully working!!! Or so I thought... Now I have TWO problems:
I cannot update to MM. If I try to update from the phone itself (because it does say there's a new version available) I go back to being stuck at the LG logo.
When I make a call the screen goes off... nothing I do will turn it on, and if the other person does not hang up, the phone will remain locked. However, if I plug in a headset everything works normally.
Is there anything I can do about these two problems? Please, leave your comments and questions, I think this phone is pretty weird and I found nothing else like it on YouTube or here on XDA.
Take care :good:!
Click to expand...
Click to collapse
U already had flashed a firmware so check for sensors use an app called phone doctor plus download from playstore run its all sensors test see if it shows error and also is ur phone refutbished did u bought the phone new or used... U can also take it lg service center see what they have to say avout it

PhillipDSX said:
Good evening everyone,
I come to you guys with a very particular problem. The LG G4 in question is an H815T (Asian variant). Let me clarify right now, it was not bootlooping. This one was getting STUCK at the LG logo, it didn't restart to it multiple times, it just got stuck there one day after turning off by itself. It did go into the download mode, though.
It went into the first part of the recovery, but when you selected that you wanted to factory reset, it got stuck there. The only way to get it out of the logo or the stuck recovery was taking the battery out. Interestingly enough, the phone DID charge at the stuck logo, albeit not so much due to the screen being constantly on at full brightness.
An even more interesting fact... I managed to fix it! I flashed the KDZ corresponding to the latest LP for the H815T, after the process was done, it did bootloop. I found the YouTube video about flashing a certain file to deactivate most of the cores and said "what the hell have I got to lose?"
Flashed the KDZ and.... VOILA! It showed the Recovery Android doing its job at Format Resetting !
Something even crazier... The phone booted into AndroidLP, I was worried about the cores thing, but the phone seemed to work at full speed... I was surprised to run HWmonitor and notice that all of the cores were active. The phone was fully working!!! Or so I thought... Now I have TWO problems:
I cannot update to MM. If I try to update from the phone itself (because it does say there's a new version available) I go back to being stuck at the LG logo.
When I make a call the screen goes off... nothing I do will turn it on, and if the other person does not hang up, the phone will remain locked. However, if I plug in a headset everything works normally.
Is there anything I can do about these two problems? Please, leave your comments and questions, I think this phone is pretty weird and I found nothing else like it on YouTube or here on XDA.
Take care :good:!
Click to expand...
Click to collapse
I also got the same problem! How do you managed to flash KDZ when the phone is stuck at LG logo?

jinderation said:
U already had flashed a firmware so check for sensors use an app called phone doctor plus download from playstore run its all sensors test see if it shows error and also is ur phone refutbished did u bought the phone new or used... U can also take it lg service center see what they have to say avout it
Click to expand...
Click to collapse
Got it! The sensors thing was definitely it for the screen problem. I also read this is very common with many screen protectors in 5.1.
Do you have any ideas regarding the issue updating to MM?
willy792003 said:
I also got the same problem! How do you managed to flash KDZ when the phone is stuck at LG logo?
Click to expand...
Click to collapse
All good, Willy! Even is you're stuck at the LG logo, take your battery out, or it back in BUT DON'T TURN IT ON... Instead, try to access DOWNLOAD MODE. If you're able to do it, you can flash any KDZ you want, but be careful.
Sent from my GT-N8010 using Tapatalk

Yes ur right using a heavy screen protector will block all the sensors so ya try removing it... No issues in MM u can try OTA through wifi

PhillipDSX said:
Got it! The sensors thing was definitely it for the screen problem. I also read this is very common with many screen protectors in 5.1.
Do you have any ideas regarding the issue updating to MM?
All good, Willy! Even is you're stuck at the LG logo, take your battery out, or it back in BUT DON'T TURN IT ON... Instead, try to access DOWNLOAD MODE. If you're able to do it, you can flash any KDZ you want, but be careful.
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
your screen protector had the sensors covered . you need one with the cut out in the speaker and sensors..

Zenfone 2 only boots Android when plugged in a USB.

So I was using my phone normally yesterday, until it shuts down randomly while using the camera. So I restarted it, but it still restarted as I got to my home screen. So I said to myself that there must be something went wrong in the rom that I am using (which is LOS 14.1), but I've got a backup before **** happened, not to worry, after I restored it though, IT STILL RESTARTED, but the weird part is, It doesn't restart if it is charging. So I wondered maybe the battery has given up, but in the TWRP, it doesn't restart even unplugged?
Things that I had tried:
1. Tried a new rom (this time using BORETS ROM), still restarts when unplugged.
2. Ran the backup again, still no change.
3.Drained my battery in TWRP, charged it up to 100%, still restarts.
Also, when I boot up my phone without a USB cable plugged in, It restarts when loading the main rom (the rom's splash screen, not the main splash screen), PLEASE HELP ME.

Xnin47 said:
So I was using my phone normally yesterday, until it shuts down randomly while using the camera. So I restarted it, but it still restarted as I got to my home screen. So I said to myself that there must be something went wrong in the rom that I am using (which is LOS 14.1), but I've got a backup before **** happened, not to worry, after I restored it though, IT STILL RESTARTED, but the weird part is, It doesn't restart if it is charging. So I wondered maybe the battery has given up, but in the TWRP, it doesn't restart even unplugged?
Things that I had tried:
1. Tried a new rom (this time using BORETS ROM), still restarts when unplugged.
2. Ran the backup again, still no change.
3.Drained my battery in TWRP, charged it up to 100%, still restarts.
Also, when I boot up my phone without a USB cable plugged in, It restarts when loading the main rom (the rom's splash screen, not the main splash screen), PLEASE HELP ME.
Click to expand...
Click to collapse
Hello ..a few questions.
What phone is it ?
What number TWRP do you have ? 3.0.X.X
X= ?

timbernot said:
Hello ..a few questions.
What phone is it ?
What number TWRP do you have ? 3.0.X.X
X= ?
Click to expand...
Click to collapse
It's a ZE551ML and I currently have returned to stock boot loader and recovery image, but the time that it happened I was on TWRP 3.0.3-M4. Why'd you ask?

Xnin47 said:
It's a ZE551ML and I currently have returned to stock boot loader and recovery image, but the time that it happened I was on TWRP 3.0.3-M4. Why'd you ask?
Click to expand...
Click to collapse
Thought you might have older TWRP - no worries
Alls OK now then ?
If it is ? Put **[ solved ]** in title :good:

timbernot said:
Thought you might have older TWRP - no worries
Alls OK now then ?
If it is ? Put **[ solved ]** in title :good:
Click to expand...
Click to collapse
Unfortunately, No it's still not okay.

Xnin47 said:
Unfortunately, No it's still not okay.
Click to expand...
Click to collapse
Have you got IFWI version 0094.0183 in bootloader and M stock recovery ?
If you have , you can use my downgrade from M to LP via SD card from my signature below
If, when back in LP .196 -- You still have the same problem , you will be looking at an hardware and not software problem :good:
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642

timbernot said:
Have you got IFWI version 0094.0183 in bootloader and M stock recovery ?
If you have , you can use my downgrade from M to LP via SD card from my signature below
If, when back in LP .196 -- You still have the same problem , you will be looking at an hardware and not software problem :good:
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Click to expand...
Click to collapse
Today I flashed 2.15.40.13 on raw using Asus Flash Tool, still no luck , I guess it's a hardware problem huh?

Xnin47 said:
Today I flashed 2.15.40.13 on raw using Asus Flash Tool, still no luck , I guess it's a hardware problem huh?
Click to expand...
Click to collapse
Seems like you didn't need any help.

timbernot said:
Seems like you didn't need any help.
Click to expand...
Click to collapse
The problem just seems very weird to be a hardware problem , So, again, after charging my phone up to 100 percent, booted it up to Android and then unplugged it, and I had about a minute of activity now before it shuts down. Again in recovery or boot loader, it never shuts down.

Do me a favour , test with cable attached to phone but detached from charger to rule out USB socket , cable etc:good:

timbernot said:
Do me a favour , test with cable attached to phone but detached from charger to rule out USB socket , cable etc:good:
Click to expand...
Click to collapse
Tried it now, still shuts down.

Xnin47 said:
Tried it now, still shuts down.
Click to expand...
Click to collapse
If its out of warranty , i would first check all connections inside phone ,
it could be battery
it could be main board or usb board.
If it were battery though , it should shut down connected to lower amp pc usb2.
Not much you can do really apart from above, usb boards are cheap`sh to buy, maybe worth the gamble ? Obviously if connections dont fix before ditching if main board. Try a discon of all connections and reconnect before ditching

I have the EXACTLY same problem.
Did you solved?

Guys, I know it's been a long time this question was asked, but I'm having the exact same problem since a week.
@owenreilly @Xnin47 any luck on solving it?
Thanks a lot!

neves4 said:
Guys, I know it's been a long time this question was asked, but I'm having the exact same problem since a week.
@owenreilly @Xnin47 any luck on solving it?
Thanks a lot!
Click to expand...
Click to collapse
Wow this is an old problem. Nope, I didn't fix it, instead I was back on my Galaxy Alpha until I moved on to newer phones. I believe the problem though was the battery, so if you want, you can replace that. Sorry for the late reply bro!

Xnin47 said:
Wow this is an old problem. Nope, I didn't fix it, instead I was back on my Galaxy Alpha until I moved on to newer phones. I believe the problem though was the battery, so if you want, you can replace that. Sorry for the late reply bro!
Click to expand...
Click to collapse
Hey dude! I've replaced my battery 3 weeks ago based on a Brazilian forum and it was, indeed, the culprit haha. Now everything is back on track again.
Thanks a lot for the answer

Unbricking I9192

Hello,
My S4 Mini I9192 Suddenly died while charging overnight and now no response whatsoever. Only thing I know is that I am in 9008 mode.
QFIL Can see the phone, but i need a firehose programmer and some XML files. Can anyone tell me where I can find those files? Thanks in advance.

kasa ssg said:
Hello,
My S4 Mini I9192 Suddenly died while charging overnight and now no response whatsoever. Only thing I know is that I am in 9008 mode.
QFIL Can see the phone, but i need a firehose programmer and some XML files. Can anyone tell me where I can find those files? Thanks in advance.
Click to expand...
Click to collapse
I read a little about using qfil some time ago, and even if you can find the files I don't think it will work on Samsung phones, though I stopped researching when I read the following link (luckily my phone was not bricked, so I didn't need to), he says QFIL won't work as Samsung do not use the default options (well that was my understanding)
http://www.androidbrick.com/unbrick...-have-the-right-kind-of-rom-qhsusb_dload_edl/
I think the only option is take it to a repair shop for jtag or new emmc/motherboard, but I could be wrong. (or buy an old phone with cracked screen and use the motherboard from that)

While I was searching the web for files the phone was connected to the pc. It didn't show any signs of life until a battery icon suddenly popped on the screen. I was even able to boot into download mode, but when I went to recovery it said "No Command". Odin recognized the device, I flashed stock, but when i tried to boot it up, It was in a bootloop. I tried flashing many times with no success, still bootloops. Even after the flashing the recovery was in "No Command" mode. Yesterday i tried to flash it for the last time with the same rom, and this time it just booted to the Samsung logo and then turned off. Now I'm back to the 9008 mode. I tried the sdcard method with a debrick.img, no success. Any idea what might be wrong with the phone?

Okay so now I'm again in download mode, but everytime i boot up the samsung logo distorts and stock recovery shows up but it says E: Can't mount /cache or smth. I've read that i need the correct pit file, apparently the one I have is for the 8gb version. Can anybody send me the .pit file for the 16gb version?

kasa ssg said:
Okay so now I'm again in download mode, but everytime i boot up the samsung logo distorts and stock recovery shows up but it says E: Can't mount /cache or smth. I've read that i need the correct pit file, apparently the one I have is for the 8gb version. Can anybody send me the .pit file for the 16gb version?
Click to expand...
Click to collapse
I can't help as I have different model but yakapa40 can as usual, if nobody else has pit for you
https://www.sammobile.com/forum/showthread.php?t=30208

Exact Same Case
kasa ssg said:
While I was searching the web for files the phone was connected to the pc. It didn't show any signs of life until a battery icon suddenly popped on the screen. I was even able to boot into download mode, but when I went to recovery it said "No Command". Odin recognized the device, I flashed stock, but when i tried to boot it up, It was in a bootloop. I tried flashing many times with no success, still bootloops. Even after the flashing the recovery was in "No Command" mode. Yesterday i tried to flash it for the last time with the same rom, and this time it just booted to the Samsung logo and then turned off. Now I'm back to the 9008 mode. I tried the sdcard method with a debrick.img, no success. Any idea what might be wrong with the phone?
Click to expand...
Click to collapse
kasa ssg said:
Okay so now I'm again in download mode, but everytime i boot up the samsung logo distorts and stock recovery shows up but it says E: Can't mount /cache or smth. I've read that i need the correct pit file, apparently the one I have is for the 8gb version. Can anybody send me the .pit file for the 16gb version?
Click to expand...
Click to collapse
Hey, Hi.
So same thing happened with me, I was on Stock Kitkat S4 mini i9192, phone froze while using and never booted up. But then I left it connected to laptop and it vibrated and showed the battery icon and I got every problem same as you, like no command, boot loop, and again phone went into QHS_DLoad mode.
I want to know that how did you manage to get back into the Odin Download mode again because since the last time my phone didn't show any sign of life and I also want to know if you were able to fix it? I have not tried debrick.img yet. Please help to fix my phone :laugh:

geek_hsk said:
Hey, Hi.
So same thing happened with me, I was on Stock Kitkat S4 mini i9192, phone froze while using and never booted up. But then I left it connected to laptop and it vibrated and showed the battery icon and I got every problem same as you, like no command, boot loop, and again phone went into QHS_DLoad mode.
I want to know that how did you manage to get back into the Odin Download mode again because since the last time my phone didn't show any sign of life and I also want to know if you were able to fix it? I have not tried debrick.img yet. Please help to fix my phone :laugh:
Click to expand...
Click to collapse
Well, sorry to disappoint you, but I found out that the flash memory of the phone was dead. After all I've done the phone just turned off, and never turned on again. I also found out that this phone is known for dying memory chips.

Howdy. Does anybody know what happened here and how to fix it???

Claudio4780 said:
Howdy. Does anybody know what happened here and how to fix it???
Click to expand...
Click to collapse
Just press power button when rebootnow is highlighted by using volume buttons.....

HemanthJabalpuri said:
Just press power button when rebootnow is highlighted by using volume buttons.....
Click to expand...
Click to collapse
Thanks, tried it. But it just starts in Recovery Modus or Bootloader Modus

Claudio4780 said:
Thanks, tried it. But it just starts in Recovery Modus or Bootloader Modus
Click to expand...
Click to collapse
Flash TWRP and flash custom rom like you did before.....
And If you want stock rom then flash my stockrom lite in twrp

Thanks a lot for replying
kasa ssg said:
Well, sorry to disappoint you, but I found out that the flash memory of the phone was dead. After all I've done the phone just turned off, and never turned on again. I also found out that this phone is known for dying memory chips.
Click to expand...
Click to collapse
Thank you, I was thinking that once the battery is empty and when you connect it via USB mode, it reboots itself, so maybe that is why you got the second chance with it but when I got the phone turned on, I charged it up to 90 percent and now my battery is not draining. Previously my phone died when it was having around 35% of charge which was drained in 20 days. So I have avery strong reason to believe that its just a corrupt bootloader and I have to flash using pit.

geek_hsk said:
Thank you, I was thinking that once the battery is empty and when you connect it via USB mode, it reboots itself, so maybe that is why you got the second chance with it but when I got the phone turned on, I charged it up to 90 percent and now my battery is not draining. Previously my phone died when it was having around 35% of charge which was drained in 20 days. So I have avery strong reason to believe that its just a corrupt bootloader and I have to flash using pit.
Click to expand...
Click to collapse
I did try flashing with .pit, but to no avail. Actuall, it recalled to me right know, god knows how I managed to flash stock firmware., BUT, everytime the phone started booting, the samsung loading logo would become slowly more and more distorted, until all my screen became pink with white stripes. It was strange.