Related
I just tried to use this method on my Inspire today and there was an error when flashing back to the stock AT&T ROM after gaining S-OFF and root. When I try to start up the phone normally, it gets stuck on the HTC screen. When I try to boot into recovery, it just shows a black screen while the LED is green.
Anybody know what I can do to fix my phone?
xr2unitx said:
I just tried to use this method on my Inspire today and there was an error when flashing back to the stock AT&T ROM after gaining S-OFF and root. When I try to start up the phone normally, it gets stuck on the HTC screen. When I try to boot into recovery, it just shows a black screen while the LED is green.
Anybody know what I can do to fix my phone?
Click to expand...
Click to collapse
which root method did you use?
I used the one click root method.
xr2unitx said:
I just tried to use this method on my Inspire today and there was an error when flashing back to the stock AT&T ROM after gaining S-OFF and root. When I try to start up the phone normally, it gets stuck on the HTC screen. When I try to boot into recovery, it just shows a black screen while the LED is green.
Anybody know what I can do to fix my phone?
Click to expand...
Click to collapse
Here you go...
http://forum.xda-developers.com/show...8#post12393978
SNadler said:
Here you go...
http://forum.xda-developers.com/show...8#post12393978
Click to expand...
Click to collapse
Sorry your link doesn't seem to work.
If you press the down volume and hold power can you get to hboot?
Try using bubby's tool to fix the CWM black screen. Its under the fixes link.
I can't seem to access any sort of recovery or hboot. Holding down both volume buttons and turning the phone on will result in the black screen with green LED. Holding the down volume button and turning the phone on does nothing.
xr2unitx said:
Sorry your link doesn't seem to work.
Click to expand...
Click to collapse
Sorry go to Bubbys super one step and search for CWM black screen....
If it helps, the phone vibrates 5 times then shows a black screen.
Well I was able to get into HBOOT but when I tried to go into recovery, the screen would just turn black.
You need to get the stock rooted PD98IMG.zip into the root of your sd card. Then go to hboot and let the phone find it. Follow on screen instructions. Note the progress bar will be vertical on upper right. I bet that fixes you up on getting the phone working. Black screen on cwm is a whole nother issue. One that I share. I think I'm going to revert to stock unrooted and then our attn1 hack kit.
There is a solution you can eng s-off, but I would not advise this there is no need to eng s-off your phone.
The simplest way though it may take longer is to, revert to stock and reroot and s-off with the hack kit.
This is a very common problem with the one click. To be honest there is a thread made just like this twice a day.
Thanks for all the help everyone. I managed to fix everything on my phone. I just flashed the rooted AT&T stock ROM with HBOOT and then used the one-click ENG S-OFF method to fix the black screen on CWM. Now running CM7 perfectly. I'm glad I no longer have to send it back to AT&T.
kinder gentler XDA i guess. Last year posts like these would have been flamed right off the board. Thats not a bad thing, but new people are wasting everyones F'ing time with these posts.
RTFM! w/e it is you decide to do , how about looking for help in the dam thread you downloaded the stuff from? I duno maybe we have a bunch of people brand new to Forums or something.
Ok I don't mean to thread jack, I just didn't want to start a new thread for this. I've been running the Coredroid Rom since I first rooted my phone. I have never had any problems with my phone even when trying out other roms. Today I tried installing the new Coredroid 5.0. It all went well as usual except this time on the last step of the setup wizard, it said something like "setup has stopped working unexpectedly and will notify HTC" and only let me press ok to force close.
After that happened all I couldn't even go to my home screen. I then tried restarting my phone but got stuck on the Coredroid rotating logo. Only way out of that was to pull the battery cover. Tried going into recovery mode but the screen would just be black and I would have the orange light flashing. That didn't work so I tried restarting again. Again just got stuck on the spinning logo.....This is where **** gets weird. I began to receive a call while on the logo and that allowed me to answer thus leaving the spinning logo. I still could not go to my home screen. I could only use the drop down notifications menu. I restarted my phone again so I could call myself while on the logo and again it got me unstuck from the logo. Only way to fix every thing was to use the search option and run Rom Manager and recover from my previous back up.
So I was wondering if this has happened to anyone else? I always fallow instructions and hardly ever have any problems but this was just odd. I felt like I had to solve riddles in order to get my phone working again.
See if you can boot to bootloader by means of ADB (adb reboot bootloader). If so reflash the stock rooted rom then reload CWM. You might need to Eng-S off if you have a corrupt file / bootloader? When done reflash CorDroid 5.0 (What I am running by the way)....
black htc screen
I tried to root my phone like an idiot because I dont know anything about this stuff and I got a black htc screen and i cant do anything. HELP!!
I see a lot of motivation in this and other threads to leave well-enough alone. Going to leave mine unrooted-stock.
I just had an excellent session of Google Nav where it performed exemplary. My phone does all I need and remains within the rules as the OEM wants it.
kadukasan said:
I tried to root my phone like an idiot because I dont know anything about this stuff and I got a black htc screen and i cant do anything. HELP!!
Click to expand...
Click to collapse
check out this thread --> http://forum.xda-developers.com/showthread.php?t=1019868
I don't have a history of random reboots other than the once in a blue reboot because the browser gets stuck. I was using my Xoom last night before going to bed checking out a couple of website. I laid it down and went to bed and this morning I just put it in my bag and left to work.
The Xoom doesn't get past the Motorola logo and then the screen dims a black-blueish tint as if it were on but not on. I booted into recovery and tried to do a nandroid restore to a prior date. The restore finishes but when I reboot the Xoom still has the same issue.
The last thing I downloaded on the Xoom was that new market but I didn't like it so I uninstalled it. Right now the Xoom is plugged in charging. I don't believe it's the screen because I'm able to navigate through recovery without it shutting off. I'm stuck. What could it be?
By the way I pressed Vol Up + Power to force reboot and it's not working. Still a blackish blue tint screen.
Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?
fleury14 said:
Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?
Click to expand...
Click to collapse
Not for nothing but you're thread jacking.
Not trying to. Just didn't want to litter with a whole new thread.
Sent from my Nexus S 4G using Tapatalk
It's cool but my Xoom is still dead
I'm going to try and do the update.zip for 3.2 after class and see if it boots up with that. This sucks.
Sent from my PC36100 using XDA App
Update:
I downloaded the 3.2 update that's in the development section and installed it. It still won't boot past the Motorola logo. It goes to the Motorola logo and then the screen turns blackish blue. If I hit the power the screen goes black. It was working g fine yesterday and I'm out of ideas.
Sent from my PC36100 using XDA App
Try going back to the beginning. Flash stock 3.0 and lock. If your xoom boots then you're back in the game. If not, at least its stock to send in for warranty repair.
Sent from my HD2
That will have to wait until tomorrow. What could have caused it?
Sent from my PC36100 using XDA App
Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2
jase33 said:
Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2
Click to expand...
Click to collapse
I hope it's not an issue with my screen. I just find it weird that the screen shows that weird tint and if I hit the power button it goes black. It's as if the tablet is on but I'm not seeing an image on the screen. When I did a nandroid restore it got past the Motorola logo and went into the next phase (boot animation). It froze on the boot animation within 1 second of entering it. I left it alone for 30 minutes and it didn't do anything.
I don't want to send it back to Moto because G-D only knows when I'll get it back. Does anyone have experience with their repair ETA's? I'm nervous on sending it in because I read a thread where some Xoom owner got accused of having water damage. I don't want to them use that as an excuse so they won't fix it.
I have no personal experience. But there were a couple of posts in the General section (April, May time frame) from users who sent there Xoom to Moto for repair. All reported outstanding service. Call Motorola customer service and they will send you a shipping box overnight. Turn around in most cases was only 2 days. All had their devices back in under a week (departure to return). Good luck. Won't hurt to call Moto and talk to them about it.
Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.
gqstatus0685 said:
Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.
Click to expand...
Click to collapse
You didn't use an app like screen off and lock did you? I had a problem with that app after the update...at one point my screen went completely black, I could see my soft keys and could access settings but that was it. Had to boot to recovery and wipe all over again.
It's a long shot but sometimes apps that behaved before an update can act whacky.
No nothing like that. I remember I was watching some YouTube videos and ended my night. The last thing I downloaded was the new market but it looked hideous so I removed it. I'm trying different things and I can't get it to work.
Sent from my PC36100 using XDA App
I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App
Oxirane said:
I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.
Wipe, wipe, repeat!
This most certainly is a software issue. The fact alone that the device is showing the boot logo proves that the screen is functional. Sounds like a boot img problem.
I have had similar issues on a few occasions with my Evo, doing a full wipe and restore has always done the trick as has been posted above.
Good luck Gq.
dhemke17 said:
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.
Click to expand...
Click to collapse
Thanks for the advice. I was too busy yesterday (Full Time Work and Student) to fix it. I will try today since I don't have class. I really want to see what caused the problem so I will try that command in CMD and will post the output on these forums. Hopefully a dev can use it in the future to prevent this from happening to someone else.
I miss my Xoom.
I'm assuming I would CD to the directory and then run that command, correct?
Ok I guys I included the attachment so maybe someone can tell me what's wrong with my Xoom.
When I ran that command in command prompt a debug window popped up. Let me know if the attachment makes sense.
Uncaught Exception most likely has to do with software as I remember fixing Blackberry's that always had those issues but I could be wrong.
Update:
I followed this thread
Re-Lock & Unroot
http://forum.xda-developers.com/showthread.php?t=1084537
and everything successfully pushed. I ended up getting an error messaage in fastboot (Failed image SOS 0x0002) so I decided to unlock the device by running fastboot oem unlock command. It completed successfully and got rid of the error message in fastboot. When I hit reboot it got past the Motorola logo and froze at that honeycomb animation (right in the beginning. I turned it off and turned it on again and now it won't go past the Motorola screen.
I went on a chat with Motorola and they will be sending me an email so I can send my Xoom for repair. I'm going to lock it again and send it back. I'm giving up unless anyone recommeds something I can try.
I know this title comes up a lot but I can't seem to find my problem.
I wanted to go back to the stock rom and I used the proper RUU but totally forgot to use the S-ON tool before hand. It installed successfully but now I get a solid amber light and so far I got my inspire to boot once only to get stuck on the splash screen with it vibrating non-stop.
And now it just vibrated once, went to a black screen and then shut off. I really don't know what to do since I can't even get to HBOOT nor will the computer recognize it.
I've done numerous batter/sim card pulls as well as clean them out.
Any help would be greatly appreciated
Have you tried booting into the bootloader and doing a factory reset?
Sent from my Inspire 4G using XDA
I think he was referring to the bootloader as HBOOT. I had this problem while rooting my sisters Inspire. Might be a corrupted bootloader.
Sent from my Inspire 4G using xda premium
lay012 said:
I think he was referring to the bootloader as HBOOT. I had this problem while rooting my sisters Inspire. Might be a corrupted bootloader.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Last I remember my bootloader was TWRP which I guess I had accidentally installed somehow. If you think its a corrupted bootloader how would I go about solving this, if there is a solution?
moutansos said:
Have you tried booting into the bootloader and doing a factory reset?
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
Never do a factory reset on a S-OFF device....it will jam u up.
greggyt79 said:
Last I remember my bootloader was TWRP which I guess I had accidentally installed somehow. If you think its a corrupted bootloader how would I go about solving this, if there is a solution?
Click to expand...
Click to collapse
It seems that the RUU you flashed was a Froyo one and your phone was running GB so you messed the bootloader. Hit the Hack Kit IRC channel (is in the OP thread) and we will lend u a hand to fix that....
Alright so I went to the IRC and they told me they couldn't help because it did not deal with the hack kit, fair enough.
I have been able to get the phone to boot after waiting for about 10 minutes but I cannot get to the bootloader. I tried rooting the phone again this way I can turn s-on then flash the stock rom again but the phone ends up not being detected half way through the process.
I really don't know what else to do...
Forgot to mention, now my inspire boots but then fades to a greyed out screen. My computer recognizes the phone as something occupying the usb port but is not accessible. Wish the phone had a physical reset button somewhere that i can poke with a paperclip...
Sent from my SAMSUNG-SGH-I897 using XDA
greggyt79 said:
Alright so I went to the IRC and they told me they couldn't help because it did not deal with the hack kit, fair enough.
I have been able to get the phone to boot after waiting for about 10 minutes but I cannot get to the bootloader. I tried rooting the phone again this way I can turn s-on then flash the stock rom again but the phone ends up not being detected half way through the process.
I really don't know what else to do...
Forgot to mention, now my inspire boots but then fades to a greyed out screen. My computer recognizes the phone as something occupying the usb port but is not accessible. Wish the phone had a physical reset button somewhere that i can poke with a paperclip...
Sent from my SAMSUNG-SGH-I897 using XDA
Click to expand...
Click to collapse
Greggyt, Hit the IRC Channel again,.....it was a rough day and we were a bit pissed. I just connected after you were gone....=0) just hit the channel again....
glevitan said:
Greggyt, Hit the IRC Channel again,.....it was a rough day and we were a bit pissed. I just connected after you were gone....=0) just hit the channel again....
Click to expand...
Click to collapse
I will get back on the IRC this evening when I get home from work thanks again!!!
Does it say anything about QHUSB_DLOAD USB device being connected?
I ran into a similar problem not too long ago, immediate vibrating followed by a solid amber light and no phone activity (nothing on the screen at all). I knew I had a backup in Recovery, but I couldn't even get into recovery.
In order to work around this, I did the following steps.
1. Deleted the PD98IMG file from my SD card (so I could get to recovery once I made it to the bootloader).
2. Take out the battery, then put it back in.
3. Plug in the phone, and let it sit for a few minutes.
4. Start into bootloader (hold power + Volume Down)
Now, in my case I was just trying to get back into recovery. if you don't have a working recovery, or no ROM to flash, you'll want to grab a few RUU 's to try from the bootloader. Try stock GB first, then try a stock Froyo just for the heck of it.
Hope this helps! Good luck to anyone else that's stumbled into this problem.
side note: I've also heard of this "power problem" occurring to other people without bootloops or screwed up bootloaders: which is solved by doing steps 2 and 3, then it'll boot up normally.
help
im having same issue i have gb stock and i accidtly did froyo ruu phones power bottun does nothing i have to plug it into computer and it will get solid amber light then eventually it either brings up battery charge icon and then if i press power button or unplug it. it just shuts off the i plug it back in and wait sometimes white htc screen comes up and it vibrates for a while then boots ad works like nothing is wrong but i cant flash gb ruu when i try to do that or re root and go to recovery to reistall ics that is on my sd as soon as phone restarts during process it doesnt reboot then i have to go threw whole procss of trying to get it to boot back up
glevitan said:
Never do a factory reset on a S-OFF device....it will jam u up.
It seems that the RUU you flashed was a Froyo one and your phone was running GB so you messed the bootloader. Hit the Hack Kit IRC channel (is in the OP thread) and we will lend u a hand to fix that....
Click to expand...
Click to collapse
im new to this site but i did exactly what you said in your post and now my inspire wont reboot unless i go threw a few hour process of plugin my phone in and i get solid amber light for like 5 min then a battery charge screen comes up then i have to unplug my phone and plug it back in the last time i did this it took about 8 hours of tryin until it finally got amber light for like 5 min then started vibrating for a min or 2 then it booted up and its bin workin fine for like a week now ive tried to reflash gingerbread ruu ive tried doin upgrade from my phone and tried reroot but as soon as it shuts down to start upgrade my phone is off and wont reboot
Hey all,
So I've had my SGS3 for 2 weeks now. I was going to try and do the google wallet hack to enable it on our network. I saw a thread on a forum saying that people have used market enabler to do this. So I dowloaded/installed the market enabler app, then switched the phone to think it was t mobile to install google wallet. it didnt work so I just uninstalled the app and figured I would give editing the build.prop a try later.
About 20 minutes pass, and there was a notification that said something along the lines of " the sim card inserted isn't a verizon sim card" SO I figured " Oh okay, go back to market enabler and switch it back to verizon." That didn't work to clear the noticication. So Then I figured maybe I had to reboot it, and I did that, only to be stuck in some sort of bootloop? When I press the power button to turn on It says Samsung with the lock unlocked, (because I have CWM installed) and then it goes to the next page that says Samsung Galaxy S3. After that, the screen goes black, no spash screen or anything. The rom I had was Synergy 1.2 and it had the stock international boot animation. So I figured boot into recovery and wipe data/cache/dalvik cache and then restore one of my nandroids. I tried both nandroids and they both said MD5 sum does not match, and this is where I am left off at. I can't do anything right now because I'm at work, So I have to wait until I'm off to tinker with it. My true question is Can I flash the stock rom back through odin to bring it back to life? Also Is it possible to just flash the stock rooted image right now, instead of flashing stock back, and then flashing stock rooted to save myself a step?
Thanks for reading guys.
Tyler
95talondsm said:
When I press the power button to turn on It says Samsung with the lock unlocked, (because I have CWM installed) and then it goes to the next page that says Samsung Galaxy S3. After that, the screen goes black, no spash screen or anything.
Click to expand...
Click to collapse
Did you change the build.prop prior to reboot? That sounds like what happens if you change it and don't have the permissions correct. With the device off, does holding vol down + home + power take you into download mode? If so then odin should get you back with the stock verizon image. If you have a rom zip on the internal or external sdcard, you may be able to try reflashing it. Maybe someone has an alternative while your waiting though.
Thanks a lot man. I was sitting there thinking of what I could possibly do, and boom it hit me. I reflashed my from and I am good to go! I did not change the build.prop at all. I was going to wait until I got home to do that. But she's back up and running, thanks for the info.
Sent from my SCH-I535 using xda app-developers app
background: rooted and was running 4.1 stock and CWM 10.0 on verizon gs3. i wanted to bump up to jelly bean 4.2 with CWM 10.1.
first i tried using Rom Manager and Rom Toolkit to flash a new rom. from Rom Manager, i rebooted into recovery and got stuck on the CWM boot screen.
After 30 minutes or so i pulled the battery and tried flashing the stock .tar.md5 using Odin and ended up with this:
"System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest verizon wireless store for help."
now i can't boot into download or recovery. i just have this screen with the yellow exclamation point and the above message.
how screwed am i? i've tried reading everywhere and from what i can gather i didn't wipe my cache sufficiently, but all the other threads just say 'use Odin to get back to stock', but i can't get into download mode so i can't use odin.
please help.
You're bootloader wasn't unlocked. Pull the battery then hold power, volume down, and home for fifteen or twenty seconds until it boots into download mode. Odin flash a stock rom then root AND ALSO unlock your bootloader.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
You're bootloader wasn't unlocked. Pull the battery then hold power, volume down, and home for fifteen or twenty seconds until it boots into download mode. Odin flash a stock rom then root AND ALSO unlock your bootloader.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have noticed that a lot of people have not unlocked the bootloader are posting on here that they have "bricked" their phones.
jmxc23 said:
I have noticed that a lot of people have not unlocked the bootloader posted on here that they have "bricked" their phones.
Click to expand...
Click to collapse
Ha, I agree although I think its occurred in decreasing fashion since August. Being "bricked" is used overeagerly by folks not wholly understanding their situation. You really have to try to brick this device before that word can be used correctly.
Your phone has not been bricked. You will know that you have bricked your phone when you can't turn on your phone at all. No download mode and no recovery mode also no pulling of the battery just a dead phone.
ClockworkMod
When you fix your phone, root then unlock the bootloader... You can try RM again but I believe that it is best to use ClockworkMod (or the Touch version) for flashing instead of ROM Manager - old fashion, maybe, but it works!
NOTE: Once you start flashing it becomes addictive - you have been warned
thanks for the comments. my apologies for using the term Brick incorrectly as it seems to really chap the cheeks of some people on this board (http://forum.xda-developers.com/showthread.php?t=2149210)
no luck with holding down buttons with the battery pulled. i ordered a USB Jig to try and force it back into download mode.
From there, what should my first step be? return to stock?
jondotwoz said:
thanks for the comments. my apologies for using the term Brick incorrectly as it seems to really chap the cheeks of some people on this board (http://forum.xda-developers.com/showthread.php?t=2149210)
no luck with holding down buttons with the battery pulled. i ordered a USB Jig to try and force it back into download mode.
From there, what should my first step be? return to stock?
Click to expand...
Click to collapse
youll need to put the battery back in......lol
ddurandSGS3 said:
youll need to put the battery back in......lol
Click to expand...
Click to collapse
obviously. i've tried this a million times. It shows the download screen green android robot and the text in the top left for about 4 seconds. then it goes black and the yellow triangle comes back telling me unauthorized software is on there.
check here. particularly post 2. i think thats what you want.
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=odin
ddurandSGS3 said:
check here. particularly post 2. i think thats what you want.
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=odin
Click to expand...
Click to collapse
thanks that's a very helpful thread. However, i still can't get into download/Odin mode. i'm guessing if/once the USB jig can force the phone into download mode, this is where i'll start.
thanks for everyone's help and patience.