I might as well try here if anyone will see my post.
I'm screwed. Latest stock ROM, unrooted and locked bootloader. I have/had the Google App (beta) installed on my phone but for the past couple of days it was constantly crashing and my phone became sluggish so I decided to uninstall it today. I left the beta program and as provided with instructions there went to uninstall the beta version to install the non-beta one.
It stayed on "uninstalling" for about 10 minutes and I presumed it was just a Google Play glitch and decided to reboot my phone. Big mistake! After the first install it was optimizing apps (but only one, so it was probably the Google App but it never got out of the next step (starting system/app, I don't recall what it said exactly right now)). I decided, stupidly, to reboot the phone since it was stuck and now I'm stuck on a bootloop and the phone won't even go past the Android logo animation. I guess the uninstallation never completed somehow and the app got corrupted(?).
I'm lost and I don't know what my options are except trying a factory reset and/or even unlocking the bootloader and getting a custom recovery and potentially rooting the phone too. But I really don't want to lose my data!! I have no backups.
Is there ANY chance I could somehow manage to solve the problem? Is it possible to sideload an app with a locked bootloader and stock recovery? I'm trying to sideload the Google app back in case it got corrupted but it doesn't work. I get the following errors:
Code:
E: footer is wrong
E: signature verification failed
installation aborted
Haaalp!
EDIT: Even weirder. I just let it run the booting sequence again and it got beyond the lollipop logo animation and is now stuck on "Android is starting... Starting apps." message.
Related
Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.
Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-
So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.
I rooted my device using king root, in that state i got the notification for an official update. I went to settings, about phone, and updated. after it rebooted, it started installing the update. halfway through the the status bar was a little less half full, it stopped and booted normally. It said the the update installation was unsuccessful. I remembered that i had the stupid kingroot, so i uninstalled it, it rebooted, everything so far so good. i went just to double check the OS version currently installed, still on 5.0.2 Lollipop. This time i went ahead and started installing the update. I noticed that this time it looked fine because the status bar didn't stop halfway through like last time. It kept going until it was more than half full. So I was like "ok, lets just leave it for now to do its job and ill look at it later" Later, I looked and it had a black screen with the android model with an exclamation mark. It said: "No Command" I decided not to **** with it, so i jut left it. I went to Motorola's website, and chatted with one of their technicians. She told me to factory reset it. She gave me instructions on how to do that, Which those instructions did not work. I went on YouTube and figured out a way on how to get into recovery mode and factory reset it, and that was what i did of course. Now all it does is boot, show me android model, power off. Then it keeps doing the same thing over and over until the battery dies, or i force to shut down from recovery mode. BTW i still can access recovery mode, and everything is useless and leads to boot-loop thing i just mentioned. Please help i feel like i really ****ed it up.
XDA Visitor said:
I rooted my device using king root, in that state i got the notification for an official update. I went to settings, about phone, and updated. after it rebooted, it started installing the update. halfway through the the status bar was a little less half full, it stopped and booted normally. It said the the update installation was unsuccessful. I remembered that i had the stupid kingroot, so i uninstalled it, it rebooted, everything so far so good. i went just to double check the OS version currently installed, still on 5.0.2 Lollipop. This time i went ahead and started installing the update. I noticed that this time it looked fine because the status bar didn't stop halfway through like last time. It kept going until it was more than half full. So I was like "ok, lets just leave it for now to do its job and ill look at it later" Later, I looked and it had a black screen with the android model with an exclamation mark. It said: "No Command" I decided not to **** with it, so i jut left it. I went to Motorola's website, and chatted with one of their technicians. She told me to factory reset it. She gave me instructions on how to do that, Which those instructions did not work. I went on YouTube and figured out a way on how to get into recovery mode and factory reset it, and that was what i did of course. Now all it does is boot, show me android model, power off. Then it keeps doing the same thing over and over until the battery dies, or i force to shut down from recovery mode. BTW i still can access recovery mode, and everything is useless and leads to boot-loop thing i just mentioned. Please help i feel like i really ****ed it up.
Click to expand...
Click to collapse
Hello,
I'd recommend you to restore your device back to stock firmware Restore to Stock][XT1068][All Dual Sim Model][4.4.4] with fastboot.
Also, I would advice you not to flash bootloader again. (Since if yours is updated with marshmallow one, flashing the older one (downgrading) might end in a brick).
-Vatsal
last step fail
Vatsal said:
Hello,
I'd recommend you to restore your device back to stock firmware Restore to Stock][XT1068][All Dual Sim Model][4.4.4] with fastboot.
Also, I would advice you not to flash bootloader again. (Since if yours is updated with marshmallow one, flashing the older one (downgrading) might end in a brick).
-Vatsal
Click to expand...
Click to collapse
at the last step, it fails to verify the package and aborts package installation. what now?
waseem98 said:
at the last step, it fails to verify the package and aborts package installation. what now?
Click to expand...
Click to collapse
Hello,
You may try posting your query in the thread I linked above with all relevant logs, the experts there maybe able to assist you.
-Vatsal
I am asking this mainly because I hope I'm wrong about my own assumption.
My phone recently started randomly rebooting itself. At a certain point I woke up and the battery was dead. So recharged it and found it not getting passed the Samsung logo. Thought it was a xposed module since it had been acting up since I activated that again. So decided to disable xposed completely without any luck.
At that point I have tried to put a new rom on it. First time it rebooted during the installation throuwh TWRP. Second time it actually completed the installation and I managed to get into the OS.
But when I tried to install an application through the Google Play Store, in this case Chrome, it rebooted again and get stuck in the boot loop again for a while until booting up again but as soon as I tried to install the app again it crashed again and this kept going.
Have now also tried to install a different rom but the phone either crashes during the installation in TWRP or afterwards while it's trying to boot at the flashing samsung logo.
My assumption is that the problem is hardware related since it happens with multiple roms and even during the installation of said roms. But I really hope I'm wrong about this.
It's a SM-925F if that is important to know somehow.
I was running KatKiss 4.4.4 on TWRP v2.6.3.0.
Lately it was getting extremely slow. Yesterday I removed some apps I didn't use anyway. I think I removed too much perhaps because today suddenly gapps and many other things started crashing.
I thought I'd just reinstall it, and discovered there's now a KatKiss 6.0.029:
https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496
so I downloaded it, and all the other files, rebooted into TWRP and wiped, and tried the install - it just left me with a boot loop. Ugh.
Got back into TWRP and happened to format everything. Then I installed Universal Naked Driver 0.72 in Win10.
Current behaviour:
Regular reset: boot loop.
Power+up: APX mode.
Power+down: tiny menu, then boot loop after cold boot.
Power+down+up: TWRP.
EasyFlasher asks me to go into APX, then I select one of TWRP 2.2.1 and RogueXM and Roach CWM and even the WW_epaduser9_2_1_24UpdateLauncher.zip file, but in all cases it's just the same. There's some text output, then suddenly a 0.001ms black popup disappearing before I can read it, then the regular window says OK. BUT... there is no change at all.
Any idea what I can try? I searched a lot before deciding to ask here.
The KatKiss link above assumes that the files are already inside the TF101.
How do I put the files into the TF101? What is the next step?
After mannnnnnny hours, I actually managed to install and run the Asus ROM.
I went on to TWRP 2.8.1.1, KatKiss 6.0.029 and the belonging files. Now it's booting up Android, but... not very far.
It keeps complaining with many popups "Google Play services stopped". Is that normal for a fresh ROM?
I add Wifi - then it gets stuck on Checking Connection "it can take a while". It's now more than half an hour. How long is a "while" normally?
I gave up on KitKat 6 and went back to 4.4.4 which then starts.
Still the weird frequent popups "Google Play services stopped".
Reinstalled three times now (KitKat and gapps) and still the same problem.
Could this be a hardware problem?
Well, for all you who read all the above (no one? lol), it is not a hardware problem. It's google messing up: https://forum.xda-developers.com/ee...google-play-services-update-breaking-t3555444
Hi everyone last night i decided to root my ohone. I have had it for a while but for some reason hadn't got round to doing it.
I followed all the instructions firstly unlocking bootloader, TWRP then installing no verity and magisk etc and every looked to be good phone starts up with the the your device has been unlocked message and something about bad id key but then would start like normal and set about installing all my apps etc again for the phone to be back to how it was just rooted.
However tonight i restarted my phone and when it's went to start up it throws me into the fast loader screen wtih your device didnt stat up successfully use the software repair assistant on computer to repair your device.
I had only been installing my usual apps/ new luancher etc... however the only thing i think that could have caused an issue was i checked for an android version update and it found i already had the most up to date one so nothing was downloaded but possibly just checking has caused an issue ?
Any help with this would be appreciated.
I can still boot into team win recovery mode but was hoping as i've now installed everything a new... i could resolve this without another fresh install if possible ?
Thanks
fendertele said:
Hi everyone last night i decided to root my ohone. I have had it for a while but for some reason hadn't got round to doing it.
I followed all the instructions firstly unlocking bootloader, TWRP then installing no verity and magisk etc and every looked to be good phone starts up with the the your device has been unlocked message and something about bad id key but then would start like normal and set about installing all my apps etc again for the phone to be back to how it was just rooted.
However tonight i restarted my phone and when it's went to start up it throws me into the fast loader screen wtih your device didnt stat up successfully use the software repair assistant on computer to repair your device.
I had only been installing my usual apps/ new luancher etc... however the only thing i think that could have caused an issue was i checked for an android version update and it found i already had the most up to date one so nothing was downloaded but possibly just checking has caused an issue ?
Any help with this would be appreciated.
I can still boot into team win recovery mode but was hoping as i've now installed everything a new... i could resolve this without another fresh install if possible ?
Thanks
Click to expand...
Click to collapse
You could try reflashing the boot.img
What does getvar all say?
Code:
fastboot getvar all