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
Related
Hi everyone, I'm a new member to the forum, but have been a follower for quite some time.
Let's start by introducing my device wich is:
EEEPad Transformer TF101G with ICS running the latest WW_9.2.2.6 firmware.
The device is rooted and running ASUS stock recovery.
Everything was working fine until I decided to do a Cold Boot.
It got stuck on the cold boot menu for like 3 hours and I decided to turn it off.
After that it got stuck on the inicial Asus splash screen. I forced it to turn off a couple a times and it eventually booted up.
I knew something wasn't right, so I backed up all my files and applications.
Then decided to do a factory reset through POWER + VOL-
After that it never booted again, and after a few seconds on the splash screen I hear a click noise, like the hard drive is turning off.
When I try force it to turn off, it starts up again automatically.
I've tried to flash it through nvflash, but being a TF101G it also means it is sbkv3, wich is not supported by nvflash.
Also tried boot recovery tools, but it won't even start, because as I try to connect it to the computer through adb mode, after that "click" noise, the device becomes disconnected.
I didn't try any dangerous applications and stuff like that, just decided to do a simple cold boot, the device is a week old.
If I'm posting this in the wrong section I apologize.
And hope someone can come up with a good idea.
Thanks in advance.
Obviously somethings corrupted and in my opinion the only way to fix it would be to reflash the rom in apx mode using nvflash but that doesn't seem to be possible for your device as of yet but if everything is still stock maybe you can unroot the device (or play dumb) and get it replaced under warranty?
I don't think I can unroot it, since it won't run abd mode.
I'm trying to find a way of not having to send it to warranty.
Saving it as a last resort...
Akusura said:
I don't think I can unroot it, since it won't run abd mode.
I'm trying to find a way of not having to send it to warranty.
Saving it as a last resort...
Click to expand...
Click to collapse
Eek.. since it was factory resetted I think you need to send it to warranty. Not much we can do now with just a splash screen on sbkv3
I don't consider myself an advanced user.
But I really did search everywhere and I got the idea that only with APX and without a compatible NVFlash I was screwed.
But I still had some hope.
Do you think they will give me trouble because of it being rooted?
I my opinion I don't think they will ever know, because It won't boot, It won't run recovery mode (stock) and nothing else at all, the only way to fix it is to flash it, but maybe I'm just being naive.
I treated it with all the care in the world, so only by divine intervention it is a hardware problem.
But you never now...
you should be ok (should)......
i done pretty much the same thing to a customers TF and Asus fixed it no problem.
The fact is that I actually didn't do anything wrong.
Just a cold boot that didn't work, followed by a a factory reset...
How long did it take for yours to get fixed?
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:
I've been messing around with my phone, trying to flash CWM and CyanogenMod (to no avail), and yesterday something happened. I woke up, my phone was dead so I started charging it. It booted into the Stock OS (the one that ships with the G2--build D20010o I think). Shortly after, a message appeared on the screen about an update the phone was going to install (I'm assuming one that AT&T was pushing to my phone), and shortly after it powered down on its own. I have not been able to get it to boot into the OS since.
Before all of this happened, I rooted the phone with IORoot, tried to flash CWM (I think successfully), but was not able to install CyanogenMod, so I flashed an earlier build of the stock OS (D20010o), rooted it again (I'm not sure that I had to--I think it stated that my phone was already rooted), tried to flash CWM again (unsuccessfully this time), and I gave up. Then this problem occurred.
Every time I try to power on the phone, the LG logo flashes, and the screen stays on, but it's black. If I try to do a factory reset via the hardware buttons, I am able to see that screen, but as soon as I follow the instructions of pressing the power button twice, it says that it's initializing the reset, but then the phone's screen goes black again--not sure if the screen is on or off, though. The LED light is also not on during any of this.
I'm unsure what to do. I've had the phone for about 6 months, but I had not owned an Android before that--iPhone user for 3 years. I obviously did not do enough research or ask enough questions, but I would like my phone to be in a usable state. I would greatly appreciate any help that anyone can give me!
NEVER take an OTA with a recovery.
Use the lg flash tool to go back to stock
http://forum.xda-developers.com/showthread.php?t=2432476
Sorry, should have also mentioned that I can't boot into Download Mode. I'm assuming there's no .kdz file for AT&T, and the other method in that link requires Download Mode. :/
Hi, my wife got an Asus Zenpad 10 (Z300 series) tablet not too long ago, and recently it seemed to be acting up. It didn't seem to know what its battery level was so it'd suddenly shut down and would rarely stay on for a few hours if that.
I've been reading these forums and Google searching every evening for days now to no avail.
The the other day when i turned it on, it was in a bootloop. I had this happen on my own tablet so I was aware of using ADB and the recovery menu to wipe the davlik cache.
Except, that this Asus tablet only has fastboot screen (which I'd not seen before - my Samsung went to a different recovery mode), so I've been researching that more recently.
I got ADB and Fastboot working, erased the cache via Fastboot which stopped the bootloop, but it would only go as far as the logo with the little spinner circle. After messing around with fastboot trying to do a factory reset and put a custom recovery on it (TWRP) it now will only boot to the Asus logo and not even have a spinner anymore!
The flashing of anything - recovery, stock rom from ASUS (this file as I found elsewhere on these forums: UL-P01M-WW-3.3.8.0-user.zip -- although I'm not entirely sure i'm flashing correctly).
Anyway, I'm stuck with only an Asus logo or fastboot mode screen and am not that good with fastboot/adb since I only had to delve into it once to fix my own tablet over a year ago.
If anyone can help that'd be very much appreciated! :good:
[update]
OK so after failing to flash any zips (or anything!) to the device, I left it on in fastboot mode while I went to work. Now upon coming home the tablet is just a black screen! The laptop recognises it because Windows makes that chime sound when its plugged in via USB. But other than that, I can't get a response out of it Button combinations don't seem to help so now I'm not sure what to do!
Can anyone help me please? :crying:
Unless the bootloader is locked, you may have made a mistake trying to flash the ROM and trying to install a custom recovery. Anyways, if you hadn't made any changes yet to the system, I would have said check the battery first because it may be malfunctioning and not the phone it's self. I know from experience that it may have been the battery considering the way you said it was not reading the battery percentage right and shutting down. And that "bootloop", this was probably happening because it didn't have any power to start up the device as this is exactly what my device did when I had a faulty battery. My best bet is to 1 try to get a new battery, and then 2 see if your system is still intact otherwise try and reflash with the stock ROM (through adb or any computer to android debugger) and then reinstalling the right recovery that goes with the device or that of which is c-o-m-p-a-t-a-b-l-e.
Using CM12.1 on my SGH-T999
I exactly got the same issue, nothing I particularly have done as far I know, my tablet suddenly rebooted and now is stuck on Asus logo with the little circle that keeps turning.
I tried to let it go till my tablet get completely discharged and also tried to charge it completely, nothing change.
And when I wanna access to the recovery, I just get the green android mascot with the message "ERROR!". So I can't even access the recovery to reset my tablet :crying:
Edit: Tried a fastboot erase userdata and an erase cache, still bootlooping
Sorted
The only way I fixed this was by returning it to the shop and having the device replaced! Not the ideal solution, but it worked. :good:
MrLewk said:
The only way I fixed this was by returning it to the ship and having the device replaced! Not the ideal solution, but it worked. :good:
Click to expand...
Click to collapse
I guess I will have to do the same
MrLewk said:
Hi, my wife got an Asus Zenpad 10 (Z300 series) tablet not too long ago, and recently it seemed to be acting up. It didn't seem to know what its battery level was so it'd suddenly shut down and would rarely stay on for a few hours if that.
I've been reading these forums and Google searching every evening for days now to no avail.
The the other day when i turned it on, it was in a bootloop. I had this happen on my own tablet so I was aware of using ADB and the recovery menu to wipe the davlik cache.
Except, that this Asus tablet only has fastboot screen (which I'd not seen before - my Samsung went to a different recovery mode), so I've been researching that more recently.
I got ADB and Fastboot working, erased the cache via Fastboot which stopped the bootloop, but it would only go as far as the logo with the little spinner circle. After messing around with fastboot trying to do a factory reset and put a custom recovery on it (TWRP) it now will only boot to the Asus logo and not even have a spinner anymore!
The flashing of anything - recovery, stock rom from ASUS (this file as I found elsewhere on these forums: UL-P01M-WW-3.3.8.0-user.zip -- although I'm not entirely sure i'm flashing correctly).
Anyway, I'm stuck with only an Asus logo or fastboot mode screen and am not that good with fastboot/adb since I only had to delve into it once to fix my own tablet over a year ago.
If anyone can help that'd be very much appreciated! :good:
Click to expand...
Click to collapse
Asus has the firmware (Nougat) for this Z300M but I've no idea how you would get this loaded. Something to learn but as long as the OS is available you should be able to get back stock, latest OS............
zls
I am in need of serious help! I dropped my phone off a 2nd story, smashed the screen completely. So I took my wife's old stylo 2 plus (exact same phone) stuck my Sim and SD into it, registered through metro pcs, and it worked great.
I did software update because I was really excited (my old stylo 2 was rooted and had many problems along with being unable to update android software).
Update took about an hour, then said failed. After that it has been unable to boot up. I tried recovery mode, it offers to factory reset. Again reboots and stuck at logo screen. Says error device is corrupt, cannot be trusted, will not boot. I press power it says press power again to boot anyway. Restarts and sticks at logo screen. Device is basically untouched. No oem unlock, no debugging, no developer options, nothing has been touched ever, the phone is 100% stock. I even did factory reset before I started using the phone.
Can someone please help me at the least flash trip so I can fix this??
I am not new to this, but has been 5 years since I flashed anything. The problem is, is that it's still locked, and can't boot up. The phones bricked and never been touched!
If I can get twrp flashed I can go from there, I need a way to unlock it, or flash without unlocking.
Please help me I need my phone for work. I'd rather not switch back to an old smashed screen
Cecil12 said:
I am in need of serious help! I dropped my phone off a 2nd story, smashed the screen completely. So I took my wife's old stylo 2 plus (exact same phone) stuck my Sim and SD into it, registered through metro pcs, and it worked great.
I did software update because I was really excited (my old stylo 2 was rooted and had many problems along with being unable to update android software).
Update took about an hour, then said failed. After that it has been unable to boot up. I tried recovery mode, it offers to factory reset. Again reboots and stuck at logo screen. Says error device is corrupt, cannot be trusted, will not boot. I press power it says press power again to boot anyway. Restarts and sticks at logo screen. Device is basically untouched. No oem unlock, no debugging, no developer options, nothing has been touched ever, the phone is 100% stock. I even did factory reset before I started using the phone.
Can someone please help me at the least flash trip so I can fix this??
I am not new to this, but has been 5 years since I flashed anything. The problem is, is that it's still locked, and can't boot up. The phones bricked and never been touched!
If I can get twrp flashed I can go from there, I need a way to unlock it, or flash without unlocking.
Please help me I need my phone for work. I'd rather not switch back to an old smashed screen
Click to expand...
Click to collapse
You need to download the kdz(device firmware) and flash it in download mode using lg up.
Sorry for the super long delay. I did what you said, and was able to use my phone again in no time. Thank you very much!
LG Stylo 2 Plus
Cecil12 said:
Sorry for the super long delay. I did what you said, and was able to use my phone again in no time. Thank you very much!
Click to expand...
Click to collapse
Hey would you be able to tell me which firmware worked or possibly even a link. I am having issues with getting one to work on the lg stylo 2 plus using lg up.