Related
I've just flashed the ViperOneS v2.0 from v1.2.1 yesterday, I've followed all the instruction from the thread. After flashing the Rom, it keeps showing "Unfortunately, the process android.process.acore has stopped." I tried to send a bug report through the Venom Hub app, but it keeps telling the there is a error and it is unable to send the report. Can anyone tell me how to fix it?
Sent from my HTC One S using xda premium
re-download rom and check md5
did you flash boot image per instructions, if under .13 hboot you may be able to flash just the rom and no need to fastboot boot image
but, you need to wipe all including system in recovery 2X and not in aroma. i have my best luck that way
also try a full rom install as opposed to custom, if you did a custom
rugmankc said:
re-download rom and check md5
did you flash boot image per instructions, if under .13 hboot you may be able to flash just the rom and no need to fastboot boot image
but, you need to wipe all including system in recovery 2X and not in aroma. i have my best luck that way
also try a full rom install as opposed to custom, if you did a custom
Click to expand...
Click to collapse
my hboot is 1.13 and I did factory twice before flashing the rom, I'll try it again anyway. thanks for your help
I also experienced force close on certain app, is there any solution for it?
I've tried to wipe all the stuff and reinstall the rom, but the problem still exists. Is there any other solution for it? I can't even manage my contacts , whenever I want to link ny contacts, it force closes by itself.
Sent from my HTC One S using xda premium
cs96 said:
I've tried to wipe all the stuff and reinstall the rom, but the problem still exists. Is there any other solution for it? I can't even manage my contacts , whenever I want to link ny contacts, it force closes by itself.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Wipe systém twice
Sent from my HTC One S using xda app-developers app
I tried wiping all the stuffs twice, but the problem still exists
Sent from my HTC One S using xda premium
also on fc's clear apps data for tweaks and hub
redo it all again, but this time wipe sdcard first. of course back card up before wiping, just don't restore. i think new rom flash will repopulate what must be there like android secure and a couple others. someone can confirm that.
if it don't work you may want to go back to stock and start over
Is it necessary to wipe the sd card also? btw, I've lost the 3G connection after flashing the rom, I can only connect to the GSM network and when I switch to WCDMA only in my network setting, my phone shows no service is available. Is it the problem of the radio?
Sent from my HTC One S using xda premium
i can use any radio and have no issues
start over with a fresh flash of 2.1 the upgarde manually
don't have to wipe sdcard
but if you start over with full wipe 3x including system. and reformat your sdcard before doing all that. it only leaves your phone. not all phones work well on all roms.
best to fastboot boot image
don't wipe in recovery and aroma, just aroma
don't use twrp 2.4.3.0, or what ever number is for latest--leaving work so kinda in hurry
after you boot first time, reboot and clear caches and boot back into os
claer data on tweaks and hub apk's
not saying you need to do all this, it just eliminates everything but your phone
anyway--good luck
I got the same problem and just reflashed everything and it worked.
I tried reflashing everything but the problem still exists
Sent from my HTC One S using xda premium
Hi everyone. After 5 months, I decided to come back and try to root my phone again.
First, I'm on JB 4.1.2 with my VZW GS3.
I get to this step in the process.... Step 4 - Rooting Your Device and Unlocking Your Bootloader and every option I choose, tells me that the signature failed and the installation is aborted. Can someone tell me what I did wrong, if it can be fixed, and how?
I was once rooted before, and went back to stock using ODIN in the past. Will that have an effect on it?
When I got to Step 3, I used these instructions: •Flash the VRALEC Bootchain using ODIN v3.07 - My phone shows VRBMB1 - should I have used that boot chain instead? Can I still flash it using ODIN, over what is already there?
I can get my phone to boot normally, but when it boots it just shows custom at the bottom. I haven't bricked it or anything, I'm just concerned I haven't messed up the root process all together.
Thanks for the help...
Did you choose to install the zip in recovery or did you pick a different option? First make sure your zip is good and you didn't get a bad download. You can flash the VRALEC Bootchain whenever, and you must do it before flashing your recovery. If installing your zip isn't working in CWM try installing TWRP and flash the zip on that recovery instead. And no restoring back to stock with Odin won't affect anything.
Sent from my Verizon Samsung Galaxy SIII
joshua5683 said:
Did you choose to install the zip in recovery or did you pick a different option? You can flash the VRALEC Bootchain whenever, and you must do it before flashing your recovery. If installing your zip isn't working in CWM try installing TWRP and flash the zip on that recovery instead. And no restoring back to stock with Odin won't affect anything.
Sent from my Verizon Samsung Galaxy SIII
Click to expand...
Click to collapse
I chose to install the zip in recovery, and I did it after flashing my recovery.
Can I install TWRP using ODIN, right over the CWM installation? Will it hurt anything?
Thanks for your help!!
lou1210 said:
I chose to install the zip in recovery, and I did it after flashing my recovery.
Can I install TWRP using ODIN, right over the CWM installation? Will it hurt anything?
Thanks for your help!!
Click to expand...
Click to collapse
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.
lou1210 said:
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.
Click to expand...
Click to collapse
Yeah you're doing everything right I don't know why it's saying that. Try installing with TWRP - you can flash it at anytime and overwrite the old recovery.
Sent from my Verizon Samsung Galaxy SIII
lou1210 said:
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.
Click to expand...
Click to collapse
Your second and third step are wrong. You need to flash SuperSU in recovery NOT download mode. Download mode handles "tar" files, recovery handles "zips."
Edit: well, the latter half of your second step is wrong, pull battery then boot into recovery mode...home, volume UP, and power
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Your second and third step are wrong. You need to flash SuperSU in recovery NOT download mode. Download mode handles "tar" files, recovery handles "zips."
Edit: well, the latter half of your second step is wrong, pull battery then boot into recovery mode...home, volume UP, and power
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I'm sorry, I am doing the supers in recovery, not ODIN. I tried both CWM now and TWRP and still have the same exact error messages. Not sure what to do to fix this, but I'm almost ready to try to reverse what I did. I have been wanting to remove the bloatware and now I saw the Carbon ROM that looks pretty cool. If you can get me past this issue, it would be great.
Oh I just noticed you chose update. You have to choose to install in CWM not update. But if it didn't work in TWRP either it sounds like there is something wrong with the zip file. Have you tried redownloading the zip file?
Sent from my Verizon Samsung Galaxy SIII
lou1210 said:
I'm sorry, I am doing the supers in recovery, not ODIN. I tried both CWM now and TWRP and still have the same exact error messages. Not sure what to do to fix this, but I'm almost ready to try to reverse what I did. I have been wanting to remove the bloatware and now I saw the Carbon ROM that looks pretty cool. If you can get me past this issue, it would be great.
Click to expand...
Click to collapse
Here is another interesting thing....
Should I have an install or is Apply Update the same thing. When I boot into recovery, here are my choices:
reboot
apply update from adb
apply update from external storage
wipe data/factory reset
wipe cache
apply update from cache
Do I have the right version of recovery? Does this help any?
Ok. So I decided to download a new recovery file for CWM and this time it worked.
I'm not sure what told me to do it, but I decided to give it a go.
Next question, I remember the root processing being very involved with clearing cache, clearing dalvik cache, etc.
Is there a link to the newest process on how to root exactly and apply new ROMs? I of course will be backing up my existing ROM first.
lou1210 said:
Ok. So I decided to download a new recovery file for CWM and this time it worked.
I'm not sure what told me to do it, but I decided to give it a go.
Next question, I remember the root processing being very involved with clearing cache, clearing dalvik cache, etc.
Is there a link to the newest process on how to root exactly and apply new ROMs? I of course will be backing up my existing ROM first.
Click to expand...
Click to collapse
That's odd someone else had that issue where install wasn't an option. He ended up using TWRP. That clearing thing is for flashing roms. The way you flash every rom is wipe data/factory reset, clear cache, clear dalvik cache, and wipe /system. Make a backup before. I recommend using TWRP cause there have been times in CWM where I would try to restore and I would get an MD5 mismatch error, which I've never gotten on TWRP
Sent from my Verizon Samsung Galaxy SIII
I was thinking of using the carbon ROM. I realized that I didn't install the md5 file extension for cwm using ODIN so I went back and flashed it with one i was able to find, and it worked. I'm ok with using twrp but I haven't been able to find an md5 file for ODIN. Can you give me a link to one? I've only found .tar files and that seems to have been my problem. I might still try to use cwm now that I have my existing stock ROM backed up. Still debating.
On a side note, if I decide to unroot again, since I have not flashed, is there a method for that so I don't lose what I've got?
Sent from my SCH-I535 using Tapatalk 2
lou1210 said:
I was thinking of using the carbon ROM. I realized that I didn't install the md5 file extension for cwm using ODIN so I went back and flashed it with one i was able to find, and it worked. I'm ok with using twrp but I haven't been able to find an md5 file for ODIN. Can you give me a link to one? I've only found .tar files and that seems to have been my problem. I might still try to use cwm now that I have my existing stock ROM backed up. Still debating.
On a side note, if I decide to unroot again, since I have not flashed, is there a method for that so I don't lose what I've got?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
What do you mean you can't find the md5? You can flash the .tar twrp recovery in Odin the same way you flash md5s. And no sorry I don't know of any way to unroot without flashing a factory image. But to get your apps back you can use App Backup and Restore. It won't recover the app data obviously cause you need root for that but it's faster for restoring your apps so you don't have to make a list and download each one off the Play Store.
The file I had used didn't have an md5 filename and I think that's why it failed. I found one and downloaded it so it worked for me after that. Thank you for the unroot info too.
Sent from my SCH-I535 using Tapatalk 2
lou1210 said:
The file I had used didn't have an md5 filename and I think that's why it failed. I found one and downloaded it so it worked for me after that. Thank you for the unroot info too.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
No problem glad you got things working
Sent from my SCH-I535 using xda app-developers app
I succesfully added clockwork recovery, and installed the cyanogen mod 10.1 (4.2.2) to my phone, however when I click reboot, it gets stuck on the Samsung Logo
I then took the battery out and did a dalvic cache clear but the same issue occured... My install was succesfull, its just that it gets stuck on the Samsung Logo...
what have I done wrong?? Should I try install a different mod?? Or have I bricked my phone?? Or is there a foolproof way of installing a mod using Odin??
PS: (additional info)
I renamed the mod file before installing if that helps
I have no backup files
the only thing I can access on the phone atm is the Recovery Mode and Download Mode...
You would have backed up your previous rom..try fixing permissions....if not check cynogenmod is for your device or not.... If not download your device os reflash it by installing stock recovery.
Sent from my Micromax A110Q using xda app-developers app
I dont want to hijack this thread, but I have basically the same problem. I rooted my GT-I9300 phone and all was well, until I ran "NoBloat" to remove unwanted apps. Thereafter it runs up to the Samsung logo, then I get the following messages in succession: "Unfortunately messaging has stopped", "Unfortunately the process com.android has stopped", "smartcard service has failed" and "unfortunately the phone has stopped". I removed the battery, tried to flash the ROM again using the standard Samsung.tar file to restore to factory settings, but it made no difference. I am able to read the S3 files when linked to my Desktop and I can get it into download mode. I have run out of ideas and need help from the clever members.
If you get force closes fix permissions
Hit thanks if I helped
Sent from my Xperia Live with Walkman using xda app-developers app
Firstly, cwm doesn't work. Its garbage. I've semi bricked my phone well over 10 times trying to flash cm on it with cwm. Install goomanager and install TWRP to flash.
Secondly, once into TWRP recovery. Go to wipe>advance wipe> and select delvik cache, data, cahce, storage. Then go back to TWRP home and install the cm 10.1 and also the gapps package.
Sent from my SPH-L710 using xda app-developers app
Jeanrick said:
I dont want to hijack this thread, but I have basically the same problem. I rooted my GT-I9300 phone and all was well, until I ran "NoBloat" to remove unwanted apps. Thereafter it runs up to the Samsung logo, then I get the following messages in succession: "Unfortunately messaging has stopped", "Unfortunately the process com.android has stopped", "smartcard service has failed" and "unfortunately the phone has stopped". I removed the battery, tried to flash the ROM again using the standard Samsung.tar file to restore to factory settings, but it made no difference. I am able to read the S3 files when linked to my Desktop and I can get it into download mode. I have run out of ideas and need help from the clever members.
Click to expand...
Click to collapse
I think that bloatware app has taken away crucial files needed to keep the stability of an app up...
I don't know what I would do to fix that...
PS: please message me the samsung.tar file
dalton912 said:
Firstly, cwm doesn't work. Its garbage. I've semi bricked my phone well over 10 times trying to flash cm on it with cwm. Install goomanager and install TWRP to flash.
Secondly, once into TWRP recovery. Go to wipe>advance wipe> and select delvik cache, data, cahce, storage. Then go back to TWRP home and install the cm 10.1 and also the gapps package.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
if you dont like cyangenmod why did you brick your phone 10 times, why did you even go on after the second brick?
I love cm. I dislike cwm. I wanted the 4.3 jb on my phone.
Sent from my SPH-L710 using xda app-developers app
So I've downloaded all my apps and mods for my stock rooted Nexus 5(running android 4.4), how could I get and android 4.4.1 without unrooting?
Sent from my Nexus 5 using XDA Premium 4 mobile app
If you're using the stock kernel and haven't changed anything at all in /system, you can just flash the update in recovery. I'm stock rooted with TWRP, and it flashed just fine for me.
Could you give me a link to the update please!?
Sent from my Nexus 5 using XDA Premium 4 mobile app
roelmmata said:
Could you give me a link to the update please!?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's on the first page of general.
Did not work for me. Running stock with twrp. It mentioned something about unexpected info in build/prop file. Is it because I'm running art?
Sent from my Nexus 5 using Tapatalk
fytr4lyf223 said:
Did not work for me. Running stock with twrp. It mentioned something about unexpected info in build/prop file. Is it because I'm running art?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You must have modified your build.prop. Revert it back to stock and it should work.
posted this in another thread but wasn't getting much action, this one seems busier
Just flashed the official 4.4.1 zip file using TWRP onto my phone and rebooted...
Now i'm getting constant errors with every google application.
non-stop popups saying "unfortunately google play store has stopped"
My APN's all deleted themselves as well and now I can't even add any back in, I fill all the information in and I hit save and it doesn't save anything. No service now..
couldn't do a factory reset, button wouldn't respond
anyone else have any problems like this. I've tried wiping my dalvik and cache but that failed. had to wipe data first, then cache worked, then dalvik finally wiped...
I'll set my phone back up and see if it works now, just going through first boot procedures
Mines worked perfectly, no problems and camera loads and captures faster
Sent from my GN5 [D821]
djkorben said:
posted this in another thread but wasn't getting much action, this one seems busier
Just flashed the official 4.4.1 zip file using TWRP onto my phone and rebooted...
Now i'm getting constant errors with every google application.
non-stop popups saying "unfortunately google play store has stopped"
My APN's all deleted themselves as well and now I can't even add any back in, I fill all the information in and I hit save and it doesn't save anything. No service now..
couldn't do a factory reset, button wouldn't respond
anyone else have any problems like this. I've tried wiping my dalvik and cache but that failed. had to wipe data first, then cache worked, then dalvik finally wiped...
I'll set my phone back up and see if it works now, just going through first boot procedures
Click to expand...
Click to collapse
I actually had the same things you mentioned in my stock n5, I wasn't even rooted (just unlocked) and it suddenly did all the things you said. I did all the same you did haha but I had to reflash factory images and it worked again, but I have no idea of what happened.
Sent from my Nexus 5 using Tapatalk
_MetalHead_ said:
You must have modified your build.prop. Revert it back to stock and it should work.
Click to expand...
Click to collapse
I did, but still got the error. But then I pasted in my backup build.prop from ROM toolbox and it worked! Then while in TWRP I reflashed TWRP (TWRPception!). However, when I went to reboot it did not prompt me to root the device. So I'm running 4.4.1 stock kernel with TWRP, but no root. TWRP never prompts to root. Does anyone know of a .zip I can flash to root the N5 via TWRP?
fytr4lyf223 said:
Does anyone know of a .zip I can flash to root the N5 via TWRP?
Click to expand...
Click to collapse
Have a look in the sticky threads, at the top of general. It should be obvious which one
fytr4lyf223 said:
I did, but still got the error. But then I pasted in my backup build.prop from ROM toolbox and it worked! Then while in TWRP I reflashed TWRP (TWRPception!). However, when I went to reboot it did not prompt me to root the device. So I'm running 4.4.1 stock kernel with TWRP, but no root. TWRP never prompts to root. Does anyone know of a .zip I can flash to root the N5 via TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1538053
I was able to root using CF auto root :cyclops:
Did you maybe delete data for Google Framework in order to get the OTA quicker?
Dan Morrill (an Android engineer) said that that is REALLY not recommended because it can have all sorts of problems with all google apps. Doing that erases your device fingerprint used for push notifications, device identification etc. The playstore was definitely affected by this as well.
Source: http://www.reddit.com/r/Android/com...ear_data_for_google_service_framework/cdiymrp
i rooted my smg920t flashed a rom then odin back to stock so that i can have my wifi calling feature back and now an unfortunately android.process.media has stopped keeps popping up over and over and over again no matter what i'm doing please help or is there a rom i can flash that has wifi calling feature
You need to wipe data cache and dalvik before you flash.
I couldn't cause I used Odin to return to stock
Sent from my SM-G920T using XDA Free mobile app
Flash TWRP recovery from Odin and wipe from there.
that didnt work either
I had this issue back when I still had my old S3. It is usually solved by reflashing again the stock ROM via Odin.