I belive my 1+ 6 somehow got bricked. I didn't root it, I didn't unlock the boatloader, I didn't put any custom ROMs, everything was stock. I went to bed like usual, and left the phone charging. Around 1 hour later, I woke up, the screen was on
Your device is corrupt. It can't be trusted and may not work properly. Visit this link on another device: g.co/ABH
PRESS POWER KEY TO CONTINUE.
I was half asleep, I restarted the phone, everything was back to normal and I thought that was the end of it. Woke up late in the morning, confused, because my alarm didn't ring. My phone was dead, wasn't turning on, it wasn't doing anything. It was charged when I restarted it last night (75%). I tried every single combination of buttons, I couldn't get it to boot into Fast Boot, nothing was working.
In the morning, I tried using the Msm tool, but it always got stuck at 'Memory size: 119.19G' after 13 seconds.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I gave up, and tried to turn on the phone a few hours later. It turned on, and I got that message again, that your device is corrupt. Pressed the power key, and it started just fine. It restarted afterwards, and was booting to fast boot menu. No matter what I tried, it was always going to the fast boot menu.
I tried the Msm tool, and this time I got past that stage. But, this time around, it got stuck at downloading system.img to system_a (I left it there for 40 minutes), until I closed everything and tried to restart the procedure.
Now I'm back to square 1, phone won't turn on, won't vibrate and will be stuck at Memory size stage.
Please help me out, I'm really desperate...
try other rom in msmdownloadtool, i give you a link to OxygenOS 9.0.2 MSMDownloadTool v.4.058:
https://mega.nz/#!NEEEgCCJ!Wuo2tw3ehnnKhcGQEc5fMXPNZdqJO_IT5suVrCHD1UY
drivers:
https://androidfilehost.com/?fid=24052804347798730
This is what I am getting now
Do you have another usb to type-c cable for try?
Tried 3 more cables, and 2 other USB ports, same results. Will have to try it tomorrow, again, on a different machine, but I am doubtful it's going to make any difference.
Any other ideas? Thank you!
try disabling the sha256 check, perhaps you can flash it with errors but your phone boot, seems an internal damage, i never had issues with msmdownloadtool
try a different version of the program and see if a reboot works. This program saved my phone also 2 weeks ago and i thought i was hard bricked also because my phone showed there was no recovery/fastboot and bootloader and at first the program didn't work like it should and after a reboot of the pc and then starting the app and then do the correct button combination so that the led light on the phone will turn yellow i believe and then start the process.
This sounds like a hardware failure, send the phone to oneplus.
Try to contact OnePlus service, I had a very similar problem to my 5T and they solved it via remote desktop.
Press volume up for 5 seconds then plug the device into your laptop. It should be detected as COM3 and the MSM download tool should detect the device.
dragos281993 said:
Press volume up for 5 seconds then plug the device into your laptop. It should be detected as COM3 and the MSM download tool should detect the device.
Click to expand...
Click to collapse
The device, as mentioned in the initial post, is detected by the MSM tool, however, after I press start, I get hit with an error every time
I have contacted OnePlus, and they said that they no longer do remote fixes, as they used to.
For my past experience, You have to log in EDL mode instead fastboot for flashing through msntool.
DurDom said:
The device, as mentioned in the initial post, is detected by the MSM tool, however, after I press start, I get hit with an error every time
I have contacted OnePlus, and they said that they no longer do remote fixes, as they used to.
Click to expand...
Click to collapse
Sir, did you solve the problem?
Sounds like an actual hardware issue if this happened on a stock device out of the blue. Contact OnePlus and hopefully they can make it right.
SOCOM-HERO said:
Sounds like an actual hardware issue if this happened on a stock device out of the blue. Contact OnePlus and hopefully they can make it right.
Click to expand...
Click to collapse
It was a stock device. Apparently the memory went bad out of nowhere, and the motherboard had to be replaced.
Did they replace MoBo for free? I have the same issue
Did you manage to get your phone working again? My onePlus 6 died on me last week too.
It was updated to 11.1.1 a few weeks ago.
Last week while idly scrolling social media, the phone froze, turned off, and when it turned back on, it displayed Qualcomm crashdump mode.
I've been running the MsmDownloadTool, and for the past 55 minutes it's been stuck in "Downloading system.img to system_a".
Not sure how to proceed from here.
Related
Okay so i updated to Energy's build 21885 for the HTC Touch Pro and everything works fine like usual, and i began to start installing my apps etc.
It all went fine until i started installing some new apps (which might be the reason why it bricked my phone), i think one of the new app i installed was nueUSBKeyboard which is for the CDMA (i didn't read it properly at the start), and my Touch Pro is a GSM, so maybe that's the reason that bricked my fone.
I still don't know what bricked it, but right now when i turn on the fone, it shows the boot information at the very start of the startup, i.e it shows:
R 1. 14. 25. 35 (which is the radio i believe)
G 52. 64c. 25 35
D 5nergy ROM
and it just gets stuck there FOREVER.
I took out my battery and memory card and nothing changes, how do i solve this?? Please help.
Okay after doing some Google & XDA searches, i found a solution which i'm trying out right now. Since my phone could get to the screen with the boot information, and that i can get into the bootloader fine, it seems i can still connect my phone and update the rom.
To get to the bootloader, you press and hold the volume down button, and then you turn on the phone while pressing it. You should get a screen showing you some information and the screen looks red, blue & green.
Then, just plugin your USB and even though it doesn't say it's syncing with your PC (because you need to in order to update the ROM), but just go ahead and update the ROM anyway, it will connect and work.
Right now it's installing and I pray to god this will fix my problem, i will post back and update this, but hopefully anyone who had this problem can give me some other advice in case this doesn't work and hopefully anyone that might have this problem can try this out for themselves. This is the first time i've had a bricked phone.
Just wondering, what are the possible ways that you can brick your phone?? I didn't update the radio or anything, and updating roms is easy and plain as hell, i do that all the time so it can't be it since nothing went wrong, like EVER, and i restarted my fone several times after updating the rom, so it must be one of the new apps i installed for my fone but those are just .cab files that are safe because i got them from XDA itself, and those are very recent released apps too and are for WM 6.5 so i dunno what might have caused it other than nueUSBKeyboard......
EDIT:
Holy crap, it worked! Damn i almost pissed in my pants, god i can't live without a fone. But i would like anyone to give me some advice on what could've bricked my fone in case this happens again, coz i really dunno wot bricked it....
A hard reset would've done the trick.
Farmer Ted said:
A hard reset would've done the trick.
Click to expand...
Click to collapse
truf
10char
Did you guys read properly? I said my fone got bricked because it gets stuck at the booting screen.
That's the screen that shows a black background and the word "Touch Pro" in the middle, and it shows your radio & rom information at the bottom right and they're in red colour.
I.E, I'm STUCK at that screen, i can't boot into the rom at all, so how can i even use hard reset? I can't even connect my fone to PC to access the memory card, nor can i use ActiveSync or Windows Mobile Device Centre to sync with my device so that i can upgrade the rom, which is why i found the solution is to boot into your bootloader screen and then connect the USB, that's the only way it seems.
Edit:
Here, i took a picture showing you guys what i mean, sorry for the quality but you guys get the point, it gets stuck at that screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it fixed or not? Anyway, performing a hard reset and going into bootloader are pretty much the same thing (hold vol down + OK and soft reset). You can probably hard reset from the bootloader screen, although I've never done it myself.
do a hard reset may resolve this problem by pressing and hold volume down + center button then using stylus to press reset button, when hard reset screen is shown, press vol up button to accept hard reset, do again when done
ya guys, it's solved. I stated that in my 2nd post.....
anyway i didn't know u can hard reset from bootloader screen, now i can try that next time when this happens.
Hard Reset FTW
Hi all,
Just wanted to share that today, after a year of pleasant use on my Fuze, it 'bricked' after I disabled the performance upgrade options in TF3Dconfig and rebooted.
A quick search for "brick" in the Raphael forum led me to do a hard reset. All my texts and customizations are wiped out, but my phone is back up and running. Definitely glad I didn't just accept it as bricked, as I'm not due for an upgrade for 6ish months, and AT&T hasn't got anything for Android phones released yet, so I'd be back on my Wizard (with an english rom flashed onto a T-Mobile Germany-branded device, so funky keyboard action here).
+1 for the hard reset!
i have a g2x and ive been having random issues
first was the battery life thing ive see a lot about and also i had no calendar installed from the factory
tmo replaced it and i have still been having bad battery issues after reading the other thread about g2x battery issues i was encouraged to open a seprate thread
i tried a factory reset and created more problems than i had before i started
what i have now is a phone that has no android market and the buttons on the bottom are unresponsive , they have haptic feedback but make no changes unless im on the home screen
i tried the nvflash recovery
and i have tried the factory reset a few times pulled the battery numerous times
i dont know the terminology to well so please be easy....
what can i do i have a pretty dumb smartphone lol or is it that my smartphone has a pretty dumb user ?
rexxxlo said:
i have a g2x and ive been having random issues
first was the battery life thing ive see a lot about and also i had no calendar installed from the factory
tmo replaced it and i have still been having bad battery issues after reading the other thread about g2x battery issues i was encouraged to open a seprate thread
i tried a factory reset and created more problems than i had before i started
what i have now is a phone that has no android market and the buttons on the bottom are unresponsive , they have haptic feedback but make no changes unless im on the home screen
i tried the nvflash recovery
and i have tried the factory reset a few times pulled the battery numerous times
i dont know the terminology to well so please be easy....
what can i do i have a pretty dumb smartphone lol or is it that my smartphone has a pretty dumb user ?
Click to expand...
Click to collapse
Follow the directions in the OneClick NvFlash CWM Recovery thread.. (the initial post). You should be good to go. It's in the development section.
i followed this thread :
http://forum.xda-developers.com/showthread.php?t=1054492
specifically the part that says
How to revert back to stock recovery:
and i used the img5 file
like i said im new to this ive had a blackberry before this is all new to me
so was i right in the other thread and you have a factory fresh unrooted phone? thats an important detail
well i un-roothed it at one point ....
i believe i tried the factory reset when it was rooted, did i brick my phone?
this is what i did so far its at the SW upgrade with the yellow arrows part
what should i do now?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
well ive made it a bit further
followed the above instructions
pulled the usb cord and popped the battery while holding up and power until i see android in orange
then im in the recovery i choose to reset all to factory and choose yes
reboot the phone and back to where i started grrrr
im sure im missing something simple
rexxxlo said:
well ive made it a bit further
followed the above instructions
pulled the usb cord and popped the battery while holding up and power until i see android in orange
Click to expand...
Click to collapse
after you put the battery in, you should have just rebooted/powered up the phone. who told you to hold up and power? img5 was sent successfully. you have stock recovery. vol.down and power will now do a factory rest. what color is the text that say's reset all to factory? i think you're still in clockwork recovery even though it said img5 sent successfully. that would be odd though. unless your vol.up and power messed something up.
and....have you even flashed a custom recovery? why are you going back to stock recovery if not?
i guess ive been trying everything i find hoping that something works
ive got it to go back to stock and it seems as if the market is just not showing up
oh and you got a pm good sir....
fixed thanks to crazythunder !
way to go now whats next?
well ive beEn having fun with my phone
it doesn't die nearly as fast as before.... the gps works from time to time and it only restarts on its own 5-10 times a day unlike every 15 min when i first got it
now i get a really aggravating problem if i get a text message it re appears sometimes 20+ TIMES
what causes this ?
Its like it never stops with this dam phone!
for the last few days when I open the email program it takes a second to load then they are deleted a split second after they open. Gggggrrrrrrr
And it.comtinues today I get woken up with an alarm and a frozen phone. I had to pull the case apart and pull the battery out to stop the alarm
Trying to use taptalk to reply it wont work this will be the fourth time I've typed this reply
I previously had an issue with this which was solved by re-flashing, unfortunately this isn't helping this time.
So as far as I can tell things work properly with the following exception.
When I power off the phone and leave it in to charge I get stuck on the black and white lighting battery screen. The screen stays on indefinitely. The phone will not power on except for a soft reset which then boots the phone.
For clarity this is what the phone looks like ... it just never turns the screen off.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks.
- JasonVaritekMVP
Only other detail I have to add is that the charge screen works correctly after a flash-all. It is the process of installing twrp and then Magisk that seems to be borking the charge screen.
JasonVaritekMVP said:
I previously had an issue with this which was solved by re-flashing, unfortunately this isn't helping this time.
So as far as I can tell things work properly with the following exception.
When I power off the phone and leave it in to charge I get stuck on the black and white lighting battery screen. The screen stays on indefinitely. The phone will not power on except for a soft reset which then boots the phone.
For clarity this is what the phone looks like ... it just never turns the screen off.
Thanks.
- JasonVaritekMVP
Click to expand...
Click to collapse
Did you ever find a fix for this? My Pixel 2 XL does it as well!
MRL3GS said:
Did you ever find a fix for this? My Pixel 2 XL does it as well!
Click to expand...
Click to collapse
So this issue popped up for me when Magisk v17.0 came out and v17.1 didn't seem to fix it. Re-flashing did solve the problem but every time I tried to re-root the issue came back. Something about the latest Magisk and my flashing was causing the problem. I tried going back to earlier working versions of Magisk such as 16 and 16.5 but none of them seemed to work, whatever it was it stuck.
I finally ended up flashing the latest Pie along with the latest Magisk and that together allowed me to flash, root and solve the problem. I have not attempted to go back to Oreo.
Hope this helps.
- JasonVaritekMVP
this just happened to me. how do i fix this? I just want the thing to power up. I just got done using it. picked up phone and it was powered off.....
edit: phew. i panicked when i saw this. I just held the power button and it shut off. turned it back on and it booted up....had 2% battery. i guess it was just a low battery this time.
have the same issue too. Only happens when the phone dies after running out of juice. Hard reset reboot and boots up right back up afterwards. Also rooted with magisk 17.1
hard reset? like you lose everything? that sucks. im on 17.3 magisk.
psycho_maniac said:
hard reset? like you lose everything? that sucks. im on 17.3 magisk.
Click to expand...
Click to collapse
whoops, i meant hard reboot. Pressed and held the power button for 5+ seconds and it booted right back up.
eneka said:
whoops, i meant hard reboot. Pressed and held the power button for 5+ seconds and it booted right back up.
Click to expand...
Click to collapse
yup. thats what i did too. mine was due to low battery
Anyone figure this problem out? I've had this problem for a while now. It was doing this a few months ago then I reflashed magisk and it went away. I did a monthly update a month later and it came back and I've tried a factory reset...reflashing etc.. Nothing helps. It only happens if the phone dies or you power it off. I'm not using TWRP... It's a magisk manager direct install. Thanks!
fastracer said:
Anyone figure this problem out? I've had this problem for a while now. It was doing this a few months ago then I reflashed magisk and it went away. I did a monthly update a month later and it came back and I've tried a factory reset...reflashing etc.. Nothing helps. It only happens if the phone dies or you power it off. I'm not using TWRP... It's a magisk manager direct install. Thanks!
Click to expand...
Click to collapse
I've also had this issue since I bought the phone 2nd hand last June. I don't recall if it happen before rooting or not. The only pattern(?) I have noticed is that when I let the phone die completely, theres a chance when I plug it into the charger, it might get stuck on the screen as OP showed. However, as others noted, I think holding down the power button shuts the phone completely down again. Occasionally either I'm doing something wrong or the phone doesn't register the button presses all the time. In past I also tried holding the power button and volume down at the same time but I'm assuming the phone picked it up as me just holding the power button down or maybe that combo also works.
Hello everyone,
I bought this phone on sale last year and it was advertised as follows...
Refurbished: LG G Flex2 H950 32GB Unlocked GSM 4G LTE Octa-Core Android Phone
In browsing the forums here I see the excitement around this phone has waned quite a bit since it's release, but I'm hoping there's still a few of you left who might be able to help me. I totally love this phone and want to be able to use its full potential.
It's branded as an AT&T phone when the boot-up screen appears. I doubt it was sold as unlocked by AT&T, but rather Newegg, or someone they're reselling for, unlocked it. I've never been an AT&T customer. I bought it knowing I could use any carrier willing to sell me a sim card. I'm currently using Mint.
It came with the 5.01 firmware. I've spent many days reading every thread I can about how to upgrade it, and possibly get Marshmellow as well. The issue is that I can't seem to find any drivers that function properly. Here are all the ones I've tried...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The only one that's come close to fully functional is the top one for version 3.11.3.0 It's the only one that recognizes all of the sub-devices no matter how many times I unplug the USB cable and plug it back in. The only other one that came close was version 4.2.0
I use a program called USBDeview, which provides live monitoring of USB connections and shows a great deal of info about each one. In the images I'm going to share, I've shrunk away all of the columns except the ones I think are most relevant. The ones with Green dots mean it sees them as a working, connected device. The ones with Gray dots mean that there is a record of this device connecting, but that it does not see them as currently connected. And the Purple dots mean it sees the device as connected, but that there is some issue with its functionality.
Here's the result when I use the 3.11.3.0 driver...
All 5 devices show green and everything action I've tried to perform from studying guides here works perfectly. And, as I said, it keeps working no matter how often I reconnect it. The only weird thing is that USBDeview reports the version as 3.11.0.0, even as the filename and the file properties report it as 3.11.3.0 It reports correctly for all the other drivers I've tried, but I guess it's nothing to complain about at this point.
The problem is that whenever I put the phone in “Firmware Update/Download Mode” I get this result...
The LGE Mobile Sooner Single ADB Interface driver now shows as disconnected, and as such, I can't send any ADB commands and my device doesn't show up on the list when I type "ADB Devices". It doesn't indicate there is a problem, it just shows it as not there. This issue is thwarting all my efforts to upgrade the phone.
With the 4.2.0.0 driver, I get a similar, but slightly different result. Sometimes I got this when connecting the phone in normal mode...
And other times I got this...
I can't account for the different results because I was trying all kinds of tweaks and fixes between different attempts. But one thing was universal with this version: They would all show green for up to a minute or so and then all but one would start disconnecting until it looked something like this...
The other drivers I tried were similar. Some recognized more devices, some less, and some would look like the above on their first use. Some were consistent and some would look okay for a minute and then disconnect.
When it came to Download Mode, some would see the ADB driver and some would see the USB driver, but I still haven't found one that will see both. When I check the error logs, I most often see something like this...
So if anyone has a driver that they know works on this phone and has definitely used it to upgrade this model in Download mode, please let me know.
Also, if you know of a method to accomplish my goal without using Download mode, please point me to some steps to that method.
Just to avoid the obvious advice, I've tried a great many fixes...
Turned off Fast Startup.
Disabled ability to turn off device for power savings on all USB hubs.
Disabled USB Selective Suspend.
Disabled firewall and all other protection settings in Windows Defender.
Uninstalled my anti-virus.
Disabled Windows automatic device updates in Group Policy.
Made sure all my other devices have the latest drivers.
Update my BIOS to the latest version.
Windows 10 Pro is up to date.
As one person advised, tried to manually update the devices that wouldn't connect using lgx64bus.inf from the driver folder.
And various registry tweaks.
Thanks in advance for any help.
NOTE: In going through all the drivers again, I discovered that version 3.14.1, at least on the surface, is performing exactly as ver 3.11.3 has been. Works perfectly in normal mode, missing ADB device in Download mode. Guess I skipped it in my first few runs. Still doesn't solve my problem, but I strive to be accurate.
NOTE 2: I have found a method for flashing that does not require ABD to flash my phone. I can't find an option to delete this post, so the moderator has my permission to do so at their discretion.
I am stuck on this. Tried many of the suggestions on the forum still not getting anywhere.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mikeychsia said:
I am stuck on this. Tried many of the suggestions on the forum still not getting anywhere.
View attachment 5401871
Click to expand...
Click to collapse
Not sure if this helps, In some devices, ramdump mode means that the system can't deal with some determined process, for example an over exposure charging time. You should try to reboot it pressing the three buttons for about 12 seconds, and it should be fine.
SubwayChamp said:
Not sure if this helps, In some devices, ramdump mode means that the system can't deal with some determined process, for example an over exposure charging time. You should try to reboot it pressing the three buttons for about 12 seconds, and it should be fine.
Click to expand...
Click to collapse
Thanks for this tried this and no change still same message.
mikeychsia said:
Thanks for this tried this and no change still same message.
Click to expand...
Click to collapse
This used to happen many years ago, was kinda normal, but it's strange actually with such powered devices, you should find a combination key to power off device (time ago worked pressing the three buttons about 30 seconds) and then restart from there, device has to reboot normally, ramdump state creates a complete log/report that take some time and usually is nothing more than that, something like this https://www.askmefast.com/How_can_i_reset_my_phone_its_on_RAMDUMP_MODEarm9_mode-qna1311373.html if the over exposition didn't lead to a hardware issue with the EMMC itself then it has to be fixable.
SubwayChamp said:
This used to happen many years ago, was kinda normal, but it's strange actually with such powered devices, you should find a combination key to power off device (time ago worked pressing the three buttons about 30 seconds) and then restart from there, device has to reboot normally, ramdump state creates a complete log/report that take some time and usually is nothing more than that, something like this https://www.askmefast.com/How_can_i_reset_my_phone_its_on_RAMDUMP_MODEarm9_mode-qna1311373.html if the over exposition didn't lead to a hardware issue with the EMMC itself then it has to be fixable.
Click to expand...
Click to collapse
I tried all this too no change. I been trying all sorts of combinations for 4 days now each results in the same no change.
Phone won't boot to Android, stuck on ramdump
Hi there, My ZenFone 8 suddenly turned off randomly today, while playing music on YouTube. I held the power button for 15 or so seconds, and now the phone is stuck on what I assume to be a ramdump. It lists various boot stages, and has green...
forum.xda-developers.com
twistedumbrella said:
Phone won't boot to Android, stuck on ramdump
Hi there, My ZenFone 8 suddenly turned off randomly today, while playing music on YouTube. I held the power button for 15 or so seconds, and now the phone is stuck on what I assume to be a ramdump. It lists various boot stages, and has green...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried all this today again still no change same error
mikeychsia said:
I tried all this today again still no change same error
Click to expand...
Click to collapse
Still just want to say thanks for the response. It feels like its a hardware issue and so I will just have to send it back to HK for repair or replacement.
mikeychsia said:
Still just want to say thanks for the response. It feels like its a hardware issue and so I will just have to send it back to HK for repair or replacement.
Click to expand...
Click to collapse
Unfortunately I don't know the exact combination keys for your device but at least I could give you a clue, in the meantime if you want to keep trying a solution till to take it to a repair center, you should visit more threads regarding this specific searching; "How to get out of RAMdump mode Android"
SubwayChamp said:
Unfortunately I don't know the exact combination keys for your device but at least I could give you a clue, in the meantime if you want to keep trying a solution till to take it to a repair center, you should visit more threads regarding this specific searching; "How to get out of RAMdump mode Android"
Click to expand...
Click to collapse
Thanks for the advise I will give it a go
Today it popped up after installing the module in the manager magiskl restarting the phone in romdump But now it works normally
thieftime1980 said:
Today it popped up after installing the module in the manager magiskl restarting the phone in romdump But now it works normally
Click to expand...
Click to collapse
Good for you. I have had no such luck. I sent the phone back to the manufacturer who confirmed that the hardware was indeed faulty so they are going to replace the whole thing.
thieftime1980 said:
Today it popped up after installing the module in the manager magiskl restarting the phone in romdump But now it works normally
Click to expand...
Click to collapse
For the audience, How did you get it out of RAM dump mode? Which button keys did you press or something else?
SubwayChamp said:
For the audience, How did you get it out of RAM dump mode? Which button keys did you press or something else?
Click to expand...
Click to collapse
Hold all three physical buttons until it reboots
just hold the power button for about 20 seconds