Question RMX3363 - Phone does not boot - Realme GT Master Edition

Hello, my phone won't start since this morning. It's like I have no battery, nothing happens when I press the power button. I tried to access the recovery or the bootloader but nothing happens.
The last flash ROM was LineageOS 20.0 (RMX3360_11.F.03), I'm on this ROM since the beginning of March.
This morning I was listening to a visio presentation on chrome on the bigbluebutton platform while charging the phone with the superdart charger. Shortly after the call started, my phone rebooted (I don't know why). I reconnected to the platform and reconnected to the video presentation. This time my phone went black and I couldn't restart it.
Does anyone know what I can do?

Try to push on the two volume buttons together and connect it to the pc , and look on the driver manager ,and look for a change

Related

I got out of APX mode

As I understand from this thread;
http://forum.xda-developers.com/showthread.php?t=2118259&page=8
you can't get out of APX mode. Well, I did. Maybe my phone wasn't in proper APX mode, or maybe I'm confused as to what APX mode is, anyway I thought I'd share in case it can help anyone.......
Here is my original problem;
http://forum.xda-developers.com/showthread.php?p=51066504
As it says, I replaced the battery and the power flex cable (which I broke during disassembly). When connected to Windows it made the connect sound, and 'USB Device not recognised'. I pressed and held the power button and heard the sound again, nothing else changed. Went into Device Manager, it said APX device.
I searched and read through the above linked thread. Felt gutted.
I decided to run the battery charging script again (originally tried it before opening up the phone). It was running for about 5 min (with no progress) when I thought I'd try pressing and holding the power button again. While I was reading a thread, I kept pressing and holding the power button, and releasing when I heard the windows connect sound, then pressing and holding again. After about 5 times doing this, the phone just booted up normally! Everything was fine, all ok, all my stuff (texts, call logs, apps, media etc..) was all there
After charging it to 100%, I went into recovery (TWRP) to check it was all working ok. I was asked for a password, searched the forums briefly for it, will sort this after I post this thread. It couldn't see the sdcard, or mount, but this is related to the password problem I think.
Now, when I went to reboot, system, it said no OS installed. I rebooted anyway, and when it booted up it was like a fresh rom install. All my apps, texts etc... were gone, but my media was all still there.
Soooo, I'm pretty chuffed my phone is back! Does anyone know why my phone was reset just by going into recovery?
And i have read that you are back in apx. It's a shame we have to repeat it over and over. APX is a hardware failure which can't be 100% fixed. As you see now it kicks back in, the phone will never be reliable again.
Sorry mate.....wish it would be different for you ......
Cheers.

Red LED, No Boot Because of My Idiot Moment

Just happened today, I root the phone with kingroot, then installed XZDualRecovery to remove the kingroot and replaced them with SuperSU. One thing led to another, instead of flashing the SuperSU package, I end up formatting the internal storage. Nothing left there. Luckily I managed to realized my mistake in time, before rebooting the phone. So I download the flashable stock rom, planning to copied via MTP, then flash it to restore my phone. Two hours later, the download finished - yes, sadly, it took that much time here to download 1++ GB, and I still considered it fast - That 2 hours of being bored unfortunately led to another stupid mistake. I rebooted the phone before I copied and flashed the downloaded stock rom :crying:
TWRP only only offers me to flash the SuperSU package, then rebooted. Needless to say, the phone is dead. Just the red LED laughing constantly of my stupidity.
Quick Googling tells me the symptom pretty much the same with hardbricked ZL. Red LED, no Fastboot, No Flashmode. Pressing the button at the side of SDCard slot only make the phone vibrates, show Sony Logo, then blank. Okay, time to get panic, time to light a cigarette and take a distance for a bit to cleared out my head.
That done, I start googling to troubleshoot the problem. Quick search reveal the tools I need to recover the phone. I need Flashtool, ftf stock rom, good cable data, probably EMMA too. Unfortunately, the Flashtool only available through torrent, which has no peers, so I have to look somewhere else to get it. Wasn't ideal, but what a heck, I need to recover this phone.
Once all the tool in place, time to execute. Several guides I've found tells me I need to flashed the stock ftf with flashtool. But even with the cable plugged and constant pressing on the all available button (power, vol up, down and sdcard side button) can't make the phone recognized by the computer. I've tried every combination of cable plugged/unplugged, button pressed/depressed, all to no availed. Desperation seeps in.
Okay, time to take another break, another cigarette, and charge the phone for a bit. Afterward, I choose to tried to work on the phone recovery using linux. Maybe windows messed up somehow with the driver thingy that prevent me to fix the phone. No such luck unfortunately. Linux also failed to detect the phone. Hmmpppphhhh... Back to windows then.
I fired up the flashtool, pressed to lightning button, choose flashmode, pick the ftf files, then pressed the yellow button on the side of sdcard slot continually. The phone vibrates, 3x, I keep pressing, then it vibrates again 1x, but no respond from the computer, so I keep on pressing it. It vibrates again in 3x, paused, 1x, long paused rhythm. Then something happened, the LED turn green, and the windows notifying something happened. The log column of the flashtool start filling with lines, but end up in lost connection with the phone. Its a progress though, so I turned the phone off for a bit, to restart the process again. What I've done:
1. Start the flashtool.
2. Wait till it finished the initial detection.
3. Pressed the lightning button in flashtool.
4. Choose the Flashmode.
5. Choose the ftf files to be flashed, then pressed the flash button.
6. Pressed the button at the side of the sdcard slot continually - using a bamboo toothpick - until the LED turn green.
7. Let the flashing process done.
8. Restart the phone.
Voila, the phone boot normally, showing the sony logo, then the blue wave then it boot to the wizard screen with low batt warning. So I plugged it to a charger, then proceed with the wizard. The funny thing is, I swear I had more than 90% battery before I entered my special idiot mode. Apparently all of that red led period drained the battery fast. So after I finished the wizard, I put the phone on airplane mode to accumulate enough juice (till 9%) then I test to reboot the phone to make sure it really work. And it does. So I turned it off, to charge faster so I can start updating the firmware (I used C6502_10.5.A.0.230_10.5.A.0.230.ftf) and sets the phone straight again.
So that's how I spend my quality time today. Not much, but hopes it can help anyone out there with the similar problem. Cheers.
Very informativ.
Thank you for sharing your experience. I've found it very useful.
seriously a big thanks. thats a lot of effort. cheers to you. even though i dont need it now (hoping i dont end up like that) its still a great gesture from you.

Galaxy Tab 3 NO Power, boot loops when plugged in. Otherwise nothing Video attached.

Hi all, I've been using XDA for years since the original O2 XDA's and I have never had to post anything as I've always found my solution. I'm hoping somebody can assist me with a problem I have on this stock galaxy tab 3.
The device was brought to me after being thrown down the stairs. I replaced the screen and built it back up,
Removed battery connector and reconnected = nothing happens
Press power = nothing happens
press download mode = nothing happens
press recovery mode = nothing happens
Plug USB into PC = nothing happens on PC or tablet
Plug in USB mains charger and it displays battery charging logo but it doesn't fill or animate the fill then it starts the samsung boot screen. It reboots and continues to do this constantly and never ends.
I've tried two batteries and both batteries work in another tab 3 but neither batteries changed how the device works.
Thank you for any advice in advanced!!
I just received a Tab 3 lite (SM-T110) for repair, it's having a similar problem.
It does automatically turn on when plugged into charger or computer.. It is stuck on a bootloop, requiesting a Kies recovery. It does reboot when given the three finger salute (center button, volume down, and power) - it will not enter recovery mode though - same firmware error message). The device is also full off or full on, no indication of it's it's recharging or no - let the battery run out, it's off - else it's on (does not turn on or off with power button). I don't have any info how it got into this state - most likely power loss during a firmware update, but haven't ruled out other possibilities (ie bad rooting job, a custom ROM upgrade went wrong, etc). I'm not 100% concerned about cause, but hopefully I can unbrick the thing.
Anyways, I loaded Kies onto my computer and put it into recovery mode and plugged it in - nothing. Exit the recovery mode of Kies, and all of a sudden the program goes nuts trying to connect and disconnect from the device. Hmm... Okay, disconnect it, uninstall Kies, install Kies3 and try again - same thing except it complains the device is too old when the program leaves recovery mode - but same thing otherwise - does not show up in recovery mode, connects and disconnects at huge rate when not in recovery mode....
Hmmm...
Now looking at the screen, it does indicate (in the upper left hand corner) that it's in ODIN mode... So my next step I figure I'll try ODIN (although I'm researching ODIN at the moment as I haven't used it before (never had to unbrick anything from Samsung prior to now).
Okay, that was painless - downloaded and installed ODIN 3.10.7, and then downloaded the latest firmware from Samsung, extracted the firmware, added it to ODIN's AP line, then hit start to push the latest firmware onto the tablet. Good as new again.

[Q] GALAXY S2 - So weird [NEED HELP]

SHORT INTRO: My GF's phone, I am from PH [not living in Manila] so no reliable technicians, but my Gf brought it to one, the technician flashed it but I think it was fake or something becase it says Android 4.0, but exactly looks like Android 2.3, AND the phone keeps searching for network even if sim card is inserted. so I checked it myself.
I am frustrated and spent hours trying to fix this phone. AND I DONT GET IT!! WHY??
1.) I thought usb port is broken, but it was fine, i left the phone with charger connected for how many minutes, then it went on showing the battery charging animation.
2.) so i tried to boot, I SPENT HOW MANY MINUTES and TIMES PRESSING THE POWER BUTTON and it won't boot, I SMASHED THE POWER BUTTON [not hard tho], DISASSEMBLED AND CHECKED THE BUTTON, THEN TRIED AGAIN, THE SAME THING, but then IT WENT ON AFTER A FEW SECONDS, THEN I TURNED IT OFF[to prepare for installation of stock rom], THEN IT WONT BOOT, SOMETIMES WILL BOOT AFTER HOW MANY SECONDS OR MINUTES BUT WTF IS THIS. <<sorry :crying:
3.) i tried RECOVERY[stock] AND DOWNLOAD, it went into recovery mode ONCE, i tried wiping it all, "reboot system now" AND IT DIDN'T BOOT, IT WENT OFF, SO I AM BACK AGAIN TO NUMBER 2 PROBLEM. THEN IT WENT INTO DOWNLOAD MODE, but ODIN won't detect, I downloaded samsung usb drivers, the cable is from samsung, accessed the device manager[windows 10] and no device.
WHAT I TRIED/SEARCHED[NO LUCK THUGH]:
1.) turning it on without the use of power button [usb cable to computer, pressing volume up & down]
2.) turning it on with charger then removing battery quickly and reinserting it.
3.) i think everything, i've been searching all over the internet and here, no solution.
PLEASE! I need help. We've been planning to buy Galaxy S5 but we don't want this phone go into waste. This phone is over a year old. Is it because of the ROM? I really tried to boot into recovery but I don't understand problem number 2. PLEASE HELP! I'M DESPERATE :crying:

Oneplus 5t black screen unbricktool doesnt seem to work

I've got a dead oneplus 5t from my son. It was not charging anymore.. So I've replaced charging cable and battery.. Seemed to work it was charging... However it doesn't boot... No logo screen screen stays black/blank.
Tried several suggestions on this forum to get into recovery mode, fastboot mode... But still nothing. Only vibrating works after a few seconds.
So tried to unbrick with OP5T_Unbrick_tool_dumpling_43_J.40_181105(OOS.5.1.7) and the qualcomdrivers..
I was able to install the drivers and I see they are installed in devicemanagement.. and an empty folder create for oneplus.
I charged the phone all night and was able to download the upgrade. It then says download complete and I tried to restart the phone..
Still just vibrating but nothing happens.. Seems like everything has vanished from the phone, no recovery, no bootloader, no files.
So how to proceed to get all the stuff on the phone? And maybe the displayscreen is dead, but how can I tell?
Also tried the SMT upgrade. Strange thing is the device and com port are seen in devicemanagement and active when I connect without volume up, but cannot start because it says When I try to use smt mode the program says: "This COM port is disable by user". With volume button up pressed and then connect, ledlight turns green but the qualcomdevice is grayed out in devicemanagement and it says waiting for device..
Any help is welcome. I am a noob in how to proceed on the phone however I have an IT background.
Spent already so many time figuring out .. maybe it's effortless and its for the trashbin.
Thanks in advance
SOLVED
I opened the phone again loosened all those tiny connections to battery, screen,charger, mainboard and re-attached them.. Somehow a connection seemed to be fitting allright as yI looked at it, but apparently wasn't :good:

Categories

Resources