Related
I installed the Htcweatherdll.cab and my phone restart and now it doesn't not stop restarting. Is there a way to fix this?
Thanks
deizol1 said:
I installed the Htcweatherdll.cab and my phone restart and now it doesn't not stop restarting. Is there a way to fix this?
Thanks
Click to expand...
Click to collapse
Something similar to this happened to me, and a hard reset wouldn't work. I had to send it back to AT&T. Sorry man, hope you have better luck than I did.
deizol1 said:
I installed the Htcweatherdll.cab and my phone restart and now it doesn't not stop restarting. Is there a way to fix this?
Thanks
Click to expand...
Click to collapse
have you tried a hard reset, press down 2 softkeys and stick in reset button and release before letting go of the 2 soft keys. then follow on screen instructions ?
more info needed though ie can you access the bootloader, have you previously put a hard spl on your phone and if so which version.
god reading here on how to get phone back up and working http://forum.xda-developers.com/showthread.php?t=423486 and here too
i have the version from att
Ok now I got it to stop restarting but now its stuck
deizol1 said:
i have the version from att
Click to expand...
Click to collapse
From your response I'd say your best option if a hard reset does not work would be to see if you can access the bootloader screen ( press camera button and soft reset ) it looks like three colours on your phone. If you can then download an original rom for your phone and follow the instructions to place it on your phone.
Anyone have any better idea's
back in an hour let me know how you got on
That's the only conceivable idea probably. After you go into bootloader mode, flash the stock ROM and then if you have hardspl, install the custom ROM that you prefer.
Well i guess i can kiss all my #'s goodbye...you know what.....I think I want a custom rom...anyknow know where i can go to get a good one
deizol1 said:
Well i guess i can kiss all my #'s goodbye...you know what.....I think I want a custom rom...anyknow know where i can go to get a good one
Click to expand...
Click to collapse
You should always have your PIM either backed up or on your SIM.
Look in my sig for your request.
deizol1 said:
Well i guess i can kiss all my #'s goodbye...you know what.....I think I want a custom rom...anyknow know where i can go to get a good one
Click to expand...
Click to collapse
Dont go custom yet mate, try a stock rom and get it up and running first. Then take your time to read about soft / hard spl's and radios etc before diving in with a full custom rom. Believe me its worth it to understand everything first
AND READ THIS FIRST http://sakajati.com/forum/index.php/topic,3.0/prev_next,next.html#new
Thank you guys for your help....I downloaded the att rom from the htc website and i got my tilt running like new.....and I got all my #'s back ...looks like outlook does a good job hehehe
Time machine
deizol1 said:
I installed the Htcweatherdll.cab and my phone restart and now it doesn't not stop restarting. Is there a way to fix this?
Thanks
Click to expand...
Click to collapse
DOWNLOAD timemachine.cab, go back a few days, and don't make the same mistake.
Why do we get so many lame, I broke my XXXX because I'm a dolt, and expect the world have some magic panacea.
It really pisses me..
Sorry rant over.
Maybe I just hate kids, now where did I leave that gun....
I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.
Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.
Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick
Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App
Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G
Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.
You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.
Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed
Hi,
Im after a little help,
i can put my phone into bootloader mode and have access to twrp but i can't seem to write anything over what i have, i have tried to flash a new recovery and rom but it says it has successfully written but when i reboot nothing has changed, i have no rom on there and cannot flash a new one, the phone just reboots and loads twrp,
please help me get my phone back
Windows 7, adb, working htc drivers and then flash firmware with recovery twrp 2.3.3, get it from sneakyghost topic
can be other system but its easy with 7
Sent from my HTC One using Tapatalk 2
tried that
Thanks but i have tried to do that on my Mac and windows 7 pc but nothing seems to be working,
i can go to bootloader and type fastboot flash recovery..... but it says it has written everything ok with no errors but when i load recovery on my m7 it is the old one with nothing changed,
i can't restore a backup either as it crashes and reboots part way through :<
any help would be greatly appreciated,
i had same problem few months ago it must work
try with other firmware
Sent from my HTC One using Tapatalk 2
fanbogo said:
i had same problem few months ago it must work
try with other firmware
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
cant boot ruu mode, just crash and restart to twrp,
thanks for your help but i'm losing hope, :crying:
tigsandmitch said:
cant boot ruu mode, just crash and restart to twrp,
thanks for your help but i'm losing hope, :crying:
Click to expand...
Click to collapse
Sorry to hear that, seems your device is bricked like mine. I bought another htc one but i still wish i could fix my first one. Have a look here:
http://forum.xda-developers.com/showthread.php?t=2685024&page=3
darksnoopy said:
Sorry to hear that, seems your device is bricked like mine. I bought another htc one but i still wish i could fix my first one. Have a look here:
http://forum.xda-developers.com/showthread.php?t=2685024&page=3
Click to expand...
Click to collapse
thanks for the link, my device isnt even s-off and never has been, so to mess up this bad without s-off scares me,
i have the new M8 on the way and should be with me tomorrow so im not too upset just kinda makes me a little hesitant about flashing in the future.
i will keep an eye on here to see if there is any way to fix and the link you provided,
thank you again,
Dear Nexus 6 users
Please save my ass and help me debrick my nexus 6. I rooted my N6 the day I got it, flashed multiple ROM and everything was working perfectly I was playing sim city and my phone suddenly switched off tried starting it but it only showed 2 secs of the boot screen and switched off.
I booted to TWRP and tried flashing another ROM but it for some reason TWRP couldn't see my storage so i decided to flash stock downloaded the WUG nexus tool and BOOM now I have a nice brick.
It doesn't boot into recovery or even show the google sign but BUT it says QHSUSB_BULK when I connect it to my PC, shipping back would be damn near impossible since I live in Egypt, lets just keep it as a last resort soooo any ideas? thanks you for your time.
ahmad.magdy said:
Dear Nexus 6 users
Please save my ass and help me debrick my nexus 6. I rooted my N6 the day I got it, flashed multiple ROM and everything was working perfectly I was playing sim city and my phone suddenly switched off tried starting it but it only showed 2 secs of the boot screen and switched off.
I booted to TWRP and tried flashing another ROM but it for some reason TWRP couldn't see my storage so i decided to flash stock downloaded the WUG nexus tool and BOOM now I have a nice brick.
It doesn't boot into recovery or even show the google sign but BUT it says QHSUSB_BULK when I connect it to my PC, shipping back would be damn near impossible since I live in Egypt, lets just keep it as a last resort soooo any ideas? thanks you for your time.
Click to expand...
Click to collapse
Can you go to fastboot menu? If so then flash the stock image
SAW_JOK3R said:
Can you go to fastboot menu? If so then flash the stock image
Click to expand...
Click to collapse
No, I can't
@Ahmed http://forum.xda-developers.com/showthread.php?t=2575712 it seems some kindles have had this issue. You may want to read this.
BxingFetus said:
@Ahmed http://forum.xda-developers.com/showthread.php?t=2575712 it seems some kindles have had this issue. You may want to read this.
Click to expand...
Click to collapse
Thank you will differently try it when I am home.
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Same issue here. I flashed a stock image and something must've gone wrong at some point
hamzahrmalik said:
Same issue here. I flashed a stock image and something must've gone wrong at some point
Click to expand...
Click to collapse
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
ora69 said:
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
Click to expand...
Click to collapse
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
ora69 said:
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
Click to expand...
Click to collapse
Oh ok I get you. Mines USB bulk 9000 or something i can't remmeber now
Sent from my A0001 using Tapatalk
ora69 said:
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Click to expand...
Click to collapse
So that link to another thread in XDA forum, I think I had a similar experience. I too have the XT1072 as I live in the UK. now here on XDA you have to be careful and ask 3 4 maybe 5 times before someone listens properly. I know it is hard for the devs with so many dumb noobs asking so many dumb questions, I include myself as a noob so no worries. Anyway to get to the point that link is not referring to our phone the XT1072. You should ignore LTE in your search criteria, it will always point you towards the 2015 model and believe you me all roms in my experience area very device specific. You need to simply put Moto G 2nd gen 2014 in search criteria when it comes to searching for custom recoverys and/or stock ROMS. The Titan.IMG is always a safe bet if I remember correctly, dont take my word for it, I have been known to have a memory like a sieve now and again, the problem with getting older, cache gets smaller and smaller, lol! Best of luck!
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Read the beginning on this article: http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
the bricked term is a common misconception for phones that still turn on..