i've unlocked my other xiaomi phone with my pc and it works fine
but while trying to unlock my Mi6 bootloader the tool gets stuck at 99% and the loading seems to go on forever and it dosent even show a error message
i even left it over night but it shows 99% and the loading wheel keeps spinning
i even waited 15 days (according to some youtube videos )
but its not working!
did anyone face the same prolem and did you get a solve for this
TIA
Related
Hello , I have a serious problem with my gnex, yesterday i downloading on it some movies using mobile utorrent so when i checked my phone it was dead and kind of hot (it was plugged to the wall carger) , so i unplugged it and removed the battery and when i tried to restart it , it only showed the google logo the unlock logo and after aprox 10 sec green dots and lines appeasred around the logo, it doesn't enters in bootloader mode,so i left it whitout the battery this mornig and wvhen i tried to start it it showed the google logo it even showed the boot image and after it , it just staing on with a black screen , you seent only if it's dark in the room , now it enters in bootloader mode but after about 20 seconds the screen starts to flicker and green lines apear around the image , please help me , the phone was rooted unlocked and i was using 4.2.1 jb rom from modaco
First off: I have an AT&T HTC one X
I am an almost total noob when it comes to this stuff so please bear with me here.
I had my roommate put cyanogenmod onto my phone when I got it and all was well until I moved to Asia and got an unlock code from AT&T to be able to use it over here. The unlock code wouldn't work and I found some stuff online saying that it might be a problem with cyanogenmod. I followed a youtube instruction guide on how to get rid of the mod and everything was going fine until right at the end when I got a windows notification that the RUU had stopped working. I figured I would just do it again, but the actual program itself said it was successful. As I waited for it to reboot and load the roms, it started a loop. The loop is the white screen with the green htc letters for a few seconds and then it goes to a black screen with a phone logo in the middle. Around the phone logo is what looks like a recycling symbol except circular instead of triangular and on the screen portion of the phone logo there is an arrow facing down. I assume this is just telling me I need to actually download some software on the phone, but it won't connect via USB and every time it starts up it says that the drivers were not successfully installed and htc sync manager doesn't recognize that a device is even connected. The loop continued and i tried to boot it back into the fastloader which did nothing. I held down the buttons as if to boot it into fastloader, but this time for about 15 seconds which took me to a battery charging screen and finally ended the loop. I assume(hope) that since it's actually responding to input from the buttons that it's not irreversibly bricked. Is there any way I can get some version of android back on this thing? Any help would be much appreciated
Wrong forum buddy, you belong in the HTC ONE XL forum. Don't use anything from here because you risk a serious brick !
Well my G4 (VS986) has been running ok on 13b rooted since december 2015, and today it suddenly died, it was on my desk and when I tried to use it the screen was black and it won't turn on, something like this had happen before but I usually just remove the battery and voila it had it working again. But not this time.
Now It only goes to the LG screen and then it turns off again (but it doesn't bootloop) so I keep trying then I connected the phone to the charger and it tried to boot again and this time it went to a black screen saying Secure Booting Error and it was error code 1007 but it went off again.
Then I tried to access recovery mode and it can access and be there for 40 min and it wont turn off, however I can't put it on download mode alway when is connected to the PC it says "qhsusb_bulk"
Anyone have any idea on what happen and how to fix it.
Thanks.
Nevermind.. Say hello to a new bootlooping LG G4 !!
I put it on the freezer and after 20 minutes the phone boot up normal, but after a few minutes it went the famous boot loop.
Time for a new phone
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.
Since a few months, I'm facing this problem. The phone is working OK when I can get to the system, but If I turn it off or the battery runs off, it gets stuck on a loopboot: the Mi logo shows and restarts itself after a few seconds. Can't access the recovery mode (it just restarts again to the Mi logo), fastboot works tho'.
The only way I have to get to the system is to start the Fastboot Mode, keep the phone on it to drain the battery and once it's empty, plug it to the charger and try to boot 15-20 times until it magically works.
I've never unlocked the bootloader or tried to install anything, the ROM and Recovery are the Xiaomi's stock EEA. I'm on MIUI 13.
Any ideas about how I can fix this weird behavior? Anybody has faced the same problem?
Thanks for reading/helping and happy new year to you all!
helicida said:
Since a few months, I'm facing this problem. The phone is working OK when I can't get to the system, but If I turn it off or the battery runs off, it gets stuck on a loopboot: the Mi logo shows and restarts itself after a few seconds. Can't access the recovery mode (it just restarts again to the Mi logo), fastboot works tho'.
The only way I have to get to the system is to start the Fastboot Mode, keep the phone on it to drain the battery and once it's empty, plug it to the charger and try to boot 15-20 times until it magically works.
I've never unlocked the bootloader or tried to install anything, the ROM and Recovery are the Xiaomi's stock EEA. I'm on MIUI 13.
Any ideas about how I can fix this weird behavior? Anybody has faced the same problem?
Thanks for reading/helping and happy new year to you all!
Click to expand...
Click to collapse
Did you solve it? mine too acts so weird, it starts to call, reboots, and so on.
SubwayChamp said:
Did you solve it? mine too acts so weird, it starts to call, reboots, and so on.
Click to expand...
Click to collapse
Nope. One day it turned off and I never could boot back in again. Sorry.
..