I have a RN5p which I bought from China. It was running the global ROM.
I bought it 3 months ago and until now it was working fine.
Yesterday I turned on USB debugging and tried to install ADB, but all I got was "ABD is not a recognized command" on my PC and then I assumed there was some issue with my PC and I unplugged my phone and turned off USB debugging (I used this method: https://www.xda-developers.com/install-adb-windows-macos-linux/ and I never managed to get past step 4 cause powershell was screwing me over).
6-8 hrs later my phone's screen froze and I had to force reboot it (hold pwr button for 10s). Once it restarted it was working fine, but then it froze again, and this time it started to boot loop, never getting past the MI logo, sometimes the android with the 3 dots would show, but it usually just remains there or freezes and then reboots.
After like 15 reboots, I managed to reach the lock screen and unlock the phone and worked fine for 30 mins then froze again.
It took even more reboots this time to get it to boot but same thing, froze after sometime.
Now sometimes it doesn't even manage to get past the lock screen, just freezes and reboots.
Additional Notes: I highly doubt that this boot loop is bcoz of ADB as I never installed it on my phone
I checked online and my phone is running the offical international rom(checked on the mi website)
My bootloader is locked( tho I did unlock the oem unlocking setting for 5 secs just to see what happened and then locked it again, but this was at least 6 weeks ago)
Out of the 4 times I managed to get my phone running normally, it froze 2 times while I was watching Youtube and 2 times while it was locked
Running miui 10.0
I would love to have my phone back to normal
All help is appreciated.
Edit: It just turned on and I allowed OEM unlocking. I think it will be easier this way. And now its back to boot looping.
Edit 2: I factory reset it
Surge746 said:
I have a RN5p which I bought from China. It was running the global ROM...............
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3818384
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Related
Hello guys,
2 days ago my phone randomly bricked itself. It wasn't rooted or anything, everything on it was stock (I've been using it for 2 years).
Before the brick, I had the screen flickering issue, my WiFi stopped working and the sound also (this happened during a period of 2 months) - during this period my battery started draining very fast, I could use the phone for max 2 hours per day (stand-by or use, doesn't matter).
So 2 days ago I ran out of battery and left the phone to charge during the night. When I woke up, I tried to turn the phone on but at first It got stuck at the PIN insertion, and after rebooting it twice it just got stuck in a boot loop.
So what I did was follow the TOT guide and tried to flash a stock rom. All went well until I tried to do a factory reset before initial boot - I got a kernel crash and my phone is unable to enter download mode since this moment (the loading screen shows up, and once it loads the screen goes black and my phone is recognized as qualcomm. etc).
At this moment I found about BoardDiag and used the software in order to try to repair my phone. Everything works well with BoardDiag, but once it finishes it's job reboots, I get kernel crashes yet again and I am still unable to enter download mode (It's like the program didn't do anything and the phone just reverts itself to It's previous state).
So is this a hardware issue or am I doing something wrong?
Anyone?
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
this is the best method so far.
replace your battery as known to cause corruption boot problems when dying
Also try this..... download LG mobile support tool and install + run, ignore start upgrade > battery out > battery in (dont power on) USB cable in pc not phone > hold volume up plug in usb to phone, you will get download mode in blue in box on phone > now on pc > LG mobile support tool > choose options then UPGRADE RECOVERY. will take 57+ mins to complete (over 1 hour) it might seem stuck frozen at 10% to 22% it's not just wait it out...
Jahanzaibawan said:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
this is the best method so far.
Click to expand...
Click to collapse
As I said in the thread, I've already tried this but when the phone reboots and when I try to enter download mode again the phone is not being recognized again.
Several days ago I was watching a livestream when my phone froze & suddenly went into bootloop. At this point I've tried all that I know to - I've flashed several different OS versions using the Nexus Root Toolkit, I've manually flashed 6.0.1 & 7.0 (not sure if 7.0 was a good idea to flash tho just because of what's been happening), and at this point I'm not even able to go to the recovery to manually do anything. At one point the phone did work, but it would constantly go back into bootloop for a few minutes before coming back out, but now it is simply stuck in bootloop. I was using Android 6.0.1, stock. The phone was rooted for awhile, but I eventually unrooted and went back to stock. I don't understand what happened, and everything I find on the internet about Nexus 5x bootloop is in relation to the 7.0 update, which I did not bother downloading (luckily lol). Is my phone gone forever? :/
I got my phone replaced some time ago as it also went into a bootloop mid usage. Flashing anything didn't help. My finding was, that the phone worked as long as it was cold. Leaving it off to cool down and putting it on a cooling pad helped for about 10 minutes. From what I understand, it may be a hardware issue.
Gesendet von meinem Nexus 5X mit Tapatalk
See the other threads on here that showed up within the last 1-2 Weeks regarding bootloop, bricked or QHSUSB. Chances are, it might very well be a hardware problem (bad soldering).
My nexus5x suddenly died 5 days ago (with no prior symptoms). Unlocked, no root, stock 7.0 november update.
I was able to turn it on once for ~3hrs after walking outside for 20 minutes, right after it first froze down/bootlooped.
Then it showed up as "QHSUSB_BULK" (8009?) when connected to a pc, but would not even start fastboot anymore.
I tried putting it in the freezer in a plastic bag for ~10 minutes. Fastboot worked, booting freezed inbetween; twrp would not let me enter security pattern.
So I let it rest for two days. Then decided to give it one more try by putting it on my radiator for 20 minutes (just warm, not hot! - please don't panic and make the situation even worse!)
Got it to boot up regularly and keep it on for ~20 minutes. So was able to do one last backup of msgs, imgs, etc. (while still on the radiator). Booted up successfully two more times, but with every decreasing on-time.
RMAing now through Google.
Hello there everyone! Let me explain my problem:
Backstory
I have a Samsung Galaxy Nexus GT-i9250 maguro since 7-6 years or so. I've been flashing some roms into it and everything went well since a week ago.
I had installed from a very long time this version of CM "cm-13.0-20160921-NIGHTLY-maguro" and I have not updated it, so I basically was running that from a very long time.
Three weeks ago the phone started behaving strangely, it was closing automatically, and I thought that it was a temperature problem (being a very hot summer) so I did not worry too much.
Everything was working fine, charging and connecting via USB .
Problem
Last week the phone once again died and I tried to boot it up normally as I would normally do, but nothing happened, not even the Google logo popped up.
So I removed the battery and put it back in, the phone booted up to the Google logo, then after two or three seconds the Google logo flashed like brightness went up to 100% and black screen.
Went into fastboot, booted TWRP to see if that was working, and the recovery was working fine.
Things got worse.
At the moment
I cannot get the phone to do anything if it's not connected to a power source.
If the phone is connected via USB, or charger, I can get it to go ONLY on fastboot, and download mode. If I unplug the phone while on fastboot or download mode, the screen brightness goes up to 100% for half a second then it glitches out and goes into black screen immediatelly. I can not access bootloader nor recovery mode from fastboot, because the phone reboots, shows the Google logo and then it dies.
What I tried
Thinking that maybe the ROM went crazy, I followed this guide to flash the phone with all the original ROM and recovery (I downloaded "yakju-jwr66y-factory-4cadea65" and followed the instructions of the guide).
Nothing changed, if the phone is not connected to a power source, it is basically dead, if I put it to a power source it shows the charging logo for a second, then black screen, and I can only boot up fastboot and download mode.
I don't know if this might help but I've also tested the battery voltage and it seems to be fine.
Last thing, if I connect the phone to the PC (with the battery or without) every 2 seconds it shows up that an unidentified device is being detected.
I currently am using a laptop running windows 8.
On my desktop computer the same thing happens (the device detection) but from device manager I see a OMAP4400 (something like that) popping up but at the moment I cannot use my desktop PC since I'm traveling.
I would really like to know what happened to my phone, any answer will be appreciated.
Thanks in advance!
Update [solved]
After doing some research and trying different methods I gave up. But then I realized that maybe trying the stupidest thing could be the solution, so I went to a phone shop and asked them if they had some sort of test battery that I could plug in my phone temporarily to see if it was booting up.
Turns out, it was the battery.
I bought a new battery and now the phone runs smoothly like it's new.
I feel so dumb and I'm so sorry if I've made some of you people waste your time by reading the poem of the first post.
Hopefully this will someday help someone that will have the same problem of my GT-I9250!
(This thread can be closed now)
My Pixel XL 128GB on Android 10 just randomly started bootlooping during normal use. Totally stock with Verizon sim card, but received directly from Google (actually it is a warranty replacement received about 2 years ago for a Nexus 6P that I bought directly from Google in Feburary of 2016 due to faulty battery).
Bootloader is still locked. USB debugging is disabled.
Google logo just keeps appearing and disappearing on screen. I can get into fastboot by holding power and volume down, but choosing recovery mode just goes back into bootloop.
Am I hopelessly bricked?
thomase00 said:
My Pixel XL 128GB on Android 10 just randomly started bootlooping during normal use. Totally stock with Verizon sim card, but received directly from Google (actually it is a warranty replacement received about 2 years ago for a Nexus 6P that I bought directly from Google in Feburary of 2016 due to faulty battery).
Bootloader is still locked. USB debugging is disabled.
Google logo just keeps appearing and disappearing on screen. I can get into fastboot by holding power and volume down, but choosing recovery mode just goes back into bootloop.
Am I hopelessly bricked?
Click to expand...
Click to collapse
After looping several times I was able to reboot once. I went into developer mode and enabled "USB debugging" soon after which it crashed again. Only then did I realize that I was SUPPOSED to enable "OEM Unlocking" rather than "USB debuging"!
I still haven't been able to boot it again since. Any suggestions? Would heating or cooling the device help? What are the chances that re-flashing the factory image will even help?
thomase00 said:
After looping several times I was able to reboot once. I went into developer mode and enabled "USB debugging" soon after which it crashed again. Only then did I realize that I was SUPPOSED to enable "OEM Unlocking" rather than "USB debuging"!
I still haven't been able to boot it again since. Any suggestions? Would heating or cooling the device help? What are the chances that re-flashing the factory image will even help?
Click to expand...
Click to collapse
Well, I was able to get in again and barely had enough to enable "OEM Unlocking". I proceeded to unlock the bootloader and re-flash the latest Android 10 factory image (the one ending in .20). I can't get through the new phone setup process before it crashes and eventually reboots. It might get as far as connecting to Wifi but always eventually crashes while "Checking for updates...".
I could try an older Android 9 image, but it seems like I have a straight-up hardware failure (SoC, DDR, flash memory, etc.).
At this point I'm resigned to the fact that it is most likely dead. Are there any custom recovery images that I can flash that can run hardware diagnostics so I that I can pinpoint the failed component?
The same thing happened today to my wife's xl pixel still with android 9, now I've updated it to 10 and for now it works but I think it seems like there's a battery problem. I think the battery is bad but it is strange that it happens this way
Looks like i have the same issue. If you remember one of the android betas (beta 4 i believe) had this issue where the phone got stuck in bootloop. I had this issue and im unable to fix it. My phone keeps bootlooping on the google logo...i tried reflashing the factory image for 9.0 or 10.0 but no luck. I even tried installing a custom rom and that too reboots on the google/custom rom logo. Is there any other way to fix this? Is this a hardware issue? please help
A week ago, all of a sudden, my Pixel decided to freeze and become unresponsive. To make a long story short, it only goes to the Google logo screen and will not go into bootloader or recovery mode. Took it to a repair shop and they said it needed to be sent back to Google (it's three years old so long past its warranty) which would cost a fortune. They said it is soft bricked.
I'm looking into things and since my phone is already useless, I surely can't make it any worse. (fingers crossed.)
I'm wondering if anyone has any tips on how to get my phone back up and running whilst also keeping all of the data on my phone. I'm not keen on wiping the data as it has important information on it. Is it possible to unbrick a Pixel XL without factory resetting it?
Does anyone have a simpletons guide on how to do it? I've looked at numerous guides and they are either long winded or far too complicated for me. I'm not familiar with downloading a file to unzip it or extracting it. Although, I am very much willing to learn given my circumstances.
If anyone can provide any information, I would be very grateful!
i think if anything at this point, you need to assume none of your data can be saved. if you send it to google for them to fix, no data will be kept most likely, nor if you find any solution to do yourself. what happens if on the google screen you hold down power and voldown until it turns off and then keep holding them down?
It goes into fastboot with the android guy on it's back and it gives me the "restart bootloader", "recovery mode", "barcodes", etc, options. None of which the phone can enter apart from the barcodes and the powering off option. :crying:
HanaTruly said:
A week ago, all of a sudden, my Pixel decided to freeze and become unresponsive. To make a long story short, it only goes to the Google logo screen and will not go into bootloader or recovery mode. Took it to a repair shop and they said it needed to be sent back to Google (it's three years old so long past its warranty) which would cost a fortune. They said it is soft bricked.
I'm looking into things and since my phone is already useless, I surely can't make it any worse. (fingers crossed.)
I'm wondering if anyone has any tips on how to get my phone back up and running whilst also keeping all of the data on my phone. I'm not keen on wiping the data as it has important information on it. Is it possible to unbrick a Pixel XL without factory resetting it?
Does anyone have a simpletons guide on how to do it? I've looked at numerous guides and they are either long winded or far too complicated for me. I'm not familiar with downloading a file to unzip it or extracting it. Although, I am very much willing to learn given my circumstances.
If anyone can provide any information, I would be very grateful!
Click to expand...
Click to collapse
I have the same exact problem. Started Nov. 14. Talked to google asked me to take it to uBreakiFix. They ran diagnostics and said they can't fix it.
My phone used to boot up randomly but would freeze after 2-3 mins and crash again into a bootloop. Now it's stuck on white "google" screen and can't get into recovery or any other modes.
Nilkong said:
I have the same exact problem. Started Nov. 14. Talked to google asked me to take it to uBreakiFix. They ran diagnostics and said they can't fix it.
My phone used to boot up randomly but would freeze after 2-3 mins and crash again into a bootloop. Now it's stuck on white "google" screen and can't get into recovery or any other modes.
Click to expand...
Click to collapse
by boot up randomly do you mean it would randomly reboot or turn on while it was off?
sudoxd said:
by boot up randomly do you mean it would randomly reboot or turn on while it was off?
Click to expand...
Click to collapse
I mean it would boot successfully and take me to lock screen where I can use the phone for few minutes until it freezes again.
Currently I am connected to computer with adb shell open and have phone on the screen where I can see options to select 'barcode' 'recovery mode' 'power off'. The screen shows baseband version, CPU, UFS, DRAM, "Device is locked".
Adb is recognizing the devices (I can't unlock because I had the option to "OEM unlock" turned off in settings). But when I try selecting 'recovery mode' its back to 'Google' screen and stuck there.
Nilkong said:
I mean it would boot successfully and take me to lock screen where I can use the phone for few minutes until it freezes again.
Currently I am connected to computer with adb shell open and have phone on the screen where I can see options to select 'barcode' 'recovery mode' 'power off'. The screen shows baseband version, CPU, UFS, DRAM, "Device is locked".
Adb is recognizing the devices (I can't unlock because I had the option to "OEM unlock" turned off in settings). But when I try selecting 'recovery mode' its back to 'Google' screen and stuck there.
Click to expand...
Click to collapse
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
sudoxd said:
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
Click to expand...
Click to collapse
I flashed the new version of OTA from google's site. And it looks like it's booting up. Will report back if it crashes or continues to hold up.
Thanks!
EDIT: It's back to boot looping. It was at the "G" screen with white loading bar underneath. It froze there and went back to bootloop. Looks like there might be no avail.
Similar issue here. I gave up on it a month ago, but I figured it can't hurt to ask around. FWIW, there seem to be a lot of similar reports on Google's Pixel support forum.
Anyway, during the 2nd year of owning my Pixel XL (got it in Septempter 2017), I started experiencing slowdowns and random reboots more frequently, but never any bootloops until after receiving Android 10. After receiving Android 10, the random reboots seemed to be happening more frequently. I also experienced a weird issue where the phone would spontaneously exit out of the Google app (reached by left edge swipe from home screen) consistently within a few seconds of entering it.
Eventually, after another increasingly common random freeze, the phone rebooted and got stuck in a bootloop. Initially, chances were high that I would be able to complete the boot process after a few attempts, but inevitably, it would freeze and start bootlooping again. During the handful of successful boot attempts, I was able to backup some photos, and more importantly, enable OEM bootloader unlock in the developer options. After several more failed attempts to boot successfully, I did a total reflash of the latest factory image as of September 2019, after which I was able to get partially through the new phone setup process before crashing. For each subsequent attempt, the crash would happen earlier and earlier in the setup process until it wouldn't get further than the 'G' logo before rebooting. When the October 2019 factory image became available, I tried flashing that as well, but no luck.
On one hand, considering that the failures got progressively worse over time, it seems that this is fundamental hardware failure in the SOC, motherboard, RAM, etc. On the other hand, there seems to have been so many recent reports of this, especially after the Android 10 update, that I wonder whether or not it is software issue. Or could it be some combination of both, where the Android 10 update is pushing the hardware in new ways that is more likely to exacerbate an underlying hardware flaw?
Should I try re-flashing with Android 9 instead? At this point, it is a total brick...
sudoxd said:
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
Click to expand...
Click to collapse
Would this be possible to do with a phone that doesnt turn on but the computer does see it as a qualcom device?
ckidmcd said:
Would this be possible to do with a phone that doesnt turn on but the computer does see it as a qualcom device?
Click to expand...
Click to collapse
Needs to boot to any recovery, custom or not, to sideload an ota
sudoxd said:
Needs to boot to any recovery, custom or not, to sideload an ota
Click to expand...
Click to collapse
Do I have any options to pull the data from the device since it does see a qualcomm device when plugged into a computer?
ckidmcd said:
Do I have any options to pull the data from the device since it does see a qualcomm device when plugged into a computer?
Click to expand...
Click to collapse
does fastboot see your phone at all if you type `fastboot devices`