Hey guys, I really need your help here.
I was trying to flash my mate's phone with the newest MIUI today, but it wouldn't work because the SD card wouldn't mount.
Now when he got this phone, it was already rooted. No idea how they rooted it, but there were a few Chinese apps on there. I got my phone (Samsung Captivate) from the same people, and there were also a few random apps on there, but I managed to flash a new ROM on that. It got to the point where I was un-rooting and rooting it over and over again, until I found a Clockwork Mod that worked on the Defy. It mounted the SD card fine, and then it installed the ROM using the "install from zip from sd card" function or something like it. It went fine, said it finished and it didn't lose power half way through the install. Rebooted the phone, and now it's stuck on the "M" Motorola logo. Went to go flash with sbf, and then it came up saying that the battery was too low so it wouldn't program. Well ****.
Tried the Mcgyver mod where you just splice a USB in between the battery and the phone, but that didn't work. I'm hoping that it will just charge from USB while the phone is off? I've read somewhere that it won't charge while it's off, but the LED is white (I think that indicates that it's charging). Occasionally the "M" logo comes on, but it goes away and starts "charging" again. It won't take to the wall charger for some reason, just doesn't want to charge D:
I've been at this for 8ish hours now, does anyone have any advice? Anything at all will be greatly appreciated.
Thanks,
Justin
How long have you been trying to charge it? That's normal behavior for the phone to show the Moto logo and go to battery charging animation when the phone is off. You should be able to power it on if it is plugged in though.
Are you in the boot loader when you try to flash the SBF? Reboot the phone and hold the volume key up to get to the bootloader. Use RSD lite to flash the SBF. I'm sure you've already looked at http://forum.xda-developers.com/showthread.php?t=966537. It's very helpful.
Good luck!
After flashing the new firm , try to make a WIPE before you install the zip !!
Worked for me!!
this should go to the development sector
youll find your answer there under "bricked phone"
Related
Dear all,
I flashed the ROM for my HTC Touch Pro 2 and installed a new one. the new ROM worked well for 2 days, until the night I charged my HTC on the laptop. It keeps rebooting and cannot load the system.
It can enter the color screen by pressing VOL - and Power, and I can still flash new ROM via both microSD card and ActiveSync under the color screen.
However, it still reboots as it enters the "Windows Mobile" screen.
I have tried hard reset and Task29 to wipe it before flashing ROM but both of them did not work.
I have tried different ROMs and I even successfully made a gold card in order to repair it, but it still reboots when loading the system when entering the screen "Windows Mobile" .
Does anyone know what's wrong with my phone ? I am so confused and thinking it is a problem with the hardware.
THX..!
I believe this is what is called a "Boot loop". I ran into this problem once and it was because the phone wasn't fully charged. Turn the phone off and plug it into the wall charger and charge it fully. Then try again. This worked for me, but I can't say for sure if it will work for you.
doublen1 said:
I believe this is what is called a "Boot loop". I ran into this problem once and it was because the phone wasn't fully charged. Turn the phone off and plug it into the wall charger and charge it fully. Then try again. This worked for me, but I can't say for sure if it will work for you.
Click to expand...
Click to collapse
Thank you doublen1, I plugged it on the wall socket and see whether it works or not tomorrow...
It does not work for me, but thank you anyway, hahaļ¼
Sorry, I tried. Maybe someone else will know.
I'll be as brief as I can! Been using a app from the Market called Friendcaster on my rooted Defy running a pays ROM(I cannot remember which one, but it was a early Froyo, been using it for months). Noticed phone running hot after Friendcaster updated, and got a memory warning, turned out Friendcaster was constantly syncing and filled phones memory. Went to delete app, saw a fix, so installed that. Restarted phone, soon started syncing constantly then, and when ever I went into contacts phone locked up. Deleted app, rebooted, and phone went into a boot loop. Went to recovery, cleared phone storage. Phone refused to boot. Tried flashing SKTJRD-3.4.2.74.sbf flash it got to 100%, but never went to complete, even after leaving a few hours.
Phone now won't respond, won't go into recovery, only gets white LED when you connect USB, RSD lite does not see phone. Not sure if the McGuyver hack will help, the battery gets hot if you put phone on charge, and tried a fully charged battery from a visitors phone and still with no response, I understand you only need to do this if battery is flat and you cannot charge phone.
I've had a good search around on here, and on Google but can't find anything that seems to help, frustrated, I might be a new n00b, but this is the first time I haven't been able to solve a problem with a bit of Googling ARGH! Plus my phone doesn't work.
Hope you guys can help, if not what's the chance of Moto/Voda UK swapping out/repairing phone if I send it in?
If you have a new full battery, Can you put Defy into Bootloader mode?
If it cant, it should be realy brick
You should try this thread...
http://forum.xda-developers.com/showthread.php?t=1206708
Try to :
Uninstall RDS and the drivers;
Reboot PC;
Reinstall newer dirvers and rds (the 4.9 version);
Reboot PC;
Connect Defy with USB, wait 1 minute, if not recognized try to press power button and wait 1 min. If not recognized yet, try click on Config-->DeviceID and try both options.
If not recognized yet... try another pc, try another full battery... if this doesn't work there's nothing left to do.
The McGyver trick is dangerous! Don't charge your battery with this method more than 15 minutes!
usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
kasalamite said:
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
Click to expand...
Click to collapse
srry posted last night but would not show the thread... so i figured i couldn't so i tried to post in an existing thread. now i dont know how to delete that other one...
FIXED
well never mind the fact that i loaded a plethora of info onto this post and nothing.
but besides that i got it working. in the disaster recovery tut it only lists using the ruu through a flash... never stating that you can just run the file directly and not go in %temp% and get the rom.zip(excepting for the recovery_signed.img). simply find your version of the ruu that you need, flash back to the stock recovery image (within the rom.zip) relock bootloader place device in fastboot and run from pc.
the only hard part is getting it to charge... dont know how mines took charge but i pluged it into the sockets @ my school (long story read this thread: http://forum.xda-developers.com/showpost.php?p=26156147&postcount=20).
when i pluged it in the light went solid red instantly no blinking. after about an hour of charge i pressed the power button and it went to the splash screen (still was on a older CWM which doesn't support charging) left it at the splash screen for the remainder of the class (about another hour) unplugged entered bootloader.
@ this point i had no security warning under relocked. but i used the power down option, took it home and tried to unlock/flash to the latest version of CWM so i could charge. it worked without a hinge.
anyone know why it took charge on an older CWM?
note i got the phone back up and running and the first thing i did was make a nandroid back up
hi i dont have an answer to your question but i have a question to your answer am curently suffering the same problem i can flash the stock cwm because of low battery, and i know when in boot mode it doesnt charge so i rebooted the phone it took me to the htc logo and its displaying a solid red light does this mean its charging or what (the boot loader is re-locked so i can flash stock cwm but cant due to low charge)
Noob badly. But I think it should be charging. Could b wrong. Leave it there for a couple of hours and try again. Mayb fixed. Give it time and try again.
Sent from my HTC One X using XDA
Same thing is happening to my phone. and its bootloader is locked and cannot be unlocked because of the charging. its usb debugging wasnt turned on either before it went down.
Please help anyone?
Guys I have Htc One X. I rooted it then I thought to install a custom rom (resurrection remix) and gapps. so when I was in the CWM recovery I installed the mod while it was installing it said error no file contents but it installed successfully anyway. after that I installed Gapps but it got an error and said Installation aborted. I then started panicking and I tried to restore the backup but nothing happened, then I re-locked the bootloader with battery below 30% then I used the batch file to charge it then I unlocked it again. Now I want to download a stock rom I tried 2 one was a newer version than what my phone actually is and the other one was a lower version than what my phone actually is. I then tried alooooooooooot to search for the appropriate one for my phone but I didn't find it so I thought to continue with installing custom rom anyway but the problem is that I need to get the new mod zip file and new gapps zip file into my phones sdcard but I can't do that/I don't know how. My phone isn't recognized by my pc ( I can't browse it's files) and I tried using adb in command prompt which is very complicated for me however I searched on the internet and tried to do the same but then it says "adb server is out of date killing" then I found one adbFix.exe that said that the adb in HTC sync manager folder is causing a conflict but then the Fix file said that its ok and no problems are there. Now I need to put custom rom and gapps zip files to my phone's sdcard but I can't. Please I would be very grateful to anyone who would help me and guide me and If I'm posting in the wrong forum or thread then please forgive me for this is my first time I made an account on XDA and my first ever comment/
Alright, I've been working on trying to bring my SGH-I747 out of this perpetual black hole for two days and I'm running out of options. I was working with some Xposed modules, and recently installed Link2SD without issues. I was rebooting after installing new modules (before running any of them) that I downloaded from the Xposed Installer app. My phone shut down successfully, but then never turned back on.
I got extremely concerned because there should be no reason that it so suddenly decided to stop working so I tried to boot into both my CWM recovery and Download Mode. No luck. I would be really happy to see any kind of frozen boot screen, but unfortunately there is nothing. No combination of button pushing, battery removal, or charging (via usb or wall charger) has shown any sign of life except a red light that appears for about 60 seconds if I remove the battery and plug my phone into a charger. I really can't afford a new phone or JTAG so I've tried the SD card Hard Brick .img Restore from another thread with no luck. I'm running Windows 7 x64 and I've tried several different .img writers with similar results.
Any advice would be much appreciated!! :fingers-crossed: Thanks in advance!!!
musiceas66 said:
Alright, I've been working on trying to bring my SGH-I747 out of this perpetual black hole for two days and I'm running out of options. I was working with some Xposed modules, and recently installed Link2SD without issues. I was rebooting after installing new modules (before running any of them) that I downloaded from the Xposed Installer app. My phone shut down successfully, but then never turned back on.
I got extremely concerned because there should be no reason that it so suddenly decided to stop working so I tried to boot into both my CWM recovery and Download Mode. No luck. I would be really happy to see any kind of frozen boot screen, but unfortunately there is nothing. No combination of button pushing, battery removal, or charging (via usb or wall charger) has shown any sign of life except a red light that appears for about 60 seconds if I remove the battery and plug my phone into a charger. I really can't afford a new phone or JTAG so I've tried the SD card Hard Brick .img Restore from another thread with no luck. I'm running Windows 7 x64 and I've tried several different .img writers with similar results.
Any advice would be much appreciated!! :fingers-crossed: Thanks in advance!!!
Click to expand...
Click to collapse
Have you tried using a jig to get into download mode? If that doesn't work, a JTag may be your only option to get the device back working as it does sound like a real hard brick.
Hello there everyone! Let me explain my problem:
Backstory
I have a Samsung Galaxy Nexus GT-i9250 maguro since 7-6 years or so. I've been flashing some roms into it and everything went well since a week ago.
I had installed from a very long time this version of CM "cm-13.0-20160921-NIGHTLY-maguro" and I have not updated it, so I basically was running that from a very long time.
Three weeks ago the phone started behaving strangely, it was closing automatically, and I thought that it was a temperature problem (being a very hot summer) so I did not worry too much.
Everything was working fine, charging and connecting via USB .
Problem
Last week the phone once again died and I tried to boot it up normally as I would normally do, but nothing happened, not even the Google logo popped up.
So I removed the battery and put it back in, the phone booted up to the Google logo, then after two or three seconds the Google logo flashed like brightness went up to 100% and black screen.
Went into fastboot, booted TWRP to see if that was working, and the recovery was working fine.
Things got worse.
At the moment
I cannot get the phone to do anything if it's not connected to a power source.
If the phone is connected via USB, or charger, I can get it to go ONLY on fastboot, and download mode. If I unplug the phone while on fastboot or download mode, the screen brightness goes up to 100% for half a second then it glitches out and goes into black screen immediatelly. I can not access bootloader nor recovery mode from fastboot, because the phone reboots, shows the Google logo and then it dies.
What I tried
Thinking that maybe the ROM went crazy, I followed this guide to flash the phone with all the original ROM and recovery (I downloaded "yakju-jwr66y-factory-4cadea65" and followed the instructions of the guide).
Nothing changed, if the phone is not connected to a power source, it is basically dead, if I put it to a power source it shows the charging logo for a second, then black screen, and I can only boot up fastboot and download mode.
I don't know if this might help but I've also tested the battery voltage and it seems to be fine.
Last thing, if I connect the phone to the PC (with the battery or without) every 2 seconds it shows up that an unidentified device is being detected.
I currently am using a laptop running windows 8.
On my desktop computer the same thing happens (the device detection) but from device manager I see a OMAP4400 (something like that) popping up but at the moment I cannot use my desktop PC since I'm traveling.
I would really like to know what happened to my phone, any answer will be appreciated.
Thanks in advance!
Update [solved]
After doing some research and trying different methods I gave up. But then I realized that maybe trying the stupidest thing could be the solution, so I went to a phone shop and asked them if they had some sort of test battery that I could plug in my phone temporarily to see if it was booting up.
Turns out, it was the battery.
I bought a new battery and now the phone runs smoothly like it's new.
I feel so dumb and I'm so sorry if I've made some of you people waste your time by reading the poem of the first post.
Hopefully this will someday help someone that will have the same problem of my GT-I9250!
(This thread can be closed now)