Hello guys,
A few months back i got a nokia 5 which was in a bootloop. With the relevant key combinations i managed to get to the boot menu. There i did a hard reset but nothing happened. After reading several forums i understood that the problem might be corrupted system files. So i manged to find stock android for the device and tried to flash it . ( used nokia 6.0.4) But the flashing process did not complete properly and went to the same boot loop. After wasting lot of time i found out that inorder to flash the bootloader must be unlocked on the device. Since i cannot switch on the device I was not able to unlock my bootloader. So i decided to screw up my efforts on reviving my phone. We have no authorized nokia service center in sri lanka . and the service centers which does repair nokia phones are very far from my place.
This week when i charged the phone it kept on displaying the android logo for at least 10 hours. I manged to switch off the device after pressing power button for 30s. AFTer that when i switched the phone back on it went to a bootloop again. I decided to test my luck by bringing the phone to reapir center And straightway the repairman said that it was a problem with the batter and it should be replaced.
SO MY QUESTION IS CAN A BOOTLOOP BE SOLVED AFTER REPLACING THE BATTERY????
Thanks,
Pasan
Related
Hi guys!
I’ve got a problem with my optimus 7.
Yesterday i bought this device. In the shop we couldn’t power on, because the battery was discharged.
The seller told me, that „this device is ok. He tried it earlier one month, it wasn't work.
I brought home, i connect the device to the charger.
2 second later a battery status was on the screen.
About five minutes later the screen changed to lg logo. And than happened nothing.
The device don’t want to boot the windows phone os.
A tried it power on a few times, but nothing happened.
I connected the device to my pc, but the device don’t load the os.
Please help me, what can i do now ?
P.S.: Sorry for my bad english.
I had this kind of problem last summer : the flash of the LG is corrupted. You can try to flash a new ROM, but the best is to bring back the phone to the shop.
mine has same issue, whatever rom i'm flashing to, after reset , phone still stuck at LG logo
After a year of playing with Galaxy S3 I got bored with constant flashing and well, I never got used to onscreen keyboard.
I wanted a phone that will just work and decided to go for a Droid Pro+. Device was form Germany as there is no official distribution in Poland. It worked like a charm for two weeks till just now.
While playing with it (changing ringtones and stuff) I got several messages about services failing - com.service.usb, com.service.google, etc.) As it happened before (but only com.service.usb) I restarted it - in a normal way - power button and then Reboot. It rebooted and after that got stuck on M logo.
The firmware was as stock as it could be. No modifications were made. What's strange, the device can't be hard resetted. I can hold the power button for several minutes and it won't turn off.
Recovery mode works, but wiping does not help. Fastboot also works, but RSD Lite shows N/A in every column of Device info. I flashed GB 2.3.6 (5.5.1Q-110_ELW-TA-36-65-release-keys-signed.Retail-en-GB.tar) found on XDA. The rom itself should be OK, as no functionality was lost (recovery and fastboot), but the device still hangs on the boot logo. Device info is still N/A.
Could it be a hardware malfunction or is there something else I could try? Warranty is probably not an option since as i mentioned there is no official distribution in Poland. Any help would be appreciated since I'm out of ideas by now... Also, does anyone know if the battery is charged when in Recovery or fastboot mode? Connecting to a charger ends up on the M logo. And because very few people in Poland have Moto devices I have no other way to recharge the battery.
So i have bought my phone about 3 months ago. All have worked well, but a couple off days ago, it have had some problems.
It sayed 2-3 days trebuchet process have stopped and process.android.process.media has stopped. The only solution when this came i had to restart the device. I tried yesterday a factory reset but it didnt work.
Yesterday evening it did again the process stopps and then i tried to restart my phone. But when it shut down it dosent anymore go on. Now it dosent react to anything, not the normal powerbutton and not even the powerbutton + volume -. I havent rooted the device. So is there anything i could anymore do or should i just send it to warranty repair?
Im very desperate, thanks for all the help. But if you have an solution can you write it step by step, im not so experienced in smartphones.
Now i got the phone to restart but when it start it says over and over again that trebuchet has stopped. What can i do to this problem?
Edit: And now its stucked in the Zuk start screen. Dam im getting frustated...
Enter in recovery mode and do a factory/cache wipe
Have you installed any themes? Because some cm13 compatible themes cause system ui crashing
Hello, havent installed any themes. How do i get to recovery mode?
If the recovery mode is volume up and power button. This neither works, its still dead. Dosent even vibrate when pressing power button long.
Power on the phone , when you hear the vibration and the zuk logo appears , press both volume buttons, this should let you boot in the recovery
What happens if you connect the fone to charger?
But the phone dosent power on. So i cant do that. And no, the battery is not dead.
Ok, if you cant boot it, the last thing is warranty , where have you bought your device?
I could boot it today on the morning 1 time but then it again died and now its totally dead. I bought it thru tomtop, have put a message to the seller already. Lets se what they answer.
Ok, hope the seller will answer you , continue trying to boot it .
Let me know if wou solve it ��
Yeah the seller answered that i get a new device. But then on tuesday i tried a last boot, and it got alive again! I did the factory reset and now the phone has worked perfectly after that [emoji106]
But now the trebuchet keeps stopping and after that all the processes i have open. So now i changed to Nova launcher, i hope it would solve the problem.
Glad to know you solved the problem
Trebuchet problemi shoul be solved with marsmallow update.
maryankomar said:
Glad to know you solved the problem
Trebuchet problemi shoul be solved with marsmallow update.
Click to expand...
Click to collapse
Yeah it was solved like 5 days. Now the apps started to crash again :crying: And now the f***** phone dosent even start. Its just stuck in the Zuk powered by android start screen. Is there something i could do? I dont think the factory reset would help in long term beacause it didnt help the last time. Or should i just send the phone to the seller and request for a new one?
Edit: And now the factory reset dosent even work. When i try to reboot it after Factory reset its stuck on the Cyanogen start screen, so i think my last option is to ship the phone to the seller and hope i get a new device.
Edit2: And now after a second factory reset the phone started to work again. What can cause this type of meltdown? Could it be somekind of hardware problem or is it a software problem?
The Best solution is to change the device if you can, because you're not sure if it will work in the future.
my p10 plus got got bricked and it is always going to eRecovery without going to home screen after update. my phone is BOOTLOADER LOCK, NOT ROOTED THOUGH. and i want to fix this . i need help . ps : i hope theres a method that could fix this without unlocking bootloader.
mongs said:
my p10 plus got got bricked and it is always going to eRecovery without going to home screen after update. my phone is BOOTLOADER LOCK, NOT ROOTED THOUGH. and i want to fix this . i need help . ps : i hope theres a method that could fix this without unlocking bootloader.
Click to expand...
Click to collapse
hi, do you dolve your problme? i guess i have the same problem XD
regards
My P10 plus started this exact problem today. Always stock, never rooted or boot unlocked.
I was playing a game and it rebooted. Started again and lasted a minute but then constant bootloop to eRecovery screen.
Did the erecovery image download and didn't do anything brought me back to the same screen
Tried to factory reset on the ecovery screen and then booted, but during setup it rebooted.
Went to fastboot screen (pwr+vol down while attached to usb) and rebooted after. I was able to go through setup.
After letting it for sit for only 2 minutes as I type this message, it randomly started rebooting on its own.....and now back to recovery screen.
FACKKKKKKK
UPDATE: Took my phone in to a cell repair shop after exhausting all my troubleshooting options.
They said they took the phone apart to disconnect the battery and do a full power drain. Then after reconnected they installed EMUI 9.1 again via USB and got the phone up and running.
Been working for me for the past 6 hours, but the phone just rebooted on me once, so i'm sure they're still an unsolved demon in it. but no idea what it is right now.... May be time to start phone shopping.
maybe just battery broken, install app accu battery or any other to check batery
I am having a big problem with A2017G. What happened is since the battery was ready for replacement, I took it to a service shop and the man did it in front of me, opened the phone, replaced the battery and put it back together. However, when we turned it on, it went to bootloop showing only ZTE logo and that is it. He told me that he can't help with that. So, I used the Axon 7 Tool to flash Full EDL and it was successful, but the phone works like it is severely down-clocked, it is so slow you can see where you touched the screen, and it takes 3-4 seconds for it to respond to a touch. I tried at least 7-8 different full EDL ROMs (MM, N, O) always with same result. I unlocked bootloader and installed TWRP (last version available for Axon 7) but never managed to boot into any custom ROM (flashing goes fine, but no boot). Does anyone have any ideas or suggestions, or is it probably hardware problem? Any help is appreciated !