What's Happening :
When I turn on my phone, it gets stuck in pre-boot loop i.e. it gets stuck on initial mi logo(without loading sign) and stays there for (almost exactly) 10 minutes, meanwhile getting overheated, then gets restarted by vibrating & flashing the screen once, further just rinse and repeat.
It's actual state is unidentified i.e. IDK whether it's in soft brick, hard brick or broken state.
What I've Tried :
I've tried flashing the rom through fastboot mode.
I've tried flashing the rom through edl mode.
But always ended with the same result.
PS : I flashed the rom with 'clean all' option. I didn't used the 'clean all and lock' option, as unlocking the phone sometimes becomes a pain in the 'A', cause I'm pretty sure the result would've been the same.
Should I Try?
Using the 'clean all and lock' option.
Flashing another version of the miui rom.
What else to bring my phone back to life?
Final words :
On the time of writing this, I'm gonna keep troubleshooting and try some of these options as the time goes by, so I would let you guys know what I've tried.
If you guys are interested in knowing the back story a bit, LMK. I'd update the OP.
All I can say that I'm disappointed. Not a single reply and on xda, I don't have words to describe my disappointment.
Though I still didn't stopped and kept trying, whatever I thought could work. I got different errors from older versions of mi flash tools and similar errors with, newer but similar(interface) versions of the tool. The screen shots of unique errors are linked in this post. The newer versions got a similar error of 'Ping target failed (ping by firehose)' as I vaguely remember. Some newer/older versions didn't even run i.e. got error just by clicking refresh, as you can see with 2016 versions. The newer ones which didn't run were portable versions that showed this error or similar. The older ones ran some sort of installation, but you can't see them in control panel or any uninstaller (iobit in my case). So I'm gonna say they were portable as well just extracting the files. Though 2014-15 worked but 2016 one didn't.
When that didn't worked, I remembered someone saying in a mi thread that the emmc chip might be corrupted. Now I'm not a software engineer so IDK how to remove corruption at that level of software, if normal flashing doesn't work. As only the people who made that device would know the ins & outs at that level, or maybe some high level developer on xda/irl, IDK. But I didn't knew, so I went with the other route of fixing the hardware by reballing. As I'm not an expert in that either and I could've done it but it's such time consuming process and not getting a desired result after all that is an option, so I didn't wasted that much time. Only what I did is give it a heat treatment in hopes to revive it. But it din't worked it showed that blinking red led as it did before but it become somewhat of more dead. But I'm glad I tried my best.
SO THANKS FOR NOTHING GUYS.
Gurkirat_Singh said:
All I can say that I'm disappointed. Not a single reply and on xda, I don't have words to describe my disappointment.
Though I still didn't stopped and kept trying, whatever I thought could work. I got different errors from older versions of mi flash tools and similar errors with, newer but similar(interface) versions of the tool. The screen shots of unique errors are linked in this post. The newer versions got a similar error of 'Ping target failed (ping by firehose)' as I vaguely remember. Some newer/older versions didn't even run i.e. got error just by clicking refresh, as you can see with 2016 versions. The newer ones which didn't run were portable versions that showed this error or similar. The older ones ran some sort of installation, but you can't see them in control panel or any uninstaller (iobit in my case). So I'm gonna say they were portable as well just extracting the files. Though 2014-15 worked but 2016 one didn't.
When that didn't worked, I remembered someone saying in a mi thread that the emmc chip might be corrupted. Now I'm not a software engineer so IDK how to remove corruption at that level of software, if normal flashing doesn't work. As only the people who made that device would know the ins & outs at that level, or maybe some high level developer on xda/irl, IDK. But I didn't knew, so I went with the other route of fixing the hardware by reballing. As I'm not an expert in that either and I could've done it but it's such time consuming process and not getting a desired result after all that is an option, so I didn't wasted that much time. Only what I did is give it a heat treatment in hopes to revive it. But it din't worked it showed that blinking red led as it did before but it become somewhat of more dead. But I'm glad I tried my best.
SO THANKS FOR NOTHING GUYS.
Click to expand...
Click to collapse
How many times told u. Install telegram app on pc and join rn3 group chat . Xda is forum u wont get quick reply.
Rest u ur choice. Bye.
Black_Stark said:
How many times told u. Install telegram app on pc and join rn3 group chat . Xda is forum u wont get quick reply.
Rest u ur choice. Bye.
Click to expand...
Click to collapse
The device is dead, nothing can be done now. You replied, similarly someone more knowledgeable on the subject could've as well. But they didn't. Why? IDK, maybe the site doesn't promote/share topics the way they should, maybe it did and someone didn't wanna waste their time. So what's done is done, and the facts are there.
Gurkirat_Singh said:
What's Happening :
When I turn on my phone, it gets stuck in pre-boot loop i.e. it gets stuck on initial mi logo(without loading sign) and stays there for (almost exactly) 10 minutes, meanwhile getting overheated, then gets restarted by vibrating & flashing the screen once, further just rinse and repeat.
It's actual state is unidentified i.e. IDK whether it's in soft brick, hard brick or broken state.
What I've Tried :
I've tried flashing the rom through fastboot mode.
I've tried flashing the rom through edl mode.
But always ended with the same result.
PS : I flashed the rom with 'clean all' option. I didn't used the 'clean all and lock' option, as unlocking the phone sometimes becomes a pain in the 'A', cause I'm pretty sure the result would've been the same.
Should I Try?
Using the 'clean all and lock' option.
Flashing another version of the miui rom.
What else to bring my phone back to life?
Final words :
On the time of writing this, I'm gonna keep troubleshooting and try some of these options as the time goes by, so I would let you guys know what I've tried.
If you guys are interested in knowing the back story a bit, LMK. I'd update the OP.
Click to expand...
Click to collapse
Put the phone in the fridge and see if boots or not.
Or replace the battery. It seems like an hardware issue so that is the furthest possible to go.
Related
Hello everyone,
As this is my first post, i'd like to apologise in advance if this issue i'm about to detail has been posted before, but after about a month's worth of trial and inevitable error, reading everything i could find and following every walkthrough i've come across to the t...i'm at wit's end here.
So, i've got a Galaxy SII GT i9100, standard euro version i suppose, my provider is Vodafone Romania (wretched buggers the lot of 'em).
My troubles had started ever since the update from 2.3 with which the phone had arrived, to 4.0.3. I made the update through my home wifi, and i'm guessing the software was provided by either Google, Samsung or Vodafone Ro.
In any case, 4.0.3 was a lot more sluggish and badly calibrated in terms of touch responses and video lag while streaming.
About a month ago i got another notification to update to 4.0.4. This update worked fine for about 20 minutes till the thing decided to freeze up completely, and not turn off from the power button held down a while.
After i had removed the battery and turned it back on, i simply got the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Naturally Kies is a steaming pile and recovery fails every time with a message composed only of empty squares instead of text, i'm guessing it's because i lack a certain language pack, but the only option is "OK".
So i turned to Odin, when that failed, instead of wiping the counter before sending it into the warranty, i did not. so they voided my warranty because it seems Odin is "unauthorized".
Multiple tries and failures later, quite a few attempts by other people that know more about this than myself...some have said i've got corrupt flash memory while other say "NAND rw corruption".
I'm a rather experienced pc builder...but this seriously stumps me.
I've also tried the walkthrough here on XDA with the same results.
So any new input would be much appreciated...be it through skype or another medium.
can you enter the download mode, if yes then try flashing stock firmware which comes with .PIT file (using odin)......may be that will help
try this thread as well http://forum.xda-developers.com/showthread.php?t=1457458
RazorwireClouds said:
Hello everyone,
As this is my first post, i'd like to apologise in advance if this issue i'm about to detail has been posted before, but after about a month's worth of trial and inevitable error, reading everything i could find and following every walkthrough i've come across to the t...i'm at wit's end here.
So, i've got a Galaxy SII GT i9100, standard euro version i suppose, my provider is Vodafone Romania (wretched buggers the lot of 'em).
My troubles had started ever since the update from 2.3 with which the phone had arrived, to 4.0.3. I made the update through my home wifi, and i'm guessing the software was provided by either Google, Samsung or Vodafone Ro.
In any case, 4.0.3 was a lot more sluggish and badly calibrated in terms of touch responses and video lag while streaming.
About a month ago i got another notification to update to 4.0.4. This update worked fine for about 20 minutes till the thing decided to freeze up completely, and not turn off from the power button held down a while.
After i had removed the battery and turned it back on, i simply got the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Naturally Kies is a steaming pile and recovery fails every time with a message composed only of empty squares instead of text, i'm guessing it's because i lack a certain language pack, but the only option is "OK".
So i turned to Odin, when that failed, instead of wiping the counter before sending it into the warranty, i did not. so they voided my warranty because it seems Odin is "unauthorized".
Multiple tries and failures later, quite a few attempts by other people that know more about this than myself...some have said i've got corrupt flash memory while other say "NAND rw corruption".
I've also tried the walkthrough here on XDA with the same results.
So any new input would be much appreciated...be it through skype or another medium.
Click to expand...
Click to collapse
sorry i forgot to mention that i can enter Download mode using Vol. down + home + power, BUT...i can't enter recovery mode or whatever it's called with Vol. up + home + power...that button combo only starts the phone with the same old error message.
also, i've tried this walkthrough
as far as i know if you can enter into download mode, your phone is not dead...........................i don't know much about android development but i am sure that your phone can be revived...........keep searching the forum and try contacting some of the sgs2 developers they might be able to help you
cheers
RazorwireClouds said:
sorry i forgot to mention that i can enter Download mode using Vol. down + home + power, BUT...i can't enter recovery mode or whatever it's called with Vol. up + home + power...that button combo only starts the phone with the same old error message.
also, i've tried this walkthrough
Click to expand...
Click to collapse
pretty much what i'm thinking as well, there should be a way to restore it without resorting to cannibalism and taking a broken phone's mobo.
but i have been searching and being new to these forums i've no clue who to contact, but anyways, thanks for the reply sir. my thanks
bumpdonkey.
Come on,are you trying different things like disabling kies/USB cables/ports/different PC.
Have you tired flashing the stock Rom through Odin? You can find it at sammobile.com.
Sent from my SGH-I727 using xda app-developers app
as i've stated in the first post, i've tried almost everything. this includes flashing a series of different roms, kernels, pits etc.
as well as trying it with kies uninstalled, and since it's been attempted by other people, i'm guessing it's superfluous to try it on another PC than my own because others have already done so with it. and the cable is just a cable.
i have the same problem and i still searching
when i try to mount the data partition it fail
i tried all things but still no solution
come on guys help us to revive our sgs2
so far, the most i've accomplished was bringing it from the error message to the boot screen where it remains forever...by flashing the bootroom.
but if i tick "nand erase all" it fails to do anything.
No bumping
Do not bump this thread. The answer will come because someone knows it, not because it's bumped every few hours.
which reatmne
sorry about that, i'll cut the bumping then...i'm just...beyond frustrated at this point...it's been a brick for about a month now...nobody seems to know how to fix the blasted thing
Maybe...
I had once got stuck.
If you could get to the recovery, i think you can try wipe data, wipe data, wipe data....................
Then flash stock rom, or those you think is reliable.
wipe and flash. wipe and flash.
If you can't, use ODIN....... the only way
flash and flash the stock rom or any others.............
if it works, there you are.
Hope it works!!
you may wanna read the whole topic before replying, just saying
Your phone's obviously stuffed and only one of two (but 95% likely only one) things is going to fix it (nothing anyone here can suggest will).
I think you know what they both are. Continuing to post to this thread is simply delaying getting your phone fixed or getting another phone.
RazorwireClouds said:
you may wanna read the whole topic before replying, just saying
Click to expand...
Click to collapse
Exactly pal.Surprised he didnt say "if only you could boot up the phone you wouldnt need to get it repaired"......lol
MistahBungle said:
Your phone's obviously stuffed and only one of two (but 95% likely only one) things is going to fix it (nothing anyone here can suggest will).
I think you know what they both are. Continuing to post to this thread is simply delaying getting your phone fixed or getting another phone.
Click to expand...
Click to collapse
if i may ask what are thee two things which are going to fix the phone cuz mein is in the same situation thanks
I'm stuck in a similar position I'm stuck at galaxy s2 boot screen can get to download mode but not recovery I havnt tryed Odin yet only because I don't know what I'm.doing with Odin could somebody direct me on where to get the right files n stuff for Odin please I would be really gratfull thanks
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Google Odin 3, use the 1.85 version. Get the stock Rom from sammobile.com for your device. Unzip Odin and then run it. In PDA browes to the stock Rom. Make sure only auto re boot and F. Reset are checked in odin. Then hit start. Check the stickies for more details. See vincom's in the development forum.
Sent from my SGH-I727 using xda app-developers app
Cheers mate am all sorted now bk rooted with the rom I wanted lol
Sent from my GT-I9100 using xda premium
Hello,
I am encountering a strange problem with my new Redmi Note 2, purchased from Top One. Whenever it is off and the battery is in, every 30 seconds it will vibrate and momentarily flash the white Mi logo as if it is about to turn on, then it will go back to black, then do this again in ~30sec. I have tried removing the back of the phone to see if it is an issue with the power button but it continues to happen whenever the battery is in. If battery is removed for ten seconds and then put back, the issue stops -- but then as soon as I turn the phone on, and then power off, it starts again. Otherwise the phone seems to run normally.
I flashed it to Miui 7.2.2.0 global stable Rom immediately after receiving it, and the problem has been there from the start. I believe I had noticed it there even before I flashed the new rom but I'm not sure as I hadn't yet interacted with the phone much...
Any suggestions? If you could please give me your instructions as basically as possible, and for Mac, I would appreciate it as I am a newbie. I flashed the rom using my Mac following instructions from the MIUI forms that showed how to do it in terminal after installing "adb/fastboot."
Thanks!
Seems to me that it is going into bootloader mode, instead of powering off completely. I am not sure how this could have started - perhaps a partially failed ROM upgrade at some point. I think you should return it (after restoring the original ROM) because trying to solve the problem might have to involve doing some low-level and extremely risky stuff.
Or for some weird reason the buttons get stuck and restarts to recovery.
When you try to boot into recovery, you get black screen->vibration->MI logo, and if you continue pressing the buttons you repeat the pattern.
Remove the battery cover and check if there's something in the buttons for a start..
Thanks for your responses
DarthJabba9 said:
Seems to me that it is going into bootloader mode, instead of powering off completely. I am not sure how this could have started - perhaps a partially failed ROM upgrade at some point. I think you should return it (after restoring the original ROM) because trying to solve the problem might have to involve doing some low-level and extremely risky stuff.
Click to expand...
Click to collapse
Could you give me a sense of what the low-level/risky stuff would be? Is it something I might be able to get done at a phone repair shop in the UK (where Xiaomi of course is not sold)? I ask because I'm required to pay for return shipping to China if I'm going to return device, and god knows how long the whole return process will take -- so if it's not a major hardware issue it might be worth it for me to explore finding a fix.
tonydeli7 said:
Or for some weird reason the buttons get stuck and restarts to recovery.
When you try to boot into recovery, you get black screen->vibration->MI logo, and if you continue pressing the buttons you repeat the pattern.
Remove the battery cover and check if there's something in the buttons for a start..
Click to expand...
Click to collapse
I don't see anything unusual in the buttons. As I said, if I remove the battery for ten seconds and then put it back in, I don't get this problem. It's only after doing a successful boot/shutdown (which works normally) that it starts again. So as far as I can tell it doesn't appear to be a mechanical problem.
littleozzyman said:
Thanks for your responses
Could you give me a sense of what the low-level/risky stuff would be? Is it something I might be able to get done at a phone repair shop in the UK (where Xiaomi of course is not sold)? I ask because I'm required to pay for return shipping to China if I'm going to return device, and god knows how long the whole return process will take -- so if it's not a major hardware issue it might be worth it for me to explore finding a fix.
Click to expand...
Click to collapse
The low-level+very risky stuff would involve flashing a full ROM. By "full", I mean inclusive of preloader, uboot/lk, etc. This is what makes it very risky, because if something goes wrong with the preloader/lk flash, the device could be bricked beyond what normal people could recover. An example of a ROM that flashes everything is: http://www.needrom.com/download/miui-7-2-3-0-redmi-note-2/
My current ROM is based on an earlier version of this, and I noted at the time it was released that it installs a preloader - but I am not sure whether I installed it complete with preloader or not (I probably did). From what I can see, nobody's device got bricked by installing this ROM, which is actually excellent (so much so that I inevitably return to it after trying something else). However, it is still risky to upgrade a preloader. I suspect that this may be what you need - but it may not resolve your problem anyway.
PS: beware of more recent Xiaomi ROMs that lock the bootloader. If you tried to do this risky process, you would be best advised to make sure that you are not flashing a ROM that locks the bootloader (i.e., the most recent ROMs coming out from Xiaomi).
DarthJabba9 said:
The low-level+very risky stuff would involve flashing a full ROM. By "full", I mean inclusive of preloader, uboot/lk, etc. This is what makes it very risky, because if something goes wrong with the preloader/lk flash, the device could be bricked beyond what normal people could recover. An example of a ROM that flashes everything is:
My current ROM is based on an earlier version of this, and I noted at the time it was released that it installs a preloader - but I am not sure whether I installed it complete with preloader or not (I probably did). From what I can see, nobody's device got bricked by installing this ROM, which is actually excellent (so much so that I inevitably return to it after trying something else). However, it is still risky to upgrade a preloader. I suspect that this may be what you need - but it may not resolve your problem anyway.
PS: beware of more recent Xiaomi ROMs that lock the bootloader. If you tried to do this risky process, you would be best advised to make sure that you are not flashing a ROM that locks the bootloader (i.e., the most recent ROMs coming out from Xiaomi).
Click to expand...
Click to collapse
Thanks for this. Could you point me to how I might be able to install a full official Xiaomi rom? (One that won't lock the boot loader.) My preference would be to get the global stable rom running as normal so that I can have the standard working phone with OTA updates. Or, is it easier to install this rom you've suggested with preloader, and then afterwards I can flash the official rom (assuming this fixes the problem)?
Also, are there any tutorials/clearer instructions for how to do this kind of install? The instructions on the link you've provided don't seem very clear...
Not sure if I'm gonna try this yet but leaning towards it if I feel confident enough I can execute it without screwing anything up...
littleozzyman said:
Thanks for this. Could you point me to how I might be able to install a full official Xiaomi rom? (One that won't lock the boot loader.) My preference would be to get the global stable rom running as normal so that I can have the standard working phone with OTA updates. Or, is it easier to install this rom you've suggested with preloader, and then afterwards I can flash the official rom (assuming this fixes the problem)?
Also, are there any tutorials/clearer instructions for how to do this kind of install? The instructions on the link you've provided don't seem very clear...
Not sure if I'm gonna try this yet but leaning towards it if I feel confident enough I can execute it without screwing anything up...
Click to expand...
Click to collapse
I personally wouldn't touch official ROMs with a bargepole. At the very least, xiaomi.eu, or ROMs based on it (like the one linked to). But each to his own. With regard to installation, I don't think you can get more detailed instructions than those given, which I will now try to present in clearer English:
Reboot to Recovery ( TWRP only )
Wipe Dalvik/Art
Wipe cache
Wipe data (note that TWRP allows you to do 2-4 in one go - they are the same as resetting to factory defaults)
Install ROM
Wipe cache and Dalvik/Art again (but do NOT wipe data)
Reboot
Wait for about 20 minutes while it builds Dalvik/Art, and other stuff
Done
Hopefully, this will cure the problem. If so, then you can install whatever ROM you want, following the same process as above. If not, then you still have an excellent ROM anyway.
By the way, doing any of this presupposes that you have already installed TWRP recovery. If not, then that is the first thing to do.
DarthJabba9 said:
I personally wouldn't touch official ROMs with a bargepole. At the very least, xiaomi.eu, or ROMs based on it (like the one linked to). But each to his own. With regard to installation, I don't think you can get more detailed instructions than those given, which I will now try to present in clearer English:
Reboot to Recovery ( TWRP only )
Wipe Dalvik/Art
Wipe cache
Wipe data (note that TWRP allows you to do 2-4 in one go - they are the same as resetting to factory defaults)
Install ROM
Wipe cache and Dalvik/Art again (but do NOT wipe data)
Reboot
Wait for about 20 minutes while it builds Dalvik/Art, and other stuff
Done
Hopefully, this will cure the problem. If so, then you can install whatever ROM you want, following the same process as above. If not, then you still have an excellent ROM anyway.
By the way, doing any of this presupposes that you have already installed TWRP recovery. If not, then that is the first thing to do.
Click to expand...
Click to collapse
Thanks for the English translation haha, I'll give this a shot. Just one more question -- when you write "install ROM", I should just treat the ROM the same way that I would any other, by flashing it via fastboot (as I did in OSX terminal) right?
littleozzyman said:
Thanks for the English translation haha, I'll give this a shot. Just one more question -- when you write "install ROM", I should just treat the ROM the same way that I would any other, by flashing it via fastboot (as I did in OSX terminal) right?
Click to expand...
Click to collapse
No. Steps 1 to 7 inclusive are done from TWRP Recovery.
DarthJabba9 said:
No. Steps 1 to 7 inclusive are done from TWRP Recovery.
Click to expand...
Click to collapse
Well, thanks again for your suggestion, but unfortunately it didn't succeed. I managed to install the custom full ROM you suggested with TWRP, and the problem persists; when the phone is off, I get this strange problem with the Mi logo flashing.
I'm investigating how to make a return, but I thought I would ask: do you have any idea whether this problem will negatively affect the phone in any other way? Because, if I'm unable to make a return, I think it's an issue I can live with (I rarely have my phone switched off anyhow), so long as it won't cause more problems down the line...
Something else I just realised: Apparently the problem doesn't occur when the phone is plugged into the USB (both electrical socket and computer). Starts up again as soon as I remove the plug. Perhaps that provides more context...
littleozzyman said:
Well, thanks again for your suggestion, but unfortunately it didn't succeed. I managed to install the custom full ROM you suggested with TWRP, and the problem persists; when the phone is off, I get this strange problem with the Mi logo flashing.
I'm investigating how to make a return, but I thought I would ask: do you have any idea whether this problem will negatively affect the phone in any other way? Because, if I'm unable to make a return, I think it's an issue I can live with (I rarely have my phone switched off anyhow), so long as it won't cause more problems down the line...
Click to expand...
Click to collapse
Well, I would hazard a guess that this is not a software problem. Clearly, the phone is trying to boot into bootloader mode or into recovery mode when it is meant to be completely switched off. This implies;
a) that there is a possibly a hardware problem somewhere (eg., something short-circuiting somewhere?), or
b) a virus/rootkit trying to dial home?, or
c) some other unknown fault?
None of these options would give me any peace of mind. If the problem is (b) then a good anti-virus or rootkit remover program would solve the problem. Search the PlayStore for those. If that doesn't solve the problem, then it's either (a) or (c) - and that is not good.
DarthJabba9 said:
Well, I would hazard a guess that this is not a software problem. Clearly, the phone is trying to boot into bootloader mode or into recovery mode when it is meant to be completely switched off. This implies;
a) that there is a possibly a hardware problem somewhere (eg., something short-circuiting somewhere?), or
b) a virus/rootkit trying to dial home?, or
c) some other unknown fault?
None of these options would give me any peace of mind. If the problem is (b) then a good anti-virus or rootkit remover program would solve the problem. Search the PlayStore for those. If that doesn't solve the problem, then it's either (a) or (c) - and that is not good.
Click to expand...
Click to collapse
Nothing shows up on anti-virus/rootkit. I guess I should really insist on getting a return. Hopefully they will process it without too much fuss/expense. If any other suggestions come to anybody in the meantime, I'd be glad to hear them.
I just noticed as well that someone posted with what seems to be the same issue to mine last year: http://forum.xda-developers.com/redmi-note-2/help/phone-rebooting-shutdown-t3232941 , with no resolution. Perhaps this is some kind of occasional manufacturing problem.
littleozzyman said:
Nothing shows up on anti-virus/rootkit. I guess I should really insist on getting a return.
Click to expand...
Click to collapse
Absolutely.
HW problem: Power Management IC
I too faced this problem and I suspected Battery to be the culprit . Anyway , i got it checked and repaired at a local (non xiaomi) repair shop that claims it was the issue with PMIC power management IC and that he has replaced the IC .
Now the phone works fine and does not enter into that bootloop even when charger is disconnected and phone is rebooted manually. I hope the problem is resolved .
However , the other issue is still persistent which is : copper colored washed out MI logo constantly appears on the screen and reinstallation of sw did not help either . In india these repairmen usually cant explain the problem area if it is outside of "Try and test" scheme .
I spent 1000INR to get it repaired but I highly doubt that PMIC is replaced. Coz this repair guy did this replacement in just 6 work hours. probability of getting the right part at right time at his disposal is very slim. And I had seen his workstation once, where i di not see any SMT repair station either. Which means that he cannot replace BGA package IC at all. Anyway, I will receive the phone tonight. Lets hope it works fine and the other problem gets rectified by flashing.
Saurabh Srivastava, Noida , India
Hello
I need some advice and help if someone can.
My LG V10 was rooted and on latest Eliminators room. It was working perfectly and few days ago while ending the phone call it just switched off.
Since then i have been trying to bring it back to life but without any success .
I can boot it to fastboot but no commands are accepted in fastboot mode, no download mode . It only goes to logo and the information that software can not be checked , further from there it goes nowhere . Since i am mac user , i installed VM of Win 7 and only thing it detects is Qualcom 9008......
Please some advice and help what is possible to do.
In fastboot mode i can not do anything.......
Sent from my iPhone using Tapatalk
This is the exact thing that happened to me last night too. I was wondering if my phone pushed the latest update on accident or something to cause it.
Another thread in the Q & A Section has reports of this happening and maybe being a hardware issue.
I plan on trying to do a full restore back to stock tonight when I get home from work to see if I can bring it back to life. I also read somewhere that you need to have the latest binary for fastboot to work.
The few minutes I messed around with it last night, my fastboot was sending but not writing. I'll keep you posted it I have any success tonight after work.
Side note the thread I mentioned above the S/N for the phones having issues started with 510...
Also, I can get mine to boot into recovery but once I try to erase or install it freezes and boot loops again.
I will play with it from tomorrow again. From yesterday i have gave it to one service center but they have not succeeded to do anything. I have succeeded in one moment to get to download mode which laster only about 2 seconds, not enough even to connect it to lg up, suspecting tht it is maybe something because of VM that doesn't' discover phone complerely. Tomorrow morning i shall pick it up and during next few days i shall try again, if i succeed to find a solution it would be good. I was also planing to do complete factory back up to stock last version. But...
Sent from my iPhone using Tapatalk
bildo said:
This is the exact thing that happened to me last night too. I was wondering if my phone pushed the latest update on accident or something to cause it.
Another thread in the Q & A Section has reports of this happening and maybe being a hardware issue.
I plan on trying to do a full restore back to stock tonight when I get home from work to see if I can bring it back to life. I also read somewhere that you need to have the latest binary for fastboot to work.
The few minutes I messed around with it last night, my fastboot was sending but not writing. I'll keep you posted it I have any success tonight after work.
Side note the thread I mentioned above the S/N for the phones having issues started with 510...
Also, I can get mine to boot into recovery but once I try to erase or install it freezes and boot loops again.
Click to expand...
Click to collapse
I have the same problem with my v10 do you found a solution ?
No. I bought a new phone and my v10 is now a paperweight. I have not really tried too fix either. Jumped on project fi and got a got a 5x on the cheap. Couldn't be happier.
I've had luck flashing my LG from within a virtual machine, running on top of Linux Mint. I tried both VMware Workstation and VirtualBox. Just make sure to install the guest additions within VMware, or the extension pack within VirtualBox. Also download the LG driver and install that inside the VM too. Each VM software may have settings relating to sharing a real USB port with the VM, make sure you look into that and enable the relevant options. Otherwise the VM may not detect the device.
On the other hand, my v10 isn't hardbricked, I'm just going to hold onto it as long as possible until it goes belly-up. Which it will probably do sooner rather than later, if the issues I've had are any indication. If you're only seeing Qualcomm 9008, fastboot not responding to any commands, and no download mode, this def sounds like a hardbrick. If you're still under warranty I would recommend getting it replaced by LG. If you have insurance then cash it in.
This is the 3rd v10 I've had, so far I've done 2 exchanges if I remember correctly. These phones are definitely susceptible to big issues. Like the now famous LG bootloop scenario.
Hope you get this figured out!
I only want my Wogiz WX40 to work properly again. It somehow got into a booting loop and I spent many hours figuring out how to flash it due to drivers acting unexpectedly, incorrect instructions for my device and so on.
I finally got it to flash with stock software I got from needrom using SP Flash Tool. However 1) none of the bottom keys work now and 2) it looks as if the resolution is set too high for the device and I think there is also some slowness when using the phone. I have tried clicking upgrade firmware and formatting the entire flash and using different versions of the software and the result is always the same - the bottom keys not working in particular makes it unusable. I tried downloading the stock rom from another location but after downloading it said I needed a password.
So what is the next thing I can try? I'm at my wit's end here and just want it to work again. Thanks for all help.
Anyone know what I should try? For example what custom RAM + firmware might I want to try? At this point I don't care what it is as long as it works. It's a MT6580 device if that helps.
God, I FINALLY got it working.
In case there's anyone else that runs into this: My mistake was getting the stockrom from needrom, every one of those roms for this phone is bad. Get the rom from shareas.us and use SP Flash Tool to flash it, and even then you have to try to get the one that isn't password protected with no password. Leave the battery in, turn the phone off, use option "format + download" in the software and click download BEFORE you connect the phone, NOW connect the phone and after a little while it will start downloading. Disconnect the phone when it's done and switch it on, it will take a REALLY long time to boot up the first time but it should then work.
That's what came from hours of trying to get it to work. The tutorials etc. online are so confusing, even some incorrect instructions like saying I should take out the battery that are completely false and I would never have gotten it to work if I paid more attention to them. I don't ever want to go through something like that again. I finally have my phone back.
Long story short, stock phone just randomly blew up and I'm trying to re-install its stock Android OS. Phone has never been rooted before, it just started to reboot on its own and now I'm in a position where I can only access download mode.
I'm in Odin, with what I believe is the correct firmware for my device (SM-N950U1) and I just keep getting a "Secure Check Fail: system" when trying to flash. it via Odin. The Odin log says "FAIL! (auth) right after trying to write system.img.ext4 for a few minutes. The "Secure Check Fail: system" is the printout on the phone screen itself.
Any clues?
Bump! Anyone?
playbacktri said:
Bump! Anyone?
Click to expand...
Click to collapse
I see that you have not received an answer. That is upsetting. I am also struggling with this exact same issue on a g955u1. Have not found a solution. Did you end up solving your problem? If so, what did you have to do?
ap7x942 said:
I see that you have not received an answer. That is upsetting. I am also struggling with this exact same issue on a g955u1. Have not found a solution. Did you end up solving your problem? If so, what did you have to do?
Click to expand...
Click to collapse
Nope, I have not solved the problem. I've scoured the internet and other people asking the problem all have not had any answers either. My assumption is that the actual internal memory of the phone is corrupted and won't let me write past a certain point, or on certain sectors, or something and its not actually fixable via software. I think everyone else just stops at this point and its never resolved because there is no resolution hah.
Good luck, let me know if you ever figure it out...
playbacktri said:
Nope, I have not solved the problem. I've scoured the internet and other people asking the problem all have not had any answers either. My assumption is that the actual internal memory of the phone is corrupted and won't let me write past a certain point, or on certain sectors, or something and its not actually fixable via software. I think everyone else just stops at this point and its never resolved because there is no resolution hah.
Good luck, let me know if you ever figure it out...
Click to expand...
Click to collapse
This phone I am working on is for a customer of mine. Thankfully, they have given me an open ended time frame. I have been working on this for about a week trying to figure out whats going on.
The memory corruption thing you were talking about resonates with me, because prior to my customer bringing this in, they had attempted a couple factory resets trying to resolve the original issue which was all the system apps crashing. The phone would reboot like someone killed all the processes. Pretty much from the moment it reached the home screen, and it was not power related. The problem persisted after their factory resets within recovery mode. And then I hit the phone with Odin and ended up with a partial flash. Soft bricking the phone.
You saying that kinda reinforces what I was already thinking, that it might be a hardware issue. Im not sure.
5 minutes ago I was able to get odin to successfully flash BL, CP, and CSC. It even brought me back to the Samsung logo for a minute but hung there. That's the most success I have had with this thing. Ive flashed numerous firmwares and every single one of them fails on system.img.ext4. After it reboots, it boots directly into this altered version of download mode with an emergency recovery error.
I have flashed dozens of phones before without issue. This is the first time I have ever experienced this one. You could be right but I refuse to accept defeat in this case lol so im gonna keep trying and ill report back if I have success.
ap7x942 said:
This phone I am working on is for a customer of mine. Thankfully, they have given me an open ended time frame. I have been working on this for about a week trying to figure out whats going on.
The memory corruption thing you were talking about resonates with me, because prior to my customer bringing this in, they had attempted a couple factory resets trying to resolve the original issue which was all the system apps crashing. The phone would reboot like someone killed all the processes. Pretty much from the moment it reached the home screen, and it was not power related. The problem persisted after their factory resets within recovery mode. And then I hit the phone with Odin and ended up with a partial flash. Soft bricking the phone.
You saying that kinda reinforces what I was already thinking, that it might be a hardware issue. Im not sure.
5 minutes ago I was able to get odin to successfully flash BL, CP, and CSC. It even brought me back to the Samsung logo for a minute but hung there. That's the most success I have had with this thing. Ive flashed numerous firmwares and every single one of them fails on system.img.ext4. After it reboots, it boots directly into this altered version of download mode with an emergency recovery error.
I have flashed dozens of phones before without issue. This is the first time I have ever experienced this one. You could be right but I refuse to accept defeat in this case lol so im gonna keep trying and ill report back if I have success.
Click to expand...
Click to collapse
Man, that sounds very very familiar to mine. I don't know if you found my other threads where I was asking for help, but I woke up with a phone that wouldn't turn on. Finally found the key button combo to get it to soft reboot, then it would turn on and just crash in the middle of using it after anywhere from 30 seconds to 5 minutes. If i started to use the phone heavily it would just shut off instantly and reboot back up on its own.
After clearing the boot cache, then doing a factory reset, it finally just stopped turning on at all (just samsung boot logo loop)
So I hit it with odin, unsuccessfully for 2-3 days, and then out of nowhere it just finally took a successful flash. However, it still just bootlooped, so I did a factory reset again and it put it back to being toast.
Since then, not a single successful complete flash from odin. I too can do the BL, CSC and CP files but I can't flash the AP file as it is writing the most data and finally fails about 3-4 minutes into to writing the system image file.
Again...good luck, ha!