Related
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
Ive just encountered the same problem. Were u able to find a solution?
Shahin7631 said:
Ive just encountered the same problem. Were u able to find a solution?
Click to expand...
Click to collapse
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
anish100 said:
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
Click to expand...
Click to collapse
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
GStriker said:
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
Click to expand...
Click to collapse
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
GStriker said:
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Click to expand...
Click to collapse
Ive literally tried everything .even repartioned the phone . it works fine in recovery and download mode but as soon as i want too boot to android unplugged it restarts . when plugged it has no problem
Funny thing. I have a factory Sprint Note 2 with the latest kitkat updat and I am experiencing the same problem. Phone has not been rooted or messed with. If anybody come across a solution let me know. I booted the phone and unplugged the power button to verify and it does the same thing. Only stays on when in airplane mode or charging.
One more thing. I tried somewhat to do what was posted above about performance / cpu power. I put the phone in powersave mode and checked limit cpu and is is fully operation. problem gone. If I turn power save mode off I'm back to square one.
To late. Took a picture by mistake and phone jumped into boot loop.
i have GT-N7100 and same problem phone is stuck on boot loop when unpluged
---------- Post added at 04:22 PM ---------- Previous post was at 03:24 PM ----------
i just tought maybe it needs new battery. cause before i unpluged it it showed 67% then bootlooped 2x then i pluged back in and it shows me only 5%. i think its battery cause it cant dishcharge in 1 or 2min
My initial problems were that it would drop signal and show an x with no bars intermittently. then i started having problems anytime the phone demanded use. Picture, internet, video. tried a few things listed above. Still would go into a boot loop when not plugged in. Battery would charge normally and show it percentage like normal. It would reach 100% with no difference in charge time. When battery saver is on it would not have a problem unless I use an app that demands more cpu usage, network connection, battery consumption. Put a new battery and problem is gone. some people say the battery show swelling but my battery looks identical to the new one. no swelling and it is not deformed in any way.
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Shahin7631 said:
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Click to expand...
Click to collapse
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
dcmobiletech said:
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
Click to expand...
Click to collapse
Ive tried already with another battery ....its a very strange situation while everything works fine in download or recovery mode when its unplugged ...i have ordered a third party battery to see if it'll make a difference or not ....i'll keep u updated tomorrow
GStriker said:
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
Click to expand...
Click to collapse
Where is the Preferences section? I am unable to find that on my Note 2 settings.
Experienced the same thing and this is the first time I had this. I was playing a game after I fully charged my battery and suddenly it turns off. So I waited for it to turn on where I noticed that it keeps on turning on and off and stuck on the " Samsung Galaxy Note 2" logo screen. Then I tried several things like clearing the cache and dalvik but it just do the same thing. I re-flashed the 4.4 ROM that I was using but sadly it does the same thing. I then noticed that if I plug in the charger it works normally and does not boot loop. And as soon as I remove the charger it will keep on restarting on and off on that screen. I was thinking that it might be a hardware failure or the battery itself. So I went to recovery mode and unplugged the charger, it stays on. Went to download mode without the charger and it stays on. Freakin' weird. I am about to flash a different ROM and will wipe everything and see what happens...
Fully charged the battery to 100%, unplugged the charger and it started to boot loop again. I allowed it to boot loop once and immediately went to recovery mode and saw that my fully charged battery went down to 3%. Tried different ROMS (Omega, DN3, and Phoenix), I still have this issue. Now can use my Note2 as long as the charger is plugged in...
Change your battery and solve the problem ?
Sent from my GT-N7100 using XDA Free mobile app
I did. Case closed!
red_hanks said:
I did. Case closed!
Click to expand...
Click to collapse
is it working fine after battery change? does it still get stuck in boot loop? mobile networks?
It works perfectly !
OK all I am sincerely reaching out as I am out of ideas. Here is the situation...
Issue : Last evening, running most recent Liquid Smooth 4.4 (Superb ROM, I don't feel this is really at fault just relevant and thorough), I had been doing some heavy tethering when I picked up my beast and stepped out for a smoke. As I am reading up on moto360's 2 1/2 hour sellout I get a random reboot. Eh, no biggy ... it does happen. (Not often, or at all to speak of in my case just stating.) Right after reboot I hit the power button to make a forced boot cycle and it rebooted again before I pressed anything on screen!
Now SOMETIMES I will boot past the initial "NOTE II" splash (NOT often at all ... usually get reboots, splash hangs, or the phone simply turns off on its own from here) If it does make it past Note II splash it will reboot, hang, or simply turn off from here as well.
Steps Taken: I firstly, attempted a restore... no dice. I attempted a fresh install (TW, SlimRom, and DU) ... no dice dos. OK hmmmm
Now to all mighty ODIN (L900VPUCNE2_L900SPTCNE2_1561791_REV04) .... NO FREAKING DICE!!! WTF?!?!? I additionally attempted MC2_STOCK_with_COUNT_RESET-20130511 ... no bueno!
I still have access to Recovery and Download soooooooo ... I lay down at the mercy of you the community!!!
Thanks in advance and if you need more info PLEASE don't be shy!
Same issue here!!!
After a random reboot, I have the same type issue!
Running an almost stock NE2 rom, random reboot then hanging at the Note2 bootscreen.
Like you, I can access download and PhilZ recovery.
I CANNOT flash through recovery. Errors out.
Odin flashes succeed but on reboot I still hang at the Note2 bootscreen.
My recovery is showing multiple error related to accessing E:, E:/cache, etc.
Are you having that issue as well??
Try this go to samsung-updates.com
search device l900 scroll to the very bottom of the list
download the L900VPUCNE2 zip (this is a pure sprint rom)
flash using ODIN3 v3.09
I have flashed this file many times and it works every time.
Hope this Helps.
Exact same thing
I've been running the latest nightlies of OmniRom. And yesterday, out of the blue, random reset then bootloop. No luck with anything, recovery, odin, etc.
Did Sprint deliberately brick our phones?
I'll try the odin to stock to see if I get any luck there. But if anyone else figures it out, it'd be nice to know the fix. Thanks!
No luck going back to stock. It's dead Jim.
I had a very similar issue. Try booting your phone with it plugged into the wall changer; something given the full 2amps of power. It it'll boot, it's possible your battery is bad.
If my case, my phone would boot loop around the splash screen. on the battery power only. I could go into recovery and download mode with no issues and stay on for hours. If I connected it to, say a PC, it would boot, but would random shut off within five minutes. But if I plugged into the wall charger, it would boot with no problems. Stay on for hours. If I plugged it from the charger, it would immediately shut off and try rebooting which it would just boot loop.
Luckily, the batteries are pretty cheap at $10 to $20 on Amazon. I went with the Anker for $15 to get me by till I get my next phone, which will probably be October; I'm heavily learning towards the Note 4
Replace the battery
I had the exact same issues. I ended up buying a $10 battery on amazon and it solved the problem. I did go through all the flashing, odin to stock, etc. All was pretty good when plugged in to a good power source. It took me about 4 hours of trial, error, reflashing, etc before I realized it was probably a battery issue. The new battery has solved the problem.
lovekeiiy said:
I had a very similar issue. Try booting your phone with it plugged into the wall changer; something given the full 2amps of power. It it'll boot, it's possible your battery is bad.
Click to expand...
Click to collapse
When I try to power the phone on while plugged to the charger. I see the battery graphic with a circle on it but the phone won't boot at all.
When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.
Do the batteries go bad instantly?
crackrock360 said:
After a random reboot, I have the same type issue!
Running an almost stock NE2 rom, random reboot then hanging at the Note2 bootscreen.
Like you, I can access download and PhilZ recovery.
I CANNOT flash through recovery. Errors out.
Odin flashes succeed but on reboot I still hang at the Note2 bootscreen.
My recovery is showing multiple error related to accessing E:, E:/cache, etc.
Are you having that issue as well??
Click to expand...
Click to collapse
I couldn't flash any of counter reset rom through anything but TWP so i have to boot into download and update away from Philz. AFTER the recovery update I started making headway. but couldn't ever seem to make it past boot no matter how much batter is charged. I was beginning to think it was something that died on the inside (heh...heh)
After reading through some of these greatly appreciated replies I am going to plug her up to the wall and try the ne2 counter reset again(12:58 am). ... AND I may go throw some cash at a battery juuuuuust in case. (I do tether 100gigs daily sooooooo it does make sense that it could have burnted up lmao!)
UPDATE 1:25AM : I did as advised and it does seem battery has taken a dive! hmmm so weird! It still shows having power and charging. But after being plugged into wall I made it booted into a fresh ODIN install!!! (keep in mind that AS SOON AS odin gave me a pass I switched to Wall outlet!) I have even performed a power cycle to confirm it wasn't a fluke! I will indeed be out first thing in the morn to get a new battery!
AGAIN I can not thank you all enough ... I would have never thought of that. (you would think it would be one of the first things but eh you live and learn.)
I will update with any new progress!
cheers!
crackrock360 said:
When I try to power the phone on while plugged to the charger. I see the battery graphic with a circle on it but the phone won't boot at all.
When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.
Do the batteries go bad instantly?
Click to expand...
Click to collapse
'When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.' EXACT CIRCUMSTANCES AS I SIR!!!
Mine does the same and hangs .... right? HIt the power button and as soon as it lights up to start to boot then plug in the power cable. (the freezing while off and charging is a known bug in at least two roms i believe)
Congrats Rubledub!
As for me, I'm still screwed. Invested $40 in a battery (had to have it today, couldn't wait on shipping)
With the new battery fully charged I still have the same result!
crackrock360 said:
,,, Do the batteries go bad instantly?
Click to expand...
Click to collapse
There were probably signs of the battery going bad, but misread. But in my experience, it went to total crap instantly.
The signs of going bad were shorter battery life, getting stuck/freezing when trying to charge the phone when off (there's that battery graphic that shows up). Unfortunately, I did all kids of other stuff before I really figured it out, and looks like a messed up my modem and now cannot connect to 3G. Kind of irritating, but luckily, I spend 75% of my time in LTE areas. Just got to ride this out till the Note 4 is released.
Here is thread of when I was having trouble: linky/URL]. It's a lot of me trying slightly different things with no changes in results. Plus, I was a buddy's house who was in a 3G only area. The worse part, my phone did this the day before I left to spend the weekend five hundred miles away from home at a friend's house to visit.
sloanmeister said:
Try this go to samsung-updates.com
search device l900 scroll to the very bottom of the list
download the L900VPUCNE2 zip (this is a pure sprint rom)
flash using ODIN3 v3.09
I have flashed this file many times and it works every time.
Hope this Helps.
Click to expand...
Click to collapse
Just chiming in to say this worked for me! Thanks!
Joelski144 said:
Just chiming in to say this worked for me! Thanks!
Click to expand...
Click to collapse
Oh i agree! Thats is what had me so baffled ... Not even the odin installs were breathing life, and Odin ALWAYS works for me. If Odin isnt getting it done and neither is a battery then your problem may be far more serious???
Weird Recovery Lag and bootlooping after CM12 update
Hey guys,
I came across this thread and the issues I'm having sound so what similar, so I thought you might be able to help.
I have two Samsung Note 2(l900) and running on cm12 as of yesterday morning. I installed the new nightly manually on both devices the same exact way by opening clockwork recovery and installing zip. One device was successful and is working just fine, the other seemed to flash fine until it had finished loading the apps and going into boot. The device would restart on the note 2 logo screen and then proceed to the cm12 boot screen and then restart after a few seconds. I went back into recovery which took longer than usual, and proceeded to clear partition, wipe dalvik cache, and install older nightlies. I had the same result no matter what nightly I went with.
I decided to set the device back to stock rom and root again. I it worked just fine, so I went through the process about 4 times installing different nightlies but had the same restarting results. It was then I noticed that getting in clockwork recovery manually lagged about 30 seconds. I took the advice of someone on the Google plus forum and switched the recovery from clockwork to twrp. Tried again with the same restarting results and with the manual recovery lagging about 30 seconds to get into.
I'm back on stock rom and the device is working great but takes forever to get into manual recovery which I believe is why it is having issues booting Cm 12
This has been driving me nuts for the longest time now: My P600 automatically powers on and starts to boot whenever I plug in the AC charger, meaning I can't charge it while it's powered off. The battery icon shows up for a second and then goes away, followed by the boot animation.
I'm aware this is a known issue when making the jump from 4.3 to 4.4.2 (that's when it started to happen anyways) and the recommended fix is to flash a stock KitKat ROM to get the KitKat bootloader, but I've tried that at least three times by now and the problem persists, which is really frustrating.
The first stock ROM I tried was the Mexico CNF1 version after fully wiping. I also ticked the "Phone Bootloader Update" option in Odin. Then I tried the Cellular South CND2, but that was also to no avail.
I don't know what to do now. I might as well try downgrading if nothing pops up. Could somebody help me out?
EDIT: Additional info, I'm using TWRP 2.6.3.3 to wipe system/data/cache/dalvik and Odin v3.09 if that helps any.
Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
nkomp18 said:
Hello,
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
Click to expand...
Click to collapse
The single vibration with no screen normally means the batteries dead, and it's possible that it's not charging when hooked up to your computer, open it up, take the battery out for 15 seconds, put it back in, then plug it into the charger for an hour or so.
nkomp18 said:
Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
Click to expand...
Click to collapse
Are you sure the zip you downloaded is cm11? There was an issue with yesterday's first cm12 build that resulted in bricked devices.
The device can be recovered
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
mikeioannina said:
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
Click to expand...
Click to collapse
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
nkomp18 said:
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
Click to expand...
Click to collapse
Go to your custom recovery, wipe /data /cache /Dalvik and /system, then flash CM+GApps. If you used the tool in my thread, you'll have to boot into COS before flashing anything.
Now it's almost perfect,
The power button only works to lock the screen, not to turn it back on again.
As you can imagine, the phone is unusable if I can't wake it up from sleep.
I tried a lot of things. First of all it's not a hardware issue because the power button works flawlessly to lock the phone or to reboot. It only fails to wake the phone up, which sounds like a software issue.
I tried the option "double tap to wake" and that does nothing. The only thing that wakes the screen is connecting it to a USB.
Any ideas?
I noticed after I followed the instructions some things changed in my phone. The OPPO logo is different when the phone loads and fastboot graphic is different. Now I get Chinese characters whereas before I believe it was an android robot.
I suspect this is causing the power button errors. Any ideas how to put it back?
Hi guys
I seem to have an incredibly weird issue on my HTC. It is rooted and running DU 6.0.1.
For some reason, despite the battery being 60%+, whenever I unplug my phone from power it just switches off. If I try to reboot it/go to recovery, it starts up for a second and goes off. However, it seems to function normally when it is plugged in via usb. I can access recovery as well. I have tried to reflash as well as a full wipe, but nothing seems to work.
Im thinking something went wrong with the boot.img maybe ?
Any help would be appreciated.
xdaaccount123 said:
Hi guys
I seem to have an incredibly weird issue on my HTC. It is rooted and running DU 6.0.1.
For some reason, despite the battery being 60%+, whenever I unplug my phone from power it just switches off. If I try to reboot it/go to recovery, it starts up for a second and goes off. However, it seems to function normally when it is plugged in via usb. I can access recovery as well. I have tried to reflash as well as a full wipe, but nothing seems to work.
Im thinking something went wrong with the boot.img maybe ?
Any help would be appreciated.
Click to expand...
Click to collapse
Maybe its a stupid inquiry but does battery work as it should in stock rom? so that you can be absolutely sure its not faulty battery that's creating issues.because two things happen(in my experience when something goes wrong with boot.img) either its stuck at splash screen (hboot) with red text OR it goes blank but not off, just blank
Definitely isnt the battery. I am not experiencing any drain and it functions completely normally when plugged it. When I unplug, it works fine for a few min and then switches off. It will then not turn on, despite it showing 90%+ when I plug it in
but it happens in stock rom also? thats what i wanted to know .if you can full wipe and phone works when connected to usb,maybe you can run ruu and confirm that as well . If you can go to recovery ,make a nandroid backup.and try a ruu.
Yup, happens on stock as well.
Also, I think the recovery is messed up as well since it just crashes now when trying to flash something. It's having issues doing a nanroid backup as well
And no love for exe ruu as well?