I was/am rooted/unlocked, I flashed an unlocker for the hotspot, then the message for com.android.phone began popping up continuously. Tried accessing the bootloader, but for whatever reason, it won't let me get to it. It also appears that my Airplane Mode icon in Settings keeps rapidly blinking on and off.
I managed to turn on Debugging, but it doesn't seem that ADB can see the phone. I've tried to ADB into the bootloader and it won't work.
Windows DOES see the phone in Computer, so I know it does at least see it to access the drives on it.
Please, please tell me that there is still some way to make my phone work again.
Found my way into Recovery. Did a Factory Reset, but the issue is still there. Is there something I can flash that would fix the issue?
I don't care if I go back to stock, locked, unrooted. I just want my phone back. ^^;
johnequickiii said:
Found my way into Recovery. Did a Factory Reset, but the issue is still there. Is there something I can flash that would fix the issue?
I don't care if I go back to stock, locked, unrooted. I just want my phone back. ^^;
Click to expand...
Click to collapse
Wow im just going down the list in Q&A and you keep popping up, lol. You are having way too many problems with a brand new phone, i would READ this thread and RUU.
http://forum.xda-developers.com/showthread.php?t=2729173
And if you do RUU and first thing you should do is a nandroid backup in recovery. Also depending on what firmware you have i would S-off(then again with your track record maybe not) If something stops working after you just did something(like flash a mod or app) you can always go into recovery and restore a nand backup.
Related
I apologize first off for another boot problem thread.
First, I have never messed with my rom. I never flashed it or anything. The most I have done is load KaiserTweak and TomTom. Basic stuff.
I went to turn on my phone this morning and it stayed on the AT&T boot screen. It just freezes. I kept trying to soft reset the phone and at one point it loaded with like the default settings but nothing worked. The start menu only had the Today listed. The phone wouldn't work either. From then on, it always sticks on the AT&T boot screen.
I tried removing the battery and the sim card for a few hours and that didn't help. I tried turning on without the sim.
I am hoping to fix without a hard reset. I don't want to lose all of my contacts and all the data saved on the phone. Is there any way to save this stuff?
That's why you should always have scheduled backups at least once a week. I don't see this being fixed without a hard reset. You did everything that i would have personally suggested (taking out battery and everything for a few minutes). If all fails, you can always go into bootloader mode and reflash the ROM.
Is there no safe mode way to access the device? How about any work around so the computer can access the flash data without the device being in active sync mode?
Highly doubt it and i've never read anything about accessing the device when it's not on. It seems so sporadic and from the looks of it, only a reflash will get you going again.
This reminds me of back when I was trying to flash my Kaiser to 6.1... had exactly the same issues. Even worse actually since the problem started when I flashed a ROM wrongly, also without having an original to fall back to. Cue a night of trying to flash over my mistakes!!
I recall having some success with some specific mtty commands... argh, I'd bookmarked hundreds of threads on it back then but have since lost them all. All I know is there are a few commands you can type which may just get the phone booting again. Bit useless of me but it's a start!!
Ah, check these threads:
http://forum.xda-developers.com/showthread.php?t=371154 This one will erase all data
And post #2 demonstrates use of using the mtty boot command here:
http://forum.xda-developers.com/showpost.php?p=1765045&postcount=2
Those kinds of commands I managed to get my phone working with.
I figured out how to boot to the tri-color boot screen. The computer regonizes it and the boot command in mtty just does the same thing as turning it on.
Since my computer is now linked to the phone, isn't there some way to access files? Any commands in mtty that will work? Any other program out there that might help access the memory?
No one has any ideas about how to access the memory?
Did you manage to fix this in the end?
Got the very same problem with mine which hasn't been flashed in any way.
vigilante_xix said:
Did you manage to fix this in the end?
Got the very same problem with mine which hasn't been flashed in any way.
Click to expand...
Click to collapse
Never was able to figure it out. I had to reload from scratch.
Good luck with your issue. Hopefully some of the suggestions around here and elsewhere will get you back up and running.
Just received my G1 today. Haven't changed anything, went through first boot, got everything setup to my liking, downloaded a few apps from the market.
Rebooted the phone since it looked like I lost data connectivity, and it's now stuck at the bootloader screen. It doesn't seem that the camera button is stuck, I can push it and feel actually depress. Booted into recovery and did a factory reset/wipe, still no good.
Should I be able to reflash an original ROM image from recovery to get going again? (After I hunt down an SD card)
... how can you be "stuck" at the bootloader if you can already access the recovery?
Couple of things you can try:
1) Reflashing the ROM (since you can access recovery right?)
2) If you're actually stuck in the bootloader and can't get to any other screen, you can try:
Code:
fastboot reboot
3. If that doesn't work, you can try reflashing DREAIMG.nbh (RC29) and starting over.
Yea, it boots right to the bootloader. If I hold power + home it goes into recovery, but that doesn't get me anywhere.
Tried reflashing RC29 via the bootloader. After it's complete, I press the action key to reboot, and it goes right back into the bootloader.
Where am I supposed to enter in "fastboot reboot"?
Is there anything I should try updating at the recovery screen via SD card?
if you just got the G1 recently and you haven't installed any custom software on it and you're already having theese issues why not just exchange it for one that actually works instead of going through the headache of trying to fix it? Especially if the software hasn't been modified and you keep getting thrown into the bootloader
That'll be the next step. I didn't buy it locally tho, through the web, so I'd like to see what I can do before I go that route.
if you use the rc29 DREAIMG.nbh it writes over everything, so if your phone still dosn't load you may have a more serious problem, exchange may be your best bet
I've sent an email to the vendor I bought it from about exchanging it.
I've noticed that when booting into recovery, after pressing alt - L, the top of the screen says :
Android system recovery utility
E:Can't open /cache/recoverfy/command
Then it lists out the Alt commands.
possibly try downloading the DREAIMG.nbh file again, format your sdcard to fat32 once more, let your phone boot into the bootloader and apply the update and cross your fingers and pray to wich ever god you believe in
I've left the battery out all night. I was in the process of formatting the sd at the computer again, and tried powering on the G1. Holy crap it boots up!
Now I'm back to the problem of no data services. I can surf the web all I want on the dash, I know I have a data plan. I'll have to give t-mo a call I guess, since I can't get the G1 registered now.
laszlo462 said:
I've left the battery out all night. I was in the process of formatting the sd at the computer again, and tried powering on the G1. Holy crap it boots up!
Now I'm back to the problem of no data services. I can surf the web all I want on the dash, I know I have a data plan. I'll have to give t-mo a call I guess, since I can't get the G1 registered now.
Click to expand...
Click to collapse
ya i would call t mobile .they would prob replace for ya sounds like some thing weird going on!good luck
Ok, definently sending this back. It has stopped working again. I'd turn it off from the menu, swap out the SIM, and when I go to turn it back on, it'll boot to bootloader again. Reflashed later today for kicks, booted bootloader 1st time, booted up correctly the 2nd time (but didn't have SIM in), booted a 3rd time with SIM in to try to activate, but it went to bootloader again. Any subsequent boots are all to bootloader.
I'm thinking it's crappy hardware.
Still intermittent booting. Until I get the goahead to send it back for an exchange, what else do we think I should try. Could it be the radio version? I tried to update with an HTC radio, but the signature didn't let it load. What, if any, radio downloads will work with a stock G1?
I'll try a few more things tonight, and post up what happens. Maybe check out tmobile's downloads for firmware updates.
If I didn't buy the phone directly from t-mobile, would they be able to do anything for me if I take it in to a store?
laszlo462 said:
If I didn't buy the phone directly from t-mobile, would they be able to do anything for me if I take it in to a store?
Click to expand...
Click to collapse
No they won't. Your best bet is to contact HTC cause the phone is still under warranty, but you better contact them soon cause the phone is about to be a year old on Oct. 20th I believe.
I'll try that then, since all I got for a response from the seller was "has the issue been resolved yet?" I'll check with HTC today about the manuf. warranty.
After the forced AT&T software update, my WiFi will not turn on. I will go into WiFi settings, press the toggle button, and it will grey out and get stuck on "Turning on WiFi". I have tried wiping both caches, and I have replaced the bcmdcm.ko under system\lib\modules with bcm4330.ko, which was the one from the stock ROM. Nothing has worked and this problem persists. I am rooted and my bootloader is unlocked. Is there anything short of doing a full factory reset that can fix this problem?
Please post in the appropriate section.
Thread moved to Q&A
Sent from my Nocturnalized One XL using Forum Runner
Bigluc said:
After the forced AT&T software update, my WiFi will not turn on. I will go into WiFi settings, press the toggle button, and it will grey out and get stuck on "Turning on WiFi". I have tried wiping both caches, and I have replaced the bcmdcm.ko under system\lib\modules with bcm4330.ko, which was the one from the stock ROM. Nothing has worked and this problem persists. I am rooted and my bootloader is unlocked. Is there anything short of doing a full factory reset that can fix this problem?
Click to expand...
Click to collapse
Have you tried flashing the boot.img via fastboot? That seems to help a lot of people.
ronnie498 said:
Have you tried flashing the boot.img via fastboot? That seems to help a lot of people.
Click to expand...
Click to collapse
Ok I've googled around alot and looked on this forum but I can't find a boot.img anywhere that isn't modified. Can you point me to the stock boot.img?
My mom has a Vivid and her phone has been doing this ever since the update was pushed down by AT&T. Since she lives 1000 miles from me, I didn't root her phone, and leaving it stock, the only thing that ended up working was a factory reset. The other thing that was happening after the update was every boot would go through the "Optimizing application 1 of x..." message like it does after the update. I get the impression that whenever she performed the mandatory AT&T update, something didn't go correctly, which is why her Wi-Fi was permanently stuck in this "Turning on Wi-Fi" state. It seems to be working perfectly now, and we no longer see the "Optimizing..." message either when the phone reboots. Now I won't have to do remote tech support when she flies back home next week
tonemand said:
My mom has a Vivid and her phone has been doing this ever since the update was pushed down by AT&T. Since she lives 1000 miles from me, I didn't root her phone, and leaving it stock, the only thing that ended up working was a factory reset. The other thing that was happening after the update was every boot would go through the "Optimizing application 1 of x..." message like it does after the update. I get the impression that whenever she performed the mandatory AT&T update, something didn't go correctly, which is why her Wi-Fi was permanently stuck in this "Turning on Wi-Fi" state. It seems to be working perfectly now, and we no longer see the "Optimizing..." message either when the phone reboots. Now I won't have to do remote tech support when she flies back home next week
Click to expand...
Click to collapse
I think this is my next step. I tried flashing boot.img, but that didn't work. Does anyone have any other solutions short of this?
Bigluc said:
Ok I've googled around alot and looked on this forum but I can't find a boot.img anywhere that isn't modified. Can you point me to the stock boot.img?
Click to expand...
Click to collapse
There's a link to one in the thread for Kozmik Kernel.
Bigluc said:
After the forced AT&T software update, my WiFi will not turn on. I will go into WiFi settings, press the toggle button, and it will grey out and get stuck on "Turning on WiFi". I have tried wiping both caches, and I have replaced the bcmdcm.ko under system\lib\modules with bcm4330.ko, which was the one from the stock ROM. Nothing has worked and this problem persists. I am rooted and my bootloader is unlocked. Is there anything short of doing a full factory reset that can fix this problem?
Click to expand...
Click to collapse
it could just be a problem with the kernels, i was experiencing this even before the update.
Are you on a cusotm rom and/or custom kernel?
wifi will not turn on
y Rogers HTC Raider is unlocked and S-ON. I flashed MIUI 2.8.17 and now I can't turn on wifi, google play won't connect and I cannot boot into recovery mode, it just stays at he HTC screen. How do I fix this?
AshleyPem28 said:
y Rogers HTC Raider is unlocked and S-ON. I flashed MIUI 2.8.17 and now I can't turn on wifi, google play won't connect and I cannot boot into recovery mode, it just stays at he HTC screen. How do I fix this?
Click to expand...
Click to collapse
Did you install the kernel? If you're s-on you need to fastboot flash the kernel image.
Sent from my HTC Raider using xda premium
I'm trying to factory reset my HTC Desire C has it was feely slow, but I'm having trouble un-rooting the phone, Does anyone know of any way I could do this with my model please?
I've tried Quick Root but that just seems to get stuck removing the perm-root.
Thanks in advance.
I've attached the info of my phone, thank you.
mkkid28 said:
I'm trying to factory reset my HTC Desire C has it was feely slow, but I'm having trouble un-rooting the phone, Does anyone know of any way I could do this with my model please?
I've tried Quick Root but that just seems to get stuck removing the perm-root.
Thanks in advance.
Click to expand...
Click to collapse
You can do this: - lock bootloader
- power on device
- enable adb debugging on device
- make sure you have adb and fasboot working corectly
- connect device via usb to PC
- run RUU with administrator rights
- and from there on just follow the instructions given by software
- http://www.androidruu.com/?developer=Golf
you really need the 2-4 lines i mentioned up for this to work
Well I managed to lock my bootloader and that, but when i tried to install the RUU it gave me a error. I think it might be an older version.
I think I'm going to need the 2.00.771.3 version :S
I think my phone is useless now. A bit of info, I tried factory resetting my phone (I have rooted my phone prior to this and stupidly thought that factory reset would get rid of the root) but when I reset my phone after the inital setup had gone through all menus it said setup has stopped working. Then my phone wouldn't work no apps or home screen, I could recieve calls and then go onto my settings at the top but nothing more then that, I'm not sure how I can get my phone working again now lol
mkkid28 said:
Well I managed to lock my bootloader and that, but when i tried to install the RUU it gave me a error. I think it might be an older version.
I think I'm going to need the 2.00.771.3 version :S
I think my phone is useless now. A bit of info, I tried factory resetting my phone (I have rooted my phone prior to this and stupidly thought that factory reset would get rid of the root) but when I reset my phone after the inital setup had gone through all menus it said setup has stopped working. Then my phone wouldn't work no apps or home screen, I could recieve calls and then go onto my settings at the top but nothing more then that, I'm not sure how I can get my phone working again now lol
Click to expand...
Click to collapse
once it booted it not useless
try what i said with and without locked bootloader
if you need further help add me on fb
https://www.facebook.com/makerr00
Hi Everyone,
First off I am a total novice and I put my hands up to say I should not have tried to root my phone. I merely wanted to root so that I could actually use the space on my SD card, which the HTC Desire doens't.
I did try to do this manually by reading a few guide and walkthroughs with no success. So then I used the sunshine app to unlock my bootloader and then WinDriod to load TWRP recovery and then hopefully root the phone. It does say ***unloacked*** on the fastboot menu. However, I sort of messed up my phone.
I cannot load into recovery mode - it goes to a HTC load screen then right back to fastboot usb menu.
I cannot factory restore the phone either.
Can anyone advise me how to return my phone to its normal state or advise on how to fix this problem?
Appreciate any help anyone can give me!
bbop107 said:
Hi Everyone,
First off I am a total novice and I put my hands up to say I should not have tried to root my phone. I merely wanted to root so that I could actually use the space on my SD card, which the HTC Desire doens't.
I did try to do this manually by reading a few guide and walkthroughs with no success. So then I used the sunshine app to unlock my bootloader and then WinDriod to load TWRP recovery and then hopefully root the phone. It does say ***unloacked*** on the fastboot menu. However, I sort of messed up my phone.
I cannot load into recovery mode - it goes to a HTC load screen then right back to fastboot usb menu.
I cannot factory restore the phone either.
Can anyone advise me how to return my phone to its normal state or advise on how to fix this problem?
Appreciate any help anyone can give me!
Click to expand...
Click to collapse
Hello,
Since you asked for help with returning the phone to it's normal state I have some questions. Does the phone work normally? Can you make calls, text, and do other things when you simply power your phone on or is the OS deleted? Are you just referring to obtaining stock recovery or do you still want to get TWRP? It sounds like some error happened when you tried to flash TWRP and now you have no recovery. Here is a great guide that shows you how to flash TWRP. You can use that same guide to flash the stock recovery. That channel also has videos with an alternate method to unlock your bootloader and how to root the phone.
My phone works fine, makes calls, texts etc, I just can't boot into recovery. I tried several methods, following online videos etc to no avail, but ill give this one a go this evening. I mentioned returning it to its original state so I could start over with the flashing process as nothing seems to allow me to load into twrp, so i wondered if there was a corrupt file or something preventing me from doing so. The phone's bootloader is unlocked I believe as it says so on the hboot screen.
Thanks for the suggestion, ill let you know how it goes.
bbop107 said:
My phone works fine, makes calls, texts etc, I just can't boot into recovery. I tried several methods, following online videos etc to no avail, but ill give this one a go this evening. I mentioned returning it to its original state so I could start over with the flashing process as nothing seems to allow me to load into twrp, so i wondered if there was a corrupt file or something preventing me from doing so. The phone's bootloader is unlocked I believe as it says so on the hboot screen.
Thanks for the suggestion, ill let you know how it goes.
Click to expand...
Click to collapse
The method in that video should work perfect. I doubt there was a corrupt file, but we'll find out soon enough. I have a love/dislike relationship with WinDroid. I love it, because of how easy it is to use and it requires little to no knowledge of what you are actually doing and it is just a beautiful looking program. I dislike the fact that you pretty much learn nothing when you use it, as it does all of the work. Also, if you use the adb drivers it provides and you already have adb drivers, you will receive an error that the adb server is out of date.