Related
hello all, i need help again this time.
let's get to the point.
this morning, i tried to charge my G1 because the battery has yellow color.
when i charged the phone, after around 5 minutes, suddenly my G1 restart itself and then after the "G1" logo, the screen go all black, sometimes not all black but there's a little glitch (white-green-purple-all little colors.)
the phone got heated on the bottom part everytime i power-on it, even just on battery (not charged).
i tried "Camera + Power", it's only getting to that red-blue-green-white screen that shows :
"DREA100 PVT 32B
HBOOT - 0.95.0000
CPLD-4
Radio-2.22.23.02
Sep 2 2008
Serial0"
Click to expand...
Click to collapse
and it stops there for AGES . won't do anything.
i tried "Home + Power", i tried to hold down that two buttons for 25 second more, but it keeps normal boot, shows G1 logo, and then black screen again.
i tried "Menu + Power", it just the same as "Home + Power"
my G1 has never been rooted, it's all original, i haven't done any system upgrading-downgrading things.
the charger is the original one, original from htc
the battery is new, i've just changed it one month ago.
that's all the informations that i can give.
so, anyone can help me solving this problem?
if its not rooted or anything than that means its HTC's fault not yours. and since you cant access the recovery menu to flash a new rom or recover a nandroid backup, it sounds like you're up ****s creek with a turd for a paddle.... unless somebody has developed a way of flashing without recovery. in other words; get a new phone or send it in to t-mobile.
Get an SD card reader an put a DREIMG.nbh on your sdcard to downgrade to RC29 (push power+camera, select confirm), then wait for the OTA to push you to DMD64. You will loose all your data but at least your phone will work.
Alternatively, after downgrading to RC29 you can exploit the bluetooth bug to gain root access, and after that install CM5.0.8 and be twice as happy with you chunky old G1.
mejorguille said:
Get an SD card reader an put a DREIMG.nbh on your sdcard to downgrade to RC29 (push power+camera, select confirm), then wait for the OTA to push you to DMD64. You will loose all your data but at least your phone will work.
Alternatively, after downgrading to RC29 you can exploit the bluetooth bug to gain root access, and after that install CM5.0.8 and be twice as happy with you chunky old G1.
Click to expand...
Click to collapse
okay, i think i'll try this one.
just another information, i've tried another combination of buttons, such as hold down together "Call + Menu + Power" and then slide quickly to Home button, but it's giving no effect too
dioadi said:
okay, i think i'll try this one.
just another information, i've tried another combination of buttons, such as hold down together "Call + Menu + Power" and then slide quickly to Home button, but it's giving no effect too
Click to expand...
Click to collapse
Call+Menu+Power is for a reboot while the phone is on lol. Only other way is "blue light mode" which is trackball and power, but I don't feel like explaining it to you=p.
mejorguille said:
Call+Menu+Power is for a reboot while the phone is on lol. Only other way is "blue light mode" which is trackball and power, but I don't feel like explaining it to you=p.
Click to expand...
Click to collapse
ohh, to be honest, i've tried the Call + TrackBall + Power too, yes the LED light up blue, and then nothing happened while the LED still light blue.
dioadi said:
ohh, to be honest, i've tried the Call + TrackBall + Power too, yes the LED light up blue, and then nothing happened while the LED still light blue.
Click to expand...
Click to collapse
Nothing is supposed to happen unless you have a JTAG afapter. And why the hell post in two different forums?
mejorguille said:
Nothing is supposed to happen unless you have a JTAG afapter. And why the hell post in two different forums?
Click to expand...
Click to collapse
wow, i guess JTAG Adapted would be another long explanation, huh?
yes i made two posts. You know that sometimes, some people prefer to go to just specific thread/subforum, ignoring the other thread/subforum.
but who know if that people can help me?
hey, i'm back.
after days to days downloading DREAIMG.nbh again and again, finally i got the right DREAIMG.nbh, not corrupted one.
and yes, i successfully update, all stuff are signed "OK" , and then i press the action (trackball) button, restart the phone, and guess what? it turns back to the beginning problem, still. "G1" logo, and then turn to whole black screen.
so, now what?
am i bricked?
or is it hardware problem? (remember i said that everytime i turn on the phone, the down part, near sim card, is always getting heated)
the only screen that can be accessed is that rainbow screen and the update screen (Camera + Power).
dioadi said:
hey, i'm back.
after days to days downloading DREAIMG.nbh again and again, finally i got the right DREAIMG.nbh, not corrupted one.
and yes, i successfully update, all stuff are signed "OK" , and then i press the action (trackball) button, restart the phone, and guess what? it turns back to the beginning problem, still. "G1" logo, and then turn to whole black screen.
so, now what?
am i bricked?
or is it hardware problem? (remember i said that everytime i turn on the phone, the down part, near sim card, is always getting heated)
the only screen that can be accessed is that rainbow screen and the update screen (Camera + Power).
Click to expand...
Click to collapse
im pretty sure the heat issue comes from the processor, not the sim card. mine does that too. its nothing to worry about as long as you havent overclocked your device (mine is overclocked and works great aside from gettin warm during heavy usage.) what happens when you plug the phone into usb? does it show the SD card or can you get into the android sdk? its a long shot as i doubt you can get into debug mode without having a uncorrupted os, but i guess its worth a shot.
BuddhaTeh1337 said:
im pretty sure the heat issue comes from the processor, not the sim card. mine does that too. its nothing to worry about as long as you havent overclocked your device (mine is overclocked and works great aside from gettin warm during heavy usage.) what happens when you plug the phone into usb? does it show the SD card or can you get into the android sdk? its a long shot as i doubt you can get into debug mode without having a uncorrupted os, but i guess its worth a shot.
Click to expand...
Click to collapse
the phone can't get into the home screen, it's always going blank after Tmobile-G1 logo.
so when i plug the phone into usb, it's just charging, no SD card recognizing on my computer.
And how can i get into Android SDK ?
Google is your best friend.
Sent from my HTC Dream using XDA App
help i9000 after flash, doing loop of at&t logo, can not enter download mode,
when plugged in screen goes black.
!! if anyone can help please do not hesitate, mostly appreciated.
Try to hold the Down+Menu+Power combination while INSERTING the battery into the device.
i try that seem to have no response and when unplugged from usb it loop at&t logo
or plugged in usb screen goes black and no response seem from pressing buttons
I had a similar problem as most phones in Canada seem to have Download/Recovery mode disabled, and here is what worked for me.
Grab something like One Click Un Root (all models), and click one click un root (obviously phone has to be on and plugged into the computer).
This should automatically reboot you into Recovery Mode!
All you have to do is "wipe data/factory default" or something like that (should be the third option).
As it states, you will loose all your data, but at least you will have a functionning phone!
did it work?
Hi. I have similar problem. Can anybody give instruction what can I do?
I have this problem too. Please help somebody
Add me to the list. Bell Galaxy S, went to unlock my phone the screen went black. Now it will not boot into the OS, the galaxy S splash screen displays then nothing. The menu and back button light up, thats all. ****[email protected]@
I have not rooted or anything.
Of course my download mode does not work.. Going to try this one click root thing if I can find it.
NOT HAPPY
This is not working. Probably because the phone is not in USB debugging mode as I can't change it... Is there any other way to get the phone into recovery mode?
**** me
i had the same thing happen to me the other day with my bell galaxy s and my phone wont do the 3 button combo trick. i left my phone plugged in to a wall charger for a while until the back of the phone became a little warm. i pulled the battery and then left the power cord plugged in and put the battery back in. i held the volume down and enter button until the battery charging indicator showed up, then i also pressed and held the power button until the boot animation started (this is the blue moving swirl and music, not the galaxy s splash scree) and then i let go of the power button. it took a few attempts at this before it actually worked, but eventually it will go into download mode at which time you can open the odin app, then plug in the usb cable and flash your phone that way. it did seem to make a difference if the back of the phone (around the camera area) was warm. if i let go of the power button while the music was playing and the phone did not enter download mode i would keep all 3 buttons pressed until it shut down again, then i would only let go of the power button while the phone initiated the charging screen, then once the battery logo was displayed i would hold the 3 buttons again and would just keep doing this until it went into download mode. i have flashed it at least 5 times today and i have been able to do this each time.
i also had an issue where odin would not recognize my phone was plugged in and windows would show a message saying the usb device was not recognized. i left the phone plugged in and while in download mode i pressed the volume up, enter button and power button until the phone went blank and when the galaxy s logo showed up i let go of the power button and the phone would go into recovery mode and then the usb drivers would be installed. i would then do the 3 button combo for download mode and odin would work fine. it took several attempts but it does work. i hope this helps you guys
If I hold all three buttons the splash screen does not come on, it just keeps looping the Galaxy S logo until I let go of the power button....
xZeDgEx said:
If I hold all three buttons the splash screen does not come on, it just keeps looping the Galaxy S logo until I let go of the power button....
Click to expand...
Click to collapse
That's what mine did too, several times in a row and then it worked. For some reason it only works after the battery is charging for a bit and the back becomes warm. then it works at will
No luck. I am probably screwed getting it exchanged now too as I am passed the 14 days from Best Buy.
the on click thing doesn't work, if your phone is already bricked.
also it is not the phone's fault for not working, the phone was working properly before you tried the hacks.
whenever you do these kind of things you know you are entering into the "not supported" "not covered by warranty" zone.
in the worse case scenario, if you can no enter download mode to recover your phone, it'll be to take the phone back to bell and claim warranty on it, and prentent you don't know what happened to it.
xZeDgEx said:
Add me to the list. Bell Galaxy S, went to unlock my phone the screen went black. Now it will not boot into the OS, the galaxy S splash screen displays then nothing. The menu and back button light up, thats all. [email protected]@
I have not rooted or anything.
Of course my download mode does not work.. Going to try this one click root thing if I can find it.
NOT HAPPY
Click to expand...
Click to collapse
AllGamer said:
the on click thing doesn't work, if your phone is already bricked.
also it is not the phone's fault for not working, the phone was working properly before you tried the hacks.
whenever you do these kind of things you know you are entering into the "not supported" "not covered by warranty" zone.
in the worse case scenario, if you can no enter download mode to recover your phone, it'll be to take the phone back to bell and claim warranty on it, and prentent you don't know what happened to it.
Click to expand...
Click to collapse
Its my fault??
I did not hack my phone. Its not rooted, I did nothing to it.
By "unlock" I meant exactly that, unlock as in swiping the screen to unlock it.
The more I search the net the more posts I find of Galaxy S phones randomly bricking...
on the original message sounded more like you went to Unlock the phone, as in SIM unlock the phone using any of the tools available out there, and there has been already several people which had the same problem.
if you go back to Bell for an exchange, you better not use the word "unlock" rather use Swipe
as the message on the phone "swipe the screen to unlock"
there are no known issue about this causing the phone to brick.
if that is what happened to you, you should have started a new topic for people to help you, instead of hijacking the topic from the OP, as your issue is different from OP, the OP actually screwed up because he/she flashed the wrong ROM to the i9000
... anyways, Does it work if you reboot the phone?
I have rebooted the phone about 100 times. The phone crashed when I unlocked it to check a text I received. (not hacked). Has not booted up properly since. I have found many others with the same issue who have also not hacked/rooted/unlocked/ their phones.
Waiting on Best Buy to call me back. I am so pissed right now, I have been bragging to my friends and co-workers how awesome this phone is, one has already picked one up, I hope his doesn't brick too. Not recommending it to anyone anymore..
did you load a lot of MP3 to the phone?
can you boot into Recovery Mode?
in the recovery mode you can wipe the Cache and wipe the data
that should make your phone work normal again
it'll be best to open a topic to help you trouble shoot your interesting issue, as it's the first i've hear that you get a black screen after Swiping out of the lock screen
I can't get into recovery mode. I have tried every button combination I have found. I had about 2 GB of music on the phone. I also installed the Android SDK to try ADB, but since the phone is not in USB debugging mode it does not see it.
xZeDgEx said:
I can't get into recovery mode. I have tried every button combination I have found. I had about 2 GB of music on the phone. I also installed the Android SDK to try ADB, but since the phone is not in USB debugging mode it does not see it.
Click to expand...
Click to collapse
on the other topics relating to the 3 button not working.
have you tried the heating up method?
or the plugging the battery in, when all 3 buttons are pressed? (of course for this one you will need help from a friend, unless you are very skilled at keeping the 3 button on hold meanwhile able to slide in the battery in with out a 3rd hand)
Guys, thanks to all of you - especially frysee, who was a big help via Gtalk - the biggest part of my problem is solved:
My Transformer is still bricked and display won't turn on, but I was able to go back to stock ROM and wipe all personal data. So I won't get any trouble with warranty
If anyone is interested, me or frysee could write a How To for returning to stock ROM and retrieve warranty when screen is dead.
Thanks again!
qwer23
_____________________________________
Hi Guys!
I have a problem that is pretty common over at MoDaCo, but I haven't read anything about it here.
My Transformer sometimes doesn't turn on or wake up from sleep mode when turned on already. You can push the power button endlessly and nothing happens. Then suddenly it'll turn on as if nothing had happened.
I had this problem the first time right out of the box, so there's no bad software installed by me, don't know what ASUS did though. Perhaps it's one of the pre-installed apps.
As I said, normally it eventually comes to life again, but now I couldn't turn it on for a whole day! After I had no success, I left it on the charger over night, but still nothing this morning.
I feel I tried everything, pushed Vol Down + Power to go into recovery, pushed Vol Up + Vol Down and plugged USB to go into (useless) flash mode just to see the device to something, but no.
The only things that happen, if I push power:
- if I plug USB, the Windows plug and play sound plays and if I force shutdown the Transformer again (long-press power), the unplug sound plays. The device even appears in the Explorer and I can access SD card, but it only shows empty folders, no files in them.
- When I force-shutdown the device, I hear an internal "click" sound, similar to the one when you switch from front to rear camera, and you hear the speakers turn off. So it seems to initialize everything and stuff...
But all the time the Transformer screen stays dead
Any advice? Really need your help here guys! At MoDaCo there's no answer so far...
Regards,
qwer23
I was initially having this problem with my Transformer (it would usually happen when it had gone on standby and it couldn't get it to turn back on again) until I ran the ASUS updates on it - have you been able to update your Transformer on the occasions it did turn on for you?
If you've rooted it and stopped the OTA updates going onto it, you might just have to undo that and get an official ASUS firmware build on there to help fix the problem.
demonotter said:
I was initially having this problem with my Transformer (it would usually happen when it had gone on standby and it couldn't get it to turn back on again) until I ran the ASUS updates on it - have you been able to update your Transformer on the occasions it did turn on for you?
If you've rooted it and stopped the OTA updates going onto it, you might just have to undo that and get an official ASUS firmware build on there to help fix the problem.
Click to expand...
Click to collapse
Hi!
First of all, thx for your answer.
Well as I said, the first time the problem occured, the device was out of the box and untouched before. So I don't think it has to do with something I did.
For me it normally also happened when device was in sleep mode, except the first time out of the box
I installed a custom ROM + Clockworkmod Recovery after that, hoping it'll fix the deep sleep problem. And it really didn't happen again - until now
I didn't turn off OTA updates as I first saw that thread when the device was already dead Perhaps it tried to OTA update itself but I guess I would have to confirm this manually right? And I didn't do that...
Reflashing another ROM or the stock ROM was my first idea, too. But hell, I can't even go to recovery! No matter what I do, press, plug or unplugg, the screen stays black!
Nice, another german Transformer
"playing the plug and play sound" means you propably have adb access? Tried getting a logcat?
frysee said:
Nice, another german Transformer
"playing the plug and play sound" means you propably have adb access? Tried getting a logcat?
Click to expand...
Click to collapse
yes, being unable to wait for the german release, i imported from uk
adb gives me "device not found". even though i'm not a total noob, i don't know what i have to change to make it work. any advice? sadly i'm working while my tf is charging @home so can't really try something. i only hope you guys have some ideas
Sent from my rooted X10i using awesome custom roms
qwer23 said:
Reflashing another ROM or the stock ROM was my first idea, too. But hell, I can't even go to recovery! No matter what I do, press, plug or unplugg, the screen stays black!
Click to expand...
Click to collapse
Ahh. I didn't realise the screen was completely dead, I thought you had it working some of the time as had happened to me.
If you're seeing it in Explorer, maybe it is just a hardware failure and you'll have to get Asus to look at it...
demonotter said:
Ahh. I didn't realise the screen was completely dead, I thought you had it working some of the time as had happened to me.
If you're seeing it in Explorer, maybe it is just a hardware failure and you'll have to get Asus to look at it...
Click to expand...
Click to collapse
no i guess that it is indeed the same thing that happened to you, sometimes it worked, sometimes not. only this time it doesn't come back from the not working part I guess you see yours in explorer too if it troubles to get out of deep sleep. i guess it's just the screen that sometimes doesn't turn on for all with that problem. but for me it doesn't even turn on for booting
Sent from my rooted X10i using awesome custom roms
It's possible. I don't think I tested connecting it to the Explorer while the screen was off, I assumed it just wasn't on.
Can you test it with the HDMI out and see if that shows you what would be on screen?
demonotter said:
It's possible. I don't think I tested connecting it to the Explorer while the screen was off, I assumed it just wasn't on.
Can you test it with the HDMI out and see if that shows you what would be on screen?
Click to expand...
Click to collapse
Yeah, good idea! Will try this asap when I'm back home. Do I have to press something on the TF to enable HDMI output or is it enough to plug it in?
qwer23 said:
Yeah, good idea! Will try this asap when I'm back home. Do I have to press something on the TF to enable HDMI output or is it enough to plug it in?
Click to expand...
Click to collapse
You just plug it in.
qwer23 said:
Hi Guys!
I have a problem that is pretty common over at MoDaCo, but I haven't read anything about it here.
My Transformer sometimes doesn't turn on or wake up from sleep mode when turned on already. You can push the power button endlessly and nothing happens. Then suddenly it'll turn on as if nothing had happened.
I had this problem the first time right out of the box, so there's no bad software installed by me, don't know what ASUS did though. Perhaps it's one of the pre-installed apps.
As I said, normally it eventually comes to life again, but now I couldn't turn it on for a whole day! After I had no success, I left it on the charger over night, but still nothing this morning.
I feel I tried everything, pushed Vol Down + Power to go into recovery, pushed Vol Up + Vol Down and plugged USB to go into (useless) flash mode just to see the device to something, but no.
The only things that happen, if I push power:
- if I plug USB, the Windows plug and play sound plays and if I force shutdown the Transformer again (long-press power), the unplug sound plays. The device even appears in the Explorer and I can access SD card, but it only shows empty folders, no files in them.
- When I force-shutdown the device, I hear an internal "click" sound, similar to the one when you switch from front to rear camera, and you hear the speakers turn off. So it seems to initialize everything and stuff...
But all the time the Transformer screen stays dead
Any advice? Really need your help here guys! At MoDaCo there's no answer so far...
Regards,
qwer23
Click to expand...
Click to collapse
When it seems dead, try holding the power button for about 5 seconds (or whatever time you hold it for when turning it off)
Leave for about 2 minutes then hold power button again (like you do when turning device on) and it should boot.
checkbox111 said:
When it seems dead, try holding the power button for about 5 seconds (or whatever time you hold it for when turning it off)
Leave for about 2 minutes then hold power button again (like you do when turning device on) and it should boot.
Click to expand...
Click to collapse
Tried that a lot of times already. No help.
Phone still won't turn on, but I just realized I cannot only access my SD Card, I can also access internal storage.
Is this of any help?
qwer23 said:
Tried that a lot of times already. No help.
Click to expand...
Click to collapse
Then your ****ed!
checkbox111 said:
Then your ****ed!
Click to expand...
Click to collapse
I guess so
I'm getting a mini-hdmi cable today to determine if the screen is broken, because i have the feeling that ***** is booting but not showing anything...But I'll have to send it to ASUS nonetheless. Has anyone ever sent a device in for warranty reasons with custom software (CWM, Custom ROM) on it? What kind of trouble will I have to face?
I'd say try it with the HDMI cable, see if you get anything up on it and if the touchscreen/everything else still works, see if you can get the latest official ROM on there, see if that fixes the problem.
If nothing else, you can then send it back with an official firmware on it.
Try holding the power button for 5-10 sec, then press power + volume down (might be volume up - try both) together for another 5-6 sec. You'll get to a reset screen where it asks you to confirm if you want to wipe everything. press volume down (I think!! - read the screen carefully) instead to boot normally.
hope this helps
Its 10+ seconds for a full power off by the way, nothing shorter than that. If you changed any system files either by flashing or by pushing via ADB then you will have invalidated your warranty. Unless you can restore it to the way it was before you fiddled with it, you'll have an expensive paperweight.
sbirsen said:
Try holding the power button for 5-10 sec, then press power + volume down (might be volume up - try both) together for another 5-6 sec. You'll get to a reset screen where it asks you to confirm if you want to wipe everything. press volume down (I think!! - read the screen carefully) instead to boot normally.
hope this helps
Click to expand...
Click to collapse
Not possible since I installed CMW.
stuntdouble said:
Its 10+ seconds for a full power off by the way, nothing shorter than that. If you changed any system files either by flashing or by pushing via ADB then you will have invalidated your warranty. Unless you can restore it to the way it was before you fiddled with it, you'll have an expensive paperweight.
Click to expand...
Click to collapse
Big bummer And sadly there are no "ASUS Stores" around where I could use a stupid employee who has no clue and is convinced it's hardware related.
Well I don't have my HDMI cable by now and will try this first, but if that doesn't work:
Can someone give me a step-by-step how I can access the restore function of CWM without seeing anything on my device? I did a backup in CWM before installing the custom ROM. Perhaps tell me sth. like this: "press power+vol. down on start, then after approx. x seconds press vol up, wait a bit to make sure CWM started, press vol down twice, to go to recovery, ..."
And can someone do the same for the stock recovery to reset the device? Perhaps there's a chance that a failed OTA update deleted CWM an there's the stock recovery.
I know the chance to save it like this are small, but otherwise a lot of money is lost
Regards,
qwer23
On the flip side however, you could probably make some money by being the first to dismantle your device, and sell the photos of the internals to some website like iFixit. Then you could also sell it off as parts on eBay. Obviously it might take more effort than you are willing to give it, but at least it's another option.
If you do decide to open it up I would love to hear what mA rating the battery has on its label. Not being able to find out the actual proper rating from any site has been driving me nuts. I believe it's 6800mA but im not 100% sure.
Hello, first off I will say I am a total novice when it comes to messing with my phone as my upgrade is in a month so I took the plunge and all was well at first. I used SuperOneClick to root my Flipside which runs Froyo 2.2.2. I deleted the bloatware as that was my main goal. This all took place about 2 weeks ago, and no problems existed.
Yesterday when I was reading a simple text message my flipside automatically reset itself and became lodged at the Motorola M logo. I've had this issue in the past before rooting so I just removed the battery in hopes all would work well as before, sadly that wasn't the case. My phone then booted up and only the backlight appeared on the screen causing it to become stuck in the infinite bootloop. I've tried all the different hard resets with the x button and power button, the volume down button, etc. None of them work as only the backlight comes up on my screen so I can't see anything. Is there any way to unroot it or flash it back to stock?
If any of my terminology seems out of place then sorry, I honestly have not a slightest idea what to do nor what is occurring other than the bootloop.
Any help is appreciated and can you please dumb down the answer for me if possible. Thanks!
Kippyyy said:
Hello, first off I will say I am a total novice when it comes to messing with my phone as my upgrade is in a month so I took the plunge and all was well at first. I used SuperOneClick to root my Flipside which runs Froyo 2.2.2. I deleted the bloatware as that was my main goal. This all took place about 2 weeks ago, and no problems existed.
Yesterday when I was reading a simple text message my flipside automatically reset itself and became lodged at the Motorola M logo. I've had this issue in the past before rooting so I just removed the battery in hopes all would work well as before, sadly that wasn't the case. My phone then booted up and only the backlight appeared on the screen causing it to become stuck in the infinite bootloop. I've tried all the different hard resets with the x button and power button, the volume down button, etc. None of them work as only the backlight comes up on my screen so I can't see anything. Is there any way to unroot it or flash it back to stock?
If any of my terminology seems out of place then sorry, I honestly have not a slightest idea what to do nor what is occurring other than the bootloop.
Any help is appreciated and can you please dumb down the answer for me if possible. Thanks!
Click to expand...
Click to collapse
Yup just rsd the sbf back. You will lose everything however so hopefully you've got a backup somehow. Here's the sbf
http://db.tt/H2RuCD8h
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Kippyyy said:
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Click to expand...
Click to collapse
I've had a similar problem as you with my flipside. Are you sure you're using the right key combination to get into rsd mode? If you can at the very least get it into bootloader mode by holding down the volume + key while holding the power button, I'm sure you can get it into rsd mode.
Kippyyy said:
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Click to expand...
Click to collapse
Theres a post here somewhere that has the combo of keys needed to get into bootloader mode. Sorry dont have it saved. Just do a search for it
Okay well I believe I found the thread you were talking about. It mentioned holding the up arrow on the keyboard combined with the power button for 4 seconds. Still nothing. I've tried the x button and power button, the volume up and power button. The thing is my screen won't work period. Nothing shows up but the backlight. So maybe I can or did get it to rsd or bootloader mode, but I can't really tell. I feel like something isn't right here. So I still can't connect it to my pc to use rsd lite.
Kippyyy said:
Okay well I believe I found the thread you were talking about. It mentioned holding the up arrow on the keyboard combined with the power button for 4 seconds. Still nothing. I've tried the x button and power button, the volume up and power button. The thing is my screen won't work period. Nothing shows up but the backlight. So maybe I can or did get it to rsd or bootloader mode, but I can't really tell. I feel like something isn't right here. So I still can't connect it to my pc to use rsd lite.
Click to expand...
Click to collapse
Did you by any chance have the stock launcher app frozen and using a different launcher? Just seems if you are seeing the backlight that possibly it is on the home screen but the launcher is corrupt? Not sure.
I'm not entirely sure. I assume it's stuck in the bootloop because when I power it on the backlight changes shades and then vibrates to signal the screen past the motorola M. Then I can touch the screen and feel a vibration to simulate to slide to unlock and if my usb cable is attached my computer makes the noise to signal it sees my device, but moments later my computer dings to signal device disconnected and my phone goes through the above process again.
I feel as if I can get to the factory reset screen and such because if I time it right I can stop it from doing anything mentioned above and it just hangs as if in a menu of some sort. The downfall is I see nothing and the backlight only appears.
I may just have to scrap it and say well done phone. I can't seem to find a similar issue anywhere on the internet. All the other issues can make the bootloader screen appear and that appears to be my number on problem.
I guess I was just being a complete idiot and thought I had removed my SD card when I didn't. Well now it can connect to my pc so I can flash it. I hope all goes well. I flash it then it should be back to factory settings right?
Kippyyy said:
I guess I was just being a complete idiot and thought I had removed my SD card when I didn't. Well now it can connect to my pc so I can flash it. I hope all goes well. I flash it then it should be back to factory settings right?
Click to expand...
Click to collapse
Yes like straight out the box. The backlight issue just seems to me like a launcher problem but that wouldn't explain why you can't get into bootloader mode. Hmmm strange. Here is another way I just thought of. If it connects to the computer (you said you hear the beep) reflash it via Motorola's site. All the instructions should be there (if they still support it)
Well I was able to flash it using RSD Lite. I could hear the start up tone and such (progress), but unfortunately my screen still won't show anything. I'm assuming the worst and maybe say hardware failure as to why the screen won't boot up? It randomly disappeared when it first went into bootloop and has never come back so that is why I assumed no working screen was a software issue.
Kippyyy said:
Well I was able to flash it using RSD Lite. I could hear the start up tone and such (progress), but unfortunately my screen still won't show anything. I'm assuming the worst and maybe say hardware failure as to why the screen won't boot up? It randomly disappeared when it first went into bootloop and has never come back so that is why I assumed no working screen was a software issue.
Click to expand...
Click to collapse
Yup that sounds like hardware failure. Haven't ever heard of the screen going out on the flipside but the atrix forums are full of them. Maybe you can get your upgrade early. Good luck
My screen broke 6 months ago, so it wasn't used/charged for 6 months. Now I've replaced the screen, but it won't start up anymore. First thing I saw was the warning "low battery", so I charged it for a while. Still, nothing. Charged it for several days, nothing. Checked the battery voltage, 3.80 volts, exactly what it should be I think?
The phone does do something though. When I hold the "on" button, after 5 seconds it buzzes and the screen shows the oneplus logo and android. Just for two seconds, then nothing. Same thing with "on" and volume down, the start-up screen for 2 seconds...
When I use "on" and volume up, I get the screen saying "fastboot mode". And that doesn't go away untill I press "on" for a while.
I can connect it to my laptop, but cant see it. But when I take the battery out while connected to the laptop, the phone will show the "low battery" warning. Connect the battery again, and the logo and android message come on for two seconds...nothing more.
So the screen works, the battery is charged, but no way to turn it on. Tried holding the "on" button for 15 seconds, same result. Just a 2 seconds oneplus logo visible...
I have no clue what this could be, I hope its not completely fubar...
Thanks in advance, Fred Doe
Hey Fred Doe,
I wouldn't like to hijack your post, but I seem to have run into the exact same issue here.
A friend of mine got his screen replaced, and the phone acts exactly the same as yours.
I have disassembled the phone and checked all connections, but everything seems to be correct on the inside.
The phone does seem to boot, and it does boot into recovery mode (it responds to the button presses by vibrating) but the screen just doesn't show anything.
Only when doing fastboot the screen stays on.
Hopefully someone here can point us in the right direction.
there's not much to hijack here...sure sounds like the same problem. At this moment I gave up, guess its a lost cause..
Guys, the exactly same thing here. I've tried to unbrick it but failed.... So far what I know is that bootloader is locked.
I would like to know what steps should us do in order unlock bootloader, get screen functioning while getting access back to bootloder (TWRP) so after that we can install a new ROM!
Any clue from the community of OnePlus 2? This phone is still a good phone! Thnx
Have you guys tried running the msm tool. It'll restore everything to stock if you can it to work. If either of you have magisk installed it can cause issues with charging while the phone is off I believe.
I mean honestly sounds more like hardware issue that a msm wouldn't fix, but it's weird that your screen works in fastboot.
If you do the msm tool though be aware it will wipe everything on your device, and relock the bootloader if it is unlocked.
Like I said doubt it will help, but just a thought.
Edit: Also make sure you use the correct one for your device.
Edit sorry guys wrong forum ignore everything I said. Apparently xda labs thought my OP6T was a OP2.
Sent from my ONEPLUS A6013 using XDA Labs
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
dajosova said:
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
Click to expand...
Click to collapse
But the screen does show up & stays on in fastboot?
I'm no expert but any stretch. I just jumped ship from lg my 6t is the 1st OP phone I've owned. But if the screen does work normally in fastboot then it wouldn't be illogical to entertain the idea that it was a software issue. So I mean this is a bit of a chin scratcher.
Sent from my ONEPLUS A6013 using XDA Labs
Thanks for replying.
IWhen I press Power + Vol. Up it shoes Fast Boot screen. Then I connect cable and sometimes I can use command line but can't unlock bootloader with command line. All methods found indicate to use Recovery but since my screen doesn't work on Recovery I'm stuck.
When I press Power + Vol. Down (for entering Recovery) screen it goes all black but the capacitive buttons and Volume button give back a vibration response, as if it have entered Recovery Mode but since I can't see nothing on screen I can do anything either.
My bootloader is locked because I see that info via command line.
Thanks anyway
PS: I think something is corrupted. My OP2 was unlocked much time ago. I frquently change ROM's and have also updated TWRP. The only thing I did was disassembling the phone in order to change a shattered screen glass.
I've also tried different methods and installed in my pc different Qualcomm drivers, ADB, etc.
I'm getting close to the point of testing with broken touch, buying a new touch screen but with frame or giving up completely and buy a new phone :|
The last option get me in doubt because I would like a phone wich is good and fast and decent battery but not with a premium price... and popular so I can unlock it without hassle in order to install root apk's.