Hey,
I have been using CM10 Paranoid Android since it came out on the Note, I am on 2.51 version.
Yesterday my SD Card wouldn't mount so I rebooted the phone, after the reboot it got stuck on the animation (Jelly Bean Android). So I rebooted it again and this time it booted, but every application was 'Not Responding' I couldn't even get to the lock screen.
Ever since then I can't boot it up it stays on the Jelly Bean Man animation. Keep in mind I didn't install any apps, I didn't update the Rom since it came out ( a few months ), it just randomly stopped working.
I am wondering what to do.
Thank you.
Start with cleaning cache and dalvik cache in your recovery.
ThaiDai said:
Start with cleaning cache and dalvik cache in your recovery.
Click to expand...
Click to collapse
Did that, still no success.
mikus123 said:
Did that, still no success.
Click to expand...
Click to collapse
If you have a backup of your Rom (made in recovery) and/or backups of your Apps (made with Titanium Backup):
Factory reset and reinstall this Rom or install another (JB stock) Rom.
If you do not have backups:
Factory reset and reinstall this Rom or install another (JB stock) Rom.
And be sorry, that you didn't make backups.
ThaiDai said:
If you have a backup of your Rom (made in recovery) and/or backups of your Apps (made with Titanium Backup):
Factory reset and reinstall this Rom or install another (JB stock) Rom.
If you do not have backups:
Factory reset and reinstall this Rom or install another (JB stock) Rom.
And be sorry, that you didn't make backups.
Click to expand...
Click to collapse
Do you have any idea what happened? It was so spontaneous. I have a back up of the ROM, however it was before I installed APPS, and TB didn't work on my phone so I could never back them up.
So factory reset is the only way?
mikus123 said:
Do you have any idea what happened? It was so spontaneous. I have a back up of the ROM, however it was before I installed APPS, and TB didn't work on my phone so I could never back them up.
So factory reset is the only way?
Click to expand...
Click to collapse
If TB never worked there was already something wrong with your configuration.
No, I don't have an idea what could be wrong - only hoping that it isn't a hardware problem.
Yes, that's why I would install a stock JB rom with PC Odin first: if this succeeds you'll have working configuration again - if if fails we can analyze the errors in PC Odin.
Related
Alright, Here's the scenario : My phone was working fine, I tried installing the DoCoMo SystemUI here and the All-in-One add-on, Installed normally, cleared cache & dalvik, rebooted, the boot animation plays for a few seconds, it freezes and then the phone restarts. I tried clearing data, then re-installed the JB rom, then i cleared System, Data, Cache, .android_secure and even SD Card (basically everything except ext. SD) then installed CM10.1 from recovery and still the same thing, Bootlooped at boot animation.
And the phone won't charge offline normally, it charges for a while (like 10 seconds) then it starts itself and get into the bootloop.
As formatting everything and installing again didn't help, I don't think FlashTool will, but I'm downloading the 9.1.A.1.140 FTF now and I'll try it tomorrow (slow internet).
Is it possible that the phone is hard-bricked and can't be rescued? If not what else can I do to bring it back to life?
If it was hard bricked it would not boot at all, it would be totally unresponsive (Just like a brick)
Were you on cm10 before?
If so you you cant install those stock based add ons, you should be able to restore your backup. What happens when you do that? (You did make a backup didnt you? Always backup just in case it f**** up!)
If you were not on cm10 before then you need to have an unlocked bootloader to flash cm10, make sure you have unlocked.
gregbradley said:
If it was hard bricked it would not boot at all, it would be totally unresponsive (Just like a brick)
Were you on cm10 before?
If so you you cant install those stock based add ons, you should be able to restore your backup. What happens when you do that? (You did make a backup didnt you? Always backup just in case it f**** up!)
If you were not on cm10 before then you need to have an unlocked bootloader to flash cm10, make sure you have unlocked.
Click to expand...
Click to collapse
I don't have a backup, but would it matter because it only backs up data, system, cache, and .android_secure and I formatted all of them and did a clean install of both official JB and then CM10.1, Same thing for both. That's why I'm scared, I did a clean install but it still bootloops. (OFC my BL is unlocked)
AliAlsuhail said:
I don't have a backup, but would it matter because it only backs up data, system, cache, and .android_secure and I formatted all of them and did a clean install of both official JB and then CM10.1, Same thing for both. That's why I'm scared, I did a clean install but it still bootloops. (OFC my BL is unlocked)
Click to expand...
Click to collapse
a backup backups everything.
You have yet to tell me which rom you were on, informtion like that will help me help you. Please answer all my questions
which kernel is currently installed on your phone?
YES! FlashTool has fixed it!
And I was on stock rom and DooMKernel at the moment of installation.
Hello then!
The situation is as follows:
- Done a nandroid backup using a certain kernel and CWM
- Installed various ROMs
- Trying to restore my original ROM, using the same kernel and CWM version that created it
- The system boots, showing the startup animation (in this case the cellphone carrier animation, after the Samsung logo) and gets stuck, vibrating every once in a while like in forced-closes.
My guess is that some system process crashes or fails to start, dragging the rest of the system with it. I just don't know why it would happen after a nandroid recovery with the same kernel and CWM version, factory wipe, formatting etc.
- Tried a factory reset + cache wipe + dalvik cache wipe
- Tried formatting the various partitions and re-partitioning using a 512 PIT file
- Tried flashing similar (slightly earlier or later) ROMs through Odin, then restoring
I do have a Titanium backup in place, but not an Odin-flashable version of this ROM, so this isn't the end of the world, but it will force me to switch a ROM at an odd timing if I don't solve this.
Any ideas?
tempnick said:
Hello then!
The situation is as follows:
- Done a nandroid backup using a certain kernel and CWM
- Installed various ROMs
- Trying to restore my original ROM, using the same kernel and CWM version that created it
- The system boots, showing the startup animation (in this case the cellphone carrier animation, after the Samsung logo) and gets stuck, vibrating every once in a while like in forced-closes.
My guess is that some system process crashes or fails to start, dragging the rest of the system with it. I just don't know why it would happen after a nandroid recovery with the same kernel and CWM version, factory wipe, formatting etc.
- Tried a factory reset + cache wipe + dalvik cache wipe
- Tried formatting the various partitions and re-partitioning using a 512 PIT file
- Tried flashing similar (slightly earlier or later) ROMs through Odin, then restoring
I do have a Titanium backup in place, but not an Odin-flashable version of this ROM, so this isn't the end of the world, but it will force me to switch a ROM at an odd timing if I don't solve this.
Any ideas?
Click to expand...
Click to collapse
Yes , you must flash the same version of android how the nandroid is.
When Nandroid is made while using ICS 4.0.4 then flash a 4.0.4 based rom then you can restore it.
SOLVED
kevinrus123 said:
Yes , you must flash the same version of android how the nandroid is.
When Nandroid is made while using ICS 4.0.4 then flash a 4.0.4 based rom then you can restore it.
Click to expand...
Click to collapse
That much I already know.
What finally solved it is this procedure: It seems that the carrier ROM that I had (in a *.tar file) wasn't enough for resetting the device, and flashing one of the ROMs listed in this thread did the job. I then flashed the carrier ROM and the CF-Root kernel, which I had before, and successfully restored everything from my nandroid backup.
tempnick said:
That much I already know.
What finally solved it is this procedure: It seems that the carrier ROM that I had (in a *.tar file) wasn't enough for resetting the device, and flashing one of the ROMs listed in this thread did the job. I then flashed the carrier ROM and the CF-Root kernel, which I had before, and successfully restored everything from my nandroid backup.
Click to expand...
Click to collapse
Nice to hear that it's fixed now
Hi there,
I recently rooted and flashed a custom ROM onto my Samsung Galaxy S3 Mini. I'm very new to this thing and find everything quite overwhelming, but I want to learn.
I flashed this ROM - http://forum.xda-developers.com/showthread.php?t=2119219 (the v6 No Wipe version because I was petrified about losing my data if I factory reset), but the phone is now extremely laggy and buggy, so I want to go back to the stock ROM (so I can do a nandroid backup) and then try a different custom ROM like Dmod.
So, my question is, do I have to factory reset my phone to go back to stock? Or can I just flash this file (http://hotfile.com/dl/189271016/833...T-I8190N-BTU-I8190NXXALL6-1356151513.zip.html) using the CWN recovery menu without wiping? I'm asking because my phone keeps giving me an error everytime I try to backup using the CWM Recovery menu.
Thanks and if you need me to explain something in further detail, let me know.
YamiWheeler said:
Hi there,
I recently rooted and flashed a custom ROM onto my Samsung Galaxy S3 Mini. I'm very new to this thing and find everything quite overwhelming, but I want to learn.
I flashed this ROM - http://forum.xda-developers.com/showthread.php?t=2119219 (the v6 No Wipe version because I was petrified about losing my data if I factory reset), but the phone is now extremely laggy and buggy, so I want to go back to the stock ROM (so I can do a nandroid backup) and then try a different custom ROM like Dmod.
So, my question is, do I have to factory reset my phone to go back to stock? Or can I just flash this file (http://hotfile.com/dl/189271016/833...T-I8190N-BTU-I8190NXXALL6-1356151513.zip.html) using the CWN recovery menu without wiping? I'm asking because my phone keeps giving me an error everytime I try to backup using the CWM Recovery menu.
Thanks and if you need me to explain something in further detail, let me know.
Click to expand...
Click to collapse
That firmware is a zipped odin-file. Can't be flashed in CWM.
Make a cwm nandroid backup of your "/data" to your external sd (that's your installed apps)
You can also backup your apps and appdata using titanium backup or similar, for later restore.
Just remember to never backup/restore systemapps.
Backup internal sd to computer just to be sure, if you in any situation have to make a factory reset. Make sure any kind of backup is on your external sd before you make factory reset, or it will be lost forever
YamiWheeler said:
Hi there,
I recently rooted and flashed a custom ROM onto my Samsung Galaxy S3 Mini. I'm very new to this thing and find everything quite overwhelming, but I want to learn.
I flashed this ROM - http://forum.xda-developers.com/showthread.php?t=2119219 (the v6 No Wipe version because I was petrified about losing my data if I factory reset), but the phone is now extremely laggy and buggy, so I want to go back to the stock ROM (so I can do a nandroid backup) and then try a different custom ROM like Dmod.
So, my question is, do I have to factory reset my phone to go back to stock? Or can I just flash this file (http://hotfile.com/dl/189271016/833...T-I8190N-BTU-I8190NXXALL6-1356151513.zip.html) using the CWN recovery menu without wiping? I'm asking because my phone keeps giving me an error everytime I try to backup using the CWM Recovery menu.
Thanks and if you need me to explain something in further detail, let me know.
Click to expand...
Click to collapse
Backup your data in CWM, flash my ROM and restore your data with CWM.
Benzonat0r said:
Backup your data in CWM, flash my ROM and restore your data with CWM.
Click to expand...
Click to collapse
CWM has NO choice to backup/restore only parts of the device. Only a full backup is possible.
This is only in TWRP. Pity! I only use CWM because TWRP makes corrupted backups (three times) for me.
Or is it possible to pick out only DATA from the backup? And what is happen with the dalvik cache, which
consists of the byte-code for all installed apps, optimized for the ROM which created it?
"advanced restore and restore only /data". Is this the way in CWM that you mean @benz?
JackoMJ
Yes that's exactly what I meant, "advanced restore and restore only /data"
You don't have to worry about cache and dalvik because it's automatically created on the initial start.
thx for the information Benz (usefull in the future perhaps),
but i´ve decided to use Titanium Backup.
JackoMJ
So I was on cm10.2 . Today i just wanted to use some stock experience for sometime as my exams are near so i wanted a stable rom.
So i tried to restore the Nand Backup from CWM. Restore was successful , Phone Boots everything is fine till that. After i enter to the setup wizard(Coz i wiped the data before making the backup) this error : Unfortunately the process com.google.gapps has stopped.
If i skip this then Setup Wizard Force Closes and then am not able to access anything on the phone. Everything seems to be force closing randomly?
Any Solution?
leo10messi said:
So I was on cm10.2 . Today i just wanted to use some stock experience for sometime as my exams are near so i wanted a stable rom.
So i tried to restore the Nand Backup from CWM. Restore was successful , Phone Boots everything is fine till that. After i enter to the setup wizard(Coz i wiped the data before making the backup) this error : Unfortunately the process com.google.gapps has stopped.
If i skip this then Setup Wizard Force Closes and then am not able to access anything on the phone. Everything seems to be force closing randomly?
Any Solution?
Click to expand...
Click to collapse
You have CM10.2 GAPPS (4.3) on 4.1.2 system. That is the problem. You should wipe system and preload partition before you did restore. Try it now again. Do wipes and restore backup again. Gapps are not in data paritition.
Im having a similar issue
Hi! the same is happening to me, but im sure i flashed the right gapps from cwm. also, i tryed to restore a previous back up, the restore seems succesfull but when i boot i still see the setup wizard, even when i flash the right gapps after restore. I tryed cleaning caché, doing a factory reset. I dont know what else to do. The last thing i was doing with my working phone was trying (but i uninstalled it after a while) swapper2. but i letft my sd card only with fat32 as in the begining.
shut_down said:
You have CM10.2 GAPPS (4.3) on 4.1.2 system. That is the problem. You should wipe system and preload partition before you did restore. Try it now again. Do wipes and restore backup again. Gapps are not in data paritition.
Click to expand...
Click to collapse
It didnt help....still got the same error. If i skip it...setupwizard also force clolses? :/
leo10messi said:
It didnt help....still got the same error. If i skip it...setupwizard also force clolses? :/
Click to expand...
Click to collapse
Try to install gapps for 4.1.2 JB.
shut_down said:
Try to install gapps for 4.1.2 JB.
Click to expand...
Click to collapse
But I backed up the stock ROM ... why should we restore flash gapps 4.1.2?
leo10messi said:
But I backed up the stock ROM ... why should we restore flash gapps 4.1.2?
Click to expand...
Click to collapse
I know I had similiar problems when I was going from CM to stock. I can't remember what exacly I did to solve it. I will look on some posts I wrote before. You have problems with gapps, that ia why it force close.
P.S. Solution for someone was to flash some custom ROM. Try with that.
Sent from my GT-I9070 using Tapatalk
shut_down said:
I know I had similiar problems when I was going from CM to stock. I can't remember what exacly I did to solve it. I will look on some posts I wrote before. You have problems with gapps, that ia why it force close.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
Ok mate let me know if you find the solution Thanks
At least you have stock backup in cwm. I created mine in twrp, therefore I cannot go back at all now with cwm restore...
jazzh said:
At least you have stock backup in cwm. I created mine in twrp, therefore I cannot go back at all now with cwm restore...
Click to expand...
Click to collapse
Put CoCore with TWRP on SD and install it from CWM.
I had same problem. I never use GAPPS, so I have not flashed the zip. Still I encountered this strange problem.
I found two possible methods which may help.
To restore 'stock JB backup' you must flash CM 10.1(4.2.2) or CM 10(4.1) and make sure you wipe data,cache and dalvik-c before and after flashing.
The from CM 10.1/10 recovery restore the stock JB backup.
If that did not work, the use ODIN to flash the stock JB firmware and then flash custom recovery. With this recovery you can restore either data or all of the partitions. GOOD LUCK
shut_down said:
Put CoCore with TWRP on SD and install it from CWM.
Click to expand...
Click to collapse
And what will I get, permanent twrp ? If yes, then that's it.
jazzh said:
And what will I get, permanent twrp ? If yes, then that's it.
Click to expand...
Click to collapse
Yes, we do not have temp TWRP.
Sent from my GT-I9070 using Tapatalk
shut_down said:
Yes, we do not have temp TWRP.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
can i restore my cwm backups from TWRP?
---------- Post added at 08:19 PM ---------- Previous post was at 08:12 PM ----------
well... after installing cocore with TWRP and then flashing gapps 4.1.2 from there, the problem persist. As i said before, after flashing stock rom from odin, then gapps from any recovery, the problem persist. wt* am i doing wrong!?
let me remember you, I am not who started this thread, but i have a similar issue.
Thanks
Edit: in order to bring you clues in case you may help me. I noticed that the keyboard doesnt show up if i try to write the password of the wi-fi network in setup wizard, also gapps still crashing as soon the phone boots and setup wizard after i try to skip it.
later edit: HEY HEY HEY! i noticed in "show log" option in cwm that after restoring the backup there are two issues:
I: Can't format unknow volume: /external_sd
I: Can't partition unsafe device: /dev/block/mmcblk0p8
hmmm... i didn't expect that.
keep updating: both cyanogen 10.0 and 10.2 don't even boot. they stay stucked in the pretty loading screen.
didn't find anything helpfull to do from recovery or odin
any clue?
just for the record (if anyone came here looking for an answer) i did a downgrade to 2.3.6 with this guide: (it is in spanish, but provides all the files and im sure you can find one in your language)
grupoandroid . com/topic/67294-gbguia-downgrade-de-jb-a-gb/ (delete spaces)
now i will upgrade to JB again, i hope that without problems.
edit: FUUUUUUUUUUUUUUUUUUU!
after 2.3.6 working without issues, flashed 4.1.2 from sammobile with odin (the same .md5 that i had for months!) and the problem came again. gapps error, and couldnt finish the setup wizard....
alete89 said:
just for the record (if anyone came here looking for an answer) i did a downgrade to 2.3.6 with this guide: (it is in spanish, but provides all the files and im sure you can find one in your language)
grupoandroid . com/topic/67294-gbguia-downgrade-de-jb-a-gb/ (delete spaces)
now i will upgrade to JB again, i hope that without problems.
edit: FUUUUUUUUUUUUUUUUUUU!
after 2.3.6 working without issues, flashed 4.1.2 from sammobile with odin (the same .md5 that i had for months!) and the problem came again. gapps error, and couldnt finish the setup wizard....
Click to expand...
Click to collapse
Ok, try to install some ROM now. I remember that someone solved with that. But manual mount system and preload partitions just in case.
I had similar problems after coming back from CM10 before.
If that do not help, (have CWM or TWRP) put some ROM zip on SD - wipe ALL (cache, dalvik cache, system, preload, factory reset) and install ROM again.
shut_down said:
Ok, try to install some ROM now. I remember that someone solved with that. But manual mount system and preload partitions just in case.
I had similar problems after coming back from CM10 before.
If that do not help, (have CWM or TWRP) put some ROM zip on SD - wipe ALL (cache, dalvik cache, system, preload, factory reset) and install ROM again.
Click to expand...
Click to collapse
I couldn't install CM10 or 10.2 from CWM after wiping cache, dalvik, system, preload, and factory. I got
"getprop(ro.build.product) = i9070, getprop(ro.product.device) = GT-I9070
error or something like that and i get stucked.
I'll downgrade again and keep it for one day until the night, i can't be without my phone one more day.
alete89 said:
I couldn't install CM10 or 10.2 from CWM after wiping cache, dalvik, system, preload, and factory. I got
"getprop(ro.build.product) = i9070, getprop(ro.product.device) = GT-I9070
error or something like that and i get stucked.
I'll downgrade again and keep it for one day until the night, i can't be without my phone one more day.
Click to expand...
Click to collapse
Wait, do you have I9070P? That error is shown if you try to install CM on I9070P.
shut_down said:
Wait, do you have I9070P? That error is shown if you try to install CM on I9070P.
Click to expand...
Click to collapse
nono, i have I9070. 100% sure.
I hope someone can help me.
I just got my GT-N7000 back from Samsung after a repair to the audio socket. The phone was rooted but Samsung returned the phone to the stock JB 4.1.2 ROM. All was working as it should when I got it back.
Now, I wish to re-root the phone and restore my choice of custom ROM - Ultimate _N7000_XXLT4_JB_4.1.2. v6.0 with all my apps and data. This is the ROM I've been using ever since it was published without issue.
I have managed to re-root the phone with the PhilZ Touch 5 recovery + safe kernel and CWM Base Version v6.0.3.7 which I think is the version I was using before. This part of the procedure appears to have worked correctly and I can now boot into the PhilZ Touch 5 recovery without any issue.
However, after restoring the backup I made prior to the audio jack problem and rebooting, he phone hangs after a few initial swipes through the screens ie I can no longer swipe screens or start apps and the phone is non-responsive. All I can do then is remove the battery. No errors are being reported during the Restore and I've taken care to Wipe data/Factory reset, Wipe Cache Partition and then Advanced >Wipe Dalvik Partion.
I tried the Restore several times but the result is the same. One thing that may be related is that my lockscreen image is not the one I was using when I did the backup. Nor is it the stock image of the book and quill pen that the stock ROM uses (it's a picture of a kid leaping into the air with a big bunch of balloons which I've never seen before). This could mean that something isn't being wiped properly.
Any advice from the experts would be most welcome as I'm out of my depth.
Trevor
Did you check in Philz recovery if the restore of Preload partition is enabled..?
nokiamodeln91 said:
Did you check in Philz recovery if the restore of Preload partition is enabled..?
Click to expand...
Click to collapse
Thanks for the reply. No, I didn't know to check that but will do so in future. I have never encountered that setting before. Is it usually enabled by default?
I think the trouble was that at least one of my backup files was corrupt. I tried an earlier one and this one seemed to have fewer problems so concluded that this was the source of trouble.
In the end, I downloaded a fresh copy of the Ultimate ROM I was using which got the phone fully working again and then let Google download all my apps automatically. So I'm out of trouble now.
Thanks again.
Trevor