Hi Everyone!
I have an XT1641, which previously had a charging pin problem.
At the Last week, it started to reboot only many times until it suddenly shut down and didn't light anymore.
When plugged into a charger, the white light flickered.
Since I thought it was still a charging pin problem, make the change.
The cellphone works seemed to restart, but it continues with the same problem.
Sometimes the bootloader works ( Power + Vol -) and sometimes No.
I already tried everything. Install ROM STOCK, I made it blankflash (none worked "waiting for firehose to get ready" ).
It seems to be a firmware or similar problem, but I can't find the solution.
Previously, you never had a custom ROM installed, or root, or anything; at this cellphone
Thank you!
PD: SORRY FOR MY ENGLISH
How did you try for installing stock rom? Check usb drivers installed in your pc
przvlj said:
How did you try for installing stock rom? Check usb drivers installed in your pc
Click to expand...
Click to collapse
By Fast Boot (when it worked).
Now, after a week of turning it off, the cell phone turned on again without problems.
Related
Hi
I have an HTC Legend, but it's so buged
When i try to turn it on, it has to be connected to a cable, or else it goes into bootloop.
I've tried to make a factory reset, tried to install a different RUU, tried to downgrade it, but the adb shows no devices.
I've run out of ideas, so please help me
Somehow I managed to get the same issue. It goes into bootloop unless it's connected to a pc... I already went back to the stock 2.2 rom and deleted everything but nothing changed.
Funny thing is that after I got this problem I first installed the old 1.31 rom and that one worked without the usb cable. The 2.05 to. But as soon as I installed the 3.14 it started again with the bootloop thing...
Did you find any solutions?
Ok, after installing the stock rom I noticed that the usb is not working so I just needed to unbrick the phone and that solved a problem.
(I just did not think about that before because usb was still working when I installed cm7 but the bootloop problem was already there.)
CrWEE said:
Ok, after installing the stock rom I noticed that the usb is not working so I just needed to unbrick the phone and that solved a problem.
(I just did not think about that before because usb was still working when I installed cm7 but the bootloop problem was already there.)
Click to expand...
Click to collapse
What exactly means unbricking the phone?
I got simillar problems: since CM7 final I have bootloops when my phone isn't connected to power. Also I can't mount the sd card from a computer (when I press the button on the phone it works for like 5seconds and then unmounts again).
I already tried downgrading again to CM7 RC4 and other versions(I always wiped before), but the problem persists. Also upgrading to another radio version didn't work .
virus54 said:
I have this problem too
but i found one way to stop this rebot loop util u reboot your phone again...
enter into recovery mode and via adb write the command
adb devices
Click to expand...
Click to collapse
now press volume up and power button(when you see black screen with phone)
press on reboot system now and it will work for you for one time
each reboot you have to follow those steps
Click to expand...
Click to collapse
after this do a usb brick to use your usb http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/
I had exactly the same problem, the USB unbrick linked to above solved the problem. If you need the image hex edited for you give me a shout
My galaxy s was hanging on boot (at the big S logo). This wasn't the first time and last time I had tried everything and reflashed. Yet this time odin crashed (windows gave me the 'Odin.exe stopped working' notification) and my phone powered off...
Now it won't give me anything, not download mode, OS or recovery (screen stays black, not even sure if the phone boots at all, hardware buttons also stay off)
Couldn't find anything usefull, any thoughts?
Cheers
Try the JIG to force it into download mode and try again. If odin crashes again, try flashin within windows safe mode. Sometimes it prevents crashing
mrjraider said:
Try the JIG to force it into download mode and try again. If odin crashes again, try flashin within windows safe mode. Sometimes it prevents crashing
Click to expand...
Click to collapse
Will that force the device to boot too? If thats true I will give it a shot this week, hopefully. See if i can get hold of one somewhere.
Thanks for the quick reply
tinyhitman said:
my phone powered off...
Click to expand...
Click to collapse
I Think this is the problem, you may have tried flashing when you had little battery charge and that will cause serious problems as bootloader would have failed.
your only option would be read the My Android Solutions about Problem:- Cannot enter Download or Recovery Mode
xsenman said:
I Think this is the problem, you may have tried flashing when you had little battery charge and that will cause serious problems as bootloader would have failed.
your only option would be read the My Android Solutions about Problem:- Cannot enter Download or Recovery Mode
Click to expand...
Click to collapse
EDIT: I thought it was weird indeed that my phone powered off, since it had a full/near full battery (at least it told me)
Great thread ! Yet unfortunately none of the steps work for me up untill the JIG, I'll have to get hold onto one or make a homemade one (only got a single micro-usb at the moment, so that'll be a sacrifice) Havn't really got a lot of time on my hands but eventually i'll have to give the JIG a shot.
Realize that it seems like the phone isn't powered at all.
EDIT: no "usb device detected" notifications/sounds in windows when plugged in (for adb)
Also: My volt-o-meter told me that my battery outputted 6+ volts... can't seem to reproduce at the time of writing this though....
tinyhitman said:
EDIT: no "usb device detected" notifications/sounds in windows when plugged in (for adb)
Click to expand...
Click to collapse
could be a USB cable failure (guessing) try
2) Problem:- Cannot connect to PC or Unknown Device, getting Code 43 or any other code or NO response when using USB cable in My Android Solutions
did you tried to remove the battery several seconds holding down the powerbutton and put it back again?
btw i also had issues with a galaxy note and a broken usb cable. screen was black because of an empty battery, you should try an other battery maybe a friends one
hi all i bought defy about a year ago as a second phone from ebay with cm7 installed.last week i purchase another phone and give my 7 years old daughter. however i reset everything and phone turn old version blur mod then stuck on m logo i download rom and sort the problem.
real problem starts now i try to install cm 9 download all required files wiped the phone and install the rom however it didn't restart stuck on black screen and only white led when connected with usb also didn't connect or recognized by rds lite.I found tread battery wake up from i think was ''mggrager'' or something else finally rds recognized the phone and install another sbf but still stays same as black screen and white.i read so many threats on this side or others and each i installed custom roms without clearing cache
battery replaced with replacement battery also original
all drivers installed
it doesn't respond any buttons or usb connection
rds only with battery jump
please help what to do
I'm having the same problem as you are, i believe... I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport... I take my phone home, not really giving it much importance, and i noticed it would never charge and/or turn on, and that when I connect it to the pc, nothing happened other than the white led coming on.. RSD won't recognized it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
I don't know if i should make a thread of my own.. i think we have the same problem, and i REALLY need my phone back.. so i guess we could just help each other fixing it somehow....
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOLA_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
pasha543 said:
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
Click to expand...
Click to collapse
bump 4 help
Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot
easyxx said:
Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot
Click to expand...
Click to collapse
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.
kophyo07 said:
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.
Click to expand...
Click to collapse
If your phone displays Downloading... and fastboot keeps saying waiting for device then there is something wrong with the installed ADB driver. Check some of the posts in this forum like this one on how to fix this. http://forum.xda-developers.com/yotaphone-one/help/yotaphone-2-yd-206-china-flash-firmware-t3306797/post69311402#post69311402
Strange that you had an OTA (Over The Air update). You didn't do anything between the SIM/Google registration and OTA ?
Normally there are no OTAs allowed on yd206 phones bought from China/HK , where did you buy it ? Chinese retailers have their own firmware that they put on phones , for me , maybe you had bad firmware installed.
The warranty of your phone is voided if you flash yotaphones bought from China and HK .
When you use yotaflasher do you get error message or "waiting for device" ?
To flash the Yotaphone , it should be in developer mode , but you couldn't put it in this mode because it first did the OTA that started your bootloop. Android apps are updated like that ("installing x of 127") when it gets updated to lollipop. Normally the OTA should have worked OK. Did you allow enough time at the Yotaphone logo after the first reboot ? It stays on this logo for 5 minutes before starting. I made this mistake.
The OTA started just after you set up Google etc ?
If so, normal yotaflashing will never work, but at least you havent broken the warranty . The thing we need to know is what exactly happened when you tried to flash , what errors messages appeared ?
If you did not put the phone in developer mode, then you cannot easily flash the phone, so your best possibility is to return the phone. Normally you can contact the seller by chat or email . Some are very good in exchanging.
It IS possible to flash your phone using fastboot, but I would not personally attempt it and you would lose your warranty . You need rootkits, SDK toolkits, universal drivers and images. Google "bootloop without USB debugging".
When I flashed my yd206 , (after many attempts) I flashed my yd206 to yd201 Russian KitKat ROM first and then did an OTA to lollipop.
So everything was working fine a few minutes ago until i put my oneplus2 in my pocket, after sometime when i removed it there was no sign, nothing seems to work, it wouldn't boot neither into bootloader nor into recovery, and when i charge there is no indication either, anyone knows what would the problem be? or is there any way to make it work?
have you tried to enter QHS HS-USB mode?
lockmunk said:
have you tried to enter QHS HS-USB mode?
Click to expand...
Click to collapse
how to do that?
hold press volume up+volume down and plug in usb cable..see whether it detected something like QHS USB in device manager
lockmunk said:
hold press volume up+volume down and plug in usb cable..see whether it detected something like QHS USB in device manager
Click to expand...
Click to collapse
bro it ain't detecting anything, everything was working fine then how suddenly it looked like it's dead?
Did you have a custom ROM on it? Did you install a custom kernel? Were you tweaking around voltage/CPU etc..values?
Some more information about the "crime scene" would be nice..
rajatdixit said:
Did you have a custom ROM on it? Did you install a custom kernel? Were you tweaking around voltage/CPU etc..values?
Some more information about the "crime scene" would be nice..
Click to expand...
Click to collapse
ok so i had flashed h2os a week ago everything was working fine until yesterday when suddenly it stopped showing signs, neither does it shows charging signs nor does it boots into bootloader or into fastboot mode, i did not tweak anything either, i charged it the whole night but it ain't showing any signs yet, battery was working fine the other day so can it just die so suddenly?
phorcus said:
ok so i had flashed h2os a week ago everything was working fine until yesterday when suddenly it stopped showing signs, neither does it shows charging signs nor does it boots into bootloader or into fastboot mode, i did not tweak anything either, i charged it the whole night but it ain't showing any signs yet, battery was working fine the other day so can it just die so suddenly?
Click to expand...
Click to collapse
may be you should try hard reset.
check if it gets detected by your pc in auto restore tool software. your phone won't show any signs even if it gets detected by your pc in such situation.
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Aniket_IITM said:
may be you should try hard reset.
check if it gets detected by your pc in auto restore tool software. your phone won't show any signs even if it gets detected by your pc in such situation.
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
but the phone is not detected at all