Related
well i recently dropped my HTC wildfire in water. I took it to the service center a local shop
and get it cleaned. but right on the shop when the engineer repaired it; it keeps
on restarting again and again. i thought it was beacuse may be ROM get corrupted
and when i will return home i will boot into recovery and reflash it.
but when i came back to home i put the phone down and then tried to go to the
recovery , it again start rebooting again and again. i was unable to stay in recovery for a
few seconds. it shows the revolutionary recovery but again it reboot and shows the
HTC logo and then again reboot after few seconds. then i thought may be clearing the memory will
make any effect but still when i cleared memory from bootloader i managed to clear it and it
didn't gave me bootloop in bootloader. but as soon as i tried to again boot back to recovery from bootloader menu
it again start rebooting abnormally. well i thought there may be problem with the battery but when i put charger
in again the phone led shows orange color charging and then phone again start rebooting
when the charger was plugged in.
but it stays in bootloader on. battery checked it is working right.
now can somedbody tell me is it hardware fault or there is something wrong with software ??
i called the LOCAL HTC center they say that there is an IC in the motherboard of phone
it is responsible for making boot properly and may be water has runied it.
well as per them the repair is not possbile now because they just replace the whole board they
don't solder the IC'S and moreover in india HTC has halted the production of motherboards they
are not avaliable no more.
well is this the end of my little fellow phone ?
sachoosaini said:
well i recently dropped my HTC wildfire in water. I took it to the service center a local shop
and get it cleaned. but right on the shop when the engineer repaired it; it keeps
on restarting again and again. i thought it was beacuse may be ROM get corrupted
and when i will return home i will boot into recovery and reflash it.
but when i came back to home i put the phone down and then tried to go to the
recovery , it again start rebooting again and again. i was unable to stay in recovery for a
few seconds. it shows the revolutionary recovery but again it reboot and shows the
HTC logo and then again reboot after few seconds. then i thought may be clearing the memory will
make any effect but still when i cleared memory from bootloader i managed to clear it and it
didn't gave me bootloop in bootloader. but as soon as i tried to again boot back to recovery from bootloader menu
it again start rebooting abnormally. well i thought there may be problem with the battery but when i put charger
in again the phone led shows orange color charging and then phone again start rebooting
when the charger was plugged in.
but it stays in bootloader on. battery checked it is working right.
now can somedbody tell me is it hardware fault or there is something wrong with software ??
i called the LOCAL HTC center they say that there is an IC in the motherboard of phone
it is responsible for making boot properly and may be water has runied it.
well as per them the repair is not possbile now because they just replace the whole board they
don't solder the IC'S and moreover in india HTC has halted the production of motherboards they
are not avaliable no more.
well is this the end of my little fellow phone ?
Click to expand...
Click to collapse
The last thing i would suggest you is that to change recovery.try flashing some other recovery and see if it works.If the problem still persists,I'm afraid you'll have to give up on willy or buy a new second hand willy.Its pretty cheap these days.
Well i will definitely try to do that
Wasimk32 said:
The last thing i would suggest you is that to change recovery.try flashing some other recovery and see if it works.If the problem still persists,I'm afraid you'll have to give up on willy or buy a new second hand willy.Its pretty cheap these days.
Click to expand...
Click to collapse
well yeah i will try to do that i would be able to..can you tell me how to flash recovery from fast boot menu after connecting it with PC and re installing HBOOT drivers again. coz it was long ago that i had did it.:good:...
Download any recovery in pc49img format and put it on the root of your sd card. Then turn the phone on in bootloader mode, follow instructions and you're done. No need to connect to PC.
Donne
Wasimk32 said:
Download any recovery in pc49img format and put it on the root of your sd card. Then turn the phone on in bootloader mode, follow instructions and you're done. No need to connect to PC.
Click to expand...
Click to collapse
My phone is alive again and it is working one of my friend has repaired it.:good:
My note 3 n9005 international model is stuck in a loop trying to go into recovery mode every time.
The sequence goes as such:
- The phone vibrates and the screen shows a glimmer in the bottom of the screen, it goes away in a split sec.
- The phone proceeds to vibrate once again and after 2-3 seconds the phone boots up with the note 3 and such stuff.
- Up in the left hand corner it says: RECOVERY BOOTING. .... (dark blue text). Next line is: RECOVERY IS NOT SEANDROID ENFORCING (red text). Next line is: Set Warranty Bit: recovery (yellow text)
- The phone then turns off and wait for around 9-10 seconds and then the three steps above go into repeat again and again.
The only thing that stops this is pulling out the battery which i have done several times now ...
I have tried the two "Famous" key combinations AKA. Home + Power + Volume up or Volume down
but none of them seem to have any effect .. only thing that happens is that the "3-step process mentioned" now has a delay of about 15 seconds to continue instead of waiting only 10 seconds which i presume means that it turned off at some point really quick and then turned back on to begin the loop again.
Now for the cause of this mayhem:
I was trying to install a custom rom(Darklord Note 5 rom that converts your note 3 into a note 5 software) in which a Aroma installer was involved, but my TWRP recovery went into a freeze once it was trying to open up the aroma installer, i got out of this situation fairly easy by pressing the Home + Power button to turn it off and then proceeded to go into recovery and then reboot which went smoothly. But i really needed to change into this other rom since my current rom is terribly slow(CM 12.1). SO, i went around the net and found out that the aroma installer freezing was a common problem for certain versions of TWRP.
So i tried installing an earlier version (2.6.70 i believe) on top of the other one using an app called "flashify" .. which i believe is the source of this problem since it probably couldn't overwrite my current version of TWRP. And as such im now stuck in this devilish loop which is a pain in the arse.
P.S Overwriting from Clockword mod recovery 3.X to TWRP 3.X went smootly and there were no issues there .. so i guess the downgrading of the TWRP is the problem ??
I hope this is not such a seldom occurrence that you have no experience in which you can help me :-/
Please help me with this !
It might not be the only solution but when I've previously got the boot loops I've had to reinstall a stock rom from Sammobile and then root again and reinstall TWRP and then reinstall my chosen ROM using TWRP. You might loose data if you did not Nandroid backup
I can't do any of those things
samesung said:
It might not be the only solution but when I've previously got the boot loops I've had to reinstall a stock rom from Sammobile and then root again and reinstall TWRP and then reinstall my chosen ROM using TWRP. You might lose data if you did not Nandroid backup
Click to expand...
Click to collapse
Hi, it seems i haven't made myself clear enough ... i've tried the 2 key combinations as mentioned in the post .. but none of them have any special effect .. i have no way to boot into recovery mode or download mode.
So without download mode i have no way of using ODIN to reinstall stock firmware .. i am aware of how to use ODIN so if the download mode worked this whole thing would not be an issue for me since i could just do what you said in your reply.
But the problem is that it doesn't work ... so i dont know how to get into the phone and do stuff to fix it.
Also, i dont care about data such as photos and stuff ... the only thing i care about is my phone getting fixed!
Hope you can help or maybe someone you know for me
Florint45 said:
My note 3 n9005 international model is stuck in a loop trying to go into recovery mode every time.
The sequence goes as such:
- The phone vibrates and the screen shows a glimmer in the bottom of the screen, it goes away in a split sec.
- The phone proceeds to vibrate once again and after 2-3 seconds the phone boots up with the note 3 and such stuff.
- Up in the left hand corner it says: RECOVERY BOOTING. .... (dark blue text). Next line is: RECOVERY IS NOT SEANDROID ENFORCING (red text). Next line is: Set Warranty Bit: recovery (yellow text)
- The phone then turns off and wait for around 9-10 seconds and then the three steps above go into repeat again and again.
The only thing that stops this is pulling out the battery which i have done several times now ...
I have tried the two "Famous" key combinations AKA. Home + Power + Volume up or Volume down
but none of them seem to have any effect .. only thing that happens is that the "3-step process mentioned" now has a delay of about 15 seconds to continue instead of waiting only 10 seconds which i presume means that it turned off at some point really quick and then turned back on to begin the loop again.
Now for the cause of this mayhem:
I was trying to install a custom rom(Darklord Note 5 rom that converts your note 3 into a note 5 software) in which a Aroma installer was involved, but my TWRP recovery went into a freeze once it was trying to open up the aroma installer, i got out of this situation fairly easy by pressing the Home + Power button to turn it off and then proceeded to go into recovery and then reboot which went smoothly. But i really needed to change into this other rom since my current rom is terribly slow(CM 12.1). SO, i went around the net and found out that the aroma installer freezing was a common problem for certain versions of TWRP.
So i tried installing an earlier version (2.6.70 i believe) on top of the other one using an app called "flashify" .. which i believe is the source of this problem since it probably couldn't overwrite my current version of TWRP. And as such im now stuck in this devilish loop which is a pain in the arse.
P.S Overwriting from Clockword mod recovery 3.X to TWRP 3.X went smootly and there were no issues there .. so i guess the downgrading of the TWRP is the problem ??
I hope this is not such a seldom occurrence that you have no experience in which you can help me :-/
Please help me with this !
Click to expand...
Click to collapse
Hmm awkward, maybe you have hard bricked it? Idk maybe
MrHollywood said:
Hmm awkward, maybe you have hard bricked it? Idk maybe
Click to expand...
Click to collapse
Hmm, in the case of an hard brick .. what so you suggest i do ?
Do i go to the store to get it fixed. (my warranty actually expired 1 month ago) and in the case of needing such a fix .. how much do you think it would cost ?
Or do i wait for a solution from some guy on this page ?
Florint45 said:
Hmm, in the case of an hard brick .. what so you suggest i do ?
Do i go to the store to get it fixed. (my warranty actually expired 1 month ago) and in the case of needing such a fix .. how much do you think it would cost ?
Or do i wait for a solution from some guy on this page ?
Click to expand...
Click to collapse
First I would Google a solution, second I would wait about a week, who knows there might be a guy here who knows how to fix it, third of all and the end of all choices is to get it to a store, idk it might cost you at around 50-60 dollars. I once hardbricked my LG and they charged me 50 dollars. Let's hope your issues gets fixed without losing a lot of money.
MrHollywood said:
First I would Google a solution, second I would wait about a week, who knows there might be a guy here who knows how to fix it, third of all and the end of all choices is to get it to a store, idk it might cost you at around 50-60 dollars. I once hardbricked my LG and they charged me 50 dollars. Let's hope your issues gets fixed without losing a lot of money.
Click to expand...
Click to collapse
" Hard-bricked – it refers to the phone as totally jammed, unresponsive or no visible signs of starting to work as it suppose to be. No display at all. You can’t even access the Download Mode screen. The only resolution for this is by using the method called JTAG flashing, which is you are forcing to install the firmware back to the phone. The process that you are about to experience is not too easy; this includes disassembling the phone, some soldering job required and flashing by means of using a flashing device tool.
– This method means that you cannot save your device at all by yourself anymore. If you considered necessary to have your Samsung Galaxy Note 3 back to life, the best way for you to do is to bring the device back to your dealer. Explain impressive that might persuade them to have your Galaxy Note repair for free of charge or have an exchange for warranty. "
The process explained afterwards involves "download mode" which i can't access ... so yeah .. guess il'l wait for a bit for a response that might help me .. otherwise ... il'l just take it to the store i guess !
also .. what do you think about this part: " bring the device back to your dealer. Explain impressive that might persuade them to have your Galaxy Note repair for free of charge or have an exchange for warranty" ?
do you think it means explaining it to the dealer in detail what has happened .. or does it perhaps mean to act like a total fool and be like ; " umm .. is this supposed to be like this ?"
Hope you understood that one better than i, cause if i can get a free fix il'l be real happy !
Florint45 said:
" Hard-bricked – it refers to the phone as totally jammed, unresponsive or no visible signs of starting to work as it suppose to be. No display at all. You can’t even access the Download Mode screen. The only resolution for this is by using the method called JTAG flashing, which is you are forcing to install the firmware back to the phone. The process that you are about to experience is not too easy; this includes disassembling the phone, some soldering job required and flashing by means of using a flashing device tool.
– This method means that you cannot save your device at all by yourself anymore. If you considered necessary to have your Samsung Galaxy Note 3 back to life, the best way for you to do is to bring the device back to your dealer. Explain impressive that might persuade them to have your Galaxy Note repair for free of charge or have an exchange for warranty. "
The process explained afterwards involves "download mode" which i can't access ... so yeah .. guess il'l wait for a bit for a response that might help me .. otherwise ... il'l just take it to the store i guess !
also .. what do you think about this part: " bring the device back to your dealer. Explain impressive that might persuade them to have your Galaxy Note repair for free of charge or have an exchange for warranty" ?
do you think it means explaining it to the dealer in detail what has happened .. or does it perhaps mean to act like a total fool and be like ; " umm .. is this supposed to be like this ?"
Hope you understood that one better than i, cause if i can get a free fix il'l be real happy !
Click to expand...
Click to collapse
Yeah wait for a while. And what he meant was to lie lol to say you didn't do anything and somehow your device died, but unfortunately that only works when you have a warranty.
---------- Post added at 10:12 PM ---------- Previous post was at 10:03 PM ----------
Florint45 said:
My note 3 n9005 international model is stuck in a loop trying to go into recovery mode every time.
The sequence goes as such:
- The phone vibrates and the screen shows a glimmer in the bottom of the screen, it goes away in a split sec.
- The phone proceeds to vibrate once again and after 2-3 seconds the phone boots up with the note 3 and such stuff.
- Up in the left hand corner it says: RECOVERY BOOTING. .... (dark blue text). Next line is: RECOVERY IS NOT SEANDROID ENFORCING (red text). Next line is: Set Warranty Bit: recovery (yellow text)
- The phone then turns off and wait for around 9-10 seconds and then the three steps above go into repeat again and again.
The only thing that stops this is pulling out the battery which i have done several times now ...
I have tried the two "Famous" key combinations AKA. Home + Power + Volume up or Volume down
but none of them seem to have any effect .. only thing that happens is that the "3-step process mentioned" now has a delay of about 15 seconds to continue instead of waiting only 10 seconds which i presume means that it turned off at some point really quick and then turned back on to begin the loop again.
Now for the cause of this mayhem:
I was trying to install a custom rom(Darklord Note 5 rom that converts your note 3 into a note 5 software) in which a Aroma installer was involved, but my TWRP recovery went into a freeze once it was trying to open up the aroma installer, i got out of this situation fairly easy by pressing the Home + Power button to turn it off and then proceeded to go into recovery and then reboot which went smoothly. But i really needed to change into this other rom since my current rom is terribly slow(CM 12.1). SO, i went around the net and found out that the aroma installer freezing was a common problem for certain versions of TWRP.
So i tried installing an earlier version (2.6.70 i believe) on top of the other one using an app called "flashify" .. which i believe is the source of this problem since it probably couldn't overwrite my current version of TWRP. And as such im now stuck in this devilish loop which is a pain in the arse.
P.S Overwriting from Clockword mod recovery 3.X to TWRP 3.X went smootly and there were no issues there .. so i guess the downgrading of the TWRP is the problem ??
I hope this is not such a seldom occurrence that you have no experience in which you can help me :-/
Please help me with this !
Click to expand...
Click to collapse
Cheer up! Well not that much lol, I found a video that MIGHT be able to help you.
https://youtu.be/D2LZri5HT1E
Check it out and I am here if you want to ask some questions!
Maybe a USB jig will force the phone into download mode?
MrHollywood said:
Yeah wait for a while. And what he meant was to lie lol to say you didn't do anything and somehow your device died, but unfortunately that only works when you have a warranty.
---------- Post added at 10:12 PM ---------- Previous post was at 10:03 PM ----------
Cheer up! Well not that much lol, I found a video that MIGHT be able to help you.
https://youtu.be/D2LZri5HT1E
Check it out and I am here if you want to ask some questions!
Click to expand...
Click to collapse
It seems like we'll have to go with MIGHT since i just idetified it as being a stage 2 hard brick, i must have fiddled with it a little too much ... Hmm, the phone was getting old anyways and performance was faltering by the minute too. So i guess il'l check it out at the store if they can repair it for something like 50$ - 100$ .. otherwise, i guess il'l get myself a ****ty phone for now and wait for a new flagship smartphone to appear !
I was thinking about going for LG G5 .. good idea ? or do you have another suggestion
audit13 said:
Maybe a USB jig will force the phone into download mode?
Click to expand...
Click to collapse
Do you suggest buying one or making one myself (i found some guides about it ) .. which one do you think would perform best ? (assuming i make mine correctly)
Whether you make or buy doesn't matter as long as it does the job. I will say that a pre made jig is small and neat.
samesung said:
It might not be the only solution but when I've previously got the boot loops I've had to reinstall a stock rom from Sammobile and then root again and reinstall TWRP and then reinstall my chosen ROM using TWRP. You might loose data if you did not Nandroid backup
Click to expand...
Click to collapse
hey in same position and want to do exactly as you mentioned,start from scratch again which infact i dont mind at all..problem is im unsure of how to do it as all i can get w h en trying all else button combo's battery pulls etc is the start screen of twrp that just loops ..
thanks in advance for reading this
give a try with Kies 3
connect your phone with pc and open kies. there you see "phone recovery guide". click on it and it will try to reinstall the whole firmware and bootloader etc. screenshot attached
I believe kies has been replaced with smart switch.
audit13 said:
I believe kies has been replaced with smart switch.
Click to expand...
Click to collapse
if i may ask what is a jig???i ive seen something mentioned a few times briefly in tutorials suggesting to use one and im running out of options.tried samswitch and kies and phone wont connect..furthest i can get is when booting to recovery it loops at opening Twrp screen and it wont go to download mode..any help greatly appreciated
A USB jig is a small device that will force the phone into download mode.
https://www.xda-developers.com/need-a-samsung-usb-jig-build-your-own/
audit13 said:
I believe kies has been replaced with smart switch.
Click to expand...
Click to collapse
smart switch will not detect note 3 as it is developed for new devices like note 5 and onwards.
My note 3 and s4 worked with smart switch.
audit13 said:
My note 3 and s4 worked with smart switch.
Click to expand...
Click to collapse
ok. thanks for guidance. i will try it.
I have a TMobile/MetroPCS GS4 model SGH-M919N that got stuck in a boot loop last week. I was finally able to find working firmware last night and used Odin to flash. Once it got to PASS my phone automatically rebooted with the blue recovery boot text in the top left, but then it just went back into a boot loop. I tried all other firmwares and none of them got to 100% so now I don't know what else I can do.
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
alesu69 said:
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
Click to expand...
Click to collapse
Have you tried replacing the battery? I figured I would try that but I havent gotten around to it yet
Not yet, i have no spare battery. Looks like when i plug the charger my phone just vibrates, like it's rebooting, and it's not showing anything. I found a similar issue here: http://forum.xda-developers.com/showthread.php?t=2532447
Looks like one guy did solve his problem.
*need to mention that by dead I mean it shows the "Samsung Galaxy S4 GT-I9505" logo and also shows "RECOVERY BOOTING", even though I didn't enter in recovery mode. Looks like now it doesn't shows anymore "RECOVERY BOOTING", but still, it doesn't boot. I was able to flash firmwares via odin and kies, but still no luck.
LE: It start booting by.. magic, i got to samsung boot logo, but that's all, crashed again.
After flash with Odin, immediately boot into recovery, perform a factory wipe, and reboot.
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
alesu69 said:
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
Click to expand...
Click to collapse
How did you manage to get into recovery?
harary said:
How did you manage to get into recovery?
Click to expand...
Click to collapse
Yes, but if I leave my phone in recovery (stock or custom), it just either freezes, either reboots, even though i don't do anything, just let it idle.
I can't manage to boot into the ROM 'cause eventually it will reboot. I couldn't finish the setup wizard.
OK so I don't know if this helps, but I managed to at least get past the "blue recovery boot" part. When the phone vibrated I let go of the power while still holding home + vol up, and I managed to get to the android guy with a blue progress bar below him. My phone shut off as the progress bar got 80-90% but now I know it's not impossible to start recovery.
Well, nothing works. After flashing pit file, an 4.4.2 odin prerooted image from here, cf auto root and then twrp, it will still randomly reboot. I manage to get past the boot logo into setup wizard, but phone just freezes after a couple of minutes, can't finish the setup wizard. Also, if i idle in twrp it will reboot sooner or later, tested already.I left my phone idling in twrp just to recharge my battery.
At least i have no more "unable to mount /data" errors.
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Operation Ivy said:
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Click to expand...
Click to collapse
What do you mean with back and forth?
harary said:
What do you mean with back and forth?
Click to expand...
Click to collapse
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend who repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
alesu69 said:
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend which repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
Click to expand...
Click to collapse
I got several times into Recovery Mode now, flashed several ROMs. I had no issues with freezing, especially not in TWRP Recovery Mode. But sometimes if i am trying to go into Recovery Mode or i just want to start ROMs, the screen turns into yellow behind the Samsung logo. If i dont take out the battery this wents into a complete white, but nothing happens.
Yes please tell if you got some news..
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Joashrox said:
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Click to expand...
Click to collapse
But it is sure that the power button is working because i get this blue "recovery booting". Or am i wrong?
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
alesu69 said:
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
Click to expand...
Click to collapse
Replace power button to new one. I have the same problems with s3 and this works. Try it.
Sent from my GT-I9300 using XDA-Developers mobile app
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
alesu69 said:
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
Click to expand...
Click to collapse
If You can't charge phone... Yup, motherboard is died. If You plug the charger and see something this have to be button but if You plug charger and don't see anything this is motherboard.
Mi A1 bricked, hard resetted it by opening the back cover and shorting two points.
It gets detected by mi flash tool but I cannot flash the stock room. It is giving me "cannot receive hello packet" and then it times out.
Any help will be appreciated.
Thank you.
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
foggs said:
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
Click to expand...
Click to collapse
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
foggs said:
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
Click to expand...
Click to collapse
Yup, I ruined one of my usb-C cable trying do do deep flash that way. I failed, so I went to one repair shop and open up the device and did the "two point short thing", which helped to be recognized by the flash tool. Then it showed me that "hello packet" thing.
Then I dug around the Internet for couple of hours and changed the USB port on laptop. I also restarted the laptop after I reinstalled the drivers. Then it actually flashed that ROM I mentioned above. But just that ROM. I tried the latest to oldest versions and all of those ROM would flash but then they will brick the phone again. Only that one worked, i.e. helped me to get to bootloader. But alas it is stuck there, no matter how many times I clean flashed it, it is refusing to boot to system. It gives me "Your SYSTEM HAS BEEN DESTROYED" message on every boot. It only goes to bootloader if I press Volume Up + Power button while booting. And it's a dead end for now. I don't know what else to do.
Also this phone was bought in Hong Kong and its warranty won't work where I am right now. I already took it to the authorized service center and those lazy people told me to change the motherboard and it will cost around $180. So I took it back. lol
Disable driver enforcment to get the hello packet.
TrueMS said:
Disable driver enforcment to get the hello packet.
Click to expand...
Click to collapse
still no hello packet
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
:victory: Held the power button, clicked flash.. Success :good: it's in the process of flashing now. Thank you
Edit: successful flash now to just let it charge up. Thanks again guys for the help/suggestions ?
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
foggs said:
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
Click to expand...
Click to collapse
Ur presist partition is damaged..thr are many guides here about recovering it
Do the "factory flash" mode in MiFlash under EDL mode as a last resort. May wipe your IMEI and MAC's, not sure.
Could not receive magic packet is solved by using USB2 port, Windows 7 x86 (32-bit) in a VM, or power-cycling the device and starting over, any or all of the above.
Deep flash cable is only for kicking the phone out of diagnostic mode and into QDFlash mode. Not necessary if using test point. I had to use testpoint method myself, couldn't get deepflash cable to work for getting out of diagnostic mode. I hope I can get it working next time though when I inevitably brick it from repartitioning; as I broke my screen when disassembling
apexashwin said:
Ur presist partition is damaged..thr are many guides here about recovering it
Click to expand...
Click to collapse
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Did you find the guide about fixing constant reboot? It's around somewhere, might be on MIUI forum.
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Please try presist resurrector from guides section
I think i've got it back to life.
first tried to flash 7.1.2 stock the earliest one (tissot_images_7.8.23_7.1), it hung on flashing it for nearly an hour with no success, closed the miflash application then tried another 7.1.2 (tissot_images_7.10.30_7.1)flash successful, then in stalled twrp did the persist command and reboot nearly got to the home screen just never getting over the line. then i flashed January 8.0 oreo (tissot_images_8.1.10_8.0) and was able to get on to the home screen/go into settings/enable developer options but it would eventually reboot itself, went back into twrp and did the persist command again and reboot.. success (fingers crossed) now downloading/applying April security update as i type this.
Boo installation problem with the update
looks like i lost my imei, https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190 this is going to be a pain.. i'll post back when i try this. need a break from this mess ive made lol
thanks for the help/suggestions appreciated big time.
edit: up to the latest update April 1 security patch.
all done, down to 7.8.23 rom, did the stuff to get the imei back then flashed latest oreo rom
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
Man, I was trying to fix my Redmi Note 4X for the past 6 hours and you were the ONLY guy to talk about this. Thank you so much. :victory:
THANK YOU
udaan said:
it was solved after i changed the usb port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then twrp. But after flashing aosp extended rom it gave me "the system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
man you just solved my problem and saved for me like 180 eur thank you you are a god !!!! Thanks for using this site !!!!!!!!!! <3 <3 <3
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I was unable to flash on MiFlash and after changing USB port I managed to do it!.
Many thanks!
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
I love you!
Hello everyone.
My friend has been using ASUS Zenfone Max (ZC550KL, MSM8939) since one and a half year. Unfortunately, it seems in bricked state as of now. Following were the series of events that has led to current situation. Please go through it (although it's long), so that u have idea of what has been done.
Last week, due to heavy raining, some water crept inside mobile phone. We tried to switch off phone, but due to non-removable battery, we couldn't. When I pressed the power button for long enough time, it would restart. The touchscreen was also misbehaving. So, what we did, is we let it discharge and switch off overnight, by opening back cover, below the fan.
Next day, when we booted up (made sure that phone was dry, no putting in rice and all that) the touch-screen stopped working. We went to ASUS service center, and they told us a huge cost. Since, phone was out of warranty, we went to a local guy who replaced the touch-screen digitizer at a lower cost (maybe he put a resistive one). Phone started working completely normally, all the functions.
Next day, due to my friend's negligence, the phone again got discharged and switched off. Now, when we tried starting it, it went till android is starting, and stuck there. We waited for 6.5 hrs, then forced reset it (long press power key). Now it got stuck at ASUS logo. We again waited for >4 hrs. Again we tried 2-3 times, it always got stuck at ASUS logo. The phone was able to go in Stock Recovery and Bootloader (CSC) mode. The bootloader was locked and debugging mode not enabled.
*In recovery mode, following messages were coming "E: unknown volume for path /factory"
Before going to ASUS service center, we have tried following ROMs/ updates (in sequence):
factory reset from recovery mode
UL-ASUS_Z010_2-WW-13.8.26.113-user.zip [adb sideload]
UL_ASUS_Z010_2-WW-13.8.26.80-user.zip [adb sideload]
WW_ZC550KL(8916)-13.8.26.92_M3.1.42_Phone-user.raw.zip [ASUS flash tool] wrong firmware
WW_ZC550KL_8916_V13.8.26.60_M3.1.40_Phone-user.raw.zip [ASUS flash tool] wrong firmware
WW_ZC550KL(8939)-13.8.26.98_M3.1.42_Phone-user.raw.zip [ASUS flash tool]
WW_ZC550KL_8939_V13.8.26.63_M3.1.40_Phone-user.raw.zip [ASUS flash tool]
IN_ZC550KL(8939)-13.8.26.98_M3.3.10_Phone-user.raw.zip [ASUS flash tool] (we thought IN was for India)
UL-ASUS_Z010-WW-13.8.26.76-user.zip [adb sideload]
In all of above, the ASUS logo went till android is starting and stuck, for >3 hours.
In between, we flashed wrong ROM (by mistake).
Even now, the mobile can go into Recovery mode and CSC mode. We went to Recovery mode and would verify on top whether the specific ROM has loaded or not.
The recovery mode would change the version properly every time after update.
Every time after adb sideload or flashing, the mobile would go till starting android and stuck. After waiting good enough time (patiently) when we restart, it would get stuck at ASUS logo.
Finally, we gave to ASUS service center, where they said: "Mobile not accepting software, need to change motherboard", for which we denied, because the cost of motherboard replacement is 87.5% of overall mobile cost!!
Anyways, current situation is: mobile enters the recovery and boot-loader mode. Boots till ASUS logo. Properly recognized in adb and fastboot. On trying to flash custom recovery or boot, it says "Remote: permission denied" (might be because of locked boot-loader) and was unsuccessful.
We don't know what to do further. We are planning to give it to local repair guy, to see if he can do something. But we thought to post here first. Any suggestions are welcome.
More importantly, we want to understand possibly what has happened and why. ASUS guy told that internal memory chip is damaged, but how? If it was, why phone started working properly once, and got damaged once we rebooted?
Thanks in advance
https://drive.google.com/file/...ul1vuE3yJwUjVpSDJMbUJZanc/view
flash with qfil in 9008 mode
Then again flash latest flash filezip with mmc card from asus support ... if not sucess contact me on telegram https://t.me/vikastelecompathankot
Sent from my SM-G935F using Tapatalk