I hope i'm not overlooking a thread where this was a problem but i'm at a loss after looking for 3 days. I was running Tonked world edition v2 (android 4.0.3) without problems for almost a year when I saw that 4.3 PAC was released for the Rezound and I thought I would try it out. It was a lot of fun but I use my tablet for most everything and world edition seemed to give better battery life. Everything worked fine with PAC when it was running and I got world edition restored just fine but for some reason superuser is acting really weird. It would allow any app that had super user permissions before the upgrade to work fine but any new app that needed root permissions after the restore is not working. I've been using Root Checker after each trial to see if root access has been restored and nothing works. Not even a request for root permissions shows up. I booted up the phone using adb to make sure I had boot access and flashed both superuser app 3.1.3 and 3.2-RC3 and also tried just the binaries 3.1.1 (each individually of course). After trying to flash superuser through recovery even though the apps listed in superuser were stil there nothing was being granted super user access anymore. I noticed that su in system/bin didn't have correct permissions and root browser wasn't able to change anything after losing root permissions so I used adb shell to try and change permissions, which I was able to change, but it didn't do anything to help the problem. The weird thing is even after wiping the system, cache, and davilk multiple times and a fresh install of the rom the same problem persists. The only thing I can think of is somehow the built in superuser app (part of aokp) is still interfearing with superuser somehow but I have no idea and like I said i'm stil at a loss of what else to try.
I apologize in advance if this has been answered somewhere eles but if anyone can point me in the right direction I would be very greatful.
I appreciate any help in advance and even the slightest advice will be helpful, thanks again.
czach5932 said:
I hope i'm not overlooking a thread where this was a problem but i'm at a loss after looking for 3 days. I was running Tonked world edition v2 (android 4.0.3) without problems for almost a year when I saw that 4.3 PAC was released for the Rezound and I thought I would try it out. It was a lot of fun but I use my tablet for most everything and world edition seemed to give better battery life. Everything worked fine with PAC when it was running and I got world edition restored just fine but for some reason superuser is acting really weird. It would allow any app that had super user permissions before the upgrade to work fine but any new app that needed root permissions after the restore is not working. I've been using Root Checker after each trial to see if root access has been restored and nothing works. Not even a request for root permissions shows up. I booted up the phone using adb to make sure I had boot access and flashed both superuser app 3.1.3 and 3.2-RC3 and also tried just the binaries 3.1.1 (each individually of course). After trying to flash superuser through recovery even though the apps listed in superuser were stil there nothing was being granted super user access anymore. I noticed that su in system/bin didn't have correct permissions and root browser wasn't able to change anything after losing root permissions so I used adb shell to try and change permissions, which I was able to change, but it didn't do anything to help the problem. The weird thing is even after wiping the system, cache, and davilk multiple times and a fresh install of the rom the same problem persists. The only thing I can think of is somehow the built in superuser app (part of aokp) is still interfearing with superuser somehow but I have no idea and like I said i'm stil at a loss of what else to try.
I apologize in advance if this has been answered somewhere eles but if anyone can point me in the right direction I would be very greatful.
I appreciate any help in advance and even the slightest advice will be helpful, thanks again.
Click to expand...
Click to collapse
go to settings> about phone> and tap build number until deveoloper options are available....when enabled go back into settings and go to developer options and ensure root access has access to apps and adb
REV3NT3CH said:
go to settings> about phone> and tap build number until deveoloper options are available....when enabled go back into settings and go to developer options and ensure root access has access to apps and adb
Click to expand...
Click to collapse
Developers options were already visible from the beginning with the Rom but that option to restrict root to apps and/or adb isn't there (at least on 4.0). I know the setting your talking about and I'm going to see if there is another way to enable it.
czach5932 said:
Developers options were already visible from the beginning with the Rom but that option to restrict root to apps and/or adb isn't there (at least on 4.0). I know the setting your talking about and I'm going to see if there is another way to enable it.
Click to expand...
Click to collapse
what recovery did you try to install superuser from
I would assume your current rom has SU built in, may want to consider a clean install. At least back up your current one and install it clean (with no app data restored) to see if it fixes the problem.
REV3NT3CH said:
what recovery did you try to install superuser from
Click to expand...
Click to collapse
CWM based recovery by Flyhalf205 v6.0.1.9
Never had any problem until now. I tried Amon-ra a long time ago but it wouldn't wipe correctly sip I've stuck work this one
mjones73 said:
I would assume your current rom has SU built in, may want to consider a clean install. At least back up your current one and install it clean (with no app data restored) to see if it fixes the problem.
Click to expand...
Click to collapse
This Rom doesn't have su built in and I've tried about every combination of wipes, flashes, and restores
-Trial-
I noticed that in system/bin that there were two files, su and su.bak su was at 0 bytes and su.bak was at 23k and I tried switching them around and also giving su.bak (renamed to su) full 777 permissions but nothing worked. After the file modification root checker failed much quicker though. Changed everything back
I just noticed after changing everything back that su had its permissions changed again. It is listed as -rwsr-sr-x which is full read only user write and full execute with suid and sgid special. I'm trying to find out but I can't find how to give all permisions with suid and sgid. Any idea if any of this helps or is the culprit?
czach5932 said:
CWM based recovery by Flyhalf205 v6.0.1.9
Never had any problem until now. I tried Amon-ra a long time ago but it wouldn't wipe correctly sip I've stuck work this one
This Rom doesn't have su built in and I've tried about every combination of wipes, flashes, and restores
-Trial-
I noticed that in system/bin that there were two files, su and su.bak su was at 0 bytes and su.bak was at 23k and I tried switching them around and also giving su.bak (renamed to su) full 777 permissions but nothing worked. After the file modification root checker failed much quicker though. Changed everything back
I just noticed after changing everything back that su had its permissions changed again. It is listed as -rwsr-sr-x which is full read only user write and full execute with suid and sgid special. I'm trying to find out but I can't find how to give all permisions with suid and sgid. Any idea if any of this helps or is the culprit?
Click to expand...
Click to collapse
install AMON RA 3.16 as it has the super user fixed into it under advanced....once installed just reflash your custom recovery of your choice....also that version of cwm is way out of date you want version 6.0.3.6...they get updated for many reasons such as stuff like this
czach5932 said:
CWM based recovery by Flyhalf205 v6.0.1.9
Never had any problem until now. I tried Amon-ra a long time ago but it wouldn't wipe correctly sip I've stuck work this one
This Rom doesn't have su built in and I've tried about every combination of wipes, flashes, and restores.
Click to expand...
Click to collapse
Kind of surprising someone would release a modded Sense ROM with no su..
Sent from my ADR6425LVW using Tapatalk
I'll try that as soon as I can. I figured why change something if it's not broken. I appreciate the help and I'll report back as soon as I can
- UPDATE-
Tried to use Amon-RA 3.16 and use the SU fix option under advanced options. It removed my other super user app and replaced it but nothing changed, no popup to ask for super user permissions. After that I booted up cwm 6.0.3.6 touch a couple of times and like it so I decided to flash it and now data and wi-fi are not working. But before flashing, I booted it up a couple time and tried wiping everything (3x) and tried both a clean install and a restore and same problem. Neither the Amon-RA, 3.1, or the 3.2 nor the manually flashed binarys do anything. I also found how to change the premissions for su but now when I try to chmod anything it says read only system. Seems like i'm going backwards and making no progress.
I still appreciate any and all help.
Sent from my SCH-i815 using XDA Premium HD app
czach5932 said:
I'll try that as soon as I can. I figured why change something if it's not broken. I appreciate the help and I'll report back as soon as I can
Sent from my SCH-i815 using XDA Premium HD app
Click to expand...
Click to collapse
also if im not mistaken...tonked had a mass multitude of issues for me....if you need the phone for global use and trying to stay stock and stable as possible there is much better options...to further help...for all ICS roms and lower use Amon Ra 3.16 period...for anything higher like jellybean or kitkat use cwm or twrp...amon ra was meant for the earlier roms as cwm and twrp were not
REV3NT3CH said:
also if im not mistaken...tonked had a mass multitude of issues for me....if you need the phone for global use and trying to stay stock and stable as possible there is much better options...to further help...for all ICS roms and lower use Amon Ra 3.16 period...for anything higher like jellybean or kitkat use cwm or twrp...amon ra was meant for the earlier roms as cwm and twrp were not
Click to expand...
Click to collapse
When I rooted my phone initially Amon-ra it wouldn't wipe correctly and kept force closing everything which is why I went with cwm. Before I went to pac and android 4.3 everything worked perfectly. I just don't understand why (with full wipes) and a restore with upgraded recoveries something from 4.3 is still messing with the system.
The main thing I want is longest battery life and if you can suggest something I'll try it but Tonked gave me over three days on one charge with minimal use. I could get 6+ hrs talk time with hours of Mog with a single charge. I'll try anything. My screen is cracked so I'm thinking of using warranty and get a refurbished phone and restoring that way but I don't want to be out a hundred bucks.
czach5932 said:
When I rooted my phone initially Amon-ra it wouldn't wipe correctly and kept force closing everything which is why I went with cwm. Before I went to pac and android 4.3 everything worked perfectly. I just don't understand why (with full wipes) and a restore with upgraded recoveries something from 4.3 is still messing with the system.
The main thing I want is longest battery life and if you can suggest something I'll try it but Tonked gave me over three days on one charge with minimal use. I could get 6+ hrs talk time with hours of Mog with a single charge. I'll try anything. My screen is cracked so I'm thinking of using warranty and get a refurbished phone and restoring that way but I don't want to be out a hundred bucks.
Click to expand...
Click to collapse
because with any recovery...a full clean wipe meaning you wipe cache, dalvik cache, system, boot, data, factory wipe, and android secure. you still have the main internal files that never get touched by any recovery....if your s-off you can run my downgrade upgrade guide to get back to full stock as the ruu's fully wipe everything....ive actually managed with both talon 1.0 and tachyon to get 24+ hourse of normal use
REV3NT3CH said:
because with any recovery...a full clean wipe meaning you wipe cache, dalvik cache, system, boot, data, factory wipe, and android secure. you still have the main internal files that never get touched by any recovery....if your s-off you can run my downgrade upgrade guide to get back to full stock as the ruu's fully wipe everything....ive actually managed with both talon 1.0 and tachyon to get 24+ hourse of normal use
Click to expand...
Click to collapse
But how would flashing pac modify anything that a full restore wouldn't change back? I know I used a ruu before, maybe I need to go and do that back to bone stock and upgrade from there. I go out of town for a couple of days and I'll try that and let you know. If you can think of anything else I will be greatly appreciative. Thanks Austin.
czach5932 said:
But how would flashing pac modify anything that a full restore wouldn't change back? I know I used a ruu before, maybe I need to go and do that back to bone stock and upgrade from there. I go out of town for a couple of days and I'll try that and let you know. If you can think of anything else I will be greatly appreciative. Thanks Austin.
Click to expand...
Click to collapse
again...most recoveries only wipes so much to an extent....even most samsung devices no matter how much you wipe in recovery you will eventually have to odin back to stock to start fresh as certain things are left behind from flashes...im only assuming some of your issues on 4.3 was sd mounting issues as well as rebooting....in the posts for them are the fixes for those issues...some of which requires TWRP only to fix...twrp is more stable than any of the recoveries because it has the fullest amount of wiping methods that you can ask for and always gets the job done right...get 2.6.3.0 as 2.6.3.3 is for kit kat only
REV3NT3CH said:
also if im not mistaken...tonked had a mass multitude of issues for me....if you need the phone for global use and trying to stay stock and stable as possible there is much better options...to further help...for all ICS roms and lower use Amon Ra 3.16 period...for anything higher like jellybean or kitkat use cwm or twrp...amon ra was meant for the earlier roms as cwm and twrp were not
Click to expand...
Click to collapse
Not sure if I have time this weekend but I just read your s-off tutorial and it seems straight forward but what I'm wondering about is going back to stock. Do I have to go all the way back to stock or could I just use the most recent ruu on your downgrade tutorial to get close enough to stock to wipe the rest of 4.3 and then go back to my Tonked Rom?
Never mind read the tutorial wrong. Will hopefully try this later and I'm hoping to get everything back to normal.
I didn't have time for s-off or time to go back to bone stock (your tutorial) but I did flash the latest ruu and got it to boot to bone stock ics and then flashed the same Tonked Rom and it booted and runs just fine but the only thing that it's granted su access is su itself. No time to mess with anything else yet but looks like I'm running out of options. I'll try your tutorial if I can.
czach5932 said:
I didn't have time for s-off or time to go back to bone stock (your tutorial) but I did flash the latest ruu and got it to boot to bone stock ics and then flashed the same Tonked Rom and it booted and runs just fine but the only thing that it's granted su access is su itself. No time to mess with anything else yet but looks like I'm running out of options. I'll try your tutorial if I can.
Click to expand...
Click to collapse
ha ok i see what you did....when flashing that ph98img file you wiped everything....even superuser....re download amon ra 3.1.6 recovery and install su&superuser via developer options in that and youll have su again
REV3NT3CH said:
ha ok i see what you did....when flashing that ph98img file you wiped everything....even superuser....re download amon ra 3.1.6 recovery and install su&superuser via developer options in that and youll have su again
Click to expand...
Click to collapse
Well even though I tried this before flashing the ruu but after flashing supersu in recovery everything is working correctly. i'm not sure why though but I lost both my two recent cwm backups (even though I used spare sd card during ruu flash). When I went to restore from my main 64 gig sd card, even tough the folder with the date showed up, when I went to restore it said no backup avail (or something like that) and then the folder disapeared. Also haven't had time to figure why backup disappeared or if any backups are currently working but i'll cross that bridge when I get time.
But back to the main issue. Looks like superuser has been having problems with a recent update where people were having the same problem I was having. I attributed it to downgrading but looks like a faulty app update (even though when I tried to look into it no one had said the update had any problems) I guess the upside was I wanted to reset my rom to stock and kinda reset, not really the way I wanted to do it, but lemons to lemonade. I really appreciate all the help and sorry for the stupid problem.
Related
Just updated the ruu found in the bamf remix 1.5 post and lost my root? Or seemed to.
First post because most the time I can find the answers through posts but this I can't seem to find.
I was previously rooted, flashed the new ruu via hboot and everything went smooth. Reboot, reinstall superuser and clockwork via marketplace, and superuser wouldn't take an auto update when it prompted me there was a new version out. Clockwork says I need root before it can do anything.
Few notes to consider :
- s-off is still there (least it says so in hboot)
- my first root I did was the longer way with Android sdk command line, no one click, no 400mb file
- dumb me is dumb, got excited about the new ruu and no nandroid backup
Now I'm chilling here, tried reboots, flash in hboot, and all I can do is sit here staring at my stick Rom like.... Herpa derp want root and bamf back
Help??? Please? Would rather not have to re root. As I won't have access to my computer for days.
-
Did you update to bamf 1.5, or someone posted the stock untouched ruu and you decided to flash that?
Download titanium back up and root, hit "problems?"
and install busybox.
Sometimes when I flash roms it will say i dont have root access, and go through titanium, hit problems, and keep installign busybox (ive had to do it up to 3 times)
and then it works for me
I used the ruu file that was posted in the bamf remix 1.5 thread in the first post right above the zip file for the actual Rom
And I didn't make it to installing bamf. Just finished with the ruu flash via hboot and was on my way to flash bamf when clockwork told me I didn't have root. This is when I went forum hunting about two hours ago :/
Samsuck said:
Download titanium back up and root, hit "problems?"
and install busybox.
Sometimes when I flash roms it will say i dont have root access, and go through titanium, hit problems, and keep installign busybox (ive had to do it up to 3 times)
and then it works for me
Click to expand...
Click to collapse
Wish I could say it worked for me... *sigh* guess I just really lost root then :/
So you didn't do any RUU, you flashed the radio. I flashed that radio before i flashed BAMF 1.5 and everything is working fine over here. Did you check MD5 sum to make sure that it downloaded correctly?
g00s3y said:
So you didn't do any RUU, you flashed the radio. I flashed that radio before i flashed BAMF 1.5 and everything is working fine over here. Did you check MD5 sum to make sure that it downloaded correctly?
Click to expand...
Click to collapse
Yeah. Little goofy on the terminology, fairly new to Android least. But yeah I always check any Rom or kernel or anything like that
I'm not sure, I don't understand how you can lose root just by flashing the radio, never heard of it happening before, sorry.
g00s3y said:
I'm not sure, I don't understand how you can lose root just by flashing the radio, never heard of it happening before, sorry.
Click to expand...
Click to collapse
No problem. I assume I did something wrong but I can't put a finger on it.
Ah well. I appreciate the help m8!
I'm gonna go out on the limb here and say that when you first rooted you never removed the zip file from you sd card and hboot pulled that image instead of the radio update.
afewgrams said:
I'm gonna go out on the limb here and say that when you first rooted you never removed the zip file from you sd card and hboot pulled that image instead of the radio update.
Click to expand...
Click to collapse
Possibly.... If I delete that. Download the new radio, and flash via hboot any ideas what would happen?
Edit... Yup that's what I did. I know... Im a genius swear I had moved that file and over written. Took a lot longer to flash that old file lol. Thanks!
Now just live with the stock sense UI and no root till I can redo that, /cringe
No Pants Hero said:
Possibly.... If I delete that. Download the new radio, and flash via hboot any ideas what would happen?
Edit... Yup that's what I did. I know... Im a genius swear I had moved that file and over written. Took a lot longer to flash that old file lol. Thanks!
Now just live with the stock sense UI and no root till I can redo that, /cringe
Click to expand...
Click to collapse
It's an honest mistake. I had the file on my sd for awhile before I found out. Glad I could help.
I did the same thing but I am stuck in Fastboot/HBoot. If I select reboot or power down in the Fastboot menu, I just come back to Fastboot. If I choose bootloader, I can't use the volume keys to select any of the menu options except the first one (Fastboot). After a few seconds it looks like it starts running the update process on PG05IMG but fails and says "Main version is older." Google/forum searches haven't shown me anything and I don't know where to go from here.
Similar problem
Hi, and thanks for bearing with a noob.
I have a HTC desire, rooted using unrevoked 3. I and I have tried a couple different ROMs successfully and was able to use Titanium Backup and ROM manager successfully, but after flashing cyanogen 7, I want to start using Titanium Backup, but it tells me could not aquire root priv., I went to the problems tab and it tells me make sure im rooted. did I lose root? the only choices it gives me from there is 'prefrences' and 'upgrade superuser' when i upgrade su. I did that to no avail.
also going into ROM manager it tells me ; superuser was not found.
anyway, i have been trying to search for the answer to this for a few days and have tried a couple things. my question is basically, did I lose root and need to unroot and reroot? or is there a way to enable superuser?
Thanks for any help
Hey all,
I'm very new to Cyanogen, so sorry if this is a very n00b question.
The ROM Manager doesn't appear to work. It keeps telling me I'm not running ClockWorkMod recovery, and cannot connect to the web to download. I purchased the premium version thinking it would solve this (as well as to support the dev), but no luck. Is it just an issue with the nightlies not capable of handling ROM manager yet, or is it a setting of some sort that I'm neglecting? It's not a huge deal, but it looks like such a nice, simple way to stay up-to-date with the nightly builds as opposed to updating through CWM, wiping, etc.
I saw a post mentioning to go into developer tools and enable root access. The closest I found was in settings and I allowed apps and ADB root access, but this didn't help.
Any suggestions would be greatly appreciated, thanks!
I'm a bit confused, Why do you require ROM manager? The CWM that is built in with the ICS Kang releases should be doing everything that is required, then again, your reply would matter.
I think I am having the same issue. When I try to Flash ClockworkMod Touch in Rom Manager it keeps telling me I need to first install ClockworkMod Recovery even though I have Recovery 5.5.0.4 currently installed. It did the same thing when I had Recovery 4.0.0.4 installed.
I even tried to "Flash ClockworkMod Recovery" (First option in ROM Manager) and it does nothing.
Any ideas?
BEcause the same menu is in the CWM recovery lol
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
From what I've heard the ROM Manager doesn't really work for the tab yet. If you want to update without replacing all your apps you can just flash the zip file in CWM without doing a wipe. If it causes problems then you could do a wipe & reflash afterwards.
Dolfan058 said:
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
Click to expand...
Click to collapse
ROM manager works but it's wonky on the ICS kangs. It doesn't do anything that you can't already do in recovery, so there's no real advantage anyways. Oh, and don't use ROM manager to install a new recovery, and CWR touch doesn't work for the GT10.
^You saved me the trouble of insisting Why thank you good sir.
Thanks for the replies. I'll keep updating through CWM.
Coffeebeans, obviously I'm following your thread (thanks for the good work!) and I tried flashing over once but I got a ton of process media FCs so I figured wiping was the best way to go and have done so ever since. Probably should invest in titanium backup at this point so I don't have to reinstall from market everytime I wipe.
Thanks again for the help y'all.
It worked once with 4/17 build of CM9. After that, it has never worked again. It boots into recovery and pretends its flashing, but stops half a second later and restarts.
Something odd happened today when I tried to update. It rebooted and phone locked up and screen went black. I took out the battery and put it back in then held up and power to go into CWM. All of a sudden Rom Manager took over and flashed the rom as well as the additional zips successfully and rebooted. Everything works.
CWM tries to flash from /emmc. Rom Manager tries to flash from /sdcard and fails. It may be due to the swapped mount points on CM9. in CWM they are still swapped, even if you check the use internal storage box and everything shows up properly in CM9.
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....
This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.
Let me start off by saying Im far from new to the rooting and roming game. Been through several phones. Never run into this issue.
Note 2 - i605
Team Win Recovery - Up to date
Clockwork Recovery - Up to date
MJ9 Radio from Zif
I am able to install CleanROM and Sophisticated. But when I attempt to install CM11, MeanBean, or Gummy the install fails. It attempts to unzip but always ends with failed. This occurs on both recoveries. I have even tried an alternative recovery. Nothing seems to get it done. Please someone help. Like to note I checked my external SD card for errors. It passed.
Sent from my SCH-I605 using XDA Premium 4 mobile app
General consensus seems to be that philz recovery is currently the recovery of choice for 4.3, id say give that a try
Note2.5
This same thing happened to me. I couldn't even install backups I had. I finally gave up, ODIN'd back to stock and reran casual, everything has been fine since. Even re-installing the same exact recovery.
Jiggabitties said:
This same thing happened to me. I couldn't even install backups I had. I finally gave up, ODIN'd back to stock and reran casual, everything has been fine since. Even re-installing the same exact recovery.
Click to expand...
Click to collapse
Im going to give that a shot. I think it may actually be the thing that sorts this all out. Not hat Phillz is not a good option. But that's the other recovery I already tried. Thinking that maybe the Casual I did was not smooth. As it did hang a couple times and was not as smooth as I would have liked. I am going to reply back when I do it to let everyone know how it turned out. Just in case someone else has the same issues.
:good:
So I odin stocked the phone. Perform casual. Much smoother this time. But still no dice. Still able to install only some roms.
Installable:
Sophisticated
CleanROM
Unable to Install:
CM 11
MeanBean ICE
MeanBean Reborn
Gummy
:crying:
Crotty.Josh said:
So I odin stocked the phone. Perform casual. Much smoother this time. But still no dice. Still able to install only some roms.
Installable:
Sophisticated
CleanROM
Unable to Install:
CM 11
MeanBean ICE
MeanBean Reborn
Gummy
:crying:
Click to expand...
Click to collapse
Hmmmm. Somewhere there's a step that's failing you (obviously). Maybe break down your process, from download to flash, and try to pinpoint where it's going wrong. In my experience the things that have caused an install to fail have been either an incompatible or outdated recovery, bad download (check the MD5), or borked system partition (which is when I Odin'd and re-casualed).
Had issues with CM11 until I ODIN'd back to stock LJB, unlocked bootloader/rooted, updated to latest TWRP 2.6.3.1 via ODIN, wiped all partitions included cache, data, dalvik, system, internal sdcard, external sdcard then adb push CM11 plus gapps and installed. Just make sure you can adb push before wiping everything along with checking file CRC and temporarily disable antivirus.
So I the issue ended up being one of an interesting nature but not normal. When I download thw rom of choice to my phone I move it to my SD card. Making sure its out of the distruction path. As is normal practice. I am using Rom Toolbox root browser to make the move. Turns out that although it gave the impression it was moving the files, it did not always do so. So each time I copy a file from place to another I have to check that it was done in full and without flaws. Quite an interesting problem. As a move of that sort should not break files.
Crotty.Josh said:
So I the issue ended up being one of an interesting nature but not normal. When I download thw rom of choice to my phone I move it to my SD card. Making sure its out of the distruction path. As is normal practice. I am using Rom Toolbox root browser to make the move. Turns out that although it gave the impression it was moving the files, it did not always do so. So each time I copy a file from place to another I have to check that it was done in full and without flaws. Quite an interesting problem. As a move of that sort should not break files.
Click to expand...
Click to collapse
It's always something small it seems. Good practice is to download the ROM, get it to it's final destination then check the MD5. I always wait until I've moved it to the SD to check the MD5 just in case there was a bad transfer.