Hi all,
I'm having a little problem. I have researched but everything I've found leads me back to square one...
So I followed this guide to installing CM7 on my M2. Please note that I have in the past successfully rooted my phone, installed the Argenstone ROM and one other basic Great Britain Rom. So I'm not a total nub. However at this stage I have a phone that's is useless to me...
My phone is rooted. I have Droid2Bootstapper installed and I managed to get the CWM 3.X installed. I downloaded the all-in-one.zip file from the CM7 ROM thread (the zip is actually called EndlessCM7-110901-nightly_build.zip - hope that's not an issue?)
I booted into CWM and applied the EndlessCM7-110901-nightly_build.zip and after (without a reboot) wiped everything (I had backed it up previously).
I rebooted the phone and...well I get the Google logo with the Motorola M and the Cyanogen bot as the 2 'O' characters. Then after a while a 3D rotating 'square' and the android writing and logo 'shimmering' in and out but that just goes on forever. I left it for an hour at one point and just gave up.
Now I can't even get past the Google logo. I've tried restoring my previous back up but that won't work either. I can't boot into the OS to actually use RSD lite to flash a known working ROM over the top.
When the LED turns blue and I hit the volume key it displays "Android BootMenu <v1.0.3>" which is different to the CWM 3.X that I was getting prior to applying the EndlessCM7-110901-nightly_build.zip file.
From here I can select to recover the last 'latest recovery' which when done loads into CWM-based Recovery v4.0.1.6-defy.
Basically I'm at this point where I seem to be able to load just about every boot menu under the sun and do everything but actually launch the damn OS.
How can I get out of this hole? Preferably I'd like to get everything back to the stock ROM the phone came with so that I can start from scratch again.
Any bodies help would be more than appreciated.
Cheers,
- Matt
EDIT: I have even used CWM 4.X+ to try and restore the Argenstone ROM. it goes through the whole process of checking the MD5 sums, restoring the system and boot images etc and seems to work without any issues. I then wipe all data and reboot. Nothing - still the same cyanogen Google logo and the only thing I can do is boot into all the CWM menus.
*sigh*
Argh feel like a true idiot now. It took me about an hour of searching earlier but I've only just found/remembered how to get RSD lite to see my phone (pwr+volume+camera) and I'm wiping the whole thing to the factory (vodafone) ROM. Might take the opportunity to take it to Vodafone and tell them it never gets a damn 3G connection lol...provided this flash works (touch wood).
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Sounds to me like there''s something physically wrong with the phone, probably the battery. Time for a new one anyway. Lithium batteries degrade with use. After ~500 charge cycles it'll have lost upwards of 20% of its original capacity and might show other signs of wearing out like inconsistent voltages. After 2 years of use, you'll be well beyond 500 cycles. A new battery off eBay is pretty cheap, and some sellers include the needed tools.Go to ifixit.com for a tear-down guide. A hair drier can help soften up the adhesive. The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
And FYI, the whole "optimizing app" thing is the OS rebuilding the cache. When you flash your GAPPs package or a zipped Titanium backup it has to build the cache for the new apps. Same as when you do the "wipe Dalvik and cache" part of standard flashing procedure to avoid conflicts. In order for apps to load quickly, Android stores a lot of the necessary data in cache, so when you clear it or have new apps, it has to rebuild the cache. On Lollipop this takes a loooooooong time because of the way ART works.
Planterz said:
The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
Click to expand...
Click to collapse
How can i be completely sure that it's the battery which needs to be replaced? The battery shows charge. When i plug in and boot up it shows enough battery power left.
Currently, without external power it does not go past the google screen on boot. When i plug in power while device is off, the battery meter shows just a little depletion from full charge. When turned on, battery level is 82 %
After all , all this hardware mess up can be the consequence of a bad cm flash ?
the whole "optimizing app" thing is the OS rebuilding the cache.
Click to expand...
Click to collapse
I know this. Earlier it was happening on each boot. Now it seemed to be stopped.
By any chance did you have your phone charging while flashing and booting up your ROM?
ChainFires Son said:
By any chance did you have your phone charging while flashing and booting up your ROM?
Click to expand...
Click to collapse
May be? But not the the first time
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Click to expand...
Click to collapse
Exactly same problem is started with my Nexus 4 ... I really wonder, what is causing this. Meanwhile, have it sorted for you ? is that hardware (Battery) issue?
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself...
Click to expand...
Click to collapse
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
shazR00t said:
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
Click to expand...
Click to collapse
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
I also got the same problem. I thought this is battery problem, so I replaced the battery but problem still there. I thought this is problem of lollipop, never installed CM or anything. It is always running stock android. After that I even downgrade to Kitkat stock version still it is not working. One more thing I noticed is If I don't unlock the device than it will be powered on, but as soon as I unlock it and if it is not plugged in to charger it will be switched off. Any suggestion what should I do?
I have the same thing for several month now.
Always thought it is the dying battery.
theminikiller said:
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
Click to expand...
Click to collapse
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
shazR00t said:
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
Click to expand...
Click to collapse
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
theminikiller said:
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
Click to expand...
Click to collapse
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the image files. If you did that then u don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 20:42 ---------- Previous post was at 20:41 ----------
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the images. If you did that then I don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
I m too facing the similar issues. Phone is getting turned off suddenly when not charging, on charging it is working fine. i have done factory reset and also done factory image reset to 5.1.0. i m still facing the same issues. I don't think so it is related to battery. if anyone have the solution then please let me know.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Try the very basic flash technique by double clicking the flash-all.bat. It's not the same as flashing the imgs one by one.
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
gautam.is.sharma said:
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
Click to expand...
Click to collapse
Ok so Battery was the problem!! Got it changed, phone working fine now. Thanx all!
Ok guys i confirm that this is a battery issue. I took it to the service center and the guy temporarily replaced battery to show me issue solved... But... there i saw another issue due to which i did not buy the battery. I saw half the touchscreen not working (including the navigation buttons ). The guy at the center told its a h/w issue and i would have to spend 7K on it so i left my phone dead for now. The Question is ... can this be a s/w issue.. or result of bad flash which can solve on reflashing ??
same problem with my nexus ,but one thing i noticed that the phone does not power off while in recovery...Any idea??
A little bit of background.
Prior to this problem I was running dirty unicorns and elementalx kernel. Given that lately I had some freezing issues I decided that iro was time to update my ROM. Being the first time that I manually update a ROM and not having found anything online I thought (dumb decision) that all I had to do was to flash the most recent version. After I did that the phone did an app optimization (idk if that's how it's called, basically it optimised all the apps for the new version of the ROM) . After that the phone wasn't booting up, the dirty unicorns loading screen was running for half an hour and nothing happened so I restated the phone. When it asked for my sequence a message popped up "it looks like your vendor image is obsolete". The phone still wasn't booting up so I decided to restart once again and install the latest vendor image. After that the phone wasn't booting up so I decided to do a backup with twrp (version 3.0.0.0) and do a factory reset.
Plot twist the twrp decryption sequence (that worked 10 minutes before) now wasn't working so I had no way to access any of the phone's files.
Basically the phone won't turn on and I have no way of accessing it's files
I'd try a factory reset but there are some photos and whatsapp messages that are important to me and I'd rather not lose them.
Any tips?
Apologies for my terrible English
JustJohnItalia said:
A little bit of background.
Prior to this problem I was running dirty unicorns and elementalx kernel. Given that lately I had some freezing issues I decided that iro was time to update my ROM. Being the first time that I manually update a ROM and not having found anything online I thought (dumb decision) that all I had to do was to flash the most recent version. After I did that the phone did an app optimization (idk if that's how it's called, basically it optimised all the apps for the new version of the ROM) . After that the phone wasn't booting up, the dirty unicorns loading screen was running for half an hour and nothing happened so I restated the phone. When it asked for my sequence a message popped up "it looks like your vendor image is obsolete". The phone still wasn't booting up so I decided to restart once again and install the latest vendor image. After that the phone wasn't booting up so I decided to do a backup with twrp (version 3.0.0.0) and do a factory reset.
Plot twist the twrp decryption sequence (that worked 10 minutes before) now wasn't working so I had no way to access any of the phone's files.
Basically the phone won't turn on and I have no way of accessing it's files
I'd try a factory reset but there are some photos and whatsapp messages that are important to me and I'd rather not lose them.
Any tips?
Apologies for my terrible English
Click to expand...
Click to collapse
The best thing to do is this guide. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page384. Just go full stock without formating the internal. Flash twrp and see if you can get your photos. Next time back your photos up with Google photos if available in your area. Good luck
JustJohnItalia said:
A little bit of background.
Prior to this problem I was running dirty unicorns and elementalx kernel. Given that lately I had some freezing issues I decided that iro was time to update my ROM. Being the first time that I manually update a ROM and not having found anything online I thought (dumb decision) that all I had to do was to flash the most recent version. After I did that the phone did an app optimization (idk if that's how it's called, basically it optimised all the apps for the new version of the ROM) . After that the phone wasn't booting up, the dirty unicorns loading screen was running for half an hour and nothing happened so I restated the phone. When it asked for my sequence a message popped up "it looks like your vendor image is obsolete". The phone still wasn't booting up so I decided to restart once again and install the latest vendor image. After that the phone wasn't booting up so I decided to do a backup with twrp (version 3.0.0.0) and do a factory reset.
Plot twist the twrp decryption sequence (that worked 10 minutes before) now wasn't working so I had no way to access any of the phone's files.
Basically the phone won't turn on and I have no way of accessing it's files
I'd try a factory reset but there are some photos and whatsapp messages that are important to me and I'd rather not lose them.
Any tips?
Apologies for my terrible English
Click to expand...
Click to collapse
To update a ROM all you usually need to do is flash the newer version, but you also need to flash the newer vendor.img of the updated ROM is based on a newer Google build. Failure to do this is what caused the "it looks like your vendor image is obsolete" message to appear. I'm guessing you know this though as you went on to flash it later.
Not sure what happened with TWRP but you've done something else wrong at some point. Best idea (as pointed out above) is to flash the factory images. You can try it without formatting userdata in order to retrieve whatever it is that's important on your storage, but once you've retrieved whatever you need (if you even can) you'll need to format it because you really need to start fresh.
Hey all! I'm having a strange issue regarding boot looping that I can't seem to find an answer to on here or anywhere else, I hope you guys can help.
So my T-Mobile Samsung Galaxy S5 (SM-G900T), purchased in May 2014, while perusing Facebook the other day, randomly shut down in the middle of perfectly normal use and started bootlooping. I had never had the problem before. The device had been rooted for months (I forget what method I used) but it was running a stock Lollipop rom. The first thing I did was factory wipe and cache wipe through Android stock recovery. It worked!... for a couple hours. Then the bootloop started again.
I went and sought a new stock rom, believing that somehow mine had been corrupted, and flashed it via Odin. I also flashed TWRP. Clean wipes, new rom, dalvic/etc. wipes, and booted into stock Marshmallow. It worked!... for a couple hours. Then it started bootlooping again. I went into TWRP and tried to wipe just caches and whatnot, but it wouldn't start again. Long battery pulls sometimes allowed the phone to boot, but it started looping again after ~5-10 minutes.
So I installed the Twisted Lollipop but couldn't even get that to boot. I went back and found the earliest available firmware for my device (as I bought mine right after it came out) and flashed it. Wipe wipe flash wipe whatever, and a succesful boot. It was looking good! I was able to install a number of OTA updates. I was at Android 5.1 when I decided to call it a night and hold off on the further OTAs for today. Today I got up and got ready for work, all's well. As I'm getting ready to leave, I allow Google to update some apps, and begin installing Facebook, Spotify, Cap Metro (for my area's public transit system) and maybe something else, I don't remember. Anyway, as the updates are downloading or installing and I'm checking my email, boom, crash, bootloop.
What's going on here? I've never heard of hardware causing boot loops, but could it be that? I dropped my phone (although protected by a Spigen case) earlier this summer and it cracked the screen-- could it have messed with the motherboard in some substantial way? I had noticed it getting hotter and the battery lasting less than usual, but I attributed that to the device's age.
Any help, any advice, any direction you could give would be extremely appreciated. I don't have the capital to replace the phone right now, and I use it all the time. Thanks folks!
So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt