Related
itS MY BROTHERS fone and it wont turn on??? Is it complete gone or is there another way to bring it back to life. I bricked my htc nexus and ive been able to go around it. But im so lost when it comes to motorola. ? can anyone help please
Sir0 said:
itS MY BROTHERS fone and it wont turn on??? Is it complete gone or is there another way to bring it back to life.can anyone help please
Click to expand...
Click to collapse
You need to give us something to go off of. if you just say my car is broken will a mechanic know what to do?
Tell us what you or whoever has done to the phone to get it in that state then we can (hopefully) instruct you to fix it.
Is it a Droid 2 global or the original Droid 2.
My first thought is it's out of battery or you destroyed it with a liquid (Always take the battery out of your phone ASAP if you happen to get it wet).
Its a regualar droid 2. I rooted the phone months ago. and i guess he was playing around with and bricked it. I used another battery and it turn on and straight to the motorola sign. and stays there. took the battery off put it back on press X and turned it on. and i got into android ! mark. i hit search button and it takes me to the system recovery. Did the wipe date/factory reset. and wipe cache. All i get now is E: can't open /cache/ recovery/command. Im outta my league with motorola. how can i unbrick this from here
Best bet at this point would be to use RSDLite and flash the Full Stock SBF file.
Yes you need the 2.3.20 sbf and rsdlite to flash the software to the phone. Ignore that 'error' in the stock recovery it always says that.
Also if you have a D2 why did you post in the D2 G section?
Sent from my DROID2 using XDA App
I actually have the same problem, I used RSDLite to flash the full SBF, and my M2G won't power on. The process I have tired is a battery pull while charger is connected, then insert battery followed by holding power and x down.(nothing happened) I have not tried the method of using a different battery.
Any help is appreciated, I would like for the phone to power on. I don't want to use a warranty replacement just yet!
I used this SBF found here.
http://www.mydroidworld.com/forums/...l-sbf-file-2-4-29-full-rsdlite.html#post49668
Pressing the up-arrow when turning the phone on should take it straight to the bootloader, where you can then try flashing the SBF again.
helmutiffe said:
Pressing the up-arrow.....
Click to expand...
Click to collapse
Thank you, I tried that right when I went home with the same battery and nothin, then I tried the same process with a new battery and it worked.... Thank you for the response.
Peace Off & Blow Ganja!
Hey all
Before anyone mentions that i should be searching around more, i would like to say that i've been on multiple threads and they all state the same thing (use NVflash to flash CWM and then boot into CWM but the solution did not work for me past flashing CWM and then trying to access recovery after) and i wasn't able to find one that had a similar problem as mine.
I have CWM flashed through NVflash and was running CM7.1 RC1. I took a screenshot with the 'shootme' app and proceeded to look at the gallery to make sure it came out okay. The gallery crashed and i was sent to the home screen. I swiped to a different homescreen when my phone froze halfway through the transition to the next screen. No combination of buttons/long presses were able to get me out of it so i went ahead and did a battery pull. So my dilemma is that now i'm stuck at the LG boot logo with no blue status bar under it. It freezes there and will not do anything every time i boot up. volume down+power does not give me access to recovery nor does any other button combo get me past the LG boot logo.
Are there any other methods i might be able to use like ADB or what not to get myself out of this situation? or at least into recovery? Any comments or suggestions would be greatly appreciated as i've been searching for hours with little help and my eyes are starting to get strained.
hmmm.. I know it's a simple question, but I gotta ask.. are you holding the pwr and volume down button long enough? you have to keep holding it even after you see the LG screen.. Keep holding until you see the 2nd screen?
If so.. do the nvflash again? Edit: Not sure if I would do this without getting further guidance tho..
schmit said:
hmmm.. I know it's a simple question, but I gotta ask.. are you holding the pwr and volume down button long enough? you have to keep holding it even after you see the LG screen.. Keep holding until you see the 2nd screen?
Click to expand...
Click to collapse
This. I remember when I boot looped my phone I had the problem of letting go of the volume key too early, you need to hold down volume and power from a totally powered off phone until recovery actually starts and you see the green "android" logo of CWM.
Try re-flashing CWM, NVFlash CAN fail. There is literally nothing you can do within the OS that will prevent recovery from working. Either you did something wrong somewhere along the recovery process or you discovered an entirely new problem with the phone. I'm going to hazard a guess and say it's the former.
Thanks for the response guys. I wish that it was the case of not holding the buttons long enough. I have tried numerous times with the buttons held down for a long period of time. I even held the combo down for almost 5 minutes a few times.
Every time i try to boot up, it won't go past the LG boot screen so i would pull the battery out and go through flashing CWM through NVflash again. I'm sure I'm not missing anything because everything goes through and gets sent to the phone successfully.
I did happen to run into a thread that was closely similar to mine but his method was to just keep reflashing CWM and the stock recovery back and forth every time it failed until it turned on. I might have to try that if i cannot figure out this problem out soon. Not being able to use this phone is killing me! heh.
I just joined your club. Wow this sucks.
So apparently this is a whole new problem that's been found? Every other help thread seems to point to using NVflash or remaking the partitions due to a bad flash using an O2x based file instead of G2x.
But none of those solutions come close to doing anything. There has been some people with the same problem as me but aren't proactive at all enough to get someone's attention, so i'm guessing this problem is getting pushed to the side with people just going about getting their phones replaces/buying new ones.
I did happen to run into a thread on paulobrien/modaco's forum that had people using NVflash to get out of any sticky situation like this. It just reverts everything back to the stock factory settings but with root. We cannot use this though because he hasn't built it to be compatible with our LGP999's because everything was built for their UK LGP990's. Maybe that's a start to getting this solution fixed?
I hate to say this, bit you might have to call t mobile and get a replacement. Flash back to stock recovery and they won't know you messed with anything.
Sent from my Nexus 5g using XDA Ultimate App
Don't send back....you'll get same defacement a battery pull go into nvflah and go back stock then flash nv flash fix pArtitions
As I have mentioned before, NVflash does NOT give me access to my recovery let alone solve anything else. NVflash DOES work and does sucessfully send both CWM and the stock recovery but when I try to boot into either of them, let alone just power on normally, it simply DOES NOT go past the LG boot screen. it just hangs there doing nothing at all until I pull the battery out and do the same process over until it just hangs again.
while it is on/stuck at the LG screen, my computer does not recognize it so i cannot even try and run ADB commands. It does however, recognize it when I plug it in using the volume buttons held down when I use NVflash but there's nothing else I can do besides use NVflash obviously.
Jduhb said:
As I have mentioned before, NVflash does NOT give me access to my recovery let alone solve anything else. NVflash DOES work and does sucessfully send both CWM and the stock recovery but when I try to boot into either of them, let alone just power on normally, it simply DOES NOT go past the LG boot screen. it just hangs there doing nothing at all until I pull the battery out and do the same process over until it just hangs again.
while it is on/stuck at the LG screen, my computer does not recognize it so i cannot even try and run ADB commands. It does however, recognize it when I plug it in using the volume buttons held down when I use NVflash but there's nothing else I can do besides use NVflash obviously.
Click to expand...
Click to collapse
Did you ever find a solution to this issue? Because my phone is doing this...
I attempted to restore my phone back to the wrong backup that was from a galaxy sII (2.3.4 i think); needless to say, the restore failed. I then restarted my phone from CWM and it gets stuck at LG screen.
I have tried to NVflash back to stock; nothing. same thing reflashing back to CWM.
ideas?
have you tried this link out yet?
http://forum.xda-developers.com/showthread.php?t=1180331
same problem..... anybody find something to fix this yet?
From what I heard is that you need to remove the battery, then boot into recovery or something.
Sent from my G2X
Use smartflash for the p990 but only use the p999 ap.bin file which will put the rom and kernel back to stock p999.
Rom for recovery always fixes any soft brick back to stock 2.3.3 OTA. It's saved my phone multiple times from stuck on S/W screen to being stuck on lg logo or even the dreaded can't mount sdcard-cache errors in cwm.
Sent from my LG-P999 using xda premium
I used the following method when Clockworkmod became corrupted and was unable to mount my sd card. I had just wiped everything on my phone intending to install a new rom when the issue happened. I could not even get to the S/W upgrade screen. It saved my phone. Hope it works for you.
http://forum.xda-developers.com/showthread.php?p=17258229
jcbofkc said:
I used the following method when Clockworkmod became corrupted and was unable to mount my sd card. I had just wiped everything on my phone intending to install a new rom when the issue happened. I could not even get to the S/W upgrade screen. It saved my phone. Hope it works for you.
http://forum.xda-developers.com/showthread.php?p=17258229
Click to expand...
Click to collapse
omg thank you so much! It worked! Not only that but i was stuck on frodo 2.2.2 before which is why i was messing with my phone in the first place and now its on gingerbread. Awesome! thank you!!!!
sabotage99 said:
omg thank you so much! It worked! Not only that but i was stuck on frodo 2.2.2 before which is why i was messing with my phone in the first place and now its on gingerbread. Awesome! thank you!!!!
Click to expand...
Click to collapse
Glad for you that it worked.
Kwes1020 pointed me in the right direction last week. Be sure to give a thanks to ILUHA_89 who came up with the fix.
Amazing how people are soo lost without providing them link after link to other threads. They are soo lazy and can't follow simple directions, each time i get a new phone i go to that section on xda and soak up all the information as it usually is already there. It's just funny is all i guess.
d12unk13astard said:
Amazing how people are soo lost without providing them link after link to other threads. They are soo lazy and can't follow simple directions, each time i get a new phone i go to that section on xda and soak up all the information as it usually is already there. It's just funny is all i guess.
Click to expand...
Click to collapse
It's really not that big a deal. I was brand new to android once and asked all sorts of things.
I, like you, happen to read everything I can get my hands on. Some struggle going through all the info. I was here the day the forum opened, so I kind of remember where everything is.
Some are lazy and others just have no idea what the heck is going on and are intimidated by certain processes. I would rather help someone instead of listening to them ***** about their broken phone.
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.
Hello All , I think i have just bricked my phone.
This is what i did
Go it rooted. installed clockworkmod.
Tried SD partitioning
Phone shutdown and never started again.
Now when i try powering on , it just vibrates first( as ususal) but nothing more(just blank screen with no backlights)
Can i get it back, if so how?
Please help. Thanks in advance
I Have The Same Problem Exactly and i don't know what to do :/
I Have The Same Exact Problem ._.
they say if it doesnt boot recovery and download mode then it is hard bricked already which more or less likely a paper weight.
Sent from my Nokia 3310 running ICS
Have you guys tried a hard reboot by removing the battery for 15 or 20 seconds & then just popping it back in and powering on? My MT4Gs did something very similar when rooting and that's all I had to do to fix it. Good Luck!
i tried every single thing i could do but nothing happend.. i sent it already to the selling point but i think they wont fix it for free because its rooted
I have a samsung galaxy 10.1 tablet.
I was trying to root it.
After I thought I was done rooting, and went to turn it on, the "samsung" startup screen just rolled from the top of the tablet to the bottom.
About 24 hours later, (now) I attempted to start the device back up to try again, and I couldnt. I am sure it has battery, the device simply wont turn on.
I am not tech savvy, I have no idea why this is.
Help? It's my mom's tablet and I dont have the money to replace it!
22malik said:
I have a samsung galaxy 10.1 tablet.
I was trying to root it.
After I thought I was done rooting, and went to turn it on, the "samsung" startup screen just rolled from the top of the tablet to the bottom.
About 24 hours later, (now) I attempted to start the device back up to try again, and I couldnt. I am sure it has battery, the device simply wont turn on.
I am not tech savvy, I have no idea why this is.
Help? It's my mom's tablet and I dont have the money to replace it!
Click to expand...
Click to collapse
So first of all seeing that you have a samsung tab 10.1 I think you should go to the Samsung tab 10.1 threads and ask this question as there are more people who can advice you. Also you will find many guides on how to return to stock.
Sent from my HTC One using Tapatalk 4
sometimes same prob
WildfireDEV said:
So first of all seeing that you have a samsung tab 10.1 I think you should go to the Samsung tab 10.1 threads and ask this question as there are more people who can advice you. Also you will find many guides on how to return to stock.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
yeah but as with me, ive been on here awhile and still cannot post to those forums as we havent made enough posts... so its a read ans search, but not able to ask questions. im getting there though.
scooby092477 said:
yeah but as with me, ive been on here awhile and still cannot post to those forums as we havent made enough posts... so its a read ans search, but not able to ask questions. im getting there though.
Click to expand...
Click to collapse
You don't have a post limit to post in the device's question and anwser section. The post limit blocks you from posting in devolpment threads.
update?
Hate when people don't update to say if something worked..
have a aspen i just bricked (screen lights up but doesnt even load an image) ive tried livesuit with no luck ill try this now i guess
BRICKED 7inch Irola Tablet...PLEASE HELP
I am in DIRE need of some help with my tablet. I received this irola dx752 tablet bricked and cannot fix it for the life of me. I am able to hold power and volume up and get into recovery system version 4.2.01. I Have tried a factory reset and a wipe system cache and the tablet just reboots to the green robot with and exclamation mark. If I press volume up, it brings me back to the system recovery. Now i am not very versed in ADB but I tried to sideload just about every firmware I could find for an a13 allwinner a8 cortex 7inch tablet, since the irola website has taken down its firmware. Also, fastboot will not work on this tablet whatsoever (it just says waiting for device) when i enter any command. I have never seen this tablet boot into a rom of any kind and therefore cannot tell if USB Debugging was ever enabled. I also Have tried different drivers but the one that seem to hold is the Android ADB Interface. CAN ANYONE PLEASE GIVE ME SOME SUGGESTIONS OR SOME HELP? It would be greatly appreciated. Thank you.
Help
Alright! Let me tell you my problem
I have a Tablet Intex Helix II , It has no volume buttons, No Reset Button , and its has a non removable battery (it cant Power on, only with Charger)
and when it Powers on It just gets stuck on Boot
Btw i Tried To root it And i think i Failed