Hi all,
Yesterday my Jiayu S3 crashed and rebooted, after setting an alarm clock and using the Spotify app. However, it did not reboot into the OS as usual. It did not even show the Jiayu logo, but the phone vibrated (sign that it's booting), screen turned on, phone turned off again, repeating this cycle over and over (not the traditional bootloop as I know it). I was running a rom based on the original rom, with some slight modifications. This rom was running stable for more than a week. I know my way around Android, and am used to switching roms, flashing etc.
Right away, I checked the following things:
- Battery removal didn't help (I did not forget to put it in again ofcourse )
- Phone doesn't go into it's charging cycle when charger is connected
- I do NOT have access to recovery
- I can, however, access the boot menu (Volume up + power key, options: Normal boot, recovery, fastboot)
- I can get into fastboot mode (haven't tested ADB yet), that's the only thing that's still working
I tried to flash the original firmware using SP flashtool, and I am still able to upload firmware on the phone! I am sure that I'm using the correct ROM, and tried different PC's and drivers. Got a few succesful flashes, but still bootlooping.
I also had the idea that my battery was empty (didn't charge it overnight), and measured the battery at 3.52 V. So it was pretty empty but not that empty that it doesn't boot. In an effort to charge the phone, I left it bootlooping for an hour or so, and later on it turned out that it only drained the battery further, 2.99 V.
I didn't want to kill this battery so I did use 2 other batteries from an old Jiayu G4, which appear to work if you turn them around and hold them against the pins (note: I knew what I was doing here ). After a lot of Googling, and seeing a lot of generic "how to fix any brick" stuff I was not able to revive my phone again.
I still believe (and hope) that the error is on the software side of the phone. All the partitions should be ok and in working order according to SP flashtool.
Now this is where my knowledge stops and where (hopefully) your help comes in. What can be corrupted that I haven't checked yet? Do you guys have any suggestions to revive this "high-end" phone again? Once again, it did not happen because of bad flashing or something like that, it happened randomly when I was using the phone normally. I tried to be as accurate as possible (long story), but if there are any questions I'm happy to answer them.
Any suggestion is welcome!
Thanks in advance.
Bump..
Anyone?
bump
Related
I didnt reflash galaxy tab, was probably installing some software from the market. Now the battery has died, i restarted it and it keeps restarting after the logo... help, i dont know any recovery options :S Kies has nothing
I'm having the same issue. It sounds like a fastboot -w is required to wipe out userdata and cache.
Unfortunately I can't seem to get my PC to recognize my tablet in fastboot mode. I might have to send my tablet back to Samsung to get reflashed.
kolor9 said:
I didnt reflash galaxy tab, was probably installing some software from the market. Now the battery has died, i restarted it and it keeps restarting after the logo... help, i dont know any recovery options :S Kies has nothing
Click to expand...
Click to collapse
That has happened to me when I was having battery issues. I was able to keep connecting and disconnecting the charger cable until I got my tab to work again.
yeah might be that as well, i noticed strange behavior for last weeks, suddenly it started draining battery very fast or shutting down in the middle of the battery. running very slow and freezing.
when connected to pc it always goes: connect/disconnect/connect/... (hearing windows sounds for that)
i fully charged that yesterday, will try to boot today.
HOWEVER i was able to get into recovery menu, wipe/delete cache, sdcard, factory reset, etc.
might be that firmware/rom/bootstrap has been fuked up when battery died suddenly?
sharing experience
Hi guys
I didn't install new apps, no updates, no battery weak problem, no connect/disconnect problem, had DiP7's 2.3.3 rom since 10th July, very stable & solid. Not a single problem.
But my SGT GSM suddenly reboot-loop. I was just reading emails, reviewing photos.
Solutions: -
Enter recovery mode, Wipe date/Factory reset without wiping dalvik/battery stats etc. It just works and could run Titanium Backup to restore if I needed.
But ............................. Alternatives??? (New Life???): -
Tried HC_RC1, was good, but not daily driver yet, finally jumped to BOCA's 2.3.7, still playing around.
You may need to open up your tab and do the battery disconnect procedure. I finally had enough with my tab and opened it up. So far I am happy again.
i have some issue to
anyone can resolve it?
always reboot , and if i want to open keyboard, it restarting again
Thanks for the suggestion but it did not work for me...I experienced same problem you mentioned below except I had gone on vacation and my tab battery died and when I was able to recharge it, it just recycles through the Samsung logo!
Tried all the suggestions on this site and no luck so far...I'm guessing it might be time to take it in to Tmobile and see what they have to say, probably not much!
I'm not ever going to get a Samsung tablet again...Asus from here on out!!!
cx5 said:
Hi guys
I didn't install new apps, no updates, no battery weak problem, no connect/disconnect problem, had DiP7's 2.3.3 rom since 10th July, very stable & solid. Not a single problem.
But my SGT GSM suddenly reboot-loop. I was just reading emails, reviewing photos.
Solutions: -
Enter recovery mode, Wipe date/Factory reset without wiping dalvik/battery stats etc. It just works and could run Titanium Backup to restore if I needed.
But ............................. Alternatives??? (New Life???): -
Tried HC_RC1, was good, but not daily driver yet, finally jumped to BOCA's 2.3.7, still playing around.
Click to expand...
Click to collapse
ceperz said:
i have some issue to
anyone can resolve it?
always reboot , and if i want to open keyboard, it restarting again
Click to expand...
Click to collapse
if its gsm go to overcome restocking method
Just go into recovery mode by holding volume down+power button.
Wipe everything then do a hard reset in recover screen.
If not do this.
Go here and download gbsafe_v5. Zip. It has everything you need including drivers and odin files
http://forum.xda-developers.com/showthread.php?t=1317384
Also download overcome-kernel_4. 0.tar file as well.
Once you downloaded these two files plug in your tab to usb and wait for that phone and pc screen or download mode screen.
Go here and follow steps up to 10.
magrathearoms.weebly.com/install.html
Your phone is now stock'ish GB with OC'ed kernel including custom clockwork recovery. This version also comes with phone capabilities unlocked so you can use it like a real phone. All you have to do is load tmobile. Modem file. If not then use as wifi only.
Sent from my LG-P999 using xda premium
It's been few days since ur post. But I'll give it a shot for trying to suggest.
Try holding power button for 8 seconds to properly power off. Then charge it for a good hour before starting the unit.
Else just keep charging it. Standard times are 4 hours to get zero to 100%.
Once my power used till zero and no response what so ever even after charge 5 mins. Finally let it charge 1 good hour & it came back to life.
Good luck.
Regards cx5, on the move via xda tapatalk.
fabricatedhero said:
Just go into recovery mode by holding volume down+power button.
Wipe everything then do a hard reset in recover screen.
If not do this.
Go here and download gbsafe_v5. Zip. It has everything you need including drivers and odin files
http://forum.xda-developers.com/showthread.php?t=1317384
Also download overcome-kernel_4. 0.tar file as well.
Once you downloaded these two files plug in your tab to usb and wait for that phone and pc screen or download mode screen.
Go here and follow steps up to 10.
magrathearoms.weebly.com/install.html
Your phone is now stock'ish GB with OC'ed kernel including custom clockwork recovery. This version also comes with phone capabilities unlocked so you can use it like a real phone. All you have to do is load tmobile. Modem file. If not then use as wifi only.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Dont see a thanks buttom i appreciate it MAN !!!
If it really happened after installing bad apps it will only wipe recovery mode
I apologize already if this has already been posted before, I couldn't see one that had my issues so I'm making this thread.
OK, so here is my problem and everything that I can think of that I've done to my phone.
Today I tried to restart my phone as it was getting a bit sluggish. When I did it started booting fine then the animation sound stopped while the droid eye was being put together. Now my phone will not pass the droid eye during the boot phase. I press the power and both volume buttons and after a few seconds it starts itself back up again. I do the power button and down volume buttons and it still does the same thing. I've even performed the factory reset twice and it still won't help.... And no matter what I do it keeps booting itself back up on its own.
What I've done to my phone:
I am rooted but never got the boot loader unlocked since i waited too long and the last update wouldn't allow the boot loader unlock methods anymore. I have used titanium backup app to delete some system apps for example the Verizon football one, slacker radio, and any of those useless apps that I never use. I haven't deleted anything lately and have restarted my phone many times since. I have been delaying the recent update hitting no or not now, whatever it says. I thought that I said no today on the system update as well. Even then my phone was working before I restarted it.
PLEASE I hope that there is something that I can do to fix my phone because I'm forced to use my LG Vortex again and my upgrade isn't for another year..... I don't want to buy a new one since this phone has been great and I'm almost certain that if there was a way to reinstal or flash the droid razr m OS that that would fix my issues.
Thanks in advance for your input and please know that I'm a novice with this kind of thing so you will have to explain the process to me. If i have instructions I can definitely follow them.
THANKS!
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here http://sbf.droid-developers.org/phone.php?device=8 (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ .
OK, so I deleted the cashe and still a no go. For the second step of getting the .3 to regain root. would it be possible to get an even earlier version so I can unlock the boot loader? Also when you say flash in RSD, what is that? I know of the AP flash from the first menu, is that something inside of Recovery menu options?
Thanks for your help!
**UPDATE**
THANKS! I was able to eventually figure it out and used the last option that you said and my phone works! Now working on getting root back. Thanks again!! But I really would like to know if I could do the same thing but with an earlier version to unlock the bootloader.
Droid Razr starting up issue
Hi guys, I am facing a weird issue with my Droid Razr and hoping pros to help me sort this out and get my phone running.
I am using Droid Razr but since last one week it is not starting up. Let me elaborate, currently it is switched off and not getting up. While starting it pass through M logo but can't go ahead for startup animation (droid eye animation). Even after leaving on that animation for entire day, it is not going ahead of that.
However, if I connect it to a wall charger (while it is off) it shows battery getting charged. It is taking a usual timing of 90 minutes for full charge.
I have important pictures and data into phone memory is there any way to recover it.
I would appreciate if you can guide me to get my phone up and running as usual.
RikRong said:
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: .
Click to expand...
Click to collapse
Well when I charger my phone and around 12-50% my phone would just switch off and would require charging again to turn the phone back on. It then says my battery is completely dead. Wierd thing is if I boot staight to the boot loader( vol down + power) the phone boot to the bootloader and not switcher off.
I previously tried different roms which still didnt help.
I tried different kernals (only help battery to last longer)
Tried another NEW battery (same issue)
Any help guys? Sorry for my newbier questions but at this stage I dont know what to do. I even tried the lastest version of L which is 5.0.2
I tried battery recalib but it didnt work, I will try to do on the latest version of android? Can any one tell me a good app? I used a random one off play store.
bump
Hi! It's my first time making a thread here so guidance is greatly appreciated. Here's how everything started:
I was just casually using my phone (at the time I was using the built-in browser of google assistant, just looking at some news) then suddenly my phone crashed (I've experienced this before every time I was using the google assistant built-in browser, a simple browser can crash this phone?). It just restarted like it normally would, then, after using the phone for a few minutes, it froze again! I waited for it to reboot but now it just powered off and won't turn on (it won't show any sign of life, no logo, not even an icon when I tried to charge). D:
I figured to have it checked by a local technician and when he tried to plug a charger in, a display showed it charged (found it weird but happy at that time). I figured it was the charger so I bought a new one.
So I got home to charge it fully and when I turned it on, it worked normally. However, when I tried to turn my wifi on, notifications popped up and suddenly it froze again! After that, it turned off and when I tried to turn it back on, I got this dreaded red texts on a black screen:
Bootloader exception ( RST_STAT = 0x10000)
Exception: do_handler_sync: DABT_EL1(esr: 0x9600010)
RDX, do not reboot*** ext4_wait_block_bitmap:494: Cannot read block bitpc : 0x8f0261d0 lr : 0x8f02618c sp : 0x8f117fd0
This showed and the phone won't even let me turn it off, so I just waited for the battery to die out. When it did, I tried to charge it again and planned to do a factory reset thinking maybe an app was causing this. I managed to go to the no command icon and manual mode but no factory reset menu showed up (where you navigate using the volume up and down). So I tried to restart but now it died out completely- no button combination would work, it won't charge, no display can be seen. Is it hard bricked?
I tried to wait a whole day thinking I would be able to charge it again, but it has already been three days and I am not able to perform anything.
There it is, I tried to be as detailed as possible. Additional info: I never tried rooting it or flash roms with it, I haven't done anything with the software (or hardware since I am careful) but install apps (officially from the playstore). From how I see it, it's a firmware problem and I was hoping someone here can help me bring my phone back to life. Is this my fault? If I have this repaired, am I the one who should pay for this?
I mainly want to know what the error message means and if there is a way for me to access the phone. (I figured if I have the technician fix this, all they need is a computer with a software that could fix this since it's a problem with the firmware. If that's everything they would do then I could do that too, with your help of course.)
Thanks to all in advance!
Hi. This sounds pretty strange. Technically...it is hard bricked but you can bring it to life. I can tell you what I would do, when I run into such a problem.
ATTENTION: YOU WILL LOOSE ALL OF YOUR DATA EXPECT EXTERNAL SD CARD
First download the newest firmware for your S7 Edge (G-935FD) on SamMobile and unpacking the .zip.
Download Odin in the newest version, open it and put the downloaded files in the right order in Odin (BL, AP, CP and CSC - the files from the firmware from SamMobile has labeling with BL, AP etc.)
Now the tricky part because your phone won't charge and doesn't go on. You have to go in the download mode with your phone (press and hold volume down - home button - power button) than an window appears and press volume up
Connect your phone with your PC (in Odin you can see, that your device is connected) and press start. It will take some time transferring the ROM and your phone will reboot automatically and after some minutes of blinking Samsung logo...the phone should start normally into the SIM card pattern screen.
Now you have a fresh stock ROM installed and everything should work fine again.
But your phone won't get on or will charge...maybe when you connect it to your PC it will charge. Otherwise I see no option to solve your problem. Your phone must charge again that you can go into the download mode and bring your S7 Edge back to life with a clean stock firmware and an working system.
All,
I have had my Nexus bootloader unlocked and even rooted it before.
However, I friend needed a phone so I let her use my phone...about a month later she said the battery was bad because the phone keeps cutting off.
Long story short I got the phone back and I think she picked up some type of virus or something got corrupted because I forgot to lock the bootloader when I gave her the phone.
Here's what I have found and done:
Found out:
1. The phone will turn on while plugged in after a couple of tries.
2.If the phone is not plugged in, it gets to the 4 dots and either re-boots or shuts off
3.If I turn it on while plugged in and then unplug it and set the display to turn off after 30 minutes...the phone will stay on, until the display shuts off then the phone shuts off.
Here's what I tried:
1. sideloaded Android 8.1 using TWRP (about 5 times)
2. Wipe cache and the other cached (several times)
3. Tried rooted it again...using SuperSu BUT during the re-boot it will stay on the "Google" screen for 30 minutes and not do anything...will not re-boot or nothing...phone get's really hot. (tried this several times)
4. Using TWRP recovery and if I leave the phone unplugged (while in recovery mode) the phone never cuts off.
So I am thinking one of these partitions is bad, corrupted or missing which is causing the phone to think the battery is low and cuts the phone off. Just guessing here. Maybe some malware is installed on a partitions and flashing is not during the trick.
Any suggestions???
I really wanted to keep this phone as a rooted phone I can play with and try different things.
Thanks,
Real
realkewl said:
All,
I have had my Nexus bootloader unlocked and even rooted it before.
However, I friend needed a phone so I let her use my phone...about a month later she said the battery was bad because the phone keeps cutting off.
Long story short I got the phone back and I think she picked up some type of virus or something got corrupted because I forgot to lock the bootloader when I gave her the phone.
Here's what I have found and done:
Found out:
1. The phone will turn on while plugged in after a couple of tries.
2.If the phone is not plugged in, it gets to the 4 dots and either re-boots or shuts off
3.If I turn it on while plugged in and then unplug it and set the display to turn off after 30 minutes...the phone will stay on, until the display shuts off then the phone shuts off.
Here's what I tried:
1. sideloaded Android 8.1 using TWRP (about 5 times)
2. Wipe cache and the other cached (several times)
3. Tried rooted it again...using SuperSu BUT during the re-boot it will stay on the "Google" screen for 30 minutes and not do anything...will not re-boot or nothing...phone get's really hot. (tried this several times)
4. Using TWRP recovery and if I leave the phone unplugged (while in recovery mode) the phone never cuts off.
So I am thinking one of these partitions is bad, corrupted or missing which is causing the phone to think the battery is low and cuts the phone off. Just guessing here. Maybe some malware is installed on a partitions and flashing is not during the trick.
Any suggestions???
I really wanted to keep this phone as a rooted phone I can play with and try different things.
Thanks,
Real
Click to expand...
Click to collapse
Not an expert but i suggest you do the following:
Backup the boot image, download the modified boot image for 4 cores. Try to boot, if it boots normally, your problem is BLOD and it will be solved. If that is not the case, use the 1 click flash bat from the modified fastboot folder that you can find doing some search, that bat will recreate partitions and reflash everything and also flash the rom you provide it then try to boot again. Shutdown the phone, give a charge until 90ish, let it cool and then boot it up.
xxJMarian said:
Not an expert but i suggest you do the following:
Backup the boot image, download the modified boot image for 4 cores. Try to boot, if it boots normally, your problem is BLOD and it will be solved. If that is not the case, use the 1 click flash bat from the modified fastboot folder that you can find doing some search, that bat will recreate partitions and reflash everything and also flash the rom you provide it then try to boot again. Shutdown the phone, give a charge until 90ish, let it cool and then boot it up.
Click to expand...
Click to collapse
Thank you for taking the time to reply...and thanks for your suggestions. I tried both and was very hopefuly...but did not work. The phone still will not boot unless the usb is connected and powered. However, not sure if I did the 4core correctly because I could not tell if it worked or not. I found a twrp 4core for bullhead and that is what I used. However, when you first flash it and it does an auto reboot it boots into TWRP not Android. So within TWRP I just click on reboot system...but same outcome.
I think maybe this phone's hardware is dead or something got burned out...but it is not the battery.
Thanks,
real
realkewl said:
Thank you for taking the time to reply...and thanks for your suggestions. I tried both and was very hopefuly...but did not work. The phone still will not boot unless the usb is connected and powered. However, not sure if I did the 4core correctly because I could not tell if it worked or not. I found a twrp 4core for bullhead and that is what I used. However, when you first flash it and it does an auto reboot it boots into TWRP not Android. So within TWRP I just click on reboot system...but same outcome.
I think maybe this phone's hardware is dead or something got burned out...but it is not the battery.
Thanks,
real
Click to expand...
Click to collapse
You did it wrong. You have to flash the boot.img that disables 2 of your cores. Search it here on the forum you'll find it