I have a Photon Q with CarbonROM and TeamWin recovery I think. Someone else set things up for me so I don't know precise versions of things. It was working great for several weeks but suddenly seems to be in a boot loop. The device constantly cycles through green led on, boot logo, then black screen maybe and repeat.
I can get into bootloader screen with volup+voldown. None of the options does anything different except fastboot which I can get to also with voldown.
In fastboot I see "Battery Low" which seems to prevent me from doing any flashing either with fastboot or with RSD Lite.
I edited an xml file or use fastboot and can do operations like
"erase cache"
"reboot-bootloader" - but this sends me back into my loop
I feel as if I must charge the battery somehow. I noticed BP Tools in the bootloader options but that just goes back into the boot loop.
I have seen folks charge the battery by directly hooking up a charger to the battery, not quite ready for that.
Any ideas?
Thanks!
What info I have:
- Photon Q w/ cornholio SIM mod.
- CarbonROM
- Fastboot details:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-51ba9a3, 2013-03-22 20:10:25)
eMMC Info: Size 8GB
Device is UNLOCKED. Status Code: 3
Battery Low
Transfer Mode:
USB Connected
Fastboot Reason: Key pressed
usb connected
- Bootloader
Boot Mode Selection Menu (10.9B)
Vol Up Selects, Vol Down Scrolls
Available Boot Modes:
Normal Powerup
Recovery
AP Fastboot
Factory
BP Tools
You need to charge the device. Plug it into the wall and try to get some juice into it.
You should be able to charge from TWRP if you can make it to recovery.
arrrghhh said:
You need to charge the device. Plug it into the wall and try to get some juice into it.
You should be able to charge from TWRP if you can make it to recovery.
Click to expand...
Click to collapse
Thanks! I have tried that. Left it plugged into the wall for about 24 hours or so. No luck. Still Low Battery and boot loop. Recovery fails in a similar way.
I'll try charging the battery either in another device or by hooking up power directly to the battery for 10-15 minutes.
in the first post you wrote u can boot to recovery.
so put a rom on your sd card and boot into recovery.
while your phone is hanging on the wall charger.
so you can flash the rom via recovery. it worked for me when my battery was low.
huhu1312 said:
in the first post you wrote u can boot to recovery.
so put a rom on your sd card and boot into recovery.
while your phone is hanging on the wall charger.
so you can flash the rom via recovery. it worked for me when my battery was low.
Click to expand...
Click to collapse
Ah, no. I can't get into recovery. It gets there but does a bootloop just like the logo screen does. Never get anywhere that I can do "anything".
I am now charging a battery from a Droid 4 that I think is the same, EB41 minus maybe a heat sensor? Hoping I can swap batteries and get into fastboot.
I have resolved this!
- used the EB41 battery from my Motorola Droid 4
- charged it to 50
- grabbed a stock image from the interwebs (hard to find actually as http://sbf.droid-developers.org/ is gone apparently) asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml
- booted up to fastboot with power+volume down
- says Battery OK
- grabbed the motorola version of fastboot. It has "Multi-Flash" which is required for the system.img.
- used the xml file inside the stock image as a guide on which fastboot commands to run on Linux
- skipped erase "userdata" because I wanted to try and save it
- see my "me-too" comment here about Multi-Flash: http://forum.xda-developers.com/showpost.php?p=63571551&postcount=7
Thanks all.
I had a similar problem. I could not even boot into recovery, only fastboot. I don't remember exactly how I solved it, but I seem to remember that the phone would not charge when off but charged only when left in fastboot. I managed to get enough charge to get into recovery and flash a new image.
Related
My phone is rooted with stock rom. The only changes are listed below
Froze bloat that was safe
changed bootanimation to stock samsung
replaced some apps with inverted versions of themselves (ex. google +, stock messaging)
Here goes:
I was using navigation and I noticed that my phone was off after I had finished. Nothing worked at all, I could not boot into recovery or download. I connected the phone to a charger and red led flashes and an empty battery appears. The battery was full. I could reboot the phone while on the charger, but it would shut off as soon as it got to the homescreen. While off, If I pressed the home button, the green battery would appear as if it were charging. From here I could boot into recovery and download mode. The phone will only boot into these modes while connected to the charger. Here is where it went bad. I attempted to restore a backup while the phone was on the car charger and my car charger got pulled out in the middle of a restore. No charger meant that the phone shut off mid restore. Now, when I plug in the phone, the red led appears and the empty battery with a circle inside appears and then goes away. This repeats itself over and over and the phone buzzes when the empty battery reappears. I can still boot into download mode but not recovery. If I try to flash the stock samsung rom via odin, it says that it passes, however upon automatic reboot the samsung appears and nothing else. After the samsung appears the phone just continues to buzz every 5 seconds or so as if it is trying to do something. Could it be a bootloop? I have done a ton of searching here and now I am resorting to help! Your time is appreciated and beers on me if you can help me get my phone back to normal.
try:
Section 6: Using Odin to flash back to Stock from any rom/ recover from a soft brick
*Move everything you dont want to lose from internal sdcard to external sdcard as this will reformat your internal sdcard!!
Step 1: Download and install these files to pc:
Odin- http://samsung-updates.com/Odin307.zip
Samsung Driver- http://tinyw.in/Fdoz
Step 2: Download one of these Factory STOCK Bloated 4.0.4 roms and the stock kernel to your pc:
*You will need to unzip these files with a .zip program such as 7zip to extract the .tar files!
VRALG1- http://goo.im/devs/invisiblek/i535/C...w_ship.tar.zip(Yes this works with the stock VRALF2 kernel!)
VRALF2- http://goo.im/devs/invisiblek/i535/H...w_ship.tar.md5
Rooted Stock VRALF2 by MrRobinson(aka root66)- Here is the Torrent link
Stock VRALF2 Kernel- http://samsung-updates.com/kernel/Sa...LF2_Kernel.zip
Step 3: Power device off, then hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "download mode"
Step 4: Open Odin and connect the oem usb cable to pc & device, you should see a "comport #" in upper left hand corner of odin
Step 5: Uncheck auto reboot
Step 6: Click on the PDA function of odin and select the Stock Kernel you downloaded in step 2. Should take roughly 1 min, then odin will say pass/reset
Step 7: Click on the PDA function of odin and select the Stock Rom you downloaded in step 2. Should take less than 8 minutes, then odin will say pass/reset
Step 7: Disconnect usb cable, then pull and reinsert the battery
Step 8: Press and hold the volume up/home/power keys until you see a green android, you should boot into stock recovery
Step 9: Wipe data/factory reset
Step 10: Reboot! (You should now be booted into factory stock, locked, and bloated ICS 4.0.4)
*If your internal memory(EMMC) has corrupted data partitions and my method above wont recovery your device, try this: http://forum.xda-developers.com/show...4#post30477064
And thank DroidStyle for providing this ^^
I will try your method. I believe I have completed these steps but I will try again. The link you supplied is not found.
Should the stock rom file be a .tar or .tar.md5? The kernel was a .tar and I have an official samsung vralf2 that is a .tar.md5
I tried your method and the empty battery is gone , but it doesnt get past the samsung on booting into recovery and continues to buzz every few seconds with a blank screen.
For some reason the phone will not recognize the battery. I tried a new one at verizon and the same thing. I can now boot into both recovery and download mode when connected to the charger , but the phone shuts off as soon as it boots and shows an empty battery with a circle in the middle. Sometimes it does not make it through the verizon boot animation and sometimes it makes it all the way to the homescreen and I can make a few selections before it turns off. After flashing the stock kernel and rom in odin I believe i am completely stock, however I do not want to chance sending the phone into Verizon. I believe that I saw a thread before this happened to me talking about having to calibrate the battery in some way and it had an item to flash in order to fix the problem. I can not find it now. Any ideas? Now that I can access recovery is there anything else that can be done? Why won't the phone recognize that it has a battery? As soon as I pull it off the charger it shuts off. When it is on the charger it appears to be charging and the green in the battery appears to be at about 80% but the level does not move up or down at all. Thank you for your help ahead of time.
I replied to your other thread seems to have been deleted.----- Boot into download mode and let it sit on the charger for 30 minutes, remove from charger pull and reinsert battery. Boot your phone regularly. Charge/profit
Sent from my VzW Galaxy s3 using xda premium
Ok i am in the process right now. Thank you, and I hope this works. If it does not and If i try to download bootchains , kernel, modem , and stock rom once again, is there any particular order that this should be done in? Also, is there any way that I can get cwm recovery on my phone? I can not get my computer to recognize the phone in download mode or recovery mode to push it with adb. If I could get cwm on the phone would wiping battery stats and fixing permissions do anything?
Wife was running CleanRom 2.1 for a week or so. Yesterday she goes to wake the screen and the phone wouldn't wake by pushing any buttons. She pulled the battery and tried to boot the phone with no success. At this point we are stuck with the attached (IMG_01.jpg) image when plugging the phone into a USB port. Plug it into the wall charger and you get the same image however leaving it on this charge for a while brings IMG_02.jpg. Unplugging the phone from the cable results in no power at all to the device. This means no Download/Recovery Mode from battery only.
On to plugging into the computer. By quickly inserting the cable and pressing the keys to enter Download mode i can successfully enter Odin mode and flash files. From here i have flashed full stock images and still no full boot success.
So, next I can boot into recovery (sometimes, again only plugged in) I was able to wipe following stock odin flash. After rebooting from recovery i can see the samsung and galaxy sIII boot logos then the stock VZW 4GLTE boot animation(with sound). once i get to the language select screen and move to activation the phone shuts off and goes back to the empty battery with a circle in the center (IMG_01.jpg).
So far I have tried:
1. Different USB ports/cables - Incl. OEM (connection appears to be fine to the system either way though)
2. Flashing full stock images in odin with PASS results.
3. Ive tried to unbrick using the methods found here: http://forum.xda-developers.com/showthread.php?t=1840030
Im looking for any help or suggestions on moving forward here. Overall there is no power to the device without plugging in the cable. I have tried another battery still with no power. I have thought about flashing the insecure bootloader however i have not found a way to do this in Odin if it is possible at all.
ODIN MODE (Reads as follows)
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLED
Thanks in advance for any help at all. If you share a similar problem please post as well, may help narrow down the cause and eventual fix.
With my ability to access ODIN MODE and boot to the setup screen, does this mean i have a good chance at recovery?
Looks like you might have a bad battery.
I tried another battery and that's not working.
This morning I had a green LED (charged) light. I woke the screen to the lock screen and it seemed to stay on. I couldnt get past the activation since the sim is no good. ( I had to deactivate it with vzw to activate a temp phone.) I eventually pulled the plug to see if it would hold charge but it just shut off and I wasn't able to boot up again.
The same thing happened to my first s3. You will need to get a replacement.
Previously, I was using Lineage 13 on my device. I wanted to restore it to stock ICS, so I flashed some backups I found here https://forum.xda-developers.com/showthread.php?t=2295643.
However, now the phone is stuck on the loading splash screen and won't boot. Turning the device off, no combination of buttons will do anything (no recovery, no menu that let's you choose).
Using adb to try to reboot into recovery or fastboot just shuts it off, and it reboots normally, still stuck at the splash screen.
I have noticed that now when the phone powers on, I don't get the screen warning about an unlocked bootloader anymore.
I am sort of new to this, so any help would be appreciated. Thanks.
Use RSD Lite to restore the phone to factory defaults.
I've tried this but my device does not show up. I do have the correct drivers installed.
thatlegit said:
I've tried this but my device does not show up. I do have the correct drivers installed.
Click to expand...
Click to collapse
I haven't done this in literally years, but I think the device needs to be in fastboot mode.
Make sure you follow all the instructions carefully.
arrrghhh said:
I haven't done this in literally years, but I think the device needs to be in fastboot mode.
Make sure you follow all the instructions carefully.
Click to expand...
Click to collapse
I can't get into fastboot right now. Not when it's shut down or through adb.
thatlegit said:
I can't get into fastboot right now. Not when it's shut down or through adb.
Click to expand...
Click to collapse
You've tried the power+camera (I think that's the combo) to get the menu? There should be a button combo to bring up a menu to enter fastboot, recovery, etc.
If you can't get to fastboot, I don't think there's anything that can be done. I've never (soft) bricked this device so hard that fastboot didn't work...
Test to flash phone via rsd with factory cable OR pull out battery and connect 4V from power supply directly to battery contacts.
If is still dead or rsd gives you writing error then this problem is for 90% bad emmc connection or bad emmc self.
Is needed to desolder metal cover and heat emmc with approx 380-400°C for few seconds and then very little and carefully push from side to emmc with needle.
If this not helps too then desolder emmc, make new balls and solder it back.
...you can find emmc chip under large metal cover on keyboard side on mainboard.
thats all
I was charging my mi 4 it had around 70% charge when it completely went black and started to vibrate again and again like it was rebooting the screen is lighting up but there is no logo and the phone is not booting up completely, i cant access recovery mode as it wont stop rebooting. I have not done anything special to the phone.
SilverXDA said:
I was charging my mi 4 it had around 70% charge when it completely went black and started to vibrate again and again like it was rebooting the screen is lighting up but there is no logo and the phone is not booting up completely, i cant access recovery mode as it wont stop rebooting. I have not done anything special to the phone.
Click to expand...
Click to collapse
Back up your data if you can.
If you still have adb, try adb pull your userdata partition.
If you can still access to fastboot mode, try
- flashing a fastboot rom if you can find one.
- flashing a recovery in fastboot could help as well (so you could flash recovery rom).
Hi, ive been having problems with my pixel 7, it seemed like no matter how i flashed it it still wouldnt work 100 percent properly. even if i used android flash tool. So today i flashed the disable-verity/verification flags and then booted into system and I turned off auto system updates and did adb reboot bootloader. It didnt reboot into the bootloader but instead shut off and showed the icon for a battery that wasnt charged. holding voldown and power did notheing immidiately so I unplugged the usb and held power and volume down. It went into the bootloader, however this time the readon was not vol down pressed but "bootonce-bootloader" instead. anyone ever see this or know what this means?
PochiRaccoon said:
Hi, ive been having problems with my pixel 7, it seemed like no matter how i flashed it it still wouldnt work 100 percent properly. even if i used android flash tool. So today i flashed the disable-verity/verification flags and then booted into system and I turned off auto system updates and did adb reboot bootloader. It didnt reboot into the bootloader but instead shut off and showed the icon for a battery that wasnt charged. holding voldown and power did notheing immidiately so I unplugged the usb and held power and volume down. It went into the bootloader, however this time the readon was not vol down pressed but "bootonce-bootloader" instead. anyone ever see this or know what this means?
Click to expand...
Click to collapse
Question: Is your Pixel Carrier Locked?
It's my first post leave some comments if you find it helpful...
I was using a Linux box with a BLU oem USB c charger.. wait till the battery percentage shows 0% or 1% hold the volume down button while pressing the power button just get to the bootloader and ..
Once your able to connect it using fastboot... Either use fastboot reboot recovery or select it from the boot menu..
Download the platform tools from Google.. also the latest OTA for your device.. extract the zip to a your Desktop then toss the compressed OTA... In that folder open terminal or cmd... Run adb sideload OTA.zip..
Reboot one more time to manually enter recovery WIPE DATA nd Factory Reset..
Reboot back to bootloader fastboot reboot sideload or reenter recovery>apply OTA from adb..
Adb devices should return device and sideload... Issues the command adb sideload OTA.zip one last time... Nd your back in business... My friend