Hi, I flashed CM 10.2 on my Galaxy S4, and I used titanium backup to restore all my apps, only apps I didn't choose was TouchWiz and the TouchWiz simpler one. And it said I needed to reboot my device for the changes to apply, so I did that. When I rebooted it said everything stopped working. Even the core thing. Screen went black. Then I took out the battery and when I tried to go to my custom recovery, it just skipped the recovery screen and booted into cm again and same thing happened. Everything just stopped working. Help please. Also I am able to get into download mode. I just don't know how to recover from this. I am running 4.3.1 cm nightly, well I was. I don't know if I could count it was 4.3
if you are able to access the download mode then flash a stock rom. then root your device again.
Related
So, I was running Cyankang 4.3 ROM, and everything was good. I tried the new nightly with PDROID, and everything was fine, except I was having some issues with some apps. So I went to the nightly W/O PDroid, and now everytime I try to reboot, it just hangs at the black screen, I have to restore to a previous version (9/18) that I had on it. But that's not all, even after I restore to that version, if I need to reboot, it gets stuck as well, and I have to restore again in order to get it to boot.
I'm about to go back to stock at this point, it's pissing me off.
Hi everyone, this is somewhat complicated and il try my best to describe what happened.
My device is a i747m (rogers).
I was running CM10.1 (running gapps-jb-20130812 and CWM recovery 6.0.4.3) for a long time, tried to update to 10.2.
(i messed up on 2 things.I don't think i cleared neither of the cache or data and also didn't have proper gapps which would be 20130813).
After installing 10.2 through recovery, it would just stay in the boot Cynogen booting logo.
i restarted into recovery, since my old CM10.1 zip was still there, i installed that instead, but same thing happened, it would just stay at booting logo.
I had made a nandroid back up from before all of this, and so i wiped data, dalvik cache, cache, formatted system, and i recovered into that, which was a stock 4.1.2 rooted (rogers).
However, nothing worked, only WiFi. I couldn't make any phone calls, send/receive messages, or get data.
I then used ODIN 3.07 to flash the new stock 4.3 rooted (rogers). WiFi worked as before, but i still couldn't make any phone calls, send/receive messages, or get data.
i then re-installed the latest recover 6.0.4.5, and installed paranoid android 4.4.2 and gapps for this version. But still nothing, so i went back to the stock 4.3 rooted.
4 months ago, when i made the nandroid back up, i also made an IMEI back up as well (i did not do a full imei/NV/EFS/IMSI/data backup) , i only had my IMEI backup, so i wrote using "NV items reader writer" the IMEI back onto my phone, and now i can recieve/send messages, and get phone calls and make phone calls. wifi also works.
But my data is stuck in Edge, its extremely slow, takes 10min to download a 15mb file.
so far:
-The APN settings are correct
-my IMEI number in settings menu, matches the one on the back of my phone.
-network mode is GSM/HSPA/LTE
-i have installed the latest modem for i747m through CWM recovery and also tried slightly older versions.
i am pretty much lost and i dont know what i should do.
-rogers has told me to use kies and perform backup and then recovery, apparently that will factory reset my phone.
-should i simply use kies to install the latest 4.3?
-does anyone have the imei/NV/EFS/IMSI/data files? or the full NV file?
-should i install CWM recovery and wipe everything that i can? and re-install stock rooted 4.3?
-should i use QPST to fix my IMEI? <-- dont know anything about this, noticed a few threads.
i have used these threads in all my rooting and so forth.
http://forum.xda-developers.com/showthread.php?t=2179330
http://forum.xda-developers.com/showthread.php?t=1831898
http://forum.xda-developers.com/showthread.php?t=2129993
please someone help me out, I dont know how to fix this.
thank you for reading this long and complicated problem.
same problem, ive spent every minute working on it for a week
Hi,
I was on the paranoid 4.4.4 rom on my I9300, everything worked fine.
I did the last update with paranoid 5.1.1 but it didn't worked well, i have multiple error and Google service won't work anymore.
The thing is, i can't do anything at all, like restore my last backup because i lost the root access with the update.
I can't load in recovery mode, i tried the HOME+VOLUME DOWN (or up) + POWER, it won't work.
I can't fine the debug mode on this version, so i really don't know how i can at least restore my last backup to go back to the 4.4.4 version.
Any help is appreciated, thaks for your time.
Root doesn't ship with any 5.x build of paranoid android. To reset you need to boot into recovery and restore your backup or flash a different ROM.
You don't need root access for that.
It sounds like you installed an incompatible gapps....
Thanks for your reply,
I managed to boot in recovery, using a method i found on the web, i pull the battery then hold the combination keys when i put it back, and it load in recovery just fine.
I think i couldn't install the proper gapps because i was in clockwork recovery, i installed the latest TWRP, but i still can't manage to install the latest paranoid rom prpoperly.
here's what i did so far:
- wipe all/ factory reset , install Paranoid5.1.1 + Gapps 5.1 mini => paranoid load but Black screen once it's loaded with the message "Android.phone interrupted" (gross traduction) popping every 2 sec, it disapear if i put the phone on airplane mode => make me think the Google service can't connect.
- Restore my last 4.4.4 backup then => wipe cache/dalvik=>install Paranoid 5.1.1 + gapps => same as the previous problem, but this time i have my old app and i can call and receive sms.
My guess so far is a problem with the Google service who can't synchronize, the Gapps i try to use are the pa_gapps-modular-pico-5.1-20150315-signed.zip
Any guess ?
Yeah. The problem is you are using old gapps. Use banks gapps
I had trouble with a clean install of PA 5.1 + Gapps on my S3 (i9300) and similar issues to yours, not sure why but I found that if I used th full fat "Stock" 5.1 Gapps the phone was fine and has been for a day or 2 now, the pico/mini/full seemed to be problematic (at least for me). Also moved to Philz Recovery using the "Rashr" app as my old CWM kept throwing an error of status 6 on any Gapps I downloaded... Must admit though that once stable PA Lollipop runs well on the S3 and battery seems better over the past couple of days too...
Phone was originally bone stock, I then rooted & installed TWRP recovery, booted into TWRP and did the Backup option and saved it to SD Card, I then flashed CM 12.1 and used it for a little over a month, trying the various Nightly updates.
I decided to go back to the stock rom I had backed up previously, It restores successfully but when I boot the phone everything is crashing once it hits the home screen, "Unfortunately xxxx has stopped" is seen over and over, I can't load anything, even the settings menu crashes.
I then tried rebooting into TWRP and did Factory reset but when I do this It wont ever get past the Samsung logo on reboot.
Not sure what went wrong with the backup or if Im missing a step? I also tried enabling the verify MD5 check option for the Backup and it says everything is fine.
For now I'm back in CM 12.1, Any ideas appreciated!
mathesar said:
Phone was originally bone stock, I then rooted & installed TWRP recovery, booted into TWRP and did the Backup option and saved it to SD Card, I then flashed CM 12.1 and used it for a little over a month, trying the various Nightly updates.
I decided to go back to the stock rom I had backed up previously, It restores successfully but when I boot the phone everything is crashing once it hits the home screen, "Unfortunately xxxx has stopped" is seen over and over, I can't load anything, even the settings menu crashes.
I then tried rebooting into TWRP and did Factory reset but when I do this It wont ever get past the Samsung logo on reboot.
Not sure what went wrong with the backup or if Im missing a step? I also tried enabling the verify MD5 check option for the Backup and it says everything is fine.
For now I'm back in CM 12.1, Any ideas appreciated!
Click to expand...
Click to collapse
Have you tried the wipe option.. for a clean install?
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S