Hi!
I desperately address you today to ask you for help with my Huawei G615 (U9508; 1GB Version so it’s not Honor2/U9508B, but shouldn’t make a difference).
Problems:
- Phone won’t turn on (seems to be a bootloop).
- Phone won’t charge.
- Can’t find many of the needed files for flashing. So I need working mirrors or would appreciate uploads.
History:
Early 2013: Bought, standard Android 4.0.4 version, rooted by myself.
April 2015: Updated/Flashed to official (?) 4.2.2 with EmotionUI 1.6, rooted afterwards. Since then (not sure, maybe it’s unrelated to the update), I had multiple, annoying error messages when Wi-Fi got (re-)connected, but ignored it for months for not finding a solution.
Indeterminate timespan: State of battery charged wasn’t shown correctly, phone shut off too early. Used app “Battery Recalibrator” to fix this, needed some attempts but finally worked.
16th Feb. 2017 (Day X): Accidentally dropped phone (1-meter drop height, good TPU/silicon phone case cushioned it; no visible damage to phone or battery, no software-crash). Phone continued to work normally. Charged it to 100% before sleeping.
X+1: Phone was 99% after waking up, then suddenly 12%, shut down on 10%. Showed 0% afterwards, plugging it in to charge didn’t help. Despite charging it says 0%, powering on (only possible when charger plugged in) leads to bootloop (Huawei Logo, Android Logo, Huawei Logo (because it restarts)). Decided to put the phone on the cool window board over night without charging it.
X+2: Tried again to turn it on, after many attempts it magically turned on. Worked for the whole day, I still tried to flash the phone to get rid of my other Wi-Fi error log problem (and to prevent other possible problems by doing a fresh new start), didn’t seem to work. Charged it to 100%.
X+3 (today): Phone was already powered off when I woke up. Still can’t turn it on.
What I also tried continually:
- Tried charging with different power adapters or directly from USB. Still 0%.
- Tried wiping cache, wiping/factory reset.
- Flashing it to official 4.0.4. and 4.2.2., seemed not to work because it was over after some seconds, but the SDROOT/dload folder is ~1GB (although it said it worked, see spoiler).
Spoiler
When in recovery and choosing “apply update from external storage”, and then “dload” it says it failed to mount /sdcard (E:; “no such file or directory”).
Then error to open /sdcard/dload (“no such file or directory”)
Then
“Install from SD card complete.
cust copying files.
copy cust files succeeded.”
But as I said, that's possibly not true that 1GB gets copied in some seconds.
Status now (as I remember from Day X+2 when it worked):
- 4.2.2
- EmUI 1.6
- Android system recovery <3e>
- USB-debugging should be turned on (not sure) and phone should be rooted (Superuser was still installed after wiping, but it said it needed an update, so it might not fully work).
- Kernel and other software stuff: Can’t remember, can’t turn on the phone. And don’t know what they all mean tbh, I’m glad I know a little about the differences of Android official and custom ROMs and what a recovery is (and that I may need the Chinese recovery for flashing I cannot find online).
Further Details:
I personally don’t think the fall caused my problems because it continued to work for the whole day and the drop was cushioned. What I suspected: It could be an extreme case of the battery charge status problem. The phone thinks the battery is still 0% although it’s not. So it shuts itself off. Or the bootloop is caused by faulty software/ROM, although I didn’t change anything before the problems appeared.
I’ve read through several manuals and now get some sense of the topic, but I still don’t know everything relevant. Also, most of the links to important files are dead.
In addition, a problem I have is that despite reading through lots of threads, they require me to have a working phone, but mine is stuck in a bootloop.
What I want:
A clear, new phone software. Doesn’t matter which Android version or if official or custom ROM. Just want a working phone without the Wi-Fi error, so a fresh new start, a clean flash.
So: How do I do it, and importantly, where can I find the needed files?
(Even though I might buy a new phone next month, I want this one to be fixed so I can gift or sell the phone.)
Software I already have:
HiSuite, HuaWei_USB_Driver.exe, Android SDK, dload-B115 (folder, should be official Android 4.0.4), dload-B703 (folder, should be official Android 4.2.2), cm-10.1-20131006-EternityProject-hwu9508.zip (CyanogenMod 10.1 from Eternity Project); already rescued my data, so I’m ready to wipe.
Software that might be missing:
Chinese recovery, fastboot mod (what for?), CWM (what’s this, what for?), TWRP (what for?).
Many thanks in advance!
EDIT:
As recovery mode (Power + VolumeUp) works and the phone can be on for hours when in this mode (as long as it's plugged in), I assume that it's not the battery but a soft/firmware problem.
Zockerfreak112 said:
Hi!
I desperately address you today to ask you for help with my Huawei G615 (U9508; 1GB Version so it’s not Honor2/U9508B, but shouldn’t make a difference).
Problems:
- Phone won’t turn on (seems to be a bootloop).
- Phone won’t charge.
- Can’t find many of the needed files for flashing. So I need working mirrors or would appreciate uploads.
History:
Early 2013: Bought, standard Android 4.0.4 version, rooted by myself.
April 2015: Updated/Flashed to official (?) 4.2.2 with EmotionUI 1.6, rooted afterwards. Since then (not sure, maybe it’s unrelated to the update), I had multiple, annoying error messages when Wi-Fi got (re-)connected, but ignored it for months for not finding a solution.
Indeterminate timespan: State of battery charged wasn’t shown correctly, phone shut off too early. Used app “Battery Recalibrator” to fix this, needed some attempts but finally worked.
16th Feb. 2017 (Day X): Accidentally dropped phone (1-meter drop height, good TPU/silicon phone case cushioned it; no visible damage to phone or battery, no software-crash). Phone continued to work normally. Charged it to 100% before sleeping.
X+1: Phone was 99% after waking up, then suddenly 12%, shut down on 10%. Showed 0% afterwards, plugging it in to charge didn’t help. Despite charging it says 0%, powering on (only possible when charger plugged in) leads to bootloop (Huawei Logo, Android Logo, Huawei Logo (because it restarts)). Decided to put the phone on the cool window board over night without charging it.
X+2: Tried again to turn it on, after many attempts it magically turned on. Worked for the whole day, I still tried to flash the phone to get rid of my other Wi-Fi error log problem (and to prevent other possible problems by doing a fresh new start), didn’t seem to work. Charged it to 100%.
X+3 (today): Phone was already powered off when I woke up. Still can’t turn it on.
What I also tried continually:
- Tried charging with different power adapters or directly from USB. Still 0%.
- Tried wiping cache, wiping/factory reset.
- Flashing it to official 4.0.4. and 4.2.2., seemed not to work because it was over after some seconds, but the SDROOT/dload folder is ~1GB (although it said it worked, see spoiler).
Spoiler
When in recovery and choosing “apply update from external storage”, and then “dload” it says it failed to mount /sdcard (E:; “no such file or directory”).
Then error to open /sdcard/dload (“no such file or directory”)
Then
“Install from SD card complete.
cust copying files.
copy cust files succeeded.”
But as I said, that's possibly not true that 1GB gets copied in some seconds.
Status now (as I remember from Day X+2 when it worked):
- 4.2.2
- EmUI 1.6
- Android system recovery <3e>
- USB-debugging should be turned on (not sure) and phone should be rooted (Superuser was still installed after wiping, but it said it needed an update, so it might not fully work).
- Kernel and other software stuff: Can’t remember, can’t turn on the phone. And don’t know what they all mean tbh, I’m glad I know a little about the differences of Android official and custom ROMs and what a recovery is (and that I may need the Chinese recovery for flashing I cannot find online).
Further Details:
I personally don’t think the fall caused my problems because it continued to work for the whole day and the drop was cushioned. What I suspected: It could be an extreme case of the battery charge status problem. The phone thinks the battery is still 0% although it’s not. So it shuts itself off. Or the bootloop is caused by faulty software/ROM, although I didn’t change anything before the problems appeared.
I’ve read through several manuals and now get some sense of the topic, but I still don’t know everything relevant. Also, most of the links to important files are dead.
In addition, a problem I have is that despite reading through lots of threads, they require me to have a working phone, but mine is stuck in a bootloop.
What I want:
A clear, new phone software. Doesn’t matter which Android version or if official or custom ROM. Just want a working phone without the Wi-Fi error, so a fresh new start, a clean flash.
So: How do I do it, and importantly, where can I find the needed files?
(Even though I might buy a new phone next month, I want this one to be fixed so I can gift or sell the phone.)
Software I already have:
HiSuite, HuaWei_USB_Driver.exe, Android SDK, dload-B115 (folder, should be official Android 4.0.4), dload-B703 (folder, should be official Android 4.2.2), cm-10.1-20131006-EternityProject-hwu9508.zip (CyanogenMod 10.1 from Eternity Project); already rescued my data, so I’m ready to wipe.
Software that might be missing:
Chinese recovery, fastboot mod (what for?), CWM (what’s this, what for?), TWRP (what for?).
Many thanks in advance!
EDIT:
As recovery mode (Power + VolumeUp) works and the phone can be on for hours when in this mode (as long as it's plugged in), I assume that it's not the battery but a soft/firmware problem.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried this thread
https://forum.xda-developers.com/showthread.php?t=2039998
it should have all the files you need
Good Luck
Sawdoctor
Related
First, Lonnnng time reader/modder/hacker/technut, first time poster.
Secondly, my questions are: 1) Anyone else had such a positive experience as I did? And 2) Anyone else reproduce or trigger this ‘update’ in ICS?
Story below:
So I just purchased TF101 used, brought it home, and found out the long and hard way about the SOD/RR/DOCK/BATTERY/KERNEL issues that are plaguing a lot of users. So I researched for the past week (I'm a new owner), tried JB, ICS, etc, rom after rom. Still had same issues, and new ones (no wifi, sound, docking support gone, etc).
So, I went BACK to honeycomb 3.01 by flashing official update (WW version as I am in Canada) zip via CWM. I wiped cache, dalvik, data via CWM. Installed the zip. Tablet booted up perfectly. I did not sign into the google store. Turned tablet off completely WITHOUT being docked. Cold booted. Shut down. Used it for about 1.5 hrs, no reboots and could not repeat SOD/RR. However, HC is very slow compared to ICS. I then looked for the 3.2.1 update as it apparently makes the dock work correctly, and could never find it ANYWHERE (one rapidshare link and it was dead), all links were dead as the JP vers is the only one on Asus official site. 'check for updates' within the tablet did not work.
Next, I downloaded official xx.27 ICS off Asus website (around 253mB). Same procedure. wiped all cache/data/etc, flashed in CWM still (never put stock recovery as many recommended, didn't see the point). Booted tablet. Signed onto wifi, skipped signing in google account. Once in, turned off and cold booted back on. Used it for maybe 10 secs, and Asus updater pops up in task bar. The update had the same file-name of the update I just flashed however it had a July 27 date on it, and it was 302 mB (noticably larger than the 250~mB) update. NEVER saw this dialog before, even with my many attempts previously and all the different flashes/roms. Updater rebooted, installed itself (maybe 2 mins). I shut down completely once back in. Also, I still have not signed into my google account.
Following ICS update and shutdown, I then plugged my dock into wall outlet. I then finally docked (while off and for first time during entire process) the tablet, which then booted up. It immediately recognized the tablet, and made that ping sound confirming it was connected. Tablet booted up. I shut down, cold booted one last time. I then put it away on my shelf, lid closed. I opened this morning and 0 SOD or battery drain, which happened with EVERY SINGLE kernel/rom I tried for the past week. It would either SOD or RR. I left it open on 'about tablet' with uptime counter. It is still going. I checked various emails this morning, and ran some videos, etc, etc. Trying to reproduce RR/SOD. Usually it would occur within 10-15 mins of actually using it unit/being on wifi/etc/sleeping and waking.
I have a feeling that somehow Google is sending code (since you authorize OTA updates when you sign in) via being signed in that is somehow RR/SOD'ing (my theory), or there is some mysterious update I somehow triggered through this process. If anyone has reproduced this please let me know. But for now, this seems to fix battery drain at the very least, however I am running stock CPU clocks.
As i and many other are familiar with the RR/SOD troubles i have to say since i've updated with stock rooted .27 i haven't got the trouble anymore
Just checked and my transformer is still 86 % of battery capacity with an standby time of 1 day 18 hours
Before this update it almost always RR after using it when it was in standby mode again !
Ever since this update procedure my RR/SOD problems went down to near 0. I had one reboot in 3 long days of using my device, and that was from the stock browser. Which crashed before as well, anyways. I think this is a definite fix, which DOES NOT rely on external apps.
Not sure exactley how I triggered the update process. Please someone reproduce this 300~mB update that I triggered using CWM the entire update process!
Also, I have since extesively installed Google Play apps, and non-market sources. Not one crash, SOD, or RR. Dock work, charges excellent. Been using the unit for 2-3 days off and on with cbr viewer, movies n music playing, tonsof web browsing, etc. NO RR! NO SOD!
I have a LG G2x, got it when it first came out, dont want to buy a new phone really, but this thing is a plague.
the issues didnt matter before because i strictly used it for a very occasional phone call or txt and that was it, but now I'm using it more, and all its problems are too much to deal with. below is a list of issues with details I believe are relevant, if anyone has any suggestion for any of them please share.
Currently running:
Android version 2.3.3
kernal 2.6.32.9
build GR140
software version LG-P999-V21e
Issues:
1. Computer doesnt recognize phone (Can't go into USB Mass storage mode):
-when I plug the phone in, it charges, but no USB signal in the notification bar
-no "enable mass storage mode?",
-turned on/off mass storage mode in settings
-turned on/off usb debugging in settings
-used various (20+) usb cables, no change
-used various (10+) computers, no change
-used various USB ports on each computer, no change
-Installed various versions of LG Drivers and LGs update tool (every version I could find) into my PC
The phone originally went into mass storage mode fine and without trouble. within a few weeks of owning the phone I was given notification of an update and downloaded it, all was fine (I assume this was 2.3.3 from 2.3.2, not sure, wasn't familiar with android back then and didn't know these things). A couple months later I got another notification of a new update and downloaded it. When it was done I couldn't notice any changes, and I believe (its been years) the version stayed the same (2.3.3, LG-P999-V21e) After reading the last few days, it looks like my phone should have been able to upgrade to V21y and I had LG support verify this, but it never did (partially failed update?), using the check for update in my phone yields a never ending "checking server for update", and I'm unable to use the LG update tool because my PC cant recognize my phone.
This stops me from easilly accessing my phones files to share between my pc, plus I cant root or install any other android versions, nor can I even get the latest update for the stock version.
2. Random freezes
From what I can tell the phone stays on but the screen goes out (might be wrong, but I'm sure I heard a phonecall come in once when It did this), the only fix is to pull the battery and put it back in. Supposidly this was fixed in the 2.4.4 update, but I cant get it...so... yea.
3. SMS Messages (sometimes) come in multiple times.
This only recently started in the last 6-8 months, and is occuring with multiple people over multiple networks. Sometimes txting will be completely normal, but other times (random from what I can tell) I'll get the same text 2, 3, 4, 18 times over the course of an hour. It drives me nuts when someone says "sup" to me over and over again for an hour strait. cleared all my messages, cleared cache etc, factory reset, even got a new sim and called tmobile, nothing fixes it.
4. GPS SUCKS:
-cleared data/cache and uninstalled google maps updates
-reset various settings
-gone into hidden menu and altered various settings for the GPS (and set them back to the default ones)
-used various gps testing apps
-added Google to the SLP server list
-tried all combinations of data/wifi/roaming being enabled/disabled
Basically, I recently got data on my phone (never needed it) and tried to use GPS when going somewhere I'd never been to before. The first try googles nav sat there saying "searching for GPS..." and never found me, which I thought was weird because when I open the app it would put me exactly where I'm at, it just would instantly lose me for good. After a few days I realized SOMETIMES it would pick me back up, so I could travel with GPS, it would tell me where to go, lose me, I drive blind for 5-10 minutes, then it'd pick me up again long enough to give me the next turn, or tell me how to get back if I traveled off course.
Unacceptable.
So thats when I started reading and tinkering with settings. I've been able to make it so it -always- finds me within 10 seconds, unless I'm moving. If I'm in a car it will constantly lose me and re-find me (most of the time it can find me within 20-30 seconds, but sometimes it still completely loses me). It's better, but not right, and still only barely useable as a GPS guide for driving. The only fix I've seen that I havent tried yet is editing gps.conf, because I need root access to do so, and I cant do that because of issue #1 and can't find a "one click app/website" that works for my phone and software.
5. Performance in general kind of sucks
-factory reset
My phone was running very, very poorly, but that turned out to be due to 2 years of use, I did a factory reset on it and it sped up significantly, but it still manages to hang really bad in weird ways, maybe I just dont understand how android handles its memory. I can use an app perfectly fine, but if I continue to use it (say for 30+ minutes) my phone will begin to freak out. lock up, not respond, screen shut off, sometimes it even does a "soft restart" as i call it, the screen turns black but not off, then 5-10 minutes later it comes back on and acts like it was shut off completely. Not sure if theres a known performance issue with this phone or if this is just hardware limitation, figured I'd mention it.
==================================
The two issues I really want/need fixed is GPS stability, and mass storage mode. I can even do without mass storage mode, but I really, really want the GPS to work if nothing else.
Thank you in advance for anyone who can help, if I can get this thing to work right I think I'll have a lot of fun tinkering with the android OS.
This is a very strange issue, I'll describe it here. I bought recently a OnePlus One in Spain. I've followed these steps:
1. Install CWM from High on Android guide
2. Install Android 5.1.1 from Gizbot guide (which comes from this XDA guide).
I finished the steps and got Android working perfectly. I love how smooth it is and all. However, I was ready to leave so I unplugged the USB (official cable). The phone freezes for few seconds and then it reboots. Now, I have tried many things and been in the same point many times, so there are two behaviours that can occur:
- When starting from the beginning with the cable unplugged, the Dirty Unicorn spinning wheel just freezes and reboot. It keeps doing so constantly. Reboot hell.
- When starting with the USB connected, but after a reset from disconnecting it, it goes into "Android is starting... Optimizing app 8 of X". There are two odd things here: the X is a different number each time it reboots, like 55 or 90, and then it freezes apparently at Google Apps and reboots again. Same reboot hell, but longer.
Now, I can turn it off, enter into recovery mode and reinstall everything. This is what allowed me to test exactly when it breaks. In any case it will only even start the Android 5.1.1 if the USB is connected.
My question is, any idea why this is happening? Any recommended step once inside Android to try to avoid this?Otherwise I'll try with another ROM, but I think that it's super odd and it looks like it might be fixed easily by someone who understands the system better than me...
Few extra details:
- Battery is 100%, so no apparent problem there.
- I'm using Ubuntu 15.04 on the computer side.
- I don't have a SIM card yet.
PS, if trying other ROM/gapps, which one do you recommend?
fpresencia said:
This is a very strange issue, I'll describe it here. I bought recently a OnePlus One in Spain. I've followed these steps:
1. Install CWM from High on Android guide
2. Install Android 5.1.1 from Gizbot guide (which comes from this XDA guide).
I finished the steps and got Android working perfectly. I love how smooth it is and all. However, I was ready to leave so I unplugged the USB (official cable). The phone freezes for few seconds and then it reboots. Now, I have tried many things and been in the same point many times, so there are two behaviours that can occur:
- When starting from the beginning with the cable unplugged, the Dirty Unicorn spinning wheel just freezes and reboot. It keeps doing so constantly. Reboot hell.
- When starting with the USB connected, but after a reset from disconnecting it, it goes into "Android is starting... Optimizing app 8 of X". There are two odd things here: the X is a different number each time it reboots, like 55 or 90, and then it freezes apparently at Google Apps and reboots again. Same reboot hell, but longer.
Now, I can turn it off, enter into recovery mode and reinstall everything. This is what allowed me to test exactly when it breaks. In any case it will only even start the Android 5.1.1 if the USB is connected.
My question is, any idea why this is happening? Any recommended step once inside Android to try to avoid this?Otherwise I'll try with another ROM, but I think that it's super odd and it looks like it might be fixed easily by someone who understands the system better than me...
Few extra details:
- Battery is 100%, so no apparent problem there.
- I'm using Ubuntu 15.04 on the computer side.
- I don't have a SIM card yet.
PS, if trying other ROM/gapps, which one do you recommend?
Click to expand...
Click to collapse
Same issue here, did you ever figure it out?
Had the same issue today but with another rom. Fixed it by first installing CM12 latest release and booting, then flashing custom rom + Gapps + Kernel.
Maybe this helps for you as well!
Hi guys
any solution to this issue?? It happens to me as well, now with latest Oxygen ROM (from yesterday).
When it is unplugged it will reboot. not if plugged in.
Help!!
Can you give us specific details as to what ROM, Kernel, and Gapps versions you used? This problem is a seemingly unfixable one at the moment.
Greetings xda-developers,
I own a galaxy tab 2 P3100 16GB model since march 2013 (pretty old yeah, but i like it, its my first tab ) It is running everything stock (recovery plus OS, JB 4.1.2).
It was working all good and serving good for my browsing, whatsapp, mails, youtube, hotstar etc etc. (heavy user of tab) Suddenly on one fine Sunday morning it restarted by itself. I thought this to be normal but it wasn't. After every 10 to 20 seconds I could hear the starting tone. When i looked to the tab, it was pretty warm on the left side where it usually does when used heavily, but it was acting strange.
The tab was restarting by itself! The home screen appears, i could start an app and suddenly it restarts and this continues every 20 seconds until the battery goes low.
I thought two new installed apps would e problem so i removed them and to my surprise(!), they were back again after next 'auto restart'. The 'auto restart' stuff happened back in January this year (after my nephew installed many games on it) but was solved when I did factory reset from settings menu.
But this time nothing successful. Neither factory reset from settings menu nor from recovery. I have tried using twrp and CM11 last year but returned to stock after few months.
I tried flashing twrp, cwm recoveries but after every boot it returns to stock. Even flashing OS didn't helped.
My problem is similar to these:
https://forum.xda-developers.com/showthread.php?t=2641158
and
https://forum.xda-developers.com/showthread.php?t=2627490
and
https://forum.xda-developers.com/galaxy-tab-2/help/unable-to-install-twrp-t3696545
Also the stock recovery screen shows the following at bottom:
# Manual Mode #
-- Appling Multi-CSC...
did not match sized '/system/csc/common/system/csc/default_workspace.xml'(No data available)
(I wanted to attach image to this post but could not find an option.)
From all my readings on this forum, I can conclude (?) that its an emmc issue (end of life?).
Need your help guys.
The tab is in excellent condition except this issue. Can this be solved?
I am from electronics and embedded system (microcontrollers) profession and hobbyist. I know replacing emmc or motherboard (or scrapping the tab, NO! i don't want to though i now own the Lenovo tab 4 8 plus 3GB RAM+16GB version ) is an obvious solution.
A (may be obvious) possibility came in my mind if external memory card could be used for booting and I (and many others) could bring their tab to use (instead of making it a paperweight )
I though this to be possible solution: https://forum.xda-developers.com/galaxy-tab-2/general/discussion-alternative-tab-2-emmc-bug-t3306862
but i am not able to understand the instructions and the links posted by OP are not functional.
Can this be a solution:
https://forum.xda-developers.com/showthread.php?t=1866675
OR
I am thinking of this:
I got schematics and service manual for p3100 from internet. I looked the datasheet for OMAP4430. I am thinking whether the boot sequence can be changed (or may be no need to change the sequence) and we can boot from external micro SD card
or something like
https://forum.xda-developers.com/showthread.php?t=1312391
or can https://forum.xda-developers.com/showthread.php?t=2109044 be used?
But whenever i plugged my tab in windows without battery or with battery, initially i could see new device found 'OMAP....' something but immediately after 2 or so seconds it shows device unplugged.
Any comments guys?
Thanks for reading patiently the long write up...
You can't boot from external SD because you aren't able to flash a high modified boot.img if your emmc got read only.
You'll need to replace the emmc or find someone who can flash an updated emmc firmware via isp (but the issue might come back in short time after firmware update).
Thanks for reply.
Well i have to search someone from my nearby city for such service.
Is it not possible booting from external even if the boot sequence is changed, i mean if hardware is modded to change boot sequence?
Humm but it will require the primary and secondary bootloaders then...
The pandaboard has increased by curiosity of such possibility. I think i need to study more...
Dear all,
from the occasional reboot my Zenfone performed every now in a while (which didn't bother me too much) it now reboots so fast that it usually has not yet booted to the point where I could get data off the device before it reboots again.
As always, the backup is too old and I want to extract some data off the device. Most important are a few KBs worth of text notes. Here come some questions:
- It seems to be a hardware fault. Are there educated guesses what may give me a few last moments with the device to extract data? Heat? Freezing?
- Are there professional data recovery companies dealing with smartphones such that they can extract data from the chips without the phone working?
- As it is a Qualcomm device: Would any access via QDLoader work or would it be as unstable as the rest of the phone?
I appreciate any input. And yes, I know that I didn't backup often enough.
Thanks,
weaker
which rom are you on?
Sorry for the late reply.
I'm on stock ROM with Magisk. In the end when it became worse, I let Magisk restore the images but this definitely seems to be hardware-related. I also did no overclocking and I don't use games on the phone so I think that it is also not a thermal issue.
To keep the interested ones updated how it evolved: The situation is now as follows:
I tried to boot into recovery via fastbooting the TWRP (the one I used many times successfully for my phone) after one of the phone bootings was stable for enough seconds so have ADB contact and go to fastboot mode. I hoped to be able to interact more stabily in the recovery. However, the result was that the phone rebooted (I am unsure if the TWRP transfer was finished before that) and then the charging screen appeared and the charging screen remained constantly on, even when pulling the cable. It didn't react to any keypresses in that state.
I let it drain the battery (which was only a few hours as the screen was always on). Then, I plugged the phone in and it booted normally and was stable for 15 minutes or so, which gave me enough time to save the most important data. Phew.
This session however seemed to be the last farewell. The phone started to bootloop and I switched it off*. Now the phone has always a black off screen and doesn't respond to anything: Pressing (and holding) the power button, also in combination with Vol+ or Vol-. Also plugging a cable to charge doesn't create any reaction.
* switching it off worked the following way: The unlocked bootloader shows that one could press the power button to pause the boot. I can't think of why this might be a useful function in a normal situation. However, in my situation I could pause the boot and after some time it would switch off. That way I could at least break the bootloop.
you will have to boot into qloader to be able to recover your phone...
follow step by step exactly what is mentioned in the below link, ypu should be able to recover your phone :
Here’s how to unbrick Asus ZenFone 6 (Asus 6z) from QDLOADER 9008 mode - PiunikaWeb
Is your Asus ZenFone 6 (Asus 6z) hard-bricked? You can use still flash via QDLOADER 9008 mode to give a new life to your dead handset.
piunikaweb.com
Sorry to be the prick here, but next time post this in Q&A section. This one is for posting development (Kernels and ROMs)
OK, no offense taken. I thought that I would need to resort to some TWRP magic to get data off my device.
@MOD: Feel free to move thread where it fits best.
For the sake of completeness:
The phone is back from RMA. According to the sparse documentation they exchanged the mainboard and battery and some connector. Some firmwares are now newer than on the old mainboard (little surprise here). Bootloader unlock worked also on the new phone (some report that this would not work by default after an RMA, for me it did).
So, ASUS did a great job dealing with the issue.