Hey all.
So just a few hours ago, I was running rooted stock, as per the guide in the development section. I then installed twrp, and attempted to flash a ROM, which resulted in my phone not booting.
Since then, I got into recovery, attempted a factory reset (which didn't work), and ended up using Odin to restore to stock.
So now I'm sitting on the stock image, unsure if I have root. Everything seems to work fine, but is slow. Also, I cannot enable wifi (the switch goes on for a split second, then back to off).
Is there a way I can uninstall twrp, and go back to complete and total stock?
If it's relevant, I get a constant "This device has detected an application attempting unpermitted actions..." error.
Thanks guys!!!
UPDATE: It still has root access.
UPDATE 2: I'm finding some similar issues people were having with the T-Mobile version (http://androidforums.com/t-mobile-g...connect-wifi-prevention-information-help.html) though I'm not sure whether I can follow those solutions. I will wait until someone can advise me on this.
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
wolfgrrl said:
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
Click to expand...
Click to collapse
I tried the factory reset option from within twrp recovery, which doesn't fix any of these issues I'm having with constant security alerts or Wifi.
Got it fixed by doing this:
http://forum.xda-developers.com/showthread.php?t=2301259
Related
So I know there are few threads out there already on this topic, and i read through them, and I think my situation is a little different. I fully Factory reset my phone. I am on .173 right now, but when I go to apply the update, it downloads, reboots, installs about 25%ish, then the icon turns to the droid+exclamation inside a triangle, it reboots to home screen, and a message pops up that the install failed. I have the DRUtility 1.51. I've tried running the update with and without ROOT enabled. I've lost track of what RECOVERY mod im using/running and not sure how to find out what it is, but I think that is what is preventing the update from completeing. I've had Bootstrap installed at some point but that should be gone now since i did a factory reset. I also had clockwork mod installed at some point too. But I assume that is gone now as well due to the factory reset.
Any help would be greatly appreciated!
EDIT: Also my android version shows 2.3.6
Factory resets just clear the data on your phone. You will need to fastboot.
[TSON] said:
Factory resets just clear the data on your phone. You will need to fastboot.
Click to expand...
Click to collapse
sorry for being noob, but how do i do that and what is it? or can you point me to a thread that clarifies that?
EDIT: I found a youtube link detailing a fastboot method complete with RSD Lite 5.6.4 link and FastBoot file links. However, in the video it shows that it restores the phone to android version 2.3.5. This seems to be outdated. Will it still work for my purposes?
My issue is now resolved.
Used Droid RAZR Utility 1.51
Booted into AP Fastboot mode and used the utility to revert to .173
booted phone ran the update without issue.
Thank you mattlgroff for a great Utility.
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
I was recently on a rom and today i updated to CM 11, and couldn't make any calls, or texts. I could connect to 4G though which is weird to me... I then went back to beans rom 22 which is 4.1.2 thinking it'll work, but nothing. Can you please help me! Please. I have no idea what baseband i should be on.. thanks
You may have to odin either to a rooted stock rom or a complete odin unrooted stock image to fix it. I had a similar situation and after many attempts I was forced into going back to stock and rerooting and unlocking via adam outlers casual process which is located in the Verizon i605 development section. You will need to know what version you first rooted on and use that odin image to restore. Hoope this helps get yiu in the rigjt direction.
NUKED N2
Just do a factory reset from a touch wiz rom and it wii fix the problem... no need to poison back to stock.
Sent from my SCH-I605 using Tapatalk
I was having this exact same issue and still haven't resolved it. No, restoring to 100% stock does NOT fix the issue.
SJonesGSO said:
I was having this exact same issue and still haven't resolved it. No, restoring to 100% stock does NOT fix the issue.
Click to expand...
Click to collapse
Did you follow and use adam outlers restore thru Odin process back to stock?
NUKED N2
Room?
whos room are you using ? im using sspencer10 and everything is perfect just as a normal 4.4 kitkat very smooth and work 100% perfect u should try it out
If you load a TW ROM, then boot into recovery and wipe everything,then install the TW ROM it should fix it, don't do a restore from a backup as it won't fix it. I have used nephilims latest and it works every time. Also, once you install 4.4 you will probably loses phone and text if you try to install any other rom
Sent from my SCH-I605 using xda app-developers app
I'm in the same boat. Odin'd back to stock Verizon rom, but still no phone or text messaging. LTE works fine though.
After you get your tw rom loaded go into settings and do a factory reset. Do it from settings and not from recovery. You must run through the setup to reprovision your phone do not do a restore and it should fix the problem.
Sent from my SCH-I605 using Tapatalk
N_Jones said:
After you get your tw rom loaded without anything wiringgo into settings and do a factory reset. Do it from settings and not from recovery. You must run through the setup to reprovision your phone do not do a restore and it should fix the problem.
Sent from my SCH-I605 using
Awesome! Thanks man. That worked! I tried so much today but nothing worked. I really appreciate the advice.
Click to expand...
Click to collapse
ran into this issue made attempt to odin back to stock but got stuck at boot now cant communicate phone with computer?any help with next step please!
Hey all, I was wondering if there was an update to this? (Or if anyone else has found something that has worked)
Here is what I have tried so far (and all attempts have failed)...
** All the following attempts at installation used CWM Recovery 6.0.4.3 **
1) Install the ROM (SlimROM 4.4 over 4.3, clean install, wiped cache/data/system/dalvik 3x)
2) Flashed Nandroid of Stock TW ROM (rooted), then installed Slim 4.4 (Clean flash failed, then tried dirty flash, which also failed)
3) Reverted back to stock (The Official VRAMC3), Re-rooted, Installed CWM 6.0.4.3 (Dirty flashed first, which failed. Then did a clean installation, which again failed)
4) Flashed the new MJ9 Modem (with the 4.4 ROM installed), which failed.
Has anyone else had a similar problem, which then fixed it?
Same Issue
N_Jones said:
After you get your tw rom loaded go into settings and do a factory reset. Do it from settings and not from recovery. You must run through the setup to reprovision your phone do not do a restore and it should fix the problem.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Any other advice? This method did not work for me unfortunately.
Any update on this??
The above method did not work for me either.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Greetings-
I used the Cyanogenmod procedures to compile an image for my Note 3. The first time I installed it, the imaged booted up but I got a message about nfcservice not working. I do not recall the exact words, but it implied that nfcservice has an issue. I then, went into recovery and recovered an earlier image. The initial recovery try did not go well, and it was stuck. The last message was about the modem. But my next try worked. I had to use a backup I had from my stock firmware. Then I tried to install my unofficial image again. This time the phone went into download mode after I flashed my image. This keeps repeating, and I don’t know where to begin to troubleshoot this issue. Are there any logs I can look through? Aside from factory reset, I tried to clear all the other data; everything except the internal memory which holds my backups. But this did not fix anything. Do you have any advice for me? Oh, btw, this image is patched with seek-for-android patches. And I went through a lot to get it to work, since they did not support version 11. Thanks in advance.
RE
In my experience trying to troubleshoot something like this can be way more time consuming then un-rooting doing a factory reset back to stock OEM rom and then re-rooting and flashing the image again.
I'm new to rooting and it took me a while to get it working on my phone. It was going great though for over a year until today. I updated my phone with an AT&t update and after it booted me to the recovery area which I believe is called teamwin. I updated that too (like I have a couple of times) and my phone completely stopped working.
After troubleshooting for a few hours I was able to boot into safe mode, which I then did a factory reset. I've been able to install apps, but I none of them seem to work. Spotify is giving me error messages saying, (no storage area found) and when I installed zedge to look at ringtones and whatnot I couldn't install anything through there.
I'm assuming I have to redo the root process, but I was hoping there was another fix I'm not seeing. Like I said I'm very new to all of this. Any help would be awesome and also if I have to reroot is there any specific I have to do? Like getting rid of what I've done already?
KStef56 said:
I'm new to rooting and it took me a while to get it working on my phone. It was going great though for over a year until today. I updated my phone with an AT&t update and after it booted me to the recovery area which I believe is called teamwin. I updated that too (like I have a couple of times) and my phone completely stopped working.
Click to expand...
Click to collapse
You need stock recovery, as well as stock ROM (never rooted, unrooting does not work) in order to update OTA.
The phone tried to boot into stock recovery to install OTA; and since you don't have it (TWRP is a custom recovery), update fails.
General rule on Android, is that OTA updates don't play well with root. You should always research (for the specific device) before applying an OTA to a rooted device. That includes requirements to OTA, and also the expected results. On past devices, I've seen it not uncommon that an update removes the ability to unlock the bootloader and root. So its good to know what you are getting into before installing OTA.
KStef56 said:
After troubleshooting for a few hours I was able to boot into safe mode, which I then did a factory reset. I've been able to install apps, but I none of them seem to work. Spotify is giving me error messages saying, (no storage area found) and when I installed zedge to look at ringtones and whatnot I couldn't install anything through there.
I'm assuming I have to redo the root process, but I was hoping there was another fix I'm not seeing. Like I said I'm very new to all of this. Any help would be awesome and also if I have to reroot is there any specific I have to do? Like getting rid of what I've done already?
Click to expand...
Click to collapse
I suspect that your internal storage got corrupted somewhere along the way (as you were trying to OTA, recover, etc.). I'm not clear on the current status, you are still on the stock rooted LP ROM, with TWRP custom recovery?
If you still have working TWRP, I'd suggest booting into TWRP, select Wipe from the main menu, then the option to "Format Data" which will format internal storage. Strongly suggest not picking any other options (particularly in "Advanced Wipe" section) unless you know exactly what you are going. Lots of posts on here, by folks that delete things like System (OS) and wonder why there is no longer any OS!
After formatting internal storage, reboot and see if you still have the same issues accessing storage. If so, you may need to RUU back to full stock image, and root again. But we'll cross that bridge if the TWRP format storage option doesn't work.