Help, I got into developer mode for the first time, decided to see what was there, chose the dsu loader, there were several items, chose random. After a while I rebooted the phone and it is in an eternal reboot. It turns on only before real me runs on the android screensaver
in the device manager on the PC it is displayed as qusb_bulk_cid
English?
0kti said:
English?
Click to expand...
Click to collapse
Help, I got into developer mode for the first time, decided to see what was there, chose the dsu loader, there were several items, chose random. After a while I rebooted the phone and it is in an eternal reboot. It turns on only before real me runs on the android screensaver
Related
OK. I have had my Atrix 4G since it first came out. I rooted it and installed apps and made customizations to it, etc.
I never installed a custom ROM since the tweaks I made fit my taste enough to not need to install a custom ROM. I have thought of it...but that is for another time.
Anyways, I recently changed fonts on using FontChanger and everything was working fine. However, last night I decided to change to another font and after rebooting my phone, I am now stuck in the ever so pleasant "Boot Loop".
I have tried wiping and restoring back to factory defaults, which appeared to work, but once I start going thru the process of setting up the phone and getting to the "home" page, the phone will suddenly automatically reboot and start to loop again. I can perform a reset which allows me to go thru the setup process again, but it suddenly reboots again after a few minutes.
I am guessing that perhaps the font is still causing problems, but I am not sure how to check to see if that is the case or not.
I have looked at other boot loop threads but I keep getting a bit confused as to what I should attempt or not attempt to do. It seemed to me that loading the 1.2.6 SBF might be my answer, but I have read that I could brick my phone doing that. Not to mention that some of the download links are dead....
Sorry for being yet another numbnutz and the long thread, but I would greatly appreciate some guidance on how to recover!
Thanks!
Ok... So after resetting my phone a few times I noticed that it goes into the boot loop cycle once the screen shuts off/or goes into sleep mode. If I keep the system from going to sleep everything appears to work fine.
My guess is still a font issue, but I thought a factory reset would've replaced the font back to default.
Anyone experience this issue or something similar to it?
And as a second thought can someone link me to the default fonts that I can try to reload?
UPDATE: well it looks like i am good to go again. It just occured to me that I can just download and use FontChanger to replace the bad font with the stock font. i let me phone go to standby mode and it didnt boot loop.
MODERATOR - Please feel free to close this thread as I believe I solved my own problem.
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
Hi all.
I have installed the Cyanogenmod 12.1 UNOFFICIAL on my Galaxy S II for several months, but yesterday, suddenly, the phone shutted down and kept doing this everytime I tried to turn it on, until I couldn't even go further than the "Samsung Galaxy S II" sign.
At first I could boot in recovery mode, so I tried to do a full wipe and then re-install the Cyanogenmod, but something went wrong during the installation and a dead android with a red triangle appeared in the background. I rebooted the phone, and from that moment on I couldn't even boot in recovery mode anymore.
So I followed this guide found in the forum to fix the issue (http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771) and it worked well, because the phone installed everything successfully.
Now, the bad news is that the phone keeps shutting down soon after the operative system starts (I can't even finish the initial configuration). The good news is that at least I can boot in recovery mode (in this way the phone is turned on as long as there is enough battery energy, so it is not an hardware problem, I guess).
I really don't know what else could I do.
Can you help me in any way please? Is it a known issue? How can I fix this?
If you need further informations I'll be happy to let you know them.
Very thanks in advance.
You are using an unofficial build of CM, install an official build of CM12
Fhronk said:
Hi all.
I have installed the Cyanogenmod 12.1 UNOFFICIAL on my Galaxy S II for several months, but yesterday, suddenly, the phone shutted down and kept doing this everytime I tried to turn it on, until I couldn't even go further than the "Samsung Galaxy S II" sign.
At first I could boot in recovery mode, so I tried to do a full wipe and then re-install the Cyanogenmod, but something went wrong during the installation and a dead android with a red triangle appeared in the background. I rebooted the phone, and from that moment on I couldn't even boot in recovery mode anymore.
So I followed this guide found in the forum to fix the issue (http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771) and it worked well, because the phone installed everything successfully.
Now, the bad news is that the phone keeps shutting down soon after the operative system starts (I can't even finish the initial configuration). The good news is that at least I can boot in recovery mode (in this way the phone is turned on as long as there is enough battery energy, so it is not an hardware problem, I guess).
I really don't know what else could I do.
Can you help me in any way please? Is it a known issue? How can I fix this?
If you need further informations I'll be happy to let you know them.
Very thanks in advance.
Click to expand...
Click to collapse
Is your device boots and works well on stock?
nhmanas said:
Is your device boots and works well on stock?
Click to expand...
Click to collapse
My device couldn't even boot in the end. However I solved the problem by changing battery, so it wasn't a software problem. Thank you anyway!
Rooted Fire hd 7 screen repeatedly turns black
Hey guys, so I had just rooted my fire hd7 and then I tried getting the google apps on it. In the process, I installed some google apps and then my fire hd started going to a black screen( I do believe I followed the instructions wrong ). As soon as I unlock my device, it shows the home page for a sec then the screen turns black and it repeats that process. I tried the factory resets and reboot and it did not work.
I hope I did not permanently damage my device. Is there anyway to fix it from my computer?
joshhdaniel said:
Hey guys, so I had just rooted my fire hd7 and then I tried getting the google apps on it. In the process, I installed some google apps and then my fire hd started going to a black screen( I do believe I followed the instructions wrong ). As soon as I unlock my device, it shows the home page for a sec then the screen turns black and it repeats that process. I tried the factory resets and reboot and it did not work.
I hope I did not permanently damage my device. Is there anyway to fix it from my computer?
Click to expand...
Click to collapse
Does it do this after a reboot? Do you have ADB authorized?
How did you exactly try to install GAPPS, with JMZ tool ?
Potentially it's simple to disable various apps via ADB, if you are set up to do so (a great tool is "Debloater")
bibikalka said:
Does it do this after a reboot? Do you have ADB authorized?
How did you exactly try to install GAPPS, with JMZ tool ?
Potentially it's simple to disable various apps via ADB, if you are set up to do so (a great tool is "Debloater")
Click to expand...
Click to collapse
Hey im not sure why my title says goes black after "flashing gaps" i have no idea what that means lol
I didn't write the "flashing gaps" part. But what happens is that everytime i turn it on and slide left to unlock, it shows the "homepage" for about a second and turns black , and it repeats that process until i turn it off.
Yeah im sure there is some way to fix it through ADB but i have no idea how .
I had download 5 google apps, but I installed them wrong. i was in the Es File program trying to install one and it went wrong after that.
any videos on how to use "Debloater" and where to download it from.? I will definitely check that out. I just had this tablet for a month I would highly appreciate it if someone could help me fix it.
joshhdaniel said:
Hey im not sure why my title says goes black after "flashing gaps" i have no idea what that means lol
I didn't write the "flashing gaps" part. But what happens is that everytime i turn it on and slide left to unlock, it shows the "homepage" for about a second and turns black , and it repeats that process until i turn it off.
Yeah im sure there is some way to fix it through ADB but i have no idea how .
I had download 5 google apps, but I installed them wrong. i was in the Es File program trying to install one and it went wrong after that.
any videos on how to use "Debloater" and where to download it from.? I will definitely check that out. I just had this tablet for a month I would highly appreciate it if someone could help me fix it.
Click to expand...
Click to collapse
Can someone please help me with this?
I'm experiencing the same issue. Happened after running snap chat. Worked fine then stopped.
Morning Folks.
3 Days ago (Saturday) I received my Pixel 6 (Vodafone UK), Sunday evening, the device turned itself off, only noticed in the morning when the alarm didn't go off.
I eventually received my E-Sim from Vodafone yesterday (Monday Morning), All was fine during the day until the evening. The device rebooted, after the reboot I entered my pin, and non of the apps would work, the device rebooted again. After this reboot then I would have 3-5 seconds before it would reboot again.
Went into Fastboot and WIpe/Formatted device... This did not make any difference, it would reboot at the welcome screen instead.
My questions.
Has anyone came across this before on the pixel 6?
The last phone I updated firmware was the Galaxy I5700, and I noticed ADB on the fastboot section, Is it possible to get a Vodafone UK Image for the pixel 6 and reflash it?
The only way this could happen is that you tried to boot a modified boot.img or the system UI was changed.
I do not think you are telling us the whole story here. Missing information.
Try booting in SAFE MODE.
vandyman said:
The only way this could happen is that you tried to boot a modified boot.img or the system UI was changed.
I do not think you are telling us the whole story here. Missing information.
Try booting in SAFE MODE.
Click to expand...
Click to collapse
Afternoon
Thanks for the reply. Nope literally the above happened as is, I've no interest in a new ROM, changing any file system, or changing UI... Actually one thing I did change was changing the Icons to Themed Icons(beta mode) or something, this was within Settings, but could not tell you exactly where. Wouldn't think this would affect anything else tho.
I am unable to boot into safe mode. I have wiped the device, and the next reboot takes me to the Welcome Screen (Get your Device Ready) then a few seconds later, it reboots. The reboot afterwards might not even take me to the welcome screen and just get stuck on the Google Logo.
Anyway I've nipped to Vodafone today and the guy at the desk checked it out, going back for a warranty job, he managed to get it to boot to the main screen, but the screen was doing things by its self, and again rebooting for him. See how this goes and maybe they will find the issue.