Rooted adb shell, was on Modaco 1.3 for three months with no problems.
Ok, so today I wiped all & SD card, flashed to Fresh 2.0d, again no problems. Flashed the Vanilla lock screen fix #3 (deleting the HTC clock). Ok stupid me, I like the HTC scene/weather battery eater clock.
Realized I wanted the clock back, so I went into Flipz Kitchen and attempted to push back the stock clock. My phone froze, blank black screen, charging light on. Left it that way for a while, then felt the phone & it was hot-hot-hot, so I disconnected it and the charging light stayed on until I pulled the battery.
Tried a reboot; no go. Gets past the "Fresssshh" sound, quietly brillant screen; hangs at the HTC screen. I went to try my nandroid and found that everything has been wiped. Everything!!!
Ok, so I made sure everything was totally wiped... again. Got Fresh back on the SD Card. Attempted to reflash the zip and it said all was fine. But still hung at the black HTC boot up screen.
WTF? Never before used the Kitchen before tonight, but everything seemed ok before this happened. I admit, I'm not the brightest blub in the bunch but I can take direction real well. Please help; I gotta a conference call bright and early and need ANY kind of workable ROM. Really don't care which at this point.
jedijackie said:
Rooted adb shell, was on Modaco 1.3 for three months with no problems.
Ok, so today I wiped all & SD card, flashed to Fresh 2.0d, again no problems. Flashed the Vanilla lock screen fix #3 (deleting the HTC clock). Ok stupid me, I like the HTC scene/weather battery eater clock.
Realized I wanted the clock back, so I went into Flipz Kitchen and attempted to push back the stock clock. My phone froze, blank black screen, charging light on. Left it that way for a while, then felt the phone & it was hot-hot-hot, so I disconnected it and the charging light stayed on until I pulled the battery.
Tried a reboot; no go. Gets past the "Fresssshh" sound, quietly brillant screen; hangs at the HTC screen. I went to try my nandroid and found that everything has been wiped. Everything!!!
Ok, so I made sure everything was totally wiped... again. Got Fresh back on the SD Card. Attempted to reflash the zip and it said all was fine. But still hung at the black HTC boot up screen.
WTF? Never before used the Kitchen before tonight, but everything seemed ok before this happened. I admit, I'm not the brightest blub in the bunch but I can take direction real well. Please help; I gotta a conference call bright and early and need ANY kind of workable ROM. Really don't care which at this point.
Click to expand...
Click to collapse
The kitchen doesn't support Android 2.1 yet and is only for 1.5. Just reflash Fresh 2.0d on top of itself in RA and you'll be good to go. You may need to wipe again.
Ah crud I'm sorry Flipz, I did read that but I was stupid thinking that I could use it to push back Sprint Navigator and customize themes and stuff. My bad.
Took me several wipes, but Fresh finally worked. My total bad.
Hey Flipz, man thank you a bunch for the super-quick response back. Damn you're good!
Related
So today I was happily playing on the phone. I decided to apply the BSB tweak for LED on message notification.
It asked me to do a soft reset which I did and then it wouldnt turn on.
As well as that, for some reason my outlook calendar on PC deleted all my appointments.
Right now though the phone is just showing the white HTC screen, I can get into boot loader I think. I even tried hard reset.
I'm going to try installed the stock o2 rom I had from the sd card. Hopefully it will delete the HSPL and I can send it back.
Fingers crossed.
This is really crap though, this shouldnt really happen to the damn phone. I love the thing and I've defended it but come on. I just need a working phone that's all.
Okay so basically Im doing what I said, I've followed the step 4 from the HSPL thread.
WHAT THE HELL, the update is in progress and then the screen shut off and i got a triangle and an exclamation mark.
The screen has turned back on and going back into the installation.
It said its installed the radio v2- ok Rcust - ok, bootloader - ok, splash1 - ok its just installing the OS.
You can tell Im ****ting my pants, I've never bricked my phone before especially since this is messing up the warranty. At least I have insurance I could always say it got lost.
Okay the OS is installing still.
Hasn't anyone else had this problem? I only came across one thread but they sent it back and they didnt mess about with HSPL or anything.
Okay, Im back on the O2 Rom. I might send this back anyway.
OK I have G1 T-mo, it was on stock 1.6.
Yesterday I followed carefully the instructions on http://forum.xda-developers.com/showthread.php?p=5214290#post5214290
the ultimate beginner guide:
I downgraded the G1
Then rooted it and used Amon Ra recovery
Installed the Cyanongen Mod
Flashed the Radio and SPL
Then I used the new Super D with the arabic support
All was great, except the market was not downloading anything.
Kept using it today, then when battery was getting drained I plugged it to the wall and was browsing the news... Suddenly I got the Boot screen, so i selected the ''press menu'' to shut down.
tried to reboot normally, got some lines on the screen, then a white screen then nothing at all
It doesn't boot, doesn't turn on the LED if i plug it in the wall... tried all the back and end, camera and end etc nothing working
is it totally dead? what can be the reason?
it was working perfectly well and really fast since yesterday with all the EXT3 and sawp etc!!
any ideas?
thanks
As long as you can boot into the recovery menu then your G1 is not dead. The ROM probably just went bad somewhere.
I recommend you to use Cyanogen until Super D gets sorted out. I was on the latest Super D and that was soooo slow and laggy that I just wiped and went to Cyanogen.
I can't log to recovery screen! it stays black screen no matter what i press!
Your phone's dead. There's nothing anyone can do for you. Send it in for warranty, or buy a new phone.
ok even if it is dead, can some one please help me to understand what/what happened?
I mean all the installation and flashing etc went well and the mobile was perfect for 24 hrs!
hendfarid said:
ok even if it is dead, can some one please help me to understand what/what happened?
I mean all the installation and flashing etc went well and the mobile was perfect for 24 hrs!
Click to expand...
Click to collapse
Did u overclock it?
one thing you can try is switching battery, if you have a spare or a friend that has a g1 use their battery real quick.. i had a similiar problem.. phone would stay black but an off-black color like it was trying to light up, charging indicator wouldnt light up either while it was plugged.. nothing booted, got another battery and it worked.. now i have a 2800mAH =)
Hi,
No I didn't overclock it.
My G1 stays totally black, no back light, no feedback when i try to start it either! I will try to look for a battery
Keep it official
You should of just used the official release of Super D from bbuchacher.
http://forum.xda-developers.com/showthread.php?t=613809
It would have saved you alot of headaches right now.
Since I first flashed the Super D Rom I knew I wasn't going to change it for anything else for the life of my G1.
Hopefully someone can help you with your issue, like someone else said maybe its your battery.
Sounds like a hardware issue of some sort. Original battery?
Thanks I do wish it works, if it does I will move to the original Super D, it was very fast (with the Arabic text and applications)!
Yes it is the original battery, I will try and find one to test it with.
I wish it will be the battery and bad luck that it died after the new Rom
I was using my aria as a router using the 2.2 rom. I was IMing people and my sister was watching youtube videos on another computer. After awhile my phone became very hot but it still worked fine so I thought it was okay. Then all the sudden I got disconnected so I saw that my phone had rebooted into clockwork recovery. When I clicked reboot it went to a grey screen for a few seconds then back to clockwork recovery. I decided the phone must have tried to shut it off because it had become too hot but couldn't because it was plugged in and when its plugged in it goes to clockwork recovery. So then I decided I really wanted to talk to my friends so too cool my phone down I put it in the freezer. Yeah, that was stupid. Because now it will not get past clockwork recovery.
When I try to reboot it just flashes the led orange and goes to a dark grey screen for a few seconds then back to clockwork recovery.
Clockwork recovery only shows up when its plugged in and when I try to press the power button when its not plugged in nothing happens.
I tried clearing cache, davik cache and clearing battery stats in addition I reflashed the ROM and it still does the same thing.
UPDATE:
Wow I was a little too quick to head onto trusty XDA and make a post. It works fine now after I unpluged it and waited a few min.
"I really wanted to talk to my friends so too cool my phone down I put it in the freezer."
That is damn funny.
Never mind, glad to hear your up and running.
Sent from my HTC Liberty using XDA App
Back in the old days, when DVD players first came out, I had one that would not play an entire movie because it would overheat. I used to put an ice pack on the top of it to play movies. Worked like a champ.
Nothin' wrong with putting the phone in the fridge to cool it down... I wouldn't put it in the freezer... glass can crack when it undergoes a rapid temperature change. Either way, cooling it too much will likely kill the battery (requiring it to come back to room temp and be recharged).
I just installed the OTA update for Gingerbread on my (non-rooted and totally stock) Droid X.
When the main screen came back up after the installation I was unable to manipulate my screen (i.e. slide, open anything). When I hit the power button (short tap) the screen went black but does not come back on. The only way to reset was removing the battery. It booted fine, came to the home-screen, but then the same problem--can't move or open anything and then the screen goes black.
Please advise what you think I should do to fix this? I'm so bummed and would love your help.
TIA
dchay said:
I just installed the OTA update for Gingerbread on my (non-rooted and totally stock) Droid X.
When the main screen came back up after the installation I was unable to manipulate my screen (i.e. slide, open anything). When I hit the power button (short tap) the screen went black but does not come back on. The only way to reset was removing the battery. It booted fine, came to the home-screen, but then the same problem--can't move or open anything and then the screen goes black.
Please advise what you think I should do to fix this? I'm so bummed and would love your help.
TIA
Click to expand...
Click to collapse
Boot into recovery and do a factory reset.
Thank you for the suggestion but I'd love to save the wipe option as a last resort. Are there any other options?
I noticed in the recovery menu it has the option to apply update from the sd card. Do you think Verizon would be able to re-apply gingerbread via the SD card and save me from re-formatting?
Mine seems to be solved.
Apparently, it really did require me to pull the battery 7-8 times, reboot 15 times, and then let it sit. For some reason, though, now it's working and it's like it never went wrong.
Not sure what kind of update needs to sit and soak but apparently this one did.
Meanwhile, a friend sat next to me and updated his effortlessly. Luck of the draw for me, I guess.
It probably was something with your data, that is why it is always recommended to make backups
I've had this Motorola Droid RAZR for like two years now and a friend of mine took it and worked on it, adding something called "Cyanogen Mod" and he 'rooted' it I believe? Ever since, phone has worked great. However, today I tapped the home button and the whole screen had a weird visual glitch where the wallpaper was entirely intact but the icons and such were only half appearing, like someone scratched them out with fingernails or something. It would go away and come back so I got frustrated and rebooted my phone. It starts up normally and goes to this screen where you can do different stuff with Cyanogen mod (like changing the rom? or changing boot options) and usually I just continue past that because for 1) I know nothing about it and 2) It always was fine. But when it did the typical boot up, it just skipped back to the first screen you get when you turn the phone on and repeats. It never goes to the second part of the Cyanogen Mod where the words appear and the little thing spins, it simply skips back to the screen you get when you power up and repeats. It keeps doing this and I looked online how to fix it, tried about twelve different things (like restoring different aspects and using different roms or making new roms) and it just didn't work. Eventually it got bugged out where the screen was just black, couldn't get it to do anything but reboot and go back to black. I let it sit until the battery ran dry I believe and now I'm at a brick wall.
Is there a way I can totally just revamp and start fresh? Like remove all of it and reinstall Cyanogen mod/the OS and all that jazz? I don't mind losing everything if I can just keep the phone, I don't pay for a cellphone and I don't want one I just use the droid for texting apps/games/reddit/etc. If anyone could help me save this thing I'd appreciate it.
Hi there,
Please stand by until mods will move this thread to the related forum for Droid RAZR.
For reply or ask other questions you must register an account.
Stand by
Hello? Can Somebody help me out, I've waited a couple days now and no one has said a thing?
You have safestrap installed, correct? If so, what version?
Dr. Mario said:
You have safestrap installed, correct? If so, what version?
Click to expand...
Click to collapse
How would I know if I had it installed? I remember when I booted up the phone something came on with a picture of a little robot that said "Safestrap Enabled" and then when I had this problem it was saying "Safestrap Disabled". I can't get the phone to turn on right now though, is there a way I can check what version I have another way?
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Dr. Mario said:
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Click to expand...
Click to collapse
Just tried booting it up, nothing is working I think the phone is dead. I plug it into the charger and only the notification light on the top left goes on a blueish white and stays on as long as it is plugged into the charger. Nothing will turn on at all and the phone doesn't seem to respond to anything. Is my phone just dead..?
Soft bricked. Try pushing both volume down and up button while plugged into either computer or charger, and hold down power button until it boots. I hope you won't need to buy Motorola factory cable at this point.
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
ATTACK said:
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
Click to expand...
Click to collapse
In English please?
Edit: Just plugged it in like you said and instantly the boot screen came on rather than simply that silly light so I think my phone is improving but I still would like to entirely revamp it or redo it or whatever you wanna call it so that everything is fresh and new and my phone is okay.
Good. I think it could be because the battery died somehow. Good thing the protection mechanism on the bootloader didn't have the wild idea of disabling the phone.