Firstly I am sorry if this has been covered in the forums - however I did not bump into this query or issue yet nor was Google able to find anything like it.
A few months ago I attempted to root my HTC one x by using the HTC One X AIO Kit.
It did not work - the phone stated it was Rooted however I was unable to run any custom roms or specific Apps. It wasn't causing any issues and the phone was running stable though so I left it as it was.
A few weeks ago my provider released out a new update that would fix the consistent issue I had with Data over 3G but since the phone was rooted it would updated it for me.
So after searching around I figured "why not just factory restore the phone and apply the Stock Kernel (2.6.39.4)
That was this morning... since then the phone has been stuck in a boot loop.
Tried clearing cache and tried a few different walk through to get it up and running but to no avail.
I managed to get it to boot into the phone however I get no reception, no Wifi, unstable, and once reset will once again go back into a boot loop cycle.
Does any one have any suggestions on what I can do to fix this issue?
At the moment the phone is not being recognized by the PC by USB as well.
Thank you Developer Gods.
*UPDATED*
Well looks like its hard bricked!
FML - New lesson learned I guess.
So your phone won't turn on at all now?
Sent from my HTC One X using xda app-developers app
Try going into fastboot
Well its got be bloody confused.
It wont turn on and then sometimes it does and goes into the rom.
Rom is unstable though, doesn't pick up sim card - Wifi goes bonkers. In other words its corrupted as hell.
Go to charge it and it says it charges but doesn't (4% it sits on - leave it for an hour come back 4% is still there)
So there might be hope after all in getting this back up and running.
Scouring the net and forums now for something similar but nothing so far.
tomascus said:
So your phone won't turn on at all now?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Tried that as well just now since its somehow booting.
But again once in, cant flash it and PC still doesn't pick it up so I cant run any tools.
Also connect it by USB cable and it looks up in fastboot. Disconnect the cable and its fine again.
XxVcVxX said:
Try going into fastboot
Click to expand...
Click to collapse
Can you go into recovery?
Related
i am unable to connect to the mobile network and when i go into mobile network settings there are none. Anyone have any ideas on a fix for this please?
What software version?
What radio?
Is your phone rooted?
What network do you try to connect and in which country?
jpot1 said:
i am unable to connect to the mobile network and when i go into mobile network settings there are none. Anyone have any ideas on a fix for this please?
Click to expand...
Click to collapse
try to reinstall android
EdikNeznanov said:
try to reinstall android
Click to expand...
Click to collapse
are you on o2 or giffgaff? they are having issues right now.
help
virgin mobile usa
yes it is rooted with s-off
not sure which software as i cant check now
being a newb and having a impatient wife that wanted it fixed i thought i could just reflash the stock ruu to fix it however i got a 170 usb error and now the phone dosent work. I turn it on and just get the 3 vibrations with black screen. no recovery mode and pc dosent recognize it. now im in the doghouse lol
jpot1 said:
virgin mobile usa
yes it is rooted with s-off
not sure which software as i cant check now
being a newb and having a impatient wife that wanted it fixed i thought i could just reflash the stock ruu to fix it however i got a 170 usb error and now the phone dosent work. I turn it on and just get the 3 vibrations with black screen. no recovery mode and pc dosent recognize it. now im in the doghouse lol
Click to expand...
Click to collapse
F**k. That's not gone well buddy but! Ill do my best to help Ok so I think you have hot your device stuck in qualcomm diagnostic mode. Which isn't very good. But, some people have had some luck coming out of it when the device vibrates 3 times. Also since you are full s-off (I assume by xtc clip?) Then you may be in luck
Afaik the idea behind that mode is that the phone is doing things, but with no visual. So, if a recall correctly you can put a recovery that is flash able by BootLoader and it will flash it. But I think you should take your stock ruu, remove the rom.zip by using a process manager and then throw that on the root of you sdcard after renaming it pg76img.zip (I think that's the wfs code??) Boot the phone into BootLoader and wait for two or so minutes. We will assume that it has asked you to perform the sdcard update. Push volume up. That will hopefully make it install the rom ect and fix it up for you. But be careful and remember to RESEARCH this before you do anything. If I recall correctly their is a thread dedicated to this! Good luck man
Sent from my HTC Sensation XE using xda premium
mobile network help
thanks for trying to help)
I followed some guide i found using google to get s-off... atleast i assume it worked since on the phone it changed it from s-on to s-off.
I tried placing the zip on the sd card and waited 5mins hit vol up then 10 mins hit volum up again, then took out battery reinserted but just get three vibrates and blackscreen again on reboot.
Looks like virgin mobile replacing it may be my last hope ...
That's not good. Looks like it. Well, in theory your phone should be stock. So they can't refuse you on the grounds of you messing with it. Just say it stopped working and you don't understand or something like that.
Sent from my HTC Sensation XE using xda premium
Right i know ive posted before but i have had a lot more since i posted last and now im in another different situation
About a week ago i was running Hboot 1.28 along with ARHD 12.1(i think)
Randomly during the day changed my gmail account to a different email that went fine
Next i ended up having some random SuperUser commands asking me to do random things that had never seen before so i denied them and my phone was running as normally
Few hours later all my apps started crashing starting with process.com.gapps.process i think? and then everything else crashed
So i thought ahh its just my rom messing about so i wiped and then re-flashed (yes i installed the boot, and wiped properly and didnt install any tweeks) and as it booted up everything crashed and it reboots and bootloops
So i tried a few different roms to see if it would work and i got the same problem on EVERY rom i tired including ARHD MAXIMUS
So i posted on here and was told to reflash hboot up to the latest which i did at the time it was 1.31 and i still had the same problem even when i flashed the recovery boot image and new roms ect
I messaged football on twitter to find out when the latest RUU would be released and waited a few days to flash the latest RUU WWE for JB which was for my CID which is HTC_001 so i flashed that and everything went completely fine so i let my phone boot up and then the same problem happened
I then unlocked it again and left phone charging in recovery over night like i normally do
and now my phone is hard bricked im pretty sure i cant even turn it on?
any ideas?
Ok, so you can't turn it on? That's seems somewhat more important than changing your email account.
So you last had it in recovery (which one? CWM 5.8.4.0?) and it was charging? Then, some time later it was dead, right?
So when you plug it into a usb charger (give it 5 minutes) does the charging light come on? And what about a USB port?
BenPope said:
Ok, so you can't turn it on? That's seems somewhat more important than changing your email account.
So you last had it in recovery (which one? CWM 5.8.4.0?) and it was charging? Then, some time later it was dead, right?
So when you plug it into a usb charger (give it 5 minutes) does the charging light come on? And what about a USB port?
Click to expand...
Click to collapse
Aha, i cant turn it on as of today i changed my email account about a week ago
i had the latest CWM yes 5.8.4.0 and yes it was, and last night it is now dead and wont even turn on
I have tried wall charger i get nothing havent tried USB when i get back home in a couple hours ill give it another go and use the USB
Seems like a hardware fault, you can't hard brick an s on device
Sent from my HTC One X using xda premium
Stuar said:
when i get back home in a couple hours ill give it another go and use the USB
Click to expand...
Click to collapse
Can you hear input sound in windows when you plug it in? Does anything show up in device manager?
TToivanen said:
Can you hear input sound in windows when you plug it in? Does anything show up in device manager?
Click to expand...
Click to collapse
Right ive finally plugged it into my laptop and now i got the red light charging, i can now get into fastboot
Stuar said:
Right ive finally plugged it into my laptop and now i got the red light charging, i can now get into fastboot
Click to expand...
Click to collapse
Since you are already unlocked, try to install some ROM.
There has to be something wrong since the problem persists on every ROM.
You sure you wiped everything you can? SD-card also?
TToivanen said:
Since you are already unlocked, try to install some ROM.
There has to be something wrong since the problem persists on every ROM.
You sure you wiped everything you can? SD-card also?
Click to expand...
Click to collapse
I haven't done the SD card, so ill give that a try, so wipe SD card first then put rom ect back on the sd card, then preform full wipe
also wipe using computer or recovery?
Flash the boot.img. enter recovery, perform a full wipe there, install the rom.zip
I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!
In case of emergency!
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.
Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download
Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing
Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!
http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2
Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.
Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.
I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app
There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.
The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!
Do u guys have the most up to date version of whatever particular recovery that you're on?
Yep. I've flashed the stock recovery multiple times to no avail. :/
nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?
wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/
nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?
wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!
My brother got HTC Desire 816 a month ago.
He found OTA Update and he installed it and when phone was updating he noticed that phone stuck on htc logo.
He keep waiting for almost hour to see if it is finished or not, but ???
Well i am using ATrix 2 and i suggested him to go to recovery and try for system restore. But still no luck.
Phone was above 65% and wifi connection was proper that time. I don't know what went wrong?
I Google regarding this and searched in xda also, for same, but i didn't find anything helping.
Can any one help me regarding this.
Gr8mobiPro said:
My brother got HTC Desire 816 a month ago.
He found OTA Update and he installed it and when phone was updating he noticed that phone stuck on htc logo.
He keep waiting for almost hour to see if it is finished or not, but ???
Well i am using ATrix 2 and i suggested him to go to recovery and try for system restore. But still no luck.
Phone was above 65% and wifi connection was proper that time. I don't know what went wrong?
I Google regarding this and searched in xda also, for same, but i didn't find anything helping.
Can any one help me regarding this.
Click to expand...
Click to collapse
This is the second case so far I came across that has issues with updating OTA on HTC desire 816. May I please ask whether it was rooted and xposed module installed ? If not, the only way is to look for a custom rom or else, install the custom recovery (if your brother can manage to boot into fastboot mode) and restore from the cwm backups floating around in xda. @jithumon has the indian backed up version, which will allow you to get your phone back alive, if not already is.
vbrsekhar said:
This is the second case so far I came across that has issues with updating OTA on HTC desire 816. May I please ask whether it was rooted and xposed module installed ? If not, the only way is to look for a custom rom or else, install the custom recovery (if your brother can manage to boot into fastboot mode) and restore from the cwm backups floating around in xda. @jithumon has the indian backed up version, which will allow you to get your phone back alive, if not already is.
Click to expand...
Click to collapse
His mobile is not rooted, even he is not technical person at all.
Yeah! he was able to go to fast boot mod by pressing volum and power botton. He also managed to hard reset. But no luck. Fiinally he returned the phone to ebay. He will be gettiing his phone by 5th september (hopfully). The thing is phone is almost new (~1 month old). So neither he noe I wanted to take chance.