Related
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Sshaffer1992 said:
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Click to expand...
Click to collapse
god that is really hard to read...did you make a back up before you do installation? if so do a restore, if you dint, download another rom, kernel, put it in your phone, wipe everything except internal storage via TWRP then flash rom then kernel.
G1_enthusiast said:
god that is really hard to read...did you make a back up before you do installation? if so do a restore, if you dint, download another rom, kernel, put it in your phone, wipe everything except internal storage via TWRP then flash rom then kernel.
Click to expand...
Click to collapse
lol sorry i wanted to be as pacific as possible. I did make a backup before flashing the rom. when i tried to go back to it i had the same problem with it rebooting after a few mins. i tried flashing furnace 0.0.8 kernel after installing a fresh rom but same problem. I am back on factory recovery atm is there anyway to flash twrp back to the phone without it being rooted? i tried to get the computer to communicate with the phone when it turns on but it wont seem to connect unless im in download mode or recovery.
Sshaffer1992 said:
lol sorry i wanted to be as pacific as possible. I did make a backup before flashing the rom. when i tried to go back to it i had the same problem with it rebooting after a few mins. i tried flashing furnace 0.0.8 kernel after installing a fresh rom but same problem. I am back on factory recovery atm is there anyway to flash twrp back to the phone without it being rooted? i tried to get the computer to communicate with the phone when it turns on but it wont seem to connect unless im in download mode or recovery.
Click to expand...
Click to collapse
so the phone turn on? try enable debugging in developer option, sometimes that works for me, not sure why.
Solution?
Sshaffer1992 said:
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Click to expand...
Click to collapse
I had the same problem except with me, i was just trying to change fonts manually. It went into a bootloop and i stressed dover it for hours until finally i found out that you have to use the lg mobile support tool (you can find it in one of these threads on the lg g2) and revert it back to stock. That fixed it perfectly fine. Its a lengthy process but simple. If that doesn't work you have to do what the lg mobile support tool does semi-manually with another program lg flash tool which is longer but just as simple if you follow the directions given in the thread to the letter.
androidfantic32 said:
I had the same problem except with me, i was just trying to change fonts manually. It went into a bootloop and i stressed dover it for hours until finally i found out that you have to use the lg mobile support tool (you can find it in one of these threads on the lg g2) and revert it back to stock. That fixed it perfectly fine. Its a lengthy process but simple. If that doesn't work you have to do what the lg mobile support tool does semi-manually with another program lg flash tool which is longer but just as simple if you follow the directions given in the thread to the letter.
Click to expand...
Click to collapse
I tried the lg flash tool and it put my phone back to stock but still have the same problem. I also tried lg mobile support tool but it will not recongize my phone. I did happen to get into settings and seen that both my imei and baseband are unknown. Could this be causeing the proble m? is there any way to fix it?
G1_enthusiast said:
so the phone turn on? try enable debugging in developer option, sometimes that works for me, not sure why.
Click to expand...
Click to collapse
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Sshaffer1992 said:
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Click to expand...
Click to collapse
**** thats not good at all. This happen when I was using my S3, if IMEI is gone then you could not use the phone at all, theres no way you can get it back unless you made a back up. you have to sent it in man, sorry this is as good as hard brick.
G1_enthusiast said:
**** thats not good at all. This happen when I was using my S3, if IMEI is gone then you could not use the phone at all, theres no way you can get it back unless you made a back up. you have to sent it in man, sorry this is as good as hard brick.
Click to expand...
Click to collapse
My friend also has a lg g2 that i rooted for him would i be able to use a backup from his phone. Also when i turn the phone conpletely off and hold down all 3 bottons it brings me to a hardware key settings it does shows my imei number there. If i sent it into lg would they know the phone was once rooted or does the back to stock method cover it up? Thanks for your help btw
Sshaffer1992 said:
My friend also has a lg g2 that i rooted for him would i be able to use a backup from his phone. Also when i turn the phone conpletely off and hold down all 3 bottons it brings me to a hardware key settings it does shows my imei number there. If i sent it into lg would they know the phone was once rooted or does the back to stock method cover it up? Thanks for your help btw
Click to expand...
Click to collapse
they have coders there, I'm sure if they really want to know they can figure it out. If you send it in to get it fix out of your own pockets (meaning you pay them) then i'm sure they dont care, but if you want a replacement due to warranty then it may be a different story.
Sshaffer1992 said:
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Click to expand...
Click to collapse
That suck bro I'm facing the same issue right now hope you got it repaired if so feel free to share the process lol
Nba2kgod said:
That suck bro I'm facing the same issue right now hope you got it repaired if so feel free to share the process lol
Click to expand...
Click to collapse
I eneded up restoreing my phone back to stock and took it into my local sprint store it cost ne 75 dollars to replace the phone not under warranty (if u have sprint protection its free) i told them i took and ota update and it started rebooting itself. If you do get a replacement make sure u back up your efs files to a safe place on your phone. Theses files can become corrupted by flashing roms and kernals.
Sshaffer1992 said:
I eneded up restoreing my phone back to stock and took it into my local sprint store it cost ne 75 dollars to replace the phone not under warranty (if u have sprint protection its free) i told them i took and ota update and it started rebooting itself. If you do get a replacement make sure u back up your efs files to a safe place on your phone. Theses files can become corrupted by flashing roms and kernals.
Click to expand...
Click to collapse
Not under warranty? Doesn't it have a 1 year manufacturer warranty? The G2 wasn't released on Sprint until November last year so it should have been covered.
Sent from my LG-LS980 using Tapatalk
Yes its still under manufacturer warranty but when i made a repair order with lg it said it would take 2 to 3 weeks to get my phone back and if they found out it was due to being rooted and flashing roms im sure lg would of charged a arm a leg to repair it. With sprint i got a new phone in 2 days or ordering it.
Hi everyone,
Full blown Android noob here, coming from BlackBerry.
Here's my story:
I rooted my AT&T D800 G2 using ioroot25 today and installed apps like Titanium Backup, Wakelock Detector, and Greenify. None of which caused any problems.
The issue started when I found this thread http://forum.xda-developers.com/showthread.php?t=2664507 which explains that there are two .so files related to carrier iq in /system/lib. So using the adb tools with ioroot25, I was able to remove these two files. Afterwards, I rebooted my phone and the persistent error message that "Unfortunately, the process diagandroid.iqd has stopped." Okay, luckily I had kept the two carrier iq files on my computer, so I put them back into /system/lib (which was a serious pain in the a** for me because I kept getting permissions errors that I didnt understand).
This error message doesn't let me use the phone at all. When I hit OK, it immediately pops back up, rendering the phone almost useless. If I'm stubborn, I can get to one button or something on screen within about 10 minutes.
I don't think the two carrier iq files are causing this because I put them back and the problem still exists.
Thinking it would help, I booted into I guess what would be called "recovery mode" (there's no custom recovery installed on my phone) and I used it to perform a hard reset. This was clearly a mistake because now I can't get into the menu to enable developer options and usb debugging.
Now I'm stuck and don't know what to do, any suggestions to get rid of the "diagandroid.iqd" error would be extremely appreciated.
Thanks for your help
Bump? Any help at all would be appreciated.
Bump again
Currently I have no way of turning USB debugging on so I can access ADB.
Also when I go to download mode, it gets stuck on "Firmware update" and the progress bar stays at 0% and does nothing.
If there's a way to remotely enable USB debugging, I'll love you forever.
Please help
yeah, I need this can't use phone lol.
rancur3p1c said:
yeah, I need this can't use phone lol.
Click to expand...
Click to collapse
I just used this thread: http://forum.xda-developers.com/showthread.php?t=2663369 and completely wiped the phone to fix the issue. I don't have a fix other that this nuclear option, sorry. Good luck.
I'm usually fairly good at troubleshooting my own stuff but this really has me stuck in the same place for a few hours now.
So basically Flipboard has been nagging me(well play store is, not the app itself but anyway) so I said to myself why don't I uninstall it since I've never used it and don't plan to, and besides I hate to have pointless apps installed. So I open TitaniumBackup and I see it is installed as a system app, I thought what's the worst that can happen? so I do uninstall it and a minute later my phone shuts off. I try to turn it on and it doesn't go past the Samsung Galaxy Note 4 flash screen, it either reboots or stays like that.
I try to go into recovery to restore a backup and I can't, it is stuck at Recovery Booting and again it either stays like that or reboots and does it again and again and again.
Now, I haven't made any changes or installs on my phone for weeks now, so this is either because I unistalled Flipboard(I know I shouldn't have risked it since it was a system app but I really could not see it going this way) or the hardware is on it's way out(don't see what else could it be).
I figured I should flash a stock rom with odin, I can get into download mode, and reinstall everything from scratch.
I took a stock image from xda and flashed it and it does exactly the same thing.
Right now I'm downloading another stock image from sammobile for my country/provider to see if this will change anything.
What else can I try? I'm completely stuck and I really don't want to send the phone back like this, I doubt amazon is gonna be happy about it.
Specs:
N910F
Emotion Revolution 12.1 Rom
POK1 BL&CP
TWRP 2.8.7.0
Really sorry for the double-post. I'm quite desperate and need my phone for work.
Since last post I've tried flashing N910FXXU1COH4_N910FH3G1COH3_H3G.zip through Odin from SamMobile and it did the same thing with rebooting constantly.
Then I've installed Kies and went to Tools -> Firmware Upgrade and Initialisation and gave it the model and S/N and it downloaded something and everything went all right, the phone reboots and I'm back in the same circle, it just shows me the splash screen(in some video's I've seen that after this procedure they get the splash screen and then the android bot with a progress bar, I don't get that, I only get the splash screen and reboot) and reboots.
I thought this was a last resort thing? Is the phone completely dead or is there something I can try?
Again sorry for the double-post.
Update: still no progress so I've contacted Amazon and they said to send it back so hopefully this works out in the end, no matter how annoying the waiting time will be, if you do have any suggestions on what I should try please let me know as I haven't posted the phone yet.
So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Ghujii said:
So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Click to expand...
Click to collapse
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Ghujii said:
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Click to expand...
Click to collapse
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
I will attempt to do this, since nothing since has work. I am about to get a new logic board for the system in the next 2 weeks. Towel root DOES typically work on this system, however the last time I attmpted it it failed to work outright. Im not sure what has changed with the device, but i believe reflashing stock is the best method. The phone now, will boot up, then skip the lock screen and go straight to the home screen, which is black with no pull down bar, or with no signal and there is no way to rectify it. Even if there were, it boots back down and launches back up and becomes locked at the ATT logo.
After a fair bit of messing with it, and recovery mode it will sometimes boot normally where it tells me that processes has failed and askes me to cancel the ''app''. This is the best option to update the phone and attempt root, but getting it here is so difficult because it reboots itself and the mode is rare to acquire. This problem either is due to the kernel, or the rom i believe. I also am to believe the powercell may have some issue, as i replaced the battery a few weeks back and it worked fine for about 1 week.
Booting into safemode doesnt work either as it skips over the lock screen straight to the home screen. Outsidce of replacing the logic board, or attempting another flash im at the end of the short rope i was already on in terms of options.
sway8966 said:
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
Click to expand...
Click to collapse
UPDATE: I found therein two methods to flashback to stock. I did so, then proceeded to attempt to flash from nb1 to nj4. Progress stopped there when it flung an error 7 at me. So this means either something in my phone is corrupted or the file i downloaded from the above mentioned forum is corrupted. I also attempted flashfire, but seen as it STILL crashes at random due to process errors thats almost impossible to attempt.
My XT1575 just decided to go into a bootloop a week ago on its own, literally. I was just checking traffic on Google maps when I noticed it started to lock up. Finally, I see the Motorola splash screen, and that was the beginning of it. Went into recovery mode and tried a factory reset, clear cache partition, etc. but no luck. I've tried everything under Android 6.0 here but it continues to bootloop no matter what I do.
It's not rooted and the bootloader is locked, so I don't think I can even install TWRP or any custom recovery. I have never even though of enabling USB debugging so that's out of the question. What's odd is after trying all sorts of things, sometimes, after the phone has been off for a while I would power it on and it would actually boot into the Welcome screen. Shortly after that though, it locks up and starts bootlooping again. I don't know what else I can do about this or if it's recoverable. I hope someone can help. If it's of any significance, when in recovery mode, at the top I see what I think is the firmware it's currently on -- motorola/clark_retus/clark 6.0/MPHS24.49-18-4/5. Please help!
Update - After having my XT1575 powered off overnight, I powered it on this morning and it was able boot all the way into the Welcome screen, setup, etc. Right away I went and turned on USB Debugging and Allow OEM unlock. Tried rebooting and again it fails to boot. What's weird is it randomly seems to boot when it wants, and something must be corrupt but I just don't know what it could be. Does anyone have any ideas?
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
Yes undo what you just did an follow this guy
jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
jason2678 said:
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
Click to expand...
Click to collapse
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
iflyimpilot said:
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
Click to expand...
Click to collapse
/proc/last_kmsg is a log file that should get written to if a kernel panic causes a reboot in theory. In practice I find it is often blank even after a random reboot.
iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
going by that logic the thing that you should have done was get a factory image from moto and flash to stock using moto tools if that failed at fixing it then send into moto it might not be lost yet but the more you progress the more less likely to replace the phone moto is...
it sounds like something is going bad could be ram emmc or the soc
What i would do is get into discussions with lenovo to see if they can get you fixed up. if you unlocked the bl they know be straight with them. if you get nowhere and no rom you load can fix it sell as parts replace at your expense...