Related
So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
a bit more info plz
alemale said:
So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
Click to expand...
Click to collapse
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
rishr4 said:
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
Click to expand...
Click to collapse
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
alemale said:
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
Click to expand...
Click to collapse
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
2. There is a possibility that you could "brick" or bootloop your phone. There are two types of brick: soft (recoverable) and hard (non-recoverable). With a soft brick, the phone will not boot or keeps rebooting ("bootloop"), but it can be started in bootloader mode which allows repair of the ROM. With a hard brick, the phone won't even boot into bootloader after holding the power button for 10 seconds and the phone must be returned to HTC for service.
Click to expand...
Click to collapse
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the
PROCEDURE 1
Click to expand...
Click to collapse
then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
rishr4 said:
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
Click to expand...
Click to collapse
I tried to unlock the bootloader but it wanted 2.3.5 so i tried to install the new version. now it can't do anything. Well this didn't broke my heart because the phone is pretty worthless . now i have to buy new phone sooner than i planned but still all help is still accepted.
Hi, exactly the same for me : I bought the phone 2 years ago and immediately unbranded it with a goldcard, but never tried to unlock it because it was my wife's and I didn't want to risk anything.
Now she got a new phone, I wanted to play a little with the Wildfire S ^^.
In order to unlock the phone on htcdev I had to update it from 2.13.401.2 to 2.13.401.3, with RUU because can't update with OTA (different CID), with goldcard inside.
After the RUU finished, it says "congratulations everything went well", but actually the phone does not boot, stocked in a loop "quick flash / turns off", can't access bootloader, no USB detection for ADB.
Can't send it to HTC because the 2 years warranty is expired, how ironic ! :laugh:
So... if anyone does know or see any trick that could help to boot anything on this "seems to be hard-bricked" kid... huge thanks to you
I rooted my phone yesterday and everything was going fine. Then my phone died and now my phone only boots into the recovery(CWM) and it wont charge. I have done a lot of searching and have found no solution. My phone is recognized when I use adb commands, but when I try to do anything all I get is <<waiting for device>>. Any help would be appreciated.
Soft brick
GoTZeus said:
I rooted my phone yesterday and everything was going fine. Then my phone died and now my phone only boots into the recovery(CWM) and it wont charge. I have done a lot of searching and have found no solution. My phone is recognized when I use adb commands, but when I try to do anything all I get is <<waiting for device>>. Any help would be appreciated.
Click to expand...
Click to collapse
So you rooted your phone successfully, installed custom recovery through ADB then flashed superSU zip from the root of your SD card, and then the battery died normally and now you can't get into anything but recovery correct? This post is a little late so you might have found a fix by now but pressing your power button and volume up button should reboot your phone.
I Need help fixing my g3, been Trying for hours to no avail. i need some guidance i am completely lost.
GTFODeathknight said:
I Need help fixing my g3, been Trying for hours to no avail. i need some guidance i am completely lost.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091
GTFODeathknight said:
I Need help fixing my g3, been Trying for hours to no avail. i need some guidance i am completely lost.
Click to expand...
Click to collapse
First tell us what the issue is?
Is it a soft brick? Just flash your TOT file by the LG flash tool and your good to go. But first you should give us some more information
_SDroid said:
First tell us what the issue is?
Is it a soft brick? Just flash your TOT file by the LG flash tool and your good to go. But first you should give us some more information
Click to expand...
Click to collapse
(sorry for the reply time was camping) i just woke up one morning and my phone just wouldnt boot up, i cant even get to the recovery mode nor download mode. when it starts powering on i get
SECURE BOOTING ERROR
BOOT CERTIFICATION VERIFYAlong with the LEDs blinking
GTFODeathknight said:
(sorry for the reply time was camping) i just woke up one morning and my phone just wouldnt boot up, i cant even get to the recovery mode nor download mode. when it starts powering on i get
SECURE BOOTING ERROR
BOOT CERTIFICATION VERIFYAlong with the LEDs blinking
Click to expand...
Click to collapse
If you can't access the download mode you've hard bricked your phone some way. You should send it back and let it repair by someone
If you're out of warranty and feel up to taking your phone apart you could try this: http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
If you still have warranty, send it in.
Hey All,
I have searched the forum for this but i dont seem to get the same issue. And i dont want to make things worse, so i post it here. Hope you guys and galls are able to help.
So what happend. I wanted to flash back my G3 d855 16Gb Eur model.
Something allong the way went wrong, and i dont know what. All i know is that when i came back my phone was turned of. And my pc gave a failed message.
Now i cannot get in to download mode anymore. It gives me the LG boot logo and that is it.
When i want to enter download mode i get the download mode logo, with in the top left corner a verification error.
It goes quite fast so i cannot get the exact message. Can anyone point me in the direction of a fix. Ore is it indeed really dead?
Hello and thank you for using Q/A,
if you can't enter the download-mode, your mobile is dead. You may flashed a wrong firmware and the bootloader was overwritten with a wrong device.
Can you enter into Recovery?
Kind regards
Trafalgar Square
Nope, the phone reacts when i connect it to the pc. I get the android bootlogo. And when i power up with volume -, the i get the factory reset options but it dont work.
would the wiretrick help me out ?
Darkje said:
Nope, the phone reacts when i connect it to the pc. I get the android bootlogo. And when i power up with volume -, the i get the factory reset options but it dont work.
Click to expand...
Click to collapse
Can you reboot your phone into recovery mode (If it is already rooted and custom recovery installed).
I also faced a problem like that. In my problem when i reboot into download mode it took me to fastboot mode with 4 to 5 commands on left upper edge. If you can boot into that "fastboot" mode then tell me so i can help you better.
If you can't see anything like above then tell me that too i will try best to help you get out of this problem>>
No I don't get those options.
I get some kind of miss match error
exact error is:
boot verification failed
cause mismatch_sig_len
Hey All,
Just want to let you know, that i have been struggeling with my phone for two weeks. Offcourse not 24/7. But it is back alive. I managed to do the wiretrick and i was able to load up the Qualcom 9008 driver. After a long struggle i even managed to get the phone reconized by board diag. From that on it was easy to flash back all partitions. And download/firmware update mode was back. After this all i was able to flash the KDZ file.
I then lost my IMEI, but i backed up my EFS and all other importend files in the beginning. After rooting and flasing my EFS all was back to normal.
So ... i quess the d855 is indeed unbrickable
Solution
Darkje said:
Hey All,
I have searched the forum for this but i dont seem to get the same issue. And i dont want to make things worse, so i post it here. Hope you guys and galls are able to help.
So what happend. I wanted to flash back my G3 d855 16Gb Eur model.
Something allong the way went wrong, and i dont know what. All i know is that when i came back my phone was turned of. And my pc gave a failed message.
Now i cannot get in to download mode anymore. It gives me the LG boot logo and that is it.
When i want to enter download mode i get the download mode logo, with in the top left corner a verification error.
It goes quite fast so i cannot get the exact message. Can anyone point me in the direction of a fix. Ore is it indeed really dead?
Click to expand...
Click to collapse
It's not english, it is portuguese Brazil, but it works.
youtu.be/watch?v=gHAA5e2FQbU&index=1&list=LLtlXyuPzN6skeex-P2apfrQ
hi, I had this also but I can go to recovery mode but....
dksoni411 said:
Can you reboot your phone into recovery mode (If it is already rooted and custom recovery installed).
I also faced a problem like that. In my problem when i reboot into download mode it took me to fastboot mode with 4 to 5 commands on left upper edge. If you can boot into that "fastboot" mode then tell me so i can help you better.
If you can't see anything like above then tell me that too i will try best to help you get out of this problem>>
Click to expand...
Click to collapse
hi, I had this also but I can go to recovery mode but not download mode.. can you help me? thanks in advance
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.